On Fri, May 15, 2009 at 8:06 AM, James Carlson <james.d.carlson at sun.com> wrote: > [repaired incorrect subject line and cc list]
Thanks. > > Garrett D'Amore writes: >> This is all driven by my believe that the Java platform is just that -- >> a platform -- that stands apart from Solaris. > > That part doesn't sound right to me. ?Neither LSARC nor PSARC nor the > ARC in general are in any way specific to Solaris. ?They're Sun > engineering processes. > > Simply saying that the Java system is its own platform isn't enough to > determine the ARC's role. > I wish I had the original thread. I would agree with Garrett in at least one respect -- Java is its own platform -- with its own ecosystem, practices, and requirements. Many Java applications have their own update mechanism and delivery channels. Java applications and libraries depend on JRE releases as much as more as OS releases. They have their own documentation. Etc. It's more than, say Python, for instance -- Java was arguably designed with a lot more intent surrounding packaging and distribution (manifests), and a more dynamic run-time (classloaders). It seems somewhat like a shoe-horn to package it onto such a relatively static delivery vehicle. I'm thinking of Netbeans, which can update itself. I'm thinking of Eclipse, that we hindered from updating itself. I'm thinking of all those common jars that got integrated project private. I don't think this changes the ARC's role (i.e. no JARC) at all, but I do wish there was a more complete, consistent, and robust picture of what it means to integrate Java packages, no matter from where they come. Maybe we'll get it right eventually as we plug along. > -- > James Carlson, Solaris Networking ? ? ? ? ? ? ?<james.d.carlson at sun.com> > Sun Microsystems / 35 Network Drive ? ? ? ?71.232W ? Vox +1 781 442 2084 > MS UBUR02-212 / Burlington MA 01803-2757 ? 42.496N ? Fax +1 781 442 1677 > _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc at opensolaris.org >
