In a similar vein, logic would be questioned if a browser vendor blockef shipping ES2015 modules, because the equally-functional alternative of bundling dependencies on the server exists November 25th, 2015 at 05:50įor those who want to try web components today without the bloat of huge frameworks there is. Surely its understood to use modules for code, and imports for HTML? js file with the element’s shadow DOM HTML in a multiline string, but that’s clearly going against the grain. You can have a look at them here: November 30th, 2015 at 02:00ĮS2015 modules and HTML imports serve very different purposes and work completely differently. They have also raised interesting points that have been taken into account for changing parts of the spec, based on actual usage and real-life experience. In parallel to this, the people working on Firefox OS have been exploring using web components without HTML imports, and pretty much all of the UI is now built using components. Working together-developers and browsers! Using polyfills is not “a solid framework” or “proof of concept”, but a “temporary solution based on the draft of a standard” that should help developers inform browser makers on what’s good or not for the web platform. This is *very dangerous*, specially if you’re loading *code*. But that means that you’re not testing out how the real imports would work, and therefore browser makers cannot make decisions based on what a polyfill does, because when the real implementation happens, it might behave differently to what the polyfill did due to platform limitations.
#Darksiders 2 deathinitive iso download code
Although there are many ES6 features implemented in browsers already, modules are not implemented yet, and developers can only use imports by “transpiling” their ES6 code to “normal JavaScript” using some tool such as Babel. To add some perspective, ES6 just become an standard in *June 2015* – that’s less than five months ago. I don’t think you should “wait to see what developers do”.ĭevelopers will use what Fb, Google, Mozilla, etc… propose to them, they won’t invent their own framework & patterns just to make their own app, they’ll use those available to them.įacebook makes react, Google has polymer,… it’d be nice for Mozilla make their own (and this time not abandon it like brick) that would not only allow to make web sites, firefox OS app, etc… but would also prove that Mozila’s choices of web standards are coherent ( for eg here it would show that HTML Imports are not necessary and that we can have a cleaner solution with ES6 modules).īut otherwise it’s kind of easy to say “we like that” or “we’re against it” without having any solid framework/proof-of-concept to prove your point. Now ES6 modules are here, so what are we still waiting for ? You said the same thing one year ago ( ). “We want to wait to see what developers do with ES6 modules” Sign up for the Mozilla Developer Newsletter:
We’re addressing this issue by creating the Web Components Status in Firefox page in MDN. We are very aware that keeping track of these changes is time consuming for developers who want to make sure their web components code works in more than just one browser. There was an early unfinished implementation which will be removed. HTML Imports are not shipping, as we want to wait to see what developers do with ES6 modules.There won’t be active work on Custom Elements on Firefox until consensus is reached. There was an initial implementation of Custom Elements, based on prototypes, which is also the version Blink shipped, but Apple’s Ryosuke Niwa is fleshing out some experiments to come up with new approaches that use the ES6 class syntax instead.You can read Anne’s and Wilson’s posts for more details.
0 kommentar(er)
