Daniel Vöěkerts wrote:

> Oh it is going on. By your hint, I searched for PocketRuby and patch and
> found an thread on ruby-dev. Great I thought. Unfortunatly the thread is
> in japanese?
>
> I can spanish, french, english, german and Java(tm) *g*. A automatic
> translation failed. Any help is appreciated.

I would try Babelfish, although the translations that I try for
Japanese->English tend to make things sound a little silly. But at
least it gives me some hints as to what is going on. Frankly this is
still the one aspect of Ruby that leaves it lacking for me as a
production solution for some areas in my company. After over a year of
trying I have still found it isn't totally friendly toward Win32/MSVC
and seems biased toward Linux/GCC. And trying to rig my own solution is
tough because key documentation can be Japanese only in certain
situations I have run into (e.g. - PocketRuby, DL).

I love Ruby's syntax, intuitiveness, mindset, and elegance. It makes
sense to me more
than any other language. And perhaps that's what frustrates me the
most, since I have to resort to other (less preferred) languages for
certain tasks. I'd rather be doing it in Ruby. Not to troll, but if
Python is a more prominent language compared to Ruby I would bet in
part it's because it's more Windows-friendly. Sure it's been around
longer and had more libraries and extensions built for it. But if
Windows clients make up the vast majority of OS market share it's
certainly easier to deploy solutions that don't involve digging deep
under the hood to compile things :-)