I'm sorry, this doesn't wash. It's great that they've introduced new APIs, even better that upstream GTK etc is being tracked now. However, this shouldn't have come at the expense of the old APIs. When MS, Apple or even Debian/other Linux distros upgrade to new libraries, they keep old ones around as well so that everything doesn't break. I typically have wxGTK libraries of about three or four versions on my systems for different apps that haven't been brought up to current. I realize that there are extra constraints with this being an embedded platform. I also think it's acceptable to have this sort of breakage for brand-new platforms in brand-new categories. However, as the platform matures, as is surely the case with ITOS 2008, this sort of behaviour becomes less and less tolerable. I hope this is the last time that Nokia intentionally breaks compatibility. Otherwise, I fear they risk alienating 3rd party developers for the platform. Just look at all of the OSS apps that only work on specific versions of ITOS for examples of this already. Jpilot and Abiword to name two. What did this buy us? Lost apps and lost developers. Apple, Sun, Microsoft, Red Hat, Canonical, all of them keep old versions of libraries around to prevent just this sort of thing from happening. Sure, deprecate old APIs/libraries, but at least keep them around for a release or two. Can you imagine how popular Java would be if each new release of the JDK broke _ALL_ non-trivial apps compiled against the previous version?