They need to work on the presentation. How do you get started ? How does the code look like ? etc. Not just "download this program and buy this book"
Pharo, the Modern Smalltalk
31–40 of 178 posts
Re: Pharo, the Modern Smalltalk
#32On a tangent: I wonder how everybody who writes for Medium feels about the new Quora-style nag screens. (I can only go on tangents since I saw the nag screen and bounced.)
Re: Pharo, the Modern Smalltalk
#33Is there a snippet of example code to look at? I browsed the pharo.org website, but couldn't find an example to give me a taste. I even tried googling "pharo example" and with a brief look at the results didn't find an example. Today, there are hundreds of programming languages competing for attention. It is in your interest to put an example front and center of why one should spend time looking into yet another prog…
I've always found the 'image' environment to be far more interesting than the language of Smalltalk itself. If you do find just code snippets, you're missing out on what I, at least, see as the most significant feature of the whole thing. The way it goes about defining the code is clunky, but the overall structure of 'images' and the workflow involved with them is fascinating. I could easily see something similar bei…
Re: Pharo, the Modern Smalltalk
#34Earlier quoted context omitted.
I've always found the 'image' environment to be far more interesting than the language of Smalltalk itself. If you do find just code snippets, you're missing out on what I, at least, see as the most significant feature of the whole thing. The way it goes about defining the code is clunky, but the overall structure of 'images' and the workflow involved with them is fascinating. I could easily see something similar bei…
Lots of other languages work/worked that way. System images were a common feature of many Lisp systems and some Forth systems in the 1980s.
Re: Pharo, the Modern Smalltalk
#35One interesting "killer app" might be the Moose platform [0]. It's basically an interactive environment for the analysis of software. Writing a parser is rather straight-forward and turning the AST into a visualization is also quite easy. This sort of feels like how I imagine a good IDE should be.
[0] http://www.moosetechnology.org/
update spelling.
Re: Pharo, the Modern Smalltalk
#36Okay, so lot's of praise for a language. But I have three questions that aren't answered by the article: 1.) How fast are programs written in Pharao? 2.) Is it possible to write complete and halfway modern looking desktop end-consumer GUI applications in Pharao? 3.) How good is it at parallel programming (i.e. multicore support, not just concurrency with green threads)? I'm always interested in learning a new languag…
1) Last time I tried it was reasonably fast for a dynamic language - somewhat slower than javascript (V8) but faster than python (cpython) to give you a ballpark 2) Yes, but ou will not use native widgets. The way you write applications is: you write code by modifying the behaviour of objects in the Pharo application (which is your editor, debugger, GUI, version control system and so on), then you strip off the parts…
However, I've looked at screenshots and the default widget system seems fairly reasonable. So I'll check it out anyway.
Thanks a lot for the replies, they were helpful!
Re: Pharo, the Modern Smalltalk
#37Re: Pharo, the Modern Smalltalk
#38Is there a snippet of example code to look at? I browsed the pharo.org website, but couldn't find an example to give me a taste. I even tried googling "pharo example" and with a brief look at the results didn't find an example. Today, there are hundreds of programming languages competing for attention. It is in your interest to put an example front and center of why one should spend time looking into yet another prog…
I've always found the 'image' environment to be far more interesting than the language of Smalltalk itself. If you do find just code snippets, you're missing out on what I, at least, see as the most significant feature of the whole thing. The way it goes about defining the code is clunky, but the overall structure of 'images' and the workflow involved with them is fascinating. I could easily see something similar bei…
From what I understand, none of this applies to Smalltalk. You always modify code on the fly, so you may end up with properties which exists, but no current code ever sets them. Or your program ends up in the invalid state, and you have no idea why -- is it a genuine bug or did it happen few minutes ago, when the function was still incomplete?
Re: Pharo, the Modern Smalltalk
#39I'll take "powerful" versus "cleanest and purest" any day, thank you very much. Sorry but i'm staying with CLOS whenever i want to do object-oriented programming without feeling limited.
The author is on a pro-Smalltalk crusade (which I find just fine, Smalltalk is a great lang, and in a perfect world, it would be as popular as Javascript is today), but does so at the expense of constantly deriding Clojure, Common Lisp and Racket, which I find silly.
Re: Pharo, the Modern Smalltalk
#40I'm sorry but the 3d image of the light house is horrible. It reminds me of POV-Ray renders from the 90s. Is Medium so poor that they can't afford a competent artist?