Pesthuf

No, that's just them patching out a feature it used to have so you buy their newest model instead.

It would certainly help other browsers keep up in performance and battery life if Apple didn’t make all the APIs that allow Safari to stay so far ahead private and undocumented.

I think it makes more sense to use the kernel‘s’s sandboxing utilities (like seccomp, SELinux, namespaces, prctl and eBPF) than to rely on the process to try to isolate itself purely in userspace which will always have holes.

Or a server version. I have an M1 Mac mini as my home server and it really feels like I'm fighting the fact that it's a desktop OS with a GUI and full of components that really, really, really can't deal with being run on a headless system. Not much fun when your super efficient ARM processor suddenly uses 100% CPU for 6 days straight because WindowServer and CoreAudio are having a panic attack due to being unable to find any outputs.

And so much useless crap you can't turn off without disabling SIP, which it doesn't feel like you're meant to, because who knows what daemon will bring down the entire system when another it expects to be there isn't…

Isn’t kqueue pretty much as fast as epoll?

There’s no io_uring, but in practice, almost all servers run epoll anyway, don’t they?

The project says it’s in pre alpha so that’s to be expected

Sending files to another would be easy if only the services that allow doing this - over WebRTC - didn’t sell out to sketchy advertisers constantly. I have to look up which service is still good to use every time.

I don’t even need the features but I’ll probably buy a license anyway. This software is great and I can’t imagine going back to macOS’ built in alt tab or Mission Control.

The only downside is the "this app is recording your screen" notification light that pops up briefly when you enter full screen mode that a native implementation wouldn’t have to deal with. But clearly, Apple has no interest in building one.

I wonder if this has any measurable impact on compile times.

Tell me: why are these algorithms suddenly okay when the victim turns 18?

They are bad for everyone and if you’re willing to regulate them, make them illegal to be used on anyone.

I love how to do anything in this language, you have to fight it with all you have. You have to use features in ways that feel like they were probably never intended to be used in. Everything is just an accident, some random pattern randomly discovered by someone when some typo happened to compile.

I feel like they could do a better job, though. In the postmortems of incidents you often hear it's because some maintainer got hit by the perfect phishing attack at the right time and they got tricked into entering password and TOTP into a phishing site. If that is so, why are we still allowing phishable credentials for logging into package repositories?

Maybe we could add an extension to webauthn that adds a reason to a passkey. Then, the credential manager can warn the user better why deleting the passkey would be a bad idea.

Many such cases