Maybe I’m just paranoid, but I personally decided to stop buying their computers because of it.
https://boingboing.net/2011/12/27/the-coming-war-on-general-...
At what point do we stop saying "he was so prescient, look we're almost there," and just admit things haven't turned out as badly as people feared? DRM has turned out be more of a nuisance than an apocalypse, and general purpose computing is at least as available today as it was in 2011.
In some ways it is even easier; for example anyone with an email address can get access to a cloud-hosted computer for free.
Finding parties that would benefit is a trivial exercise one has only to look towards app store revenue, Intels idea of selling "upgrades" to your cpu via software unlocks, or Verizons ability to rent you access to your gps for $10 a month.
Others have been pouring water on a fire that would have already filled your kitchen with smoke by now otherwise and you have merely failed to attend to this fact.
Could you explain some of these incremental lock downs? I honestly can't think of any that are genuine restrictions, but that might just be because I don't encounter them with what I do.
That alone has stopped me moving my Macs to the latest OS after testing.
Why not? It's his system, he should be able to do whatever he likes. On most Linux I can rm -rf / all day long and nobody cares. What's the problem with creating root level directories?
> On most Linux I can rm -rf / all day long and nobody cares.
So let me turn this around: Why do you think a system that doesn't make it difficult to completely destroy it with one command is a bad idea? "It's my system, I should be able to do whatever I like" is an answer, to be sure.
(N.B.: in fact, "rm -rf /" won't work without "--no-preserve-root" in most Linux distributions, AFAIK, and I presume sudo.)
The decision on which bits of the system I can destroy should be mine, not theirs. That's the issue. At the moment, I am getting pushed out of my machine, bit by bit. Every binary I run is getting report to Apple etc.
It is also possible to destroy the system by dropping your MacBook from a very great height. Should it be padded to cope with this eventuality?
This does not seem very charitable.
It is fine if the system warns you about doing potentially dangerous operations (which --no-preserve-root amounts to) but it must not prevent you from ignoring that warning.
It was a habit on macOS since /Developer used to be where xcode lived until they moved it to /Applications.
It also makes it easy to look in the /DeveloperLibs directory and see if I've got all libraries I need on this machine (I have different development machines under different OSes).
Removing ability to create directories under the root seems draconian for no good reason, other than the iOS-ification of my machine. Not Apple's machine - my machine.
I don't understand why people would ask "why would you want to do that?" because everybody used to defend the ability to only resize windows from the bottom right corner under macOS until a few versions ago, when it became obvious that resizing a window from any edge was a good idea and always had been. But people oddly defended it for decades before that.
What if they now remove the ability to change your desktop wallpaper? Would we all say "but why would you want to change your wallpaper?"? We seem to accept the gradual lock-down of our own machines. Apple users (and I am one) seem to be the most defensive of the company's behaviours and it doesn't make sense - we just have to accept it.
If Microsoft removed the ability to create a directory under C:\, what would the result be? Would we be asking "but why would you want to create a directory under C:\?"? I think not. It'd be the apocalypse.
There are certainly many decisions Apple makes that I don't like and I am always keeping my eye on Linux in case I really feel the need to pull the rip cord. But for me, this is just not a hill of sufficient size to die on. "Apple now mounts the system partition as read-only" just doesn't feel like a slippery slope that leads inexorably to... well, I'm not really sure where people imagine it's going. "This is something I used to be able to do and now I can't and soon that means I won't be able to open a shell!" I mean, maybe, but... probably not. If I had to choose whether "Macs in five years will only be able to install programs from the Mac App Store" or "iPads in five years will be able to install programs from places other than the iOS App Store" is more likely, I'd honestly go with the latter.
> I don't understand why people would ask "why would you want to do that?"
I guess I don't understand why asking the question is controversial; I'm not trying to lead anyone into a rhetorical trap that forces them to admit only axe murderers would ever use this functionality. :) It's simply that in what I'm pretty sure is over a quarter-century of Unix use on my part I don't recall ever putting anything in the root directory of any of my systems except by mistake.
As for "defending the ability to only resize windows from the bottom right corner until a few versions ago," your memory of this is different from mine, I suppose. I recall a lot of Mac users thinking that Apple's one-corner-only approach was a bad leftover from the pre-OS X days that needed to change!
It would get rid of shitty Mac application documentation that rather than installing itself in correct locations, has troubleshooting steps like:
> Just chown your entire `/` to your current user and `chmod +w *`...
Until Atomic installations become the norm like SilverBlue its probably a good step.
The second, is that I am able to create root folders, I just have to remount as rw before creating it and after that I can mount any data folder to `/foo`. I'm not entirely clear why not having `/` as rw by default is such an issue, but you are cetainly not prevented from doing it if you wanted to.
Why would Apple want to restrict access to certain memory locations?
Finder hides all of /etc and /bin and /usr for the "protection" of normal users, just like the default view for Windows Explorer under C:\Windows\System. But you can still change the contents on Windows, or see the directories in Terminal on macOS.
Should they hide those directories when you use Terminal too? After all, /etc is important. Your reasoning would also stand up there - perhaps whatever files you were attempting to modify under /etc wasn't actually that important.
When does the "you cannot easily modify files on your own machine" stop?
Would you also accept the inability to change your wallpaper with such glee? Perhaps the wallpaper you wanted wasn't actually that important.
...it's...the root of your entire system? Are you really asking me why `rm -rf /` is a meme, or are you just being contrarian?
> Finder hides all of /etc and /bin and /usr for the "protection" of normal users
And you can change Finder's preferences to show those folders, like any actual macOS user that's qualified to be making changes to those folders should know. If you lack both the curiosity and the ability to look up how to enable that option, then you frankly have no business modifying them yourself. If whatever you wanted to copy or edit there wasn't important enough for you to take ten seconds to look up how to do it and then follow through with the instructions, then why on earth would you be complaining about it to anybody?
I can also do rm -rf ~/Documents or rm -rf /Applications or rm -rf /Library which has a similar devastating effect to my life/machine - should we block that too?
I can also fling a hammer into the screen and break the screen - should we put extra thick glass on the screen? I guess I have no business using a MacBook if it is possible to break the screen.
I can also pour liquid into the keyboard - should the keyboards be waterproof? I guess I am not qualified to use a Macbook and have no business using one if I spill a drink.
Using the keyboard is dangerous too because someone can type dangerous commands. Let's stop people using it. Only those with sufficient "curiosity" and those "qualified" should use it, right? How do I get "qualified"?
I am saying that as it is my machine, I get to decide which parts are dangerous. But I no longer can because someone the other side of the world has decided that I am cannot create a directory under /.
I do not ever modify /etc using Finder. Should I only be allowed to edit files under there using Finder or is Terminal permitted?
I guess if we follow this "lock down" and "only those qualified" route that you encourage, we'll soon see permission prompts to do anything anyway.
There have been examples of (un)installer scripts removing substantial parts of your system, steam for example. Linux in this case https://github.com/ValveSoftware/steam-for-linux/issues/3671, but not generally unthinkable on MacOS. It's generally good if the system puts up barriers to prevent such occurrences.
You're entirely welcome to disable these protections, but MacOS is designed to protect Joe User who may have substantially less knowledge and who has no general need to mess around in /etc
It's like banning knives because there's been a few stabbings. It removes the general utility due to misuse by a few.
> synthetic.conf describes virtual symbolic links and empty directories to be created at the root mount point.
It's almost as if they've been actively devesting in OS X.
At least we now understand why.
Mac's are no longer machines fit for professional development. It's a damn shame, but it's true in my mind.
For a long time, I and other people I know chose MBP for professional web-development / video editing / music production because they were provided with a slick GUI on top of a solid operating system.
It's fairly apparent to most people who read tech news, that the quality of the operating system isn't what it was. For instance, think back to the 'no password necessary for root user' debacle a few years ago.
I don't think it's beyond the realms of credulity to consider why this type of problem was allowed to occur in Apple's 'professional' line.
If you're still with me, perhaps you'd also be able to follow my line of reasoning when I surmise that the reason for this degradation of support, may have been because they were planning on dropping their support for OS X .. with this convergence event being its replacement.
In reality, it's your own sassy comment that's devoid of content. Hope you really did wait! :)
Would you buy a house without any locks since it's convenient? As long as you have the key it's paranoid not to buy Apple because of some restrictions since any PC also has a lot of these (secure boot, DRM etc).
Not my experience. It took a couple weeks of noodling to get parts of my environment moved over, and some of my automation I just moved to a linux box because I got sick of it.
> we've somehow got to the point where people bash apple for actually taking privacy and security seriously
Wow.
On the planet I use a Mac on, the complaints are about a set of non-manageable, opaque and somewhat buggy security changes that arbitrarily changed semantics on big chunks of the filesystem and broke a bunch of things is hard to figure out ways.
Add in that there is no sensible mechanism for cleaning up any of these magic permissions paths, and I don't even know what permissions are active on the machine I'm typing on.
I've loved OS X for being a decent gui on a real Unix. It had a decent run, but my next laptop will be a Linux box.
Lately, I've been doing most of my dev work on a Windows 10 machine using WSL. It's come a long way and is very usable now.
Having said that: I agree, WSL is pretty amazing.
Try running dtrace without having to configure a bunch of settings and restarting your Mac. Then you have to change the settings back and restart again to go back to the way it was.
It's a pain in the hole, and for basically no reason.
I still don't believe Apple on the privacy front. Yes, they are better than competitors. Anyway, I would like freedom and privacy and don't see them as contradictory. And you won't get more privacy if a manufacturer locks down environments.
We had OS without any privacy intrusion without any form of lock down. MS drops the ball constantly, agreed, but that isn't a metric anyone should look for.
Freedom and privacy are at odds. If I give any app the freedom to access my messages or call list, does it increase or decrease privacy?
I have an app(lication) that has access to my messages. It doesn't do anything with them aside from showing them to me on request. It doesn't affect my privacy at all because doing so is far beyond its scope. If I had shitty apps, I would agree, but until now those seem mostly restricted to shitty app stores. But if they cannot be trusted, they cannot be trusted to see my messages at all.
> People are drawing, creating music, making movies, editing photos on their mobile OSes
True, they are not completely useless, just mostly. I can do that on other OS with far more freedom. Artists generally don't like restraints too much and I do actually paint digitally. Wouldn't know how to connect it to a mobile device, nevermind the atrocious software selection.
The cameras on mobile devices are nice though. Don't think the common mobile OS makes handling image date easy at all. Even most normal users want images on their desktop as soon as possible.
People are taking the UI / ARM change as apple taking away more control, but macOS is THE development platform of the entire apple ecosystem.
So yeah, the ecosystem may be tighter knitted, but they sure as hell will not lock down macOS like they do iOS, they have so many mac users who are developers and apple are absolutely aware of that.
People complain about features in catalina and other recent versions of macOS 'locking things down' - it's incredibly easy to bypass the stuff that makes a difference using the terminal.
In a world where every company in the world wants to track and harvest your data, we've somehow got to the point where people bash apple for actually taking privacy and security seriously.