From: Thomas Hurst <tom.hurst@...>
Date: 2002-02-20T03:59:53+09:00
Subject: Re: Ruby for web development

* Billy (beripome@yahoo.com) wrote:

> I assume you mean URL. Havn't got one yet its all on my local.

That wasn't a typo, URL's are subsets of URI's.

> Zend 2 sucks. Its reaks of sticky tape and chewing gum if you get my
> drift. They are just tacking on extra features and at the same time

I must admit I do have the odd laugh at some of their suggestions, half
of which are in the name of "performance", in saving a couple of ns in
hash lookup time or so.

> Hell I wouldn't use Windows for a production environment either. In
> fact I wouldn't use windows at all if I had the choice (thats maybe a
> little harsh - 2000 is ok). But I develop on windows cause I have to
> (Macromedia Dreamweaver/

Ugh.  Not a tool I'd use to generate real life HTML, unless maybe I was
in desperate need to use tag soup, otherwise I prefer to stick to
writing XHTML + CSS.

> fireworks + photoshop) and you'll find that a huge amount of
> webdevelopers do that too. Then transfer to linux server.

I write and test on my Windows XP box and run and host the code on a
FreeBSD server.  Keeping the test environment the same as the production
environment in that way keeps flexibility up, keeps me close to the best
tools for the job (i.e. recent vim in ports, as opposed to 6 month old
vim 6.0 exe that's 220 patch levels out of date) and keeps me
productive despite Windows' best efforts.

> I just got eruby working. Nice. And I guess since Im not in production
> it doesn't matter if I run eruby as CGI.

I'm surprised you first talk about a big CMS system and then want to use
eruby.. I prefer to keep HTML and logic seperated as much as possible,
otherwise you end up with something that looks like phpNuke.

> Get mod_ruby going for linux properly. Ruby could steal a huge user
> base from PHP, if eruby + mod_ruby was a real option.

Stop using Linux and *ix interchangably :P

> > Maybe you might concider using PHP as a thin caching front end to
> > a Ruby-powered daemon or so, or even coding to a platform like
> > WEBrick.  Probably more for interest value than anything else, but
> > you don't mention whether you're coding for a mission critical
> > environment or just to make something cool.
>
> I'm very seriously thinking about something along these lines. Push
> all the logic over to Ruby maybe then have it generate PHP code for
> simple dumb serving of pages.... brain working.... brain working...

Blegh, I don't mean that, I mean have a Ruby mycmsd run in the
background and communicate with it over a simple protocol (maybe even
http) to manage all the logic, and have a small bit of PHP at the front
end that manages requests, passes stuff onto the daemon and then caches
it locally.

You could even serve direct to the clients and turn your CMS into a
fully blown web application server, which would have caching/pooling
advantages.

-- 
Thomas 'Freaky' Hurst  -  freaky@aagh.net  -  http://www.aagh.net/
-
The hardest thing in the world to understand is the income tax.
		-- Albert Einstein