3 ms·
I was a little bit disappointed to see that the plan for Polymer 3.0 is to leverage ES modules to handle all the asset loading. Maybe their hand has been forced
by cageface 9y ago
I was a little bit disappointed to see that the plan for Polymer 3.0 is to leverage ES modules to handle all the asset loading. Maybe their hand has been forced here since browser vendors refused to implement http imports but if Polymer requires a fair bit of Javascript to do anything interesting then its advantage over something like React becomes a bit less clear-cut, IMO.
- hplustime 9y agoYeah, its definitely been forced, you can see it in the team's faces (https://www.youtube.com/watch?v=0N-ldg1IPn4&t=1766s https://www.youtube.com/watch?v=0N-ldg1IPn4&t=1766s). Its possible that the HTML Modules spec will hit browsers in the next year or so (the fact that the ES Modules spec does nothing when the resource mimetype isn't JS means it'll be very easy to extend), in which case Polymer 3.0 will have just been a crash course in tagged template literals.