abcrawf

> like, why would using a certain percentage of my total space be fine, what if all programs thought that?

Because the journal’s role in a system is inherently different than most programs. It’s collecting logs for everything; not just itself. It seems reasonable to me that a system-wide service would use a percentage of the system’s resources.

Plus, if you don’t like it, reconfigure it. It’s only the default, after all.

Man, we fought hard at Red Hat to get them to continue using networkd with their latest container-focused OS. Ultimately, the organization just had too much institutional momentum behind NM. Frankly, I’m disappointed that they lacked the imagination and drive to push the industry forward.

Can you provide any specifics of the serious issues you’ve encountered with journald and networkd? There were some performance issues with journald early on, but I know a lot of work has gone into it over the years (a coworker of mine, for example, improved the performance of log retrieval by 10x). And networkd has always fulfilled my needs nicely, so I’m curious what sort of trouble you ran into.

Drownings and ice cream sales also track nicely, but it doesn’t mean it’s the ice cream that’s causing the drownings.

Slow down and take the shortcut.

Of course it is; almost by definition. The confusion stems from the fact that most people use the term when they actually mean plumbing.

Author here, I found it pretty interesting the amount of similarity between BPF and embedded development. My original background is in computer design and low-level software, so this was a bit of a blast from the past - lots of delicately holding the compiler in just the right way to get it to emit the desired set of instructions, reading through the resulting assembly (_much_ easier with the validator annotating register values), digging deep into language specs and compiler documentation. It makes sense in retrospect, but it caught me off guard when I first started.

Let me know if you have any questions.

Not as satisfying as http://instantfart.com/

1. itch.io uses PayPal. Assuming you trust them, there is nothing to worry about.

2. itch.io provides the same mechanism. You are paying for the game, not the single download.

3. As long as you can re-download the game, then there is no reason to save the installer. Serials/keys are up to the discretion of the game developer and I don't see why giving the game developers control is a bad thing. I think most indie games are against DRM anyway.

4. In order to support auto-updates, the game developer has to invest in the Steam APIs. There is nothing stopping games on itch.io to using out-of-band updates.