[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=20
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=20
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.=20

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.

- brent




Wolfgang N=C3=A1dasi-donner-2 wrote:
>=20
> Neil Stevens schrieb:
>> Trans wrote:
>>> On Sep 25, 1:39 pm, "Berger, Daniel" <[e-mail]> wrote:
>>>> Then there's the other option of removing everything from the standard
>>>> library completely except rubygems, and letting folks install only wha=
t
>>>> they want. But, maybe that's another topic. :)
>>>
>>> Probably not quite everything should go. But, given that RubyGems is
>>> now standard, and used by everyone, I'd say that sounds like a damn
>>> good idea.
>>>
>>> The problem with including all these extra libraries is that it
>>> discourages developers from trying, using and building alternatives.
>>> In a way, Ruby reminds me of Windows in this respect, we all know the
>>> effect of it's bundling of IE. I'd much rather see Ruby take the light-
>>> weight open road. While it may not be quite as convenient to install,
>>> in the end I think we'd see much higher quality libraries.
>>=20
>> And the counterpoint to that, is if Ruby's standard library is light on=
=20
>> features, it will discourage people from even trying it.  If Python and=
=20
>> PHP can do X, Y, Z out of the box, but you have to install other=20
>> libraries to get Ruby to do those things, it will be counted as a strike=
=20
>> against Ruby.
>>=20
> In addition it will difficult to use Ruby in some companies for ad hoc=20
> tools, because it is usually not allowed to install additional things.
>=20
>=20
>=20

--=20
View this message in context: http://www.nabble.com/-ruby-core%3A18937--A-s=
tupid-question...-tp19673111p19728569.html
Sent from the ruby-core mailing list archive at Nabble.com.