Fortunately Smalltalk is a never ending journey into the land of weirdness and Pharo is its champion. Pharo is by far the most actively developed open source Smalltalk out there. Most likely more actively developed than the commercial ones too. So the overlap is pretty minimum actually.��

Smalltalk is not a programming language. Its a live coding environment that has also a very minimalistic language. Yeap documentation is a big problem in Pharo. I was complaining about it a few days ago. However people here are very helpful and very friendly to newcomers (unlike other programming languages ) and stackoverflow questions never go unanswered so you are not alone and people can help a lot. So its not that bad. Also there is already a lot of documentation about Pharo. Pharo for The Enterprise , Pharo By Example and Deep Into Pharo should keep you occupied for months if not years.��

As a newcomer its important to keep an open mind, Pharo is actually easy to learn but unlike other programming languages is not the same thing repackaged diffirently . Its quite diffirent actually and I think that is what makes it so productive and fun.��

In any case the secret of learning is very simple ... ask and you shall receive ;)

Oh and welcome to Pharo .And remember if you are not having fun then its a Pharo bug and you should report it ;D��


On Thu, Aug 7, 2014 at 10:56 PM, Ichiseki <is076@outlook.com> wrote:
Konnichiwa
First thanks to those that gave me some directions to start with Pharo /
Smalltalk.
Now I have some questions that I'm sure are very stupid.
The first one is, is there a way to use the bouncing atoms and the lights on
on Pharo 3? Because I tried to build it in there and it doesn't work
The second one is why there are like three different smalltalk environments?
Pharo Squeek and Cuis? What are the differences? Is there a standard? I find
this extremelly intriguing as it seems like there is a lot of dupplicate
effort?
The third one is which is the line between the core language and frameworks
and libraries in Pharo?
I found that, for instance Cuis has something like a basic image and some
external frameworks, pharo has some internal frameworks and lots of
externals. This is weird from someone comming from other languages.
The fourth is I found that documentation is very, very scarce especially for
some frameworks. This is also a major drawback for a newcomer to pharo. A
very thick entry barrier.

Thank you
Ichiro




--
View this message in context: http://forum.world.st/Two-Questions-from-a-Newbie-tp4772384.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.