On 02/06/02 13:16, "Gunnlaugur Thor Briem" <[EMAIL PROTECTED]> wrote:
> Hi, > > here's one community vote saying "drop it yesterday". Here's a vote for think carefully what your dropping, when are you doing it, and how will it affect developers and end users. > > Those users still clinging to Java 1.1 (either because > of arcane platforms or just plain upgradeophobia) are > probably (hopefully?) a pretty small proportion of the > Xalan user base, and anyway they already have a well > functional, stable 1.1-compatible release, Xalan 2.2 > (plus the option, in the case of MacOS 9 users, of > upgrading to an actual operating system :) Some of us do not have the luxury of dictating what our customers would use, How I wish it was different sometimes. So what you're saying if I understand correctly is from 2.3 on screw everyone who is limited on the platforms they can deploy in and let's only worry about the cutting edge. That makes for a very lousy development strategy. Another thing that annoyed the hell out of me is that you're saying upgrade like it was as easy as upgrading Linux or something. Most of the people who are using OS 9 in my experience are people who can't upgrade to OS X (the real operating system) even if they wanted to. > > It's not worth holding on to stone-age compatibility > forever, at the cost of performance and development > ease. And there will always be cries of despair from > the paleolithic contingent, no matter how long we wait. > I say it's been plenty long enough already. And a little more tact wouldn't hurt either. If people think they've been waiting long enough, they could always have striped the source from all the JDK 1.1X stuff a long time ago. > > Cheers, > > - Gulli > -- Carlos E. Araya ---+ WebCT Administrator/Trainer P | California Virtual Campus - | C/O De Anza College G | 21250 Stevens Creek Blvd ---+ Cupertino, CA 95014 email [EMAIL PROTECTED] web http://www.cvc1.org/ (work) http://www.silverwolf-net.net (personal) phone 408 257 0420 (work) PGP Fingerprint: E629 5DFD 7EAE 4995 E9D7 3D2F 5A9F 0CE7 DFE7 1756 80/20 Rule: Simplicity vs. complexity. 80 percent of the functionality/feature set of an "ideal" solution set, with only 20 percent of the complexity of the ideal solution or 20 percent of the effort required to build the ideal solution; or put another way, the last 20 percent of the "ideal" feature set is what creates the most complexity
