It may be that AI performs better on such code.

~$ bun upgrade [2.42s] Upgraded.

Welcome to Bun's latest canary build!

Report any bugs:

    https://github.com/oven-sh/bun/issues

    https://github.com/oven-sh/bun/compare/f161e0311...98f664962

Given the effort you've put into the comment I doubt you looked much at the code, but the github also looks well-crafted.

FWIW the README is actually way better curated than the average Claude-only README

So is the rise of microtransactions mostly history repeating itself? There are nuances but web microtransactions feel a lot more like putting a quarter in to an arcade machine than the iap for phone apps.

https://github.com/losfair/zeroserve/blob/main/CADDY_COMPAT....

VS Code doesn't have a similar scaling issue that I see

I went through the package.json on my machine - seems like ~400 / 60000 or 0.7% have (pre|post)install. (That's not all of the scripts that run at install)

Seems to me like a backwards compatibility is a non argument since pnpm is popular enough to stand as existence proof that scripts can be, at least, opt-in

IMO - pre- and post- install scripts should just be abolished/deprecated. It should require a special dispensation from npm to even publish one. A better system for binaries (needed by esbuild) is probably needed.

Even saying "just use pnpm" isn't enough, we need to get the developer community to herd immunity and that isn't going to happen on an opt-in basis.

I would love for npm to sandbox as well. But I think the better way forward is just turn off scripts.

I'd like to orange turn signals come back! They could even have an arrow inside them and toggle between inside and outside. Maybe thats too goofy, but at least something would always be illuminated. Here's a goofy SVG to show the concept

https://codepen.io/tln0/pen/WbodXKw

    bun upgrade --canary

I still hope there is a beta release.

The issues should absolutely be kept. The rewrite was file by file translation so logic bugs would remain. It's valuable to ensure the memory bugs are in fact fixed. Starting the issues from nothing does not make any sense to me.

element is not yet universal.

Wait what?

has been in HTML since.. the first draft in 1993!

I like DL's but they can be challenging to style. This article is using a lot of fixed pixel widths which would break on really small screens or larger data.

]]>Sat, 23 May 2026 14:50:06 +0000https://news.ycombinator.com/item?id=48248200tlnhttps://news.ycombinator.com/item?id=48248200https://news.ycombinator.com/item?id=48248200This is about the rust conversion but that has not been released.

> Due to foreseeable compatibility and security issues

Hmm, Zig bun crashes plenty.

I wish yt-dlp linked to detail on why there are foreseeable compatibility issues. Both projects have test suites, in an ideal world they would allow fast rewrites. Maybe they want to limit inflaming the situation, but if they have spotted some specific issues it would be good to see.

I hope Bun.rs is 1.4 or even 2.0 and not a minor release, with some alpha/beta releases.

]]>Fri, 22 May 2026 19:13:27 +0000https://news.ycombinator.com/item?id=48240159tlnhttps://news.ycombinator.com/item?id=48240159https://news.ycombinator.com/item?id=48240159pre- and post- install scripts should just be abolished. It should require a special dispensation from npm to even publish one.

Yes, I choose to use pnpm but opt-in safety isn't going to get the developer community to herd immunity.

]]>Tue, 19 May 2026 17:00:06 +0000https://news.ycombinator.com/item?id=48196002tlnhttps://news.ycombinator.com/item?id=48196002https://news.ycombinator.com/item?id=48196002Thanks for that!

So, back to the GP post - TC39 should make a bigger stdlib.

Lets say timeago.js is warranted (as a polyfill and terser API) AND TC39 is taking action.

On slice.js, TC39 took action AND usage is unwarranted since the functionality is widely available. Maybe a stride.js would be needed.

There are 2 modules where npm's culture of "tiny modules because the stdlib is impoverished" holds - but the issue isn't TC39 really. There are 312 modules that aren't related to npm's culture of "tiny modules because the stdlib is impoverished".

]]>Tue, 19 May 2026 16:51:09 +0000https://news.ycombinator.com/item?id=48195885tlnhttps://news.ycombinator.com/item?id=48195885https://news.ycombinator.com/item?id=48195885I'm not sure any of the packages here would be part of a "better standard library".

Do any language standard libraries have a "3 hours ago" formatter? Thats what timeago.js does

Maybe slice.js, which just does python-style indexing with negative numbers. TC39 already made array.at() and array.slice() handle negative numbers.

]]>Tue, 19 May 2026 15:30:12 +0000https://news.ycombinator.com/item?id=48194647tlnhttps://news.ycombinator.com/item?id=48194647https://news.ycombinator.com/item?id=48194647I thought the IFC International Fire Codes were a bit more ubiquitous than they are. Apparently whole roof is possible in a few EU countries. Probably not a good idea for the stick-built houses prevalent in US though

Thanks for sharing

]]>Mon, 18 May 2026 18:12:12 +0000https://news.ycombinator.com/item?id=48183300tlnhttps://news.ycombinator.com/item?id=48183300https://news.ycombinator.com/item?id=48183300Thats a really elegant solution.

How does the website trigger the CI script? Through GH rest API?

]]>Mon, 18 May 2026 15:49:11 +0000https://news.ycombinator.com/item?id=48181443tlnhttps://news.ycombinator.com/item?id=48181443https://news.ycombinator.com/item?id=48181443Don't you need fire setbacks? I didn't think full roof racks were possible

]]>Mon, 18 May 2026 01:48:07 +0000https://news.ycombinator.com/item?id=48174852tlnhttps://news.ycombinator.com/item?id=48174852https://news.ycombinator.com/item?id=48174852