To really see where "why would you want that at all" or "nobody needs that" or "the software is fine as it is" or such ilk come from, I recommend reading "Understanding Media" by Marshall McLuhan.
The "VAX Users See the Writing on the Wall" article brings up some interesting issues. However, it could have dug a bit deeper. The title, all by itself, deserves some comment. Most VAX "users" probably don't even know they are using a VAX. Many of them are likely using character-cell based applications that get the job done day in and day out. It is the whining of the VAX owners and application managers to which the article really dedicates itself.
Speaking of dedication, who can feel sorry for VAX owners who have let the whirlwind of the last decade keep them from paying attention to the critical systems and applications that keep their business going? The applications must be critical since someone noticed when the system finally crashed. The applications must be substantial since they have not already been replaced by some GUI/BlahScript solution whipped out in a couple weeks.
Come to think of it, past efforts have probably been attempted to replace the VAX based applications but have failed for any number of reasons. I am sure you know of at least one multi-million YourCurrency development effort that was slated to replace some legacy application that either failed to deliver or was cut before it could be implemented. For the applications that actually do get replaced, if they have just been simply replaced by some point-n-click poorly designed GUI, they seldomly seem "more efficient" than the past application.
The real issue goes much deeper than just one model of computer, like the VAX. For any organization, there might be some critical function busy spinning on some tough solid box sitting softly in some unseen corner or closet. It might be a VAX, but could also be an HP3000 or a 3B2 or maybe even a 486 clone. In a decade or less, it will be one of the sexy new systems we wish we could afford today.
Images evoking a response--reflection, revulsion or reverence are art. Technology and technique used to create the images only matter in their unique evocation for the medium. What is the message? Where does it take me? What is fine art? Maybe just enduring art that takes more than a few folks for a journey. Check out a copy of WAYS OF SEEING by John Berger for an analysis of the journey.
You do some consulting for a company. A company of networked consultants. Consultants many of whom utilize AOL. From AOL, who send you specifications. Specifications you turn into a billable product. Work done, oh no, have to send invoice. Have to mail invoice to...guess what. Accounts payable person with...guess what. An AOL mail address. Send invoice and wait. Hey. what's go'in on? Oh my! You didn't get the reply? Needed to validate some information. Information needed to release the check. Sorry, you'll have to wait until next month, to be paid for your work.
Coming from a pre-GNU time when shared "open" source code came on DECUS tapes, this CDDB issue sure smells like the initial stages of the ARC/ZIP conflict.
Who uses ARC to package original content anymore? ARC won their lawsuit hoping to hijack the market. ZIP won the market with better support and technology.
It would be nice if everyone could get along and be happy--however, it seems like a gaggle of lawyers have already piled onto a CDDB litigation train that is starting to pull out of the station.
Slashdot Mirror
To really see where "why would you want that at all" or "nobody needs that" or "the software is fine as it is" or such ilk come from, I recommend reading "Understanding Media" by Marshall McLuhan.
The "VAX Users See the Writing on the Wall" article brings up some interesting issues. However, it could have dug a bit deeper. The title, all by itself, deserves some comment. Most VAX "users" probably don't even know they are using a VAX. Many of them are likely using character-cell based applications that get the job done day in and day out. It is the whining of the VAX owners and application managers to which the article really dedicates itself.
Speaking of dedication, who can feel sorry for VAX owners who have let the whirlwind of the last decade keep them from paying attention to the critical systems and applications that keep their business going? The applications must be critical since someone noticed when the system finally crashed. The applications must be substantial since they have not already been replaced by some GUI/BlahScript solution whipped out in a couple weeks.
Come to think of it, past efforts have probably been attempted to replace the VAX based applications but have failed for any number of reasons. I am sure you know of at least one multi-million YourCurrency development effort that was slated to replace some legacy application that either failed to deliver or was cut before it could be implemented. For the applications that actually do get replaced, if they have just been simply replaced by some point-n-click poorly designed GUI, they seldomly seem "more efficient" than the past application.
The real issue goes much deeper than just one model of computer, like the VAX. For any organization, there might be some critical function busy spinning on some tough solid box sitting softly in some unseen corner or closet. It might be a VAX, but could also be an HP3000 or a 3B2 or maybe even a 486 clone. In a decade or less, it will be one of the sexy new systems we wish we could afford today.
It would be satisfying until...
You do some consulting for a company.
A company of networked consultants.
Consultants many of whom utilize AOL.
From AOL, who send you specifications.
Specifications you turn into a billable product.
Work done, oh no, have to send invoice.
Have to mail invoice to...guess what.
Accounts payable person with...guess what.
An AOL mail address.
Send invoice and wait.
Hey. what's go'in on?
Oh my! You didn't get the reply?
Needed to validate some information.
Information needed to release the check.
Sorry, you'll have to wait until next month,
to be paid for your work.
Think this is made up?
Sorry, its reality!
Coming from a pre-GNU time when shared "open" source code came on DECUS tapes, this CDDB issue sure smells like the initial stages of the ARC/ZIP conflict.
Who uses ARC to package original content anymore? ARC won their lawsuit hoping to hijack the market. ZIP won the market with better support and technology.
It would be nice if everyone could get along and be happy--however, it seems like a gaggle of lawyers have already piled onto a CDDB litigation train that is starting to pull out of the station.