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 in. Honestly, using VS Code daily as part of my stack I'm leaning towards just accepting that WebView2/Electron/etc is the future.
I have read the complaints, but VS Code is a solid piece of engineering and it "just works". If that's an example of what we can easily get cross-platform, so be it.
And yet it had an issue for quite some time where animating the cursor flashing was taking an enormous percentage of CPU.
https://github.com/microsoft/vscode/issues/85971
Or how Rust is used for search via ripgrep.
Also do you consider that VSCode has higher performance requirements than XBox dashboard, or Office plugins?
Having a declarative rendering logic, a rendering runtime, the VDOM, diffing, re-rendering, update scheduling and everything else that React uses under the hood is always going to be slower than tailor-made imperative rendering.
And let's not even go down the rabbit hole which is concurrent mode and suspense, where React is going to be basically a black box more suited to quantum computing with the whole "render x times and settle on a result that it thinks is correct".
I'm not sure if it will take up more resources than the Xbox dashboard or office plugins, but I am willing to say "yes". The dashboard is quite simple compared to a full-fledged IDE which VScode is becoming, and I'm yet to see the whole Office suite, including the underlying logic, being ported to React Native.
Atom was ported to React at one point but they quickly abandoned it because of the bad performance. Microsoft followed suit and hasn't even bothered with React for VScode.
VSCode has a very technical user base that will complain a lot if there is any kind of sluggish performance when doing live debugging. It's not just to work on small JS projects anymore. I use it to debug CUDA kernels on several processes at the same time and a lot of people have similar push-it-to-the-limit use cases.
I work on very large and complex projects ... the current one I'm working with is a massive Angular 12 project.
The fact that it's Electron doesn't matter to me. I am not concerned with it "using much more memory than native" because that has no effect on me.
All I care about that it works, and that is is performant. It is both.
The rest of it is in hosting the processes and plug-ins for it. Microsoft also developed the Language Server Protocol that provides intellisense and other features for each language: https://microsoft.github.io/language-server-protocol/
So it's not so much the stack as the pure engineering time.
So...not a lot of Microsoft product in it. Ironic.
Anyways, try golang with imgui.
You can make imgui look like anything. Ontop of that, you get true cross platform binaries with native speeds with only a couple dozen lines of code and amazing dependancy management. If you've never done immediate mode front-ends, you'll be delighted.
It would be interesting to see older systems retasked to a free clone OS, potentially running most/all of the same software.
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.
The first thing we observe is that the directory structure is basically identical. Yes, NT kernel subsystems are identified with short codes like "Ke" or "Ex". It's plausible that someone with a lot of NT knowledge would end up creating top level directories with these exact names, as is true of the WRK. But it seems kind of unlikely: the Wine sources do not show this pattern.
If we look at the Kernel Executive (Ke) subtree, we can see that there is a thing called a "Balance Set Manager". Both source trees define it in a file called balmgr.c - not only the location of the file but also the file name is identical.
https://github.com/Zer0Mem0ry/ntoskrnl/blob/master/Ke/balmgr... https://github.com/reactos/reactos/blob/master/ntoskrnl/ke/b...
It appears from the module description that the "balance set manager" is an optimisation of some sort related to reducing memory usage. Is this really something that needs a reimplementation with identical function prototypes?
Looking at the code of the identically named KeBalanceSetManager function, we can see that not only is the function prototype identical, but the order in which it does things is also identical. First it changes a thread priority, then it schedules a periodic timer callback.
Some of the local variables in these functions have identical names: PeriodTimer, DueTime, WaitObjects. Yes, these are obvious names. It's not a smoking gun. But it's not looking good.
Finally we discover that the ReactOS Balance Manager does .... nothing. It enters a loop which starts out by doing a wait for an event (fine, it's inherent to the task), and then switches on the result. But the code in the arms of the switch are commented out (the commented out code does a subset of the stuff in the NT code). The loop does nothing, just sits blocking in a loop forever. Why does this code in ReactOS exist if it does nothing?
It's the same story for the other big function in this file, KiScanReadyQueues. The code is virtually identical, line for line, with minor formatting and occasional trivial naming differences. Even the assertions are identical.
I'm not alleging anything specific or illegal, just comparing a small part of both codebases. However given what I've just seen, I wouldn't touch ReactOS with a barge pole. The Microsoft guy's complaint is entirely understandable.
Someone put namespaced functions into a folder named after that namespace? If it wasn't for that classic C style filename I would have suggested a call to the K&R police for the most heinous crime of all: the attempt to write maintainable C code.
Wine also isn't providing driver API compatibility.
They took the huge effort of complete rewrite and clean room implementation just for that! So not only it would make no sense for them to cheat, it would mean actually harming the project and causing its demise. Nobody in their right mind would do so.
I want to play modern games but with the Windows 98 desktop experience.
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.
WinRT is the OS/2 of the 21st century.
On one side .NET Native is left to stagnate in C# 7, and C++/CX got replaced with C++/WinRT, which to this day (4 years later) still doesn't offer any kind of IDL tooling on VS (lets forget for a second that IDL exists since OLE 1.0), and requires manually merging generated files.
Then to top that, we get MAUI on top of WinUI, but with the XAML format used by Xamarin.
Anyone following the now 2100+ issues on Github, community calls, change of roadmap of what WinUI 3.0, Reunion and XAML Islands were supposed to be originally, and where they are going after Windows 11 announcement, can only be dismayed.
They don't seem to either get the complaints, or most likely, are stuck in a position where they cannot publicly acknowledge them.
OS/2 was actually much better than this with CSet++, while SOM had metaclasses and implementation inheritance, with Smalltalk and C++ support.
Still, I can equally well rant about other platforms, it is all a matter of which flaws we are willing to put up with.
Anyway, after a particularly awful project involving UWP and Forms UWP, I'm taking my vacation days and using them to learn Typescript, React, and Electron.
Edit: if you find yourself working at Microsoft on the WinUI or UWP teams, quitting is an option. There are many good products that could use your skills and programmer labor is in high demand.
The higher resolution a display is, the less and less you need anti-aliasing so it's unnecessary in the 4K and up era. Also while I am not on a 4K display, I find AA fonts blurry compared to nice crisp hinted non-AA fonts.
Remember, they did the same thing with Windows 10 a couple of times.
From https://www.pcworld.com/article/3623008/windows-11-faq-featu... rather than the horses mouth but I expect it is correct.
I'm glad I'm on unsupported hardware.
I'd like to be able to play the games I want to without worrying about being frog-marched into an OS without a taskbar.
At this point I would settle for a deny-then-allow solution involving dropping any and every packet that's not from the servers of the small handful of online games I play, any well-known wikis that cover the games I play, or any relevant modding sites.
> I'd like to be able to play the games I want to without worrying about being frog-marched into an OS without a taskbar.
Lutris/Steam with Proton works wonderfully nowaday!
The main caveat is if you enjoy multiplayer gaming, it often require extensive low-level access to your Windows environment for anti-cheating purposes. Wintendo is the correct approach in that case; VFIO is an option, but afaik some anti-cheat systems will detect that they're running inside a VM.
Most security concerns go out of the window (pun not intended) when the most sensitive information your OS has access to is your Steam account, which has 2FA against a separate non-Windows device.
But WinForms is immensely useful in building tools, and configuration utilities, and little one-off GUI things for various reasons. Anything that would take less time to slam together soup-to-nuts than just getting webpack working for a new project would take.
Just as example, companies that buy this kind of software,
Doing a 3D visualization for a LOB application? WPF can handle it.
Doing the same in UWP/WinUI? Ah the pour soul needs to go learn C++, C++/WinRT and DirectX then make use of SwapChainPanel, or trying to fit a third party .NET game engine into the application.
Then the team acts surprised that WPF has 3D capabilities when asked about this.
Apparently doing requirement analysis for what a replacement framework should cover wasn't part of the deal.
They had quite clear goals.
If they bring back Aero I'll be happy.
There is always hope ;-)
At this stage, the 3rd party gui libraries are looking better and better i.e. Electron.NET https://smackeyacky.blogspot.com/2021/08/electronnet-cross-p...
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.
At least Vista had a real start menu. Yeah, early Vista was rough, but by SP2 all the problems were fixed.
NT 3.51 — solid
NT 4.0, 2000 & XP — less, less and less solid
Vista — premature
7 — ok
8 — borked
10 & 11 — untouchable
XP - decent
Vista - horrorshow
7 - alright (compared to vista)
8 - Not too bad
8.1 - alright
10 - dumpster fire
11 - another dumpster fire
With Win 11 requiring SecureBoot and the Trusted Platform Module turned on, it is a hard no for me. I like having control over my PC.
9x - please no!
2000 - great
ME - oh god, make it stop!
ME was not an upgrade path from 2000 even though it came out after 2000, it was an upgrade path for 98.
It's possible that MS will just force-update everyone to Windows 11.
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 pushing Blazor everywhere including on Web Widgets.
I will just wait for Windows 12, whenever it comes up, the UI war will be settled by then.