Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In many ways it hasn't been outclassed. Every time I dip a toe into the Linux waters, I recoil in horror at the things that lurk beneath the surface.

You're all suffering from Stockholm syndrome.

Where to begin?

There is no Linux, except the kernel. There's dozens of distros, and none are even vaguely compatible in their user space in the same way Windows is. Docker containers are effectively mandatory if you want to retain your sanity.

Configuration files are ad-hoc, unspecified, text formats (huuurk) with arbitrary and capricious escaping and quoting rules. It's rare for these to be formally specified anywhere. Good luck doing anything to Linux configuration programatically!

A Linux operating system in general is "write only, once" -- which also explains the popularity of docker. Trying to manage a fleet of heterogeneous servers with Ansible, Puppet, or whatever is an exercise in frustration. They're barely more than script-execution engines, applying opaque changes that are difficult to audit later. You're always best off discarding servers entirely and starting from scratch.

Linux barely even has a concept of a "service", which invariably require a full stop-start to pick up configuration changes. When -- finally -- systemd was introduced to catch it up to NT4, there was much wailing and gnashing of teeth. It's still inconsistent, so publishing server software for Linux is again, you guessed it, best done with containers.

Don't even get me started on how Linux stumbled into UTF-8 in an era where Windows, MacOS, and Solaris had already been doing Unicode for a decade.

Can I put spaces in file names yet, or is that still considered an eldrich incantation to greybearded admins?

Unicode in user names?

Central auth without hard-coding IP addresses for "the" (singular) Kerberos server, like it's an MIT lab in the 1980s?

Here's a trivial operation on Windows that would make any Linux admin collapse into a twitching heap and foam at the mouth: Make every server and workstation trust the same private root certificate authority, for every HTTPS client on the system, not just one particular web browser or app runtime.

Or... ensure the existence of a consistent firewall rule to every Linux computer, e.g.: for Tenable scanners.

Or... add a local user to every Linux computer with some non-trivial rights.

PS: I've done all of the above and was horrified about the time, complexity, and cost.

 help



First of all, this is about Windows Server, not client. The extent to which you need a Windows Server is to manage a fleet of Windows Clients.

All the issues you mentioned are irrelevant for a Linux server (distro selection, any ill-conceived notion of svchost benefits on a server, client CA management, adding local users, etc) or much better on Linux as a server (utf8, file length, and yes you can have space on the file, you can have more that 256 spaces as a matter of fact)

You can get all the windows client benefits if you lock on a distro like you said or use macOS. Windows is garbage ware.


Ironically, Microsoft is busily removing the need for that! Windows desktops can now be managed with just Entra ID and Intune, there's no need for Windows Server.

In practice, ~80% of Windows Servers in typical deployments are not used to manage the client fleet, they're hosting web apps on IIS, database servers, etc.


they gave me a windows server as a dev environment. i laughed. it never gets used, because it sucks.

> Configuration files are ad-hoc, unspecified, text formats (huuurk)

depends, toml and json are becoming more widespread. systemd's format is also specified.

> Docker containers are effectively mandatory if you want to retain your sanity.

If your application consists of a sprawling mess of files and depends on specific library vesions then yeah, but that's no fun on windows either where you either need to run a bunch of prerequisites-installers or bundle a ton of dlls before you run the actual application.

It's entirely possible to write single-binary executables that integrate themselves into a system, sans containers. I have done so for windows and linux. On windows it registers itself as system service, on linux as systemd unit. Afterwards things start to diverge a lot. On windows if you want to talk to the system you either need to call a lot of C APIs or or startup a powershell interpreter to run cmdlets wrapping those APIs. On linux you can write a bunch of config files or invoke the a CLI tool directly without indirecting through a shell.

> Can I put spaces in file names yet, or is that still considered an eldrich incantation to greybearded admins?

Has been possible for decades. Some shell scripts might be handling them incorrectly, but passing command line arguments in cmd/pwsh is fraught too. I'd say windows' argument passing is worse than unix.

> Don't even get me started on how Linux stumbled into UTF-8 in an era where Windows, MacOS, and Solaris had already been doing Unicode for a decade.

As I understand it it was only with windows 11 that they finally finally converted the *A APIs and the terminals to utf8, before that they defaulted to some legacy codepages.

> Make every server and workstation trust the same private root certificate authority, for every HTTPS client on the system, not just one particular web browser or app runtime.

As the eMudhra debacle showed neither windows nor linux can do this since various applications started shipping embedded certificate bundles instead of using the system store.


> Don't even get me started on how Linux stumbled into UTF-8 in an era where Windows, MacOS, and Solaris had already been doing Unicode for a decade.

The Unicode story is hardly a triumph for Windows here. UTF-16LE is strictly worse for almost every case.


Yeah. As a Windows and Linux server admin, the capitalism leads to a lot of dumb in Windows Server like Edge having Game Mode and Xbox Services starting by default on Server out of the box. Most of what Windows does badly isn't poor engineering... it's own-goals due to business interests.

But Linux is downright primitive in comparison in a lot of ways. It's nice to have a robust free operating system, but Linux is downright primitive sometimes in comparison. And a lot of it does come down to being fifty separate systems with no clear vision. Things like discovering disabling suspend in GNOME doesn't actually disable suspend, because that only applies when you are logged in.

systemd has helped a lot in closing the gap, but while I'd rather have a Linux server "just running", I'd definitely rather troubleshoot a problem on a Windows box.


Rather than refute your points individually, I'll just say that if you think having spaces in file names requires some kind of Eldritch incantation then you are so far off base and/or unskilled it's not even worth engaging.

This. For every point he has, I can think of one or several counterpoints. But I can't be bothered with an obvious troll.

The funny thing about callouts like this is it ignores stupid things like Microsoft saying to never rename a domain controller in the pre server 2012 days. Now it's a lot more accepted/easier to do and there aren't as many warnings, if any. But I recall in so many books, guides, videos and documentation they mentioned to not rename a domain controller hostname under any circumstances. Windows is not without it's faults and some of it's quirks are no different that Linux.

There is a lot of LARPing on HN.

Unfortunately they give most of the unsolicited advice.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: