gmac

In my experience with front-loaders, all of these are non-problems.

But my understanding is that top-loaders are always inefficient: they have to use a lot more water, because the clothes have to be submerged, and thus they also have to use a lot more energy to heat it.

Typo: prescribed burns.

One of the most ridiculous pairs of approximate homophones in the English language.

Proscribed = forbidden. Prescribed = recommended/required.

Watch this happening! https://bytebybyte.dev/

I skipped macOS 26 (except on my work laptop, where it’s crap), but I don’t think iOS 26 is significantly worse overall than iOS 18.

Same here. And I was seriously impressed with how much noise cancelling the v4 can do. I will be seriously impressed again if the v5 is as much better as they claim.

Discussion: https://www.postgresql.org/message-id/CAAKRu_bEtjWYWhYxSo0o_...

The price is so reasonable, I think the risk is that you’re paying mainly with your data?

Perhaps not if the one framework we ended up with was a good one …

I mean, there's certainly silly money involved, but there's surely no credible doubt that AI is already really good at many valuable tasks.

So if there's a crash, doesn't that just leave us with a bunch of useful AI hardware whose costs have been written off? I wouldn't have thought that much changes what social impacts AI is going to have.

https://printervention.app (also co-written by Claude) may be useful in similar cases.

Yes — configuring strongSwan as a bog-standard VPN server was so hard to fathom I made GitHub repo for it [1]. To be fair, some of the complexity comes from OS support that seems specifically designed to make secure setups difficult, presumably at the behest of various Three Letter Agencies.

I have now mostly switched to Wireguard for this, which is much more sane [2].

[1] https://github.com/jawj/IKEv2-setup [2] https://github.com/jawj/wireguard-setup

These are called phrasal verbs. https://en.wikipedia.org/wiki/English_phrasal_verbs

I've found Opus 4.8 pretty amazing, and Codex a bit meh. YMMV?

I mean, that's fair. To an extent it depends how high the stakes are and whether there are realistic alternatives to a service.

I have plenty of ability to read, but I never read these T&Cs because they’re usually dozens of pages long and life’s too short (or, if you prefer, the cost/benefit doesn’t support it). For consumers in Europe, at least, it’s usually safe to assume that anything too shitty is unenforceable, which helps.

(It's a double-press, which I think of as one action but I guess it's technically two button presses, because I believe the EU mandates that)

Renault have nailed this. In their latest cars (the EVs, at least) you set up which features you do and don’t want, then a single button press when you get in the car makes it so.

Some of their implementations, such as lane keeping, are good enough to keep. Others, such as speed limit detection, aren’t (though it’s much better at French speed limits than UK ones, which I suppose makes sense).

There's a middle ground between ORMs and raw SQL, especially if you're using a strongly typed language. My library Zapatos[1] is one example among several.

[1] https://jawj.github.io/zapatos/

Basically: you can't teach people to think without giving them some facts and ideas to think with. It's like trying to teach woodworking without giving the students any wood.

Which is generally slower than Googling, because it's paged content in a terminal which can search only for literal strings?

Practically speaking, yes: I have a Renault EV and the battery % goes up on long descents.

It’s interesting that EESMs can be more efficient at high/highway speeds, and it’s something I had read before. This seems to me to be a key advantage of EESMs, because when people worry about EV range, they worry mainly about range on long-distance, high-speed journeys.

(I have a Renault EV and it’s excellent. Aside from the motor technology, it’s relatively light, has a heat pump as standard, and a good-sized battery).

No, it's an immigration restriction. There's no way it applies if the Swiss start having 5 kids each.

Are you trying to claim that American private healthcare is anything other than a giant shitshow of inefficiency, profiteering and death?

My monetization idea doesn't involve charging users, and it's more on the printing side (but most of the source is shared with scanning).

That is super helpful (I may well use it myself). But I guess a web app probably reaches some non-technical users that CLI tools don't.

There’s separately a /credits page where I’ve done that, linked from the footer. Perhaps I should link it from the apology too. Tell me if you think I’ve not shared what I have to.

If you think I’ve done something wrong according to the licences involved here, please do clarify. I had understood that open-sourcing the Linux stuff (as branches of a fork of v86, linked from the /credits page) met all relevant legal obligations, which I absolutely intend to do.

More broadly, it’s unusual for me not to make everything open, and I do feel bad/conflicted about it. But, unusually, I feel like I have identified a possible route to monetising this, and I think open-sourcing all of it risks making that harder.

Do you really find you can reliably sustain your full attention that long?

My EV can do 3 – 5 hours on the motorway between charges (depending on weather conditions and speed), but to avoid fatigue I always want a break within 3 hours or so.

And by the time I've parked, gone inside, queued up for and drunk a tea or coffee, used the facilities, and checked the next leg of my trip, that's half an hour and the car is ready to go again.

Previous discussion on Yes We Scan's sibling project, printervention.app: https://news.ycombinator.com/item?id=47677885