I have to agree, even though I have plenty of pro-Windows comments. To me Windows 11 feels like Vista, and to everyone that got burned with the rewrites on the WinRT side, just using plain Win32/MFC/Forms/WPF feels liberating. Multiple teams are fighting UI politics over WinUI, MAUI on top of WinUI, React Native with WinUI, and classical UWP is not going away (Windows 11 Store is written in it), then ASP.NET team is…
Winforms will never die. If I was looking to make an investment into a skillset that will still be really useful in thirty years, I would go deep on WinForms.
Windows 11: Just say no
431–440 of 539 posts
Re: Windows 11: Just say no
#432It works just nice, but it has the 1 thing that drives me crazy - rounded corners! WTH Microsoft, you could at least has an option to toggle it - I really loved the square UI of Windows 10... :|
Re: Windows 11: Just say no
#433Earlier quoted context omitted.
It's definitely a big problem with software. This "need to constantly pay developers" is part of the justification for moving towards subscription payment instead of one-time payment. The logic goes: One-time payment won't pay for future changes, and developers are always making changes, and they need to be paid for. But, what if I don't want future changes? For almost all software I've ever paid for, as a user, I ju…
Funny, I was just thinking to myself that maybe a paid subscription Windows could be a solution to undesired UI change. Because it would take away the lure of the upgrade sale licence. 64 bit w2k? Yeah, I'd totally pay for that. If I were in charge of Windows product strategy I think I would create competing subdivisions that replicate the model of Linux distributions but on the NT kernel. Sworn to binary compatibili…
Re: Windows 11: Just say no
#434Earlier quoted context omitted.
They won't let it happen. For now they decided to just ignore the project and not give it any publicity, but the moment it gains popularity, they will definitely react. Until now they attacked it indirectly through their kernel developer saying ReactOS stole his code - in spite of the fact they took all necessary measures not to and underwent an audit. This is the same old strategy Microsoft supported during the SCO…
i thought reactos contained portions of windows NT code?
Moreover, you know it is the biggest danger and the main avenue Microsoft will attack you in the future, so you are extremely careful never to do anything even remotely illegal. When someone sends you links to fragments of Windows source code, you politely but firmly answer you are not allowed to look at this code. Because you know that if you look at it even once, an evidence of that could be used against you in court - and you are competing against the most important product of one of the richest corporations in the world, so you can't let yourself to be sloppy.
Re: Windows 11: Just say no
#435Earlier quoted context omitted.
> Why do they keep messing with the UI? UX folks don't get paid to leave things alone.
Nobody gets paid to leave things alone and maybe that's a big problem with the world.
Re: Windows 11: Just say no
#436Earlier quoted context omitted.
I wonder if ReactOS will hit 1.0 by the time that Windows 10 goes out of support in 2024. It would be interesting to see older systems retasked to a free clone OS, potentially running most/all of the same software. https://reactos.org/project-news/reactos-in-2020/
Doesn't ReactOS use the libraries from wine? So you could just run Linux.
It's an admirable project, though of course it's nowhere near ready for use. Currently ReactOS doesn't run on a lot of real hardware, and is still well behind WinXP in terms of hardware support (USB memory sticks don't work, USB keyboards have problems, Wifi has minimal support and only for open networks, etc), but the goals of ReactOS are very different from Wine.
Re: Windows 11: Just say no
#437Re: Windows 11: Just say no
#438Proton[1] is the reason my next machine will be Linux. [1]: https://www.protondb.com/
Re: Windows 11: Just say no
#439Earlier quoted context omitted.
Eh, I don't agree. NT 3.51 — solid NT 4.0, 2000 & XP — less, less and less solid Vista — premature 7 — ok 8 — borked 10 & 11 — untouchable
2000 was pretty good really, more solid than 3.51 even
Re: Windows 11: Just say no
#440Earlier quoted context omitted.
> Even Apple and Google have both figured out that screwing around with UX every release is a recipe for making your customers HATE you. ...are we talking about the same Apple and Google? Big Sur? Material You? Sure, maybe it’s not “every” release, but only because they have a faster release cadence than Windows.
I don’t know about Google but I would say that the majority of Apple’s design refreshes are iterative in such a way that someone coming from the previous release is very unlikely to get “lost” when presented with the latest UI. And this is the key. UI refreshes are fine as long as they don’t add unnecessary friction to the user experience. Apple’s refreshes are also generally complete, cohesive and coherent. Yes they…
There are a couple of Google IO sessions where the presenter goes through how to custom write Android views to match Material.
Then a couple of years of comunity complaints they released a Material custom theme for Android that still doesn't implement 1:1 their UI/UX specification.
When this framework was finally catching up with Material documentation, they release Material You.