-

The above thread has shown the direct responsible for the defective "ri
Class" documentation:

It's the language designer, Mr. Yukihiro Matsumoto.

-

Mr. Matsumoto had not the decency to publically confirm this - and to
apologize for the caused inconvenience.

He had not the courage to say "Hey, lovely folks of ruby-talk, this guy
is right, with all his points - and I'm the responsible".

He had not the strength to say "Behave like analysts, like scientists -
and stop throwing stones to an researching individual".

-
-
-

Mr. Matsumoto has silently admitted point b)

"Horizontal arrows do not represent inheritance"

-

He has _not_ admitted point a)

the faulty and missleading usage of the term "metaclass"

But in past, he heas clearly confirmed what is reality:

"In Ruby, the Class class is the class of all classes, no metaclass."
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/40537

but he uses the term "metaclass" in source-code:

"metaclass = rb_make_metaclass(rb_cObject, rb_cClass);"
http://www.ruby-lang.org/cgi-bin/cvsweb.cgi/ruby/object.c?rev=1.168

setting the foundation for many missunderstandings.

Fact is: the "exclusive class" of an ruby object is not a "metaclass".

-

He has not admitted point c)

An language future, which is not accessible via the standard object
mechanisms is not a part of its object model. It's an implementation detail.

Mr. Matsumoto should have either:
  * admitted the validity of point "c", or
  * confirmed that his _refusal_ to make this directly accessible was a
failure.

btw: what he "considered abuse" is irrelevant:

http://www.ruby-talk.org/cgi-bin/scat.rb/ruby/ruby-talk/40548

-
-
-

"Sorry for being a Vapoware for Long Time"
"Too Much Ideas popping in my Brain"
http://www.rubyist.net/~matz/slides/rc2002/mgp00026.html

This is nothing worse.

Worse is the inability to admit and the inability to accept analytic
input from the community.

Worse is the inability to couple the development process to the own
understanding processes.

-
-
-

I've read somewhere, that Mr. Matsumoto is working on Version 2 of ruby.

He will most possibly understand, why I have intensive doubts about ruby
and its future.

"Human Factor" - "Character of Designer".
http://www.rubyist.net/~matz/slides/rc2002/mgp00018.html

Yes, this is very important.

His ability to admit failure.

His ability to apologize.

His ability to protect those in a weaker position.

But most of all:

his ability to "spiritually lead" a community, thus it becomes
efficient, and it does not behave publically like herd of savages in the
middle ages.

-

"Human Factor" - "Developing Community" "User Community".
http://www.rubyist.net/~matz/slides/rc2002/mgp00018.html

I thought the "savages of comp.lang.lisp" would never be topped by
another community.

I was wrong.

The major/minor parts of this community are as ridiculous as inefficient.

A few positive exceptions, which act like scientists and analysts.

-
-

Ruby [context of comp.lang.ruby], the summary is:

Weak puppets with a weak leader.

But...

...possibly I'm wrong.

And all this was just a missunderstanding.

-
-
-

My subconscious has signaled yesterday that this was my last public
analysis.

I've not expected this would take so many years.

I'm happy.

It's so exhausting to assimilate the weaknesses and strenghts of systems
which have an high amount of human factors:

http://lazaridis.com/efficiency/process.html#ideal_structure

-
-
-

I will soon publish an updated version of The Ruby Object Model, which
will contain the "exclusive class" or "xclass":

http://lazaridis.com/case/lang/ruby

This should help evaluators to look at ruby, without getting confused
from this [unnecessary] insider-terminology.

-

Have a good time.

.