4 ms·
A lot has changed over the decades, security models and stances have traded a lot of flexibility. To smooth some of the rough edges of purely compiling from sou
by artificial 6y ago
A lot has changed over the decades, security models and stances have traded a lot of flexibility. To smooth some of the rough edges of purely compiling from source take a look at homebrew (https://brew.sh/ https://brew.sh/). Spacemacs (https://www.spacemacs.org/ https://www.spacemacs.org/). I don’t develop desktop software any more and didn’t rush get into it on Mac, I’ve played around with swiftui a bit for iOS and server side (https://vapor.codes/ https://vapor.codes/). Perhaps the server side will scratch the itch?
- smoldesu 6y agoThese are stopgap solutions made to imitate aspects of other operating systems, and ultimately "break" the security model of the Mac. Apple knows the end-user is the weakest link in any security model, so by reducing the end-user's capabilities, you limit the risk they pose to the system. I'd rather just use an operating system that doesn't second-guess my choices in the first place.
- astrange 6y agoInstalling homebrew and emacs doesn't require turning off security. Maybe the one about "only run Apple signed software" - is that the default? I don't think it is.
- artificial 6y agoI don't think a 3rd party package manager "breaks" the security model. I'm pragmatic and that gives me a few choices about flexibility. I'm able to run the software I need locally (Adobe Products) and the shell is familiar and I've got the utilities I need and the languages to interact with them and I'm able to get what I need done. Thankfully my workflow isn't one that requires fighting the OS or tooling support. I spend my time fiddling with the server side of things and now that docker is a thing it's more application side than anything.