Basically agreeing. On Fri, Nov 20, 2015 at 12:08 PM, Wilson Page <[email protected]> wrote: > > - Optimize UI performance once and benefit everywhere >
Having dedicated raptor tests sounds a must have to make sure performance is monitored and we do not slowly regress over time. Arguable we could use a JS framework (eg. React) instead of the built-in > browser APIs, but: > > - Frameworks come and go. What's next year's trendy framework? Should we > wait for that? > "Should we wait for that? " is definitively a valid concern. For years I was hoping ES6 modules will arrived - that was likely a mistake. My understanding of the current state of the situation is that they will arrive probably in 2016 but without the associated module loader... I'm fine to use require.js all over the place and move it to shared/ instead of waiting again and again. And then switch to ES6 modules once they will be here. > - Browser APIs will tend to be/become faster than a JS framework > equivalent. > TBH I feel like there is still a lot of work to make Web Components really fast, but I agree on the theory for the long term. > - We're Mozilla, we should be supporting the platform we're building :) > \o/
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
