The real Elm has been at version 2.5.8 for many years. Why didn't these guys pick a name not already used by a famous piece of software?
Small Assets without the Headache in Elm 0.19
21–30 of 129 posts
Re: Small Assets without the Headache in Elm 0.19
#22They forgot Mithril[0] in the size comparisons -- I haven't seen anything useful beat it in size/value ratio. [0]: https://mithril.js.org/
Here's the link:
https://github.com/gothinkster/realworld/blob/master/README....
Have fun!
Re: Small Assets without the Headache in Elm 0.19
#23> If you have ever tried to use ADVANCED_OPTIMIZATIONS in Google Closure Compiler, you know that this is extremely difficult even when you write all the code yourself Perhaps, but it’s quite nice when you use languages that were built to support Google Closure from the beginning, like Clojurescript. Then it is painless and built into the build process automatically, and you get to benefit from all the other great adv…
Re: Small Assets without the Headache in Elm 0.19
#24They forgot Mithril[0] in the size comparisons -- I haven't seen anything useful beat it in size/value ratio. [0]: https://mithril.js.org/
https://realworld-mithril.netlify.com/
I have minified and gzipped `main.js` and it end up around 26k.
Re: Small Assets without the Headache in Elm 0.19
#25Re: Small Assets without the Headache in Elm 0.19
#26> If you have ever tried to use ADVANCED_OPTIMIZATIONS in Google Closure Compiler, you know that this is extremely difficult even when you write all the code yourself Perhaps, but it’s quite nice when you use languages that were built to support Google Closure from the beginning, like Clojurescript. Then it is painless and built into the build process automatically, and you get to benefit from all the other great adv…
The big surprise though, is how few other new library/framework/platform/languages/whatever have followed this path.
Re: Small Assets without the Headache in Elm 0.19
#27Re: Small Assets without the Headache in Elm 0.19
#28> If you have ever tried to use ADVANCED_OPTIMIZATIONS in Google Closure Compiler, you know that this is extremely difficult even when you write all the code yourself Perhaps, but it’s quite nice when you use languages that were built to support Google Closure from the beginning, like Clojurescript. Then it is painless and built into the build process automatically, and you get to benefit from all the other great adv…
Re: Small Assets without the Headache in Elm 0.19
#29> If you have ever tried to use ADVANCED_OPTIMIZATIONS in Google Closure Compiler, you know that this is extremely difficult even when you write all the code yourself Perhaps, but it’s quite nice when you use languages that were built to support Google Closure from the beginning, like Clojurescript. Then it is painless and built into the build process automatically, and you get to benefit from all the other great adv…
CLJS is awesome too! For what it's worth, Elm 0.19 likely also works with Closure Compiler in Advanced Mode - it did in a quick proof of concept I tried, but obviously that's something you want to be really confident in before suggesting people use it!
Note that Elm has always appeared to work on the surface with advanced optimizations, but the bugs would creep in and show up eventually, and the official advice has always been not to use those optimizations.
Re: Small Assets without the Headache in Elm 0.19
#30> If you have ever tried to use ADVANCED_OPTIMIZATIONS in Google Closure Compiler, you know that this is extremely difficult even when you write all the code yourself Perhaps, but it’s quite nice when you use languages that were built to support Google Closure from the beginning, like Clojurescript. Then it is painless and built into the build process automatically, and you get to benefit from all the other great adv…
Elm also outputs smaller assets than cljs+closure.
That being said, I do love cljs, having used it on numerous projects myself :)