I hope you’re all enjoying the Olympics as much as the Australian swim coach. This week we’ve got a big Yarn update, hot takes about Safari, and Mark Dalgleish helping us name our company pug. Welcome to #59.
Did someone say there’s a major Yarn upgrade?
Yarn 3 wants you to *actually* upgrade this time
Yarn released v3 last week with some cool new features, but a much shorter list of breaking changes than the Yarn 2 release (thankfully).
How did we get here? Yarn is an open-source package manager like npm that was created in 2016 to address npm’s performance and security issues. Since then, npm has improved its performance and security quite a bit and copied some key Yarn features (👋 Workspaces), so they’re not actually quite as different as they used to be.
Many developers struggled to upgrade to Yarn 2 back in January 2020 when they basically rewrote it from scratch, and one of its original creators even struggled to not flame the entire Yarn project on Twitter.
Anyway, here’s what’s new in Yarn 3:
Bottom Line: If you used to be a Yarn fan, but got turned off by the v2 migration , it may be worth revisiting it now.
Kendo UI delivers everything you need to build modern, beautiful, responsive apps!!! [sponsored]
These Kendo UI grids just make life easier
Building a data grid is one of the things that sounds pretty easy and straightforward, but always has a bunch of hidden gotchas waiting to sabotage your project (and your sanity).
And most data grid libraries out there are kind of like that old used car you saved up to buy in high school — it might technically work (some of the time), but it’s almost not worth the hassle. Oh, and it’s dangerous.
👉 Check out Kendo UI’s free trial, and see what grid nirvana feels like.
Everyone knows you’re the… good guy
Is Safari killing the web?
Tim Perry thinks so. And he laid out a pretty compelling case last week in a well-researched article, which argues that Safari isn’t protecting the web from Chrome (as some have claimed), but slowly killing it. The full article is worth reading, but we wanted to highlight a few points and give our take.
Three ways Safari is killing the web:
Why is this happening?
How could the most valuable company in the world (with literally 50x the number of employees as Mozilla) be overseeing a browser that’s so consistently under performing? As usual, Charlie Munger and Wu-Tang have teamed up to give us the answer: “Incentives rule everything around me.”
Turns out, Apple has a lot more to gain from a “walled garden” of native apps, than they do from a free-and-open internet (30% on in-app purchases, to be exact). That’s not to say this is an explicit strategy, or that the very talented developers on the Safari/WebKit team are to blame, but it seems clear that Apple’s not marshalling many of it’s near-limitless resources towards the browser.
Whatever the reasons, if Safari doesn’t get its act together soon, Chrome will become even more popular/dominant than it already is — which would ultimately give it full power to shape the entire web as it sees fit. And no one wants that.
2x Sr. Frontend Engineers - React | 100% Remote
Close.com is looking for two experienced individuals that have a solid understanding of React and want to help design, implement and launch major user-facing features. They are a 100% globally distributed team of ~45 high-performing, happy people that are dedicated to building a product our customers love.