Re: Pier-EmailSender and "Contact Us"

5 May 2009

...

 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  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. 
Yes you are right. But we have pretty limited resources.

...

  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. 
So do not use pharo! Please don't!

Stef
...

 Keith
 _______________________________________________
 Magritte, Pier and Related Tools ...
 https://www.iam.unibe.ch/mailman/listinfo/smallwiki 

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Re: Pier-EmailSender and "Contact Us"