> 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...

That explains why the effects looked so similar in the two...

Never did get into Babylon 5, but SeaQuest, for all its campiness, was my jam briefly in my childhood.

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

It's incredible that it still lives to this day. I remember running it on Pentium-133. The gallery they have there still has showcase renders from 2000s.

yes, you are right ... its been a few years :))

Sounds interesting. What's the title?

Roaring Across the Horizon

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.

Someone might still commit to campaign contributions if it aligns with their philosophy or goals. But I don’t think that’s what is going on here

Wow, that's massive. I guess it's inevitable that a popular piece of open-source software for end-users will be compelled to accrue dependencies due to popular demand for features that require them.

I feel Telegraf made a good compromise: out of the box, it comes with a _ton_ of stuff[1] to monitor everything, but they make it possible to build only with pieces that you need via build tags, and even provide a tool to extract said tags from your telegraf config[2]. But lots of supply-chain security stuff assume everything in go.mod is used, so that can results in a lot of noise.

[1] https://github.com/influxdata/telegraf/blob/master/go.mod [2] https://github.com/influxdata/telegraf/tree/master/tools/cus...

Thanks! That’s an interesting approach. Haven’t seen that before. I think a better approach (in a monorepo) might be to use separate go.mod files for each module, allowing the user to configure only the needed parts separately. But I haven’t seen it used much.

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

Ames sentry coot Amy sent scooter Steamy toe corns A messy cottoner