3 ms·
It's a fascinating experiment. A language that's actually a single developer's walled garden, where they make all the decisions, write all the code, and person
by Lazare 9y ago
It's a fascinating experiment. A language that's actually a single developer's walled garden, where they make all the decisions, write all the code, and personally vet every library. (There must be other languages where the language team devs hvae to individually approve every package before allowing it to be added to the package manager, but I certainly haven't run across it before!)
It's quite enjoyable to watch, but obviously it's not scalable or sustainable in the general case.
> Elm's management has left me with the impression of a really smart, well-intentioned hellscape.
That seems fair, yes.
My personal view is that there's about a 90% chance the project will collapse under its own weight before it ever hits a release and becomes a normal project, but there's a 10% chance it'll (one day) migrate into a real language (with a real governance model, an actual team working on it, bugfixes being shipped, etc.).
- dennisdamenace 9y agoYou are wrong. Anyone can publish a package for Elm - without approval. What you can’t publish is a package with JavaScript in it. And, if you understand Elm, this makes sense. Elm has no runtime errors - which means any JS has to be perfectly designed. Elm is not to be bound to just a JavaScript platform. Elm has ports for interior. As for bug fixes - there appear to be some cases where there are bugs, but I have never come across any. The langauge just works. The slow pace of releases is a business adavatage - we don’t need to be upgrading every N months. The last upgrade had tools to automate almost the entire process. Anyway. Would you wager that Elm will fail? I will put up $1000 to your $9000.
- Hurtak 9y agoHow would you define "fail" in such bet?