3 ms·
> These topics (to me) are far more important than simply creating new connectors. Yes. What this vision requires is pushing down a shared library or coordin
by abernard1 5y ago
> These topics (to me) are far more important than simply creating new connectors.
Yes. What this vision requires is pushing down a shared library or coordinated behavior into every new language or future technology that requires it.
If the behavior is not actually required, and is more of a suggestion, then it's a "protocol" and requires interface modifications everywhere. And now we're back to "why do we need this shared code/language?" and "how is this different than patterns?"
This model has been tried many many times. We just got rid of the ignominious stench of CORBA and its removal from Java in the last year after a 25 year failure. The architecture astronauts require their language to be guaranteed across wire boundaries which is a fancy way of saying that their uber-language needs to be implemented in all the subsystems for guarantees to work.
- mpweiher 5y ago> What this vision requires is pushing down a shared library or coordinated behavior into every new language or future technology that requires it. NO IT DOES NOT. Please do not repeat this false claim. > This model has been tried many many times No. What YOU describe has been tried many times. It doesn't work. We agree. > The architecture astronauts require their language to be guaranteed across wire boundaries Yep. This does not. > which is a fancy way of saying that their uber-language needs to be implemented in all the subsystems for guarantees to work. Yep. Which is why that is a bad idea.