3 ms·
I don't know. I think the original idea for Windows was that services are accessible through APIs on a system-wide message bus (COM) and the various GUIs are si
by xg15 8y ago
I don't know. I think the original idea for Windows was that services are accessible through APIs on a system-wide message bus (COM) and the various GUIs are simply clients for those APIs.
I'd argue that, if that design were held through (and an easy to use universal client for COM had been available) it could have become even more versatile than unix. But of course, that's not what happened...
Then, today, we have a new trend where "GUI-only" functions are actually used deliberately to implement security restrictions or preserve business models.
And then there is the mess that is "web-based" GUIs...
- dmortin 8y agoMaintaining such internal APIs is additional work and since most users prefer clicking in GUIs, companies ditched this approach, because it's simpler and cheaper to create a GUI only tool.
- jimjimjim 8y agothe original idea for windows was a gui with everything sending messages to windows, and everything was a window. COM came along much much later.
- de_watcher 8y ago> And then there is the mess that is "web-based" GUIs... I am an all-for-native guy (Qt, etc.), but the "web-based" GUIs are actually bearable from the stand point of the developer with a CLI: their data interfaces are HTTP, so it's easy to hook them into CLI tools their graphics are decently accessible through Selenium
- xg15 8y agoTrue. From an API standpoint, SPAs actually improved the situation a lot: Introducing an API boundary and separating concerns is now a routine part of developing an SPA.
- kyberias 8y agoCOM is not a "message bus" and the operating system APIs are mostly not COM-based.
- rambojazz 8y agoIsn't DBUS basically the same thing?