The example I'm talking about is the first non-trivial example in the readme - 34 lines of believable code, not an individual function of the library.
The library is used about once every 3.5 lines, which feels less dense than most jQuery code I see, but that whole function runs 3 times slower than the plain MB-aware equivalent.
Some of the library functions might be implemented inefficiently but from a quick glance they're nearly all very thin wrappers.
Overhead from libraries like Symfony and ZF is quite acceptable since they offer much higher level features which you'd have to code yourself otherwise.
However making all your code (excluding I/O) run up to 3 times slower, just to add some syntactic sugar, is insane.
The library is used about once every 3.5 lines, which feels less dense than most jQuery code I see, but that whole function runs 3 times slower than the plain MB-aware equivalent.
Some of the library functions might be implemented inefficiently but from a quick glance they're nearly all very thin wrappers.
Overhead from libraries like Symfony and ZF is quite acceptable since they offer much higher level features which you'd have to code yourself otherwise.
However making all your code (excluding I/O) run up to 3 times slower, just to add some syntactic sugar, is insane.