What if they lock the next version of DirectX behind Windows 11?
Windows 11 is going over like a lead balloon in the enthusiast gaming community, so the will is there.
101–110 of 539 posts
What if they lock the next version of DirectX behind Windows 11?
Windows 11 is going over like a lead balloon in the enthusiast gaming community, so the will is there.
Earlier quoted context omitted.
and UI elements that haven't been updated since Windows 2K. Also known as "the good part"... Everything else about Windows UI since then has only gotten less usable and more hostile.
This is what drives me nuts. Why do they keep messing with the UI? Nobody wants that! Even Apple and Google have both figured out that screwing around with UX every release is a recipe for making your customers HATE you. What I, and probably non-power users want out of windows is for it to be faster and use less power. I'd honestly be happy to go back to a Win95 interface with the latest kernel. Microsoft needs to fi…
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…
This is M$ doing its tik-tok releases. XP - decent Vista - horrorshow 7 - alright (compared to vista) 8 - horrorshow 10 - alright (compared to 8) 11 - horrorshow Personally I will never use it unless I really need to and then kicking and screaming but that is my observation.
XP - decent
Vista - horrorshow
7 - alright (compared to vista)
8 - Not too bad
8.1 - alright
10 - dumpster fire
11 - another dumpster fire
Earlier quoted context omitted.
I would rather see them rewrite VSCode in React Native, given all the love it is getting from Office and XBox teams, but lets see if it ever happens.
React is slow for the perf targets of VSCode.
Also do you consider that VSCode has higher performance requirements than XBox dashboard, or Office plugins?
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…
> 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 pushing Blazor everywhere including on Web Widgets. Great point. As a developer in the Windows sphere for decades, I'm used to change. However, at this point I have no idea what I am supposed to be developing user interfaces…
Earlier quoted context omitted.
My favorite is when I see the result I want flash by and then I accidentally type the next character -- correctly -- due to momentum, and the result disappears. Then I delete the last character in an attempt to bring back the result, and then I try retyping the whole thing, but the correct result never reappears. It is gone. Only useless web results remain.
Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Search] "BingSearchEnabled"=dword:00000000 "CortanaConsent"=dword:00000000 ^ put this into a .reg file, run it, and never see those bullshit web search results again. Have been doing this first thing after a fresh install on every PC.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Search]
"ConnectedSearchUseWebOverMeteredConnections"=dword:00000000
"AllowCortana"=dword:00000000
"DisableWebSearch"=dword:00000001
"ConnectedSearchUseWeb"=dword:00000000
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Search]
"CortanaConsent"=dword:00000000
"BingSearchEnabled"=dword:00000000
"AllowSearchToUseLocation"=dword:00000000Earlier quoted context omitted.
This is what drives me nuts. Why do they keep messing with the UI? Nobody wants that! Even Apple and Google have both figured out that screwing around with UX every release is a recipe for making your customers HATE you. What I, and probably non-power users want out of windows is for it to be faster and use less power. I'd honestly be happy to go back to a Win95 interface with the latest kernel. Microsoft needs to fi…
> It's not broke, stop trying to fix it. There could have been better ways to keep it modern, but just leaving everything alone because “it works” isn’t really an option. First comes Unicode, then 4K/High-dpi scaling, then touch support and so on. Once high DPI screens arrived, UIs that scaled poorly literally don’t work.
Earlier quoted context omitted.
> and UI elements that haven't been updated since Windows 2K. Windows 2K + cleartype would be perfect.
Plus individual screen dpi scaling from whenever that was. And the usb handling from win10. Oh and the audio device switcher is so much better in w10 than w7. Actually people seem to focus a lot on UX but in terms of the core features (handling my hardware and managing processes) windows has improved a lot . I also fondly remember win2k but I think it would be absolutely awful to use now.
Earlier 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/
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…