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

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

Ovid
  (email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Monday September 26, 2005
01:08 PM

Enterprise Class Open Source Software

[ #26890 ]

I just wrote up a brief piece about Bricolage and one of our competitors, Vignette. Despite all of the praise Bricolage has been winning and the large corporations who are choosing us over competitors, we're still not satisfied. In fact, because our customers want it, we now provide templating in PHP. You can embed PHP in Perl and it works just fine. Of course, it's on the CPAN.


List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Enterprise Class Open Source Software 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Yeah, "enterprise software" is often of very poor quality, and designed poorly, because it is developed under tight deadlines. No time to think things through, just ship it!

    Compounding this problem is the turnover at proprietary software companies. The best way to get a raise is to switch jobs. The *only* way to avoid ever-increasing responsibilities is to switch jobs. As a result, people switch jobs frequently, and there is a constant refrain of "don't touch it, we don't really understand it any more".
    • The original version of Vignette was actually pretty interesting. It was not a CMS so much as a web development system created by some apache hackers at cnet.com. They hooked into the 404 handler to generate missing content on demand and then cache it so it could be served statically. A daemon process would clear out expired items. This is better than a pre-generation strategy (like Bricolage and Krang use) in some situations, especially when you have a large amount of content but only some of it gets l
  • Storyserver was my introduction to CMS back in 1997. It used TCL *gag* 7.2 when 8 was long since available. All templates were stored in the database (if anyone suggests large blocks of human editable text should live in an SQL database, shoot them.) Templates had no symbolic names, you had to refer to them by numeric ID. This lead to cryptic statements like "include 2938" and you just had to remember that template 2938 is your top menu bar.

    Templates had to be edited through a special Java editor that o
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.