But what exactly are you projecting? Typically when people have said they have a bad feeling about something (imagine Next.js) it's because they are running into more bugs or they are seeing more production incidents. In this case there has been no chance to observe these things.
replyBun in its current state absolutely has issues like segfaults. As nice as it is, I moved off of it back to node for production.
replyFolks generally tolerate issues if they believe they’ll get better with time. I know I did for a while. If that confidence collapses, that’s not politics.
It's 1mloc that no human has seen. There is no possibility for that project to be reliable, at least initially.
reply“You're absolutely right! I've seen things you humans wouldn't believe.”—Claude Opus 4.7
replyEngineering decisions and the resulting output.
replyWe've known for decades that machine-translated code is garbage, and should only be done as a last resort.
Your HN account is too new for me to be sure whether you're being sarcastic or not. Perhaps you know, or perhaps you don't, that all code is machine-translated, even assembly language. None of it is perfect, but it's not garbage. Today's AI merely provides a new level. It's a weird, non-deterministic level, but hiring an employee to write code for you is similarly non-deterministic.
replyRight, and that's why Mel was a true programmer!
replySeriously though, that's an overly-pedantic definition of a compiler. Broadly speaking, languages compile in a direction of decreasing abstraction. Crossing from one high-level abstraction to another is just asking for trouble, especially in this case where the target language makes very specific performance promises as long as certain abstractions are maintained.