2 ms·
OK, in fairness, some portions of the Windows API are well though out as you mention. Some people may also argue that other APIs like Direct3D have a more conve
by partycoder 9y ago
OK, in fairness, some portions of the Windows API are well though out as you mention. Some people may also argue that other APIs like Direct3D have a more convenient design.
The UNIX philosophy ("Everything is a file") has pros and cons. It makes interoperability fairly trivial, and being a filesystem it has access control capabilities.
If you want to have something similar to the Windows' IO Completion Ports (IOCP) paradigm you can make use of https://www.kernel.org/doc/Documentation/scheduler/completion.txt https://www.kernel.org/doc/Documentation/scheduler/completio...
- Tobba_ 9y agoIt really hard to compare them fairly since they're quite different in scope; X11 wouldn't exactly be considered a Linux API. Win32 is also split between several modules and the functions don't quite correspond to the syscalls; it's basically a bunch of wrappers around the actual NT API, win32k and some userspace servers. So it's really hard to draw a line somewhere if you wanted to compare them.