[SpecialistK]

A year or two ago I moved my outdated Proxmox server over to TrueNAS Core because I was getting more into the BSDs and liked the idea of "less controversial" ZFS support.

Sadly it did feel clunkier in many ways (my Unifi Jail sometimes fails with a vague error message, CPU temp sensors are inaccurate, SMB share auth is a pain), although stability has been rock solid.

I'll be moving back to Proxmox when I rebuild and upgrade disks. It's a shame that a company that was at the forefront of BSD development has decided to move away from it.

[gh02t]

Jail-based plugins were always half baked and brittle on Core back to when it was still called FreeNAS. Updates seemed to require complicated manual intervention every time and trying to do it through the UI was a death sentence. Scale is attempting to streamline it with container/Kubernetes-based plugins. It's got some rough edges and growing pains, but in my experience so far it has still been an improvement for me even if I liked the simplicity of jails more.

Proxmox is a better platform if you wanna run a fleet of custom VMs etc, but Scale is doing interesting things if your use case is more "plugin"-like. I use both.

[SpecialistK]

On Proxmox, as much as possible I would just spin up an Alpine or Debian LXC container and install whichever packages I need, so it is more manual than the Jail-based plugins, but not a huge inconvenience.

While typing that I remembered another annoyance I had with TrueNAS, which is that it doesn't let me pick truly custom MAC addresses for my Jails or VMs, which I like for DHCP reservations. I use Coca-Cola's prefix, because it's funny and I know immediately that it's one of my hosted services.

I recall a blog post or thread somewhere describing the issues TrueNAS devs had with Jail plugins, but can't immediately find it again. If I do, I'll link it.

[CoolCold]

Why it's the shame? Keep being relevant and satisfying users needs are reasons to be proud, not shamed.

When Microsoft added WSL/WSL2 and collaborated with Canonical for smooth UX, is it a shame as well from your perspective?

[SpecialistK]

It's a shame for the reason I said in the same sentence: "a company that was at the forefront of BSD development has decided to move away from it."

iXsystems has employed some of the most prominent and important BSD developers - they were a big funder of the projects and I don't like that this will change.

I don't mean to be patronizing, but I should clarify that in English, something being "a shame" is not as strong as something being "shameful" or "should be ashamed." My friend canceling plans to see me is "a shame" (I lament it, it's sad) but my friend telling lies and rumors about me is "shameful" (he should feel bad) - iXsystems' decision is a shame, but it isn't shameful.