On 11.02.2010 21:42, Stéphane Ducasse wrote:
pfff.... I should say that kent should have not broken his rule. Don't blog when you are mad. It gives a bad impression and not only about smalltalk
Now what is the solution. get stuck with a ANSI bad standard? get with vendors evolution that are not optimal?
what if we do not like VW Namespace ? what if we would like to have first class instance variables? Vendors like parceplace did not really ask the community about the changes they did.
Now Seaside is developed on pharo and run on nearly all the dialects so there is a path. It is not easy.
Because what we settled for is that every vendor has to rewrite a chunk of Seaside. Because we left out all the non basic stuff like files, sockets, os access, graphics, sound, logging, xml parsing, database access, crypto, .... Seaside itself is not portable, it's simply possible to only load the parts which we assume to be portable. So yeah, if you're writing a counter application that's probably portable. But as soon as you start to do Pier or Magritte you can write your own portability classes for everything that Seaside does not need. If you're doing a Pier addon like AudioScrobbler or TopFeeder you're almost guaranteed that it's not portable. Believe when I say I speak from experience and it's really frustrating. Cheers Philippe