Quite a few years ago I read on Reddit a post made allegedly by a Microsoft programmer, who was telling that the young generation of programmers do not want to maintain the old optimized code (he was saying specifically about pipes in windows) and want to reimplement all fro scratch. In this example (pipes) they wrote a new pipe mechanism which then was lacking that ACL et. al. authorisation features and they had to hide it from normal programmers (made it somehow internal to system)
What it would mean (if we can believe this) is that Windows becomes a legacy burden and without proper management and knowledge will become a big ball of mud (if it's not yet like this) unbearable and unmabagable.
Right now I can access at least five styles of UI, from different epochs, each one is doing something important in the system, BC one cannot rewrite everything to the new style without enormous funds
Feels like we're living through the bronze-age-collapse of software. It's depressing to watch the software I use get worse and worse and be forced onto the downgrades
Yeah, I'd take that with a giant grain. You can't "hide" features that the system uses -- they're all visible. This is why NT APIs get used, even though they're not supposed to be leveraged outside of the kernel/critical system components. There's no "hiding" a pipe.
Mail Slots are on their way out, though. Not that they're useful today.
What it would mean (if we can believe this) is that Windows becomes a legacy burden and without proper management and knowledge will become a big ball of mud (if it's not yet like this) unbearable and unmabagable.
Right now I can access at least five styles of UI, from different epochs, each one is doing something important in the system, BC one cannot rewrite everything to the new style without enormous funds