Why not Windows 11? Because China, like many other non-US governments, no longer trusts American companies with their software and services. This approach is all about digital sovereignty.
I never understood why any country would allow their government computers to run proprietary software from a foreign (to them) company.
I’m sure that China had access to a lot of Windows source code as part of their previous agreement, but it’s far too big a risk, really, for any country, even the United States, to run Windows.
As far as I’m concerned, China is decades late in making this decision, and it’s still ahead of a lot of (most?) governments.
I’d argue that Linux has only within the last 3 to 5 years become “good enough” to use as a daily driver for the casual, tech illiterate government official. I’ve tried different flavors on and off for the past decade and never stuck with any of them due to instability or UX problems. It was only at the beginning of this year that I found a Linux flavor I could actually stick with and use as my daily driver (CachyOS).
Linux was ready for tech savvy enthusiasts 10+ years ago, but Government is never that.
Edit: Also note that government NEEDS stability, which Linux very much wasn’t until recently (and arguably still isnt); this is why Windows has starting becoming a liability.
A lot of the world server-wise is running on Linux already anyway, Microsoft’s own servers included. For the end user I’d argue it is not about stability but rather UX mostly. I’m not completely tech illiterate, but I prefer something that “just works” without too much fiddling, and Linux definitely isn’t that currently.
On the other hand, a knowledgeable IT department can provide that for the enduser, you just need the knowledgeable people in your IT department and the will (budget) to move away from the current environment, then everything works just fine. But time will tell.
I grew up with Windows and I constantly had to fix shit just for my own casual use, the biggest barrier to moving to Linux is about learning a new OS from scratch, we already go through that learning curve with Windows normally so we forget how much time and effort it took us just to understand the system well.
That aside, I’d argue that for most productive work that doesn’t require proprietary software, you also don’t need to understand Linux that well to be productive. You just need to know how to log in, launch whatever you need, and then turn it off before going home. The biggest reason why we can’t just make people switch overnight is that they’re probably used to proprietary software that just won’t work well on Linux, like Adobe or Microsoft Office. If you train your personal to first switch to FOSS alternative, when you do make the switch to Linux the learning curve for what they need to do is small and they won’t be as intimidated. But now, if you’re talking about how their years of learning Word or Excel or Photoshop doesn’t translate 1:1 because of different UI and behavior, they’ll be very uncomfortable and less productive when they switch.
Things inevitably go wrong no matter what system or software in general you use, we’re just used at tolerating it when it’s something we know and use already, but there’s no reason why we should think Linux or FOSS software has to be strictly much more stable than its counterparts, as long as they’re good enough for the person or the use case, it’s already good enough to switch, with the caveat that you should never switch everything at once, but rather first switch your productive software, retrain to feel confident in it, and then switch to Linux. That way you’ll not even remember you’re running Linux after a few weeks, other than when you see the login screen or something.
Also note that government NEEDS stability, which Linux very much wasn’t until recently (and arguably still isnt); this is why Windows has starting becoming a liability.
I was using Linux in the late 90s when my Linux machine would run for months, only being rebooted when I decided to do a kernel upgrade, and meanwhile everybody was running Windows 95, one of the least stable OSes that I’ve ever used. It literally had a counter baked into the OS that caused a crash if you ran it for a certain amount of days, I think 30. If stability was so important, they’d have switched to Linux back then.
Even in the late 90s, the UI was decent enough as long as you had a decent administrator. I don’t think casual users could be expected to set up Linux back then, but that’s not a government type of use case.
I remember learning about that bug years after the OS came out, and not being too surprised that it was never fixed.
Windows 95 crashed so often that you’d basically have to specifically do nothing with the machine to ever get that crash. And even then, you’d just assume that it was crashing like Windows 95 always did anyway.
So you’d be unlikely to see or recognize that bug unless you were specifically testing for uptime issues.
I never understood why any country would allow their government computers to run proprietary software from a foreign (to them) company.
I’m sure that China had access to a lot of Windows source code as part of their previous agreement, but it’s far too big a risk, really, for any country, even the United States, to run Windows.
As far as I’m concerned, China is decades late in making this decision, and it’s still ahead of a lot of (most?) governments.
I’d argue that Linux has only within the last 3 to 5 years become “good enough” to use as a daily driver for the casual, tech illiterate government official. I’ve tried different flavors on and off for the past decade and never stuck with any of them due to instability or UX problems. It was only at the beginning of this year that I found a Linux flavor I could actually stick with and use as my daily driver (CachyOS).
Linux was ready for tech savvy enthusiasts 10+ years ago, but Government is never that.
Edit: Also note that government NEEDS stability, which Linux very much wasn’t until recently (and arguably still isnt); this is why Windows has starting becoming a liability.
A lot of the world server-wise is running on Linux already anyway, Microsoft’s own servers included. For the end user I’d argue it is not about stability but rather UX mostly. I’m not completely tech illiterate, but I prefer something that “just works” without too much fiddling, and Linux definitely isn’t that currently.
On the other hand, a knowledgeable IT department can provide that for the enduser, you just need the knowledgeable people in your IT department and the will (budget) to move away from the current environment, then everything works just fine. But time will tell.
I grew up with Windows and I constantly had to fix shit just for my own casual use, the biggest barrier to moving to Linux is about learning a new OS from scratch, we already go through that learning curve with Windows normally so we forget how much time and effort it took us just to understand the system well.
That aside, I’d argue that for most productive work that doesn’t require proprietary software, you also don’t need to understand Linux that well to be productive. You just need to know how to log in, launch whatever you need, and then turn it off before going home. The biggest reason why we can’t just make people switch overnight is that they’re probably used to proprietary software that just won’t work well on Linux, like Adobe or Microsoft Office. If you train your personal to first switch to FOSS alternative, when you do make the switch to Linux the learning curve for what they need to do is small and they won’t be as intimidated. But now, if you’re talking about how their years of learning Word or Excel or Photoshop doesn’t translate 1:1 because of different UI and behavior, they’ll be very uncomfortable and less productive when they switch.
Things inevitably go wrong no matter what system or software in general you use, we’re just used at tolerating it when it’s something we know and use already, but there’s no reason why we should think Linux or FOSS software has to be strictly much more stable than its counterparts, as long as they’re good enough for the person or the use case, it’s already good enough to switch, with the caveat that you should never switch everything at once, but rather first switch your productive software, retrain to feel confident in it, and then switch to Linux. That way you’ll not even remember you’re running Linux after a few weeks, other than when you see the login screen or something.
The city of Munich did it in 2004. Only reversed it after Microsoft decided to build their new Germany hq in the city.
https://en.wikipedia.org/wiki/LiMux
I agree with the daily driver part, but hard disagree with the stability part.
Linux has been running the most stable machines in the world since the 90s, along with unix.
I was using Linux in the late 90s when my Linux machine would run for months, only being rebooted when I decided to do a kernel upgrade, and meanwhile everybody was running Windows 95, one of the least stable OSes that I’ve ever used. It literally had a counter baked into the OS that caused a crash if you ran it for a certain amount of days, I think 30. If stability was so important, they’d have switched to Linux back then.
Even in the late 90s, the UI was decent enough as long as you had a decent administrator. I don’t think casual users could be expected to set up Linux back then, but that’s not a government type of use case.
Apparently it was 50 days:
https://pipiscrew.github.io/posts/why-window/
Wonderful, thanks for looking that up.
I remember learning about that bug years after the OS came out, and not being too surprised that it was never fixed.
Windows 95 crashed so often that you’d basically have to specifically do nothing with the machine to ever get that crash. And even then, you’d just assume that it was crashing like Windows 95 always did anyway.
So you’d be unlikely to see or recognize that bug unless you were specifically testing for uptime issues.