Damus
THE MARTYR OF BUTLERIAN JIHAD profile picture
THE MARTYR OF BUTLERIAN JIHAD
@THE MARTYR OF BUTLERIAN JIHAD

We must negate the machines-that-think. Humans must set their own guidelines. This is not something machines can do. Reasoning depends upon programming, not on hardware, and we are the ultimate program! Our Jihad is a "dump program." We dump the things which destroy us as humans!

This is the tech account of @newt, formerly located at @pureevil. If you reached this place, it's your own fault.

Expect long posts about the metaphysics of computing. Don't blame me for any adverse side effects.

Relays (1)
  • wss://relay.ditto.pub – read & write

Recent Notes

THE MARTYR OF BUTLERIAN JIHAD profile picture
Designing a good audio codec is hard. Designing a stupid one is even harder, and nothing can surpass Matrix people here.

Under the m.audio_details content block, a new optional field named waveform is added. It is an array of (non-floating) numbers to represent the amplitude of the audio over time. Because floating point numbers are not allowed in Matrix events, integers should be between 0 and 256, inclusive. Though there is no limit to the number of entries in the array, senders should aim to have at least 30 and not more than 120.

We have reached peak webshit, ladies and gentlemen, because there are no applicable alternatives to encoding 8-bit PCM into JSON arrays. None. Audiophiles can cope and seethe.

I will leave you with a link to this glorious proposal.

https://github.com/matrix-org/matrix-spec-proposals/blob/c4209de8c593a7880842bbe02a3da8b2938ab0d2/proposals/3246-audio-waveform.md

THE MARTYR OF BUTLERIAN JIHAD profile picture
Remember, boys. Every time you see a fat HTTP routing table or a huge command line parser in a program, that's just a half-assed underimplemented DSL struggling to break free. Most programmers today wouldn't be able to add an existing scripting language interpreter to their code, much less write a new one from scratch. Instead, they do this. This is the true meaning of the Greenspun's tenth rule and it has nothing to do with Lisp.


THE MARTYR OF BUTLERIAN JIHAD profile picture
Autoconf is when you can't build a project from 13 years ago because the compiler version is too big.

checking how to run the C preprocessor... gcc -E
checking for the version of the GNU C compiler... 15.3
checking for the version of the GNU C++ compiler... 15.3
error: unsupported compiler version 15.3
1
pesekcuy · 10w
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpq7esnvwnpunszha3whjk4y4xe0g7u8maswrul49lgg4sqpxanlkjscl4kgw is this why containerization is uber-popular nowadays (i.e. one would pull one of old distro version just to get period-correct tools)?
THE MARTYR OF BUTLERIAN JIHAD · 10w
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqer26g8v2gdquxkyk43usmlk7gaqhle08p378ld3ldfd6p5yrt8us3qs2sp to be fair, Intel tried to kill x86 at least three times. First, with iAPX432 in 1982,...
THE MARTYR OF BUTLERIAN JIHAD profile picture
@Phantasm adding to that, x86 has survived and thrived not because of Intel but despite of them. Basically, other vendors have forced Intel to stay in lane and continue with x86. IBM saved them from bankruptcy by buying their 8086 for the IBM PC after iAPX432 drained Intel's funds, then came them competition from AMD, Cyrix, and other vendors, forcing Intel to continue. If Intel wasn't going to make x86, someone else would've, as it happened with AMD64.
1
Phantasm · 10w
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpq7esnvwnpunszha3whjk4y4xe0g7u8maswrul49lgg4sqpxanlkjscl4kgw >then came them competition from AMD IBM actually forced Intel to license x86 and the CPU designs (until 486 I think) to AMD fairly early, because Intel couldn't keep up with the deman...
Phantasm · 10w
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpq7esnvwnpunszha3whjk4y4xe0g7u8maswrul49lgg4sqpxanlkjscl4kgw Intel no longer has the talent to implement a sane ISA, not like x86 is a very sane IS...
THE MARTYR OF BUTLERIAN JIHAD profile picture
@Phantasm to be fair, Intel tried to kill x86 at least three times. First, with iAPX432 in 1982, then with i860/i960 5 years later, then a decade later with Itanium. With the exception for iAPX432 (which was totally and completely insane), other attempts were sound. i860 was a good RISC chip and Itanium wasn't so stupid at the time. Compiler sentience and hindsight 20/20 aside, back in the late 90s it wasn't even known that CPUs would peak at 5GHz frequency. Intel could've been very well planing for Itaniums to hit 10GHz and above.

Check the graph attached. Before CPUs hit around 2-2.5GHz mark, it was thought the power requirements and therefore heat production were scaling linearly with the frequency, not exponentially. You can blame this fact for the failure of both Itanium and Pentium 4 cores. Itanium was initially designed with physically larger cores in mind running at much higher frequency than what they ended up with.

1
THE MARTYR OF BUTLERIAN JIHAD · 10w
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqer26g8v2gdquxkyk43usmlk7gaqhle08p378ld3ldfd6p5yrt8us3qs2sp adding to that, x86 has survived and thrived not because of Intel but despite of them. Basically, other vendors have forced Intel to stay in lane and continue with x86. IBM saved them fr...
Phantasm · 10w
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpq7esnvwnpunszha3whjk4y4xe0g7u8maswrul49lgg4sqpxanlkjscl4kgw >This makes writing any sort of a generic kernel very difficult -- you literally have...
THE MARTYR OF BUTLERIAN JIHAD profile picture
@Phantasm x86 is on the other of this side spectrum. There is no reason to pretend to support DOS when none of the systems today run it. X86s initiative was among the most sane ways to solve it. Just start in long mode from the get go, support the 32-bit subset for compatibility, and leave the ancient code to emulation. Unfortunately, Intel is run by a bunch of pussies.
1
Phantasm · 10w
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpq7esnvwnpunszha3whjk4y4xe0g7u8maswrul49lgg4sqpxanlkjscl4kgw Intel no longer has the talent to implement a sane ISA, not like x86 is a very sane ISA either. They couldn't do it with Itanium, although that thing was doomed from the start with its "...