THIS. We shifted to Office365 Office at work in April (I early-adopted on April Fools Day, apropos? :D) In the past, the centrally-managed workstation patching processes included monthly MS Office patching, bundled into managed & scheduled OS & desktop app patches. Which resulted in 1-2 mandated 'patching' shutdown & reboots per month. Now, with Office 365, I have Microsoft independently _pushing it's own_ unmanaged patch reboot demands, _in addition to_ the preexisting OS locally-managed patches. I've worked at firms that required detail time-accounting, so I routinely track every minute of my day in an app. I also run a lot of monitoring and dev components open on my desktop - which takes a while to get reloaded, after a reboot (which is why I hibernate my laptop daily for the trip home). Net result, every mandated reboot costs a minimum of 20mins of work-time. So, when I look back at time allocated to 'Mandated Workstation Patching' (company managed + o365), I find that in June alone of this year, I had to perform _8_ separate reboots on different days of the month. Some were prompted (or unprompted) patches, and some were reboots tied to sorting out buggy code in Office365. And yea, I'd echo most of the complaints from the below. Compared to the Office 2010 I'd run at work until April: Office 365 is _much_ slower, much more bloated for memory, and annoying as spit to any power user that works primarily from the keyboard (the shift to touchscreen interface support made a lot of useful shortcuts go away). Fact is, I still run an old copy of Office 2003 Visio from time to time at home, and I do some pretty fancy architecture diagrams for the office (with Visio2013 & now 2016): Visio 2003 isn't missing a single core function I rely on in Visio 2016/O365, but it runs much snappier, and a lot cleaner. Not to mention with a lot more stability. I'm starting to believe Office365's 'Ever-Green' continuous-revision concept actually means, 'Never-Stable'. #^|
via Facebook http://ift.tt/2afOFXY
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.