Hey Steve, you have to be happy with change. That’s the nature of this industry.
But it’s the lack of control over when that occurs is the problem, coupled with the fact that it routinely breaks things. That’s the issue. If it almost always worked and didn’t break things, no problems. Having a setup where relatively randomly, your machine is broken for you, no matter what you were in the middle of doing, or what you thought you needed to be using the machine for, is not cool. Also not cool was when they changed my “connect when I decide to” internal broadband modem to “Windows will manage this” and turning it on automatically as part of the upgrade, when I was in Europe and paying extortionate data roaming charges on that modem, is also an example of not cool. 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:* [email protected] [mailto:[email protected]] *On Behalf Of *Stephen Price *Sent:* Wednesday, 13 December 2017 2:09 PM *To:* ozDotNet <[email protected]> *Subject:* Re: [OT] Big Windows 10 update 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 <[email protected]> wrote: On Wed, 13 Dec 2017 at 10:08 Grant Maw <[email protected]> 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 [email protected] | @davidconnors | https://t.me/davidconnors | LinkedIn | +61 417 189 363
