From: Bill Kelly Date: 2006-07-26T12:59:03+09:00 Subject: Re: [ANN] Nitro/Og 0.31.0 From: "Jamey Cribbs" > > Jeff Pritchard wrote: >> >From the rubyforge summary: >> Nitro is an efficient, yet simple engine for developing professional Web >> Applications using the Ruby language. >> >> Guess it is a rails wannabe. >> > I personally have not used Nitro, and I have no idea how many hours the > Nitro team has spent working on the project, however, I am pretty sure > that the amount of work put into Nitro warrants that it deserves to be > referred to as something more than "a Rails wannabe". > > I don't mean to come across as critical of your statement; I just felt > like this should be said. I'd like to add that I'm not affiliated with the Nitro project itself, but I'm using Nitro to develop a commercial web application. I *think* Nitro has been around about as long as Rails. Certainly Nitro and Rails were both around before either one became popular. :-) On my current project, I started out in Rails, and bought the excellent PragProg Agile Development w/ Rails book, and also the superlative Rails Recipes book... Personally, (and this is 100% PERSONAL OPINION) Nitro ended up fitting the contours of my skull better than Rails, so I switched to Nitro. And I'm happy. .... I was going to write more, but I just refreshed the unread messages, and I see James Britt has already said the rest. * * * After some deliberation, I'd like to share a paragraph I wrote to the Nitro mailing list, circa my decision to switch from Rails to Nitro. . . . I am hoping this is acknowledged as personal opinion, and is recognized to be just my __personal impressions__: 2006-05-07 "(One of the things I _loved_ about Nitro vs. Rails, is how Hello World in Nitro can be literally one .rb file and maybe five simple lines of code. And how that Hello World can be morphed steadily--as in the screencast--into a more complex project piece by piece incrementally. Contrast this with Rails, which generates a skeleton project of 44 files and 31 directories - just for Hello World. I'm sure the argument is that for a large project one will eventually _need_ all this structure; but I much prefer the way Nitro gives me the opportunity to build incrementally with just the structure I want.)" Again, Nitro just meshed with my brain better - just a personal opinion, and I respect others who may feel differently. Regards, Bill (P.S. if anyone can find the Nitro screencast showing the evolution from simple Hello World "one liner" to a gradually more complex app, I'd appreciate a link, as I seem to have lost it. Thx.)