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.
Bound to happen... (Score:1)
Seaside - the next "rails" (Score:2)
Allow me to suggest that Seaside - the Smalltalk continuation-based web framework [seaside.st] will be the next "Rails". Already faster and in some ways, more powerful, and cross-platform (commercial smalltalks and Squeak all providing support).
I'm exploring Seaside (and Smalltalk in general) in my new blog: Methods and Messages: Randal Schwartz on Smalltalk [vox.com]. Check it out!
Re: (Score:2)
Re: (Score:2)
If there's a "next Rails", it's Django, not Seaside.
Google Trends/Alexa vs. DICE (Score:1)
I see this as another case of using noisy (and to some extent, downright bogus) stats. As usual, if you want to know the truth, follow the money.
Alas, my graphic [presicient.com] only tracks Ruby, not Rails, but I think they'd correlate pretty closely (esp. since the Rails crowd has hijacked the language). My read of the jobs data indicates Ruby has stalled...but so have Python and Perl. The real Next Big Thing (sadly) appears to be PHP.
I guess there's no accounting for tastes. At least Perl stalled at a 4x to 8x great
Re: (Score:2)
You're probably right. I get the feeling that the PHP community has probably learned a lot from Rails and Django frameworks in general. Hey, if they can do it better, faster and cheaper, then hats off to 'em.
Heh (Score:2)
I think not.
Re: (Score:1)