Notices by 🌈 A. Wilcox delicately (awilfox@mst3k.interlinked.me), page 8

I'm listening to 1979; it seems oddly appropriate given my situation, and the situations of those I care about

🎵 And we don't know
Just where our bones will rest
To dust, I guess

@Elizafox sarcasm? or real?

You're Elizacorn so like I can't tell. 🌽

@adfeno @luciferMysticus I think the loss of Type 1 fonts matters more. A lot of older typefaces are only available as Type 1, and I've never seen a decent conversion package that didn't subtly make it look worse.

Manually redrawing glyphs for OTF isn't fun 💔

@Elizafox dude I remember changing my cousin's diapers. She's fucking ENGAGED

@Elizafox proud of you. All of you, tbh. 💖

@plausocks then I committed a felony just walking to my car

@luciferMysticus #adelie when @alyx is on

@IceWolf when devs choose *different things*, it results in everything being unusable because nothing interops and you have 100 copies of Gtk and Qt.

When devs all choose the *same thing*, you get a monoculture and new, better ways of doing things will never be developed or tested unless it is held back being compatible with whatever bad idea is popular right now.

This is why we HAVE distros.

@IceWolf "outside a distro".

Yes, if your distro doesn't offer a package, you should be building it from source. (And if you don't trust distros, that's what LFS/Gentoo is for.)

Consider: I have no x86. ARM and PPC only.

Also consider things like service supervisors (systemd, rc, s6, ...), sound systems (ALSA, Pulse, sndio), toolkit versions (Qt 5.13 is broken on my PC, but I need a specific patch from it to fix a bug)...

Letting devs choose this is always bad

@sroracle energiser keeps going and going

I have a DVD here that smells like burnt electronics.

Literally the disc itself smells like it.

Still plays fine...?

@Aerdan @ullbeking I didn't count Bionic here because it's only used in Android and isn't designed to be used publicly.

I similarly didn't include the Fuchsia libc (which is a badly maintained fork of musl) for the same reason.

This new proposed one would be in LLVM and explicitly for use in a wide array of software, not just targeting one experimental OS (or the innards of a mobile OS).

@ullbeking my title was a bit tongue in cheek but it's very concerning to me that Google wants to assert itself as a libc vendor

Think about what they've done to JS. First they made a ECMAScript impl (V8), made it fast and standards compliant, made everyone use it, now when they make a new custom JS API everyone has to implement it or risk not being able to run the latest google sites.

Now consider what they could do to libcs with libvpx, WebP, Chromium, Go, etc.