Richard

if you would like to have a real impact why don’t you help for real to copy 
edit and improve documentation. 
This is not your articles that will attract people, a strong documentation 
smoothing the learning curve
will. 
This is super easy you can edit text right in your web browser.

I do not think that you understand what I’m saying but I had to try. 
We have not many native english speakers and having better and more 
documentation is super
important but if people can could help don’t do it then we will do it slower. 

S


> On 11 Aug 2020, at 03:07, horrido <horrido.hobb...@gmail.com> wrote:
> 
> It's true, Smalltalk faces the same dilemma as Linux and Lisp. As a /family/
> of languages, portability is a genuine issue.
> 
> There's no getting around this dichotomy. You can have either a flexibility
> of choice or the tyranny of one standard, but not both.
> 
> The decision is a fact of life that we face frequently. You can have either
> the flexibility of dynamic typing or the safety of static typing, but not
> both. You can have either the natural modelling of the real world due to
> state mutation or the mathematical safety of immutability, but not both. You
> can have either the portability of a virtual machine or the
> close-to-the-metal performance of native code generation, but not both (JIT
> compilation notwithstanding).
> 
> Life is about choices. There will always be a place for different
> technologies. Smalltalk will not always be the ideal choice. That's why
> there are five entirely different languages that dominate our industry
> (Python, JavaScript, Java, C#, C++).
> 
> There is no reason why there can't be a sixth, especially if it can
> dramatically improve our productivity and make programming less cognitively
> stressful. Surely, that's worth fighting for.
> 
> Enough?
> 
> 
> 
> Richard O'Keefe wrote
>> Here is a challenge:  What is "Smalltalk"?
>> VAST, VW, and Pharo are quite different environments.
>> To the extent that they share a common syntax (which
>> they don't, quite), fine, but porting nontrivial
>> code between them is NOT easy.  They certainly have
>> very little in common as GUI kits.  All praise and
>> thanks to the people who *have* ported stuff.
>> 
>> 
>> On Tue, 11 Aug 2020 at 01:05, Richard Kenneth Eng &lt;
> 
>> horrido.hobbies@
> 
>> &gt;
>> wrote:
>> 
>>> https://smalltalk.tech.blog/2020/08/10/smalltalks-successor/
>>> 
>>> A bold claim. It'll be interesting to see if anybody challenges me on
>>> this.
>>> 
>>> 
> 
> 
> 
> 
> 
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
> 

--------------------------------------------
Stéphane Ducasse
http://stephane.ducasse.free.fr / http://www.pharo.org 
03 59 35 87 52
Assistant: Aurore Dalle 
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley, 
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
Villeneuve d'Ascq 59650
France

Reply via email to