On Apr 27, 2011, at 11:41 PM, Jon Hancock wrote: > Stef, > I'm with you!! Keep hacking away at Pharo and make it the cleanest, nicest > Smalltalk environment. Backwards compat talk this early in Pharo's life is > premature. Besides, one of Smalltalk's best features is discovery and > refactoring. This makes it much easier to migrate and rewrite when things > break. > > Thanks for all your work!! I'm only "playing" with pharo these days but keep > looking for U.S. clients where I can plug it in.
Excellent I cross my finger. Stef > ~Jon > > On 04/27/2011 01:42 PM, Stéphane Ducasse wrote: >> Mike and other >> >> How many engineers are payed to deliver freeBSD? >> How many active committers and packages responsible are actively commiting >> and taking >> responsibility for packages? >> >> We need also stability but right now not changing is just been dead. >> I think that lot of people do not read the code of pharo else they would see >> why we are >> changing. We do not change for the fun. THIS IS NOT FUN TO write boring code >> to fix ugly situation. We would prefer to write hyper cool sexy app and be >> fancy to >> impress girls but this is not like that. Network is bad, compiler is bad, >> file is ugly.... >> Once this will be fixed then we will not change for the sake of it. >> >> Now comparing Smalltalk to cobol is silly (sorry but it is). Right we are >> fighting >> with python, ruby, javascript (in fact we are not fighting since we do not >> even exist in the radar). >> If we want to get a chance, we should move way faster and be really >> aggressive to make sure >> that you can write hyper cool application. >> >> Now why would you need to upgrade all the time to new versions if your system >> is working. >> >> Metacello and versioning systems are your friends: maintain difference >> streams >> and versions if you want to share between different versions. >> >> Stef > >
