SolidJS 30k Stars nitter.siddz.com/i/broadcasts/1nAJEawmR…

I love seeing other people who care about performance gather around @solid_js. Amazing work @chiefcll on taking SolidTV to 2.0: solidtv.dev/blog/renderer-2-…

Are Metaframeworks Dead? Catch my talk live at 11:58am PT (in 25 mins): viteconf.org/live

A React Metaframework with an architecture I can get behind. And it supports @solid_js. 🔥

I've been pretty much on this side of the argument. When I've seen the work that goes into designing a framework even one that I generally have little love for like Next.js, but still appalled by things like vinext. Atleast there I get the platform tension. But a library or tool without its vision is doomed to fall apart. Its the same problem as compat. Either you reconcile yourself to always follow the others vision or you admit it is stopgap migration strategy. It's not a long term plan. But, step back and think about this as an entrepreneur. Ie.. build it and they will come. You are supposed to throw as many ideas against the wall and see if they stick. I see the danger here in leaving rotting carcasses of projects in its wake. But at the time of building there is every intention of supporting them if they are successful. If they are successful, is the distinction. What's crazy to think is how low the upfront cost is to do this. Our measure of how to trust a project completely changes. However, our cost of migrating solutions is also cheaper than ever so is it actually that expensive? If Vinext proves a dud you can always go to Next.js or maybe something else. I guess what I'm saying is capitalism has been a part of OSS for a long time. We like to think of it often as this communal thing, but we've had Microsoft and other large players dictating the shape of this for years. AI is actually democratizing this in a sense. In a sense it sucks for the smaller players, I think it risks snuffing out real innovation. But on the average we just put bigger capability in everyone's hands. A single maintainer can move mountains with the right product. Honestly it is terrifying as a smaller player myself, but I don't think this just amplifies what was already happening. OSS has been struggling for years. Maybe this puts the nail in the coffin. Or maybe this points to the way forward. Or most likely this is just the new balance between both.

It's known that @solid_js already has a very performant, very strict runtime. @devagrawal09 asks what if you could do more ahead of time, because lets face it you aren't writing the code anyway? Ugly as sin, but super powered for agents?

I didn't get in on the conversation as to not invite more work for myself, but AI has been great for PRs and issues. Yes some things are clearly exhaustive for no real reason, but we have people contributing now that never would have before. People who take place in the conversation and understand the problems but didn't trust themselves to write the code. Solid's core was notoriously hard to contribute to because I needed to size and perf vet everything all the time. And I didn't have time for that. Now I do thanks to agents. So between my AI fueled maintenance and contributors use of AI our throughput has never been higher. 7.7x year over year on PRs. And also on issues. People are more comfortable producing issues becaues they feel more confident what they found is a bug. Issue reports are up 20x. Now to be fair some of this could be based on our Beta timing and usage dramatic usage increase the last 12 months. But my general impression is AI has undeniably has been a enormous net positive here.

Yeah, the folks over on @QwikDev are still cooking.

Exploring the Grand Unifying Architecture of Frontend nitter.siddz.com/i/broadcasts/1qKVmyLLN…

I keep coming back to this. AI isn't shattering egos. It's inflating them. It's harder than ever to keep it in check. You think of the problem that's beaten you for years. You solve it. Then you do it again tomorrow.

Yes! Great post. I'd typically say more but he already said it.