4 ms·
> This basically crippled the language beyond usability for everyone else. This is not true. You can argue that it was perhaps the downfall in terms of contrib
by the_gipsy 4y ago
> This basically crippled the language beyond usability for everyone else.
This is not true. You can argue that it was perhaps the downfall in terms of contributions and popularity. But you don't need native code for writing apps in Elm.
- imustbeevil 4y agoYou don't need a hammer to hit a nail, but if you hand me a screwdriver I'm going back to Node.
- matsemann 4y ago[flagged]
- the_gipsy 4y agoYea, exactly. I have written a complete functional game in Elm, with multiplayer over websockets, push notifications and whatnot. It has daily users to this day. I never needed "native" code. Maybe some decisions were wrong, as I said. Elm is not popular today. But they are also right in some aspect: I don't need another TypeScript (but with weird syntax).
- JoeyJoJoJr 4y agoWould you mind sharing a link to you game :)
- danabrams 4y agoI’ve written quite a bit of elm professionally and it was an issue for me and was a contributing factor (but not sole factor) to leaving Elm behind. A viable solution to my problem in professional contexts would have been private packages, which I believe Gren supports, so perhaps Gren would be a solution today, but I’ve moved on. That said, what’s happening with Gren is interesting and I applaud it.
- fyzix 4y agoThe fact that the maintainers made a whitelist for their projects disproves your point.
- the_gipsy 4y ago"Their projects" were core libraries or experiments IIRC.