On 6 December 2010 21:22, Tudor Girba <[email protected]> wrote:
> This kind of view is nice as a joke, but I also think it tends to be counter 
> productive. We should not kid ourselves. There are so many books because 
> there is a market large enough to consume them.
>

No, but you know, books about Java or C++ dedicating a full chapters
explaining classes, visibility rules, constructors, destructors,
virtual functions, templates or <generics> and all things related to
that. A lot of wasted paper (where the Green Peace looking? ;))
And now take the smalltalk at the other side. What we have? Just
classes and methods. Simple rules. End.
So, at the day when one student finish learning the basics of java or
C++, a student who decided to learn smalltalk will finish learning a
standard class library basics, and will be ready to go with first
coding attempts. While Java/C++ student will still be 2 or 3 chapters
away from finishing with basic language concepts and rules.

It is a lot of time for reading, not mentioned about how much time it
takes to comprehend and understand all the concepts and remember them.

Yes, maybe its a bigger market. But i know a good way to learn
something: write a description (book) of it. So it looks like many
people wanting to learn C++ or Java so bad, that they start writing a
books about it. Good for them. Good for readers.
Bad for Green Peace :)


> Cheers,
> Doru



-- 
Best regards,
Igor Stasenko AKA sig.

Reply via email to