for the vision behind pharo
imagine all the implications behind
• Better for the better
• Beauty to learn from
• Not backward compatible
• Clean, lean and fast
We want a system in which
- we can plug different UI frameworks
- clean network, clean file system, clean fonts, clean events, clean
compiler...
- that we could bootstrap: this is one of the goal also
- with robust software engineering practices (packages with
documentation, tests, smalllint rules attached).
Stef
On Oct 21, 2008, at 8:47 AM, Marcus Denker wrote:
On 20.10.2008, at 23:44, Antony Blakey wrote:
And there must be some context behind wanting to remove eToys/
BookMorph. Is it obsolete/unused? Is it used only by a class of
user that you explicitly don't wish to target?
eToys is, implementation wise, not written very cleanly. The
implementors of etoys always knew 100% that "this hack is the last,
then we rewrite everything". If you
do that for 10 years, hmm, it shows in code quality.
EToys, the one on the OLPC, is based on 3.8 plus *many* changes.
Etoys will never be based on 3.9 or 3.10. Thus the etoys in 3.10 (or
pharo) would be a fork indpependend
of the main eToy branch. Nobody would be interested in maintaining
that.
But seriously, look at the code. It's a nice example for many
things. For example: the prototype will be the product. Or: Never
plan to redo everything. You will not.
It kind of validates the idea that *evolution* is the most important
property of software, and if we want to make progress, supporting
evolution is *the* thing to do.
The next revolution in software will be a system that supports
evolution.
Etoys + the support are maybe (conservative estimate) 100.000 of
280.000 lines of code in Pharo. Just imagine how much less
maintance, less bugs and in general
cleaner architecture we will have.
Marcus
--
Marcus Denker -- [EMAIL PROTECTED]
http://www.iam.unibe.ch/~denker
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
