8 ms·
This is hardly surprising. Not to crap on MS, but I do think Linux has traditionally just been a better operating system for servers, probably due to the fact
by tombert 7y ago
This is hardly surprising.
Not to crap on MS, but I do think Linux has traditionally just been a better operating system for servers, probably due to the fact that that's where most of the funding for Linux ends up going, with the desktop versions of Linux being sort of secondary.
It doesn't help that a lot of serverey software is kind of designed with POSIX-ey stuff in mind. Node.js took awhile to get Windows support and ZeroMQ's Windows support doesn't support IPC sockets. Hell, in the little bit of testing that I've done with this, .NET Core is faster on Linux than Windows.
This isn't to say Windows is "bad". I'm personally not a fan but plenty of smart people I know like Windows better than Linux. It's just to say that, for the domain that Azure fills, Linux is often a better fit, and if MS wants to compete with AWS, it would be borderline-idiotic not to support Linux.
- code_duck 7y agoIt just makes sense to run a server OS that works well and is full-featured when there is no GUI.
- tombert 7y agoYou know, I was thinking this, but honestly how much overhead is the Windows GUI when no one is logged into it? I know it's not nothing, but I suspect it's not that much, is it?
- code_duck 7y agoI don't mean as far as idle resource usage. The advantage of Linux is when you want to accomplish tasks without a great internet connection, but the windows tools are not evolved enough as far as command line functionality.
- jen20 7y agoThis was once the case, but PowerShell has been a solid administration tool for quite some time now. OpenSSH Server also ships as part of Windows, which was the missing link (since WinRM is, charitably, awful). The remote administration experience of Windows is now certainly comparable to Linux, in my opinion.
- mmcconnell1618 7y agoWindows Server is available in a "core" edition without a GUI.
- tonyedgecombe 7y agoNot only that but pretty much everything on Windows Server is exposed to PowerShell and has been for some time.
- code_duck 7y agoAnd does it actually have well tested, well known, reliable functionality on everything you tend to use? Configuration of programs using easy to edit text files vs some system of ticking checkboxes in a GUI? RegEdit, is there a text version for that? Imo there's no comparison to the Linux ecosystem. Windows is GUI first.
- what-the-grump 7y agoIt's a lot. I run core for critical windows infrastructure to cut costs, patch times, and save on core count, instance sizing and reduce attack footprint. The GUI is big, and I run that when needed, RDS, userland stuff etc.
- mekster 7y agoIt's not the resource but the cognitive load is so high when you have to click little parts and you can only interact as good as what the UI offers. Apparently Windows is human first which isn't what servers are meant to be.
- oblio 7y agoYou don't have to click little parts, you can use Powershell :-)
- koffiezet 7y agoYou don't want to know how many RHEL servers are out-there running a gui...
- mekster 7y agoAs many as wannabe sys admins.
- adolfojp 7y agoWindows Server Core (no GUI) has been the default since 2012.
- rhacker 7y agoI've always got the feeling that MS specific developers are highly visual studio oriented. They have their connection string built into the IDE. In fact, if you asked them to make something that builds from the command line, and runs, they would probably be scratching their head for a while. It wouldn't surprise me at all to find some windows based companies that have classic windows VMs in the cloud, running Visual Studio, and production deployments are: RDP in, stopping with the little red button, updating the codebase (with a copy over a network share), and then re-running the code on the production server with the little green play button. Database changes are done by hand in SQL Server Manager. I know this isn't at all related to the post here - but it's just an interesting phenomenon - the fact that Azure is about 50 percent windows means it's mostly running things like Office backend products, crazy running copies of Visual Studio. It is probably a total mess if half of Azure goes down for 5 minutes. Linux servers would come back up and continue running whatever. All the Windows companies get a call, have to RDP in and do shit.
- NicoJuicy 7y agoI'm one "visual studio Dev" I have also build in Go, nodejs, Php, RoR. But VS is truelly the best IDE experience I have witnessed. Database changes are automatically migrated and deployed using entity framework fyi. The big deployment button changes the connection string per deployment, deploys with feature flags directly and automatically migrates the db to the latest version
- addicted44 7y agoIt's kind of funny to see the disdain for VS based deployment here, while all the current rage right now is declarative deployment systems. Something VS based development, build and deployment based workflows have been doing for over a decade through the largely Web..config files and .csproj files.
- NicoJuicy 7y agoIndeed, it's really powerfull. https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/transform-webconfig?view=aspnetcore-3.1 https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy...
- eitland 7y ago> in the little bit of testing that I've done with this, .NET Core is faster on Linux than Windows. My experience as well. In fact it was extremely much faster. - Hello world took something like 5 seconds to run on Windows - on Linux (a VM on the exact same laptop, with the same Windows running underneath in fact) it was so fast I had to use the time command to figure out how many milliseconds it took :-) FTR: while it was hardly scientific I actually put some effort into trying to make sure it was equal.
- jfkebwjsbx 7y agoThat does not make sense at all. The files were probably cached in the Linux case.
- eitland 7y agoBelieve me I tried a number of things. It was like that from the first run and every time. Well, technically it might have used 700ms the first time and 400ms later, I didn't measure the first run, but it was still way faster than on Windows which was why I started measuring using time after all. Also on Windows it kept being slow on subsequent runs, and in my world that matters too. I don't have recordings, but I recommend you try for yourself. I compiled both from the same source, and as far as I can remember I used standalone compilation for both (I don't have perfect memory but I have a history of being careful.)
- int_19h 7y agoSpawning a process is a rather heavyweight operation on Windows, compared to Linux, so it's not surprising that it's slower. But 5 seconds definitely makes it sound like an I/O caching issue.
- eitland 7y agoAnother common problem on Windows seems to be antivirus. Many of the available options seems to insist on checking every file on every invocation even if I have compiled it from my own sources (I see this can be hard to judge) and even if it last checked it a few seconds ago.
- freefriedrice 7y agoWindows came from the single-user domain. Unix came from server space. It is literally two different evolutionary paths. From day-1, Unix was built for shared file systems, multi-user accounts, and distributed computing. Networking on Microsoft was an afterthought until the mid-90's. Sure there were token ring and banyan vines drivers in the late 80's early 90's, but that was to share a drive letter. The entire idea of multiple users didn't appear until Win3.1 for workgroups, decades after multiuser OSes. WinNT started to take protected mode seriously, but they re-invented networking from an MS perspective (e.g., POP/SNMP? nope: MSExchange). It's not a surprise that Windows is such a mess under the hood compared to Linux/BSD/Unix/SystemV when you look at the history of Windows. I dunno, maybe that's not fair, but switching between *nux and Windows from a networking / distributed computing perspective is jarring. And that's just for simple things (interface config, tracing, configuration of multiple adapters and bridges...)
- ThrowawayR2 7y ago> "Windows came from the single-user domain. Unix came from server space." Windows 9x came from the single-user domain but is long dead except for compatibility stuff left over in modern Windows. Windows NT and its successors came from server space from its VMS lineage.
- ghostpepper 7y agoI have to wonder what percentage of the Windows 10 codebase is for backwards compatibility.
- oneplane 7y agoWhile that is true, the win32 API and other stuff that floats on top of NT for the GUI based stuff (which is most stuff) is still very much restricted by that legacy. NT was supposed to be very tunable and modular and have multiple personalities and abstractions but it turns out it mostly is just win32-on-NT and everything else ended up being on top of win32. It has gotten better, especially post-OneCore, but it still is very much restricted compared to Linux, BSD and Unix. Windows NT (and VMS) were not as much multi-user server as they were more closer to mainframes (which died/are dying for their own reasons). VMS, like plan9, had concepts to allow many (theoretically) fancy server things, but were to much a created world instead of a grown world (like post-system-v). Also, while the VMS dude who was on the NT team did influence it heavily, the legacy they had to support made it almost impossible to use any of that fancy 'new' stuff back then. While it was orders of magnitude better than DOS, it feels like Windows needs to make yet another evolution like it did going from DOS to NT to get back to current times instead of patching on top of patches every time.
- GordonS 7y agoI've used Windows on desktop since 3.1, and nowadays Windows 10 is my daily driver - IMO it's the best desktop OS, and always has been. But for servers, I much prefer Linux. It uses less resources, and it's so much easier to get it into a known and consistent state that Windows. Also, something about having a GUI for servers has always felt... wrong somehow!
- mixmastamyk 7y agoRight tool for the job. Also Windows finally has a terminal and ssh, so it is tolerable.
- FpUser 7y agoAlmost the same here. I do not really have problems with GUI on server besides you can configure Windows server run without one. But the pricing however is not very attractive for smaller fish.
- tracker1 7y agoWSL2 is the only thing that has made Windows bearable for me. That and VS Code's remote extensions. Almost everything I use is cross platform for years now.