News for hackers. Stuff that matters.
Re:First Rust Code Shows Up in the Windows 11 Kernel by gjsman-1000 on Friday May 12, 2023 @10:18PM (#35924822)
Windows under the hood with the NT Kernel is actually regarded among some experts as technically superior to Linux with the driver model and personalities subsystem; it’s just that the stuff above the kernel isn’t so great…
Re:First Rust Code Shows Up in the Windows 11 Kernel by LeFantome on Friday May 12, 2023 @10:34PM (#35924917)
VMS under the hood
Re:First Rust Code Shows Up in the Windows 11 Kernel by waboremo on Friday May 12, 2023 @10:51PM (#35925026)
The one place microsoft's advertising branch can't get to!
Re:First Rust Code Shows Up in the Windows 11 Kernel by photonbeam on Friday May 12, 2023 @11:27PM (#35925190)
For now

Syscalls powered by MSNBC

Re:First Rust Code Shows Up in the Windows 11 Kernel by streakfix on Saturday May 13, 2023 @01:41AM (#35925919)
Their scheduler is pure bullcrap. It favors cpu intensive applications, meaning it's good for gaming but horrible for every other use case
Re:First Rust Code Shows Up in the Windows 11 Kernel by PaulRobinson on Saturday May 13, 2023 @01:56AM (#35925988)
That makes sense if your main target use case is desktops where a small number of CPU-intensive apps are running, right? And even in many server apps where you have one main app being the reason the server is booted, this makes broad sense.

Don’t get my wrong, but me and I bleed Unix-like systems and have done for decades, but what you’re saying actually makes sense for MS as a design decision…

Re:First Rust Code Shows Up in the Windows 11 Kernel by AlexSW on Saturday May 13, 2023 @02:33AM (#35926166)
How so? I believe I understand Windows' thread scheduler and this conclusion isn't obvious to me at all; from my understanding it seemed perfectly reasonable.
Re:First Rust Code Shows Up in the Windows 11 Kernel by streakfix on Saturday May 13, 2023 @03:44AM (#35926458)
Put windows on a 4 core system. Open two terminals. Run cargo build in one terminal. Run ls in the other terminal.ls will hang for a good 10 seconds before printing output
Re:First Rust Code Shows Up in the Windows 11 Kernel by pjmlp on Saturday May 13, 2023 @02:43AM (#35926205)
I would agree, if we would still be talking about Windows NT 4.0 or Windows 2000.
Re:First Rust Code Shows Up in the Windows 11 Kernel by yukIttEft on Saturday May 13, 2023 @01:21AM (#35925833)
Citations needed.
Re:First Rust Code Shows Up in the Windows 11 Kernel by toyg on Saturday May 13, 2023 @02:01AM (#35926011)
The stuff above is actually pretty good, the problems come mostly from the obsession with supporting a flawed 30-year-old paradigm (the DOS world with its simpleton prompt), a failed system-management concept (the Registry), and the recent steer towards being adware.
Re:First Rust Code Shows Up in the Windows 11 Kernel by Xeamek on Saturday May 13, 2023 @02:09AM (#35926053)
Why is the Registry a failed concept?
Re:First Rust Code Shows Up in the Windows 11 Kernel by doodlesdev on Saturday May 13, 2023 @02:32AM (#35926152)
It tries to be both a filesystem and a database and fails miserably at both. Entries layout is a total mess that not even Microsoft pays attention to anymore.

Relevant:

Why the Windows Registry sucks … technically https://news.ycombinator.com/item?id=32275078

https://rwmj.wordpress.com/2010/02/18/why-the-windows-regist...

Re:First Rust Code Shows Up in the Windows 11 Kernel by pjmlp on Saturday May 13, 2023 @02:42AM (#35926200)
Yet, the GNOME folks decided to copy it.
Re:First Rust Code Shows Up in the Windows 11 Kernel by toyg on Saturday May 13, 2023 @04:24AM (#35926627)
Never underestimate the lack of imagination in the Linux-desktop world.
Re:First Rust Code Shows Up in the Windows 11 Kernel by lloydatkinson on Saturday May 13, 2023 @05:13AM (#35926815)
Agreed. Years and years of objectively bad UX and UI with the likes of GNOME, KDE, etc. I cannot understand why the organisations creating Linux distros have never at any point thought to hire a designer or two so their desktop apps don’t look like someone just slapped them onto a window with either far too much padding (even more than HN loves to complain about the web) or not enough so usability is harder.
Re:First Rust Code Shows Up in the Windows 11 Kernel by photonbeam on Saturday May 13, 2023 @12:00PM (#35929656)
The issue is likely getting the people working for free to listen to a designer
Re:First Rust Code Shows Up in the Windows 11 Kernel by lenkite on Saturday May 13, 2023 @01:14PM (#35930417)
I think the problem is that they listened too much to designers.
Re:First Rust Code Shows Up in the Windows 11 Kernel by lloydatkinson on Saturday May 13, 2023 @02:37PM (#35931299)
No they really didn’t. No designer is making UIs that don’t align, are full of inconsistencies, and have confusing UX.
Re:First Rust Code Shows Up in the Windows 11 Kernel by cassepipe on Saturday May 13, 2023 @05:33AM (#35926892)
How so ? I am curious to know more
Re:First Rust Code Shows Up in the Windows 11 Kernel by pjmlp on Saturday May 13, 2023 @05:39AM (#35926920)
Re:First Rust Code Shows Up in the Windows 11 Kernel by dontlaugh on Saturday May 13, 2023 @05:55AM (#35926986)
Using a database is not a bad idea, especially for many reads and few writes.

The problems with the windows registry are orthogonal to that.

Re:First Rust Code Shows Up in the Windows 11 Kernel by ssokolow on Saturday May 13, 2023 @05:39PM (#35933023)
GNOME is infamous for blindly copying things that appeal to them without underlying the originator's rationale and, in the process, making a mess of things... they just usually lean more toward copying Apple.

(eg. Changing their save icon to an "arrow pointing at hard drive" one that's harder to visually distinguish from their download icon because they don't understand that you shouldn't privilege affordances (which only give benefit while learning a new system of symbols) over consistency with existing established iconography like the "save icon" (diskette) used by every other system.)

...or GNOME 3 ruining the "Cancel/OK in the bottom-right corner of the dialog, in that order for LTR languages" they borrowed from Apple with their "action buttons in dialog header bars" idea. (TL;DR: Dialog boxes are laid out to read like paper forms, following the writing order of prose text in the user's native language. Action buttons go in the reading-order-terminal corner for a similar reason to why the signature field on a paper form is at the bottom and why business letters are supposed to end with what you want the reader to do.)

Likewise, for dialogs where they stretch OK and cancel to full width. Now you've required the user to move the cursor much further during normal operation.

See also https://uxmovement.com/buttons/why-ok-buttons-in-dialog-boxe...

This is quite literally stuff that was covered in my introduction to Human-Computer Interaction course at university.