lantastic

On topic of fear of nuclear war:

After reading Daniel Ellsberg's The Doomsday Machine, I'm surprised we as a species are still around.

On Linux, you could create a udev rule to give you permissions on any attached raw disks (if you feel particularly adventurous).

What's the license for ffs?

Stunts was the greatest! You could make your own tracks, save replays and (IIRC) even resume gameplay from any point in the replay. My very favorite game of all time.

.. and have been for a long time. I don't remember the last time I reached for a hand-written SDK for a HTTP API. It's always some codegen affair. But out-of-the-box experience for many codegen tools is that the generated API ends up being very far in usability from what you'd write by yourself.

The API consumer should be able to adapt the binding to their needs and idioms instead of relying on behavior encoded in a pre-built SDK. The ability to do that with specific codegen tools (e.g. swagger-codegen, go-swagger) is pretty high-barrier. Oagen-emitters looks like something that addresses that gap.

Mine too! Another Lightwave-produced show I loved was Space: Above & Beyond.

> if i remember it correctly: they used a software called "lightroom"

Afaict, it was Lightwave3d, that I just learned still lives to this day. Last release June 11 2025. Also used to make SeaQuest :) Oh, the memories...

Sounds interesting. What's the title?

It is subject to legislation and certification, but it's harder to lobby when you can't privatize the direct costs. Still, scams are common (e.g. inflated medical equipment costs). I guess hustlers gonna hustle in any system.

Others pointed plenty of arguments, but the ones I find most compelling (not necessarily useful in this context) are:

- you can serve any number of disjoint websocket services via same port via HTTP routing - this also means you can do TLS termination in one place, so downstream websocket service doesn't have to deal with the nitty-gritty of certificates.

Sure, it adds a hop compared to socket passing, and there are ways to get similar fanout with TCP with a custom protocol. But you need to add this to every stack that interacting components use, while websockets libraries exist for most languages that are likely to be used in such an endeavor.

Sure, socketpairs on Linux.

Care to elaborate?

My cynical take is this is regulatory capture on part of the most lucrative tech sector in the next few years, in return for campaign contributions.

In every program that uses a particular feature from the stdlib. Given the same feature, I tend to trust stdlib more than some rando project. And if you don't trust the stdlib, why would you trust the compiler?

comatose sentry

necessary motto