1,369 karma · joined December 12, 2012
Get in touch: hi at salem dot io
1. it is flexible enough to fit all of our weird edge cases.
2. it has a really solid community of people working on it.
3. it made adopting new features like TypeScript extremely simple for us.
I don't see us upgrading from 4 to 5 eagerly (at least until it's been production-proven), but I'm excited about this release, and I love all the hard work that's gone into it. Congrats to the team — it's no small feat.
Edit: formatting
Edit: I'd add that the book does a good job about explaining the sorts of motivations there were behind un-densifying cities (or keeping density from rising) in the first place.
[0]: https://en.wikipedia.org/wiki/The_Death_and_Life_of_Great_Am...
Plus, Venmo (and PayPal) has interest in being a trusted brand in financial transactions of other sorts, I'm sure. PayPal has a credit product now, for example. I would not be surprised if they have a rent-seeking lobbying interest in making federal bank transactions remain a worse experience than their own service.
[0]:https://www.marketplace.org/2018/02/20/what-are-apps-venmo-d...
I think in our case a lot of our decisions are based on two success criteria:
1. We want our developers to be able to use language features (like Promises, Maps, and Iterators) that make development easier.
2. We need to pick a solution that offers the best performance in the browser. We run an e-commerce marketplace; we pay for every additional byte we send over the wire in our conversion metrics, whether it's in the short term or the long term.
It's not really reasonable for us to only write JavaScript that works for the lowest-common-denominator of our traffic (we still support IE11!) but at the same time, we also can't drop support for them. So, we have to partition our traffic in order to allow modern browsers to skip the polyfills they don't need, while supporting the older browsers that need them. There really isn't a better way to do this than serer-side parsing of the user agent string. Identifying features in the browser means that we have to incur another round-trip, which delays the execution of any of our other JavaScript and hurts usability metrics like Time To Interactive[0]. I have to plug Polyfill.io[1] here; their service is open-source and works extremely well.
And as far as whether this is an anti-pattern or not, it's something that works really well for us. We've implemented both a general polyfill and a user-agent-specific polyfill solution, and there were in fact small performance benefits in the latter, with no cost to conversion.
Plus, whether user-agent parsing is an anti-pattern or not, it's the state of the world. As I've already mentioned above, we don't gain much by avoiding this anti-pattern, so what's our motivation to change our implementation? As a challenge, I'd encourage you (or anyone reading this) to try spoofing your browser's user agent to be IE11. You'd be surprised how little of the internet works, even on sites that claim to support IE11.
[0]:https://github.com/w3ctag/design-reviews/issues/467
Edit: added citation.
Edit: clarifying that I'm talking about my workplace, not a company I run.