4 ms·
None of those actually. Mind you 4/5 of what's listed here is also functionally available on -nix, or straight up pales in comparison. Specifically looking at
by w7 6y ago
None of those actually.
Mind you 4/5 of what's listed here is also functionally available on -nix, or straight up pales in comparison.
Specifically looking at Storage Spaces and ReFS: can't protect boot media with it (can't boot from USB either really, WTG depreciated), can't do error correction outside of basic configurations, also awesome to look at data loss and performance issues up into 2019 on "stable" releases with hardware on the HCL.
The WMI is a Windows-ism that has similar analogs with tooling on -nix. Don't get me wrong though, along with PowerShell the WMI/CIM stuff is extremely awesome.
Don't really care what MacOS does, not sure why it was mentioned, that's not what I'd consider in the "server" space.
Off the top of my head based on recent solutions I've had to implement: I'm talking stuff like per-process/user network stack segmentation (NetNS), proper native container primitives with an ecosystem to match (cgroups, runC, container, etc.), out of the box full syscall level auditing and logging (kernel auditing framework), fine grained and configurable application mandatory access control (AppArmor, SELinux), low level insight into storage properties should you ever need it (relevant FS tools), fully integrated storage and volume management options (ZFS; on FreeBSD at least), live kernel updates, and in general not making me want to gouge my eyes out any time I have to touch networking configuration.
I believe we probably occupy different spaces though, as I can see some things you mentioned that aren't entirely relevant to my use cases, as I'm sure the things I mentioned may not be relevant to yours.