Amazing interview! It's so good to see you bringing such an important figure to the conversation, really a privilege to see both masterminds talking. Thanks Jack for your hard work! hope you had some fun in Amsterdan
I've been used solid + vite for my last project, pretty solid and good experience but I didn't need any fancy library for it so I can't really tell how the lack of ecosystem compared to the big 2 would've affected me
The dream would be bringing Solid's features into React (performance, signals, etc.) There isn't such a huge difference between the two to warrant moving to a totally new framework and losing the ecosystem that was built over the years.
Right!?! Unfortunately I think the resumeability feature in Qwik is baked too far in to allow integration. And it’s so fundamental that it basically replaces everything that solid would bring in.
I mean, Qwik already has signals and also uses JSX. I'm not sure how much most people would want to mix in Svelte because it's typically the syntax differences that cause people to choose one over the other. They all have a few things in common with one or the other. I think it's a great time to be a dev when we are so spoilt for choice. Choose one of these three for any new project and you can't go wrong!
@@IainSimmons Nah. I wouldn't pick any of them. They're all going to fail in the long run. Their ecosystems suck, because their communities can't get along with each other enough to focus on UI libraries and services... So it's a waste of time. Vue too is a failure, React hooks almost killed it, now it's crawling in pain. I would use Svelte with Partytown if it had a proper ecosystem like HeadlessUI support, but it doesn't. So Nextjs + Million (performance) + Partytown (resumability) for the win. (and I choose this while still thinking JSX is a liability)
I worked with Ryan back in 2013! He's an awesome developer!
I switched to solidjs 9 months ago. No regrets. Better performance, familiar syntax.
I've been using SolidJS with NativeScript and Tauri and the experience has been extremely pleasant.
Have been wanting to check out solid+nativescript but never gotten to it. Curious to what u have been building with it.
Yesss! Excited to hear they're working on bridges to bring Solid to the masses.
Amazing interview! It's so good to see you bringing such an important figure to the conversation, really a privilege to see both masterminds talking.
Thanks Jack for your hard work! hope you had some fun in Amsterdan
Wish this interview would have been 2 hours long!
I've been used solid + vite for my last project, pretty solid and good experience but I didn't need any fancy library for it so I can't really tell how the lack of ecosystem compared to the big 2 would've affected me
That was cool. Keep them coming!
Oh a new format :d
The dream would be bringing Solid's features into React (performance, signals, etc.)
There isn't such a huge difference between the two to warrant moving to a totally new framework and losing the ecosystem that was built over the years.
Ryan is a king
🎉
Solid components in react. Which can take react children 😮. We definitely need that
Awesome Video..
Sweet!!
solid native ??? would be damn nice
vercel: dont worry my friend. I will get the compiler ready.😅
Two programmers are talking..
Can Solid Svelte and Qwik merge their powers to make a Union Framework that has all the good things each one possess please?
Right!?! Unfortunately I think the resumeability feature in Qwik is baked too far in to allow integration. And it’s so fundamental that it basically replaces everything that solid would bring in.
I mean, Qwik already has signals and also uses JSX. I'm not sure how much most people would want to mix in Svelte because it's typically the syntax differences that cause people to choose one over the other.
They all have a few things in common with one or the other. I think it's a great time to be a dev when we are so spoilt for choice.
Choose one of these three for any new project and you can't go wrong!
@@IainSimmons Nah. I wouldn't pick any of them. They're all going to fail in the long run. Their ecosystems suck, because their communities can't get along with each other enough to focus on UI libraries and services... So it's a waste of time. Vue too is a failure, React hooks almost killed it, now it's crawling in pain.
I would use Svelte with Partytown if it had a proper ecosystem like HeadlessUI support, but it doesn't.
So Nextjs + Million (performance) + Partytown (resumability) for the win. (and I choose this while still thinking JSX is a liability)
@@greendsnow partytown doesn't have anything to do with resumability
@@bigmistqke oh yeah, lazy loading. my mistake.
Astro Solid Qwik Svelte
Next has nothing to do into this list
This is a new era