Join a discussion about the future of Web frameworks moderated by This Dot Labs' Jesse Tomchak.
Featuring Daniel Roe (Nuxt), Fred K. Schott (Astro), Ben McCann (SvelteKit), Ryan Carniato (SolidStart), Bret Little (Hydrogen), and Miško Hevery (Qwik City)
https://imgur.com/VbwxeUl
#Frameworks Panel
112 messages · Page 1 of 1 (latest)
les gooooo
Hydrogen - React <> VueStorefront - Vue ??
Shoutout to Jesse from This Dot!
❤️ this dot
Oh no
?
How much you guys are afraid of AI taking over before you will release next version of the framework? 🙂
Just the "Which framework is best" question, I got triggered
Ah, fair
literally no one would have said anything to that question
Snowpack!!!!
Snowpack+Pika 🙂
https://www.snowpack.dev/ build tool for ESM before Vite existed, around the time of Rollup's creation (citation needed, plz)
Q: "what is the piece of innovation that you are the most proud of?"
either in your specific framework or the community in general
We worked on making vite-note to benefits all web framework to bring on-demand build for SSR, read more on Anthony Fu article about it: https://antfu.me/posts/dev-ssr-on-nuxt
hearing about so many new tech. snowpack, tauri, analogjs, etc.
snowpack v1 was jan 2020
same
I love how much nuxt created - it's so crazy getting a glimpse behind the scenes of what @glossy cloud and the rest of the team are delivering!
holy shit a 45 minute panel.... and i have a 30 minute meeting in between
Oh hey!
Q: do you guys miss that Remix and Next.js is not on this panel? 🙂
i am going to miss so much
The work that Pooyah, Daniel, and Anthony are doing... their unjs org is agnostic and AWESOME. https://github.com/unjs
framework !== metaframework
i think that is the logic behind this panel
What about Hydrogen and Nuxt?
hmm i guess it might be svelte+sveltekit, react+hydrogen, vue+nuxt
since there is an overlap between the core teams
💜 @wild vapor getting some love on the panel!
I think it's more that Remix and Next don't use Vite
strong +1
Remix is esbuild, Next is (I think?) webpack
ah this makes more sense
yes
(yes, it's webpack)
he's the man
and on that topic, getting the resolved next.js config to spawn a webpack server w the user bundler config... so painful (as a devtool, like Cy CT)
💯 supporting what @glossy cloud just said - it's incredible how vite works for SO many different frameworks!
Right, that’s why I’m asking do you guys wish they were using it
Yes.
I prefer to use tools built on Vite, yes.
I like utility CSS frameworks that are vite-first and icon libraries that are vite-first
just listening to Misko brings back so many memories about AngularJS and my time using it lol... it's been a while since I saw him
I don't think it's wrong to use something else, but I'm gonna stick to this ecosystem
so the question is that "do you prefer if pretty much every framework used vite and ditched webpack/etc"
I would rather have more agnostic tools that don't care about node/browser environment than care about unifying on a dev-server.
I really liked the question in the #2022-viteconf chat:
Q: Do you think it hurts the community as a whole to have too little competition, when everyone is joining Vite?
my answer would be "no", as much as i like vite, no one should have a monopoly over a some area, there should always be space for healthy competition, or there will be no innovation. but really curious to hear the panel's thoughts
This is not even close to that yet 🙂
I know we're not even close - just an interesting question I thought!
I think a good example of why competition is good is Jest's proprietary module transform system. Unification throughout a toolchain such that your entire pipeline is using the same "compiler options" is very important to me.
And I would argue: There will always be competition. There will be multiple people creating new frameworks and tools that solve different problems or even the same problems differently!
i need to hop into a meeting, would love if this question is asked
I like utility CSS framework that are unplugin first 🙂
Oh. Yeah. This little buddy is what I use. Any innovations w/ uno yet?
https://github.com/unjs/unplugin is the fondation if you are interested
i've dug into unjs, but not the unplugin core.
And come try nitro! https://github.com/unjs/nitropack => https://nitro.unjs.io/
are you chatting while on the call Daniel? 😮
LLVM is an interesting comparison
Two years of WFH will do that to you
hahahaha
https://github.com/unjs is made for any frameworks to collaborate and use universal JS librairies to work across any environments (Node, Browser, Workers)
thanks!
💚💚💚💚💚💚
what was the project @FredKSchott shouted out there?
library name? hahaha sorry, I'm slow
How many @digital temple are around?
including the bots?
Fuzzy is a bot
@hybrid quail hey, get here! Fred is throwing flowers at you ❤️
HatTip powers Rakkas too, btw.
@hybrid quail I'd love to see how our adapters in Astro could leverage this internally, feels like the missing layer for all of these adapters to fit on top of
That was our idea. SvelteKit, SolidState, Rakkas, Astro, etc. each has to maintain their own adapters which is a huge amount of duplicated effort.
Can’t believe no one said what framework is best yet 🙂
it really is, and there is greater implications that is felt downstream with the users, interoperability, poorly understood and hence poorly built adapters that can then cause spiraling cloud costs
I thought it was determined in #2022-viteconf to be Wordpress with jQuery?
goes back to topic 🙈
WordPress on vite when?
already exists apparently: https://github.com/blonestar/wp-theme-vite-tailwind
goes back to topic 🙈
😄 hey, it's hard, ok?
"I'm not a shill, I promise" lol
"Resumability"!!! I hit the viteconf bingo
there you go - Misko says Qwik is the best fw
thanks everyone!!
This panel needs like 5 hours to get started 🙂
45 minutes is too little 🙂
😍
Great panel!!!
just saw that this conf is going all day and night - into 1:21 AM woah!!!!
Just caught up with the frameworks panel, thanks for the shoutout @compact folio 😄 I should really set a deadline for the prebundling work. Need the pressure
the deadline is Vite 4 / SvelteKit 1.0, so we don't have long 😆