4 ms·

>> Microsoft are free to change the Native API at will, and you will be left holding both pieces when things break. > [...] the worst case scenario is really m

by cmovq 8mo ago

>> Microsoft are free to change the Native API at will, and you will be left holding both pieces when things break. > [...] the worst case scenario is really mild: A new version of windows comes out, breaking ntdll compatibility. Zig project adds a fix to the std lib. Application developer recompiles their zig project from source, and ships an update to their users. That assumes the application developer will continue to maintain it until the end of time. Also "the fix" would mean developers wanting to support earlier Windows versions would need to use an older std library? Or is the library going to have runtime checks to see what Windows build its running on?

eps 8mo ago
> Microsoft are free to change the Native API at will,... But they won't, because if there is one thing that Microsoft has always been extremely good at and cared for is backward compatibility. And changing Native API will break a ton of existing software, because even though undocumented it is very widely used.
- dbdoskey 8mo ago
  Actually they do change the native API quite a bit. Not in minor releases so much but in major releases
  - eps 8mo ago
    They depricate some methods (very rarely and reasonably) and add new enums or struct versions to existing ones, but never change existing semantics, leave alone method signatures. As I said elsewhere, I invite you to find examples of actually destructive Native API changes.
- blibble 8mo ago
  you are confusing the ntdll interface (which is undocumented and subject to change), and win32 (which is stable, mostly) they tell you not to use ntdll, and say they will change it whenever they want and they have in the past (they have had to moderate this policy with "containers", but it's still what they say)
  - eps 8mo ago
    I'm not confusing anything.
chroma_zone 8mo ago
Sounds like the iOS model: your app only exists as long as you are alive and able to pay $99/year. This mentality is a nightmare for software preservation.
josephcsible 8mo ago
> That assumes the application developer will continue to maintain it until the end of time. If it's still relevant after the developer abandons it, someone else will probably fork it.

by cmovq 8mo ago

eps 8mo ago

> Microsoft are free to change the Native API at will,... But they won't, because if there is one thing that Microsoft has always been extremely good at and cared for is backward compatibility. And changing Native API will break a ton of existing software, because even though undocumented it is very widely used.

dbdoskey 8mo ago
Actually they do change the native API quite a bit. Not in minor releases so much but in major releases
- eps 8mo ago
  They depricate some methods (very rarely and reasonably) and add new enums or struct versions to existing ones, but never change existing semantics, leave alone method signatures. As I said elsewhere, I invite you to find examples of actually destructive Native API changes.
blibble 8mo ago
you are confusing the ntdll interface (which is undocumented and subject to change), and win32 (which is stable, mostly) they tell you not to use ntdll, and say they will change it whenever they want and they have in the past (they have had to moderate this policy with "containers", but it's still what they say)
- eps 8mo ago
  I'm not confusing anything.

chroma_zone 8mo ago

Sounds like the iOS model: your app only exists as long as you are alive and able to pay $99/year. This mentality is a nightmare for software preservation.

josephcsible 8mo ago

> That assumes the application developer will continue to maintain it until the end of time. If it's still relevant after the developer abandons it, someone else will probably fork it.