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 ]

Theory (10)

Theory
  (email not shown publicly)
http://www.justatheory.com/
AOL IM: dwTheory (Add Buddy, Send Message)
Yahoo! ID: dew7e (Add User, Send Message)
Jabber: Theory@jabber.org

Perl, PostgreSQL hacker; US politics junkie; Webapp developer; Portvangelist; profane iconoclast.

On CPAN see: DWHEELER [cpan.org].

Journal of Theory (10)

Saturday July 12, 2003
11:49 PM

Synergy at OSCON

[ #13415 ]

Well, I thoroughly enjoyed OSCON this year. I knew a lot more people than last year, and thus was able to socialize more, and talk to more people about more stuff. Really a great time, with lots of cross-pollenation of ideas.

My favorite moment came on Thursday. The PostgreSQL BOF was on Wednesday night, where Bruce Momjian was discussing some of the problems they've been having with the Win32 port, specifically with fork and exec. Now, I know nothing about C, but James Briggs suggested that the PostgreSQL guys talk to Gurusamy Sarathy about it, since he did the work on fork and exec for Perl and thus might be able to provide some advice for the PostgreSQL folks.

No one reacted much to this, but I thought it was a good enough idea that during the morning break on Thursday, I introduced my self to Sarathy and asked if he'd be willing to discuss it with the PostgreSQL developers. He said he'd be happy to. So during the afternoon break, I brought Bruce down to the ActiveState booth and introduced him to Sarathy.

Well, that seemed to go very, very well. Sarathy seemed willing not only to help them with some questions they might have, but perhaps even to contribute some work to the effort. It turns out that he views PostgreSQL as an important open-source asset, and is willing to put his code where his opinion is. He asked about subscribing to the PostgreSQL hackers mail list! He and Bruce talked for a while about the issues at hand, and there seemed to be a great deal of understanding and mutual respect. This could be a major benefit for the PostgreSQL community, and will in turn give Perlers another great OSS RDBMS that runs just about anywhere. Yay!

A similar thing happened on Thursday night. Andy Wardley of Template Toolkit fame has promised to create a TT burner for Bricolage. This will bring the total number of Bricolage templating systems to three (Mason, HTML::Template, and TT). After the action, I accompanied Dave Rolsky, one of the lead Mason hackers, into the bar where we ran into Andy. Andy started telling us that looking at adding TT to Bricolage had led him to hatch a plan to come up with a unified, foundational templating API that many or all of the Perl templating systems might one day be able to use, so that they might start to share a common feature set. And then, when one of them wanted to add a feature similar to a feature in another templating architecture, it might be able to just exploit the common API.

This seemed like a very cool idea to me, and Dave said that he would definitely be interested in participating in such an effort. I think that, if he can find the tuits, Andy may well start a project in this vein, inviting the Mason, Embperl, Apache::ASP, and other Perl templating hackers to collaborate. This could really be to the benefit of them all.

What a great conference. I can't wait till next year when I can see some of the fruits of these meetings, the spoils of inter-community synergy, and where it will happen all over again.

My apologies for those friends I didn't get a chance to spend much time with at the conference. All of a sudden I know so many people! See you next year.

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.
  • It would be great if Bricolage had a TT burner, with all the TT modules and plugins and my own codebase it would mean that I could build a web app in any of openinteract, openframe or bricolage according to the needs of the project.

    Great news

    I would also love to see some kind of common api or framework between the different templating systems available - in particular something that I would want for my autodocumentation / code generation projects would be some kind of reflection API so that I could run

    --

    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
    • And the next version of OpenInteract (the 2.x series) will be able to use HTML::Template (or Text::Template, or...) as well. All the TT functionality isn't there (particularly the plugin), but it seems the HTML::Template folks prefer it like that anyway...
  • Why not have the Postgres guys work with the Apache guys as part of the APR (Apache Portable Runtime library) which the subversion team is using for porting across platforms???

    Granted I dont know the details but I would imagine there is a lot of potential leverage opportunities with APR.

    --
    John Cavanaugh