Sounds a bit like crying to me. You built something using a framework and it didn't workout, "so what", rebuild it again. What's next, another blog post about

Sounds a bit like crying to me. You built something using a framework and it didn't workout, "so what", rebuild it again. What's next, another blog post about why Rails wasn't right either because of scaling issues? There is no write once and live forever model. Build what you need today, learn, and if you have to rewrite it 10 times then do it. Frameworks save people time. Not every framework is perfect or maybe 90% of the functionality is never used, but alot of good stuff that solves problems. Maybe the lack of research on your part before you chose something like ember is the real root cause, or maybe the lack of building a proof of concept to determine if ember was the right choice before yapping about your own failure with a framework that you really don't know.