Re:Windows 10: Microsoft launches intrusive full-screen upgr...
by cm2187 on Monday July 04, 2016 @11:02AM
(#12031159)
Two control panels with settings scattered all over the OS, privacy invasion, in-OS advertising, frequent forced reboots, and more generally, inability to turn down future OS features. Keep in mind the "geniuses" who came up with Windows 10 are also the idiots who came up with Windows 8: contextual menu at the bottom of the screen, very very far from where the mouse is when it clicked, full screen everything (at the age of 4k monitors...why???), hiding the option to create local windows account behind several layers of non obvious opt-out buttons, etc. If these guys take the same moronic design decisions, they will flow through your OS update whether you like them or not. And if Microsoft wants to launch Candy Crush Soda on every start up, there might be nothing you can do to prevent it.
[ Parent
| on HN ]
Re:Windows 10: Microsoft launches intrusive full-screen upgr...
by Redoubts on Monday July 04, 2016 @03:27PM
(#12032523)
> Two control panels with settings scattered all over the OS
I still don't understand this. What's the point of a UI refresh if you're going to do it really half-assed.
Re:Windows 10: Microsoft launches intrusive full-screen upgr...
by cm2187 on Monday July 04, 2016 @03:32PM
(#12032550)
I have the feeling it is more half-baked than half-assed. I have no doubt they will unite them at one point. I just find surprising they would ship a half finished product like that, particularly given that it wouldn't take very long to an intern to redesign these few forms.
Re:Windows 10: Microsoft launches intrusive full-screen upgr...
by ayuvar on Monday July 04, 2016 @08:17PM
(#12033718)
It's by far my biggest complaint. There are even issues where one control panel does one set of features and the settings window does a whole different set.
I also had a sticky problem where it was convinced I had a Canadian French keyboard even after deleting it from both keyboard control panels. I ended up having to solve that with a registry modification.