I noticed two trivial and failsafe ways of optimizing Formtastic, and there are plenty of places in the current code where this applies right now:
Formtastic doing a lot of String-manipulation so... Just putting this as a note on the wall - haven't done any benchmarks on Formtastic yet but might do soon for the fun of it. 8) 1.0?
We should definitely get this in for 1.0 -- optimizations and code clean-up are top of my list for the 0.9–1.0 gap.
Another possible optimization:
Here are some recent benchmarks showing tr() is ~2 times faster. Peep the other benchmarks, might be useful as well.
Actually when looking more into these, in some cases 10 times faster (!) =o
Sure, PDI :)
Quite obvious changes, and belongs to 1.0 for sure.
Using interned strings whenever possible and where it makes sense (String => Symbol), and concat (<<) instead of appending (+). Closed by e1a4a41.
Using interned strings whenever possible and where it makes sense (St…
…ring => Symbol), and concat (<<) instead of appending (+). Closes #45.