Thanks to all your feedback, the Pharo Quick Start guide gets better and
better. Now, the reader will *really* see how easy Pharo is by the end of
the second section. The rest of the guide deals with the System Browser.
I'm very happy about this because I keep hearing crapola from JavaScript
developers saying how low the entry barrier for JavaScript is (everybody has
a web browser; all you need is a text editor and you can see immediate
results). I wanted to drive home the point that the entry barrier for Pharo
is exceptionally low, too.
And it's just as low as for Elixir, Julia, Nim, Racket, and other languages
I've recently tried.
Offray Vladimir Luna Cárdenas-2 wrote
> Maybe the core of the suggestion is start with the Playground and then
> go to the code browser, that's my workflow coming from other languages
> like Python and Scheme, and having the playground to emulate REPL before
> going to code browser has been really refreshing and also "going from
> scripting to object" is a well received approach in our Data Weeks.
>
> So the Pharo Quick Start, after providing the installation instrucctions
> could be something like:
>
> """
> The classical "Hello World!" program can be done in one line in Pharo,
> as in most dynamic languages by opening the Playground ("Cmd + Shif + o"
> shortcut on Mac o "Ctrl + Shift + o" on Windows) and writing "Transcript
> show: 'Hello World!" (see figure below), but we are going to learn also
> how to put this simple script into the Code Browser, a place where much
> of the Pharo power resides.
>
>
> ^ Up: The "Hello World!" example as a one-liner script ran in the
> Playground.
>
> """
> and then I would add the succinct explanation you are doing about how to
> create the Greeter.
>
> Cheers,
>
> Offray
>
> On 08/12/17 09:41, horrido wrote:
>> I'm not sure what you mean by *PrintIt:*. If you mean type 'Hello World'
>> in
>> the Playground and just *Print it*, that's not really a "program."
>>
>>
>>
>> Sean P. DeNigris wrote
>>> hernanmd wrote
>>>> To me the Hello World in Smalltalk was always just writing: 'Hello
>>>> world'
>>> +1. While putting it in a class shows a few more of the system's
>>> features,
>>> it also makes it seem more complex than other languages, when that's not
>>> really true. Why not just PrintIt: 'Hello world'? If it seems important
>>> to
>>> show classes, maybe start with PrintIt: 'Hello world' and step-by-step
>>> build
>>> through `Transcript show: 'Hello world'` to the class-based solution.
>>>
>>>
>>>
>>> -----
>>> Cheers,
>>> Sean
>>> --
>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>>
>>
>>
>>
>> --
>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>>
>>
>
>
>
> amgfcildhiemjbph.png (21K)
> <http://forum.world.st/attachment/5060126/0/amgfcildhiemjbph.png>
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
