Re: Best practices for "static" code

> Thoughts? I've had such a directory for years in my webapps, although I've always called it "assets", which I like better than static. But that's just the bikesheds color, I guess.

Best practices for "static" code

This email from Beorn: Beorn wrote: Ruby's more extensive skeleton isn't all bad: Ruby generates a lot of empty directories that actually "sell" the notion that this is a framework that can grow with you and has best practices for testing, documentation, using AJAX, logging, staging, where to