4 ms·
The problem was, code written for J++ wouldn't run on "regular" Java outside of Windows, effectively killing the cross-platform aspect of Java and turning it in
by sn_master 6y ago
The problem was, code written for J++ wouldn't run on "regular" Java outside of Windows, effectively killing the cross-platform aspect of Java and turning it into another Visual Basic.
- MichaelMoser123 6y agothat's what i meant: by naming it a windows jdk they would not imply to be cross platform. they could then argue that they implemented the same sdk for their platform only. (interesting if Oracle tried to argue that the same logic should apply in this case too).
- sn_master 6y agoTo be fair, Java isn't and arguable was never a true cross-platform language that the media used to portray it as. Any non-trivial app always needed a lot of platform-specific code and API calls to get that native look and feel.