MC writes: > The key thing at the end of this quote should have cut the debate before it > started: > > > As has been repeatedly discussed here, the current > > memory requirements > > of the developer release installer are an artifact of > > its hurried > > implementation (eg 2 jvms). This will not continue > > to be the case. > > "This will not continue to be the case" :) So I like to believe that Sun > isn't pushing Java for the sake of Java anymore.
I don't know that we ever did that. However, if you really want to make a difference here, the right way to go about this is by setting requirements for the project. "Must boot within X seconds and install within Y minutes on reference platform Z" would likely be a decent sort of requirement. So long as a project in question is able to meet its requirements, why should any user really care what language was used to implement it? And if some particular language won't cut it due to an inability to meet requirements, then that makes the choice clear, and doesn't force us to resort to name-calling and other such unproductive activity. In other words, "language W sucks" is not just unprofessional, it's also pointless. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-discuss mailing list [email protected]
