Ok, it’s true that you have to spend 15 mins after setting up to “install developer tools”, and remove some safety rails. However, the mac doesn’t prevent you from doing that, and doesn’t really even try to make it hard (if you’ve ever touched a terminal before). Once it’s set up, you’re good to go…
Depends on what you are doing. My company was using clang for c++ compilation and it was a drag to make all this clicks for each .so every is update. And there is no way to automate the process.
And those occasional compatibility breaks didn’t help either.
what do you mean? clang is a command line tool, can’t you write some cmake and a bash script to automate the build process? That’s what I always do when I writing any C++ that needs to be compiled/updated fairly regularly.
It has nothing to do with clang being command line. It consists of many binaries, all of them untrusted. Any time new dynamic lib is loaded Mac stops the process and complains. Then you need to do manual stuff, as you can’t automatically trust a binary, for obvious reasons. This happened almost two years ago, maybe clang got apple certificates or some shit to combat the issue. But my point was that every OS update on Mac brings annoying issues for developers.
I have to admit, I’ve never touched the kind of issue where I need to load a bunch of binaries I can’t automatically trust as part of a build process, so I won’t speak on that.
On the part about OS updates being a PITA, yes: I’ll admit that I offset updating the macOS major version for as long as possible. As long as my major version is maintained/get’s security updates, and the newer versions are backwards compatible enough that I can compile stuff for them without any hassle, I’ll stay on macOS 13. Judging by historical data, that means I have about two more years before I might need to spend an hour or two fixing up stuff that bugs out with the eventual major update.
I really like it, and I miss it on Linux. On Linux, I have to trust that each and every sh/bash script, package install script, or some stuff you download from internet are actually safe and don’t access your private stuff. On mac I get the prompt when some software needs to access a specific folder.
As a macOS user I don’t agree.
Me: “ls ~/Downloads”, mac-gui: Would you like to give “Terminal” access to the “Downloads” folder?
Ok, it’s true that you have to spend 15 mins after setting up to “install developer tools”, and remove some safety rails. However, the mac doesn’t prevent you from doing that, and doesn’t really even try to make it hard (if you’ve ever touched a terminal before). Once it’s set up, you’re good to go…
Depends on what you are doing. My company was using clang for c++ compilation and it was a drag to make all this clicks for each .so every is update. And there is no way to automate the process. And those occasional compatibility breaks didn’t help either.
what do you mean? clang is a command line tool, can’t you write some cmake and a bash script to automate the build process? That’s what I always do when I writing any C++ that needs to be compiled/updated fairly regularly.
It has nothing to do with clang being command line. It consists of many binaries, all of them untrusted. Any time new dynamic lib is loaded Mac stops the process and complains. Then you need to do manual stuff, as you can’t automatically trust a binary, for obvious reasons. This happened almost two years ago, maybe clang got apple certificates or some shit to combat the issue. But my point was that every OS update on Mac brings annoying issues for developers.
I have to admit, I’ve never touched the kind of issue where I need to load a bunch of binaries I can’t automatically trust as part of a build process, so I won’t speak on that.
On the part about OS updates being a PITA, yes: I’ll admit that I offset updating the macOS major version for as long as possible. As long as my major version is maintained/get’s security updates, and the newer versions are backwards compatible enough that I can compile stuff for them without any hassle, I’ll stay on macOS 13. Judging by historical data, that means I have about two more years before I might need to spend an hour or two fixing up stuff that bugs out with the eventual major update.
I really like it, and I miss it on Linux. On Linux, I have to trust that each and every sh/bash script, package install script, or some stuff you download from internet are actually safe and don’t access your private stuff. On mac I get the prompt when some software needs to access a specific folder.
click yes when this happens. this one is a freebie.
As a carrot I half-agree.
FYI https://en.m.wikipedia.org/wiki/MacOS