SoylentNews is people
SoylentNews
For experienced IT veterans—and PC enthusiasts—there is a common wisdom about the latency between when a version of Windows is released, and when those releases become reliable. Windows XP is the primary example of this, as the original release of XP lacked a variety of important security protections—a rebuilt firewall enabled by default, support for NX bit, and finally disabling the Windows Messenger service abused by spammers, were added in Service Pack 2, three years and a day after XP was first released.
And so, that leaves us with our present circumstances with Windows 10. Roughly seven weeks ago—on May 21—Version 1903 (or 19H1), otherwise known as the May 2019 Update, was released. This marks three years, nine months, and 22 days since the initial release of Windows 10. Reception has been politely positive, though problems with the launch have prompted Microsoft to require users to remove USB storage devices or SD cards before upgrading; likewise, the update was blocked on the Surface Book 2 because a driver problem renders it incapable of seeing the NVIDIA GPU in the base of the high-end model.
Given the positioning of Windows 10 as being essentially the last version of Windows (similar to the way Mac OS X has been around since 2001), it is potentially unwise to declare this exact point in time "as good as it gets." Microsoft's track record is likely to back up this claim, though—at best, Microsoft can deliver iterative changes on top of Windows 10, but the biannual release cadence does not lend itself to massive changes, and further iterative changes are not going to convince the skeptics. If you don't like Windows 10 now, you're not going to like it in the future.
https://www.techrepublic.com/article/windows-10-three-years-later-why-this-is-as-good-as-it-gets/
(Score: 2) by PartTimeZombie on Wednesday July 17 2019, @08:20PM (2 children)
Um... no that's sales for this one rather insignificant site at the bottom of the world.
(Score: 2) by JoeMerchant on Wednesday July 17 2019, @08:41PM (1 child)
Ah, makes sense...
Still, our $30B/yr org runs completely on Office 365 (wonder what that contract costs...)
I'm not sure how that interacts with the direct connect MS Office clients, I'm not that bothered to use straight MS Office anymore. Maybe that is a fail-over that can cover for when "Cloud Office is feeling rainy..." not that your $30M in monthly sales guys wouldn't go ballistic when the mail client they normally use starts acting even a little bit different.
One "killer app" for me is accessing Office 365 from Chrome on Android... I think IT didn't want this to happen at first, but they couldn't really block it since Chrome on the phone can masquerade as Chrome on a desktop. I think after a year or two of everybody end-running them and getting e-mail on their phones without installing the death from above wipe-your-phone company app, they probably figured out that Chrome doesn't cache enough of the e-mail content locally on the phone to worry about.
🌻🌻 [google.com]
(Score: 2) by PartTimeZombie on Wednesday July 17 2019, @10:06PM
I had not thought of the death from above wipe-your-phone company app, but we have one too.
I wonder if the Office 365 guys have thought of it? That might be fun.