If you have to pick a line-feed style that works best overall, on all the platforms we support, and which is primarily designed for use in text files, i.e. stuff that you’ll open in a text editor, then CR/LF is the one that pretty much any text editor, on any platform, will get right.
It may no longer be the case, but when I first wrote this, maybe 10 years ago, using just a LF would produce files that were unopenable on the major platforms like Windows.
And being a cross-platform toolkit, it would be annoying if the same program produced different types of text output when you run it on different OSes. That’d mess up automated testing, GIT repos, etc. So a single choice of line ending makes sense for this.
“Obnoxious”? Really? You think this was a choice made to deliberately annoy people?
99.9% of the times that people will use the juce file writing classes, they’ll be generating plain text, XML, JSON, etc., where CR/LF is just fine. If you’re using it to create bash scripts, you may be the first and only person to do that, so why do you think this would be a use-case that we’d put at the top of our priority list?