The latest articles on DEV Community by Sandeep (@sendy). https://dev.to/sendy https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F487495%2Fa5033c13-2018-4334-a0d2-81881e7a6981.png https://dev.to/sendy en Sandeep Sun, 11 Oct 2020 16:34:12 +0000 https://dev.to/sendy/should-react-opt-for-compile-time-instead-of-virtual-dom-60d https://dev.to/sendy/should-react-opt-for-compile-time-instead-of-virtual-dom-60d <p>I am front-end developer who loves working with React. I am really impressed with Svelte's approach for reactivity and I just wanted community's input on my thoughts.</p> <p>React drastically changed the way we develop frontend apps, but Svelte definitely redefined reactivity with it's approach to compile time optimizations vs Virtual DOM.</p> <h1> Why </h1> <p>Everyone talks about switching from one framework to another but if React could ditch Virtual DOM, and start adopting compile time optimizations, that would be best of both worlds.</p> <p>React is already very much mature, has lots of tooling available and lots of community support. Developers will be able to continue using the existing tools with much more improved React.</p> <h1> How </h1> <p>I am just putting my thoughts here. There are lots frameworks which are using React internally like Next JS, Gatsby etc. All the frameworks and tools will definitely be affected as well if React changes it's underlaying architecture.</p> <p>But may be React can do an opt-in phase like how it did during React 16. This will allow a slow transition into a new React.</p> <h1> What are your thoughts? </h1> <p>Let me know what you guys think about this. Is it possible? or is it unnecessary?</p> react svelte javascript discuss