It depends. Pharo 2.0 is UNSTABLE. It says it everywhere. If you want to do seriuous development you won't beusing Pharo 2.0, will you? ;)
I talked about that few days ago with Germán. The problem is not in using of unstable version. The problem is that it is very easy to stop to be in touch with Pharo now and within one year when the current unstable version will become stable the developers will face to very different system. That is one of the reason why Germán choose Cuis for his current projects. Developers want simple predictable system.
Absolutely wonderful. So what people wants just the same. Ok but this is not Pharo. And and and again again again and again who is concerned by RPackage vs PackageInfo, systemNotifier vs. announcement, better monticello, better canvas, better Zincâ¦. I find that a totally false argument.
I do not think that the way out from this is to slow down. On the contrary. We simply have to do this era of a lot of big changes as short as possible ;-)