From: James Britt Date: 2006-07-31T00:44:11+09:00 Subject: Re: [ANN] Nitro/Og 0.31.0 Nathaniel Brown wrote: > After looking at the Nitro video, the structure is very loose, which I > appreciate and somewhat dislike at the same time. Having default > organization is nice, but at the same having useless organization is just > that - pointless. > > Would be nice to see a Rails version of Nitro, with the directories already > there for you, with the auto-loaders present for things such as Models. > > On that same note, I noticed during the screencast, you had to directly > require the Model. In Rails it has the auto-loading mechanism which will > attempt to locate the model in specific directories which are based on the > load path. I am under the impression nothing like this exists in Nitro? It's a mixed blessing. If you know that all of your applications are going to follow a certain file layout then it helps to just have that handled automagically. But the code to do that is trivial, so rather than have to accept the layout and code bundling presented by the framework, you can pick your own. You still get auto-requiring while not having to adopt a forced layout or wade through a dozen files and directories you may not have any use for. YAGNI, and so on. But there are benefits when developers are following the same conventions. For example, people can reasonably expect that any random Rails app will have certain files in certain locations. You can use engines and plugins and helper tools (such as AutoTest, which is quite slick) written by other people, and they Just Work. -- James Britt http://www.ruby-doc.org - Ruby Help & Documentation http://www.artima.com/rubycs/ - The Journal By & For Rubyists http://www.rubystuff.com - The Ruby Store for Ruby Stuff http://www.jamesbritt.com - Playing with Better Toys http://www.30secondrule.com - Building Better Tools