jojo wrote:
Purely devil's advocate:
Quote:
In point of fact, the original definition of 'micro-kernel' was a system that did not compile the whole operating system into a single binary, and used message-passing for inter-process communication and synchronization.
So kind of like NT, then?
Yeah, hence the claim. I'm not saying that the claim doesn't have
any merit, just that it is 'technically correct - the best kind of correct', rather than a meaningful description. Also, the NT kernel has several kinds of IPC primitives, not just message-passing - I should have said 'used message-passing as the sole primitive for inter-process communication and synchronization', since the primary idea was that less abstract synchronization primitives such as semaphores were more prone to bugs, and more likely to get misused or sabotaged.
Anyway, the reason for this whole pedantic aside was not to say that the term was being misused, but that the idea has evolved a lot since it arose. In the real world, 'pure' designs are rarely practical ones - and yes, I am aware that there is a bit of hypocrisy in me saying that, but I am no longer aiming at writing a world-beating OS; purity is just fine for a research project, and in fact is in some ways a necessity to reduce implementation variables.