Change is a good thing, because it allows for new better things to be possible, and it's also pervasive. When I call to replace a broken windshield, they ask for make, model and year of my car. Computer industry and software in particular are more consistent with change and even have a term compatibility. But even more consistent is that everything is changing constantly: take the GUI: it used to be Visual Basic and MFC, then it was .NET, now it's Avalon; in Java it was AWT then Swing. In the parallel universe of web, there's been plain HTML, then XML and XSLT, now Ajax. Apple replaced Mac OS with UNIX and NeXT API, then switched to Intel; while Microsoft to a PowerPC cell. Companies have to redevelop their whole code bases from scratch to adapt and compete. Just visiting the regular bookstore you could see new major technolgies appearing every 6 months. That said, the best part is that the added value of the new technolgy far exceeds the effort for adaptation. (Here you should come up with your own favorite example.)
----- Original Message ---- From: Andrew Nikitin <[EMAIL PROTECTED]> To: [email protected] Sent: Sunday, June 25, 2006 12:15:20 AM Subject: [Jprogramming] Grid API Usability Hello, Randy. I did not realize that this is an official policy. If it is in fact so, it explains most of the grief. However, it is not necessarily a bad thing. If you make an application for a customer you just ship it and install it with whatever version is current. If you use J as a tinker toy (like I do) most scripts have line counter in double digits, so it does not matter anyway. Maybe, that is the lesson of all this. >Hello Andrew; > >You do realize that upward compatibility is not part of >the J mission. This is disappointing to me. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
