I agree, and to solve this problem I say we nationalize and socialize healthcare to provide it to all citizens free of cost just as they do in many African and other countries. This will remove the need to have any healthcare CEOs entirely.

Nope, I'm saying pharmaceutical companies don't need to be capitalist and profit driven.

OK, but they still need to be run by someone, no?

Distributed RPC, i.e. dbus over the network, is an incredibly complex and still basically unsolved problem. To really do it right and guarantee correctness across systems (which may be in different states of working or failed!) you need a perfect message queue with exactly once delivery... but in practice implementing that is incredibly storage intensive (you'd have to store every message forever). You're basically asking for something as complex and difficult to run as kafka--it's not as simple as just send dbus messages over a network socket.

Systemd doesn't remove any control, and in fact gives a lot of extra control over things like process dependencies, environment, etc. The big complaint people had/have really just boils down to someone moved the cheese--your bespoke and brittle startup scripts are now declarative config files. Some people had to learn something new and that _really_ angered them.

Unix domain sockets or FIFOs could be an alternative, but you'd have to do all kinds of complexity to support pub/sub style many to many communication over them (which is what dbus effectively does for you).

It depends if you are a fan of a centralized server vs decentralized communication.

Anyway, all the complexities of using sockets/FIFOs could be hidden inside libraries.

Once you hide the complexities of using sockets you just end up with some sort of message bus that each application connects to and registers an ID with... which is essentially what dbus is.

I specifically said libraries (as opposed to a centralized service).

Dbus doesn't have anything to do with systemd FYI. It's a communication bus for processes to talk to each other through structured RPC messages.

From the article:

> udev and dbus are forced dependencies.

Not true (although maybe in the systemd world?). udev just populates /dev dynamically (rather than having to create all the /dev/ entries manually/via scripts).

Even udev is optional (upon upon a time, adding a new device involved knowing the right 'mknod' invocation in order to be able to connect to it - udev sort-of solves that).

Dbus isn't a systemd project any more than a libc is a systemd project. Systemd just requires it as a dependency. It's a freedesktop project.

It's from the same microservices ecosystem, and it was mentioned in the article. That's why I brought it up.

Yes systemd can use dbus, but plenty of non-systemd systems use and used dbus.

Just run a web terminal like ttyd: https://tsl0922.github.io/ttyd

Moka pots don't make espresso, they don't get up to the pressure required for espresso-level extraction. They're still quite good and I prefer them over drip brew for most coffees.

It can extract more flavor. The most fruity and sweet brews I've ever had were good espresso shots. The same beans in a pour over are still fantastic, but it's all amplified and more pronounced when made as an espresso shot. There's also a syrupy texture that you really can't get with any other brewing method.

All that said, every day I drink pour overs and aeropress brews--I don't want to drop the $1k+ on a proper home espresso setup.

Exactly - espresso is good, but unless you're really into it, not worth the money and complexity to make at home, save it for a treat when you're out.

Yeah hiring in January is the real tell of what's going on. The layoffs winding down now were all planned and executed early at the start of the year. If next year rolls around and companies are still doing rounds of layoffs then everything is very far from being over.