| Did I miss some sort of formal directive from Microsoft or is this just outrage that someone dared do something not up to your standards? It's just the way it works, it isn't my standards, it is literally any piece of software that detects line breaks. Nobody's being punished. Configuring your dev environment is something people do for every language. No one has to configure around this issue because it is trivially solved and dealt with by every piece of software on the planet. It takes longer to write an error message than it does it just split a line correctly. Let's add some perspective here: we're talking about a single runtime option for your text editor of choice. Let's add some perspective here: they intentionally broke their own software to upset 72% of their potential users. More to the point, why isn't your editor or IDE properly supporting Zig files? No one has to care about zig, it's a niche language that doesn't care about its users, it's irrelevant except for hacker news threads. If some language started demanding you save all your text files with carriage returns or will will error out, what would you think? You sound like a lawyer grasping at straws instead of someone with a reasonable perspective that wouldn't be hypocritical when flipped around. |
Were I in a situation where I needed to work with something not expecting LF line termination I'd either configure my dev environment appropriately or find tools that do what I want.
So when it's your tool selection nobody has to care? But when someone else makes a decision you disagree with it's the end of the world? Gotcha. Don't check that checkbox. Stay mad, bro.