I agree that it seems like overly big. I'm glad that Rupert was able to minimize and zip it to a reasonable size.
I tried loading the webcomponent polyfill conditionally, per the comment in index.html. That works fine in Chrome and Firefox with the bare code but I could not get it to work with the "vulcanized" version. I just couldn't get the load order right such that the webcomponent API would be ready before it is called. I'm old-school and prefer working with 'make' but my resistance to the gulp/grunt/webpack tools may be futile. On Wednesday, September 28, 2016 at 5:35:56 AM UTC-5, Rupert Smith wrote: > > On Wednesday, September 28, 2016 at 7:59:55 AM UTC+1, Peter Damoc wrote: >> >> I've tried your solution and at least I got to confirm a personal fear: >> it's scary big. >> 1.7MB might not seam much but... I'll be honest, I don't like artifacts >> this big . >> The inspector says that it will take 17 seconds over a regular 3G >> connection to load this. >> > > When I ran 'make dist' I got an index.html about 1MB. Some of its contents > did not look minified, so I ran minify on it and it went down to about > 600K, when gzipped it was about 100K. > > I think with some attention to detail the polymer library can be split up > a bit, and various polyfills not loaded on chrome as it does not need them: > > https://aerotwist.com/blog/polymer-for-the-performance-obsessed/ > -- 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.
