| |||||||||||||
|
| |||||||||||||
Project Jigsaw (Mark Reinholds Blog)Project Jigsaw (Mark Reinholds Blog)Posted Dec 6, 2008 5:35 UTC (Sat) by elanthis (subscriber, #6227)In reply to: Project Jigsaw (Mark Reinholds Blog) by drag Parent article: Project Jigsaw (Mark Reinholds Blog)
No. Because then libraries end up depending on different versions, and there's no way to use two separate libraries that depend on two incompatible versions of a runtime.
Even in the Open Source world it can take larger projects and libraries to convert to newer runtimes and APIs. In the corporate world, it can take ages.
Breaking compatibility with any major, popular platform consumer just isn't a realistic option if you're trying to deliver a true end-to-end platform rather than just a prepackaged runtime+library kit.
(Log in to post comments)
Project Jigsaw (Mark Reinholds Blog) Posted Dec 6, 2008 16:59 UTC (Sat) by jengelh (subscriber, #33263) [Link]
Which is why we have symbol versioning... Glibc does it for ages already.
Project Jigsaw (Mark Reinholds Blog) Posted Dec 6, 2008 18:19 UTC (Sat) by nix (subscriber, #2304) [Link]
And it's modelled on the version from... Sun! So I suspect Sun can do
something similar in a modular JDK :)
|
|
||||||||||||