Hi, Seeing this "language war" on -dev I think I should say again that the component model should make us free from language restrictions. There is no sense in saying "we should use language XXX for portage-ng" as the goal should be that each component can be implemented in the best fitting language. So it should be possible to have the dependency resolver in prolog, the ebuild parser in perl, the frontend in python, the storage backend in C and so on. Instead of arguing about the "best" language for implementation we should discuss about the language for the _interface_ for the component interaction. Once we have decided on that we can start creating the global architecture that describes which components interact with each other, which components are mandatory or optional and so on. Later in that process we can specify the first function signatures and start implementing the individual components. Then and not earlier we have to choose the implementation language. I hope we can stop the "let's use XXX" discussion now.
Marius -- Public Key at http://www.genone.de/info/gpg-key.pub In the beginning, there was nothing. And God said, 'Let there be Light.' And there was still nothing, but you could see a bit better.
pgp00000.pgp
Description: PGP signature
