On Wednesday, September 28, 2016 at 11:55:06 AM UTC+1, Peter Damoc wrote: > > I looked at the entire dist folder as that was the actual result in my > perspective. 1MB index.html with about 700k extra JS (elm.js included) > Yes, it was not minified. > > The performance details are part of what I mean by integration. > > Should I, the beginner, solve this or should I have some kind of help in > this from Elm tools? > In other words, should I spend time figuring out how to connect tools > (maybe get paralyzed by not being able to figure out if I should use grunt, > gulp or webpack) OR should I invest that time in learning to use Elm? > > This is how constrains liberate. > One integration solution (even if sub-optimal for some of the veteran web > devs) frees the beginners from all the complexity of making that work from > scratch. >
You can work solely within Elm, in which case an Elm specific tool could help you. But I think there is a very high chance that an Elm project will need stuff outside of Elm, in which case you need to learn to use the tools that are being used generally for web dev to do this. To give an example - I have a step in my build to do some optimization on all the images that I use. I will almost certainly use some images in any site I create and optimizing them seems likely to always remain outside the scope of Elm. It is also true that there is no correct solution - you might concatenate all your .js and .css into single files for example, or you might keep them split into several files with parts to be loaded on demand so that your pages render sooner/progressively. My advice to a beginner would be - pick a build tool our of grunt, gulp, ... whatever you feel most drawn to. Knock together a simple build with it, it does not need to be perfect. Copy someone elses build file to get started, and delete the bits you don't need or understand. Just get your site building so that it works. As you learn more about the tool, start figuring out how to optimize your build for size/load time/render start time as you see fit. If you hate it, try one of the other tools and see if you like that better. I think a tool chain specifically for Elm that covers areas already covered by other tools would be a waste of time for the Elm community to invest in creating. For the beginner elm-make and elm-reactor are good enough to get started. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
