On Fri, Apr 29, 2011 at 14:12, Colin Walters <walt...@verbum.org> wrote: > On Fri, Apr 29, 2011 at 3:00 AM, Johannes Schmid <j...@jsschmid.de> wrote: >> >> >> I think the "we define the platform" argument is really weak. Our whole >> platform is written in C and we definitly don't define that platform. >> You can include a lot of really old Unix API in C and nobody can prevent >> you doing it. > > Yes, but GLib is very prominent in the world for code written in > C...third party libraries are quite likely to already depend on it. > > Also, it's not just the API exposed, but the fact that we have control > over the implementation if we need it. For a different example, if we > wanted to go to town on memory usage optimizations and have a > pre-forking zygote process for gtk3+js apps, we could do that. But it > would be impossible with Python (at least, not without effectively > rewriting it, which would preclude access to all the libraries written > in C).
Not making an argument for this discussion, but can you explain why it would be more difficult with Python? I did some experiments on this and the issues seemed to be in libraries, not in Python itself. Regards, Tomeu > _______________________________________________ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list > _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list