3 ms·
> It means I know where the switches are, and more importantly, what they do Does that mean you would never be comfortable with with a complete UI overhaul? >
by x3haloed 7y ago
> It means I know where the switches are, and more importantly, what they do
Does that mean you would never be comfortable with with a complete UI overhaul?
> The new UIs change with every minor update
I completely agree that this is a problem. And this part of my biggest issue with Windows 10. They're constantly reworking the new UI for what seems like micro-optimizations, but they're mostly ignoring the old UI. Not only is it a headache for users to keep up with new paradigms every 6 months, but there continues to be two areas in Windows to control system settings, one of which is hidden pretty well, and the location of settings between the two is continually changing. It's a nightmare.
.NET Core, on the other hand, is pure gold. It's fast, it runs everywhere, it's well document, and it's a joy to work with.
Which leads us to Visual Studio, which is becoming like Windows. Constant tweak updates that break things. I stopped installing '.0' releases, beacsue they're consistently broken.
- Faark 7y ago> Does that mean you would never be comfortable with with a complete UI overhaul? I'd like for the old interface to be still around, so I can click though the nav layers like I always have. At the end, instead of the information / setting I'm looking for, I'd be fine with info on how now to find that info/setting. This "tutorial" should obviously be kept up to date on later UI changes. It also requires the info/setting to still be available... so no dumbing-down please.