Pharo: Difference between revisions
mention squeak vm as a platform. the vm is not forked by the project |
|||
| Line 21: | Line 21: | ||
==Emergence and fork from Squeak== |
==Emergence and fork from Squeak== |
||
Unrest in the Squeak community led to a fork of the [[Squeak]] project into the Pharo project in 2008. The issues were mainly about |
Unrest in the Squeak community led to a fork of the [[Squeak]] project into the Pharo project in 2008. The issues were mainly about four proposed changes:{{Citation needed|date=November 2009}} |
||
# (Open development process) The development process for the Squeak main image was perceived as not open enough to all community members. |
# (Open development process) The development process for the Squeak main image was perceived as not open enough to all community members. |
||
# (Clear MIT licencing) The licence of Squeak was doubted to be an Open Source licence, and it was doubted whether the relicensing of Squeak to MIT violated the rights of contributors who had never agreed to its terms. |
# (Clear MIT licencing) The licence of Squeak was doubted to be an Open Source licence, and it was doubted whether the relicensing of Squeak to MIT violated the rights of contributors who had never agreed to its terms. |
||
| Line 34: | Line 34: | ||
While Squeak kept stable releases for years, many community members needed code with integrated bugfixes faster than that. Especially the [[Seaside (software)|Seaside]] community had a fast update cycle and needed the language to react faster to bug fixes. Therefore, prior to Pharo, an unofficial release of Squeak was regularly released by Damien Cassou with recent bugfixes integrated. In a sense, Pharo emerged as the canonization of this process. |
While Squeak kept stable releases for years, many community members needed code with integrated bugfixes faster than that. Especially the [[Seaside (software)|Seaside]] community had a fast update cycle and needed the language to react faster to bug fixes. Therefore, prior to Pharo, an unofficial release of Squeak was regularly released by Damien Cassou with recent bugfixes integrated. In a sense, Pharo emerged as the canonization of this process. |
||
In Pharo, much unessential code was removed. Many packages that are integrated into the Squeak base distribution are optional in Pharo. |
In Pharo, much unessential code was removed. Many packages that are integrated into the Squeak base distribution are optional in Pharo. |
||
==References== |
==References== |
||
Revision as of 06:13, 19 August 2010
 | The topic of this article may not meet Wikipedia's general notability guideline. (July 2009) |
 |
 | |
| Stable release | 1.1
/ 26 July 2010 |
|---|---|
| Repository | |
| Platform | Squeak virtual machine |
| License | MIT license |
| Website | http://www.pharo-project.org/ |
Pharo is a fork of Squeak, an implementation of the object-oriented, dynamically typed, reflective programming language Smalltalk. Appearing in 2008, Pharo focuses on removing unessential code from Squeak and serves as the reference implementation of Seaside, a web application framework for developing web applications in Smalltalk.[1]
Squeak before version 4.0 shipped under the Squeak license, which was not an approved OSI open source licence,[2] Pharo has a policy that enforces contributors to agree to publishing their code under the MIT Licence.
Many packages that are integrated into the Squeak base distribution are optional in Pharo. Unlike Squeak, Pharo ships with TrueType fonts bundled already.
Emergence and fork from Squeak
Unrest in the Squeak community led to a fork of the Squeak project into the Pharo project in 2008. The issues were mainly about four proposed changes:[citation needed]
- (Open development process) The development process for the Squeak main image was perceived as not open enough to all community members.
- (Clear MIT licencing) The licence of Squeak was doubted to be an Open Source licence, and it was doubted whether the relicensing of Squeak to MIT violated the rights of contributors who had never agreed to its terms.
- (Frequent updates) The release process of Squeak was perceived as too infrequent.
- (Slim stable core image) The main release of Squeak offered a wide code range of vastly varying quality, while some community members preferred to have a stable and slim platform which can then be extended.
In detail: Squeak Smalltalk was used with two different directions, as an implementation of EToys, which allows teaching children both programming and other subjects using computer programming (graphically), and as an environment for general Smalltalk development. While reusing the Squeak virtual machine, Pharo focuses on the latter.
Pharo is now organized as a benevolent dictatorship of the community members who previously felt that they did not have enough influence. However, committing into the repository is open to everyone, including non-community members. Pharo from its beginning had a policy that enforces every contributor to agree to publishing under the MIT Licence. Squeak completed the switch to MIT only in 2010.[3]
While Squeak kept stable releases for years, many community members needed code with integrated bugfixes faster than that. Especially the Seaside community had a fast update cycle and needed the language to react faster to bug fixes. Therefore, prior to Pharo, an unofficial release of Squeak was regularly released by Damien Cassou with recent bugfixes integrated. In a sense, Pharo emerged as the canonization of this process.
In Pharo, much unessential code was removed. Many packages that are integrated into the Squeak base distribution are optional in Pharo.