The cost of abstractions. <3
Awesome to see @parceljs team really weighing in on the cost of features/integrations/etc.pic.twitter.com/u0wJmPnIFC
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Consious Tradeoff
However we do support before/after, etc now. So its getting _less unpredictable_
I guess I'm just saying all abstractions are not created equal. One of the big insights of React is that passing functions as props and calling them is better than firing an event into the ether and hoping someone is listening.
Among other benefits: - When you call a function wrong, you get errors right away that pause your debugger - Wrapping functions is easy to understand, and even higher order functions are easier to step through than evented patterns.
Truth! So what's the tradeoff them Katz?
I don't understand the question.
I'm saying if you take the model you are talking about (a more functional composing approach), what are the trade-offs to that system as it grows?
Ah! I think it just means that you should only "decouple through events" when you really need it. A lot of people perceive it to be an unvarnished good even when a parameter would do just fine.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.