kabdib

After a day of single combat with multimillion-SLOC tangleware, it's fun to work with a system that you can fit in your head

Personally, I don't do much nostalgia. I've built the PDP-11 clones and run v6 Unix again and (o dear lord) compiled world.c with BDS-C on CP/M and realized that the 70s and 80s kinda sucked, and that I really like modern computing

I have seen a pure C/C++ implementation of coroutines (it used setjmp/longjmp, and memcpy to copy stacks in and out of the native arena). Not the most portable of constructions, but it worked absurdly well.

Being able to write "async" code essentially in-line is a superpower.

I've been doing embedded systems in C++ since rocks were young, and this is a great summary of what to avoid.

I would sure love a good coroutine runtime, and first-class support for defer. You can do these manually, but language/toolchain/debugger support is nice to have.

(Pragmatically, I will be retired by the time they would be useful)

"Can I borrow your calculator"

"Sure!" (hands over HP-25C)

<start counting seconds...>

"Hey, where's the equals key?"

I miss my Q/A partner. He was a engineer who gave me feedback on designs and code, helped debug, and I could run the tests he wrote.

It's terrifying without that support. The beancounter level mgt does not Get It that it's cheaper to have this kind of support now than much later in the product cycle.

Lap-insistent cat made it impossible to use a keyboard. I finally bought a desk-height cat "tree" (maybe a shrub...) and put it beside my chair. He'll move to it after some scratching, and he's happier because he can actually nap.

I intend to :-)

Thanks, I was honestly curious. I knew about Infogrames, did not know about the holding company.

"The reward for winning is the opportunity to play again"

I really wonder who "Atari" is these days . . .

Computing hardware that isn't rad-hard is going to have a bad time without a handy atmosphere for shielding.

And hardware that is happy in high-radiation environments is not going to be fast.

> incompetency

"corruption"

I had a QA engineer who gave me feedback on designs, great code reviews, and who wrote tests that I could also run.

It was a partnership. I miss it.

I was hoping for a secret society of volcano watchers, handing down carefully guarded records from generation to generation . . .

("There's nothing written in here, Dad")

> 4. Verify Device Genuineness: Confirm if a phone (new or used) is authentic before purchase.

    DisplayDialog("Yup, perfectly genuine, trust me!");

:-)