News for hackers. Stuff that matters.
Re:Windows 11: Just say no by pjmlp on Thursday September 16, 2021 @03:02PM (#28555828)
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 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.

Re:Windows 11: Just say no by EMM_386 on Thursday September 16, 2021 @03:52PM (#28556588)
> 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 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.

Re:Windows 11: Just say no by thrower123 on Thursday September 16, 2021 @04:12PM (#28556873)
VS Code is like the absolute greatest Electron app that has ever, or will ever be written.

And yet it had an issue for quite some time where animating the cursor flashing was taking an enormous percentage of CPU.

Re:Windows 11: Just say no by pjmlp on Thursday September 16, 2021 @04:30PM (#28557123)
It is also one that has big chunks of C++ and Rust code, and WebGL based rendering to make it actually usable.
Re:Windows 11: Just say no by 0-_-0 on Thursday September 16, 2021 @05:57PM (#28558232)
Oh you can do that with Electron? This is not my area of expertise... Are there any other ways to have GPU acceleration?
Re:Windows 11: Just say no by pjmlp on Thursday September 16, 2021 @06:30PM (#28558615)
Here how WebGL is used for the terminal in VSCode,

https://github.com/microsoft/vscode/issues/85971

Or how Rust is used for search via ripgrep.

https://github.com/microsoft/vscode-ripgrep

Re:Windows 11: Just say no by bool3max on Wednesday September 29, 2021 @04:14PM (#28699294)
Rendering webpages is already GPU-accelerated by default in most browsers and platforms.
Re:Windows 11: Just say no by greggturkington on Thursday September 16, 2021 @05:41PM (#28558044)
To be fair it was partially related to a bug in Chromium, and was fixed in 2017

https://github.com/Microsoft/vscode/issues/22900

Re:Windows 11: Just say no by pjmlp on Thursday September 16, 2021 @04:09PM (#28556830)
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.
Re:Windows 11: Just say no by v413 on Thursday September 16, 2021 @04:41PM (#28557266)
React is slow for the perf targets of VSCode.
Re:Windows 11: Just say no by pjmlp on Thursday September 16, 2021 @04:58PM (#28557507)
React Native != React.

Also do you consider that VSCode has higher performance requirements than XBox dashboard, or Office plugins?

Re:Windows 11: Just say no by baxuz on Friday September 17, 2021 @03:42AM (#28562414)
It's still React, and it's still too slow. The only difference is where the render is committed to (DOM vs Native UI)

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.

Re:Windows 11: Just say no by pjmlp on Friday September 17, 2021 @04:03AM (#28562557)
Ah, that is why Teams dropped Electron for React Native!
Re:Windows 11: Just say no by DragoCubed on Friday October 01, 2021 @02:55AM (#28715455)
Microsoft Teams? No they didn't drop Electron for RN/RNW. They dropped Electron for Microsoft Edge WebView2. I might be missing some sarcasm though
Re:Windows 11: Just say no by belval on Thursday September 16, 2021 @09:02PM (#28559834)
No commenting on the React thing, but yes I do think that VSCode has much higher performance requirements than Xbox dashboard or Office plugins.

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.

Re:Windows 11: Just say no by pjmlp on Friday September 17, 2021 @02:00AM (#28561793)
If the user base was that technical, with performance requirements, they wouldn't be using an Electron based product to start with, when there are plenty of other native alternatives, including for CUDA debugging from Nvidia themselves.
Re:Windows 11: Just say no by EMM_386 on Friday September 17, 2021 @08:03AM (#28564439)
I have over 2 decades in this industry and have used almost every IDE that exists.

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.

Re:Windows 11: Just say no by tacker2000 on Thursday September 16, 2021 @05:00PM (#28557524)
Yea vscode is really great! Could someone knowledgeable give a rundown of the exact stack/frameworks/etc they are using?
Re:Windows 11: Just say no by manigandham on Thursday September 16, 2021 @11:27PM (#28560868)
Take a look at Monaco, the editor that powers VSC: https://microsoft.github.io/monaco-editor/

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/

Re:Windows 11: Just say no by kyrra on Thursday September 16, 2021 @10:18PM (#28560490)
I can't remember where I saw the post, but the reason it's such a fast product is that they put a large amount of time into performance analysis and fixing those issues.

So it's not so much the stack as the pure engineering time.

Re:Windows 11: Just say no by smackeyacky on Thursday September 16, 2021 @08:21PM (#28559574)
AFAIK it's Electron (i.e. javascript, chrome as the renderer, node.js I think looking at the processes).

So...not a lot of Microsoft product in it. Ironic.

Re:Windows 11: Just say no by fartcannon on Thursday September 16, 2021 @10:28PM (#28560559)
It's chock full of Microsoft's telemetry!
Re:Windows 11: Just say no by arriu on Thursday September 16, 2021 @04:11PM (#28556861)
I'm going to get down voted for this, I realize it isn't for everyone... If it's not for you, no problem. Let me know what you prefer.

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.

Re:Windows 11: Just say no by kertoip_1 on Thursday September 16, 2021 @05:18PM (#28557760)
From what I see it's the kind of library for people preferring usability over good looking appearance. Of course you can make it "look like anything", but sane defaults are also important for rapid software development and this definitely lack them
Re:Windows 11: Just say no by dgellow on Friday September 17, 2021 @02:57AM (#28562118)
If you’re already used to WPF then you can continue using it. You don’t have to switch to something else.
Re:Windows 11: Just say no by chasil on Thursday September 16, 2021 @03:32PM (#28556256)
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/

Re:Windows 11: Just say no by hdjjhhvvhga on Thursday September 16, 2021 @03:40PM (#28556397)
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 trial.
Re:Windows 11: Just say no by aliswe on Thursday September 16, 2021 @05:02PM (#28557557)
i thought reactos contained portions of windows NT code?
Re:Windows 11: Just say no by hdjjhhvvhga on Friday September 17, 2021 @04:21AM (#28562680)
No. Imagine you are a ReactOS (or Wine etc.) developer. The main thing you can't do is to use any code you are trying to reimplement. It literally contradicts the very aim of your project: to create a legal viable alternative to a proprietary system.

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 by aliswe on Friday September 17, 2021 @04:52AM (#28562880)
This is part of what I read on HN:

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.

https://news.ycombinator.com/item?id=20345645

Re:Windows 11: Just say no by josefx on Monday September 20, 2021 @06:54AM (#28592330)
> 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.

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.

Re:Windows 11: Just say no by hdjjhhvvhga on Friday September 17, 2021 @06:49AM (#28563747)
Yes, I remember that discussion, it was very interesting, but it was quickly became obvious that the whole thing is very nuanced, and what may seem too much of a coincidence for an outsider (comparing the codebase of stolen or licensed source code of Windows with React OS), it could have a very rational explanation.

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.

Re:Windows 11: Just say no by amyjess on Thursday September 16, 2021 @06:55PM (#28558851)
I'd settle for being able to delete explorer.exe from my system and put the ReactOS shell in its place.

I want to play modern games but with the Windows 98 desktop experience.

Re:Windows 11: Just say no by pantalaimon on Thursday September 16, 2021 @07:49PM (#28559318)
Doesn't ReactOS use the libraries from wine? So you could just run Linux.
Re:Windows 11: Just say no by ACS_Solver on Friday September 17, 2021 @04:34AM (#28562763)
The point of ReactOS is driver-level compatibility with Windows. The project implements their own equivalent of things like the Windows HAL or Windows Driver Model, which ideally should mean ReactOS can be a drop-in replacement for old Windows machines used to run some piece of hardware that only has a Windows driver. There are still industrial machines being driven over parallel port by WinXP. The Win32 API program used for controlling the machine most likely works just fine with Wine, but the necessary driver definitely doesn't. The ultimate goal of ReactOS is that you could just install the driver on it and thus control the industrial machine exactly like WinXP did it.

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 by itronitron on Thursday September 16, 2021 @06:04PM (#28558309)
I like Windows, and I would prefer to keep everyone in my family running Windows, but Windows 10 just doesn't work as smoothly as it should considering the resources that Microsoft should be able to throw at it. Due to various latency issues in Windows 10, it feels like it was written by a couple of developers that don't fully understand the api/framework they are using. This should be their wheelhouse, since it is their OS, but it feels cobbled together. So I am slowly migrating my family to Linux as I don't have much confidence that MS will fix their shit.
Re:Windows 11: Just say no by GnarfGnarf on Thursday September 16, 2021 @03:20PM (#28556068)
I migrated from Win32 to Qt two years ago. Never looked back. Much easier to program dialogs & UI. Qt gives you macOS as well. (And UWP if you insist).

WinRT is the OS/2 of the 21st century.

Re:Windows 11: Just say no by pjmlp on Thursday September 16, 2021 @04:22PM (#28557020)
WinRT looked great, finally .NET being like Delphi and a C++ stack that looked like C++ Builder, for those moments that .NET alone won't do it.

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.

Re:Windows 11: Just say no by n8cpdx on Thursday September 16, 2021 @09:57PM (#28560330)
I think there's a degree of denial. I remember walking up to an engineer on the WinUI team at Build (can't remember if 2018 or 2019) and they were _shocked_ that I had complaints about UWP. They seemed to think it was a revelation. It was honestly offensive how out of touch she was. I think at least the PMs on that team do not understand the human suffering they cause by releasing such a bad product.

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.

Re:Windows 11: Just say no by pjmlp on Friday September 17, 2021 @02:29AM (#28561950)
I guess you have put it quite well.
Re:Windows 11: Just say no by Sunspark on Thursday September 16, 2021 @03:38PM (#28556342)
I have some concerns with Qt. Not the functionality, but the implementation of some of it. My primary concern is that it doesn't respect the OS's anti-aliasing settings. It defaults to making fonts anti-aliased, even if you don't want them to be. Because of this, last year I stopped updating an app using Qt.

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.

Re:Windows 11: Just say no by mark-r on Thursday September 16, 2021 @10:25PM (#28560543)
As you get higher in resolution, I'd expect the difference between AA and non-AA to get less noticeable. Is that not the case?
Re:Windows 11: Just say no by jhgb on Friday September 17, 2021 @08:27AM (#28564645)
Have you tried Ultimate++, by any chance?
Re:Windows 11: Just say no by nyanpasu64 on Friday September 17, 2021 @02:02AM (#28561808)
What OS and DPI are you on?
Re:Windows 11: Just say no by N00bN00b on Thursday September 16, 2021 @06:47PM (#28558783)
Wouldn't surprise me if you reboot your computer one day and surprise! It's windows 11 now!

Remember, they did the same thing with Windows 10 a couple of times.

Re:Windows 11: Just say no by tonyedgecombe on Friday September 17, 2021 @03:39AM (#28562396)
"As a free replacement for Windows 10, your PC will upgrade to Windows 11 automatically."

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.

Re:Windows 11: Just say no by amyjess on Thursday September 16, 2021 @06:56PM (#28558862)
Welp, time to start dropping every packet from any Windows Update-related IP block in my router...
Re:Windows 11: Just say no by harry8 on Thursday September 16, 2021 @08:31PM (#28559639)
Seriously if you're genuine about that it's such a temporary solution. You're saying you can't trust your operating system vendor at all. Start making plans to dump them is really the only sane thing to do at that point.
Re:Windows 11: Just say no by amyjess on Thursday September 16, 2021 @09:07PM (#28559869)
I use Linux for most things and only boot into Windows for games. Wintendo is a real thing.

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.

Re:Windows 11: Just say no by piaste on Friday September 17, 2021 @06:09AM (#28563406)
> I use Linux for most things and only boot into Windows for games. Wintendo is a real thing.

> 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.

Re:Windows 11: Just say no by aceazzameen on Thursday September 16, 2021 @11:44PM (#28560970)
Since my PC is on wifi, what I do is set my wifi as a metered connection. Windows won't download updates on metered connections. I have to trigger the updates manually, which allows me to review them first. Like how it used to be.
Re:Windows 11: Just say no by scns on Friday September 17, 2021 @08:20AM (#28564574)
Nifty trick, thanks for sharing. Will be useful to many readers. Including those booting into W10 1% of the time, for SD-Card formatters and other Windows exclusives.
Re:Windows 11: Just say no by thrower123 on Thursday September 16, 2021 @03:26PM (#28556165)
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.
Re:Windows 11: Just say no by js4ever on Thursday September 16, 2021 @04:11PM (#28556858)
Hum, my last winform app is from 2009, after that all projects ordered from customers where in web ui instead (same customers)
Re:Windows 11: Just say no by thrower123 on Thursday September 16, 2021 @04:16PM (#28556923)
All of my real products are web-based.

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.

Re:Windows 11: Just say no by pjmlp on Thursday September 16, 2021 @04:33PM (#28557167)
My last one is from 2016, now I am mostly doing other stuff, but there are plenty of places that still are quite into this kind of frameworks.

Just as example, companies that buy this kind of software,

https://perkinelmerinformatics.com/

Re:Windows 11: Just say no by slowmotiony on Friday September 17, 2021 @04:16AM (#28562649)
WinForms or COBOL. You'll be set for life :-)
Re:Windows 11: Just say no by int_19h on Thursday September 16, 2021 @09:11PM (#28559909)
At this point, WPF won't die, either.
Re:Windows 11: Just say no by pjmlp on Friday September 17, 2021 @02:33AM (#28561973)
And has lots of features that WinUI or UWP will never get.

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.

Re:Windows 11: Just say no by m_mueller on Friday September 17, 2021 @01:57AM (#28561777)
IMO the UI war is settled by now. It‘s either CLI or a web interface of some sort. Everything else just seems like asking for trouble nowadays.
Re:Windows 11: Just say no by int_19h on Thursday September 16, 2021 @09:08PM (#28559875)
The UI war predates WinRT - remember Silverlight? Or, for that matter, WPF itself. So why would you expect it to be over?
Re:Windows 11: Just say no by pjmlp on Friday September 17, 2021 @04:06AM (#28562581)
Silverlight was a response to Flash, and WPF was Forms replacement out of Longhorn's UI.

They had quite clear goals.

Re:Windows 11: Just say no by strictnein on Thursday September 16, 2021 @05:13PM (#28557705)
> To me Windows 11 feels like Vista

If they bring back Aero I'll be happy.

Re:Windows 11: Just say no by Gys on Thursday September 16, 2021 @04:25PM (#28557070)
> I will just wait for Windows 12, whenever it comes up, the UI war will be settled by then.

There is always hope ;-)

Re:Windows 11: Just say no by smackeyacky on Thursday September 16, 2021 @08:29PM (#28559626)
They've had 4 years to settle on a GUI for .NET Core and completely failed.

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...

Re:Windows 11: Just say no by pjmlp on Friday September 17, 2021 @06:12AM (#28563435)
Here is the joke, MAUI with incompatible XAML is now delayed to post .NET 6 release, while with UNO you can go cross platform today, on .NET 6 and without having to rewrite XAML yet again.
Re:Windows 11: Just say no by smackeyacky on Friday September 17, 2021 @01:14PM (#28568036)
I will go take another look at UNO then.
Re:Windows 11: Just say no by ZuLuuuuuu on Friday September 17, 2021 @11:02AM (#28566267)
I can't even track these UI techs anymore. I thought WinUI is the new version of the UI layer of UWP and all apps who use WinUI are actually still considered UWP apps? I genuinely don't know, can somebody enlighten me?
Re:Windows 11: Just say no by jnsaff2 on Thursday September 16, 2021 @04:08PM (#28556815)
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.

Re:Windows 11: Just say no by amyjess on Thursday September 16, 2021 @06:56PM (#28558872)
Vista SP2 was better than 7.

At least Vista had a real start menu. Yeah, early Vista was rough, but by SP2 all the problems were fixed.

Re:Windows 11: Just say no by Koshkin on Thursday September 16, 2021 @06:11PM (#28558396)
FWIW, it’s “tick-tock.”
Re:Windows 11: Just say no by Paianni on Thursday September 16, 2021 @05:42PM (#28558052)
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

Re:Windows 11: Just say no by Dork1234 on Thursday September 16, 2021 @07:39PM (#28559235)
This cycle doesn't work anymore. Windows 10 wasn't a normal release, it has been around for 6 years, and has at least 3 major updates(with many small ones). Windows 7 was around for ~3 years, and had one update before it was replaced with Windows 8.
Re:Windows 11: Just say no by gpvos on Thursday September 16, 2021 @06:27PM (#28558593)
2000 was pretty good really, more solid than 3.51 even
Re:Windows 11: Just say no by Paianni on Friday September 17, 2021 @04:39AM (#28562799)
I hear the era of GDI being run in kernel mode was...not good for stability or security, but I rarely used 2000 and never used NT 4.0 so perhaps there are better mouthpieces than myself.
Re:Windows 11: Just say no by gpvos on Friday September 17, 2021 @08:08AM (#28564483)
By W2K a lot of problems had been fixed, and on the other hand 3.51 was still a bit early and wobbly in other areas. I thought GDI was still in the kernel?
Re:Windows 11: Just say no by Paianni on Saturday September 18, 2021 @08:28AM (#28575687)
Well Vista removed support for kernel-mode printer drivers (https://docs.microsoft.com/en-us/windows-hardware/drivers/pr...), Vista introduced the WDDM model for video drivers in user-mode, 8 removed support for XDDM so I guess one could say that by 8, things had come full circle.
Re:Windows 11: Just say no by hef19898 on Thursday September 16, 2021 @04:20PM (#28556998)
That! It started before XP so...
Re:Windows 11: Just say no by Zardoz84 on Thursday September 16, 2021 @04:58PM (#28557504)
Allow to fix your list :

XP - decent

Vista - horrorshow

7 - alright (compared to vista)

8 - Not too bad

8.1 - alright

10 - dumpster fire

11 - another dumpster fire

Re:Windows 11: Just say no by pitay on Friday September 17, 2021 @09:05AM (#28564997)
I completely agree with this list. Although Windows 8 had a bad desktop UI, it was easily mostly fixed with Classic Shell at the time (these days it is Open Shell as Classic Shell is not updated any more). What Windows 10 has now is a better UI, but it has all this background stuff and telemetry which screws any performance for long periods of time, other times it is fine. But I have had to have performance monitoring tools open all the time to see what is going through my hard drive. It is that bad that I have resource monitor open all the time, just out of habit, because of how often there is Windows telemetry stuff or update medic service or even stuff which tries to measure power usage of programs in Windows when I am running it on a desktop. This is all stuff built into Windows installed by Microsoft, not 3rd party stuff. I have been able to deal with this by bypassing the haphazard protections MS put into place to stop me turning that stuff off, if they truly manage to stop me using my PC the way I want, not allowing me to disable the stuff I don't like, then it will become to unbearable to use Windows. The only reason it isn't unbearable is the protections against turning stuff off can be bypassed (not that they haven't tried to stop it).

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.

Re:Windows 11: Just say no by tartoran on Thursday September 16, 2021 @07:26PM (#28559113)
Yes, W10 is/was kindof a garbage. W11 is going to be worse. The only reason I still use Win is for work purposes, otherwise I wouldn’t touch it with a 10 foot pole
Re:Windows 11: Just say no by dmitrygr on Thursday September 16, 2021 @04:41PM (#28557264)
and even before:

9x - please no!

2000 - great

ME - oh god, make it stop!

Re:Windows 11: Just say no by genewitch on Thursday September 16, 2021 @05:04PM (#28557580)
95 was a paradigm shift, 98 had batteries included for the internet, but 98se and 2000 server are the best OSes MS ever put out.
Re:Windows 11: Just say no by Jtsummers on Thursday September 16, 2021 @05:15PM (#28557726)
95/98/ME were operating on a different kernel than the NT line (which 2000 fell under). The difference really being that the NT kernel was targeting pretty much exclusively businesses, while the 9x line was targeting home users and some business users. They merged (with the NT kernel winning out) in XP, which targeted both home and business users.

ME was not an upgrade path from 2000 even though it came out after 2000, it was an upgrade path for 98.

Re:Windows 11: Just say no by meijer on Friday September 17, 2021 @03:57AM (#28562519)
I hope we will be able to wait for Windows 12.

It's possible that MS will just force-update everyone to Windows 11.

Re:Windows 11: Just say no by mycall on Thursday September 16, 2021 @10:38PM (#28560623)
I think MAUI Blazor App + Blazor Website + shared libs is the way to go.
Re:Windows 11: Just say no by tonyedgecombe on Friday September 17, 2021 @03:44AM (#28562427)
Until they decide to change strategy again in two years time at which point the existing stuff will be abandoned in a half finished state.
Re:Windows 11: Just say no by dgellow on Friday September 17, 2021 @03:00AM (#28562139)
That’s not clear at all. Blazer is still very niche.