Pharo
| This article may not meet the general notability guideline. Please help to establish notability by adding reliable, secondary sources about the topic. If notability cannot be established, the article is likely to be merged, redirected, or deleted. (July 2009) |
| This article needs references that appear in reliable third-party publications. Primary sources or sources affiliated with the subject are generally not sufficient for a Wikipedia article. Please add more appropriate citations from reliable sources. (July 2009) |
| File:Pharo.png | |
| Paradigm | object-oriented |
|---|---|
| Appeared in | 2008 |
| Stable release | 09.11.4 (20 October 2009) |
| Typing discipline | dynamic, strong |
| Major implementations | Pharo |
| Influenced by | Squeak |
| 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]
While Squeak is shipped under the Squeak licence, which is 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
One of the principal architects of the Squeak community, Alan Kay, is chiefly concerned in creating a platform that teaches children computing. Therefore, code that primarily serves the education of children is included in the standard Squeak distribution. Also, the standard Squeak distribution tries to provide a stable platform, and thus, the standard image for download is updated only seldomly.
On the other hand, the Squeak platform was used for web development, chiefly using Seaside, where the educational code was not necessary, but did consume memory on servers. Also, the large code base was seen as a security issue. Thus, Pharo emerged in 2008 as a fork that focuses on progress, a slim core image, and frequent updates.
References
External links
If you like SEOmastering Site, you can support it by - BTC: bc1qppjcl3c2cyjazy6lepmrv3fh6ke9mxs7zpfky0 , TRC20 and more...
- Pages with broken file links
- Articles with topics of unclear notability from July 2009
- Articles with invalid date parameter in template
- All articles with topics of unclear notability
- Articles lacking reliable references from July 2009
- All articles lacking reliable references
- Class-based programming languages
- Dynamically-typed programming languages
- Smalltalk programming language family
