tln

Yes, it provides the commits for a "changelog". Canary builds track main closely, 98f664962 is the tip of main.

~$ 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

Yes, but it's a nice website. And it looks like a really nice tool.

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

That a human wrote it?

I remember feeding arcade machines coin after coin, buying magazines and newspapers, and paying to see a movie. Those aren't all microtransactions but they are direct purchase -> consume content.

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.

No ACME! That is a dealbreaker

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

Github availability is driven by massive growth in the amount of work. I might add that is without a massive growth in the amount of accounts.. MS is struggling to make Github systems scale, clearly.

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

Maybe NPM is scared to break a ton of packages? I also think action from NPM on the repo level is vital

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.

Yeah but with a flashing light, if you look during an "off" phase, you don't see anything for a little while. Animated would/could show one segment on always

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

I found this:

    bun upgrade --canary

I still hope there is a beta release.

Its not 100% different code though. Docs, build instructions, C++, Typescript...

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.

What? Why? Git has branches...

Admittedly, however, support for the <dl> element is not yet universal.

Wait what? <DL> 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.

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

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

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

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

I 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

Thats a really elegant solution.

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

Don't you need fire setbacks? I didn't think full roof racks were possible

On (1), what if the law firm hosts the AI chat?

It seems like local AI could be valuable for law firms for reasons of (2) as well

Seems like Zig Bun had 3 pointer types that map neatly to existing Rust pointer types. The other 7-8 needed types to be created.

Is that the conspiracy?

bun_collections doesn't look much older than the porting guide.

Now that Bun can leverage Rust do you think some of this code will get disaggregated? Eg, Bun could use swc crates

And now like a winey baby they LLM rewrite to Rust.

I didn't see any whining from Jarred, this seems like misplaced sentiment

It’s purely politics-based

The linked twitter thread gives clear technical justifications

Taalas. A sibling comment of yours posted the chat demo URL -

https://chatjimmy.ai/

Yes that is in the law.

Fleet reductions, new limitations on operating areas/conditions, fines, permit suspension or revocation

I should have been clearer, the hidden addition is never ok.

If I ask Claude to write a commit message, it will inserted a co-author line (and an ad), but I can see it and disapprove, add a counter instruction to CLAUDE.md etc

The sneaky commit modification is triggered by very modest usage of AI such as auto-completion.

Look, if an agent writes the code and the commit message then adding a Co-authored-by by default is ok. Not even showing it before the commit is made is not, and adding the message when AI was just completing code is not.

Absolutely, messing with commits is more invasive than messages. It gets worse:

"Sent from my iPhone" appears in the authoring view, and you can delete it.

Co-authored-by: NEVER appears in the commit message UI - it is added without the user even seeing it.

Does anyone understand this well enough to do that with confidence?

Pretty sure Chrome wouldn't ship if they weren't confident. And Firefox would object based on security grounds if they saw such an issue

The dragon image has issues like one eye, weird tail etc, but the pelican is imo perfect -- the best I've seen!