On 13 Aug 2009, at 18:04, Matt Todd wrote:

> I was talking to a friend of mine yesterday and he mentioned that  
> thought the Rack package itself seemed to be slightly bloated by  
> things like Basic Auth et al. He mentioned two things I thought were  
> interesting and I wanted to get your feedback on it:
>
> 1. Like Merb, Rack probably could benefit from using a core and more  
> separation of functionality, and

On this point, I have massive trouble agreeing. In recent months, the  
disparity of supported versions of thin/rack/sinatra has been a big  
problem for some folks (integrity mainly). Splitting up into a crazy  
number of gems causes a lot of management overhead and sysadmin /  
deployment crap that I almost never see done right. The only good  
solution is the recently released bundler system by wycats, halogrium  
and carllerche. Requiring something like that to "get by" is far far  
far worse in my opinion.

We're not as fat as you might think, because stuff you don't touch is  
never loaded. Do you have a genuine use case to drop 100K or so out of  
core, by adding ~500K (or more) to deployment overhead of *each*  
composite part?

> 2. Rack core should only include what's necessary for Rack::Lint to  
> validate a basic application at minimum.
>
> Thoughts?
>
> Matt
>
> -- 
> Matt Todd
> Highgroove Studios
> www.highgroove.com
> cell: 404-314-2612
> blog: maraby.org
>
> Scout - Web Monitoring and Reporting Software
> www.scoutapp.com