AnAmericanPotato
Switching to another Chromium-based browser is a half-measure. Other Chromium-based browsers are on borrowed time.
As time goes on, it will become more difficult for them to maintain v2 support. Nobody has the resources to properly maintain a browser fork with more than minor modifications. And you can bet Google will go out of their way to make this difficult for everybody else.
I mean, sure, use what you’re comfortable with if you really can’t use a non-Chromium-based browser for some reason. But it means you’re likely going to have to jump ship again sooner or later. Why not just jump once, to something with better long-term prospects?
Then again, the folks behind Arc Browser have expressed interest in becoming engine-agnostic, so perhaps there will be a Chromium-free Arc version in the future. That would be very cool.
I don’t know about strictly “unable” but there are a million contexts where it is a bad idea and simply not done. Like a spreadsheet or financial document. Or anywhere you want your text to behave like text — with a consistent font, color, style, etc. The difference between $ (text) and 💲 (emoji) is pretty stark in most contexts.
This will likely be rejected for one the same reasons that they decided they would not add any new flag emojis. Flags come and go. Bitcoin hasn’t even been around for 20 years yet, and its future is highly uncertain.
Also, considered as a currency, it would be better as a regular text character, not an emoji. Like $, €, ¥, £, etc.
everyone and their mother uses VS Code
This is usually a good reason to avoid something. Especially if that something comes from Microsoft.
This doesn’t seem to be a problem with disaster recovery plans. It is perfectly reasonable for disaster recovery to take several hours, or even days. As far as DR goes, this was easy. It did not generally require rebuilding systems from backups.
In a sane world, no single party would even have the technical capability of causing a global disaster like this. But executives have been tripping over themselves for the past decade to outsource all their shit to centralized third parties so they can lay off expensive IT staff. They have no control over their infrastructure, their data, or, by extension, their business.
The solution to the whitespace gripe is strictly enforced formatting standards with a git hook running a manually invokable script.
Throwing a linter into the pipeline just hardcodes the formatting at that point in the pipeline. That doesn’t really solve the issue, which is that style is not a one-size-fits-all concept, and displaying text appropriately is really the job of a text editor. To quote PEP 8, “default wrapping in most tools disrupts the visual structure of the code”. In other words, “most tools” suck at displaying code, because they are not language-aware. That’s the real problem. Hardcoding style is a workaround, not a solution.
That said, I wouldn’t consider intelligent editors to be a replacement for formatting standards, either. Ideally my text editor would display my Python code the way I like it, and then save to disk in accordance to PEP 8.
4 is sheer madness. 1 is common sense. 2 is just the cooler version of 1.
I’ve always found hardcoded style to be an obnoxious and counterproductive paradigm. It’s the text editor’s job to handle line wrapping, and there’s no reason a coding editor shouldn’t be able to format code intelligently. I hate hard line breaks that do not have meaning. Not everybody is using the same size windows! It’s 2024! We have the technology!