Words evolve, and sometimes, they gain new meanings. “Bare metal” is not a scientific terms, and so it can be bent depending on the context.

You can either accept that or not, it doesn’t change the fact that that’s what it now can mean.

It’s just what it means in this specific context.

They’re not running directly on the host, with directly meaning directly.

If you go by definition, I agree with you, but the definition is not always the thing to go off of.

Have you read my comment? It’s about where the packages and services are installed.

In this case, they’re installed in the container, not on the host

Not in this context. Bare metal means all packages and services installed and running directly on the host, not through docker/lxc/vms

it’s satire

Yeah, but people don’t like change, and I’d expect low level engineers to like it even less.

And looking at Linux, that shit still supports ancient hardware, being able to actually get rid of old code (that now has to be maintained alongside the new code) is gonna be a PITA.

I’m just guessing, but what about backwards compatibility? Or cross-system compatibility?

For example, something like a syscall that’s existed for 20 years. Changing it would break old apps.

Of course you could just keep the now “old” syscall and add new methods that replicate it’s behavior, but haven’t you then introduced bloat? More ways to do the same thing, meaning (eventually) more bugs, more fragmentation, memory usage, etc.

I had no idea, thanks for the info

That’s on the tv manufacturers though, it’s their choice.

Oh I know, but I do think anti-trust would require an erection of some sort of barrier. Say, if HDMI required that if HDMI is present, displayport cannot be.

Right now, tv makers are complete free to choose.

Doesn’t mean displayport can’t be used there.

If the tv maker wanted to not pay licensing fees, they could put a displayport on the thing. But they don’t. Their call.

That’s not the point of my comment, the point is that whatever hdmi is, it’s got very healthy competition, so there’s no real reason for anti-trust stuff

But displayport exists, is widely used and is free?

I’m pretty sure that’s kinda exactly what happened though, I wouldn’t be surprised if it was just that no one thought to add a logo because engineers don’t care about shit like that (at least a lot of them don’t)

They literally say “it doesn’t matter” if you leave it open, but that you might come across issues if you don’t

https://letsencrypt.org/docs/allow-port-80/

It’s not.

It’s not like there’s a shortage of text editors on MacOS either though

Well, looking at how popular VSCode is, looks like people don’t mind the web browser thing

If you want to learn zfs a bit better though, you can just stick with Proxmox. It supports it, you just don’t get the nice UI that TrueNAS provides, meaning you’ve got to configure everything manually, through config files and the terminal.