Where does the Pharo runtime run? To which platforms can I bring its solutions? are these standalone binaries or can I create libraries or code which play well with other languages and systems?<p>Every time I look at a programming language, and at the HN it is every second day, I think about what kind of problems can it solve, and for what kind of platforms these compile/run their runtimes.. and surprisingly not many programming languages inform properly about the most basic feature, and prefer to go deeper into their.
Detailed changelog: <a href="https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70ChangeLogs.md" rel="nofollow">https://github.com/pharo-project/pharo-changelogs/blob/maste...</a><p>Sounds incredible! Git integration and related code management changes are especially nice, 64-bit by default is great and support for binary packages is also important. New, extensible code browser (Calypso) also sounds impressive, but I'll have to see it in action first.<p>Pharo is an incredibly productive environment. Fully inspectable everything (on the language level, but also on GUI level - you can inspect all kinds of widgets interactively) and the Debugger where you can define your logic as needed make for incredible programming experience. Plus, it's Smalltalk, which is a beautiful language in its own right.<p>With this release, it looks like Pharo may finally become more than just a toy. Looking forward to it!
I like what I see, but they do a poor job of explaining the use cases, which is a common issue for most technical projects. Is this for:<p>- learning?<p>- developing personal projects?<p>- developing business projects?<p>- can be deployed to desktop platforms? mobile ? web?<p>- Has GUI library support?<p>Without a clear break down of use cases, I am just lost in the cool technology without any way of determining if it fits my needs.<p>A good example of how to do this well is GameMaker Studio: <a href="https://www.yoyogames.com/gamemaker" rel="nofollow">https://www.yoyogames.com/gamemaker</a>
I was going to say that it sounds a little like that Smalltalk IDE Squeak, and then it dawned upon me that this is actually a Smalltalk dialect too. :D<p>I'm going to throw this in here:<p>"Squeak or Pharo for the beginning Smalltalker?"<p><a href="https://stackoverflow.com/questions/8426981/squeak-or-pharo-for-the-beginning-smalltalker" rel="nofollow">https://stackoverflow.com/questions/8426981/squeak-or-pharo-...</a><p>And a third option that is much leaner and maybe less overwhelming especially if you are interested in actually learning Smalltalk itself to begin with:<p><a href="https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev" rel="nofollow">https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev</a>
I lol'd when the quote, "Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback.", is accompanied with a relatively chaotic artwork of the development environment.<p>Anyways, the dedication of the team is really remarkable. It looks like a really useful learning/teaching tool for OOP. I'll try and hopefully beat my prejudice.
"Everything's an object" is object oriented programming done right and I can see why Ruby and other languages used those ideas from Smalltalk. I couldn't understand the fascination with the integrated environments though. It was my biggest stumbling block. Is there a pathway to use Pharo with my traditional tools?
> <i>IoT is now an important part of Pharo. Installing PharoThings (<a href="https://github.com/pharo-iot/PharoThings" rel="nofollow">https://github.com/pharo-iot/PharoThings</a>) provides an impressive amount of tools to develop applications in small devices.</i><p>On that GH repo[0] I see:<p>> <i>Raspberry driven by WiringPi library</i><p>> <i>Arduino driven by Firmata, soon</i><p>> <i>Beaglebone, soon</i><p>Has anyone played with this?<p>[0] <a href="https://github.com/pharo-iot/PharoThings" rel="nofollow">https://github.com/pharo-iot/PharoThings</a>
The Pharo website has zero mention of its relation to Smalltalk, although the Wiki article calls it a dialect.<p>So how close are the two in reality? Is the syntax from your standard Smalltalk-80 textbook largely portable/compatible to Pharo, or is Pharo merely "inspired" by Smalltalk?
Final steps have been taken to make it useful from small devices up to enterprise usage. Still the best working environment ever encountered. Congrats to this gem!
Every time I try a Smalltalk (++) implementation, the custom UI framework is what kills it for me. Not only are they completely non-native in look and feel, but they also lag behind on features - e.g. Pharo is apparently non-high-DPI aware on Windows.
Their website is down atm.<p><a href="https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70ChangeLogs.md" rel="nofollow">https://github.com/pharo-project/pharo-changelogs/blob/maste...</a>
The main issues that prevents me to have an interest in Pharo are the following two:
- There is no real multithreading support
- It's not easily embeddable<p>I believe that there are attempts to tackle these problems but what is the status?
For anyone interested in learning Pharo/Smalltalk, there is a pretty decent MOOC: <a href="https://mooc.pharo.org" rel="nofollow">https://mooc.pharo.org</a>
TLDR: Pharo needs mountains of high-quality documentation equal to Python's docs or Java's docs if it seriously hopes to attract server-side or desktop mindshare among developers.<p>Long Version:<p>In 1980, Smalltalk had some of the best documentation of any language out there. In 2019, it basically has none. By 2019 standards, Pharo 7 ships without any documentation at all. That's a game-stopper.<p>Pharo 7 looks really polished. It sounds like the design team put in tons of hard work over the past year and half to produce this release. Moreover, since it's smalltalk, Pharo is also probably very powerful for both web and desktop development. BUT NONE OF THAT MATTERS IF DEVELOPERS CAN'T FIGURE OUT HOW TO USE IT!!!<p>(pardon the all caps, but I want to emphasize my point)<p>Here is my message for the development team: if you really want developers to start building stuff with Pharo, then you absolutely must (1) write detailed, soup-to-nuts, high quality docs for web design and (2) write another set of detailed, soup-to-nuts, high quality docs for desktop GUI programming.<p>The Pharo book doesn't cut it--not even close. It's not a very good book. The Pharo MOOC doesn't cut it--again, not even close. Who wants to learn that way? ProfStef is just a fancy hello world; it's really not a tutorial and it doesn't lead anywhere.<p>I realize that what I'm saying comes across as pretty strong medicine, but please understand, that's because I actually think Pharo looks amazing and would like to use it.<p>In my opinion, you should stop development on Pharo and document what you've built instead. Write docs for a year. Today's release announcement states that the Pharo 7 team closed 2142 issues. Brag in 2020 about the fact that you wrote 2142 pages of documentation and tutorials over the past year. Make your documentation coverage as thorough as your testing coverage.<p>Imagine what might happen if Smalltalk 2020 was as thoroughly documented as Smalltalk 80.
Is it possible to integrate Pharo with KDE so the windows won't be trapped inside the Pharo window (I don't really like MDI) and would have system-set decorations (I love using "keep above", "keep below" and "shade" buttons I've added via the window manager configuration)?
Is there any progress on porting to mobile system.[This](<a href="https://medium.com/@richardeng/mobile-smalltalk-c6f0cc712909)mobile" rel="nofollow">https://medium.com/@richardeng/mobile-smalltalk-c6f0cc712909...</a> SmallTalk seems to be the furthest endeavor.
old article about calypso class browser <a href="https://dionisiydk.blogspot.com/2016/12/calypso-new-system-browser-for-pharo.html" rel="nofollow">https://dionisiydk.blogspot.com/2016/12/calypso-new-system-b...</a>
A few years back Pharo's predecessor/sibling Squeak was garnering some interest due to its "Seaside" web framework, which used continuations and so made some interactions easier to program.<p>But after the rise of JavaScript, this became a lot less important.
Looks interesting. Getting a weird error when installing it via Homebrew, though: "“Pharo6.1-64” is damaged and can’t be opened. You should move it to the Trash."<p>Anyone experience anything similar?
I have Pharo installed on my laptop to try some stuff out with it, but I haven't gotten around to it yet. Maybe this is as good a time as any to start it up again.
After reading this line:<p>> Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback.<p>and seeing the initial screenshot on the announcement, I thought that this was a joke post. How you can call this "focused on simplicity" while showing that horrific hodge podge of a screen shot is beyond me.