4 ms·

> Evan responded, giving the all clear, and put up this Roadmap as a way to put into writing that the project was stable, not abandoned, and give an idea where

> Evan responded, giving the all clear, and put up this Roadmap as a way to put into writing that the project was stable, not abandoned, and give an idea where it's headed next. Strange, because this document isn't a roadmap at all. In fact it says absolutely nothing, just that Elm isn't going to change for the foreseeable future. And in the Elm community, "isn't going to change" means no updates or bugfixes, period. RIP Elm.

savanaly 6y ago
Yeah, it's pretty light on the exact details of what's coming. Although it does justify why that's the case in the last paragraph. In any case I'm happy making my side projects in Elm as it is and not changing is to me a bonus. Let me put it this way: I have an "empty side project" template I use when I start a new project every month or so, and invariably something about it is out of date every time I do so, and it's one of the biggest barriers to starting new things. Also invariably, updating the dependencies I have baked in turns out to be harder than I expect and eat up a bunch of willpower and time. But it's never Elm that is the culprit! It's always the CSS framework, the bundler, the minifier, the something else. I wish to god that other technologies worked like Elm did to be honest, at a glacial pace. It's not like they ever give me any startlingly new benefit; I have to go through hour+ annoyance just to get back to zero! I liked Tailwind 1.X or whatever, why did they have to update to 2.0 and I have to go through all this trouble... Elm stands athwart that tide and says no, I'll only release an update every four years, and it will introduce only extremely carefully considered, elegant changes. Refreshing.
- michaelcampbell 6y ago
  > It's always the CSS framework, the bundler, the minifier, the something else. Well, for 4 things, the rate of change of that group is on average 4x the rate of any one thing. I get your point, but it's rare that something that would cause a break in any one framework is not some biggish change IN that framework, so ... > It's not like they ever give me any startlingly new benefit; ... may not be a "startingly new" change FOR YOU, but it may be for someone else.
  - savanaly 6y ago
    I mean, looking at the change notes for e.g. Tailwind 2.0 which is the latest one to cause me pain, hardly anything in it was a response to changes in the CSS handling of the browsers. It's all shuffling of namespaces, additions of little conveniences, etc. The sort of thing that makes sense in isolation, but overwhelms one when every part of your stack needs to do it several times per year. Sure, Elm could do the same thing, rearranging the chairs on deck, and make some people marginally happier. I'm really happy it doesn't though because of the externalities that would cause.

savanaly 6y ago

Yeah, it's pretty light on the exact details of what's coming. Although it does justify why that's the case in the last paragraph. In any case I'm happy making my side projects in Elm as it is and not changing is to me a bonus. Let me put it this way: I have an "empty side project" template I use when I start a new project every month or so, and invariably something about it is out of date every time I do so, and it's one of the biggest barriers to starting new things. Also invariably, updating the dependencies I have baked in turns out to be harder than I expect and eat up a bunch of willpower and time. But it's never Elm that is the culprit! It's always the CSS framework, the bundler, the minifier, the something else. I wish to god that other technologies worked like Elm did to be honest, at a glacial pace. It's not like they ever give me any startlingly new benefit; I have to go through hour+ annoyance just to get back to zero! I liked Tailwind 1.X or whatever, why did they have to update to 2.0 and I have to go through all this trouble... Elm stands athwart that tide and says no, I'll only release an update every four years, and it will introduce only extremely carefully considered, elegant changes. Refreshing.

michaelcampbell 6y ago
> It's always the CSS framework, the bundler, the minifier, the something else. Well, for 4 things, the rate of change of that group is on average 4x the rate of any one thing. I get your point, but it's rare that something that would cause a break in any one framework is not some biggish change IN that framework, so ... > It's not like they ever give me any startlingly new benefit; ... may not be a "startingly new" change FOR YOU, but it may be for someone else.
- savanaly 6y ago
  I mean, looking at the change notes for e.g. Tailwind 2.0 which is the latest one to cause me pain, hardly anything in it was a response to changes in the CSS handling of the browsers. It's all shuffling of namespaces, additions of little conveniences, etc. The sort of thing that makes sense in isolation, but overwhelms one when every part of your stack needs to do it several times per year. Sure, Elm could do the same thing, rearranging the chairs on deck, and make some people marginally happier. I'm really happy it doesn't though because of the externalities that would cause.