Mutability of NT syscalls numbers/ids (when compared to Linux kernel)

[Luca91]

In the NT kernel, syscalls numbers (ids) are not stable and unlike in Linux, they tend to change from every major (or even minor) OS release. That's why it is dangerous to directly use syscall and instead the proper way is to call kernel32.dll.

Now my question is: why in Linux kernel we get a more stable syscall ids? Is there any practical reason why MS is changing so often the syscall ids on NT?

I'm just asking out of curiosity.

Thanks,
Luca

[deepzero]

There is no practical reason, they just want people to use their APIs instead.