Scuds

Oh yes, apple hardware continues to improve and M4 pro still the single threaded champion of anything under 300 w.

FWIW - last stage where the binary is produced takes the longest and is single threaded and that's the largest difference between release and debug.

I have a mac m4 pro and it's 2 minutes to compile all of Deno, which is my go-to for bigass rust projects.

```

> cargo clean && time cargo build

cargo build 713.80s user 91.57s system 706% cpu 1:53.97 total

> cargo clean && time cargo build --release

cargo build --release 1619.53s user 142.65s system 354% cpu 8:17.05 total

```

this is without incremental compilation. And it's not like you have to babysit a release build if you have a CI/CD system

I figured that articles like folklore are like an amusing movie file (say someone chopping a skin of a watermelon) that's repeatedly being passed around reddit.

management could have decided on a process change. Simple as that.

I get the sentiment though, "He blew management's mind so much they made an exception for him".

But, Folklore.org is a bit less onanistic than ESR's jargon file.

"Seems like a waste of effort" in a vacuum yes, but

1 - GNU utilities is ancient crufty #IFDEF'd C that's been in maintenance mode for decades. You want code to handle quirks of Tru64 and Ultrix? You got it.

2 - Waving your hands around 'the community will take care of it' is magical thinking. C developers don't grow on trees. C tooling is kinda weird and doesn't resemble anything modern - good luck finding enough VOLUNTEER C developers to make your goals happen.

you're just an end user, you don't have to maintain the suite.

In OSS every hour of volunteer time is precious Manna from heaven, flavored with unicorn tears. So any way to remove Toil and introduce automation is gold.

Rust's strict compiler and an appropriate test suite guarantees a level of correctness far beyond C. There's less onus on the reviewer to ensure everything still works as expected when reviewing a pull request.

It's a win-win situation.

there's a reason why people remember kent state.

there were crematoriums falling apart because of constant use. Morgues overflowing with coffins.

Three of my direct coworkers died from covid. One guy didn't get his sense of taste back for a year.

People just gasping to death in their bedrooms waiting for things to improve and only going to the overloaded ER when it's too late.

I'm an asthmatic, I've been close to that feeling where sub 90% oxygen saturation made me feel like death. Anything like 80% your lungs start to fail. You're dead in a hurry.

jesus, when's 4chan going to turn up here?

I'm kind of surprised that after all these years TF2 and Source are still separate entities. Like, is there any TF2-only code in Source that only runs if TF2 is the current mod?

I thought Monolith worked on doom95.

"3. your green field project growing into legacy project."

You do all this upfront design about how it's going to work and then "Oh god there's so many splinters and sharp corners, it's only getting worse and every new team onboarded to the framework needs to have their hands held, and management won't allocate time to address the tech debt."

that's one ep that sticks out in my mind - hardware hacking to dump a 2600 cartridge and build homebrew development hardware and then reverse engineering to figure out what's what.

Also the subtle flex of making the Donkey Kong girders on an angle when the 2600 is a 'race the beam' system where each scanline must be computed. Even modern homebrew remakes of Donkey Kong on 2600 have horizontal girders.