That’s exactly it. It’s like someone randomly just says “forget what you were planning to do the next day or so, you now need to start researching how to fix your machine”. Then doing that more than once per year.
I thrive on change but that’s not reasonable. Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax SQL Down Under | Web: www.sqldownunder.com |http://greglow.me *From:* ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Tony McGee *Sent:* Wednesday, 13 December 2017 2:27 PM *To:* ozDotNet <ozdotnet@ozdotnet.com> *Subject:* Re: [OT] Big Windows 10 update Although there's plenty of room for improvements on scheduling when updates happen (e.g. "active hours" as currently designed isn't good enough IMHO), I don't see many complaints here about change or the frequency of updates. Complaints are quite rightly that the software was working before it was updated, and then afterwards it ranges from flaky to utterly broken. I'm sure Microsoft is keenly aware of the complexities of updating billions of Windows devices globally, but the rest of us just want a hassle free update process and to get on with it. :) On 13 Dec 2017 13:09, "Stephen Price" <step...@lythixdesigns.com> wrote: What we are experiencing is not a new thing. Change is constant. Each new release of software, for all things, comes with new bug fixes, new bugs and new features. Some we need some we don't. The pain we are feeling is a combination of lack of control combined with the frequency of these changes. Once upon a time we had to wait several years for a new release (take Visual Studio as an example). Now we see new updates weekly and sometimes daily. Hopefully the pain we feel is shorter lived as a result. We can communicate with the Devs much easier now. Often we can see the name of the developer who checked in the code. We can comment on the codebase and raise issues. Take the recent icon colour change of VScode for example. For those who were not watching, they changed the colour to orange (or green depending on the branch). People were NOT happy. The Devs listened and in about a week or maybe two it was back to the familiar colour. Imagine having to wait 2 years to get your icon colour fixed or some other life altering bug. You can't make everyone happy all of the time. We are all at the whim of the developers of the code we use. If you don't like that, you have options. Feedback or change software. Or write your own. If you don't like something, change it. If you can't change it, change how you think of it. Hmm, might make this a blog post. On 13 Dec. 2017 9:10 am, David Connors <da...@connors.com> wrote: On Wed, 13 Dec 2017 at 10:08 Grant Maw <grant....@gmail.com> wrote: Never thought I'd ever see myself switching to Linux but I have to say that I'm starting to look very, very hard at it, for all the reasons that Mike and the Gregs have outlined above. I just wonder if I REALLY need to learn a new OS at my age ... life is too short :) I bought a chromebox on a lark a while back. It said it needed a new OS so I clicked reboot. OS installation and reboot was ~10 seconds. Le Sigh. I was boned by one of these updates in a customer meeting. It half installs before it wants to reboot and that took out my WiFi. Windows said it wanted to reboot - sure fine. 1 hour later... David. -- David Connors da...@connors.com | @davidconnors | https://t.me/davidconnors | LinkedIn | +61 417 189 363 <+61%20417%20189%20363>
