With Apple degrading the developer experience with each release and Microsoft working hard on things like WSL(2) and the new "package manager" I think within a year or 2 lots of developers will go back to Windows-based machines.
MacOS Catalina: Slow by Design?
281–290 of 1001 posts
Re: MacOS Catalina: Slow by Design?
#282This is completely insane. I am so glad I decided years ago to leave closed operating systems behind. This design seems to cement the trend at Apple to position their products as consumer appliances, not platforms useful for development.
> I am so glad I decided years ago to leave closed operating systems behind. The problem is, there's nothing else out there. Everything is going to shit in one way or another. Windows is now a disaster, Linux was always a disaster in terms of user experience and isn't improving. Mac OS was the last bastion of somewhat good, thoughtful design, user experience and attention to detail and now they've gone to shit too.
The funny thing is, Linux has amazing User Experience if you go all-in on the latest KDE and its associated tooling.
Re: MacOS Catalina: Slow by Design?
#283Re: MacOS Catalina: Slow by Design?
#284I am using Ubuntu 20.04 on a Thinkpad X1 Extreme Gen2 and you would be surprised how "normal" it feels as a development machine. Sure there some little annoyances, the touchpad behaves a little worse than on windows, sound is a little worse. But the most important things, Keyboard and Screen are excellent. The system in general does not feel like the horror stories that people keep telling about linux on desktop(note…
Windows is still very much subpar, even with support for CUDA in WSL2. Loading packages is terribly slow in Windows, for some reason. Also don't get me started on package management (no, Anaconda doesn't cut it).
Re: MacOS Catalina: Slow by Design?
#285In our company many of us have similar issues. I have always loved OSX but this time it is driving me crazy. I though the issue was some sort of company antivirus/firewall, or it could even be a combination of that and this issue (maybe my vpn + path to company firewall is what magnifies the issue in this post). The thing is that some commands take 1 second, some others take 2 minutes or even more. Actually, some com…
IIRC the big thing that changed with 10.15 for CLI applications is that BSD-userland processes (i.e. ones that don't go through all the macOS Frameworks, but just call libc syscall wrappers like fopen(2)) now also deal with sandboxing, since the BSD syscall ABI is now reimplemented in terms of macOS security capabilities. Certain BSD-syscall-ABI operations like fopen(2) and readdir(2) are now not-so-fast by default,…
> IIRC the big thing that changed with 10.15 for CLI applications is that BSD-userland processes (i.e. ones that don't go through all the macOS Frameworks, but just call libc syscall wrappers like fopen(2)) now also deal with sandboxing, since the BSD syscall ABI is now reimplemented in terms of macOS security capabilities.
Is this actually new in macOS 10.15? I seem to recall this being a thing ever since sandboxing was a thing, even all the way back to when it was called Seatbelt.
> That means that any CLI process that "walks" the filesystem is going to generate huge amounts of sandboxd traffic, which bottlenecks sandboxd and so slows down the caller process.
Is this not implemented in the kernel as an extension? I thought the checks went through MAC framework hooks. Doesn't sandboxd just log access violations when told to do so by the Sandbox kernel extension?
> Unlike macOS app-bundles, regular BSD-userland executable binaries don't have a capabilities manifest of their own, so they don't start with any process-local capabilities (with some interesting exceptions, that I think involve the binary being embedded in the directory-structure of a system framework, where the binary inherits its capabilities from the enclosing framework.)
I am fairly sure you can just embed a profile in a section of your app's binary and call the sandboxing Mach call with that…
Re: MacOS Catalina: Slow by Design?
#286I've been using linux distros (~5 years of Ubuntu and ~3 years of Arch) before switching to macOS somewhere around 2013-2014. And now years later I'm thinking about moving back. But every time I'm think about this I start with digging about current Linux situation and every time I realise than it is still a horrible system for anything outside of work, especially if you can't really do without a decent UI\UX. Apple's…
Linux on the desktop has been my daily driver for years (mainly xfce and gnome). I use linux to watch movies, create music, play games and everything else. What exactly makes it a "horrible system outside of work" for you?
>Linux on the desktop has been my daily driver for years
Same for me, I've even been a maintainer of one (ONE! lol) AUR package.
>especially if you can't really do without a decent UI\UX.
Outside of a few Electron-base apps and maybe a few native gtk\kde one - everything looks like a work of high schooler. Nobody thinks about the UI\UX.
Compare Things3 and something from linux word. Or Bear. Or Twitterrific\Tweetbot.
But go no further than your system's settings: https://imgur.com/a/p0kl7wM - wtf is this? You have a window that takes 80% of your screen some huge ass controls that still take some 20% of the the whole view. Who thought this was a good idea?
Gnome 3 is even worse (I loved gnome2 back in 2009)
Re: MacOS Catalina: Slow by Design?
#287> This is not just for files downloaded from the internet, nor is it only when you launch them via Finder, this is everything. So even if you write a one line shell script and run it in a terminal, you will get a delay! > Apple’s most recent OS where it appears that low-level system API such as exec and getxattr now do synchronous network activity before returning to the caller. Can anyone confirm this? Because hones…
[deleted]
Re: MacOS Catalina: Slow by Design?
#288It gets even worse. I was doing some web dev in the last couple months and I noticed that my "localhost" was ridiculously slow. At first, I thought it was NPM/Gulp but then I noticed that it behaved irrationally, sometimes it is slow and sometimes it works.
The problem was: Parental Control. Apparently, every request was checked and thus slowed the whole thing down. Needless to say, a couple days at least were wasted in this.
Re: MacOS Catalina: Slow by Design?
#289Earlier quoted context omitted.
Any distro in particular you'd recommend?
not him but same experience, from my previous comment: I would recommend: Ubuntu, Linux Mint, Elementary OS, Pop!_OS if you want: nice experience out of the box I would recommend: Arch, Gentoo, Debian Net inst, Void if you want a base system and install things you want on top of it
Thank you @all for the suggestions!
I'm going to set aside some time to experiment with these and see how far I get.
Re: MacOS Catalina: Slow by Design?
#290Earlier quoted context omitted.
I don't experience a delay in Terminal.app either, but I've tried running the script with a fresh install of iTerm2 while capturing with Wireshark and it does look like the script triggers a connection to an Apple server
I just ran the same script on iTerm2 and had no delay.
I had no delay neither until I reinstalled iTerm2, I have no idea why