I think my biggest concern for server-side components is the overhead at scale... or anything resembling scale. I know there are FaaS, Lambda, Vercel, Cloudflare, Deno, etc for functional and horizontally scaling hosting, but a lot of people are using a VPS or dedicated hosting for more predictable pricing. It would be nice to see some comparative overhead for say 10000 simultaneous users of an application in Brissa vs Next.js vs HTMX to see what the performance overhead, response times, etc look like in practice.
I think they all have good and bad, but I'm thinking there are other values in using Go or Rust with HTMX that outweigh the benefits of server driven component frameworks. Though the DX for the latter is at least interesting.
Personally, I don't like using the thenable syntax or response.json() directly with fetch api. I prefer to use async/await syntax against response.text() then JSON parse directly, keeping a handle to the original request... Then I can return the json body or text body with the error and the result code as part of the error raised. I'll usually put this directly in a function that will give me more information as part of the error chain.
Using thenables this way makes it a lot harder to do that.
It's worth noting that protocol buffers are *NOT* faster in JS than in other languages. You can often get faster results from compressed json than protobuf and other binary wire formats.
You might be able to use a binary extension/module for Node/Deno that can access the direct sockets to handle the encode/decode in a lower level language (such as rust).
It's definitely nice to cover this... that said, if you understand the loose comparisons it can be useful in practice. Especially when you're dealing with ETL workflows.
I definitely appreciate these efforts... I kind of wish there was a bit more collaboration between some of these groups. I mean rspack/rsbuild, biome, and even the typescript, deno, bun and other groups that are duplicating some of these efforts in several ways.
I'd also like to see a bit more integration of TS into these tools as a flag beyond transformations alone.
Maybe worth mentioning... Foo.prototype = Object.create(null); ...to break default inheritance from Object.