Earlier quoted context omitted.
> There is probably a registry value you can change to do so though. Thanks, but with "probably" I sense that I'm about to get into what I call "mud wrestling" or hours or days of just throwing wild guesses against a wall to see if any appear to stick. I've only got 365 days a year, and I've given away far too many of them to such mud wrestling. GOD knows I do NOT want to do more of that. For physical things, say, an…
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-on…
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.