Windows: Prefer the Native API over Win32
codeberg.org
Windows: Prefer the Native API over Win32
1–10 of 99 posts
Re: Windows: Prefer the Native API over Win32
#2For people not familiar with Windows development, another name for the NT native API is "the API that pretty much every document on Windows programming tells you not to use". It's like coding to the Linux syscall interface instead of libc.
Re: Windows: Prefer the Native API over Win32
#3For people not familiar with Windows development, another name for the NT native API is "the API that pretty much every document on Windows programming tells you not to use". It's like coding to the Linux syscall interface instead of libc.
Yeah, I know go has had issues because they subvert libc themselves in similar fashion. I wonder how this will turn out.
Re: Windows: Prefer the Native API over Win32
#4[deleted]
Re: Windows: Prefer the Native API over Win32
#5For people not familiar with Windows development, another name for the NT native API is "the API that pretty much every document on Windows programming tells you not to use". It's like coding to the Linux syscall interface instead of libc.
Yeah, I know go has had issues because they subvert libc themselves in similar fashion. I wonder how this will turn out.
I think they had to revert back to libc on macOS/iOS because those have syscall interfaces that truly are not stable (and golang found that out the hard way). I wonder if they had to do the same on BSDs because of syscall filtering.
Re: Windows: Prefer the Native API over Win32
#6For people not familiar with Windows development, another name for the NT native API is "the API that pretty much every document on Windows programming tells you not to use". It's like coding to the Linux syscall interface instead of libc.
Yeah, I know go has had issues because they subvert libc themselves in similar fashion. I wonder how this will turn out.
Go backed out of their strategy on MacOS and started using libc (libsystem?), because when Apple says something is internal and may change without notice, they really mean it. It may be a better risk with Microsoft, but it’s still a risk.
Re: Windows: Prefer the Native API over Win32
#7Fool's errand. Apps built with this will have to be maintained forever (vs the apps from Win 9x which still work in Windows 11).
Re: Windows: Prefer the Native API over Win32
#8For people not familiar with Windows development, another name for the NT native API is "the API that pretty much every document on Windows programming tells you not to use". It's like coding to the Linux syscall interface instead of libc.
Linux syscall interface is actually stable and can easily be targeted. It’s BSDs (and Mac OS) that force everyone to link to only libc.
Re: Windows: Prefer the Native API over Win32
#9For people not familiar with Windows development, another name for the NT native API is "the API that pretty much every document on Windows programming tells you not to use". It's like coding to the Linux syscall interface instead of libc.
> It's like ...
Considering the level of the API. But it is total opposite comparing a bit deeper. Linux has a famous rule "WE DO NOT BREAK USERSPACE!" e.g. [1].
Re: Windows: Prefer the Native API over Win32
#10For people not familiar with Windows development, another name for the NT native API is "the API that pretty much every document on Windows programming tells you not to use". It's like coding to the Linux syscall interface instead of libc.
> It's like coding to the Linux syscall interface instead of libc.
The right thing to do? I don't see why I would want to use libc.