On Sat, Apr 26, 2008 at 9:23 AM, Arie Kusuma Atmaja <
[EMAIL PROTECTED]> wrote:

> 2008/4/11 Leo Laksmana <[EMAIL PROTECTED]>:
>
> >  Mau nanya ke Bung Arie, filosofinya pertanyaan ini apa yah?
>
> I'm temperamental when talking about philosophy. Better not to talk
> about that. Males panjang panjang omongin filosofi, enak saya mbaca
> buku yg saya suka aja sambil rileks.


Hahaha, oke... won't poke my finger anymore than... :)


>
>
> > Karena ini kan gak ada practical use-nya di real life coding.
>
> s/gak//
>
> as a developer we often deal with small and specific items, a "small"
> thing in Ruby like every one symbol can have memory leak in Hash can
> destroy our life and we consider that as "not small" man, that's
> serious. I don't know if one example I mentioned has been patched but
> I hate it when it became the culprit then our app goes wrong, not
> because of our codes, but because of Ruby bugs (now I remember I'm
> used to use ruby to write what what what what =)) everything just
> sucks.
>

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!!!)

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).


> So, a mixin implementation idea that has been implemented in a
> software using C language is something _big_ and _practical_ for me.
> As we know we might have tremendous different standard to say it's
> practical # A business guy might think ruby practical use is when it
> has value and we can get $$$$ benefits from it, A marketer might think
> ruby practical usage is when it has a great approach that could impact
> to transform customers to become our loyal customers, A coder might
> think ruby codes that can return result of
> "3.months.ago.beginning_of_day" is something.
>

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...


[Non-text portions of this message have been removed]

Kirim email ke