The Grumpy Editor's guide to 2009
The Grumpy Editor's guide to 2009
Posted Jan 8, 2009 2:33 UTC (Thu) by pr1268 (guest, #24648)Parent article: The Grumpy Editor's guide to 2009
If some other company "pulls a SCO", then Groklaw will likely need to come out of maintenance mode to cover it. ;)
While I'm not a Perl apologist, I just can't see it ever becoming "legacy". Or, if one considers it to be legacy already, then it'll join the ranks of FORTRAN and COBOL and such as one of those ancient languages that demands a lot of skilled programmers in perpetuity.
2.6.33 sounds mighty optimistic, given how the time interval between 3-number kernel releases continues to grow. We'll see...
We still won't know about Fedora's "infrastructure issues". But they'll promise to fill us in as soon as they possibly can.
I'm not holding my breath. Forgive me if I sound trollish, but I'm resigned to thinking that Fedora will quietly let sleeping dogs lie on this one (for legal reasons).
Finally, it will be a hard year for Linux-related media; we have already seen a foreshadowing of the situation with Groklaw's shift into maintenance mode and the recent demises of LinuxWorld.com and Linux.com.
Please, don't let LWN suffer the same fate as these! Thanks to LWN's editors for all the fine work. Here's to a fun and productive 2009!
Posted Jan 8, 2009 4:40 UTC (Thu)
by jordanb (guest, #45668)
[Link]
One thing that potentially makes Perl different than Fortran and COBOL is that the latter two survive and prosper (in their own way) by serving a particular niche very well.
To the extent that Perl has a niche it's being plowed into by other languages (Python for system scripting, and a grab bag of them for web scripting). To look at the lifecycle of a language that is attacked in its niche, it might do well to look at something like Pascal. Yes, there still is some Pascal/Delphi work being done in this industry, but it's highly anemic. There's just no sector anymore where Pascal is still the 'default' choice for doing anything.
Posted Jan 8, 2009 7:26 UTC (Thu)
by tajyrink (subscriber, #2750)
[Link]
Posted Jan 8, 2009 8:20 UTC (Thu)
by mlawren (guest, #10136)
[Link] (4 responses)
Posted Jan 8, 2009 13:43 UTC (Thu)
by roblucid (guest, #48964)
[Link] (1 responses)
If I say "skow" to rhyme with then it's "pulls a SCO", but if I say ess-see-oh, then it's "pulls an SCO". What reads right, might depend on how you pronounce the acronym.
Posted Jan 8, 2009 13:44 UTC (Thu)
by roblucid (guest, #48964)
[Link]
Posted Jan 8, 2009 14:22 UTC (Thu)
by hummassa (subscriber, #307)
[Link]
Posted Jan 8, 2009 14:31 UTC (Thu)
by pr1268 (guest, #24648)
[Link]
"pulls a SCO" - you wrote it that way, but didn't mention that the article has written it as "pulls an SCO" which doesn't read right, to my eyes. I habitually pronounce SCO as a single-syllable word that rhymes with "snow" or "slow". It is an acronym, so saying it as "S-C-O" wouldn't be improper. I perish the thought of our editor agonizing over whether to use "a" or "an" in that sentence. :)
Posted Jan 8, 2009 8:28 UTC (Thu)
by Ze (guest, #54182)
[Link]
I'm not holding my breath. Forgive me if I sound trollish, but I'm resigned to thinking that Fedora will quietly let sleeping dogs lie on this one (for legal reasons). What legal reasons? Honestly I reckon Fedora will try to sweep it under the carpet so they aren't further embarrassed. Now I'm going to take a completely uninformed wild guess and say the compromise was most likely due to incompetence in securing their own servers ,perhaps even someone not following the projects procedures for security. Sweeping it under the carpet is what they shouldn't do , as anybody who cares about security should be assuming the worst possibilities rather than ignoring it.Until you know what happened you can't know if the procedures in place are sufficient to fix further problems or even fix the current problem.
Posted Jan 15, 2009 10:23 UTC (Thu)
by renox (guest, #23785)
[Link]
I consider that there's two Perl language: Perl5 which is 'legacy'/'stable' as it won't change much now and Perl6 which is very different from Perl5.
Perl6 as a new language will have to compete against Python3, Ruby and Perl5, so I wouldn't bet on it..
The Grumpy Editor's guide to 2009
> becoming "legacy". Or, if one considers it to be legacy
> already, then it'll join the ranks of FORTRAN and COBOL
> and such as one of those ancient languages that demands
> a lot of skilled programmers in perpetuity.
The Grumpy Editor's guide to 2009
Small grammar fix?
Small grammar fix?
Small grammar fix?
Small grammar fix?
Small grammar fix?
The Grumpy Editor's guide to 2009
The Grumpy Editor's guide to 2009