Speaking as a veteran Microsoft administrator, in total seriousness: buy a Mac. If you have a corporate network complete with good administrators, Windows can be made to work well enough. If you are a lone professional, Macs are secure, low-maintenance and have an OS designed by people that care about your privacy. Windows is probably not worth your time or energy right now unless there a specific piece of Windows-only software that you must use.
Okay, and when my Web site software, with several special back end servers, is all working well, what platform do I use to keep, say, an 8 core AMD processor at 4.0 GHz busy?
On Windows, I'm aiming at Windows Server (WS). My initial usage of WS will be just dirt simple. As I get revenue, for more I will pick up a phone, call an expert, maybe you, pay for an hour to walk me through the most recent issue, take notes, and then move on until the next issue.
For Windows, I have used the .NET Framework, Visual Basic .NET, ASP.NET, ADO.NET, a little of platform invoke to call some C code, etc. and, of course, Microsoft's Internet Information Server (IIS) to sit between my Web pages and the users. I wish the .NET documentation had better technical writing, but otherwise I'm from happy enough to thrilled with .NET. If I am to use .NET heavily, then I sense that to minimize mud wrestling with weak documentation and too many bugs (e.g., from trying to get .NET to run well on iOS or Linux) I should stay on Windows.
Maybe implicit in your suggestion is that I would deploy for production on some Linux system? Okay, which one? And how many loose ends, third party, open source, do it yourself issues would I encounter?
Roughly I get the impression that for high end production use of Linux, I would be nearly rolling my own operating system -- this could be wrong. I'm eager to have good information on any operating system I use, but really I want to draw a line at the operating system, compilers, etc. and not cross that line.
At this point, I about have to go ahead with Windows. Maybe I'll get some books Windows Server 101 for Dummies or some such.
As no-one else seems to have replied to the parent as I write this, let me just reassure you that if you do ever want to look into using a Linux platform for the server side of your system, it's not so big and scary.
There are lots of Linux distributions. For general purpose server work, something big and well-supported like Debian would be a sensible starting point. You can install a relatively bare bones system to start with, and then use Debian's package manager to install and keep up-to-date most other software you're likely to need without having to build anything manually yourself.
You have several decent web servers available. Apache is the 800lb gorilla, huge but does just about everything and very thoroughly documented. There are some good alternatives like Nginx and Lighttpd as well.
There are also plenty of tools that you can add to do things like load balancing and caching if you need them.
You have several decent database servers available. Postgres is a solid choice for most things if you want a traditional relational database. Again, there are plausible alternatives such as MariaDB if your needs are slightly different. The main "NoSQL" databases also tend to run on Linux if that's what you're looking for.
Almost every major programming language has tools available to run back end code in that language on a Linux system.
Basically, the only thing you give up by moving to Linux on the back end is the Microsoft-specific technologies like IIS, SQL Server, .Net and C#. (There have even been some efforts to get .Net and C# supported usefully on non-Windows platforms, but I have no experience with those so won't comment further here.)
There is obviously a learning curve to configure these things if you haven't used Linux before, so I wouldn't necessarily recommend jumping ship if you're already set up on Windows servers and comfortable administering them. But if you do ever decide to switch, there are plenty of tutorials and HOWTO guides for setting up things like web servers and databases on Linux as well, and it's the kind of thing where you could probably get up to speed on the basics within a week or two of homework and experimentation.
Nice. Thanks. I needed that. I was hoping for something like that.
Okay, if my startup becomes a big thing, then maybe I'll have the servers all on some version of Linux. For the conversion, if I could consider doing it now, then it would be easy enough for a team of a dozen if my company gets to 100+ people.
As it is, except for nonsense interruptions not due to Windows or Microsoft but would be much the same for Linux, I am a few weeks of good work from going live. I shouldn't jump ship now.
Your original post just specified "Web site", so I assumed that you'd be using an Open Source stack - mea culpa.
Without writing a long reply - I sympathize with where you are coming from. I spent 5 years as a .NET developer between admin jobs, and the apparently all-encompassing, answer-for-everything nature of the Microsoft stack was attractive. If we could have stayed inside the lines of what Microsoft wanted to provide at the time, it would have been pleasant.
One of the advantages of switching to an Open Source platform was being able to access a much wider range of options for things, including hosting. One of these is the full-service Heroku platform - there are Web developers that only deploy to Heroku, and never set up servers.
