@mamund @SeanTAllen @pkeane we're trying to make Ember better in this regard. We'll see how it goes and how long it takes...
-
-
Replying to @steveklabnik
@steveklabnik@mamund@seantallen@pkeane If you "do it right", my guess is you'll ultimately end up reimplementing the browser1 reply 0 retweets 1 like -
Replying to @stilkov
@stilkov I don’t really even now where to start with this one, but wow.@steveklabnik1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@steveklabnik Of course I do not mean this literally. A follow-up in more than 140 characters might be useful.1 reply 0 retweets 0 likes -
Replying to @stilkov
@stilkov I’m just baffled by the “only the browser is *real REST* crowd”@steveklabnik1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@steveklabnik I don't consider myself part of that crowd, but yes, I've found the browser to be a very good REST client role model2 replies 0 retweets 0 likes -
Replying to @stilkov
@stilkov It sounds like you are philosophically opposed to other, more special-purpose REST clients. Not REST, opinion.@steveklabnik2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@steveklabnik Not in general, no; I just have a hard time justifying a specific one where I consider the generic one "good enough"1 reply 0 retweets 0 likes -
Replying to @stilkov
@stilkov the apps I build and help others build don’t have the luxury of “good enough”@steveklabnik1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@steveklabnik Fair point. For most scenarios I'm involved with, what you consider insufficient would be an amazing step forward3 replies 0 retweets 0 likes
@stilkov my position: Ember’s “REST” transport is imperfect, but @steveklabnik is helping make it better.
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.