Re:Windows NT vs. Unix: A design comparison
by OvbiousError on Tuesday September 10, 2024 @07:00AM
(#41499484)
I've had to work with api functions like https://learn.microsoft.com/en-us/windows/win32/api/winuser/... and friends. It was by far the most unpleasant api I've ever worked with.
Re:Windows NT vs. Unix: A design comparison
by frabert on Tuesday September 10, 2024 @07:48AM
(#41499801)
I think that particular pattern is a perfectly reasonable way to let the user ingest an arbitrarily long list of objects without having to do any preallocations -- or indeed, any allocations at all.
Re:Windows NT vs. Unix: A design comparison
by mananaysiempre on Tuesday September 10, 2024 @08:10AM
(#41499939)
Yes, but the inversion of control is unpleasant to deal with—compare Find{First,Next}File which don’t require that.
Re:Windows NT vs. Unix: A design comparison
by wongarsu on Tuesday September 10, 2024 @09:23AM
(#41500543)
Which is a pattern that also exists in the Win32 API, for example in the handle = CreateToolhelp32Snapshot(), Thread32First(handle, out), while Thread32Next(handle, out) API for iterating over a process's threads.
I also find EnumChildWindows pretty wacky. It's not too bad to use, but it's a weird pattern and a pattern that Windows has also moved away from since XP.
https://learn.microsoft.com/en-us/windows/win32/toolhelp/tra...
Re:Windows NT vs. Unix: A design comparison
by wruza on Tuesday September 10, 2024 @10:55AM
(#41501425)
Because allocating well under a hundred handles is a biggest problem we have.
WinAPI is awful to work with for reasons above anyone’s comprehension. It’s just legacy riding on legacy, with initial legacy made by someone 50% following stupid patterns from the previous 8/16 bit decade and 50% high on mushrooms. The first thing you do with WinAPI is abstracting it tf away from your face.
Especially UWP and its successors (I think it's called WinRT now?) are objectively terrible.