One of the hardest things to explain about Ember is that it's a framework *only* used for apps running entirely on the client side 1/
-
-
I would love some help finding a tweet-sized way to explain it. 3/3
-
-
@attilagyorffy@emberjs the main issue is that people compare non-"SPA" usage of React/Angular/Knockout/etc to Ember, which skews. -
@attilagyorffy@emberjs Other frameworks allow you to build fully client-side apps, but that isn't their dominant use-case. -
@attilagyorffy@emberjs this makes the ecosystem value lower than you might expect if you are in it. -
@wycats That's the downside of inventions (even if they are incremental in some ways). The router component gives a whole new twist to it.
End of conversation
New conversation -
-
-
@wycats Hm - is SPA really confusing? "Ember is only for SPAs; it won't play well with PHP ASP[.]NET, etc." -
@AdamRackis "SPA" is just an outdated term that sounds trollish to a lot of people. It's actually pretty accurate. -
@wycats SPA sounds trollish to some people?!?! -_- -
@AdamRackis one big issue with "SPA" is that Ember apps always have multiple pages, just not server-rendered, so it's confusing.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.