The builtins don’t even compile in these examples. This is 2 years out of date at least.

I don’t think I’m exceptional at all. I was always behind and that probably reflected pretty poorly on me. But all it took to teach was preparing interesting examples and then spending time with subgroups and individuals.

I bet a lot of people think I’m catastrophically wrong, probably just got lucky.

https://en.wikipedia.org/wiki/Asynchronous_Transfer_Mode

For others who did not get the joke, Kindall was kind of a big deal:

https://computerhistory.org/blog/fifty-years-of-the-personal...

Some confuse this with LDS-OS, which makes the user weirdly and unquestionably `nice` by only accepting inputs from protected mode.

Arenas are great for avoiding allocations per tick/request/frame/layer. No symmetric free() to bracket lifetimes! They have a purpose, and we always knew that.

But by definition, your program is over-allocating as a tradeoff. Makes a ton of sense in certain use cases. However, we didn’t invent garbage collection and borrow-checking and realloc() just to publish papers ;)

Half of my time programming zig is spent considering allocation strategies. That’s a feature. “Where are the bytes?”

If only the guy who was destined to close a disk operating system deal with IBM hadn’t been goofing around with his plane that fateful day.

We would all be using lisp machines, running smalltalk on microkernels that put the HURD to shame. Just imagine: instead of backslashes and drive letters, we’d have parens. Endless, syntactically-valid parens.

Or CP/M, probably that. But can it run doom?

“Have a pint, stay a spell. It’ll be our cozy little secret, mate.”

I had heard it a lot in punk and pop-punk to create swells. I improvised my still-favorite solo that day.

If a loom had a jump instruction, would you change your mind? (They did not.)

And yet we still have IDE defaults of 80 characters because of FORTRAN punchcards. That’s the heritage being invoked.

EDIT: I think all of these early devices also helped us to understand how to build multiplexers, which are the basic building block of any CPU. Given this instruction, I do a different thing.

(Just experienced this multiple times in Phoenix. It’s impressive at navigating and braking, but not rational planning or flocking.)

- Helmetball

- Gridiron

- Scrimmage

- Brain-B-Gone

- Turnover (if you are Bo Nix)

- Fumblederp

- Kicks and Giggles

So. Am I the only one who kind of likes watching the commercials more than the game when my family or friends make me watch football? They are entertaining when you only see them every now and then.

Now, banner ads are not in the same category. But above is a real use-case for enjoyment of ads.

I still write my code in all the places I care about, but I don’t get stuck on “looking up how to enable websockets when creating the listener before I even pass anything to hyper.”

I do not care to spend hours or days to know that API detail from personal pain, because it is hyper-specific, in both senses of hyper-specific.

(For posterity, it’s `with_upgrades`… thanks chatgpt circa 12 months ago!)

> There should be a TaskManager that stores Task objects in a sorted set, with the deadline as the sort key. There should be methods to add a task and pop the current top task. The TaskManager owns the memory when the Task is in the sorted set, and the caller to pop should own it after it is popped. To enforce this, the caller to pop must pass in an allocator and will receive a copy of the Task. The Task will be freed from the sorted set after the pop.

> The payload of the Task should be an object carrying a pointer to a context and a pointer to a function that takes this context as an argument.

> Update the tests and make sure they pass before completing. The test scenarios should relate to the use-case domain of this project, which is home automation (see the readme and nearby tests).