3 ms·
> Sadly, nobody has ever really figured out how to make GUI software like this - general purpose & composable. Somebody did figure out how to make general purp
by bitwize 5y ago
> Sadly, nobody has ever really figured out how to make GUI software like this - general purpose & composable.
Somebody did figure out how to make general purpose, composable GUI software: Microsoft, in the 90s, with COM.
COM is a superior model for software composition because it goes beyond the Unix metaphor of the pipe: a single communication channel that produces and accepts streams of unstructured bytes. COM objects have well-defined, strongly-typed, discoverable APIs, can live in- or out-of-process (with the same call semantics for each), and allow seamless integration between components. A custom control, for example, can be placed and configured in a visual GUI builder just the same as the controls that came with the builder.
Unix almost faded away in the 90s, and Linux never won, because Windows was simply better. More consistent, easy to use, and a joy to develop for. Old Unix hands like Larry Wall looked at what was possible in Windows and COM and said "Wow, I wish my environment let me do that!"
Microsoft's move away from component-based development and towards an "app model" is really one of the great tragedies of modern Windows. That and Windows turning into Bonzi Buddy tier spy/ad/nagware.
- dflock 5y agoI was a Windows desktop application developer during the 90's, so I've done COM development, with VB, Delphi and a tiny bit of C, so I know what you mean. I would say that COM is more special case and embeddable, rather than general purpose and composable? And this is all on the developer side, rather than the user side too. If the OS and applications had just been shipped as pre-packaged collections of COM objects - which you could reuse and remix into new tools and applications, with writing piles of code, then yeah. It was close for a while, but never got all the way to userland, sadly.