Let's be careful about what it might mean to "unroll". We have certainly tried to focus the framework code on Pay-As-You-Go (PAYG). IMO, that's not unrolling, it allows incremental feature addition.
We are working on composited component sets like Express which can be manually disassembled into smaller pieces, but the compiler doesn't do that. The GCC compiler is capable of dead code removal, but we haven't experimented much with it. I think there is potential there to have the compiler further reduce code size. No matter what, though, the fact that we code in small pieces we call Beads and composite them on Strands give us the opportunity for the tool chain to automatically detect and remove other kinds of unused code in the future. Thanks, -Alex On 10/26/17, 1:03 PM, "Harbs" <[email protected]> wrote: >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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter >>>.com%2FNetflixUIE%2Fstatus%2F923374215041912833%3Fs%3D09&data=02%7C01%7C >>>%7C7289cad6488d41eef80e08d51caca8b1%7Cfa7b1b5a7b34438794aed2c178decee1%7 >>>C0%7C0%7C636446450242521705&sdata=Tje6QQVnleq5SWlh%2FC%2BhBkufZmec7n14od >>>RTdbtfUlY%3D&reserved=0 >>> >>> "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 >>> >>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me >>>%2Fcarlosrovira&data=02%7C01%7C%7C7289cad6488d41eef80e08d51caca8b1%7Cfa7 >>>b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446450242521705&sdata=uk9gqu9 >>>LV9Z7gPiprqvHzcHFFwiZMfmNIwWZMFfvVwA%3D&reserved=0 >> >
