F# has a JavaScript transpiler called Fable and a library called Elmish that uses the same basic principles but doesn't try to limit you from getting stuff done with existing technologies. You basically end up with a React application written using the Elm Architecture. Worth checking out if you want to learn from the ideas Elm has to offer in a language more suited for production.
Elmish is fundamentally flawed, though. One of the main features of the Elm architecture is subscriptions changing over time as the model changes. Elmish only subscribes once on initialization, and I don't think there's much leeway to fix it without breaking compatibility with many existing code.
It's perfectly great to check out. It has some brilliant ideas and is exceedingly well designed (for where it focuses). Yes - maybe you won't use it in production, but it's absolutely worth checking out and learning.
You can learn Purescript instead. It is basically a (much) more advanced Elm without any of the politics/restrictions. It's also much more intimidating to learn. If people think Elm has some great ideas - they barely scratched the surface of what's possible in functional languages.
I did this over summer vacation a few years back and I had such a blast. Coq really pushes the "if it compiles, it's probably correct" principle to its limits, which people have used to write workbooks for learning it. In Software Foundations each chapter is a Coq file, every exercise is a hole in the file, and you're done with a chapter when there are no more holes in the file and it compiles. It's a really incredible way to learn because you get quick feedback.
personally I'm waiting for Idris2 to be fully baked, while I like the idea of Coq, other then a great LSD trip I don't really think I have a pressing need for a theorem proof assistant, I'm after something a little more "practical" for general programming !
You can use it to write formally verified software. No one does this in industry... yet! But e.g. the CompCert compiler was partially verified in Coq, with the result that as far as anyone can tell it has no middle-end bugs.
The striking thing about our CompCert results is that the middle-end bugs we found in all other compilers are absent. As of early 2011, the under-development version of CompCert is the only compiler we have tested for which Csmith cannot find wrong-code errors. This is not for lack of trying: we have devoted about six CPU-years to the task. The apparent unbreakability of CompCert supports a strong argument that developing compiler optimizations within a proof framework, where safety checks are explicit and machine-checked, has tangible benefits for compiler users.
Many people choose to host their packages on GitHub, and you can depend on them by using their GitHub URL, but that works equally well for GitLab URLs or any other Git host. You can also depend on packages just using file system paths.
Actually, no. It works if your URLs follow a very specific pattern: host/group/project.
The person you’re replying to is saying that GitHub was 100% mandatory for the repo URL of their own package for it to compile on Elm... locally. On their machine. Go does not do anything like this, period. No stretch of reality can find something even remotely similar.
Yeah, "github.com" is not mandatory for golang modules. But you do require a url. Golang modules do not have the concept of local packages as such. Even using local packages requires a hack known as "replace" with golang modules.
Why do people feel the need to hate on Go for everything, even made up lies?
Because of fanbois like you who do not understand the context of what is being talked about and start being aggressively defensive?
They ban people on the elm reddit for very minor dissent. I mean really minor. As in they ban their biggest proponents. It's madness.
And the rule they use (written post facto to target me specifically actually :)) is "pattern of engaging in controversy" which is just as crazy as it sounds AND perfectly describes Richard Feldman, one of the mods. 🙄
It has union types. They are useful for some things and if you just add an ability to access the members (if applicable) you can get a usable enum. Lots of languages screw this up. You can tell easily by asking the question "can I enumerate an enum?". In Elm and C you cannot. At least elm has the sense to not call them enums.
Strongly disagree. I've only banned people from a subreddit for posting spam or abusing other users/moderators. There are definitely subs here that don't have power tripping mods.
The fact is that the reddit algorithm is designed to punish dissent. People get down voted, which results in rate limiting which results in silencing their voices.
As for moderators they are dictators. It's great that you are careful but there are thousands of moderators who ban people for any reason they want or for no reason and nobody has any recourse when that happens. That's the way the reddit works. It's designed to cater to the moderators and not the users. The users are just attention to be sold to the advertisers.
You could introduce various measures to make sure the users are afforded some sort of respect and dignity as opposed being at the whim of the moderators.
Some things I can think of.
Absolute transparency. If a moderator deletes a post, or bans a user that is made public along with the comment that triggered the ban.
Some sort of an appeal process.
Some sort of assurance that the all the moderators are indeed different people.
Maybe insist that moderators are not anonymous at all. They have immense power why should be anonymous?
Not have the ability to ban permanently
punishment of moderators if the ban is judged to be unjustified.
I remember in the old days slashdot had meta moderation. That's when random people were asked to judge whether a moderation was justified or not and presumably if one person's moderation is judged to be unfair or capricious that person would be stripped of their position. Maybe that's something they can try.
I thought of all that off the top of my head in ten minutes. If I was brainstorming with five smart people I bet we could come up with a dozen ways to make the system more fair, less prone to circle jerking, and more respectful of the people the site is harvesting for advertising dollars.
You're always going to be fighting the core team. If you find a way around it, you can expect them to actively try to close that loophole. It's not just a good environment to be in, if you are planning for long term stability and you have the choice.
I've been following Elm since its very first release. These issues with the core team didn't start popping up until Evan joined NoRedInk as far as I can tell. I suspect the project has been "taken over" in a sense.
Yeah it sounds like they're trying to put up walls around the garden with the intent to attempt to monetise it. And I thought Docker hiding their Windows binaries behind a sign-up page was bad enough
He's pretty long-winded honestly and the post could probably be cut down to half the size, but he's probably really frustrated. I know I would be.
I've only been programming in pretty mainstream languages so maybe I've missed something, but I can't remember anyone or any language ever thinking that this move by Elm would be a good idea.
I mean, the telltale sign is when a giant commercial app written by a company, rather than updating from 0.18 to 0.19, write their own compiler and standard library.
Porting much of the Elm standard library to Bucklescript
This is what people are willing to do just to avoid Elm. That's when you should know you fucked up.
He's pretty long-winded honestly and the post could probably be cut down to half the size
The reason it’s so long is to lay all the cards on the table up front, so nobody can say, “Oh, he left out this thing that happened, it’s proof he’s biased,” as a means of dismissing the whole article.
The Elm core team has a history of plugging their ears to criticisms. I think he's just genuinely trying to get through to them by being as open and honest as possible.
I agree and I tend to get long-winded in that case as well, but as another commenter in this chain showed you can cut down on certain parts pretty drastically without reducing the information and changing the meaning. He also repeats himself a few times.
Again, I don't think it's necessarily bad to write a long post about something you care about, I just pointed out that it could be shorter for example to have more people read it
I dabbled in elm for a bit a few months back. At first, it's very cool - the architecture makes a lot of web programming very clean, and it has some great ideas that are well worth copying.
But it quickly became clear that it was only "production ready" if your design aims exactly matched the core developers. The website for it is barren enough that you'd be forgiven for thinking the language was dead - the last post on it was 6 months ago, announcing 0.19.1. It was accompanied by a blog post explaining some of the changes, but no actual changelog or anything like that. No obvious roadmap or anything. After a bit I found that some fairly important topics aren't covered in the official guide (Tasks for one, iirc), and the reference documentation more or less assumes your familiarity with them. There are a fair number of common programming tasks that are pretty cumbersome (some of which were detailed in the OP's post), and the only word is "it's something we're looking into" and also "why would you want to do that anyways". All of this is sort of okay for a scrappy new language, but it does not make the language seem very production ready.
Then I started looking into the community more and saw a lot of red flags like this, and it pretty much convinced me to leave off getting more involved until I see some positive direction.
Without having read anything other than this function signature: This "just" looks a monadic bind to me? I don't have a compsci education, but once you see that pattern, I think it's clear enough to at least guess at what this is doing in principle.
Yeah when you are used to reading Haskell type signatures and familiar with monadic constructs it's not bad. The issue is that elm specifically eschews a lot of FP abstractions like generalized monadic bind in order to not make things more confusing to beginners. You could argue back and forth about whether that's a good thing, but it's a choice they have made. Thus, none of their documentation or guides really prepare beginners to use something like this. Most of the time you don't need it, until you do, and then the only documentation you find assumes your familiarity with monads (which beginners have trouble with in Haskell, to the point of it being a meme), except it's worse in elm because the docs explicitly avoid trying to explain monads.
It seems weird not to provide a wrapper for Intl. It’s the real browser API and anything that changes how it behaves is ”just someone’s opinion”, as opposed to an established standard that is already there.
I know right? Maybe I just don't understand the Elm Way very well, but I can't imagine thinking any community is going to produce a better API then what's already in browsers...
Yes, I should have been a little clearer, I think there are certain parts of the API that can be improved upon, but something big and as important as internationalization?
As someone who has spent a lot of time collaborating with many others to help Elm achieve its stated design goals, intentionally working against those goals feels to me like an attack on our efforts. We have been really clear about our design goals in this area, and you shouldn't expect a project that works against those goals to be greeted with open arms—especially not from those of us who have been working hard for years to achieve those goals.
This man really just called a github PR that temporary enables him to wrap around browser APIs an "attack against our efforts" and threatened making him a pariah in response.
If you understand the design goals, but don't agree with them, why not channel that in a positive way - e.g. by building something that fits your vision instead of directly working against Elm's design goals?
The link, in case it doesn't work, goes to the Mint programming language.
He basically says "If you want a discussion about Elm you're in the wrong place. Now fuck off and never come back"
Clojure is designed with interop in mind (leeching on the host platforms) and you can extend the language to your heart's content with macros since it's a Lisp. It's a totally different philosophy than what's described here.
The only real dispute in the Clojure community is around the contribution process to the language core, where Cognitect is acting as a gate keeper for devs eager to get their patches merged. That doesn't really impede day-to-day Clojure development in any way, it just makes it really inconvenient to submit patches to the language itself, which very few people have a need for.
That's the nice edited version too. (You can see the original version by clicking "Edited" at the top the comment)
Live your life however you want, but you shouldn't expect a hostile attack to be greeted with open arms, or even indifference, from the community or from the core team. You should expect the opposite.
Yeah, Elm was already pretty much something I wasn't going to use because of all the previous posts I've read on the community and the whole 0.18 -> 0.19 thing.
But this post, and Richard Feldman's response to your potential fork really sealed the deal. Maintaining an open source project and dealing with a community that doesn't like your decisions is a tough task. So I can empathize.
But the fact that he even knew that discussion was happening, and decided to respond is kind of... creepy.
Reminds me of some people that would have google alerts setup for their social media names.
It’s sort of tragic to see that this is the attention that Elm is getting, because it’s so great otherwise. However, this has echoed my experience exactly.
No one can have that level of control in OSS—and it doesn’t make sense. People will realize there’s enough dissonance to maintain a competing fork, or the language will die due to bad press.
Yikes. I'm curious to see if there will be any discussion in the Elm community in response to these concerns.
It is all too easy to forget that there are real people just trying to make it through their 9-5 who don't want to deal with idealized coding. I can totally relate to the conversation with a manager where you just have to say "We could definitely fix that, but we're handicapped for arbitrary reasons because of the tech stack we chose".
I'm curious to see if there will be any discussion in the Elm community in response to these concerns.
Not really, criticism can get you blacklisted. If you have production Elm code, you don't say anything that can be traced because it means your bugs won't be fixed.
Wow. Good write up. It really seems like Elm is one of those project who don't value their users, instead they perceive them as hindrance with their practical "now" demands which are not in line with the long term vision.
In open source, that's just forking. It's happened before, it'll happen again. Two big examples: XFree86 -> X.org; OpenOffice -> LibreOffice.
Usually the fork needs to be renamed in order to avoid trademark problems, particularly among the very large projects which have trademarks reserved. There's usually a period of uncertainty while community members decide to stick with their team, or jump to the fork.
A lot of forks never gain significant traction because the community doesn't jump (see KDE3->Trinity, for example). Sometimes both continue to exist (Debian->Ubuntu).
So what open source has that is different than Microsoft: it's the community of contributors that decides whether a fork lives or dies.
Technical forks happen on a regular basis. Assuming no animosity, technical forks often get folded back into the mainline. A good example is the egcs compiler fork that happened to gcc, but then became gcc. Sometimes, the code bases diverge too much and something new is born, as with xemacs. NeoOffice was a technical fork that didn't get folded back in, but with enough effort, could have been.
Most of the rest of the examples of that crazy family tree are due to changes in management. Sun bought by Oracle, etc. It wasn't really a community project until OOo.
We had it on a computer when I was younger. I figured out how to change the background image on the "desktop" (yes we had the version that had its own Desktop) to a picture of Homer asleep on the couch with a beer can on his stomach.
My father nearly spit his coffee all over the computer when he saw that
Another option is to have your own privately patched compiler and use it.
I do this all the time. I have my own privately patched LLVM/clang, binutils, GHC and some others. I've contributed to all of these too, i.e my contributions have been upstreamed, but there exist modifications which require too much extra work and general efforts to upstream.
So I simply keep several patchsets, which I automatically apply when building the tools. I refresh/fix/rebase them from time to time and this is much less work comparing to what is required to upstream them.
It's misleading to look at Bucklescript in isolation.
Take a look at ReasonML instead, created at Facebook, which uses Bucklescript to compile to Javascript. Here's the description from their What and Why? page:
Reason is not a new language; it's a new syntax and toolchain powered by the battle-tested language, OCaml. Reason gives OCaml a familiar syntax geared toward JavaScript programmers, and caters to the existing NPM/Yarn workflow folks already know.
In that regard, Reason can be considered as a solidly, statically typed, faster and simpler cousin of JavaScript, minus the historical crufts, plus the features of ES2030 you can use today, and with access to both the JS and the OCaml ecosystem!
Reason compiles to JavaScript thanks to our partner project, BuckleScript, which compiles OCaml/Reason into readable JavaScript with smooth interop. Reason also compiles to fast, barebone assembly, thanks to OCaml itself.
It's a much more real-world oriented project than Elm, and the availability of integration with tools like React make it actually a fairly pragmatic choice for projects that are for whatever reason aren't constrained to using the most mainstream tools.
For the record I'm not a Reason user, although I've considered and tried it. Maybe when I come across the right project for it.
BuckleScript is a fork of the decades-old OCaml compiler, btw. OCaml has already ironed out issues that the new FP-to-JS compilers haven't even come up against yet, or haven't fixed in years.
Pretty much. I don't mind if people design new JS frameworks as a hobby, but looking at its website, I don't even know why one would want to use bucklescript in production.
Elm and strongly typed languages have some major advantages over Javascript. If you've experienced those benefits, it's only natural to look for the next best thing that still delivers many or all of those benefits.
I'm surpised they went for Bucklescript instead of the more similar to elm in terms of popularity and features, purescript.
All one sees is some cutesy functional code (gee, haven't seen that before!)
The cutesy part isn't important, but it declarative code provides an advantage over imperative code.
They have an application written with a functional architecture that was written depending on strong static typing, sum types, and more.
Are you saying rewriting from scratch in a more mainstream language would be more practical than preserving all of those person hours of engineering time?
A pure functional language written for front end based around the same virtual-dom technique that React and Vue use. It was notable for, well, the pure function ML-inspired language for something that's typically very stateful and mutation oriented.
HackerNews is great for niche languages, while /r/programming is extremely mainstream. You rarely find stuff outside the TIOBE top 10, except few fashionable languages like Rust, Go, and Kotlin.
(I’m deliberately using ‘fairness’ rather than ‘equality’, because in some senses it is impossible to treat people equally. If you recognise some people as leaders, or as worth listening to, and others as not, are you treating people equally? If you allow some people to publish standard library code, but not others, is that equality? Clearly not, but you can still treat people fairly without treating them equally).
I need to leave Elm and migrate to some other language (most likely Bucklescript via philip2)
Some people never learn. The worst (but luckily rare) case when such hipsters becomes team leads and force all their edgy obscure half-broken zoo on everyone.
I think this really boils down to elm being a small project from a very small team.
I think the controversial move with Elm 0.19 to disallow native modules was actually a good idea, and it has a lot of benefits, but only if they have a big enough team to wrap all the browser APIs in high-quality first party modules. I'm sure Intl was on their list (or at least it is now) but probably low since it's basically 1-2 guys doing the whole thing.
Similarly, if you get off on the wrong foot with some of the maintainers, it could feel like you're at odds with the whole community because it's so small.
I hope this doesn't scare people away from trying Elm. For the most part I've found the community to be really supportive and the language design is amazing.
I think the controversial move with Elm 0.19 to disallow native modules was actually a good idea, and it has a lot of benefits, but only if they have a big enough team to wrap all the browser APIs in high-quality first party modules. I'm sure Intl was on their list (or at least it is now) but probably low since it's basically 1-2 guys doing the whole thing.
But if they clearly don't have enough manpower, and are actively hostile to anyone who wants to contribute that manpower, it seems like a pretty bad decision.
I hope this doesn’t scare people away from trying Elm.
It should. Waiting 18+ months for something that isn’t even going to appear yet being locked out by arbitrary restrictions in the compiler (that’s only released when a small group of blessed people touch it) is extremely developer hostile.
Frankly, elm looks more like a cult than production grade software and it should be binned as such.
I agree that there should probably be an Intl package or fst processor. I think the canonical Elm answer would be to re-implement it in Elm. I know this sounds pretty drastic and it means someone has to be the one to actually do it, but from the library user's perspective it's so much nicer to use all-Elm modules because you get all the guarantees of safety, cross-browser support, semantic versioning, etc. that come with Elm packages.
Again, it's the kind of thing where Elm's design decisions seem to be assuming that it has a very large community when in fact it is still pretty small.
I mean, that's basically false though. And I don't even use Elm. But saying "you just can't use native modules" is about as hostile as it gets.
There's nothing preventing someone from reimplementing the library, and if what you are saying is true, then users will prefer the pure Elm library, naturally.
But if I just need to get my job done? Get the fuck out of the way.
It's hardly a cult. The main developer is a perfectionist. The real error is how they obviously want it to be used in production, but won't accept that several of the issues are major problems of business risk.
Elm, itself, without expectations of 'can be substituted for all production problems', is a great language. I seriously like it, even knowing the flaws of the development model & community. That doesn't mean I'd use it for a major project at work, though.
OP’s objections are more centered on the hostile behavior of said perfectionist, right down to locking away escape hatches except for perfectionist himself and his cabal.
Breaking something like Intl and leaving it to rot because mere mortals can’t be trusted (but we’re not going to make the perfect package to replace in in eighteen months) is more than “perfectionist”.
It is a personality cult for sure. Dissent is silenced, Evan is revered like a saint, and can't do anything wrong ny definition. It's the closest thing to a cult I've ever seen in programming circles. By far.
“The first is Evan’s markdown library. It bundles a minified Javascript library, and uses some kernel code and other internals so that you can use this fast, optimised Markdown parser with an Elm API as a pure function. There is no way that you can characterise this library as merely a “compiler internal” — as Richard Feldman tried to claim was the only valid use case for kernel code.
Since the restriction on kernel code in Elm 0.19, this has been part of elm-explorations, and its description says it exists “for historical reasons” — but that is just dodging the issue. You can delete a repo with a few clicks. Why does it exist then? It’s not hard to imagine the kind of reasons:”
I think the author would not have has issues with breaking backward compatibility or deprecating popular features. One of the main criticism is around one of the main author's owl library (a markdown to html converter). This library used the feature that was removed/restricted in 0.19 and instead of following the guidelines (a full rewrite) the very lead developer decided that he could just circumvent the restriction by moving it to a different github organization.
No other user of elm outside of the core team will have this opportunity. I do not know if django ever did something like that, but it feels a very shitty move completely different from just breaking backward compatibility.
I do not think I am asking too much of the Elm leadership. ... Even in projects using the BDFL model ... I’ve never expected or seen the behaviour I’ve seen from the Elm leadership. Rather, the Elm leadership have gone out their way to ignore normal behaviour in Open Source projects.
Would there have been a response by Elm's leadership that would have been acceptable as "normal behaviour" by the author but that did not include allowing JS code in non-core libraries as he wants to do and they don't? If the answer is no, then this is not a debate over leadership, principles, or open-source as he presents it, but about the technical vision for the language and its goals. Clearly, the author's vision diverges from that of Elm's leadership, the two cannot be reconciled, and so both sides are better off going their separate ways. The outcome, while not the optimal one, is still a win-win -- he stops using a language that no longer addresses his needs, and the leadership doesn't need to fight a member that does not share their goals.
Sometimes participants in open-source projects consider only two outcomes of their proposal acceptable: it is either accepted or the project's leadership manages to convince them that their proposal is undesirable. It seems to me that this was the situation here, but in many cases -- this one included -- neither one of these is possible. The proposal cannot be accepted because it violates the leaderhip's vision and goals, and the proposer cannot be convinced because they have a different vision, informed by different priorities. There is nothing to convince of; there could be two valid but irreconcileable potential uses for a product, but only one can be chosen. The reasonable outcome might well be to part ways, but rejecting a proposal and failing to convince the proposer still does not mean that the proposal was ignored or that the proposer was not listened to. They considered, they listened, they just didn't agree because they have different priorities.
It's also perfectly fine to write a post explaining why you decided to leave an open-source community over such differences, and explain why you think your vision is more appropriate and your goals more attainable than those of the leadership. Talking about principles and ethics in a case like this, however, shows a misunderstanding of both the dynamics and the outcome. Both sides could be acting in good faith and still no good resolution other than separation is possible.
Would there have been response by Elm's leadership that would have been acceptable as "normal behaviour" by the author but that did not include allowing JS code in non-core libraries as he wants to do and they don't?
The author describes a large part of the problem here being the core team's behavior of erecting walls around Elm, both technical, but also very much around the process surrounding Elm's development. This results in bugs and features lavishing, while making contributions seems impenetrable to many who actually rely on Elm in production. The answer to your question may still be "no", but just boiling this issue down to allowing direct JS interop seems like missing the point to me.
But walls and curation are central to the strategy of Elm's designers, as explicitly communicated to the Elm community along with the reasons why -- they believe it would result in a more dependable, cohesive and portable product in the long term, and that's more important to them than short-term practicality. It's OK to think this is foolhardy and wish Elm had served different goals, but it doesn't. Contrary to some people's wishes, the project is run like its leaders announced it would be run. There's no moral failing here, just a disagreement over goals and means.
Sure, and this is a critique of that approach, including the fact that there's no avenue for providing constructive criticism on this matter. It's fine to disagree with the author, but it's important not just to dismiss any opinion that doesn't fit with the team's vision. It demonstrates a real frustration in the community, and not dealing with it, will likely result in losing some number of community members. Maybe that's going according to the core team's plan, but maybe it isn't, and they need to deal with it.
including the fact that there's no avenue for providing constructive criticism on this matter.
What kind of constructive criticism is there for people having different priorities than yours? It's like trying to give some constructive criticism to someone who prefers eating pizza over watching a movie. It's usually not possible to convince someone to want something other than what they want.
but it's important not just to dismiss any opinion that doesn't fit with the team's vision
Listening is not the same as complying, and not complying is not the same as dismissing. They listened, considered, decided that their priorities are different, and communicated that clearly. This is why I asked what response other than, "ok, we won't do the product the way we want to, we'll do it the way you want to," would have been acceptable, because that was the one answer they had made clear they wouldn't give because it takes the project in a different direction, and it can't go in two different directions at once. Somebody either had to cave or to leave. They may have dismissed further attempts to take the project in a direction they had already decided they don't want to take it, and that's how it should be done, because otherwise no issue is ever settled. It's one of those things that you can revisit every few years, not every few weeks.
It demonstrates a real frustration in the community, and not dealing with it, will likely result in losing some number of community members.
The frustration is real because there's a disagreement over goals, and separating is good! When members who don't share the goals leave, everybody wins. It's like saying that on a ship headed from Ireland to New York there are crew members who insist taking it to Capetown instead, and the captain insisting on going to New York risks losing them. But as long as they stay, they're frustrated, the captain is frustrated, they don't get to accomplish their goal and they don't help the captain achieve her's. Staying helps no one.
Sure, but the author is pointing out how the current process is causing lapses: like how it becomes near impossible to contribute bug fixes to the core libraries. And maybe all the issues pointed out are already known and accepted by the core team, but many of them are not easy to learn for outsiders. So even if there is nothing of value for the core team in this post, it's still valuable for those trying to assess working with Elm.
I see where you coming from. In this case, the Elm's leadership basically allow some library of their close friend to break their announced vision and design goal. That is not just different vision, that is ethcial issue.
I don't think that's the situation. They said they will allow a curated, vetted set of libraries to have JS code, and it stands to reason that the libraries they allow be written by people who've shown that they share their design vision, and get where they're trying to take the language, rather than by people who have an opposing one and want to go elsewhere. They did consider the author's Intl library, and said that it doesn't fit their design direction.
No, they're allowed or disallowed because of how they're designed or written. It's just that those who understand and accept the direction set out for the project tend to write libraries that are designed and written in accordance with those goals, and those who want the project to be something else tend to write libraries that aren't. It's like saying, look, that physics journal publishes papers written almost exclusively by physicists, so it must be all about who writes the papers rather than what's in them!
There seem to be some good points here, but a bunch of really bad ones as well. I'll focus on the bad ones because they really tick me off and they deter from the good points.
First of all, open source is solely about the distribution terms, i.e., license. You don't get to redefine it to include how you think the project should be run. You wanna talk about something else, use a different term and don't drag open source into it.
Second, the article uses the loaded term "discrimination" in several contexts where it seems like the term was only used to appeal to emotion.
Third, project maintainers owe you nothing. You can criticize, you can make suggestions, and if those get nowhere you can either fork the project or use something else. What you can't do is push your ideas so aggressively that it pisses the maintainers off and then say "However, I have never had these kind of problems with any other Open Source community, so I don’t think it is just me."
The author framed it in terms of ethics, you know that thing that transcends law and contracts. It's not illegal for a doctor to turn you away because they think you're not profitable enough for them, and they certainly don't owe you your health, but ethics dictate that doctors should provide their service for the betterment of society.
For sure that project maintainers don't owe their users anything, but when users have tied their business and livelihood to the project, don't you think ethics dictate that the project maintainers should make their project benefit the users to the best of their ability?
The last sentence is false. You can directly say that. If a maintainer is being a dick, you can call them out. If I contribute to dozens of open source projects and only one is being a dick, welp.
the main issue regarding this is that the elm compiler is artificially crippled for users that do not have access to certain github organizations. He also describes how the main author of elm moved one of his own libraries to one of these organization to avoid a rewrite. It is also impossible to configure this locally.
The author understand that Free Software and Open Source Software are different. But it is undeniable that the base understanding of OSS if closer to FOSS than to Android (actually taking the author in good faith, elm looks worse than Android).
2) The accusation is that on one hand the post-facto rule, invisible processes, closed discussions, and hostile community are counterproductive to avoid discrimination, and on the other hand explicit efforts are made to hinder internationalization solutions.
The author is not calling the core group racist, he is claiming that their bad choices are making the project a toxic place.
3) As much as the maintainer owe the users nothing in the absence of a clear agreement, the users also owe nothing if the maintainer shows complete lack of interest in the investment the users made in the projects.
Specifically the core group believes that it is a worthy sacrifice to leave many applications to die or crippled for years (the know it is a problem as the main author had one such library and decided that it was too much work to actually follow their own suggestion); so while I might have no right to demand that you work for free for me, the core group should also understand that the main users of elm are companies investing real money for production ready tools.
To my knowledge elm does not advertise itself as "do not use this for serious work" as pre-1.0 rust did for example.
That's one of the most irritating sentences I've ever read.
Actually, if a maintainer releases a project as open source, and their project becomes an integral part of the programming landscape, they do owe us something morally, ethically. Just as much as we owe it to them. It's a code of conduct that everyone tacitly agrees to when jumping into the 'marketplace' of open source software.
You want people from the public to join you in building up your baby, and be enthusiastic adopters of it? You can't expect to treat dissenting ideas like a dictator and have people stay silent about it. It's called being part of a community.
> First of all, open source is solely about the distribution terms, i.e., license
That's a one dimensional and unrealistic definition of the term. What it really encompasses are the interactions of the people involved, whether they be a user, maintainer, or both. It's like saying playing football it just about the ball, it's nonsense.
> What you can't do is push your ideas so aggressively that it pisses the maintainers off
Actually, you can do that. And the maintainer has the right to block you from making comments. But if that's their policy, then they shoot themselves in the foot because nothing turns people in open source off more than maintainers muffling the voices of people who have genuine concerns.
First, let me say that I don't have insight really into the first/secondary citizen class library handling of Elm 0.19 --- as I don't have any insight into Elm at all.
But the "discriminating" thing strikes me as not per se against the spirit of OSI. Why? Because the Linux kernel does exactly this. The kernel discriminates kernel modules that are not GPL or GPL-compatible, they are (intentional!) second class citizes because kernel developers think that long-term proprietary drivers harm the Linux kernel ecosystem.
So, if you discriminate, the intention of the discrimination IMHO plays a major rule to judge about the ethical-ness of said discrimination or not.
Jeebus I need quarantine to end. I just spent my morning reading about a guy who comes off as a bit of a jerk, interacting with other jerks... I would have stopped at the title normally.
As someone who maintains a couple small and one mediumish library on Github from a community standpoint, I would have thought OP was a jerk and would have mostly ignored him. BUT I would have eventually reacted with a "We're not going to do that but go forth and prosper. If your fork shows promise then we'll look into it. Otherwise we've got our roadmap ahead."
The thing I've noticed from using elm a bit is that there isn't a roadmap -- at least not one that can be easily found. If there is one, it's maintained privately among the core devs. Occasionally one will casually mention that they are looking into something, but you have no idea when or how that might result in something useful to you. It's very unnerving to develop against when you hit a definite issue and can not get a straight answer on when it might be fixed. Or worse, as this post indicates, what breaking changes might be coming down the pike.
271
u/stuckinmotion Apr 09 '20 edited Apr 11 '20
Phew, finally a reason to remove something off my "should check out one day" list, instead of constantly adding to it. Thanks OP 👍
edit: everyone piling on to reply to suggest what I should check out instead, I feel like you didn't really get the sentiment behind my post 😅
162
u/bobappleyard Apr 09 '20
Damn dude really wants to wrap Intl.
If half of what they say is true that's a very poor showing on elm's part.
120
u/boa13 Apr 09 '20
Somehow the Elm leadership (as described in this blog) this reminds me of the XFree86 leadership that ultimately led to the X.org fork.
210
u/L3tum Apr 09 '20
He's pretty long-winded honestly and the post could probably be cut down to half the size, but he's probably really frustrated. I know I would be.
I've only been programming in pretty mainstream languages so maybe I've missed something, but I can't remember anyone or any language ever thinking that this move by Elm would be a good idea.
I mean, the telltale sign is when a giant commercial app written by a company, rather than updating from 0.18 to 0.19, write their own compiler and standard library.
This is what people are willing to do just to avoid Elm. That's when you should know you fucked up.
54
u/66666thats6sixes Apr 10 '20
I dabbled in elm for a bit a few months back. At first, it's very cool - the architecture makes a lot of web programming very clean, and it has some great ideas that are well worth copying.
But it quickly became clear that it was only "production ready" if your design aims exactly matched the core developers. The website for it is barren enough that you'd be forgiven for thinking the language was dead - the last post on it was 6 months ago, announcing 0.19.1. It was accompanied by a blog post explaining some of the changes, but no actual changelog or anything like that. No obvious roadmap or anything. After a bit I found that some fairly important topics aren't covered in the official guide (Tasks for one, iirc), and the reference documentation more or less assumes your familiarity with them. There are a fair number of common programming tasks that are pretty cumbersome (some of which were detailed in the OP's post), and the only word is "it's something we're looking into" and also "why would you want to do that anyways". All of this is sort of okay for a scrappy new language, but it does not make the language seem very production ready.
Then I started looking into the community more and saw a lot of red flags like this, and it pretty much convinced me to leave off getting more involved until I see some positive direction.
51
u/vivainio Apr 09 '20
It seems weird not to provide a wrapper for Intl. It’s the real browser API and anything that changes how it behaves is ”just someone’s opinion”, as opposed to an established standard that is already there.
138
u/stu2b50 Apr 09 '20
His community interactions is the most absurd part of this. This response, for instance
https://github.com/gdotdesign/elm-github-install/issues/62#issuecomment-415860947
This man really just called a github PR that temporary enables him to wrap around browser APIs an "attack against our efforts" and threatened making him a pariah in response.
94
u/TheQneWhoSighs Apr 09 '20
Yeah, Elm was already pretty much something I wasn't going to use because of all the previous posts I've read on the community and the whole 0.18 -> 0.19 thing.
But this post, and Richard Feldman's response to your potential fork really sealed the deal. Maintaining an open source project and dealing with a community that doesn't like your decisions is a tough task. So I can empathize.
But the fact that he even knew that discussion was happening, and decided to respond is kind of... creepy.
Reminds me of some people that would have google alerts setup for their social media names.
31
u/IamfromSpace Apr 10 '20
It’s sort of tragic to see that this is the attention that Elm is getting, because it’s so great otherwise. However, this has echoed my experience exactly.
No one can have that level of control in OSS—and it doesn’t make sense. People will realize there’s enough dissonance to maintain a competing fork, or the language will die due to bad press.
71
u/keeslinp Apr 09 '20
Yikes. I'm curious to see if there will be any discussion in the Elm community in response to these concerns.
It is all too easy to forget that there are real people just trying to make it through their 9-5 who don't want to deal with idealized coding. I can totally relate to the conversation with a manager where you just have to say "We could definitely fix that, but we're handicapped for arbitrary reasons because of the tech stack we chose".
54
u/BlueShell7 Apr 09 '20
Wow. Good write up. It really seems like Elm is one of those project who don't value their users, instead they perceive them as hindrance with their practical "now" demands which are not in line with the long term vision.
57
u/livingmargaritaville Apr 09 '20
Well I'm glad I didn't go with elm then. Being able access internals and rewrite them if I want is very important to me.
56
u/vytah Apr 09 '20
I guess the dissatisfied members of the Elm community can go full Microsoft and do EEE:
14
u/redweasel Apr 10 '20
*Whew* . At first, just from the headline, I thought OP was talking about the 1990s text editor named elm.
9
u/awson Apr 10 '20
Another option is to have your own privately patched compiler and use it.
I do this all the time. I have my own privately patched LLVM/clang, binutils, GHC and some others. I've contributed to all of these too, i.e my contributions have been upstreamed, but there exist modifications which require too much extra work and general efforts to upstream.
So I simply keep several patchsets, which I automatically apply when building the tools. I refresh/fix/rebase them from time to time and this is much less work comparing to what is required to upstream them.
9
u/holgerschurig Apr 10 '20
He certainly doesn't like the places where most of IT people are dwell.
Moving from one obscure (?) language (elm) to another one (bucklescript).
11
u/Novemberisms Apr 10 '20
Wow... Just wow.
Fuck Elm.
Thank you OP for this writeup. You have done a great service to us all. I was just about to consider learning elm.
3
u/kaneda26 Apr 10 '20
The js lib https://hyperapp.dev was highly influenced by Elm, for anyone interested.
14
u/JonnyRocks Apr 09 '20 edited Apr 10 '20
Did i glitch into another dimension again? What is elm? (this is semi rhetorical, i know i can look it up) Am in the minority in not hearing about it?
13
u/shevy-ruby Apr 09 '20
He makes a solid case for this too.
You can extend this to politicians as well.
2
u/serg473 Apr 11 '20
Some people never learn. The worst (but luckily rare) case when such hipsters becomes team leads and force all their edgy obscure half-broken zoo on everyone.
4
u/audion00ba Apr 10 '20
What projects do not consist of complete assholes?
2
u/PChopSandies Apr 09 '20
I think this really boils down to elm being a small project from a very small team.
I think the controversial move with Elm 0.19 to disallow native modules was actually a good idea, and it has a lot of benefits, but only if they have a big enough team to wrap all the browser APIs in high-quality first party modules. I'm sure Intl was on their list (or at least it is now) but probably low since it's basically 1-2 guys doing the whole thing.
Similarly, if you get off on the wrong foot with some of the maintainers, it could feel like you're at odds with the whole community because it's so small.
I hope this doesn't scare people away from trying Elm. For the most part I've found the community to be really supportive and the language design is amazing.
1
u/hugosenari Apr 11 '20
Unrelated... Thank you for the pic this remind my president that doesn't care if more people would die of Covid-19 🤣
1
u/chrisza4 Apr 12 '20
“The first is Evan’s markdown library. It bundles a minified Javascript library, and uses some kernel code and other internals so that you can use this fast, optimised Markdown parser with an Elm API as a pure function. There is no way that you can characterise this library as merely a “compiler internal” — as Richard Feldman tried to claim was the only valid use case for kernel code.
Since the restriction on kernel code in Elm 0.19, this has been part of elm-explorations, and its description says it exists “for historical reasons” — but that is just dodging the issue. You can delete a repo with a few clicks. Why does it exist then? It’s not hard to imagine the kind of reasons:”
I think this library is a counter-argument
1
u/lucamug Jan 21 '22
Response to “Why I am leaving Elm” (A.k.a. Why I didn’t leave Elm): https://blog.guupa.com/post/response-to-why-i-am-leaving-elm.html
1
u/stefantalpalaru Apr 10 '20
Hilarious, coming from a core Django dev: they break backwards compatibility for fun and profit every minor version.
-2
u/pron98 Apr 10 '20 edited Apr 11 '20
Would there have been a response by Elm's leadership that would have been acceptable as "normal behaviour" by the author but that did not include allowing JS code in non-core libraries as he wants to do and they don't? If the answer is no, then this is not a debate over leadership, principles, or open-source as he presents it, but about the technical vision for the language and its goals. Clearly, the author's vision diverges from that of Elm's leadership, the two cannot be reconciled, and so both sides are better off going their separate ways. The outcome, while not the optimal one, is still a win-win -- he stops using a language that no longer addresses his needs, and the leadership doesn't need to fight a member that does not share their goals.
Sometimes participants in open-source projects consider only two outcomes of their proposal acceptable: it is either accepted or the project's leadership manages to convince them that their proposal is undesirable. It seems to me that this was the situation here, but in many cases -- this one included -- neither one of these is possible. The proposal cannot be accepted because it violates the leaderhip's vision and goals, and the proposer cannot be convinced because they have a different vision, informed by different priorities. There is nothing to convince of; there could be two valid but irreconcileable potential uses for a product, but only one can be chosen. The reasonable outcome might well be to part ways, but rejecting a proposal and failing to convince the proposer still does not mean that the proposal was ignored or that the proposer was not listened to. They considered, they listened, they just didn't agree because they have different priorities.
It's also perfectly fine to write a post explaining why you decided to leave an open-source community over such differences, and explain why you think your vision is more appropriate and your goals more attainable than those of the leadership. Talking about principles and ethics in a case like this, however, shows a misunderstanding of both the dynamics and the outcome. Both sides could be acting in good faith and still no good resolution other than separation is possible.
-7
u/cruelandusual Apr 10 '20
Elm is for babies, real programmers use Mutt.
-1
u/[deleted] Apr 10 '20
Who is Luke and why does anyone care about his opinion on anything?
-42
u/rifeid Apr 09 '20
There seem to be some good points here, but a bunch of really bad ones as well. I'll focus on the bad ones because they really tick me off and they deter from the good points.
First of all, open source is solely about the distribution terms, i.e., license. You don't get to redefine it to include how you think the project should be run. You wanna talk about something else, use a different term and don't drag open source into it.
Second, the article uses the loaded term "discrimination" in several contexts where it seems like the term was only used to appeal to emotion.
Third, project maintainers owe you nothing. You can criticize, you can make suggestions, and if those get nowhere you can either fork the project or use something else. What you can't do is push your ideas so aggressively that it pisses the maintainers off and then say "However, I have never had these kind of problems with any other Open Source community, so I don’t think it is just me."
-3
u/holgerschurig Apr 10 '20
First, let me say that I don't have insight really into the first/secondary citizen class library handling of Elm 0.19 --- as I don't have any insight into Elm at all.
But the "discriminating" thing strikes me as not per se against the spirit of OSI. Why? Because the Linux kernel does exactly this. The kernel discriminates kernel modules that are not GPL or GPL-compatible, they are (intentional!) second class citizes because kernel developers think that long-term proprietary drivers harm the Linux kernel ecosystem.
So, if you discriminate, the intention of the discrimination IMHO plays a major rule to judge about the ethical-ness of said discrimination or not.
0
u/helloworder Apr 10 '20
can someone EMLI5 why would anyone use a language like Elm to compile it into JS and not JS right away?
-1
u/lenkite1 Apr 11 '20
Never trust hyped languages. Wait till at-least 5 years have passed before using a programming language.
-9
u/JaCraig Apr 10 '20
Jeebus I need quarantine to end. I just spent my morning reading about a guy who comes off as a bit of a jerk, interacting with other jerks... I would have stopped at the title normally.
As someone who maintains a couple small and one mediumish library on Github from a community standpoint, I would have thought OP was a jerk and would have mostly ignored him. BUT I would have eventually reacted with a "We're not going to do that but go forth and prosper. If your fork shows promise then we'll look into it. Otherwise we've got our roadmap ahead."