From: Sean O'Dell <sean@...>
Date: 2004-06-29T06:34:32+09:00
Subject: Re: [OT] Re: Is it considered Harmful?

On Monday 28 June 2004 14:17, Hal Fulton wrote:
> Sean O'Dell wrote:
> > On Monday 28 June 2004 13:27, Florian Gross wrote:
> >>Sean O'Dell wrote:
> >>>>>>Oddly, Sean, when you are saying, "it worked like I said it could",
> >>>>>>I am hearing Guy saying, "yes - but it doesn't work like I said it
> >>>>>>wouldn't."
> >>>>
> >>>>[what ts did.]
> >>>
> >>>Ah, so it was insulting when I didn't accept his word outright.  I see.
> >>>Well, I meant no harm; I didn't know Guy knew so much about the
> >>> internals he could make a quick call like that.
> >>
> >>But if you really can't agree with me here, then I guess it is okay. In
> >>that case I just feel a bit sorry that a common denominator could not be
> >>found; that would make all the people who didn't even try to find one
> >>appear in a better light than they deserve.
> >
> > What are we disagreeing on?  I understand that Guy knows enough about
> > Ruby that he can quickly determine the likelihood that #class= would ever
> > be safe enough for release.  I'm not sure what part of what I said you
> > feel puts me in disagreement with you.
>
> He thought you were being sarcastic in the paragraph starting "Ah..."
> I had to read it twice, but decided you were not.
>
> Guy (ts) is not superhuman, of course, but I would speculate that he
> knows more about Ruby internals than anyone else outside Japan (and
> quite a few or nearly all in Japan).

Nope, no sarcasm from me there.  I wish I'd known that about Guy's expertise 
early on; I would have given his opinion more weight.  I try not to make 
assumptions either way, but I rarely accept someone on their word when they 
make generalizations.  If a person makes a claim and doesn't provide any 
background, I generally dismiss the claim.  I learned for myself why #class= 
was potentially dangerous.  Even Matz didn't offer any clues as to why it 
would be dangerous, but at least I am aware of his level of knowledge to 
simply take him at his word on the matter.  I didn't know Guy had any inkling 
about Ruby's internals, and he didn't offer much specific insight.  Even the 
threads I was directed to read made only vague reference to potential 
problems.  I learned what some of the specific problems are, but only from 
implementing the feature myself.

	Sean O'Dell