3 ms·
> incompatible paradigms See Architectural Mismatch or, Why it's hard to build systems out of existing parts[1] Yes, we are not good at it, but we need to do
by mpweiher 9y ago
> incompatible paradigms
See Architectural Mismatch or, Why it's hard to build systems out of existing parts[1]
Yes, we are not good at it, but we need to do it. Very often, the dominant paradigm is not appropriate for the application at hand, and often no single paradigm is appropriate for the entire application.
For example, UI programming does not really fit call/return well at all[2].
> attaching software unit A to software unit B .. master/slave
Case in point: this is largely due to the call/return architectural style being so incredibly dominant that we don't even see it as a distinct style, with alternatives. I am calling it 'The Gentle Tyranny of Call/Return'.
[1] http://www.cs.cmu.edu/afs/cs.cmu.edu/project/able/www/paper_abstracts/archmismatch-icse17.html http://www.cs.cmu.edu/afs/cs.cmu.edu/project/able/www/paper_...
[2] http://dl.ifip.org/db/conf/ehci/ehci2007/Chatty07.pdf http://dl.ifip.org/db/conf/ehci/ehci2007/Chatty07.pdf
- Animats 9y agoSee Architectural Mismatch or, Why it's hard to build systems out of existing parts If you want to study that, look at ROS, the Robot Operating System. ROS is a piece of middleware for interprocess communication on Linux, plus a huge collection of existing robotics, image processing, and machine learning tools which have been hammered into using that middleware. The dents show. There's so much dependency and version pinning that just installing it without breaking a Ubuntu distribution is tough. It does sort of work, and it's used by many academic projects. In a more general sense, we don't have a good handle on "big objects". Examples of "big objects" are a spreadsheet embedded in a word processor document or a SSL/TLS system. Big objects have things of their own to do and may have internal threads of their own. We don't even have a good name for these. Microsoft has Object Linking and Embedding and the Common Object Model, which date from the early 1990s and live on in .NET and the newer Windows Runtime. These are usually implemented, somewhat painfully, through the DLL mechanism, shared memory, and through inter-process communication. All this is somewhat alien to the Unix/Linux world, which never really had things like that except as emulations of what Microsoft did. "Big object" concepts barely exist at the language level. Maybe they should.