xylophile

Because percentage of investment indicates how central Linux is to their business. If Linux disappeared overnight, Google would find another way to sell ads, but RedHat would disappear.

It's a reasonable proxy for things like long-term commitment and commits across the stack (e.g. audio and video, not just network and disk).

I love Zellij but it doesn't play well with Neovim. If you try to use both tools heavily (Neovim splits + stacked Zellij panes), your Neovim layouts will get trashed. And if I have to choose between Neovim or basically anything else, Neovim will win.

Sadly, these issues are low priority for the main dev. Instead they are focusing on things like serving terminal sessions over the web, which is useless to me if I can't use Neovim in it.

If somebody announces that their project is written in Rust but nobody complains, what happens?

Writing any non-trivial video game with Rust is (arguably) interesting in itself since developer velocity in gamedev is generally considered paramount, and Rust has a reputation (rightly or wrongly) for hindering velocity.

So yes, the fact that this is written in Rust is actually relevant and valuable. As opposed to your hollow snark.

Now, OP: tell us more about how that's played out for you.

Not a popular opinion, but RedHat (now IBM) funds an enormous amount of critical open source. They pay people to contribute to hundreds of upstream projects. And RHEL is 100% focused on stability. Sounds like a good match for your priorities / goals.

Any optimizations discovered at runtime by a JIT can also be applied to precompiled code. The precompiled code is then not spending runtime cycles looking for patterns, or only doing so in the minimally necessary way. So for projects which are maximally sensitive to performance, native will always be capable of outperforming JIT.

It's then just a matter of how your team values runtime performance vs other considerations such as workflow, binary portability, etc. Virtually all projects have an acceptable range of these competing values, which is where JIT shines, in giving you almost all of the performance with much better dev economics.

It is accomplishing something. When 40 different applicants are equally able to do the job, the only selector you have is "culture fit", which is where bias starts to easily kick in (race, age, whatever), and that is a legal risk.

The leetcode hoops exist to provide a provably objective measure for hiring, even though that measure is unrelated to job performance. It's purely a lawsuit avoidance mechanism.

I came to this thread purely to see if I was the only enlightened one.

Stalwart is perfect for small self-hosters: a single binary, a single-directory resilient datastore (by default), a UI for every setting, and defaults that guide you to a DNS config which maximizes your sender score. Plus support for all of the "power user" features such as ManageSieve and shared CalDav folders.

Honestly, I love hosting my email now. And the last remaining battery which could possibly be included is now WIP: webmail!

Unix philosophy need not apply when there is exactly one use case for integrating these tools. (Or at least, one case which covers 99% of users. The remainder can keep their managerie of arcane config formats and susceptibility to unsafe language CVEs.)

I'd like to read this but my eyeballs are burning. And since it's only a handful of pages, there's no reason for it to be a PDF.

The executive class is entirely based on personal branding. If you're not changing anything, it's like being a TikTok influencer without posting any new videos. It doesn't matter what you post really, and often the more controversial you are the better. If you play your cards right, you're not an "idiot" for making the company worse, you're a "bold and innovative thought leader".

You often see the same thing from ambitious managers. Aka, "managers gonna manage".

The other part of the equation is pure politics and PR, which at least does provide some real value to the company (if only temporarily, and at long-term net negative). Amazon made it pretty clear that their RTO was all about maintaining their relationship with politicians.

Docker daemon runs as root, and runs continuously.

If you're running rootless Podman containers then the Podman API is only running with user privileges. And, because Podman uses socket activation, it only runs when something is actively talking to it.

Trying to be genuinely helpful here:

After many years of "I want stability and evergreen", I finally realized that this is Fedora. Each release is very stable, and they arrive more often than once an eon.

You mean curl?

You can always edit the file in the container and re-upload it with a different tag. That's not best practice, but it's not exactly sorcery.

I know everyone wants "just one more feature", but I've been looking for a tiny kv for a side project that allows you to query by key prefix. I haven't had time to build one yet, and have honestly been hoping to stumble across one. Only the huge kv's seem to offer this, despite the existence of off-the-shelf hashing algorithms that will preserve lexicographic ordering.

Just FYI, you may also enjoy systemd-machine. It's essentially the same thing as toolbx but it handles the system bus much more sanely, and you can see everything running inside the guest from the host's systemctl.