> Rewrite the entire node:http stack to use llhttp (Node.js's HTTP parser)

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...

▲

bartlomieju 2 hours ago | parent | next [-]

We tried to build `node:http` on top of Rust libraries (like Hyper) but we failed for a couple years. So earlier this year we decided to make it compatible (by using llhttp to have very high coverage - at the moment 88% compatibility for node:http module) and then focus on improving performance and slowly chipping away llhttp parts while keeping compatibility.

	▲	SOLAR_FIELDS 2 hours ago \| parent \| next [-]
		It's so easy for others to casually dismiss how difficult of a problem it is to get this right, especially, as you say, this is happening in flight for many thousands of users. Kudos to you for being transparent and building a genuinely cool and useful platform.
	▲	re-thc 2 hours ago \| parent \| prev [-]
		> We tried to build `node:http` on top of Rust libraries (like Hyper) but we failed for a couple years. 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.

▲

someguyiguess 2 hours ago | parent | prev [-]

> what's the point of Deno?

To demonstrate how amazing bun is in comparison.