Earlier quoted context omitted.
Any distro in particular you'd recommend?
The trick is to go all-in on KDE if you want that Windows feeling where things just work.
And in that case the distro choice should be KDE Neon.
MacOS Catalina: Slow by Design?
821–830 of 1001 posts
Re: MacOS Catalina: Slow by Design?
#822Earlier quoted context omitted.
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 missi…
Do you write much system-level software? I feel like Apple's changes don't affect the XCode crowd much - but under the hood, things are slowly getting worse for command-line developers. How about when Apple removed /usr/include in its entirety from Mojave? Or when they decided to make the root filesystem read-only? Or when they removed the ability to permanently disable the "only run verified apps" option? Or when th…
I feel everything you say, and still don't see a better alternative. They're just too good at the hardware and integration.
Re: MacOS Catalina: Slow by Design?
#823Earlier quoted context omitted.
Here's some shell script to use a random file name and have friendlier output. RAND_FILE="/tmp/test-$RANDOM.sh"; time_helper() { /usr/bin/time $RAND_FILE 2>&1 | tail -1 | awk '{print $1}'; } # this just returns the real run time echo $'#!/bin/sh\necho Hello' $RANDOM > $RAND_FILE && chmod a+x $RAND_FILE; echo "Testing $RAND_FILE"; echo "execution time #1: $(time_helper) seconds"; echo "execution time #2: $(time_helper…
Huh this is crazy. 2 seconds is way slow and this shouldn't involve any network activity. Seems like a real problem.
He/she added an artificial network latency/delay into the config, just like they describe. That is the reason for the delay. It is made artificially long on purpose.
Re: MacOS Catalina: Slow by Design?
#824If microsoft was doing this there'd be a riot but since it is Apple but will rationalize this bad behaviour and say it is for the best.
Re: MacOS Catalina: Slow by Design?
#825Earlier quoted context omitted.
> Curious: what have you tried? People who use "Linux" as a catch-all in terms of UX usually have only tried a single distribution with a single desktop environment. Yup. You've just described a disaster. How many permutations of x must a user try before finding a good UX?
Mac is a BSD. OpenBSD exists. FreeBSD exists. NetBSD exists. Because there are at least four BSDs, Mac therefore isn't good. Do you see how ridiculous applying that logic to any operating system is? Linux isn't a disaster. It's a kernel. There are Linux distributions with great user interfaces and great UX, developed by people who are great at it. There are also distributions that aren't.
> Do you see how ridiculous applying that logic to any operating system is?
Somehow, when you ask a person about PC or a Mac, the answer is: Windows or MacOS, and then the discussion is about their quirks, or advantages, or deficiencies.
You ask about Linux, and this is what you get:
> Linux isn't a disaster. It's a kernel. There are Linux distributions with great user interfaces and great UX
So, once again: which one of the hundreds of permutations of x has a great UX?
Re: MacOS Catalina: Slow by Design?
#826Earlier quoted context omitted.
> The existence of a distro I don't like doesn't degrade my experience using a distro I do like. The problem under discussion here is not that of using a distro you like, but finding a distro that you like.
If an icecream shop only has one flavor, I might get lucky and discover it's the flavor I like. But more likely, I'll just be screwed and have to settle for something I don't like. Only an icecream shop with variety can hope to give the most amount of people an optimal experience.
Unless the ice cream shop provides you with hundreds of flavours, 90% of which are nearly indistinguishable from each other. And hardly anyone on this planet can answer a straight question of "Which flavour is good".
Re: MacOS Catalina: Slow by Design?
#827Earlier quoted context omitted.
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 missi…
Do you write much system-level software? I feel like Apple's changes don't affect the XCode crowd much - but under the hood, things are slowly getting worse for command-line developers. How about when Apple removed /usr/include in its entirety from Mojave? Or when they decided to make the root filesystem read-only? Or when they removed the ability to permanently disable the "only run verified apps" option? Or when th…
> Did you know that Apple will soon be using zsh for /bin/sh? Without much regard to how many shell scripts have a #!/bin/sh hashbang and some bashisms in them? You can call those scripts buggy or poorly designed if you want - but they're plentiful and widespread, and will be broken so that Apple can steer clear of GPLv3 code. All so that they can block you from modifying your OS installation. MacOS was a Unix nerd's dream 10 years ago
Yep. Sorry. I’m struggling to connect “Unix nerd” to “thinks /bin/sh and /bin/bash are the same”, especially as that’s very much a Linux distro created problem, and (the clue’s in the name) Linux Is Not UNix.
Re: MacOS Catalina: Slow by Design?
#828It seems like there is a lot of confusion here as to whether this is real or not. I've been able to confirm the behavior in the post by: - Using a new, random executable. Even echo $rand_int will work. Edit: What I mean here is generate your rand int beforehand and statically include it in your script. - Using a fresh filename too. Just throw a rand int at the end there. e.g. /tmp/test4329.sh I MITMd myself while rec…
It's called lockdown for a reason. Apple was just the very first to implement centralized binary blacklisting, revocation. They call it notarization. Problem is, that they did it unannounced. There must be really some weird stuff going on in those managers heads. How can they possibly think to go away with that?
Command line apps aren't affected by Notarization.
If you're compiling something yourself, the compiler won't put a quarantine bit on it and it will execute fine. Same with homebrew/friends.
Scripts don't need to be signed. There is something else going on here.
Re: MacOS Catalina: Slow by Design?
#829It seems like there is a lot of confusion here as to whether this is real or not. I've been able to confirm the behavior in the post by: - Using a new, random executable. Even echo $rand_int will work. Edit: What I mean here is generate your rand int beforehand and statically include it in your script. - Using a fresh filename too. Just throw a rand int at the end there. e.g. /tmp/test4329.sh I MITMd myself while rec…
God, this shit makes me laugh. Why are they doing this.
But from Edit2: Your hash is some sort of base64
let str = Then we see weird random gaps in the alphabet used, not so weird, because not every character will be used in every string:
Prelude Data.List> map head $ group $ sort $ str
"+0246789=ABCDEFGIKLMOPQRSTUVXYZ_abefghiklmpstuwxyz"
Prelude Data.List> let xs = "+0123456789=ABCDEFGHIJKLMNOPQRSTUVWXYZ_abcdefghijklmnopqrstuvwxyz"
Prelude Data.List> length xs
65
Re: MacOS Catalina: Slow by Design?
#830It seems like there is a lot of confusion here as to whether this is real or not. I've been able to confirm the behavior in the post by: - Using a new, random executable. Even echo $rand_int will work. Edit: What I mean here is generate your rand int beforehand and statically include it in your script. - Using a fresh filename too. Just throw a rand int at the end there. e.g. /tmp/test4329.sh I MITMd myself while rec…
Here's some shell script to use a random file name and have friendlier output. RAND_FILE="/tmp/test-$RANDOM.sh"; time_helper() { /usr/bin/time $RAND_FILE 2>&1 | tail -1 | awk '{print $1}'; } # this just returns the real run time echo $'#!/bin/sh\necho Hello' $RANDOM > $RAND_FILE && chmod a+x $RAND_FILE; echo "Testing $RAND_FILE"; echo "execution time #1: $(time_helper) seconds"; echo "execution time #2: $(time_helper…
I tried just blocking "api.apple-cloudkit.com" with /etc/hosts. This reduces the delay but doesn't eliminate it. A connection attempt is still made every time. (I don't recommend making this change permanent. Just give your terminal app the "Developers Tools" permission instead)
After blocking that domain I can see that tccd and syspolicyd are logging some error messages to the console related to the failed connection. I don't recommend blocking because my guess is that'll put syspolicyd/tccd in some unexpected state and they'll repeatedly keep trying to make requests.
Try this for watching security related console log messages:
sudo log stream --debug --info --predicate "processImagePath contains 'tccd' OR processImagePath contains 'syspolicyd' OR processImagePath Contains[c] 'taskgated' OR processImagePath contains 'trustd' OR eventMessage Contains[c] 'malware' OR senderImagePath Contains[c] 'security' "
syspolicyd: cloudkit record fetch: https://api.apple-cloudkit.com/database/1/com.apple.gk.ticket-delivery/production/public/records/lookup, 2/2/23de35......