Live data from Hacker News

MacOS Catalina: Slow by Design?

sigpipe.macromates.com

561–570 of 1001 posts

Re: MacOS Catalina: Slow by Design?

#561
post #419

Earlier quoted context omitted.

I share almost all of these issues. What drives me super nuts is the multi-display support which NEVER "just works". I have to disconnect and reconnect USB-C 3 times, turn off the second monitor, switch inputs, restart the €3000 machines twice or whatever. So annoying, how does this pass QA at all? Also, don't setup and use multiple users at the same time. That's really messy as well.

Since Steve left us, over time I've witnessed so many issues crop up in the Apple ecosytem, for users/customers and developers, and it's clear that there's nobody to be shit-scared of anymore at Apple. So many recent things would have pissed him off. There's no way the 'notch' would have appeared. Nor the fact that the iPhone camera design stopped the device sitting flat on a surface.

if Steve were still alive, iOS would never have been as open as it is today.

Re: MacOS Catalina: Slow by Design?

#562
post #490

Earlier quoted context omitted.

OCSP is Online Certificate Status Protocol, generally used for checking the revocation status of certificates. You used to be able to turn it off in keychain access, but that ability went away in recent macOS releases.

Ah, Apple. When you can no longer innovate, just start removing features and call it simplicity...

Feature-removal has been the most aggravating part of my Mac life for the past several years. Admittedly I tend to use unusual features, but it's just another PITA when they go away.

Re: MacOS Catalina: Slow by Design?

#563

Earlier quoted context omitted.

Happy MacPorts user of just over a year as well, for a variety of reasons I won't get into here but that being one of them.

Very satisfied MacPorts user since 16 years. I really don’t get why brew is a thing...

ports are for old beards, brew for cool hipsters.

Re: MacOS Catalina: Slow by Design?

#564
post #525

Earlier quoted context omitted.

Or NIX_PATH, or ~/.nix, et c. I am infinitely tired of this node_modules “we know better than you, it isn’t configurable and will never be configurable so stop asking” hubris. It’s not open source entitlement to say that a maintainer with that attitude is bad and wrong. My homebrew is installed to ~/Library/Homebrew and while they claim it’s unsupported, it works, and if it stops working, then I’ll stop using Homebre…

You can use an alternate path with Nix. When you choose to do that, you will have to build all packages from source instead of installing prebuilt binaries.

That makes sense, and is good news. I withdraw my complaint against Nix; in my defense my ignorance was based on the thread on their GitHub about how Catalina makes Nix basically unusable. Turns out those people were both a) wrong and b) speaking authoritatively from ignorance. :/

I’m quite glad I can just install it somewhere else, and finally ditch the Homebrew spyware. Thank you for letting me know!

Re: MacOS Catalina: Slow by Design?

#565
post #111

Earlier quoted context omitted.

I switched to a linux desktop full time last week because of this exact problem. VPN w/ windows would flake out on me all the time, and I got sooo tired of just...waiting. Remember when windows search worked? Like, you could press the windows key, type what you were looking for and find it? Quickly? Being able to turn the computer on, type in my password and have it be just..ready is so incredibly refreshing. Having…

Rumors on the internets have spoken positively about Opensuse Leap & Tumbleweed, any truth to that?

I don't have a ton of experience with other options, but 2 weeks in and tumbleweed has been pretty plug and play! 0 issues getting my netcore/python/golang/docker dev stack up. I get a weird popping noise in my usb dac at the login screen but that's the only issue I've had so far. Teams screen sharing even works perfectly! I chose it over Ubuntu 20 because I knew I wanted kde and it seems like a first class citizen in tumbleweed, while still being vaguely stable. Not-quite-bleeding edge! I ran freebsd/kde for fun back in the halycon days of lamp stack and gnome never felt...right to me when I would test drive Ubuntu desktop.

Re: MacOS Catalina: Slow by Design?

#566
post #519

Earlier quoted context omitted.

Putting Terminal (and your favorite text editor) in this category and in "Full Disk Access" will change your life.

Yes, falling victim to ransomware is definitely lifechanging if you don’t have good backups.

That is a non-sequitur.

Re: MacOS Catalina: Slow by Design?

#567
post #540

Earlier quoted context omitted.

So since these permissions apply to process trees, what happens if you put launchd in there?

The computer will probably hang while it tries to solve the chicken-egg problem. Isn't launchd Mac's ‘init’? I.e. run before anything else.

Yes, and that's the point — everything you run will theoretically inherit the permission from it.

Re: MacOS Catalina: Slow by Design?

#568
post #437

I'm so confused about the comments here. There are a bunch of people who can't reproduce the slowness at all, but nearly all downvoted or you have to wade through 100's of comments to get to them. The majority of comments are just dumping on Macs, nothing whatsoever to do with the content of the article, and seem to be blindly assuming it's true. And I can't seem to find any substantive discussion of whether this is…

Did you run the test yourself? Why do you assume people are blindly assuming it's true? For me first run was 0.5s, second run was 0.004s, so there's definitely something going on.

I did. It got downvoted with no replies. I don't have any security settings changed or anything. First and second run were both around 0.005s.

That's why I wrote this new comment, in the hopes that maybe it would be seen.

Re: MacOS Catalina: Slow by Design?

#569

Earlier quoted context omitted.

`mkdir -p /opt/nix` assumes that there is a convention, and that this is the correct convention - which may not be the case for every situation, and would result in creating unnecessary nested directories. You could make a more sophisticated installation script that attempts to install Nix into conventional locations depending on the specific operating system - or user input - but if you want a simple catch-all, simp…

> `mkdir -p /opt/nix` assumes that there is a convention A correct assumption on virtually all relevant extant systems... > which may not be the case for every situation In the supposed scenario where the assumption isn't correct, the downside of /opt/nix vs /nix is basically insignificant. What's the overhead of one level of directory nesting, a single extra inode? Big whoop.

And what is the issue with leaving it as `/nix`, which is (was) accessible on virtually all extant systems? Other than "the root folder is special!"

Re: MacOS Catalina: Slow by Design?

#570

Earlier quoted context omitted.

Brew never had this problem because they chose a sane path without corrupting the system directory. It’s a bad design on part of NixOS and one can even say the changes in the macOS were designed to encourage good/sane design.

Nix living at a predefined path is integral to how it works. An executable does not dynamically link to a generic "ncurses" but (via rpath) links to a specific compiled version of ncurses (such as /nix/store/81rb87agmp9cbsvg2xm2n4kp9c6309lv-ncurses-6.2). This is the root of all the benefits of Nix such as being able to install things side-by-side that use different versions of things or upgrade and rollback without p…

The Nix abides.
Post reply on HN