From: Thomas Hurst <tom.hurst@...>
Date: 2002-01-02T00:19:00+09:00
Subject: [ruby-talk:29962] Re: Announcing Ruby.APP

Did you hit <reply> when you meant <mail>? :)

* Stephan J. Schmidt (stephan.schmidt@neotis.de) wrote:

> The most important design goal is *ease of use*. Ruby.APP will provide
> the easiest way for building web applications (from my point of view
> :-)

echo "Write our web application, or you're fired!" | mail -s "Oi"
employee@mycompany.com ;)

> Where not to use Ruby.APP:
> - Module for web servers

A lot of systems are already running webservers - does it not make sense
to intergrate with them?  Especially when you're going to be serving
images, css etc.

> - Design-to-the-pixel websites

Now, that's got to be a personal thing, how does tag soup and JS
interfere with a web server in a way strict HTML and CSS don't?

> - Object Store: You do not have to write SQL queries.  Objects can be
> stored, retrieved, found and changed.  Relationships are automatically
> managed.

Not at the cost of performance, I hope, <grumbles about the last third
party CMS he tried which called 80 SELECTS on the front page>

> - Integration with IDE GUI builders and UML: The component based
> approach makes the development of GUI builders and the design with UML
> tools easy.

So long as it works with vim I'm happy ;)

> - Ruby.APP is free and open source (LGPL, BSD or Apache, I'm not sure)

BSD is the best choice if you want to be free, GPL's more if you're into
the evil FSF agenda :)

-- 
Thomas 'Freaky' Hurst  -  freaky@aagh.net  -  http://www.aagh.net/
-
Chamberlain's Laws:
	1: The big guys always win.
	2: Everything tastes more or less like chicken.