A reminder: Google added support for and then subsequently dropped JPEGXL support in Chrome. Fuck Google.

Type-safe lipstick :)

To offer a differing opinion, why is null helpful at all?

If you have data that may be empty, it’s better to explicitly represent that possibility with an Optional<T> generic type. This makes the API more clear, and if implicit null isn’t allowed by the language, prevents someone from passing null where a value is expected.

Or if it’s uninitialized, the data can be stored as Partial<T>, where all the fields are Optional<U>. If the type system was nominal, it would ensure that the uninitialized or partially-initialized type can’t be accidentally used where T is expected since Partial<T> != T. When the object is finally ready, have a function to convert it from Partial<T> into T.

With powered hubs and balanced tree topology, you can split a single root controller into 4⁵ endpoints. Your motherboard being able to support that many devices and the shared bandwidth might be a problem, but it’s theoretically possible to survive off of a single USB port.

The problem is that they’re trying to frame it as a better replacement for sudo when it’s really not.

In some respects, it’s safer by not using a setuid binary. In other respects, it massively increases the surface area by relying on the correctness of three separate daemons: systemd, dbus, and polkitd. If any one of those components are misconfigured, you risk an unauthorized user gaining root privileges.

With sudo, the main concern is the sudo process being exploited through memory safety bugs since it runs at root automatically.

Don’t get me wrong, sudo has a lot of stupid decisions and problems. There’s a ton of code in sudo for features that almost nobody uses, and there’s bound to be bugs in there somewhere. It needs to be replaced with something simpler, but run0 is not that.

A better implementation than run0.

If you’re willing to admit that you’re denigrating an operating system for having the same flaws as the one you prefer and are being a massive hypocrite in doing so, sure.

You’re thinking of operating systems that give unrestricted access to all parts of a computer that aren’t memory or the camera. That would everything¹, actually.

¹ There’s also Linux with properly-configured SELinux, but good luck with that on a distro that isn’t focused on opsec.

If the school has a zero tolerance policy, there’s nothing to lose. If you’re getting punished either way, you might as well take preventative measures for the future.

Full Self-Driving

Any idea that comes out of that prick’s mouth is snake oil if we’re going to be truthful about it.

50ms of latency in a first-person perspective. That’s a great way to exclude people with motion sickness from playing games.

Capitalism bad. Support Epic Games instead. /s

If you can find the download for GitHub Enterprise, Ruby Concealer is little more than an XOR cipher. Make of that what you will.

You can self-host GitHub. It takes around 32 GB of memory, however.

The “++” in C++ stands for extra verbose.

You don’t?

They do, but then go on to contradict themselves:

On a platform level, we believe GTK should stop forcing a single stylesheet on all apps by default. Instead of apps having to opt out of this by hardcoding a stylesheet, they should use the platform stylesheet unless they opt in to something else. We realize this is a complicated issue, but assuming every app works with every stylesheet is a bad default.

Emphasis theirs. They are explicitly saying that their belief is for applications to use the [original GNOME] platform stylesheet by default, and making the ability to reskin an application opt-in by the application [developer]. I agree that a one size fits all stylesheet is bad, but the solution should be to provide more granular selectors at the toolkit level to allow themes to fix what they break, not force defaults onto everyone.

I’m in a small minority, but their ring0 anticheat isn’t helping with that.

Also, with Rust, if you’re optimizing for performance and not legibility, it’s actually pretty important to not prematurely optimize. Its type system gives the compiler a lot of information to work with, and it does a really good job finding places where code can be optimized.

What might make sense in some languages, such as trying to cache small strings instead of recomputing them, can actually hurt performance by preventing the compiler from using certain optimizations.

Allison from The Breakfast Club. I can fix her.

^{I’m not a teenager anymore however, so yeah, no thanks, Chris Hansen. I’ll stand.}