Asset minification with Elm (2018)

Re:Asset minification with Elm (2018) by weavie on Tuesday August 27, 2019 @12:28PM (#20811471)

Microoptimizations performed by someone else is only really a problem if they sacrifice something else to acheive them. So if it meant that writing Elm code was a horrendous buggy experience in order to achieve that extra 50kb, then sure that's a problem.

But when its added on top of a really pleasant development experience then you don't really need to to think about it too much. All it really is saying is that you aren't paying for it with extra code bloat.. Which is a great thing!

[ Parent | on HN ]

Re:Asset minification with Elm (2018) by bastawhiz on Tuesday August 27, 2019 @12:52PM (#20811805)

I don't disagree that it's a net positive. My point is that aside from being a post about the technical accomplishments of Elm, it does little to sell me on changing my tools and language. I don't doubt that Elm is pleasant to work with, but I find React really pleasant to work with.

If the goal is to convince me to learn a new language for the weekend and play with it, telling me how I can save 50kb isn't huge motivation. Seeing actual examples of real world benefits are compelling for me, not artificial samples.

[ Parent | on HN ]