However, when it comes to both Linux and Windows, the speed in a VM blows macOS out of the water. I have done some tests running different macOS versions in both Parallels and VMWare giving maximum juice to the VM, and also tried to “optimize” macOS (unloading/removing OS features not needed). The issue is that it will run pretty slow. I've yet to see a compelling reason to upgrade from Adobe CS6, and being forced into an unending and very, very expensive monthly payment plan just to use Adobe anything. Might be worth purchasing a copy of Parallels or VMWare just to sandbox and run older apps. I wish I could upgrade, but killing 32 bit app support makes that impossible for me, at least for the time being. Into the system python regardless of platform/os. If you are doing python development you should be using virtual env's and not installing everything There is a version of homebrew for linux though I don't/won't use it Homebrew is great, even arguably better than some Linux package managers, so no. If you do a lot of development in Python, Perl or Ruby, you'd might want to just switch to Linux where the hoops you have to go through to install OSS stuff are fewer. You can easily download those from their respective repositories. Not including those apps isn't a choice made by Apple, but due to licensing. If this direction continues, I'm done with Apple. I've been using Macs, exclusively, since 1988. Time Cook said it years ago, why would anyone want a Mac if they could have an iPad instead. The fact they no longer include Python, Perl, or Ruby gives me more indications as to their direction. I’ll need to see if I can roll back if I can’t figure out what’s going on with the certificates. Generally speaking the enhanced security is a real pain and the Citrix thing is a real problem for me. Not entirely sure why they need to, but giving all of them permission one by one is a faff. I had never realised how many apps needed to monitor the keyboard while using other apps. Then it spends a couple of minutes “Verifying the file” while the process xcodeprotect maxes out the processor. However none of the games would run until I launched them through Finder rather than Steam. It means I’m going to have to use my XPS 13 today (ugh - I hate multi monitor support in Windows and, on an unrelated note, discovered that the XPS won’t charge from my TB3 monitor - one of the LG 4K 23.7” “designed for Macs” which is supposed to put out 60w - so I need to use another USB connector for the charger).įixing Steam was painless in terms of updating the client. It claims the certificate is untrusted and I’ve not been able to persuade it it’s fine through utilities/keychain access. None of this has absolutely anything to do with the security model. On Linux, you just figure out the names of the packages and you’re done. I curse the days when I have to fiddle with the Mac to do that half of the time thing don’t compile, compilers are messed up, libraries are installed in all the wrong places if you get them to compile, environment variables are missing or wrong. I work with and develop low-level software that is mostly run on Linux but it also has to compile and run on the Mac. Pointless overcomplications in the MacOS security system is why garbage like homebrew et al. Trying to attain some sort of “correct Unix” ideal is counterproductive to a single user desktop system that is used for getting shit done, not for pretending that you are managing a server. Pointless overcomplications like this are exactly why Linux as a desktop OS is still a joke today. If Homebrew wants to install to /usr/local as non-root, then the correct Unix way to do it is to create a separate account that is not used for anything except to maintain Homebrew. macOS in general is based around that philosophy with how applications are managed, and Homebrew is consistent with it. managers/.ĭespite what old-fashioned Unix nerds will tell you, there is no real benefit in installing everything as root on a desktop computer, especially if it is mostly going to be used by a single user anyway. This approach is to be avoided.įor more details on the issues that can arise with Homebrew’s approach, I agree with much of the criticism in this post. Homebrew avoids `sudo` by taking over permissions in `/usr/local`. Many applications must be installed and controlled securely at the system level with `sudo`. It’s important to know that Homebrew’s security model is incompatible with many scenarios. Anyone who relies on the built-in versions Python, Perl, or Ruby can breeze through installation using Homebrew or other methods
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |