TBH, when I started the project, I choose Angular because I want to learn and use it. Now that I have been using it for a while, I can justify why I want to switch to Angular from Backbone. Backbone is small and only provide a "structure" to JS App. You need a lot boilerplate code. While Angular is "full-stack" and eliminate almost all boilerplate.

Per my experience, CakePHP is probably one of the slowest PHP frameworks. It has a large overhead and lots of legacy code that slows down the whole system. Generally, frameworks targeted at PHP 5.3+ are faster. PHP 5.4 has further performance boost in production and PHP 5.5 has Zend Optimizer built-in, which suppose to further speed up but I have never try that in production.

We have Zend in mind as the next PHP framework we'd like to include in the tests.

use either symfony 2 or silex. There is really 0 reason to use Zend Framework II.

Well, this is more of an example of the syntax. The lambda body might be quite complex.

Right. But I have seen actual code do this plenty of times and there was no explanation in the article so I naturally assumed it was just like those cases where basics of functions are not understood.

You are right. I should. This is definitely not a good example of showing "Everything is an expression" is CoffeeScript.

Sorry, that's my bad, it should be { silent: true }. I translate myself and mix CoffeeScript into this. I guess that's a proof of the fact that I cannot live without CoffeeScript. I have corrected in the post.

Even though CoffeeScript handles this consistently, the difference is subtle and can be overwhelming for beginners.

But the language support is not as good as Java and C#, which are static typed and IDE can make use of static analysis.

Agreed. They look cool, but they are usability disaster.

It really depends on who your intended user is. If the slides are intended to form a presentation (quite likely), then the user is often the person making the slides in the first place. In such cases they're not a usability disaster at all. Rather, they're really helpful (being able to switch between different sections, or miss sections that your audience already knows about easily is really useful).

On the other hand, if the slides are intended for reading, then yes, they may be a usability disaster. But then, slides aren't going to be the best format for reading anyway.

Exactly. Thanks bro.

What's the difference between this and Yeoman ? (http://yeoman.io/)

Haha was very prepared for this question. The main differences for me are that roots doesn't rely on ruby, it's built for advanced devs (starts with jade, stylus, and coffeescript), it uses roots-css rather than compass, and the project structure is a bit lighter and cleaner.

I tried yeoman and played with it for a while when it came out, but for me it feels vastly different to actually use. The concepts are definitely similar though. Great question!

I thought Akismet was the first to adopt such design: http://akismet.com/