That's not really what I'm talking about. For instance, a few years ago when I was really into Elm, I wanted to implement a WebAudio library. Back when Elm was an FRP language, I thought it would be a great fit with the language's model.
I even got a proof of concept working and showed it off in the Elm Slack.
And then I got told my library would not get accepted on the official package repository because the core team was developing their own "correct" abstractions for the main Web APIs and they did not want third-party libraries to compete with the core team's libraries, as regular web developers don't know what they're doing and are incapable of choosing the "right" abstractions, which apparently only the Elm core team is capable of doing.
That experience turned me off Elm for good.
Flash forward to 2020: There is still no "official" Web Audio library. (There are a few non-official ones on Elm Packages)
It's your right to side with the core team, but they're the ones pretty much killing the language's chance to see any real usage.
I even got a proof of concept working and showed it off in the Elm Slack.
And then I got told my library would not get accepted on the official package repository because the core team was developing their own "correct" abstractions for the main Web APIs and they did not want third-party libraries to compete with the core team's libraries, as regular web developers don't know what they're doing and are incapable of choosing the "right" abstractions, which apparently only the Elm core team is capable of doing.
That experience turned me off Elm for good.
Flash forward to 2020: There is still no "official" Web Audio library. (There are a few non-official ones on Elm Packages)
It's your right to side with the core team, but they're the ones pretty much killing the language's chance to see any real usage.