Am 24.10.2013 um 10:47 schrieb Philippe Marschall <philippe.marschall@netcetera.ch>:
On 24.10.13 08:05, Marcus Denker wrote:
On 23 Oct 2013, at 23:07, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Hi,
just as info: looks like already fixed Pharo issue #11876 makes problem for Seaside in 3.0:
http://lists.squeakfoundation.org/pipermail/seaside-dev/2013-October/005509.... http://lists.squeakfoundation.org/pipermail/seaside-dev/2013-October/005540....
It would be a bit sad that Seaside does not work in Pharo3.0 I imagine that Philippe is tired.
I would revert the change and add a rule that check that the argument of shouldnt:raise: should not be an Error
yes, people are not willing to change code all the timeâ¦
We are willing to change the code where there is a clear benefit. For example it's hard to argue that the new filesystem is an improvement over FileDirectory. We have a partically working Spec based UI for the servers. We would happily change the walkback to a new context API should it fix the bugs in the existing one. However this isn't the case with this change. To sole and only purpose of this change is to break code. This is what annoys me.
Personally I think the new filesystem is way better than the old one. Maybe not for seaside that has rather basic usage of it. This change I would consider game changer for pharo that need to happen from time to time. But with arbitrary changes we need to be very careful. There needs to be change because we cannot evolve without. But there is a border where changes are just for the sake of it (hard to justify). And that would turn pharo into _one of those_ open source projects where the only thing that is stable is the number of bugs. Norbert