Live data from Hacker News

MacOS Catalina: Slow by Design?

sigpipe.macromates.com

771–780 of 1001 posts

Re: MacOS Catalina: Slow by Design?

#771

Earlier quoted context omitted.

Another way to look at it is that Apple is making it harder to run the system in an insecure fashion. You may not agree with that decision, but I certainly appreciate how Apple is looking out for the safety and security of the user. Tangent: as much as some developers hate that the only way to distribute apps for the iPhone is through the App Store, as a user I consider that walled garden of apps to be a real securit…

Who is this Gruber person you quote and why is he relevant here?

He's the person who made the markdown format, which you've used as your username.

Other than that, he's mostly known for writing and talking about Apple.

Re: MacOS Catalina: Slow by Design?

#772
post #14
post #3

If Microsoft wasn't doing ever worse privacy things with Windows I'd seriously look into switching away from Mac OS given the ever growing issues it's been having with every release.

At least 10.14 is supported for now. It's really frustrating to see Apple make all these poor decisions and they almost never are willing to admit their mistakes and go back. In the rare case when they do (e.g. butterfly keyboard, Mac Pro), it takes them years to turn around.

> it takes them years to turn around.

or until they need something to throw out for investors. "dark mode" did not come about because of a technical breakthrough

Re: MacOS Catalina: Slow by Design?

#773

Adding network calls to syscalls like exec() is utterly insane. This road can lead to bricked laptops where you can't run anything to fix it (imagine an unexpected network error that the code doesn't handle properly). And crackers will just use ways to overwrite running instruction text to avoid the exec(). The comments on the article are annoying: it good that there's a mini way to reproduce, but please, use some fu…

The kernel sources are available. https://opensource.apple.com/source/xnu/xnu-6153.81.5/

…with everything to do with the sandbox left out.

Re: MacOS Catalina: Slow by Design?

#774

Earlier quoted context omitted.

I call this 'Outsourcing the cost of development to the user'... Getting knowledgeable people costs money so we build more abstractions that lower the cost of development and pass the costs of development from the company to the user in the form of requiring more hardware to do the same thing. How come I need 16Gb of RAM these days when 8Gb did it yesterday? How come my phone needs 4Gb of RAM while my 2012 tablet had…

The reason is very simple: developers don't want to develop anymore, they just want to offload real programming to third party libraries, where what used to take 100 lines of code to accomplish will take 10K or more (because, obviously, the library will do the most general version of what it wants to do). All this is considered "good development practices", which means that programs will inflate to take whatever memo…

and is absolutely encouraged by google and amazon, as delivering that bloat makes them money

Re: MacOS Catalina: Slow by Design?

#775
I intend to stay on Mojave for as long as possible, but I am curious to try out Catalina. I believe it is easy enough to install Catalina on an external SSD. My concern is whether this would be safe enough and if my computer would remain unmodified (e.g. could there be changes to firmware settings or firmware updates?)

Re: MacOS Catalina: Slow by Design?

#776

Adding network calls to syscalls like exec() is utterly insane. This road can lead to bricked laptops where you can't run anything to fix it (imagine an unexpected network error that the code doesn't handle properly). And crackers will just use ways to overwrite running instruction text to avoid the exec(). The comments on the article are annoying: it good that there's a mini way to reproduce, but please, use some fu…

Well NFS and SMB exist, you can exec() on such mounts.

Re: MacOS Catalina: Slow by Design?

#777
post #597

Earlier quoted context omitted.

Wouldn't a sandboxed Zoom downloaded directly from them be equally secure?

Yes, but would a typical user know or care if the app they downloaded from a web site was sandboxed and would otherwise have been approved by the App Store if it was submitted there? And if not, how could someone like John Gruber make that claim of safety on anything other than iPhone and iPad? Taking the Zoom example on a parent thread above, look at what happens when you’re installing a Zoom client on the Mac witho…

This just doesn't seem like a terribly difficult problem. Web browsers have figured it out. Any webpage that isn't served over SSL says "Not Secure" right at the top.

I can think of a dozen ways which the OS could prominently display "Not Secure" for non-sandboxed applications, in a way that wouldn't preclude or hinder users from using such applications if they really wanted to.

Re: MacOS Catalina: Slow by Design?

#778

Earlier quoted context omitted.

I don't think the people at Apple are actively trying to make non-App Store apps unusable because they want to make more money from the App Store or anything. It's just that they want code to pass through them, and as a by product making code that has been vetted less or does things that could potentially be abused is made more annoying to run. Such a change is divisive, as you may have guessed.

That vetting will come at the cost of 30% of money paid for your software and any money earned within the software.

[deleted]

Re: MacOS Catalina: Slow by Design?

#780
post #713
post #685

Earlier quoted context omitted.

The problem is that there is more than one market here. There is a general market where people love the vendor looking after their security and doing things for them, and there is a pro/hacker market where people want to control things themselves and dont want a lot of this stuff.

This. Yes the option of a walled garden is a great thing and I wouldn't recommend anything but an Apple device to my non-technical relatives. But if Apple also wants to make the $$ that comes from selling "pro" gear, they need to stop relentlessly consumerizing and turning OS X into iOS. I don't think they realize the level of ill will they are engendering in the developer/pro market. Perhaps it's time for a "Pro" an…

I've been doing software development on macOS/OS X for quite some time now and the consumerization aspects don't bother me. I install almost everything I need via Homebrew, from software libraries to desktops apps, and the fact that there's an App Store isn't particularly relevant (although I do use it for consumer apps now and then).

I'm trying to think of how macOS is so different from 10/20 years ago. What's missing? What can I not do now? Maybe my brain has just been consumerized and I forgot something important.

I was going to switch to Linux 10 years ago when people were talking about the iOSification of OS X back then, but that never happened.

Post reply on HN