Hacker News Re-Imagined

The Perils of M1 Ownership

55 minutes ago

Created a post 70 points @ingve • 1 comments

The Perils of M1 Ownership

@laurent92 25 minutes

Replying to @ingve 🎙

The other peril is not being able to run a docker machine because it’s not available for M1. Which is disappointing because, you know, because you can’t tell customers that your software wasn’t tested in Oracle, and we invented VMs to be able to run any VM on any other machine…

Reply


@Wowfunhappy 23 minutes

Replying to @ingve 🎙

This isn’t the right solution, but I’d be curious to know if these problems disappear in Permissive Security mode (aka Secure Boot off).

Reply


@Amin699 19 minutes

Replying to @ingve 🎙

Good job

Reply


@JoshTko 18 minutes

Replying to @ingve 🎙

In other news, edge case use encounters edge case issues.

Reply


@gjsman-1000 18 minutes

Replying to @ingve 🎙

It’s almost as if Apple is building their Macs to be rogue nation-state resistant or something. Because otherwise is this almost actually security overkill? (Which does exist, we don’t want TSA Security to enter a grocery store, for example.)

Reply


@grishka 15 minutes

Replying to @ingve 🎙

One question: can I finish the setup of an M1 Mac without giving it an internet connection? As in, could I get it from unboxing to desktop without it sending a single network packet to Apple?

Reply


@xrd 11 minutes

Replying to @ingve 🎙

Trying to ship software for OSX *in general* drives me crazy, and this seems like more.

This quote: "I’ve been unable to find any information provided by Apple (or anyone else) which explains what’s going on, what the errors mean, or how to address them."

That's my experience constantly.

My development build had weird behavior when I explicitly launch it? Oops, Apple launched a cached version of the app inside a private temp directory (thanks Gatekeeper!) associated with the protocol handler.

But no way to tell until I casually check the process working directory. No documentation indicating how to troubleshoot this.

Countless issues like this.

Whenever I develop for JavaScript, if I find a module that just has weird undefined and undocumented behavior, I get rid of it no matter how powerful. I wish I could do that with the Mac developer ecosystem. It's closed and Apple will say that gives them a premier experience but it's the little snags that cost me 90% of my time and are impossible to troubleshoot other than grunting through it.

Reply


@dlevine 9 minutes

Replying to @ingve 🎙

It seems like these changes have good intentions (i.e. improved security), but introduce a lot of complexity that can have unintended consequences for end-users. This reminds me somewhat of my process setting up UEFI Secure Boot on my Windows PC that wasn't originally configured for it. Not in the exact steps, but in that there is a ton going on behind the scenes and the UX is horrendously bad.

Unfortunately, vendors haven't really thought about how to explain these changes to end-users. They are trying to make them fairly transparent, which probably works at least 95% of the time, but for a small percentage of people, becomes a big PITA.

Reply


@kartayyar 7 minutes

Replying to @ingve 🎙

You don't buy a Mac (M1 or otherwise) to live an adventurous life. You get it because it has really well executed take on an opinionated computing platform that just works for normal people.

Reply


@smoldesu 29 minutes

Replying to @ingve 🎙

Well, this just about confirms the worst nightmares I've had about hardware-based TPM. This "Owner" concept in particular rubs me the wrong way, it just seems antithetical to the idea of general computing.

Reply


@unstatusthequo 28 minutes

Replying to @ingve 🎙

Fringe use case of using multiple operating systems != peril.

Reply


About Us

site design / logo © 2021 Box Piper