Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by ziggy (25) on 2004.09.16 21:56 (#34404) Journal
    As I mentioned above [perl.org], I never really cared enough about ColdFusion to do more than look beyond the surface.

    But there was talk to rewrite the big nasty webapp at work some other language. The contenders were mostly Perl and Python, with Scheme, Smalltalk and Forth thrown in for fun. (It was Friday. The RAID array was down. For a week.) One of the other members of the team seriously put forward this week's platform from Microsoft, and ColdFusion.

    We ignored the Microsoft platform outright (we deploy on Solaris), but this guy did make a not-completely-implausible case for ColdFusion. In managementspeak, ColdFusion isn't about the language, it's about the platform. Given a codebase written in any language, really, the issue is the rest of the platform -- the IDE, the deployment environment, database connectivity, connection pooling, components, scaling up and out, etc.

    Now, I couldn't care less about ColdFusion as a language, but as a platform (a "whole product" in projectmanagementspeak), there's something worth examining here. Do these features make sense, or are they there to make better sounding marketing collateral? Given real programmers, are these features even necessary, or is the point to codify good development practices so you don't need great hackers [paulgraham.com] to write a moderately interesting webapp? I don't know, but that was the only part about ColdFusion that I found even vaguely alluring....