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.
That would definitely be a nice tool... I feel that this will only get more difficult in time though. Right now it's easy enough to prompt a few popular LLMs to see if you get similar text, but man, what will the cost be in the end.
Both in generated content as well as bot detection and anti-bot tooling. I'd hate to be github.
I can only say I fully expect that we may wee a return to more niche communities that are self-regulated, similar to BBSes of old. In only that the popular platforms for social media are already inundated with bot activity.
I don't personally have any tools to check for this... I don't care for the relatively Jr level content myself, and often call out errors or at least oddness in the articles that I do read with a comment. I don't always read every article though, just a quick pass to clear obvious spam.
I could favor nuking the very jr and simple content... just wouldn't want to actually discourage anyone genuinely writing learner/beginner content.
What's funny to me is the name shift from deh-noh to dee-noh, which was relatively quick, but still hard for me as the first announcement pronunciation was burned into my brain.
Aside: I do think the video itself seems a bit short on content and would have liked to see how the engine is being used by a few different cloud providers. And how frameworks like hono are leveraging the different options in a similar way.