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
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.
So functions and parameters: - create coupling between components - but make it easier to see mistakes While events: - reduce coupling between components - but make it harder to see mistakes
The choice of which to use is based on how much you really need decoupling (and therefore are willing to pay for it with more opaque error cases)
It doesn't make sense for a React or Ember component to use events as much for communicating between components, because most of the time both sides share a contract and failing to pass something is a mistake.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.