2 ms·
> Primary evidence in the case against OLE-style compound documents is that it's gone out of fashion and is hardly used anymore outside of office suites, and on
by TeMPOraL 3y ago
> Primary evidence in the case against OLE-style compound documents is that it's gone out of fashion and is hardly used anymore outside of office suites, and only hardly even there. Users don't seem to care and aren't asking for it back.
Microsoft still has deep integration between apps, even outside the direct Office trio (Word, Excel, PowerPoint). Most recently, there have been developments such as "Loop components", which let you embed components like "Checklist" or "Paragraph" or "Progress tracker" or "Table" or "Task list" into a Teams conversation, and I think some other programs too, and this is backed by (AFAIK) SharePoint. At work I haven't seen it used much, so I can't say whether anyone wants it at all, but at first look it sounds nice.
Then there's Unix philosophy; modern Linux systems are built out of tiny components that can be embedded, except instead of COM-like IPC, it's done through a mix of shelling out, exec() calls and filesystem operations. Ironically, Linux is going through its own period of appification - if Unix philosophy is like COM, then Docker, FlatPak, and other ways to containerize software are a push towards siloed out apps.
> OLE/COM were the product of C++ architecture astronauts who didn't seem to care much about developer usability.
I've dabbled in COM and DCOM several times over the past few decades (DirectX, old DCOM-based industrial protocols, ...), and I agree it's a special kind of hell that's laced with landmines on which you continuously step, but the dungeon keeper doesn't let you die until you finish the project... but honestly, it still feels better than the Web and modern distributed development. More raw, but also much less wasteful in terms of compute.
- anthk 3y agoKDE has Kparts which was pretty close.
- hollerith 3y ago>modern Linux systems are built out of tiny components that can be embedded, except instead of COM-like IPC, it's done through a mix of shelling out, exec() calls and filesystem operations. I always thought that the main reason MacOS is more appified ("siloed"?) than Linux is because when both programs are open-source, it becomes easier for one developer to make two programs ("projects"?) work more closely together. More precisely, it becomes easier for a developer to make a change that crosses a boundary between projects and get that change integrated into both projects. Unlike the situation with COM, there can be a great variety of methods ("implementation details"?) by which the two Linux projects start working together better.
- mike_hearn 3y agoHow often does that happen though? In practice very few developers work that way, and Mac apps tend to interact with each other more/better than Linux apps because of things like Cocoa services that aren't too hard to implement and provide N:M "thin waist" rallying points around common interaction patterns.
- fl0ki 3y ago> dungeon keeper You probably meant dungeon master but had in mind one of the greatest PC games ever made. Try out War for the Overworld if you haven't already, it's a modern and faithful continuation of the series without the original IP.
- TeMPOraL 3y agoYeah, I thought of that game when writing that sentence. Thanks for the recommendation; I've never heard of "War for the Overworld", I'll check it out! EDIT: I initially mistyped Overworld as Overlord, revealing that I played way too much StarCraft as a kid.