> -----Original Message-----
> From: Brent Roman [mailto:brent / mbari.org] 
> Sent: Monday, September 29, 2008 11:49 AM
> To: ruby-core / ruby-lang.org
> Subject: [ruby-core:19023] Re: Let Ruby be Ruby
> 
> 
> For another point of view...
> 
> We put Ruby on ARM-based, 2 Watt processor boards with 32MB of RAM and
> 8 MB of flash memory.  This is a typical embedded Unix configuration.
> One of the main reasons I stay with Ruby 1.6.8 is that I'd 
> have to hack apart the current standard library to make it 
> fit in my target environment and still have enough room for 
> my application.
> The 1.8 series interpreter is not much larger than 1.6.8.  It 
> is only the bundled libraries that bust my storage budget.
> 
> I think Ruby might serve in both the embedded and 
> server/desktop environments if a core-subset could be broken 
> out of the current monolithic standard library.  This core 
> would obviously include rubygems and its dependencies.  The 
> standard Ruby install for typical users would silently 
> install the full set of standard libraries as it does now.  
> However, those wishing more control of over their 
> configurations could install just the core. 
> 
> Would this packaging be acceptable for corporate IT users as well?
> 
> I'd suggest that the core libraries
> consist of Rubygems, its dependencies and most of the very 
> small set of libraries that shipped with Ruby 1.6.8.  But, 
> there may be better ways of deciding which libraries should 
> be in the core.  The important thing is to recognize the 
> benefits to Ruby inherent in factoring out this core library 
> subset so that this "lean Ruby" becomes a supported 
> configuration and not something that everyone who needs it 
> must invent (and continue to maintain) for themselves.

If we installed the current Ruby stdlib as a gem bundle, you could
achieve the same effect by just uninstalling all the gems you didn't
want, right? A bit of a pain, but not terrible.

Regards,

Dan


This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly 
prohibited and may be unlawful.  If you have received this communication n error, please immediately notify the sender by reply e-mail and destroy 
all copies of the communication and any attachments.