If you spend some time working on cross platform code you will quickly realize that that choice is actually the right one. The NT API is actually very close in abstraction to Unix and allows for much less ad hoc code to handle windows specifics than using Win32 API (which is an abomination).
replyThe zig windows NT implementations are very well done and I actually use them as reference when dealing with windows IO.
> Completely destroying any forward compatibility!
replyMicrosoft breaking the ntdll.dll function interface is extremely unlikely, there's too much popular software in the wild depending on it.
From the link:
reply> > Won't this get flagged by anti-virus scanners as suspicious?
> Unfortunately, yes. We consider this a problem for the anti-virus scanners to solve.
I am suddenly less interested in relying on Zig.
Why should you design your software around what a different piece of software could claim of your program?
replyBecause you want someone who trusts that different piece of software to use yours.
replyZig's decision here means the problem is _yours_ to convince this third party to trust you.
The next choice will be dynamically resolving syscall IDs from NTDLL? Surely that has no issues that could possibly happen.
reply