Yes. I believe it is. We need some performance testing to prove it, but I believe Royale has little or no overhead that many other frameworks have.
> On Oct 26, 2017, at 10:43 PM, Dave Fisher <[email protected]> wrote: > > Correct me if I am wrong, but isn’t part of the value proposition of Royale > that it will do the unrolling in the compiler? > > Regards, > Dave > >> On Oct 26, 2017, at 12:39 PM, Jeff Dafoe <[email protected]> wrote: >> >> >> It's not too much of a statement about React's efficiency, as you'll almost >> always see gains if you unroll framework code in that manner. The >> disadvantage is you now have a landing page constructed from unrolled pieces >> of framework. Almost categorically, this is how good software development >> is done overall - unroll parts that need the highest performance, where >> you're willing to trade off maintainability for performance. >> >> -Jeff >> ________________________________ >> From: [email protected] <[email protected]> on behalf of Carlos >> Rovira <[email protected]> >> Sent: Thursday, October 26, 2017 2:41 PM >> To: [email protected] >> Subject: Netflix removed React for plain JS to gain 50% performance >> improvement >> >> I saw this on twitter, and think I could share here: >> >> https://twitter.com/NetflixUIE/status/923374215041912833?s=09 >> >> "Netflix UI Engineers >> Removing client-side React.js (but keeping it on the server) >> resulted in a 50% performance improvement on our landing page" >> >> IMOH, that's an huge stick for React, since performance always is one of >> the main points >> >> I think here Royale has a good opportunity if we can have javascript as >> plain as we can and shows >> a good performance in browsers. >> >> What do you think? >> >> -- >> Carlos Rovira >> http://about.me/carlosrovira >
