Re:Mark Russinovich: “Working towards enabling Windows drive...
by CodeCompost on Sunday September 24, 2023 @04:02AM
(#37631052)
Microsoft tried that already. It failed miserably. I don't think they gave a reason but I suspect that garbage collection caused too many freezes in early 2000s hardware.
[ Parent
| on HN ]
Re:Mark Russinovich: “Working towards enabling Windows drive...
by resonious on Sunday September 24, 2023 @04:45AM
(#37631244)
Maybe I'm wrong but I suspect your parent comment was alluding to that sarcastically.
Re:Mark Russinovich: “Working towards enabling Windows drive...
by pjmlp on Sunday September 24, 2023 @07:49AM
(#37632248)
It didn't fail, it was sabotaged by Synosfky and friends, which then carried on doing exactly the same ideas with COM and C++.
Guess why UWP applications are much slower than regular Win32, app sandboxing and COM reference counting.
But hey, they won.
Re:Mark Russinovich: “Working towards enabling Windows drive...
by SSLy on Sunday September 24, 2023 @09:38AM
(#37633013)
> it was sabotaged by Synosfky and friends
Is this described anywhere in detail?
Re:Mark Russinovich: “Working towards enabling Windows drive...
by pjmlp on Sunday September 24, 2023 @01:35PM
(#37635256)
Yes, basically when Longhorn started to fail to meet expectations, there were two possible ways, do what Google did with Android, push forward no matter what to make it work, or forcing a rewrite into something else, which is what WinDev ended up doing.
"What Really Happened with Vista"
https://hackernoon.com/what-really-happened-with-vista-4ca7f...
"Turning to the past to power Windows’ future: An in-depth look at WinRT"
https://arstechnica.com/features/2012/10/windows-8-and-winrt...
Re:Mark Russinovich: “Working towards enabling Windows drive...
by iknowstuff on Saturday September 30, 2023 @04:14PM
(#37719291)
macOS sandboxes apps, which are usually written in Swift or ObjC and thus use reference counting, and doesn’t suffer from the kind of slowness that plagues UWP. So your hypothesis appears to be incorrect