solid

@jroosdot @steipete @solid_js The original is on our Solid 2 branch: github.com/solidjs/solid/blob/next/packages/solid…

@g2sans @RyanCarniato @theo @t3dotchat github.com/solidjs/solid/tree/next/documentation I haven't studied their server components for a precise critique, but get the feeling it's overcomplicating stuff.

@RyanCarniato @theo @t3dotchat github.com/solidjs/solid/tree/next/examples/chat-… I still see though that you guys are trying, this is good! But this is what I mean when I say that you guys are constrained by the tooling that you use The `getThread` is a `liveQuery` that accepts a `live` that accetps a `GET` server function that emits JSX, that a `dynamicComponent` renders into a HOC that accepts callbacks. This is by no means simple. I have absolutely no idea what any of this is doing under the hood, it feels like I need a phd on front end. Too much abstraction for an idea that is fundamentally simple, building an html string to the browser.

@Meliketoast21 Mm.. somewhat.. I've made some good strides recently: solid#3774 But the biggest impact to size is probably not what you'd expect. Like I imagine I might have written a smaller version and it would have worked in my happy path. Not the core floor though.. the size is retained by the async anywhere model. And stores would have a lot more edge cases. We would probably not have done the Solid/Start collapse, the Rust compiler rewrite, the observability engine, server components. Probably would have done so on about 25% of the tests. The biggest difference AI brought and the biggest size part (which you can see in the size audit logs we keep) is simply bug fixes and correctness. So it's a bit hard to compare. In a sense, it would have been a fine release, but this release feels like we've completely closed the gap with React from a maturity standpoint. Tooling, infrastructure. It feels like in the past 6 months done about 3-4 years worth of work. So the size part is somewhat a sign of that maturing and somewhat addressable where it can be by comparison.