Line endings are a different question than indentation.

Language design decisions do matter. "Figure out how to view it in your editor" doesn't do one lick to address the problems of semantic indentation.

God no. Most of those hold no value or any interest for me. Bash only because it is the default shell. And thanks for pointing out why I should avoid the others.

Have you never looked at a diff? Massive whitespace changes hide real changes. Next someone will say "Git has a -w option". To which I say "A diff without whitespace changes in those languages would be useless". I can't test it, apply it, or otherwise use it without re-indenting the source myself.

Significant-whitespace languages don't introduce any additional whitespace changes because most people keep their code in whitespace-agnostic languages neatly indented anyway.

Then I guess you don't work on any projects that only want to see non-whitespace changes.

Swift, where semicolons are optional unless you have multiple statements on the same line.

Also C++, C99, and Java if you count // comments.

? How does Javascript use semantic whitespace?

I'm not sure of the details but surely the answer involves semi-colon insertion.

That's the only one I'm aware of.

Put me in the "if that makes a difference in your code, you're doing it wrong" camp (and yes, I recognize that not everyone agrees, and that argument has already been had too many times).

.kniht uoy naht tnatropmi erom s'ti spahrep os ytilibadaer stcapmi xatnyS