Welcome to #115.
It’s time to find out what happens when OSS frameworks stop being polite, and start getting real.
(If anyone has a connection who works for The CW, we’d love an intro.)
Episode 1: Trouble in paradise?
It was May. All the JS frameworks had just moved into the mansion for the summer and were busy sipping (virgin) champagne, counting their VC dollars, and promising each other that they were “here for the right reasons.”
But we got our first signs of tension when Next.js got on-stage at Reactathon and announced that they would be
Remix clearly wasn’t too happy with the decision, but with Ember (and its router) having been in the house just a season before, they shrugged it off and said the right things about how we’re all helping to push the web forward. Peace in the house was restored… for now.
Episode 2: Stop copying me (for real this time).
Remix was considerably less understanding when they discovered that Solid.js had copy-pasted sections of the Remix docs into their own docs. The Remix team tweeted a lot, then deleted most of those tweets, then tweeted some more about how it’s OK to delete tweets.
The Solid team removed those sections from their docs and apologized, explaining that they were only “temporarily using the copy for prototyping their new docs infrastructure” without intending to ever publish the content as their own.
Eventually, everything calmed down once everyone remembered that developers don’t actually read documentation anyway.
Episode 3: Some yelling.
They actually made some good points, but no one really listened because they wouldn’t stop yelling.
Episode 4: The finale no one saw coming.
Bun announced they had raised $7 million, and were hiring engineers. The controversy? In a now deleted Tweet, they described the job as “a grind, especially for the first 9 months or so.”
Some developers appreciated the candor and upfront disclosure of expectations. Others were filled with the righteous anger of Tyra Banks because “a grind” could lead to a toxic work environment. We even got some speculation that Bun was appropriating pregnancy culture.
Bottom Line: I’ve been told that correlation doesn’t equal causation, but has anyone else noticed that the drama seems to have increased as more and more VC dollars have flooded into OSS?
Laughing about building notifications so we don’t cry [sponsored]
Courier gave my team so much time for activities
Newton’s 3rd law of motion clearly states that, “building app notifications always takes 5x longer than you think.”
And that might be understating it now that we have so many different platforms to worry about (email, SMS, web and mobile push, Slack, and tons more).
That’s what makes Courier so amazing. They give you complete notification infrastructure with one API that you can set up in an afternoon.
That API integrates with over 50 notification channels, and it handles everything — templating, routing, automations, even logging and analytics. It’s your PM’s *wildest* dream come true.
Courier is used by Fortune 500 companies and startups like Lattice and LaunchDarkly to save an average of 480 engineering hours a year. That’s a lot more time for
The best part? Courier lets you send your first 10,000 notifications of every month for free (no credit card required).
Close.com is looking for 3 experienced individuals that have a solid understanding of React and want to help design, implement and launch major user-facing features. Close is a 100% globally distributed team of ~55 high-performing, happy people that are dedicated to building a product our customers love.
Spot the Bug — Sponsored by Retool
Retool’s app-building framework and 100+ pre-built UI components can help you build any interface 10x faster (not exaggerating).
Spot the Bug — Sponsored by Retool
When we call