3 ms·
What’s “distributed” mean here?
by kstrauser 3y ago
What’s “distributed” mean here?
- bluGill 3y agoThere are two meanings we meant: other computers, and other programs. In 1995 most computers had a single CPU core, running at around 100mhz. Today each core is 10-30x higher frequency (though as always you cannot compare frequency directly it is still a sign of relative speed), and almost all computers have at least 4 cores. In 1995 you were doing good to get 8 MB of RAM, now we are looking at around 8GB. One way around the inherent slowness of computers is another one on the network to run some programs. In 1995 there were cool demonstrations where a program could plugin others for some functions. So your word processor wouldn't have a spellcheck, it would just use a third party spell check of your choice. (we sort of do that with shared libraries, but the interface is different) Some of what was done then was better than anything we have today (but see the other replies, making distributed work transparently is not easy and so if we had made it work people would probably hate how often it failed)
- kstrauser 3y agoHow would that relate to CORBA and friends? (I know I could google all this. It’s more fun to chat about it.)
- bluGill 3y agoCORBA was another attempt of much the same thing there are dozens at the time. Of course each had slightly different goals and variations, so you can't always compare directly. Some were more to one direction or the other.
- cancerhacker 3y ago(It was not fun times. It was "hey everyone, all our problems will be solved by adopting XXX" which inevitably introduced a new set of problems which could be solved by only adopting half of XXX and all of YYY, repeat. Now that I think about it, I don't think anything has really changed, except that now the XXX has mutated into a XYZZY, we call it technical debt and then we retire to leave it for the next lot.)
- coliveira 3y agoCORBA is a specification to make objects interact across processes and computers. Its main drawback is the complexity, as it has to adjust to the several use cases (local and remote processes/computers) and provide interfaces to all different languages that might want to use objects, all this in a transparent way. Having CORBA specifications working reliably was a big problem to solve, and it was never 100% done, as new problems and specifications would pop up as needed. Finally, web technology solved most (but not all) of these problems by skipping programming language level objects and moving to higher level interaction through HTML/XML interfaces.
- jamesblonde 3y agoAll true, but the real differentiator that enabled SOAP to kill CORBA was the appearance of NATs and firewalls. CORBA assumed objects could talk directly via IP. But NATs appeared at the end of the 1990s when IP addresses were running out, suddenly CORBA wouldn't work in corporate environments. But SOAP could be made to work with http proxies. SOAP, of course, was superceded by REST, because it was too complex and REST was perceived as much simpler.
- coliveira 3y agoWell, I guess that with more specifications thrown in the mix this could be covered too. The problem, as I mentioned, is the incredible complexity of the whole thing. Web technology solves these issues in simpler ways that don't involve messing up with remote objects at the programming level.