A fast, shallow reply doesn't save a customer's time. It's just a useless volley back to the customer that keeps their request off the support queue.
It may burn off customer support engagement among customers who don't have the capacity or patience to keep pushing for help (this is a bad outcome for customers, but looks deceptively positive in vendor-side metrics), but for the remaining customers it just adds latency and work.
I had a AI customer service interaction (it was explicit about being AI, used fin.ai iirc). At first I was amazed! It was doing email as fast as IM! And the first response seemed really knowledgeable and put me at ease.
But it failed to do a key step (generating a shipping label for me). I went back and forth over 21 messages trying to get it to do it. Then I wrote "escalate to a human" and an hour later someone replies with a shipping label directly.
I would much rather have had a slow but correct response than a fast but confidently-wrong response.
Before the AI first level support often wasn't allowed to type answers but instead copy paste one of the answers from the faq, which was extremely frustrating.
The chat would go like this:
- I have a question about "no vehicles in the park" policy. Does it include motorized wheelchairs?
- To guarantee safety and blablabla our policy is that no vehicles are allowed in the park.
- so can i go to the park with a wheelchair with a battery and electric engine?
- To guarantee safety and blablabla our policy is that no vehicles are allowed in the park. Please see our safety policy (link).
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.
Instants are important if you migrate something, like TLS certificates, data flows, etc. ISO-8601 is widely adopted, unambiguously interpreted, human-friendly format for that. I see no reason to not have it.
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!
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)
That's what the article says, yes. But is it accurate? The confusion of units makes me question the numbers, especially since I can find no other reference of the power usage or generation capacity of the site.
"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"
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?
No it is a vibecoded mess. Bet if you show the screen to a agent of your choice you will have yours in no time. The benefit is that if you give it self installing scripts you can just ask itself to add features
Cgroup and nice it so you never lose control of the machine tho
reply