Currently it does not solve the problem of the sh*tload of dependencies, though I'm filing an issue for now.
php-build currently solves mainly the problem of configuring PHP correctly, so the build is isolated to the prefix it's installed in (it also sets up PEAR or Pyrus correctly).
The mission of php-build is to reduce my workflow of testing new PHP versions to one command I can run. php-build also provides a opinionated default configuration, which you can build on and extend.
Without php-build I have to do this when I want to test, for example PHP 5.4.0RC1:
1. Find a tarball
2. Extract Tarball
3. Configure it
3a. If I already have a script to configure this version go to 4.
3b. Pick configure options (PHP has a sh*tload of them)
3c. See if it works
4. make && make install
5. install Pyrus
6. install XDebug
7. install PHPUnit
So with php-build (and php-build-plugin-phpunit):
1. php-build -i development 5.4.0rc1 ~/.phpenv/versions/5.4.0rc1
2. ?
3. Profit
First, a tablet doesn't let you just do those things.
I made the "80%" up, but the list should only capture what most of the people most of the time do with their computers.
If you want to do the one more thing, there will always be more software for that, also for your tablet.
My point is that Tablets are the new _personal_ computer and what we knew as PC before is now going to be the _workstation_.
I talked about simple office tasks like writing a letter, writing a CV, or a simple handout. These are all things that are at most one page, which can be done with a tablet without much pain.
The Point is, that I want my closures to have access to the context (the application) without messing with the arguments or "use".
The next thing is, that the Silex Framework binds route parameters as arguments to the closure.
Additionally the user could forget to declare the $app argument in the passed closure.
So this code throws up a "Parse error: syntax error, unexpected 'function' (T_FUNCTION)"