2) PHP5.3, well, so be it. The people stuck in the past are usually not the ones willing to take the plunge into such solution anyway. They can join us when they are ready.
3) Not yet, but we do have some plans for that.
4) You shouldn't commit your vendor dir, you should commit the composer.lock file, which allows anyone to re-install exactly the same version of the dependencies anywhere. And yes this is similar to Bundler as far as I understand it.
Do you PEAR-install PEAR packages? It's important for when there are executables. We wrote another project called comice to make it easy to create PEAR sandboxes and work with them: https://github.com/ardell/comice
2) We will move to 5.3 ourselves soon, I am just telling you the reality. PHP 5.3 broke some BC stuff, making it risky to migrate. I think that's slowed adoption a lot.
3) Not a huge problem that it doesn't install executables, so long as you support legacy PEAR installs with executables (see #1).
2) PHP5.3, well, so be it. The people stuck in the past are usually not the ones willing to take the plunge into such solution anyway. They can join us when they are ready.
3) Not yet, but we do have some plans for that.
4) You shouldn't commit your vendor dir, you should commit the composer.lock file, which allows anyone to re-install exactly the same version of the dependencies anywhere. And yes this is similar to Bundler as far as I understand it.
5) We also have plans for that, see https://github.com/composer/composer/issues/57 - but this depends on other features that we need to finish first.