Pipewire just works without needing the awfulness of pulseaudio, but there's also "apulse" to shim directly to alsa if you want more like the older behavior. But Pipewire is far more compatible and modern.
After reading this several times, I've tried to identify if your satire is trying to meet the author's satire somewhere over the Atlantic, or if it's aimed at some kind of self-reference or in-joke that I'm just not parsing.
It demonstrates the author's point from back in the 1990s so well, but also makes its own biting social commentary on how often authoritative-sounding language gets weaponized by a majority to dismiss and mock that which they fail to understand.
Impressive level of historical continuity. The dryness nearly threw me.
maybe you are right, quite sure is all 3 things at the same time :) about something that, by my point of view, is -very- easy to understand, but, i know, ymmv.
I feel that in this kind of matter, demonstrations (an others things) are in the eye of beholder, and a language that has a specific weight much greater than what it seeks to represent, set afloat in the sea of life, runs the risk of capsizing and sinking (feel free to laugh here).
it's inevitable and i'm (partially) resigned to the implications it has on whole (modern) life, but anyone who wants to continue to pathologize vivisect and classify human experience is free to do so, but (for me) regarding life, true knowledge comes first over (presumed) academicism
This appears to assume that seeking diagnosis is somehow self-limitation instead of functional troubleshooting.
In practice, understanding one's neurotype can provide the foundation necessary towards addressing friction, dealing with environments developed exclusively for a radically different baseline, and getting the support and care necessary to have a reasonable quality of life.
The alternatives often lead to massive dysfunction, especially since it compounds with systemic gaslighting and being told that the hell you're experiencing is normal and that it's a character flaw to have any difficulties or differences.
The satire of ISNT frames the very real negative framing that was already deeply pervasive 28 years ago.
Given the author of the page, I would completely agree with her assessment-- especially given what's happened in the ~28 years that have passed since the site went up.
You "instantly losing respect" because an autistic person dares value her own mind when others pathologize is part of the point of why it was posted. The satire wasn't there to seek approval in 1998 in the first place, amazingly.
Reading `hol.mm` made me grateful for Lean 4's general purpose programming.
I get the string substitution focus, and respect what metamath has achieved, but the bridge Lean 4 makes wrt systems programming has left quite an impression.
I wonder how many people mostly see mathlib4 & think that's the one prescribed route (ala Rust) when one of Lean 4's under-documented super powers is the ease with which you can roll your own light-weight low to zero overhead domain-specialized constructs that are also trivial to prove because of the dependent type system.
(Perhaps more for verified functional systems than deep math.)
Linux is not an official GNU project. You can tell because GNU created their own soft fork, Linux-libre, to cut out any blobs or nonfree bits (mostly firmware AIUI). HURD is a GNU project outright. Although, ironically, I'm pretty sure its microkernel nature means it'd be a lot easier to maintain a proprietary driver for HURD than Linux. Life is strange sometimes.
IMO it's the same problem with Rust. LLMs are trained on vast quantities of code that violate Rust soundness in safe code.
LLMs are prediction engines: you can move the needle (heavily) on the predictions from lazy to correct by construction, but the defaults even on high end models like Opus are always riddled with shortcuts.
LLMs can produce coherent & safe Rust 1.92, LLMs can produce coherent Zig 0.16, but that's dependent on in context learning & instruction following.
> that's dependent on in context learning & instruction following
Not just that. For Rust in particular, since unsafe code is uncompilable code (unless explicitly marked "unsafe"), the LLM is essentially forced to continue iterating even if the code already works but is unsafe, until it finds an implementation that's both correct (per the spec) and safe (per the compiler). That's the difference from Zig, where "make the code safe" is essentially part of the spec, and so may be missed by the LLM and not be discovered by a human until there's an observable runtime issue, or CVE.
