@trek if you can learn the framework fast enough or bill for the prod hit while learning, then by all means... @ryanflorence @jergason
-
-
Replying to @joefiorini
@trek otherwise you may be better served by growing your own from libraries you can understand@ryanflorence@jergason2 replies 0 retweets 0 likes -
Replying to @joefiorini
@joefiorini@ryanflorence@jergason one man’s “own, libraries you can understand” is her teammate’s “inscrutable, undocumented framework.”2 replies 0 retweets 1 like -
Replying to @trek
@trek true dat, but it's hard to justify high learning curve when it's technically avoidable@ryanflorence@jergason1 reply 0 retweets 0 likes -
Replying to @joefiorini
@joefiorini@ryanflorence@jergason every time you see a broken back button you realize how much is not technically avoidable.2 replies 0 retweets 0 likes -
Replying to @joefiorini
@joefiorini you’re dismissing the learning curve of server rendered. It’s actually quite high, but most of us have already paid it.1 reply 0 retweets 0 likes -
Replying to @joefiorini
@joefiorini having paid the cost of both server rendered and client rendered, I find client rendered easier to work with.1 reply 0 retweets 0 likes
@joefiorini @trek personally I've found that convincing doesn't work, but waiting does. The best you can do is provide accurate warnings.
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.