4 May
2009
4 May
'09
11:08 p.m.
John M McIntosh wrote:
On 4-May-09, at 6:10 AM, Keith Hodges wrote:
Thats not my point my point is that they broke the
code.
The way forward is to engineer a solution, not just hack something in
that breaks what everyone has already.
One could propose a new loadable Author package that handles everything
and publish that for everyone that cares to use it, rather than forcing
code to break and all manner of nightmares managing two streams per package.
I don't use pharo myself. Goodness knows why
they break things as simple
as author initials.
Keith
Er because of the re-licensing of the squeak code base and the
discovery that using JUST
initials made the chore very difficult to determine who wrote the
code. So they enforce names now since Pharo has a more business target and the first
question those
folks ask, what's the license
and code ownership like?
I use Squeak for Business, and I will continue to do so.
The whole
approach behind pharo is flawed because it is dedicated to making more
work for me the coder of stuff that is for all. This is one instance
where I feel entirely justified in saying I told you so.
Keith