When comparing Qt / C++ vs Pharo, the Slant community recommends Qt / C++ for most people. In the question“What are the best languages to write a desktop Linux application in?” Qt / C++ is ranked 3rd while Pharo is ranked 10th. The most important reason people chose Qt / C++ is:
Professional, thorough documentation with examples, available either in a web browser or in the stand-alone desktop client called assistant.
Specs
Ranked in these QuestionsQuestion Ranking
Pros

Pro Good documentation
Professional, thorough documentation with examples, available either in a web browser or in the stand-alone desktop client called assistant.

Pro Portable
Linux, BSD, Android, iOS, Windows, Mac, Blackberry ... Qt has 'em all.

Pro Global community
The community behind Qt is both massive and approachable. Digia (also owners) are joined by the likes of Intel, KDAB, ICS, Canonical and numerous others in sponsoring development, while communities such as KDE also contribute significantly. Forums are active, mailing lists are open, irc channels chatting, git repositories well managed. Answers to questions are usually minutes away.

Pro QML
QML is "HTML5 done right": a declarative language that integrates beautifully with C++ code when necessary and exposes the power of the GPU ... simply the best way to create a modern GUI in terms of effort and results.
Pro LGPL license
Pro Open Source
Qt is licensed under a OSS license through a dual-license policy.
Pro Object-Oriented
In Pharo everything is an object. Compiler - object, network - object, method - also an object. And objects communicate with messages. No operators, no control-flow statements. Just objects and messages. Few things to learn, but you can learn OOP well.
Pro Easily learnt
There is good, free documentation including several books written by experts with extensive examples. There is an online MOOC. There are many tutorial videos. Supportive conferences and community. Even a professional support option if desired.
Pro Live updates
The nature of Pharo being a "live" environment allows you to perform live updates to your system without requiring to restart it. You can upgrade/modify classes while serving requests at the same time.
Pro Highly productive
Pro Seaside
The framework for developing sophisticated web applications in Smalltalk is developed in Pharo. Seaside lets you build highly interactive web applications quickly, reusably and maintainably.
Pro Remote debugging
Pro Beautiful coding patterns in your IDE
No need to search google for compact beautiful examples of how to do things, your live environment source is available and you can easily live search, see how it works and copy how the masters would do it (examples most languages still copy too).
Pro Glamorous toolkit & GTInspector
Most languages are still copying the Smalltalk tools of yesterday - GTInspector (written in Glamorous) takes live exploration of code/running objects to a new level. It's really slick, and better yet, you can easily write your own inspectors in 10 lines of code.
Pro Code can be run on rock solid GemStone environment
Pro 64 bit support as of Pharo 7
Use 32 bit or 64 bit versions of Pharo on Windows, Mac & Linux.
Pro Advanced code analysis tools
MOOSE environment provides extensive, easily leveraged and class leading tools for code analysis and improvement.
Pro Can run headless for production
Pro Really simple networking and REST with Zinc
Pro Graphics, graphing and visualisation framework - Roassal
Roassal and Mondrian provide fantastic and easily used frameworks for graphics, graphing and advanced visualisations (comparable to D3.js) but with much less code. Visualisations can be rendered into web friendly graphics (SVG, .png etc.) without additional work.
Cons
Con Not free/expensive
Free version is limited and prohibitive.
Con Small community
But they are very friendly and supportive. Best help comes through the mailing lists so not always easily googlable. There is also a Slack community where help is nearly instantaneous.
Con Odd language
Requires a different mindset. Much harder to apply what you know from popular or conventional languages . Switching over from or between other languages is more difficult.
Con Single threaded
Pharo's VM only ever uses one CPU core. If you want to write code that uses more than one CPU core, you need to jump through hoops such as running multiple VMs and synchronising your data.
