Interview with Jesse Vincent

Hi there,

I don’t know if everybody know about it, but there’s a interesting interview with Jesse (posted in 29/09) on link below:

http://perlcast.com/2005/09/29/interview-with-jesse-vincent/

Congratulations Jesse… Really nice interview!!

Regards,

Rodolfo de Moraes Reis
Diretoria de Soluções de
Inteligência de Negócios
CPqD Telecom & IT Solutions
Tel.: +55 19 3705-5986
Fax: +55 19 3705-6786
rmreis@cpqd.com.br
www.cpqd.com.br

So Jesse,

Why are the secret projects secret?

-Curious Todd

So Jesse,

Why are the secret projects secret?

Mostly, because we’re not ready to talk about them yet.

So what are the pieces of Jifty? I assume DBI is at the
core. I always figured that RT’s access control
architecture could be a separte perl module. I guess
custom fields, transactions, and attributes are all good
candidates. What else?

So what are the pieces of Jifty? I assume DBI is at the
core. I always figured that RT’s access control
architecture could be a separte perl module. I guess
custom fields, transactions, and attributes are all good
candidates. What else?
Jifty-DBI is prototype of the DBIx-SB 2.x.
it’s API rework, a lot of backward incompatible changes, but much
saner interface.


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

Buy your copy of our new book, RT Essentials, today!

Download a free sample chapter from http://rtbook.bestpractical.com

Best regards, Ruslan.

So what are the pieces of Jifty? I assume DBI is at the
core. I always figured that RT’s access control
architecture could be a separte perl module. I guess
custom fields, transactions, and attributes are all good
candidates. What else?

Let’s put it this way: Jifty is my vision of a sane way to build
web-based applications in perl. I’ve taken what I’ve learned over the
past…yow…decade and tried to extract out the commonalities and
complexities so that what you’re writing is your application, not a
bunch of boilerplate code for dealing with the same thing time and time
again.

Custom fields, transactions and attributes don’t currently figure into
this. I mean, they’re all easy to do, but they’re not exactly common to
every application.

So what are the pieces of Jifty? I assume DBI is at the
core. I always figured that RT’s access control
architecture could be a separte perl module. I guess
custom fields, transactions, and attributes are all good
candidates. What else?

Let’s put it this way: Jifty is my vision of a sane way to build
web-based applications in perl. I’ve taken what I’ve learned over the
past…yow…decade and tried to extract out the commonalities and
complexities so that what you’re writing is your application, not a
bunch of boilerplate code for dealing with the same thing time and time
again.

Custom fields, transactions and attributes don’t currently figure into
this. I mean, they’re all easy to do, but they’re not exactly common to
every application.

By ommission are you saying the access control does fit into “this”?
What types of stuff will be covered? Just excited to see what
cool new tools I can look forward to…

By ommission are you saying the access control does fit into “this”?
What types of stuff will be covered? Just excited to see what
cool new tools I can look forward to…

I’m not saying anything. It’ll ship when and if it works. Right now,
it’s our inhouse pet project. But I’m pretty sure that when it’s fully
baked, you’ll like it.