4 ms·
This. People who disagree - why not write in Haskell?
by solatic 3y ago
This. People who disagree - why not write in Haskell?
- amelius 3y agoOne of these days an LLM will translate ecosystems to less popular platforms. Or at least it will write the glue logic.
- wokwokwok 3y agoIsn’t the irony of this that LLMs will only have enough training data to generate meaningful code for popular frameworks? Less popular platforms will get more isolated rather than less as the wave of generated code that “works out the box” only works with stuff like react…
- jppittma 3y agoIf I thought I could deliver a better product and faster with Haskell, I'd use it.
- wruza 3y agoPeople suggest adding other languages to browsers all the time. Why not - because then you get bombarded with thousands of “why you need that”.
- the_gipsy 3y agoWe write in Elm. To elaborate further: I don't believe ecosystem is king. Success can mean different things to different people, and is not always a single dimension of "popularity units".
- minthara 3y agoWe have one Elm project at work, and frankly it is a nightmare because no one wants to take those tickets and everyone avoids it like it is radioactive. Personally I have had to do quite a few of them and every time I find it worse compared to React, people just seem to hate it and it is very difficult to find people who want to work with it, so that project is now being rewritten in, guess what, react.
- the_gipsy 3y agoFrankly, I've worked with a couple React projects that are exactly like you describe, too.
- yCombLinks 3y agoThe key difference being the team has 20 people that are fluent in React, vs the guy that decided to write it in Elm and left last year.
- the_gipsy 3y agoI've seen those React projects get rewritten.
- z5h 3y agoI’ve had to deal with a nightmare Elm project. The difference is, I know what I’m doing. I solved all the problems, created examples to lead other devs and everything was fine. Have your company contact me if you need help.
- test098 3y agoi could say the exact same thing as a React dev. > I’ve had to deal with a nightmare Elm project. The difference is, I know what I’m doing. I solved all the problems, created examples to lead other devs and everything was fine. Have your company contact me if you need help. I’ve had to deal with a nightmare React project. The difference is, I know what I’m doing. I solved all the problems, created examples to lead other devs and everything was fine. Have your company contact me if you need help.
- jokethrowaway 3y agoghcjs is not production ready imho shipping as wasm is not an option as it increase bundle size for very little gain (unless you're running something super performance intensive). We would need a bridge between sane languages and a JS framework, not just JS in general. 5 years ago I would have done a Haskell -> hyperscript bridge to build frontend applications. Today I would do a Rust -> Solid.js bridge to build frontend applications. Logic could be compiled down to JS, UI could be compiled to Solid.js components.
- chpatrick 3y agoMany reasons not to use Haskell, not just the ecosystem. Source: 7 years of Haskell in production
- brigadier132 3y agoJavascript is the ecosystem. The majority of those react libraries are thin wrappers on vanilla javascript libraries.
- nobleach 3y agothis one's my absolute favorite: https://www.npmjs.com/package/react-public-ip?activeTab=code https://www.npmjs.com/package/react-public-ip?activeTab=code Not a single bit of "React" in the code. It has absolutely NOTHING to do with React. But I've seen it in projects I've inherited... just because, "we're using React, may as well get the React version of the library".