Is Ruby is better than PHP

Aredridel wrote:

amrita – a nice templating system that I adore

I tried to use amrita for my web forum, but eventually gave up because
there are annoying bugs, development seems to be dead, amrita is
unnecessary complex and slow, the amrita interpreter requires huge
amounts of memory, and the amcc compiler generates incredibly bloated
code.

kwartz – another templating system

kwartz’s concept is not as “clean” as amrita, but it is much more
pragmatic. Instead of a CPU & memory intensive parser/VM at runtime it
can generate simple ruby code.

Release it! Users will help you build much better documentation
than you could easily write yourself, since they’ll ask questions about
what they want to know. This way you write the useful documents first.

That’s an alluring sentiment, but I keep thinking back at all the times
I’ve dismissed a library for lack of documentation. And usually I
didn’t check back for quite a while after that.

A project has to be really, really exciting before you’re going to go
through all the trouble of insufficient documentation. I think that’s
where the “10-minute rule” comes from.

I’d like to believe the reverse to be true, though. So I could release
Rails :slight_smile:

···


David Heinemeier Hansson,
http://instiki.nextangle.com/ – A No-Step-Three Wiki in Ruby
http://www.basecamphq.com/ – Web-based Project Management
http://www.loudthinking.com/ – Broadcasting Brain

Hello Andreas,

Saturday, April 24, 2004, 2:04:07 PM, you wrote:

Aredridel wrote:

amrita – a nice templating system that I adore

I tried to use amrita for my web forum, but eventually gave up because
there are annoying bugs, development seems to be dead, amrita is
unnecessary complex and slow, the amrita interpreter requires huge
amounts of memory, and the amcc compiler generates incredibly bloated
code.

kwartz – another templating system

kwartz’s concept is not as “clean” as amrita, but it is much more
pragmatic. Instead of a CPU & memory intensive parser/VM at runtime it
can generate simple ruby code.

Ever tried ClearSilver ?

···


Best regards,
Lothar mailto:mailinglists@scriptolutions.com

Hello David,

Thursday, April 22, 2004, 7:10:02 PM, you wrote:

Release it! Users will help you build much better documentation
than you could easily write yourself, since they’ll ask questions about
what they want to know. This way you write the useful documents first.

I’d like to believe the reverse to be true, though. So I could release
Rails :slight_smile:

I’m afraid that you are right. Its pure theory. Thats why we have 20
diffent libs of the same kind that do the same thing and each is
unuseable for new users.

···


Best regards,
Lothar mailto:mailinglists@scriptolutions.com

Lothar Scholz wrote:

Saturday, April 24, 2004, 2:04:07 PM, you wrote:

Aredridel wrote:

amrita – a nice templating system that I adore

I tried to use amrita for my web forum, but eventually gave up because
there are annoying bugs, development seems to be dead, amrita is
unnecessary complex and slow, the amrita interpreter requires huge
amounts of memory, and the amcc compiler generates incredibly bloated
code.

kwartz – another templating system

kwartz’s concept is not as “clean” as amrita, but it is much more
pragmatic. Instead of a CPU & memory intensive parser/VM at runtime it
can generate simple ruby code.

Ever tried ClearSilver ?

Not yet, but it looks very interesting.

That’s where I am at with Iowa. It’s easy to get an Iowa application up
and running. It’s powerful and easy to use and works well, and it is
fairly light on the memory usage. It works via a mod_ruby handler (the
applications themselves are in seperate process, so the usual mod_ruby
concerns don’t apply) or via a simple CGI script on any webserver that
supports CGI.

But if a person just downloads the CVS head and stares at it, the steps
involved in getting a sample app up and running aren’t going to jump out
and hit them in the face, even though the simplest case only takes a few
minutes to get running, and even a more complex setup using the mod_ruby
handler requires only a few more steps. They just aren’t obvious steps.

SO at the least I have to write a good installation guide and an overview
of how to use the most common 80% of Iowa’s offerings, or I really don’t
expect many people to bother downloading it and trying to use it.

Kirk Haines

···

On Fri, 23 Apr 2004, Lothar Scholz wrote:

I’d like to believe the reverse to be true, though. So I could release
Rails :slight_smile:

I’m afraid that you are right. Its pure theory. Thats why we have 20
diffent libs of the same kind that do the same thing and each is
unuseable for new users.