3 ms·
Interesting...keen to read more about Java EE. And Java interfaces were taken from ObjC protocols. I think its sad though that this entire lineage while being
by valty 3y ago
Interesting...keen to read more about Java EE.
And Java interfaces were taken from ObjC protocols.
I think its sad though that this entire lineage while being inspired by SmallTalk, seemed to miss the whole point of SmallTalk. The always-running virtual machine was an essential part of it. And a good IDE and tooling is needed to help deal with such a dynamic language. But I think a lot of people just ended up treating it like C with a quirky syntax.
- pjmlp 3y agoHere, for both https://cs.gmu.edu/~sean/stuff/java-objc.html https://cs.gmu.edu/~sean/stuff/java-objc.html https://en.m.wikipedia.org/wiki/Distributed_Objects_Everywhere https://en.m.wikipedia.org/wiki/Distributed_Objects_Everywhe... You see a bit of Smalltalk image heritage of Eclipse workspaces, basically a way to turn files into a virtual image. Eclipse still has the Smalltalk code navigation from its Visual Age for Smalltalk roots. The way JMX, Java agents and dynamic code reloading works, as well. .NET also inherited many of this due to the way it came to be.