I've tried LTSC, and to be honest, I prefer Windows Server 2019. It had the ability to set the Telemetry to 0 as well, and has less stuff pre-installed.
If you must run Windows 10
11–20 of 214 posts
Re: If you must run Windows 10
#12I see a lot of angry posts like this, but fail to understand how it's reflected in reality in 2019—I agree that Windows 10 was a little messy at launch, but it's come a long way from where many of these complaints seem to stem from. Yeah, Windows has a bad rap, but in the last 2-4 years has come leaps and bounds from where it was—implementing great, thoughtfully designed features on a regular basis, for free. With WS…
See, your comment is the typical comment of someone who comes from macOS. The angry posts come from people who've been using Windows since forever.
I was historically a Windows user and started my career as a Windows sysadmin for a few years—I switched to macOS for a few years and came back as it became increasingly buggy and Microsoft's development story changed.
The complaints seem to come from heavily technical folks that think LTSB branches are reasonable things for normal people to run. I wouldn't want to run one on my own machine.
Re: If you must run Windows 10
#13I see a lot of angry posts like this, but fail to understand how it's reflected in reality in 2019—I agree that Windows 10 was a little messy at launch, but it's come a long way from where many of these complaints seem to stem from. Yeah, Windows has a bad rap, but in the last 2-4 years has come leaps and bounds from where it was—implementing great, thoughtfully designed features on a regular basis, for free. With WS…
See, your comment is the typical comment of someone who comes from macOS. The angry posts come from people who've been using Windows since forever.
The missteps were W8-8.1 and WS2012. W10 and W2012R2 and beyond have been much better. Not perfect, but leagues better than the those disastrous years between.
Remember when Windows Server 2012 didn't have a start menu button, but instead a pixel? I hope someone was fired for that blunder.
Re: If you must run Windows 10
#14I see a lot of angry posts like this, but fail to understand how it's reflected in reality in 2019—I agree that Windows 10 was a little messy at launch, but it's come a long way from where many of these complaints seem to stem from. Yeah, Windows has a bad rap, but in the last 2-4 years has come leaps and bounds from where it was—implementing great, thoughtfully designed features on a regular basis, for free. With WS…
A serious and legitimate gripe with windows is how messy it is to automate things. It's hard to look at the command prompt the same way I look at bash. I resort to almost anything other than batch when I can.
Re: If you must run Windows 10
#15I see a lot of angry posts like this, but fail to understand how it's reflected in reality in 2019—I agree that Windows 10 was a little messy at launch, but it's come a long way from where many of these complaints seem to stem from. Yeah, Windows has a bad rap, but in the last 2-4 years has come leaps and bounds from where it was—implementing great, thoughtfully designed features on a regular basis, for free. With WS…
Some people are tired of an OS that by default phones home about actions you do on it, include advertisement in your start area, and regularly push updates to add new features that also break existing software.
Re: If you must run Windows 10
#16Another option without Edge, Cortana and Candy Crush is Windows Server 2019 which is what I have on my Dev PC. I’ve always run desktop server when I could - back to NT4 - initially to avoid any differences between local behaviour and deployed, though this is not really ever the case now. So now it’s for this reason - to avoid the cacophony of recent Windows versions, weird behaviour from updates and the like. I don’t…
There are a number of challenges with using Server as a desktop OS. Sometimes utilities I want to use are $20-40 for a desktop PC, and $1000+ to install on a server OS, even though they are the same software. Sometimes apps just won't work because they are checking what OS you are using and don't like it.
Recently I tried setting up a Windows Server 2019 install... to use as a home server... on my Intel NUC, only to discover that the Ethernet driver on the NUC has been intentionally omitted from Windows Server compatibility, because Intel wants you to use enterprise class hardware with Windows Servers. (If you plug in a USB to Ethernet dongle that uses a Realtek chip, Windows Server works fine on the NUC, but this is hilarious. There are also bad-hack ways to modify the Intel network driver so it installs on the Server OS.)
Re: If you must run Windows 10
#17I see a lot of angry posts like this, but fail to understand how it's reflected in reality in 2019—I agree that Windows 10 was a little messy at launch, but it's come a long way from where many of these complaints seem to stem from. Yeah, Windows has a bad rap, but in the last 2-4 years has come leaps and bounds from where it was—implementing great, thoughtfully designed features on a regular basis, for free. With WS…
A serious and legitimate gripe with windows is how messy it is to automate things. It's hard to look at the command prompt the same way I look at bash. I resort to almost anything other than batch when I can.
It's hard to look at Bash the same way as I look at PowerShell. I resort to almost anything other than Bash when I can.
Re: If you must run Windows 10
#18I see a lot of angry posts like this, but fail to understand how it's reflected in reality in 2019—I agree that Windows 10 was a little messy at launch, but it's come a long way from where many of these complaints seem to stem from. Yeah, Windows has a bad rap, but in the last 2-4 years has come leaps and bounds from where it was—implementing great, thoughtfully designed features on a regular basis, for free. With WS…
From a feature standpoint, Windows has definitely improved in the last few years, however, I don't see much improvement in terms of UX. To me, Windows development was always about "let's get this feature in so we can claim that we do X" but Microsoft has never proven themselves in terms of providing a cohesive experience in terms of inter-app behaviors or just UI/UX streamlining. This is extremely apparent when you look at their office apps (Outlook, Word, etc).
Re: If you must run Windows 10
#19I see a lot of angry posts like this, but fail to understand how it's reflected in reality in 2019—I agree that Windows 10 was a little messy at launch, but it's come a long way from where many of these complaints seem to stem from. Yeah, Windows has a bad rap, but in the last 2-4 years has come leaps and bounds from where it was—implementing great, thoughtfully designed features on a regular basis, for free. With WS…
A serious and legitimate gripe with windows is how messy it is to automate things. It's hard to look at the command prompt the same way I look at bash. I resort to almost anything other than batch when I can.
If you are using batch scripts on Windows in 2019 you are most definitely Doing It Wrong. PowerShell (which for my money is better than bash) is the "official" scripting environment on contemporary Windows and batch file support is only included for backward compatibility with legacy scripts. Don't use it, ever.
Re: If you must run Windows 10
#20Earlier quoted context omitted.
See, your comment is the typical comment of someone who comes from macOS. The angry posts come from people who've been using Windows since forever.
The missteps were W8-8.1 and WS2012. W10 and W2012R2 and beyond have been much better. Not perfect, but leagues better than the those disastrous years between. Remember when Windows Server 2012 didn't have a start menu button, but instead a pixel? I hope someone was fired for that blunder.
Oh man, I'll tell you—Windows 8 was a beast of its own. I think that is how people remember Windows, and assume that Windows 10 is the same. But god, don't remind me of that awful full-screen server start menu..............I remember that's when we actively started to try and go full headless with Windows Server, but it was also half-baked back then.