Re:Rust, an Anti-Sloppy Programming Language
by the_af on Monday December 22, 2014 @06:22AM
(#8782715)
(Disclaimer: this is merely nitpicking, I get the gist of your original post).
I think your split of "Worse is Better"/"Better is Better" languages is a bit arbitrary. Everyone agrees that C is a Worse is Better language, but the rest? In particular, I cannot decide whether you equate OAOOW with Worse is Better or not -- Python is OAOOW, but I wouldn't say it's a Worse is Better language (and claiming it is because "you don't need speed" is like saying Haskell is a Worse is Better language because "you don't need the ability to easily reason about runtime performance". Every language claims "you don't need X"; that's clearly not enough to classify it as WiB).
Re:Rust, an Anti-Sloppy Programming Language
by BuckRogers on Tuesday December 23, 2014 @12:27AM
(#8786900)
Great posts. I'd like to add that 'OWLs' (one way languages) and 'MTOWLs' (more than one way languages) made the most sense to me. WiB and BiB makes sense too, because I knew what you were getting at. Having used many programming languages I've settled on 'WiB' languages as my preference. Though I consider WiB to actually just be better. :D
Complexity creeps in too quickly and too easily. While I don't like the WiB moniker, I definitely prefer OWLs. :)
Re:Rust, an Anti-Sloppy Programming Language
by gbersac on Monday December 22, 2014 @08:26AM
(#8782975)
I don't get what you mean by "Worse is Better" while I understand "One and Only One Obvious Way". The old phrasing is, IMO, better.
Re:Rust, an Anti-Sloppy Programming Language
by nostrademons on Monday December 22, 2014 @02:25PM
(#8784601)
"Worse is Better" is in reference to a fairly famous essay describing the dynamics of language & system software adoption:
https://www.dreamsongs.com/WorseIsBetter.html
...now that I'm rereading it again, I wonder if my original phrasing was better. The idea that I want to capture is that there's a difference in how these languages approach corner cases: the C/Python approach is to punt and say "We're not designed for that", while the C++/D/Ruby approach is to add a feature to the language to solve that one case. C++ is basically what happens when you extend a New Jersey school language to cover the corner cases that it originally chose to ignore; that doesn't actually make it MIT school (which is more a philosophy on how to design systems, not how they end up), but it does put it in a different category from C and Python.