3 ms·
It’s really starting to look like language design goes better via benevolent dictator. Committees don’t lend themselves to coherent and consistent overall visi
by Havoc 3y ago
It’s really starting to look like language design goes better via benevolent dictator.
Committees don’t lend themselves to coherent and consistent overall vision
- rcarmo 3y agoI'm starting to think that just doing a set of "stdlib" packages for R6RS that roughly matches what Python has (including essentials like SQLite, HTTP servers and requests and JSON/EDN support, together with some common patterns) would have been easier and actually gotten somewhere by now :)
- varjag 3y agoCommon Lisp committee did just fine: produced one massive standard which has been a lasting foundation for three decades since, and dissolved. Certain popular non-Lispy languages have standards committees too with generally positive effects.
- bmacho 3y agoHaskell committee did a fine job as well > After the release of Miranda by Research Software Ltd. in 1985, interest in lazy functional languages grew. By 1987, more than a dozen non-strict, purely functional programming languages existed. Miranda was the most widely used, but it was proprietary software. At the conference on Functional Programming Languages and Computer Architecture (FPCA '87) in Portland, Oregon, there was a strong consensus that a committee be formed to define an open standard for such languages. The committee's purpose was to consolidate existing functional languages into a common one to serve as a basis for future research in functional-language design. [...] https://en.wikipedia.org/wiki/Haskell#History https://en.wikipedia.org/wiki/Haskell#History
- crote 3y agoI don't think Haskell is a good example. In my experience, real-world Haskell requires enabling half a dozen language extensions, most of which have only been implemented for GHC and some of which are mutually incompatible. Over the years Haskell has evolved from a well-defined language into "anything people managed to get merged into Haskell". Learning it is now an absolute nightmare as you are basically required to understand a dozen poorly-documented extensions to use even very basic libraries.
- deleted 3y ago[deleted]
- tome 3y ago> some of which are mutually incompatible I don't know of any. Could you please name some? > Learning it is now an absolute nightmare as you are basically required to understand a dozen poorly-documented extensions to use even very basic libraries Many extensions make Haskell easier to learn since they remove unnecessary restrictions imposed by the standard.
- crote 3y agoI haven't used Haskell in a few years, but back then one which really bit me was DeriveAnyClass (introduced in 7.10.1) and GeneralizedNewtypeDeriving (introduced in 6.8.1). Until the introduction of DerivingVia in 8.6.1 it was impossible to tell Haskell which deriving strategy to use - which is extremely annoying when one library requires the one, another library requires the other, and due to issues with orphan instances you have to use them in the same file. > Many extensions make Haskell easier to learn since they remove unnecessary restrictions imposed by the standard. I completely agree, and Haskell 2010 is obviously lacking. Unfortunately, there are also a lot of extensions which people have abused to their fullest extent to create completely unreadable code. Things like UnicodeSyntax and all the syntax overloading are heavily overused, and you simply can't expect a beginner to immediately grok phrases like "if OverloadedLabels and MagicHash are both enabled then x#y means x# y, but if only OverloadedLabels is enabled then it means x #y". And of course there's the whole cuckoo's egg of Template Haskell just waiting to blow up in your face...
- tome 3y agoInteresting examples, thanks! I have to nitpick a bit though. You said "real-world Haskell requires enabling half a dozen language extensions ... some of which are mutually incompatible". 8.6.1 is 5 years old at this point, so the conflict between DeriveAnyClass and GeneralizedNewtypeDeriving is hardly a pertinent example. The conflict between OverloadedLabels and MagicHash is even less of an example, because the average real world Haskeller never uses MagicHash (and rarely OverloadedLabels: I've never used it once in 10 years of professional real world Haskelling).
- deleted 3y ago[deleted]
- deleted 3y ago[deleted]
- pm215 3y agoPerhaps, but if you take the "single person with strong control" path then I think you tend to get a different set of failure cases instead. For a small language, a benevolent-dictator can (unintentionally, through bad decisions) take the language in a direction that just causes it to dwindle into insignificance. For a large language, they can make mis-steps with big consequences (maybe the Python 2->3 transition counts here?). Sometimes what an established language needs is mostly "write things down, keep all the implementations moving in the same direction, don't make big changes or break compatibility", and in that situation a committee can be a good approach. I think the C standards committee have overall done a reasonable job within that kind of remit.
- rollcat 3y agoIt's also about what Scheme is and isn't, and what it certainly isn't is another C. A BDFL would attract a certain following, but some people are not interested in following anyone in particular - and Scheme is there for them. I'm 100% certain that if a single Scheme implementation emerged as dominant, and appointed a single BDFL in charge of producing all blessed RnRSs & SRFIs, the remaining Scheme implementations/community would continue to do their own thing, because that's what Scheme is about. (See the general response to R6RS as an example.)
- sanderjd 3y agoI dunno, maybe the python 2 -> 3 transition itself didn't go great, but I think python 3 has been a better foundation for python's wild popularity explosion over the last decade. I think if anything it's (in my opinion) more an example of not pulling the band-aid off quickly enough, rather than an example of why you shouldn't break backwards compatibility.
- _ph_ 3y agoI disagree. Good design comes from discussions and review. There isn't one person who comes up with great designs. Rather, experience shows it is the other way around. Don't get me wrong, when you have a project which needs to advance quickly to a target, having a strong leader who can make final decisions is of course very beneficial. But that is not the case here. The basic language is designed (and has been for decades). The challenge now is to design a language standard which will need to have good community support. Which requires buy-in from enough participants. Of course, even a standards commitee can and should have a strong leader and we are discussing exactly that position. But only a leader, not a dictator, however benevolent that might be.