[Nitro] New Blog Article About Nitro/Og
william.full.moon at gmail.com
Fri Oct 26 10:13:53 EDT 2007
Hey Gang ...
I can quite see the point, and I am personally a bit sad that the framework
itself is not available now.
There are simple things (project management) things that need to be done. I
sent a list out earlier to George regarding what is needed to be production
My perspective as "audience" is that it is too hot for people to just let
BE. This is not a wise attitude. Sooner of later there as to be "ready
enough" to say let go -- Freeze it as stable.
It is easy, it takes under 5 seconds to make a decision.
Everything else is discussion. Action follows decisions.
Personally (again) I believe Nitro is the best concept I've seen in computer
deplpoyment management for 20 years.
The risk with these frameworks is of becomeing bloated. So locking down a
release now is advised. The next release can cull bloat. One has to
provide migration pathways for real-life projects. And one needs
You can say, a project gets the following its documenters earn for it.
Think about that.
And set some action plans ...
(keep up the good work)
On 26/10/2007, Trans <transfire at gmail.com> wrote:
> On Oct 26, 1:25 am, James Britt <james.br... at gmail.com> wrote:
> > http://www.urubatan.info/2007/10/ruby-out-of-the-rails-nitro-and-og/
> > Perhaps folks here could add comments to answer some of the questions
> > and concerns raised in the posts, specifically about automatic code
> > reloading, and the claimed lack of anything like Rails' migrations.
> To be honest. At this point, I don't think Nitro is ever going to make
> it beyond niche use. I've been following Nitro for a long time now,
> and while it certainly has improved a lot, there are no signs that it
> will ever move past the "some day" state it is in right now. Just look
> at the evidence:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Nitro-general