Of all the hills to die on. What an unbelivably silly one.
CRLF sucks, suck it up. As many others have noted, there are millions of devices this idea puts in jeopardy for absolutely no reason.
We should be reducing the exceptions, not creating them
3000% agree. I have been bitten endlessly by autocrlf. It is absolutely insane to me that anyone ever considered your having your SOURCE CONTROL tool get/set different content than what's in the repo
But that output is wildly more variant between applications, especially for cases involving escape sequences, whitespace handling, and so on. All of these are specified in JSON
I can make whatever I want in a [{},{},{}] and it be valid JSON. If it's the first time you've used my thing, you'll have to somehow look up how the JSON is structured. Whether that's from howtousething.com, man thing, or thing --help, you'll still need to find out what thing does. it doesn't matter if it's your thing or my thing, but some how, thing needs to be able to tell people what to do. there is no universal thing that thing outputs. otherwise, nobody would need yours or my thing, but someone else's thing already does it.
I would keep things simple and make an Electron app, then either bundle ffmpeg or use ffi to call out to it. That'll get you going right away with the performance you need
There are only a few viable routes to go when building a desktop app without pulling out any remaining hair you might have, and as usual HN delivers reems of bad advice to use the worst of the worst.
That's very interesting to hear. This last weekend down here in Florida was unbearable.
I got my first sunburn in like 20 years, just last Saturday.
And I'm out in the sun every weekend wakeskating.
This looks great, but within the first 5 seconds I'm surprised by the lack of an Undo/Redo facility. I can't imagine myself using a tool like this without it
