I feel like we can use Svelte signals/stores exclusively in any other non-signal frameworks (aka React) and set svelte as a dev dependency(like you always do anyway)! This is a huge step in code re-usability!
Like many I was kinda afraid when the OG announcement came out, and now that I'm working on some projects in Svelte 5 I'm like "Oh, I GET IT." Bravo. This is the best summary yet!
Nops, you’re mistaken. This idea was originally implemented by Knockout back in 2010. Recently, it was reintroduced by the Solid team, aka implementing reactivity using signals. There’s nothing particularly innovative about Vue; it’s just an alternative markup language to React. + Vue 3 is based on a virtual DOM, so it can never match the performance delivered by Svelte.
@@fred.flintstone4099 `So Vue 3’ basically stole Svelte’s ideas? 🤣` ... in seriousness thats awesome ... there had been too much divergance in js eco system ... its good for the industry that converges on standard patterns ... collectively improve the limitations
@@SheeceGardazi Rich Harris created Ractive.js which inspired Evan to create Vue, which inspired Rich to create Svelte so Vue and Svelte are kind of similar and have inspired each other and other frameworks SPA frameworks like like React is quite similar too. React is very similar to Solid.js, so all these frameworks are kind of similar.
@@fred.flintstone4099 I am unsure about the history ... but I agree with the ethos of statement ... ... inverted comma were to highlight this fact too Michael in his own words ... thats just opensource in a nutshell ... you feel limited by something you build some alternative ... initially there is divergence when ppl are exploring the best way and eventually they all converge ... extreme example will be hardware drive protocols that run on any os now ...
web components are a pain to write and maintain. I think it’s good to understand how to do them and their use cases but there’s no way I’m writing a whole app with vanilla js and web components
@@brandonpaul6139 use something like solid probability. At lease something that doesn’t need a compile step to work. This is the strength and flaw. It all needs so much dependencies and steps to work
I love the simplicity!!!! 🎉🎊
That was straight to the point !
And yes, it does feel like vite ecosystem is very dynamic. Keep on the great work !
I feel like we can use Svelte signals/stores exclusively in any other non-signal frameworks (aka React) and set svelte as a dev dependency(like you always do anyway)! This is a huge step in code re-usability!
Why use React at all?
@@SheeceGardazi Not me but the rest of the web world I can see using component.svelte.tsx now!
Omg, so excited for native alt runtime support 🎉
Like many I was kinda afraid when the OG announcement came out, and now that I'm working on some projects in Svelte 5 I'm like "Oh, I GET IT."
Bravo. This is the best summary yet!
This is all great! One question, from a developer perspective what is the advantage of runtime-driven reactivity?
oh shıt here we go again
First, we in the team updated from svelte kit beta, then from svelte 3 to svelte 4. Now we will be from svelte 4 to 5
What is sveltekit beta? how is that related with Svelte?
I'm sticking to ELM just works
So, Svelte becomes Vue…
it is similar to razor by lighter
here we go again! at this point i convinced my senior is right, just use javascript than using any of these shiny frontends
So Svelte basically stole Vue 3’s ideas? 🤣
Nops, you’re mistaken. This idea was originally implemented by Knockout back in 2010. Recently, it was reintroduced by the Solid team, aka implementing reactivity using signals. There’s nothing particularly innovative about Vue; it’s just an alternative markup language to React. + Vue 3 is based on a virtual DOM, so it can never match the performance delivered by Svelte.
@@SheeceGardazi Vue has a a experimental new renderer called Vapor that doesn't use the virtual DOM.
@@fred.flintstone4099 `So Vue 3’ basically stole Svelte’s ideas? 🤣` ... in seriousness thats awesome ... there had been too much divergance in js eco system ... its good for the industry that converges on standard patterns ... collectively improve the limitations
@@SheeceGardazi Rich Harris created Ractive.js which inspired Evan to create Vue, which inspired Rich to create Svelte so Vue and Svelte are kind of similar and have inspired each other and other frameworks SPA frameworks like like React is quite similar too. React is very similar to Solid.js, so all these frameworks are kind of similar.
@@fred.flintstone4099 I am unsure about the history ... but I agree with the ethos of statement ... ... inverted comma were to highlight this fact too Michael in his own words ... thats just opensource in a nutshell ... you feel limited by something you build some alternative ... initially there is divergence when ppl are exploring the best way and eventually they all converge ... extreme example will be hardware drive protocols that run on any os now ...
Rune ruined svelte
I'm a person of good taste: thumbs down for this inappropriate empty sale-y talk.
Just go webcomponents
But how about if I want to enjoy my life?
web components are a pain to write and maintain. I think it’s good to understand how to do them and their use cases but there’s no way I’m writing a whole app with vanilla js and web components
@@brandonpaul6139 use something like solid probability. At lease something that doesn’t need a compile step to work. This is the strength and flaw. It all needs so much dependencies and steps to work
@@krannark that’s fair
Have you actually worked with webcomponents? The idea is wonderful but the implementation in practice has so many unfortunate limitations.