tln

> But using an AI to reply to a human is just disrespectful. It says the organisation values their customer's time at less than their own.

One of the benefits of using AI to reply is faster replies... which values a customers time.

I think that good customer service can use AI. It's not AI composed replies that makes the customer service bad.

Is this format for data or for config?

The reason for not having is simply a matter of specification size. ISO-8601 is full of weirdness! SOML's date spec is reasonable looking but there is still a lot of nuance.

Having durations is nice and instants are highly complementary. My feedback is just that if lots of literal formats are desired, maybe an extensible literal format!

Feedback:

1. You should mention TOML in your first paragraph. "Why not TOML" exists at the end

2. how often are "instants"/dates really specified? Are you baking this in for TOML parity?

If you want leaner, drop this. If nothing else it's a lot of grammar.

If you want to lean in to "A value's type comes from its syntax", I'd suggest taking a cue from postgres and JS -- extensible literals. With JS tagged literals it would look like date`2026-09-19T14:00:00Z`. Conforming readers can fall back.

I'd use ver`3.1.0` 1000x more in config files than dates... I do like durations being baked in though.

Solid improvements over TOML and YAML.

Speaking as someone who uses Adobe apps on a regular basis, I care more about file format compatibility and correctness than feature compatibility. Obviously the two concerns overlap.

But I'd much rather have bulletproof linked file support than "concept to vector" or "live paint" (as cool as those are)

No, it's not, my numbers were off. I did find the original source for analysis

A. my math was off

1 Little Boy = 63 terajoules https://en.wikipedia.org/wiki/Little_Boy

23 Little Boys / 24 hours = 16.77 Gigawatts

B. https://www.theenergymix.com/wp-content/uploads/2026/06/Wond...

"As recently described, the project would draw approximately 9 gigawatts (GW) of power, [...] Power would come from on-site, behind-the-meter natural-gas generation. At realistic generating efficiency, supplying 9 GW of electricity means burning fuel — and therefore rejecting heat — at a continuous rate on the order of 16 to 18 GW"

23 hb / 24 h = 17.5 GW

Correction: 16.77 GW

It's not a good look.

I pulled in from -proposed this time.

Ubuntu was slow on the brotli / CVE-2026-111497 updates as well.

I've been playing with `tart`

I already have users for Work stuff and Home stuff and Rando stuff. Fast user switching is great, however sometimes I need to do a quick check on some Home stuff, while seeing all my work windows.

The source is open, but the ownership of the "text" and 130 other gems still resides with the blog author... maybe he could add the projects to https://www.codeshelter.co/ or something.

This was very easy to set up and play around with.

Giving it the ability to access webpages / do searches would be nice!

It seems like the free 10000 "neurons" would cover light daily usage, like maybe 20-30 minutes of back and forth. I spent 500 in a few minutes of chatting until I realized the tasks I had in mind aren't possible.

How often are you running out of gas, so to speak?

That looks really useful

You haven't put this on github have you?

Have any of the cloud providers disclosed this?

"Once they have root on a single machine, agents rapidly escalate privileges and move laterally throughout the container-as-a-service infrastructure environment"

Sounds like ECS - IAM is mentioned.

They could get 10% bigger globes out of the same sheet of paper by rotating the icosahedron a bit (14º)

Why is daScript too niche?? Gamedev scripting itself is a niche, what can't you do in daScript or what would you not want to do in daScript?

daScript looks very complete

There's a lot to the language. Python and Rust vibes. Written in Zig. Seems to have lost steam. I wonder what happened

AI generated code is usually full of comments, human code is usually less commented.

It may be that AI performs better on such code.

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

Changelog:

    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

...will install a very recent build, with version 1.4.0

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.