Cost scales with refinement effort, so it just results in more expensive TVs. That said, pretty sure we'll have drowned the planet in landfilled TVs long before this becomes a serious issue

I definitely was expecting "transported" to be some kind of teleportation when I clicked this link. Too much sci-fi!

Much safer than Starfleet fuel tanks.

Surprisingly, teleportation is easier.

Had the same thought! haha

Was kind of disappointed to see it was transported via 18-wheeler.

Totally sounded like Star Trek. LOL. I imagined Mr. Scott yelling something about the transporters not being able to lock onto the antimatter.

Given that they just shuttered their "metaverse", I'm guessing we won't have to for much longer...

While Ofcom hasn't required it yet, they have indicated that they very much plan to[1]. Apple is pretty clearly getting out ahead of this, and simultaneously removing the burden of compliance off all of the relevant app developers (which seems in line with their overall privacy stance - I'm more inclined to trust Apple with my ID than I am some social network)

[1]: https://www.rpclegal.com/snapshots/consumer/winter-2025/ofco...

Removing friction from a process that damages privacy is not a positive.

Passing a law that damages privacy is a negative. Complying with the law is an imperative. So mitigating harm from the law seems like a positive.

It's also not a net negative, if that process is going to be mandatory

That mentions app stores, but I can't see anything about device-level age-verification there.

Also, does Ofcom have the power under the Online Safety Act to mandate app-store verification (or device-level verification, for that matter)? Or would it require secondary, or even primary, legislation?

Somehow I confused httpx with htmlx

I guess you mean htmx. Same here. I read the article for a while, and was confused by "HTTPX is a very popular HTTP client for Python." and wondering "why is OpenAI using htmx", until I eventually realized what's going on.

And also htmlx with htmx I guess?

I've been reading the whole article wrong too.

Same! Only just realized it thanks to your comment.

I thought your comment was starting with "Samuel". Plenty of people on sick leave as of late - must be difficult for many to focus their sight.

This is substantially more useful than the marketing fluff in the press release. Probably would have made sense to post this in that thread though

> they've priced the consumer/pro-sumer out of the market prettymuch

I'd argue that (the low end of) Apple products are the cheapest they've ever been - the $599 iPhone 17e is below the inflation-adjusted price of the original iPhone, and at $599 the MacBook Neo is the cheapest launch price an Apple laptop has ever listed at (not even adjusting for inflation!)

The maximum amount you can spend at the high-end has certainly gone up over time, although the basic MacBook Pro Max config costs roughly the same as it's peer from 10-15 years ago - nobody's forcing folks to shell out for the 128GB of RAM (something that didn't exist on laptops at all till very recently)

> I’ve never sat there thinking “If this was only 2 seconds faster…” while doing an update

I definitely have thought something along those lines (mostly when I go to install a small tool, and get hit with 20 minutes of auto-updates first).

Pretty sure I also will not be adopting this particular solution, however

I've never thought "only 2 seconds faster" - I've certainly thought "why is this taking half the time it takes Gentoo to recompile an entire server".

But you can turn that behavior off, IIRC it tells you the environment variable to set if you don’t want it to do that every time it runs.

I agree it’s annoying, but I haven’t turned it off because it’s only annoying because I’m not keeping my computer (brew packages) up-to-date normally (aka, it’s my own fault).

I'd be much happier if it were on a background job, than arbitrarily running when I invoke a command

I've started using https://github.com/DomT4/homebrew-autoupdate recently, which has been great.

Terrible default behavior is a great reason to abandon a software package.

I'm not sure if I just have way fewer things installed than most people or I just update more often, but I haven't experienced anything like this for years. I run `brew upgrade` probably around once every (work)day, usually right before doing a git pull or something, and then I'll quickly look at a couple emails or slack messages, and then it's always done by the time I switch back

What? Why are you running brew upgrade every day?

To upgrade my packages? I'm not sure I understand the question. That's how I use pretty much all of my systems that have package managers.

But why do you want daily upgrades? Most of us want to wait a little while for the bugs to be worked out of fresh releases. And hey, if everything is working today... why would I want to risk potential breaking changes?

I don't recall ever having something break from upgrading it in homebrew, but I do recall having issues in the past from having things outdated without realizing it (usually stuff that wasn't getting upgraded by my package manager, e.g. VS Code being months out of date without me realizing and therefore not working with an extension the company I was working at had developed).

On the average day, I get maybe two or three package upgrades from it. Sometimes, they're packages that I'm extremely grateful to have updates for immediately (like rust-analyzer), and other times they're things that I don't use very often (or don't use directly), so I wouldn't likely remember to upgrade them at all if I didn't make a habit of it.

> Most of us want to wait a little while for the bugs to be worked out of fresh releases. And hey, if everything is working today... why would I want to risk potential breaking changes?

I felt like I was pretty clear in my original comment that I didn't know whether other people upgraded as often as me or not. That being said, it does sound like you've been having an experience you're unhappy with, and I'm not, so I'm not sure why you're so confident that the way I'm using it is weird. It's very possible that it would not end up being something you or others are happy with, but it's more weird to me that you think this is such a huge deal when it seems like the most obvious way in the world to use a package manager to me.

> Most of us want to wait a little while for the bugs to be worked out of fresh releases.

This is not something that's solved by updating less frequently though. It would be solved by a 'minimum age' setting, but `brew` aren't planning on implementing that, with arguably valid reasoning: https://github.com/Homebrew/brew/issues/21421

> It would be solved by a 'minimum age' setting

Minimum age solves a related problem - it gives maintainers some margin of time in which to discover vulnerabilities and yank the affected versions.

However, minimum age also delays you getting bug fixes (since those also need to age out).

In an ideal world one would probably be able to configure a minimum-age-or-subsequent-patch-count rule. i.e. don't adopt new major/minor package versions until either 1 month has elapsed, or a minimum of 2 patch versions have been released for that version.

FWIW this seems to have improved in recent years. Back in the dark times of non parallelized downloads I would purposefully wait to end of day and fire the thing off before leaving

It's an old joke, but it's also accurate in this case - isn't what you are asking for just WINE?

> isn't what you are asking for just WINE

An operating system is a style of thinking about your work. WINE is a way to get Windows applications to run (by now run decently) under GNU/Linux. These Windows applications are nevertheless foreign bodies in the whole kind of thinking which GNU/Linux is built around.

The joke is that the most stable Linux API for applications is ... WIN32 via WINE.

It's sad because it's true.