3 ms·
Sun folks disagree, https://cs.gmu.edu/~sean/stuff/java-objc.html https://cs.gmu.edu/~sean/stuff/java-objc.html https://en.wikipedia.org/wiki/Distributed_Obje
by pjmlp 1y ago
Sun folks disagree,
https://cs.gmu.edu/~sean/stuff/java-objc.html https://cs.gmu.edu/~sean/stuff/java-objc.html
https://en.wikipedia.org/wiki/Distributed_Objects_Everywhere https://en.wikipedia.org/wiki/Distributed_Objects_Everywhere
Sure, they could have taken a bit more, like proper AOT instead of it being a feature only available in third party commercial JDKs, or some low level niceties like C#.
- saagarjha 1y agoI was talking about good parts of the language
- pjmlp 1y agoLike [] and @ all over the place, C lack of safety, and manual memory management? Because I don't see what else good Java has left out, besides AOT in the box and unsigned types.
- saagarjha 1y agoUh, the entire runtime?
- pjmlp 1y agoI beg to differ, given the engineering effort that went into JVM across various Java vendors, versus Apple and NeXT have done. Proven by the fact that Swift had to be invented, as there was nothing left to fix Objective-C in a proper way.
- saagarjha 1y agoSwift has that runtime, by the way.
- pjmlp 1y agoNope, Swift interops with Objective-C runtime to ease code migration from legacy Objective-C code, and existing Apple frameworks predating Swift. A runtime that isn't part of the cross-platform Swift project, with missing functionality being rewriten into Swift.
- saagarjha 11mo agoYes, and those platforms are worse off for it.
- jeberle 1y agoI would look to the UCSD p-System as a precedent to the JVM. Both are byte-code interpreted VMs. Gosling used the p-system earlier in his career, prior to joining Sun. https://en.wikipedia.org/wiki/James_Gosling#Career_and_contributions https://en.wikipedia.org/wiki/James_Gosling#Career_and_contr... The Objective-C runtime is very small: just enough to do late-bound fn calls to a tree of class defs. All on top of C.