3 ms·
It turns out that hyperlinking / embedding shouldn’t involve you giving your memory address space to someone else - who knew :) And really, the web/REST wound
by parasubvert 8y ago
It turns out that hyperlinking / embedding shouldn’t involve you giving your memory address space to someone else - who knew :)
And really, the web/REST wound up being the object oriented document framework we were all looking for. It was terribly inefficient at first (and is still) but was architecturally simpler. The main issue is no one thought it would be possible to replace Windows with a cross platform GUI, and no one thought hypertext/hypermedia - a mostly academic concept at the time beyond HyperCard - would be that GUI.
https://www.slideshare.net/StuC/oopsla-2007-the-web-distributed-objects-realized?from_m_app=ios https://www.slideshare.net/StuC/oopsla-2007-the-web-distribu...
- atombender 8y agoRight — as I remember, if you embedded an Excel object into Word, the Excel part was implemented in a DLL that loaded directly into the Word process space. This would have been so much more stable if it instead started a headless Excel server process. With DCOM, this kind of cross-process COM worked great, but that came much later. OLE 1.0 preceded COM by several years.