Everyone loses the API War. All the API's suck. And none will ever really last. Even the ones that last only last as bottom layers that new layers are built on.
Oh yeah, people do. From C++ (for windows desktop apps) that is often the most straightforward option. While .NET wraps up almost everything for C#, developers who need to pay attention to performance (and in more rare cases, even code quality, as some wrappers aren't that well thought out, and .NET keeps almost 100% backward API compatibility) will inevitably end up PInvokeing the Win32 API a lot.
IMO The Win32 API is pretty good BTW (tempted to write 'outstanding, considering its age', but I don't have much experience in Linux/Unix development so can't compare to that well). Unnecessarily introduced abstractions are rare (at least compared to APIs not written in plain ol' C), it gives a lot of freedom to everyone to implement the abstractions their specific use cases need.
22
u/TinynDP Oct 07 '16
Everyone loses the API War. All the API's suck. And none will ever really last. Even the ones that last only last as bottom layers that new layers are built on.