Hacker News new | ask | show | jobs
by JadeNB 1046 days ago
> I would put it more towards Apple’s general philosophy of “the user shouldn’t have to care about that” than trying to uphold an image from a (extremely popular) 15 year old ad campaign.

Apple's general philosophy has always been "the user shouldn't have to care about that", but they've moved more and more recently to "the user shouldn't even be able to do anything about that" (I feel betraying their BSD roots along the way), and this seems to be an instance of that.
1 comments
Terretta 1046 days ago
> I feel betraying their BSD roots along the way

As a BSD 4.3, BSDi, FreeBSD, and now MacOS user, I'm not finding MacOS shell environment to be crippled in recent releases. If anything, even the ecosystem available to me through brew keeps getting broader as more and more tools add support.

What do you feel Apple has taken away from you at the CLI?

link
callalex 1045 days ago
Two come to mind 1. System Integrity Protection breaking sudo (I understand why the trade off is worthwhile but it can be painful sometimes) 2. APFS pulling endless opaque shenanigans when it comes to what uses disk space and which tools report what usage, and where data lives. The permissions model clashes badly with shell usage, and blatantly disrespects sudo.
link
ryandrake 1046 days ago
Not CLI related but here is a petty example of Apple taking something that worked for years and just dropping it. 1080i (interlaced) display support. My home theater tv supports 1080i but not 1080p, and I’ve been happily powering it with a Mac Mini running Kodi. A few years ago I “upgraded” macOS and lo and behold Apple just -decided- that I don’t need 1080i anymore and dropped support. No good reason, just “Fuck you, user. You don’t need this.”

Apple’s recent history is full of these “we know better and you don’t need this” decisions.

link