5 ms·

> This has made me reconsider my intention use Elm in my startup. Choose Boring Technology http://boringtechnology.club/ http://boringtechnology.club/ Serious

> This has made me reconsider my intention use Elm in my startup. Choose Boring Technology http://boringtechnology.club/ http://boringtechnology.club/ Seriously, don't use up your startup's innovation tokens on some guy's hobby programming language.

cultofmetatron 7y ago
I used elixir for the backend and its paid off in dividends. That said, I had a year of experience working with it so it was boring technology for me at that point.
- hombre_fatal 7y ago
  I use Elm on two large websites in production with users. Elm helps me come back to these projects after months and, in two cases, a whole year, and get immediate work done without recredentializing in the whole codebase (which I have to do with my React projects to a greater extent). You definitely can't be a fragile developer to use Elm, and I think the small community size makes people feel like others are obligated to listen to their opinions. Meanwhile they don't expect this from an ecosystem like React because they know nobody is going to listen to them, the ecosystem is just too big with too many people with hobby horses. I've patched the compiler one two occasions for the 0.19 release. One was to allow me my Debug.crash calls. Elm is updated so slowly that it's trivial to maintain your own patch. Though I ultimately factored out my two patches. While TFA makes some good points, just like I can enumerate the downsides of all technology that I use, a large bulk of it is just emotional catharsis. And I think this kind of exodus is a good thing. A lot of the people who supposedly leave stick around like a turd circling the drain just to give their aggressive two cents any time something negative can be said about Elm. I've always felt that to be most tiring of all. Kind of like the people who show up in every Typescript-related thread to say how static typing is for lazy developers and what not.
  - dorian-graph 7y ago
    > One was to allow me my Debug.crash calls. This innocent line has a lot behind it, and probably a lot of PTSD for Elm developers. The Elm compiler has a --debug flag that would compile with a useful debugging window. It was fundamentally broken for how long? A year? There were many, many posts about it in that time, several community forks etc. There was little comment on this from Evan or the inner circle. The debug flag being broken, and seemingly ignored, is a horribly beautiful example of the blog post. Imagine having effectively the only debug tool broken for your main programming language
- dorian-graph 7y ago
  I think there may be a difference between less common and novelty, otherwise we'd all be using Java. Elixir (Erlang) has been around for a while and I would venture that the could be considered a little boring. It's like functional programming. It's been around for a long time and it's safe to use, but some people would call it exotic and be afraid. It's less common, but not exactly novel.

cultofmetatron 7y ago

I used elixir for the backend and its paid off in dividends. That said, I had a year of experience working with it so it was boring technology for me at that point.

hombre_fatal 7y ago
I use Elm on two large websites in production with users. Elm helps me come back to these projects after months and, in two cases, a whole year, and get immediate work done without recredentializing in the whole codebase (which I have to do with my React projects to a greater extent). You definitely can't be a fragile developer to use Elm, and I think the small community size makes people feel like others are obligated to listen to their opinions. Meanwhile they don't expect this from an ecosystem like React because they know nobody is going to listen to them, the ecosystem is just too big with too many people with hobby horses. I've patched the compiler one two occasions for the 0.19 release. One was to allow me my Debug.crash calls. Elm is updated so slowly that it's trivial to maintain your own patch. Though I ultimately factored out my two patches. While TFA makes some good points, just like I can enumerate the downsides of all technology that I use, a large bulk of it is just emotional catharsis. And I think this kind of exodus is a good thing. A lot of the people who supposedly leave stick around like a turd circling the drain just to give their aggressive two cents any time something negative can be said about Elm. I've always felt that to be most tiring of all. Kind of like the people who show up in every Typescript-related thread to say how static typing is for lazy developers and what not.
- dorian-graph 7y ago
  > One was to allow me my Debug.crash calls. This innocent line has a lot behind it, and probably a lot of PTSD for Elm developers. The Elm compiler has a --debug flag that would compile with a useful debugging window. It was fundamentally broken for how long? A year? There were many, many posts about it in that time, several community forks etc. There was little comment on this from Evan or the inner circle. The debug flag being broken, and seemingly ignored, is a horribly beautiful example of the blog post. Imagine having effectively the only debug tool broken for your main programming language
dorian-graph 7y ago
I think there may be a difference between less common and novelty, otherwise we'd all be using Java. Elixir (Erlang) has been around for a while and I would venture that the could be considered a little boring. It's like functional programming. It's been around for a long time and it's safe to use, but some people would call it exotic and be afraid. It's less common, but not exactly novel.