4 ms·
I thought it was NeXTSTEP/Sun, but it seems disputed. https://stackoverflow.com/questions/473758/what-does-the-ns-prefix-mean https://stackoverflow.com/question
by avx56 4y ago
I thought it was NeXTSTEP/Sun, but it seems disputed. https://stackoverflow.com/questions/473758/what-does-the-ns-prefix-mean https://stackoverflow.com/questions/473758/what-does-the-ns-...
- pjmlp 4y agoWhat they collaborated was in Distributed Objects Everywhere, which ended up becoming Java EE. https://en.wikipedia.org/wiki/Distributed_Objects_Everywhere https://en.wikipedia.org/wiki/Distributed_Objects_Everywhere Their collaboration is also one of the reasons why Java is basically Objective-C semantics with C++ like syntax. https://cs.gmu.edu/~sean/stuff/java-objc.html https://cs.gmu.edu/~sean/stuff/java-objc.html Interfaces (protocols), dynamic class loading (plugins), RMI (distributed objects), jars (bundles), dynamic dispatch by default, object root class,...
- steve1977 4y agoAnd I guess Cocoa (the initially Objective-C based application framework for macOS) was kind of a wordplay on Java again. It’s like Java, just sweeter ;)
- pjmlp 4y agoDuring OS X early days, Apple wasn't sure that the Mac OS developer community groomed on Object Pascal and C++, was that keen into embracing Objective-C. So they jumped into the Java hype, created their own JVM implementation, with Swing extensions for the OS X UI, and Cocoa Bridge was born for Objective-C interop, with bindings for all key Apple techonologies like Quicktime and such. When it became clear that Objective-C wasn't going to be an adoption problem, instead of using a 3rd party owned language, they dropped support for Java and eventually gave their implementation to OpenJDK.