[laumars]

In fairness to Linux, you're not actually building a "server" there. A typical server would be running on over ethernet rather than WiFi and on server board with support for remote management (eg IPMI or iLO) which would have mitigated the VNC issues you were having (though anecdotally I've never had any problems running X + VNC on a headless Linux box on the rare occasions I've needed to)

But arguments about VNC aside, the vast majority of the time you don't want nor need a GUI running on a server to begin with. Aside maybe some game servers, any Linux server daemon is command line configurable so you're better off saving your RAM and managing your server via SSH (or better yet, Vagrant / Puppet / equivalent)

In my experience, Linux is actually very good on servers. But by this I mean "proper" servers. Personally I'd still rather run FreeBSD, but many of the same arguments for and against Linux are applicable for FreeBSD as well.

[IshKebab]

Who says a server can't use wifi? A server is just a computer that primarily provides services to other computers.

And who says I don't want to run a GUI? I don't live in the 70s.