|
Re^3: Perl is dying
by theorbtwo (Prior) on Jul 14, 2006 at 17:53 UTC |
Hype isn't just generated by having a flashy homepage; it's also something generated by lots individuals. If you keep pointing out mod_perl, you perpetuate the myth that mod_perl is the best way to do not-CGI with perl.
Would a better name and a better homepage fix things? Possibly, but not if people keep talking about mod_perl instead of fastcgi.
| [reply] |
Re^3: Perl is dying
by eric256 (Parson) on Jul 14, 2006 at 18:00 UTC |
All web based applications are CGI. Arn't they? Did I miss some change? Could be, dunno.
AJAX: Actualy AJAX is new becuase it involves a new process (retrieving data from the server after the page has finished loading.
Are you realy saying now that it doesn't even matter if the code/language is good or bad, it just doesn't have enough hype? Realy if your only concern is hype then start hyping the language instead of saying its dieing.
Honestly if your the same AM as the OP then I'm very disappointed because the original rant was actualy quite well written and thought out, while this argument was just lame.
| [reply] |
|
Actualy AJAX is new becuase it involves a new process (retrieving data from the server after the page has finished loading.
Well to be fair the XMLHttpRequest API (or rather its MS equivalent) has been available for about five years in IE and there were methods of doing similar things before that using tricks with frames and stuff. The API became available in Mozilla in 2002. I can't quite put my finger on when AJAX was first coined, but it was quite recently and the use of this raft of technologies certainly predated the naming.
Update: The Wikipedia article on Ajax clearly indicates how far the use of these technologies predates the coining of the name.
/J\
| [reply] |
|
| [reply] |
|
Re^3: Perl is dying
by perrin (Chancellor) on Jul 14, 2006 at 19:10 UTC |
Uh, Ruby on Rails runs on FastCGI. | [reply] |
|
Which is, ironically, why I use FastCGI. mod_perl is too heavy for my needs (80% of my web requests don't require Perl in every HTTP process). I tried PersistentPerl/SpeedyCGI, liked it, but found a couple of bugs and the maintainer seems to have disappeared. I thought FastCGI was pretty much dead, then discovered that it's what Rails uses. Since it seems to be getting a new audience, I figured that I wouldn't be left in the lurch like I was with PersistentPerl.
| [reply] |
|
Yeah, I don't recommend using mod_perl to serve static files on a site with much traffic. You should use a reverse proxy setup or similar for that, as described in the mod_perl docs, or use FastCGI. The nice thing about FastCGI's new popularity is it means ISPs are getting pressure to support it.
| [reply] |
|
|
|
Re^3: Perl is dying
by Anonymous Monk on Jul 16, 2006 at 01:00 UTC |
Look, CGI is old and boring.
Amen. It is amazing that they are still publishing books with "CGI" in the title. Some people never learn.
It doesn't matter if you tack on "Fast" to it; people see "CGI" and walk away.
Or perceive you as a neanderthal. CGI only matters to Perl programmers without college degrees who aren't smart enough to realize they are stuck in the past. Getting too involved in the Perl community does these things to people. It's like living in a backwards country like North Korea. After a while, you become delusional and think the rest of the world is behind rather than ahead of you. | [reply] |
|
Oh are you Intrepid or Wassencratz? You do the "oh solo mio" routine kind of like them.
| [reply] |
|
CGI is old and boring?
Guess I better stop using the web, then, seeing as everything on it is CGI.
No more Google for me, let alone internet banking or Amazon,
J
| [reply] |
Re^3: Perl is dying
by marcus (Scribe) on Jul 17, 2006 at 17:25 UTC |
Except Rails uses FastCGI for deployment too.... | [reply] |
Re^3: Perl is dying
by Anonymous Monk on Aug 04, 2008 at 06:26 UTC |
AJAX stands for Async Javascript and XML... not XHTML | [reply] |
