I find this thread somewhat interesting. When I’m shopping around
for an application, I typically look for one in terms of its
functionality; not what language it’s written in.
For the people that are asking for a ruby email app, why? For
illustrative purposes, so you can see how they do “x”? So you can
more easily modify it? Something else?
I find this thread somewhat interesting. When I’m shopping around
for an application, I typically look for one in terms of its
functionality; not what language it’s written in.
As do I, in most cases.
For the people that are asking for a ruby email app, why? For
illustrative purposes, so you can see how they do “x”? So you can
more easily modify it? Something else?
That and more.
Speaking only for myself:
So I can see the source and pick up tricks from it.
So I can modify it.
So I can contribute to its development.
So I can know the API for the database and data
formats and handle them independently of the client.
Perhaps most importantly: So I can easily write
internal scripts for it in Ruby.
As regards (5): One of the things that keeps me using
Outlook Express in spite of its problems is the “rules”
capability. (That, and sheer inertia – I’d hate to
think about importing 30,000 messages or so into a new
mailreader. Though if it were easy and errorproof, I’d
still do it.)
eventually able to run in a number of different platforms
easier to modify: written in everybody’s favorite language, the app
could eventually be adapted to suit one’s needs
extensibility (hooks): something written in Ruby is more likely to be
extensible with Ruby Having a Ruby interpreter inside can allow
“smart” filter rules, message formating…
Plus the coolness value and the feeling that, if it’s been done w/ Ruby,
it’ll be more solid in less time.
···
On Fri, Aug 16, 2002 at 04:40:33AM +0900, Michael Campbell wrote:
For the people that are asking for a ruby email app, why? For
illustrative purposes, so you can see how they do “x”? So you can
more easily modify it? Something else?
I would have said all of the above except #4 hold true for me as well, then
I started thinking it might be interesting to build a mailer that actually
stored the messages in a relational database (I guess once you get one of
these installed on a server on your local LAN or even the same machine a
lot more problems start to look like they’d be good candidates for
databases… just think of the possibilities using SQL to query your
mailbox!)
Plus, a Ruby email client could be one of those applications where “if one
hears it talk, one only wants to program immediately in Ruby”.
-michael
···
On Thursday 15 August 2002 15:18, Hal E. Fulton wrote:
So I can see the source and pick up tricks from it.
So I can modify it.
So I can contribute to its development.
So I can know the API for the database and data
formats and handle them independently of the client.
Perhaps most importantly: So I can easily write
internal scripts for it in Ruby.
As regards (5): One of the things that keeps me using
Outlook Express in spite of its problems is the “rules”
capability. (That, and sheer inertia – I’d hate to
think about importing 30,000 messages or so into a new
mailreader. Though if it were easy and errorproof, I’d
still do it.)
Having a Ruby interpreter inside can allow