NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
2004, huh? (Score:5, Interesting)
Well, back in the Day, when DEC was strong and I was using VMS at government labs, I saw accounting numbers for how many cycles I used and how much that would cost our group.
This is just another example of my notion, which I hope to turn into an idea, that so-called utility computing is just one side off the swing of a pendulum. This pendulum ossicilates between people who want to control everything on their desktop (so they can install, run, whatever anything they want), and people who want someone else (MIS, IT, geeks down the hall) to manage it for them.
Often times, these two groups of people are the same. They have everything on their desktop so they do all their own support, then they realize that they are doing all their own support, so they get someone else to do it. After a while, and by my unscientific observations, this time is 5 to 7 years, they realize they cannot do everything they want because someone else controls the computers, so they bring it back to the desktop.
Why are things like ColdFusion and PHP so popular now? Because Perl was popular before. It will come around again, maybe with a different language or technology, but people swing back and forth between flexibility and ease. How long ago was COBOL created?
Now, the real trick is to time your business cycle to know when the oscillation is going to happen (i.e. figure out its period). Different places are slightly out of phase, and some places even have different phases in the same company. Big companies may have different departments at different places in the flexibility/ease oscillation.
But, figuring out when this is going to happen is clouded by the fact that hack "computer journalists" think every development is a new thing. Ask people who have been around a long time, or someone like Ziggy who has an encyclopedic knowledge of the history of computing starting somewhere around the invention of the papyrus scroll, and you will see that almost nothing is new. Indeed, this is one thing that James Burke's Knowledge Web could elucidate.
If you beleive the hype, you will end up chasing the next "new" thing just in time to catch it and start chasing the new next "new" thing. Indeed, I think the article looks like jjohn's MarkovBlogger than a serious article on what's happening in 2004.
Reply to This
Re:2004, huh? (Score:2)
Great reply. I only have one teeny side comment:
I think the example of COBOL weakens your argument. Consider the era in which it was created. New language technologies weren't coming around the way that they are now and COBOL had no serious competi
Re:2004, huh? (Score:2)