3 ms·
To paraphrase Lloyd Bentsen: I've seen bad code and that isn't bad code. I prefer dynamic languages, but come on people. A type declaration makes 'good' code
by spooneybarger 16y ago
To paraphrase Lloyd Bentsen:
I've seen bad code and that isn't bad code.
I prefer dynamic languages, but come on people. A type declaration makes 'good' code 'bad'. I can't even... I mean... really? And this got 4 points so far? Yes, I'm having a disappointed in the world night otherwise I could ignore those 4 points. Still... 3 people saw this recently and thought that was a valid argument.
Sigh.
- silentbicycle 16y agoFor all we know, those four points on the new feed could be from bored and drunk/coked up people waiting for more Techcrunch or Apple fanfic. The intellectual rigor often doesn't kick in until after the single digits. See the flag button? The glowing, shiny, happy flag button?
- spooneybarger 16y agoI see the flag button. I like the flag button. It is my friend. Doesn't mean I can't occasionally lash out and say 'wtf do I keep having to use this flag button'. See note about 'disappointed in the world night'.
- deleted 16y ago[deleted]
- deleted 16y ago[deleted]
- gazetteer 16y agoI take it you find the one-liner more aesthetically appealing? I'm not arguing, just taking a survey. I'm deeply interested in what constitutes "good" code.
- spooneybarger 16y agoI dont prefer the one line. I find the argument that the multiple line version becomes bad code when you add type info to it ludicrous.
- gazetteer 16y agoIt seems I have communicated poorly. The point is not that the type info makes the code bad code, but that one-liners are bad code and that one-liners are encouraged by requiring type declarations.