I would not use Pixate again. It's a great idea, but the overhead is brutal on any kind of data driven list view. After filing numerous bug reports and using hacky workarounds, we finally switched back to full native... it was the source of 90%~ of our app's sluggishness.
We hear you on the list performance. There are significant performance improvements we've made in version 2.0, over the previous version. We’ve also identified more ways to make Pixate faster, especially for CollectionView and TableView, and will roll them out as soon as we can. Performance is our #1 priority, so expect it to continue to improve.
In addition to that, how you use Pixate and what CSS selectors and properties you use can have a big impact on performance, just like with CSS on the web. We’ll be making those kinds of issues clearer for developers through "best practices" posts, as we continue to build our product.
This is invaluable to hear, thank you! Was this with 1.x or 2.x (which is said to include "performance improvements throughout")? Anybody with 2.x vs. 1.x performance differences to share?
