Disclaimer: I'm the author of the linked PR. Using AI here is not really at fault here - it was just a giant rewrite that replaced how we do `node:http` in Deno. Replacing the engine while driving is never easy and we did the best we could. While we have a lot of test coverage and we use tests directly from Node.js codebase, we just don't catch everything. We're constantly working on improving the situation and I'm sorry you hit a problem. I can assure you that we are fixing all Node compat bugs as quickly as possible.
Maybe reality isn't represented by the git logs, but according to them, you appear to have composed, reviewed and merged 131 commits affecting 58 files and 6000 lines -- a task that you say amounts to "replacing the engine while driving" -- in the span of one week.
If that's accurate, of course your reliance on AI is at fault here. It invites you to mistake velocity for quality and conflate test satisfaction for completion.
Without AI, this effort would likely have taken much longer and an experienced team would have approached it with due meticulousness, being especially stringent in review. Absorbed in it, the work would have weighed on their unconscious while they slept, with "Ah shoot, did I consider XYZ?" moments striking them in the shower. Ideally, familiar with the specific contributors (i.e. you) and their style of work, the reviewer who later consider merging the work would have ideas what to watch out for and would spend extra time looking at the details you might not have fully considered. It's a whole decades-matured craft practice that can do a pretty good job of making sure that a refactor of this scale doesn't land in main too broken.
And while that version still probably wouldn't have been entirely flawless either, or might never have even been attempted because of its greater calendar and attention burden, that doesn't mean that using AI wasn't responsible for why and how this version is broken.
This is exactly how AI makes things worse and why many people are wary of relying on third-party projects that embrace it too blithely. If you're going to use it, that's great, and maybe it will help you keep landing big features more quickly than otherwise -- but at least accept responsibility for the tradeoffs that you're inviting when you do so.
Can we please not turn Deno into junk? If you do the above -- what's the point of Deno?
Once you bolt everything on like that you might as well just use Node.
Deno started off with its own tools. Bun has managed a good balance between compatibility and its own thing (the recent moves aside) without resorting to these tactics...
Are you sure you "failed"? Maybe there was good enough compatibility and that wasn't the problem?
The problem sounds like a business 1 where you're after more users and you deem this "magic compatibility" is fixing it. Well maybe that's not it.
A lot of people tried Deno and even tried to build libraries for it back some years ago. What you "failed" at is building the traction, ecosystem and community support.
Compatibility doesn't buy you moat. Deno specific ecosystem, libraries and services etc do.
To demonstrate how amazing bun is in comparison.
> "Deno has no future"
I think there may be other things bothering you? These comments aren't really productive and discourage maintainers to even continue replying.
Disclaimer: I am a maintainer.
bro what
I've been told I'm insane, retarded, a megalomaniac, or simply extinct. People I once respected are trying to convince the next generation not to learn, not to gain skill, not to build community. People with as much logic as a heap of bat feces tell me confidently that code is "over". Now if I was an AI I'd be very polite about this, but I'm a human so I say they can go fuck themselves.
I started a new project on Deno to avoid the NPM mess. Node compatibility was a distraction for the product.
I'm tired of everything depending on Node. Assuming that everybody uses it is lazy.
I've gone back and forth on this point over the years.
Yeah, Node compat has probably affected the rest of the product. I imagine at some point they (or their investors) freaked out because adoption wasn't happening. And the reality is it really doesn't matter if your product is better when nobody is using it.
In retrospect I think it would have been a better decision to target Node compat from the start like Bun did. An impossible option at the time given Deno started trying to make something different from Node.
Or maybe the problem was simply they couldn't afford low adoption after having investors on board.