3 ms·
Perhaps to dissuade the lowest common denominator of programmers that get hung up on such superficial trivialities.
by reinhardt 14y ago
Perhaps to dissuade the lowest common denominator of programmers that get hung up on such superficial trivialities.
- TylerE 14y agoBut it's not triviality - it's noise - Signal: Good - Noise: Bad, got it? If you REALLY need end of line markers, any half-way competent text editor can display them for you.
- Kiro 14y agoYou obviously have no idea what signal-to-noise ratio is about if you think semicolons are noise. Who are you trying to impress?
- pekk 14y agoEnd of line is already encoded in source files as \n. Redundancy isn't noise, but it is redundant.
- seanmcdirmid 14y agoIf end of line always means end of statement, by all means get rid of semi colons. If some non-trivial algorithms is used to infer end-of-statement boundaries that is more complicated than detecting end-of-line, then...there will be subtle problems. I went through this transition before in Scala, the error messages got a lot worse after semi-colon inference was added. I wound up telling people to add semi-colons to their code when they were scratching their head at some sort of parse/type error message.
- andrewflnr 14y agoSemicolons are distracting, both reading and writing, and mostly useless. If it's not "noise" in a technical sense, is it not still a bad thing? I don't think this should be a complicated question.
- stcredzero 14y agoIt all depends on what you define as signal and what you define as noise.