<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Casey Ransberger wrote:
<blockquote
cite="mid:CACemAZfrgaLU-N260u8p+ZFF9k5Rqi02+Wb+Mdq6F5+aGFdfeg@mail.gmail.com"
type="cite">Inline.<br>
<br>
<div class="gmail_quote">On Wed, Sep 7, 2011 at 2:24 PM, Levente
Uzonyi <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:leves@elte.hu">leves@elte.hu</a>></span> wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Wed, 7 Sep 2011, Overcomer Man wrote:<br>
<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I suggest a new fork or possibly a new orientation for the next Squeak<br>
release:<br>
</blockquote>
<br>
</div>
I guess we have too many forks already (compared to the number of
active developers).</blockquote>
<div><br>
</div>
<div>+1 </div>
<div><br>
</div>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Adopt
Cuis as the core image and focus on killer applications to attract new<br>
Smalltalk users.<br>
</blockquote>
<br>
</div>
Cuis is nice, but lacks features that are important for those killer
apps (e.g. internationalization). Also throwing aways years of work
(3.8, 3.9, 4.1, 4.2 and 4.3) sounds like a bad idea. We should pick
good stuff from Cuis (and Pharo) instead.<br>
To make the image smaller we should do two things (in parallel):<br>
- craving (make packages unloadable, remove dependencies, split
packages)<br>
- building (use Spoon to rebuild the current image)<br>
</blockquote>
<div><br>
</div>
<div>Yes, we should merge the best things from Squeak into Cuis, We
should merge the best things from Cuis into Squeak. Until all are one.</div>
<div><br>
</div>
<div>WRT internationalization, though, I do feel that most end users
don't need 20 languages they don't speak in the core system. Most users
will want to use the system in a primary language. This stuff should
all be available as rock-solid external packages. Not saying it isn't
important, not saying that at all. If we hope to rebase Etoys on
Squeak, internationalization is essential.</div>
<div> </div>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">To
make this happen we have to start with writing tests, which "document"<br>
the expected behavior of the system. So when we change it, we can be
sure that we didn't lose anything important.</blockquote>
<div><br>
</div>
<div>+1! </div>
<div><br>
</div>
<div>A living system needs a living specification, and the closest
thing I know how to do to a living specification is a great suite of
tests.</div>
<div><br>
</div>
<div>Let's start by merging the tests.</div>
<div><br>
</div>
</div>
</blockquote>
An interesting future scenario would be a shared test repository
between the various forks of Squeak, with their respective continuous
integration servers outputting results to a common database.
Differences in "good results " between forks should be catered for, but
would highlight differences in the "specification" of each fork, which
might help it to converge over time while allowing the implementations
to differ. <br>
</body>
</html>