3 ms·
Ugh, the community is barely alive and it's an unwieldy collection of non-orthogonal constructs. Generics and a few whiz-bang features doesn't paper over the s
by ballard 13y ago
Ugh, the community is barely alive and it's an unwieldy collection of non-orthogonal constructs. Generics and a few whiz-bang features doesn't paper over the sins upon sins. I see this project cutting back features or dying under the weight of crushing unmaintainability. (sad.)
- coldtea 13y agoThe above comment is content-free (at least argument wise). What are those "sins"? What are the non-orthogonal constructs, and how are they "non-orthogonal"? What's unwieldy about them? Seems mostly like pissing on somebody's work for the fun of it.
- commentzorro 13y ago>> ...unwieldy collection of non-orthogonal constructs... >> ...doesn't paper over the sins upon sins... Please elaborate. I didn't see any of that and honestly don't know what "non-orthogonal constructs" means. I'm no language design expert but would like to know what, to you, are the obvious deficiencies.
- ballard 13y agoNon-orthogonality: Multiple features that accomplish nearly the same result in different ways. For a language maintainer, this is another piece that will have to be supported, troubleshooted and documented. The other problem for users is that it gives a sense of confusion and uncertainty (Paradox of Choice) about the correctness of a program that may lead to multiple refactorings that don't add any value. Also, more features require more learning and makes programs harder to understand. The goals of any good language should be correctness and understandability. Arguably, Python learned the lessons from Perl. But there are many different languages, and some are better in different instances. What Nimrod turns into will be hard to say, but Go and Erlang need more competition.