@dakami @maradydd @matthew_d_green you can do both so long as the API clearly separates what to use for new projects versus legacy interop
-
-
@bascule@maradydd@matthew_d_green Lies we tell ourselves. Make useful things for devs, then make them fast. -
@dakami@bascule@maradydd@matthew_d_green everything can be fast, but the API design should aid the decision-making process -
@bascule@maradydd@matthew_d_green devs can tell when you're cheating. Make the awesome useful API that gets adoption. -
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.