Sure - but in the real world that mostly only happens when the documentation is an afterthought.

Not sure about jellyfin, but I assume it uses ffmpeg? The M1 is fast enough that ffmpeg can re-encode raw video footage from a high end camera (talking file sizes in the 10s of gigabyte range) an order of magnitude faster than realtime.

That would be about 20W. Apparently it uses 5W while idle — which is low compared to an Intel CPU but actually surprisingly high.

Power consumption on my M1 laptop averages at about 2.5 watts with active use based on the battery size and how long it lasts on a charge and that includes the screen. Apple hasn’t optimised the Mac Mini for energy efficiency (though it is naturally pretty efficient).

TLDR if you really want the most energy efficient Mac, get a secondhand M1 MacBook Air.

This. My Mac has 16GB but I use up half of it with a Linux virtual machine, since I use my Mac to write Linux software.

I don’t need to do that - I could totally run that software directly on my Mac, but I like having a dev environment where I can just delete it all and start over without affecting my main OS. I could totally work effectively with 8GB.

Here’s a tip on good documentation: try to write the documentation first. Use it as your planning process, to spec out exactly what you’re going to build.

And any time the documentation doesn’t match the code you wrote… that should usually be treated as a bug in the code. Don’t change the documentation, change the code to make them line up.

You don’t need metaphors or comparisons.

The Spotify app should have a button that takes you to their website, where you can sign up for a premium subscription.

It doesn’t have one because Apple would kick Spotify out of the App Store.

Also - all other links to the Spotify website (support, terms of service, privacy policy, etc) take you to pages where the main navigation of the website has been removed so that you can’t find the signup page. Because again, Apple bans that. For the longest time apps have not allowed to have any way for users to find a signup form on a website.

Apple claims to be compliant now, because they have a new API - only available in Europe - that informs the user that they might be a victim of identity theft, fraud, etc if they continue, then would take you to Spotify’s signup page. Also if Spotify wants users to see that horror show… they’d have to pay tens of millions of dollars per year. Vs not taking advantage of the new API where Spotify doesn’t pay anything to Apple.

Have they released who is going to pay for these power plants? Because if they put it on my monthly bill, I’m going off grid and I bet half the rest of the country will too.

near ChatGPT4 performance locally, on an iPhone

Last I checked, iPhones don’t have terabytes of RAM.

First of all, you’re implying it runs latest Windows - but Windows 11 shipped a few years ago.

Second - not really a fair comparison. 18 years ago the iPhone didn’t even exist. And the oldest model (17 years old) had really weak hardware. 4GB of storage, 128MB of RAM, and the CPU was an order of magnitude slower than current spec CPUs (it was also 32 bit - and 64 bit ARM is a completely new architecture - similar to the failed Itanium).

Apple was advertising that these devices would be refurbished when they were sending them out to be destroyed

When did Apple claim that?

Sure we can make a different ticket for that to move this along, but we’re getting product to agree first.

Ooof, I’m glad I never worked there.

QA’s job should be to make sure the bugs are known/documented/prioritised. It should never be a roadblock that interrupts work while several departments argue over what to do with a ticket.

Seriously who gives a fuck if the current ticket is left open with a “still need to do XYZ” or it gets closed and a new one is open “need to do XYZ”. Both are perfectly valid, do whichever one you think is appropriate and don’t waste anyone’s time discussing it.