Nested dependencies are an important factor as well. The majority of security issues (and hacks), as well as a large number of issues, originate not in the library you chose to consume — but in libraries they chose to.
Interesting read and a very interesting choice. It sounds like in certain circumstances “sibling services” may make sense. Can’t help but wonder how this frail decouple will stand in the test of time. ⏳
Great piece, thank you. I think everyone can find something useful here.
My company has a large development team and I find it important to bring some browser performance statistics to their existing dashboards (tech graphs, business statistics). Adding those custom reports promotes awareness and helps prevent performance degregation. Well worth the effort
When you’re replacing one
for loop for two iterator functions,
map , you’ve sacrificed performance for style. In performance centric programs I’d think it’s a bad call. Here’s a benchmark of both of your examples: