2008/4/26 Leo Laksmana <[EMAIL PROTECTED]>: > well, i'm a newbie in ruby (wow, that rhyme nicely eh?) so i guess your > concern doesn't really apply to me yet since i'm betting you're a guru > (compliment!!!)
Thank you for your trust. I'm not a guru at all. I only like sharing what I've learned (and also like to learn each other, I actually treat my friends anywhere just like my neighbour programmer friends, so we're just learning together, no teacher, no guru, I personally will say I don't know if I don't know, and will say I know and explain if I know). IMO what someone would call someone an expert is best to be specific (not partially), say if I know ruby it doesn't mean I also understand how to make a Mobile Gateway software or maybe Kannel in Ruby or say it doesn't mean I understand 100% of how any other alpha-beta-not-release-yet software works that's probably integrated with Ruby although I might be very happy to learn those many new things integrated with what we always call fun (I mean Ruby). In fact I'm a newbie too. I always like learning of how to maximize of what I have done because I'm just not satisfied yet with my slow achievement. That's number one. Number two is for me saying someone is an expert in something and something is not important, what important for me is, is this guy enlightening? if yes, then good, otherwise, crap (the title is useless then, I'm learning of how to listen to the _content_ and not look at the person's title/status who speaks). > now you're mentioning memory leaks, are we talking memory leaks in the > RubyVM here? If so, in terms of stability, is it a big factor? Inherently > any VM arch will have some memory leak. I want to know how "bad" (notice the > quote) is it in stock RubyVM? How does it compare to other implementation of > RubyVM (i.e. JRuby). Howa that's too deep and too low for me. What I complained was the impact of that memory leak. Of course if I have the power to patch it myself I will do it, but since I can't do that so I got headache :-) for example I have a complex hash then one of those hash keys will be changed automatically as a result, of course that's like chasing a ghost, but of course we can say no software got no bugs, but we as developers should have anticipated for that. That's all. > point well taken... kinda lost in your paragraph but i guess you're talking > about value and proposition of ruby for you as a programmer... i guess it > boils down to philsophy (ooops, i mentioned it again :) as i said in a > recent post, a programming language is just a means to an end. i mean > business owners, marketers (you mentioned) should have care less about ruby, > but think about the benefits from the product that derived out of a product > coded in ruby. we as a developer do care because it inherently help us to > better help business owners and marketers in creating their products. > > looks like it has become a philosophy chat here (strike 2, another one and > i'm out :) i'm gonna leave it at that and stop rambling... > > cheers, > -Leo > PS: hope to see you whenever you're in jakarta... oh iya, sama sama. nanti saya kabari kalau berada disana. -- http://tinyurl.com/2bjgvn
