For those that have subscribed to my media (what I’m reading, listening to, watching, playing) RSS feed
or visit the site and check the right sidebar, you’ll notice that I’ve
added a Ruby (a programming language) book and a Ruby on Rails (a web
development framework) book.

I’ve been hearing about both technologies for a while but recent blog
reading has pushed me from being mildly interested to, well, to the
point where I bought two books about it.

If it goes well, I might consider writing the new version of this site in Ruby on Rails instead of ASP.NET 2.0.

I haven’t made up my mind really, but one of the things that I really
dislike about ASP.NET is it’s marriage to the IIS (and therefore) the
Windows platform. Of course, that’s another way that Microsoft locks
you into things.

Maybe some time after Microsoft’s Office Software and OS software
cash cows are taken away from them, what’s left of Microsoft will let
IIS work on other OS’s.

Don’t get me wrong, ASP.NET 1.x has treated me right and there are
things that I really like about the platform (my favorite thing is the
separation between code and presentation). We’ll see what happens.

So what does this have to do with “a new stack?” Well, everyone in the industry knows what the LAMP (Linux-Apache-mySQL-PHP)
stack is, but I was thinking about if and when I get around to using
Ruby on Rails; I won’t be using the LAMP stack, but I’d use elements of
it. With that in mind, I present some new stacks:

• the LLiMR (Linux-Lighttpd-mySQL-RubyonRails) stack


• the other LLiMR stack (Linux-Lighttpd-MSSQL-RubyonRails)


• the LLiPR (Linux-Lighttpd-postgreSQL-RubyonRails) stack.

You heard it here first. :)