[msimpson]

> I used quite an early beta of Ember to build BugMuncehr’s new feedback interface.

> I wanted to add a full REST API to BugMuncher, even though no-one had asked for it.

> I committed to using Ember before I knew enough about it.

> I didn’t keep it simple, I was stupid.

> Web apps often look complicated from the outsite, but underneath most of what they do is simply Create Read Update Delete, and you really don’t need a fancy JavaScript framework to do that.

So, to summarize, you failed at your first usage of a JavaScript framework due to your own bad decisions. Therefore, all the benefits SPA structure can offer the multitude of other projects is meaningless as, "...most of what they do is simply Create Read Update Delete." Honestly, you've just swapped the bandwagon effect for confirmation bias as you fell back to Rails.

[MattBearman]

I never said "all the benefits SPA structure can offer the multitude of other projects" were meaningless, in fact I specifically said there's a time and place for them. My point was most web apps, particularly an SaaS control panel, may be better served with a simple CRUD app

[msimpson]

> I never said "all the benefits SPA structure can offer the multitude of other projects" were meaningless, in fact I specifically said there's a time and place for them.

No, you said:

> There’s a time and a place for JavaScript frameworks, and whatever it is you’re building probably isn’t it.

Do tell us when a SPA structure is appropriate... Then, explain how that sentiment is any less "arrogant" than Ember.