Has anyone started a project with elm and continued it for a long time?
How about cross mobile apps (ionic/cordova)?
Asset minification with Elm (2018)
51–59 of 59 posts
Re: Asset minification with Elm (2018)
#52Re: Asset minification with Elm (2018)
#53Earlier quoted context omitted.
> Every new release brings something new. Elm giveth, and Elm taketh away. I remember seeing stories about how new Elm versions removed some bits of functionality available in the previous versions...
It is true. Elm has taken some syntax away and native packages, and made the language better by being simpler and error free (I have never had a runtime error). Upgrades since 0.17 have been pretty easy too - there is automated tooling that does the heavy lifting.
Migration ease really depends on your use case. I am currently doing the upgrade on a production application, and some changes (dates, navigation/fullscreen) have been a pain.
The more automatic stuff that can be caught by the compiler is usually a breeze, though.
Re: Asset minification with Elm (2018)
#54Has anyone started a project with elm and continued it for a long time?
I've had a hobby game in Elm which I worked on for about a year and a half and I was the second engineer ( frontend lead ) hired to 'rescue' a greenfield project with Elm as the frontend. That is now at 100k+ LOC, 2.5 years later. Our team has grown from 3 to 9, we have 3 frontend devs all writing in Elm and looking for our 4th.
The company now has 4 production projects with Elm as the sole frontend tech.
Re: Asset minification with Elm (2018)
#55Has anyone started a project with elm and continued it for a long time?
I've used Elm for frontend pretty much exclusively since 2016. In the last two months I changed jobs and now write a bunch of typescript, and it's fine, but would much prefer to be writing elm...I mean, I'm only working on backend right now, but still...
Re: Asset minification with Elm (2018)
#56Has anyone started a project with elm and continued it for a long time?
We've been using it for almost two years. I wrote this just after the 0.19 release and still stand by it; I wouldn't start a project in Elm again until I'd explored more options (in particular purescript).
https://www.reddit.com/r/programming/comments/992qe5/elm_019...
Re: Asset minification with Elm (2018)
#57I don't want to downplay Elm's accomplishments here, but I really disagree with the "RealWorld" example here. Does a 29kb asset make a meaningful difference compared to a 100kb asset? Especially if the framework is a fixed chunk of that, the space savings as the project grows in size is not incredibly meaningful in the grand scheme of things. 50kb of excess code on my page due to missed optimizations isn't going to k…
> I don't want to downplay Elm's accomplishments here Then refrain, eh? How is 71% size reduction not a meaningful difference? You don't pay for bandwidth?
Because it's a pointless benchmark. Comparing percentages for an artificial app that's small enough to reasonably print out at 12pt text doesn't show anything meaningful. Seventy kilobytes, even on a bad device on a slow connection is hardly noticeable. Show me real meaningful data.
Re: Asset minification with Elm (2018)
#58Has anyone started a project with elm and continued it for a long time?
I've used Elm for frontend pretty much exclusively since 2016. In the last two months I changed jobs and now write a bunch of typescript, and it's fine, but would much prefer to be writing elm...I mean, I'm only working on backend right now, but still...
I'm curious about why you prefer Elm over TypeScript, as both are statically typed