Everyone is mad at everyone, Redis is forked, Ghost is federating over ActivityPub, Llama 3 & more

Changelog News

Developer news with a shiny new website

Hello again šŸ‘‹

We put a fresh coat of paint on the olā€™ Changelog News website! The goal was to feature our content more prominently and add some social proof to help nudge potential subscribers in the right direction. Thanks to everyone who lent us your kind words! Howā€™d we do? Hit reply with your feedback & bug reportsā€¦

Ok, letā€™s get into the news.


šŸŽ§ Podcasts? We got podcasts

šŸŽ™ļø Thomas Paul Mann on leading & building Raycast changelog.fm/587
šŸ’š Changelog News extended: Rug pull, not cool! changelog.com/friends/40
šŸš€ Paul Frazee on Bluesky apps shipit.show/100
šŸŖ© K.O.O makes the case for the boring JS stack jsparty.fm/319
šŸ¤– Udio & the age of multi-modal AI practicalai.fm/265
ā° Local cert management for mere mortals gotime.fm/312

āš ļø The threat to open source comes from within

Forrest Brazeal wrote this not-thought-leadership piece before OpenTofu published its response to Hashicorpā€™s lawyers, but the general sentiment still stands.

First, he lays out why he doesnā€™t believe external threats like the XZ backdoor are existential for the OSS community. Then, he turns inward with the horror movie classic twist: ā€œThe phone call is originating from inside the house!ā€ šŸ˜±

External threats, as the XZ thing demonstrates, seem to have a galvanizing effect on the broader open-source community. OSS just gets stronger under stresses like that.

The thing Iā€™m most worried about now is the opposite: a chilling effect. And itā€™s been creeping up on OSS like a glacier for over a decade.

After a quick history lesson (Current situation: ā€œ Everyone is mad at everyoneā€) and Forrestā€™s viewpoint of the OpenTofu / Hashicorp legal drama, he concludes with this somber note:

Here is where, if I were a thought leader, I would make some grand-sounding call for companies to ā€œdo betterā€, or for OSS foundations to ā€œrevisit their governance structuresā€, or something. But this is an impasse that canā€™t be solved with platitudes. Cloud companies, fundamentally, see open-source as something to exploit; OSS software companies see it as incompatible with a sustainable business model. Contributors who donā€™t work for either side are getting trampled on. And eventually, as the ecosystem fractures, everybody loses. The whole situation is just sad.

In the end, the fragile balance of open sourceā€”that unlikely blend of personalities and incentives that has driven techā€™s innovation engine throughout the 21st centuryā€”wonā€™t be upset by the odd state actor, or by malicious spam, or whatever scary new thing The Register is up in arms about tomorrow. It can only be disrupted when the community comes to believe maintaining that balance is more trouble than itā€™s worth. Thatā€™s the threat we should all be concerned about.

šŸ“ Redis is forked

Vicki Boykis:

I, as a cynical Eastern European, hate almost everything in software. But I love Redis with a loyalty that I reserve for close friends and family and the first true day of spring, because Redis is software made for me, the developer.

Thatā€™s high praise, which makes what she says next land with even more gravitas than it would in isolation:

The old Redis was for developers. The new Redis is for enterprise sales, and for generative AI. Itā€™s true that itā€™s not yet entirely clear what all of this means for the future of Redis the software. Some say the licensing changes wonā€™t impact much if youā€™re not a large-scale Redis reseller. Because itā€™s true that the license changes were all legal and all parties acted in accordance with both whatā€™s acceptable and what the market dictates to sustain the software. And yet at the same time, projects that depend on Redis are withholding updates or migrating.

But the problem is not only that the license changed suddenly, without warning, itā€™s the messaging behind the change, and the message is, even though there is extremely active community development, Redis is no longer in and of the community. We are no longer being consulted.

If you heard Adam and I on Changelog & Friends over the weekend, you already know how I feel about this. But if you didnā€™t: Iā€™m with Vicky. Redis is no longer for us, and Iā€™m no longer for Redis. May a thousand ideas/forks rise out of its ashes.

šŸ“ž Less stress from ring to retro

Thanks to Firehydrant for sponsoring Changelog News šŸ’°

FireHydrant offers modern engineering teams less stress from ring to retro. Full end-to-end incident management, alerting, on-call, and of course, streamlining every aspect of your incident process.

From webhook, to alert trigger, to notifications, to incidents opened, to retro tasks, to mean-time-to-X analyticsā€¦everything is inside FireHydrant for modern engineering teams.

Assemble the team and work the problem without a single swivel of the chair. FireHydrant delivers end-to-end incident management and on-call alerting for the modern software teams.

Get started for free at firehydrant.com/signals

šŸ‘» Ghost is federating over ActivityPub

John Oā€™Nolan and the Ghost team:

In 2024, Ghost is adopting ActivityPub and connecting with other federated platforms across the web.

This means that, soon, Ghost publishers will be able to follow, like and interact with one another in the same way that you would normally do on a social network ā€” but on your own website.

The difference, of course, is that youā€™ll also be able to follow, like, and interact with users on Mastodon, Threads, Flipboard, Buttondown, WriteFreely, Tumblr, WordPress, PeerTube, Pixelfedā€¦ or any other platform that has adopted ActivityPub, too. You donā€™t need to limit yourself to following people who happen to use the same platform as you.

Instead of building this all behind closed doors, the Ghost team is inviting everyone to be part of their process. With each publishing platform that rolls out ActivityPub support, the promise of the Fediverse becomes less of an idea and more of a reality. Whoā€™s next?

šŸ¦™ Llama 3 now available for ā€œbusinesses of all sizesā€

On April 18th, Meta released the latest version of their open(ish) LLM with ā€œstate-of-the-art performance.ā€ The Verge rounds it up like this:

Meta claims both sizes of Llama 3 beat similarly sized models like Googleā€™s Gemma and Gemini, Mistral 7B, and Anthropicā€™s Claude 3 in certain benchmarking tests. In the MMLU benchmark, which typically measures general knowledge, Llama 3 8B performed significantly better than both Gemma 7B and Mistral 7B, while Llama 3 70B slightly edged Gemini Pro 1.5.

What followed was your typical X Bros posting ā€œN mind blowing demosā€ of what Llama 3 can accomplish (where N = the number a rival X Bro just posted + 1). Not interestingā€¦ But two things did stand out as interesting about this announcement:

  1. They didnā€™t compare Llama 3 to GPT-4 at all, so we can only assume it still comes up short
  2. They continue to call Llama ā€œopen sourceā€ even though the license retains the commercial requirement of your business not being too big (700 million MAU)

So I guess Llama 3 is open for businesses of all sizes, depending on how you define ā€œallā€ and ā€œsizesā€ā€¦

ā“ Questions to ask when I donā€™t want to work

Sometimes itā€™s easy, but other times (especially if you work for yourself) itā€™s necessary to put yourself to work. This post by nolen might help you get that done on days when youā€™d otherwise struggle. Hereā€™s some bullet points to start from, but the details matter too.

To summarize, when I donā€™t want to workā€¦

  • I donā€™t call myself lazy. I trust that I havenā€™t changed and look for what needs to.
  • I get excited about the end result and share what Iā€™m doing with others.
  • I consider whether my tools are getting in my way
  • I give myself the same grace Iā€™d give someone else, and consider taking a proper break

Last week I was struggling to work. I wasnā€™t excited about my current project. I took two days off and played a bunch of games and piano. I realized that I was excited to write this essay. And so I sat in a chair (not on the couch!) and wrote it.

šŸŽ‰ Zero downtime Rails upgrades are within reach

Thanks to Test Double for sponsoring Changelog News šŸ’°

Putting off key Rails version updates is a recipe for disaster, because later usually means never.

Our friends at Test Double (you may recall from episodes featuring co-founder, Justin Searls) share a body of knowledge theyā€™ve built up with over a decade of Rails upgrades in codebases like Gusto, GitHub, Zendesk & more.

Plus, their blog is chock-full of helpful tips, practical posts & a RailsConf talk that lays out a framework for an incremental approach to zero downtime Rails upgrades. Check it out!


šŸ—Æļø Quote of the week

ā€œI cannot remember the books Iā€™ve read any more than the meals I have eaten; even so, they have made me.ā€ ā€“ Ralph Waldo Emerson

Take that thought and apply it to software. Or just leave it alone and enjoy it for exactly what it is. (via Jim dash Nielsen)


šŸ‘“ Introducing Meta Horizon OS

Meta is ā€œopening upā€ the operating system that powers their Meta Quest devices so third-party hardware makers can build their own mixed reality devices on top. ASUS, Lenovo & the XBox team are already putting this tech to use, according to the announcement post.

Is this a move by Meta trying to make Horizon OS the Android to Appleā€™s visionOS? Hard to say this early in the game, but theyā€™ve sunk a LOT of money into this effortā€¦.

šŸ“ˆ Measuring personal growth

Chip Huyen writes yet another excellent thing:

My founder friends constantly think about growth. They think about how to measure their business growth and how to get to the next order of magnitude scale. If theyā€™re making $1M ARR today, they think about how to get to $10M ARR. If they have 1,000 users today, they think about how to get to 10,000 users.

This made me wonder if/how people are measuring personal growth. I donā€™t want to use metrics like net worth or the number of followers, because thatā€™s not what I live for. After talking with a lot of friends, I found three interesting metrics: rate of change, time to solve problems, and number of future options.

šŸ‘Ž I love programming but I hate the programming industry

Have you ever felt like a faulty cog in a machine when the machine itself is faulty? Thatā€™s what this #somber post is all about, in light of a career in the tech industry:

Essentially, the concept of critical thinking has been made anathema to engineering: as a programmer you are to focus solely on the how, rarely on the what, and certainly never on the why. For the rare code monkey that finds themselves able and willing to critique the system theyā€™re producing for the message is clear: leave that shit at the door. A code monkey is prohibited from even identifying the lack of autonomy and creativity inherent to the position - they can only strive to build more, never to build differently, or build different and better things.


šŸ”— More links for your clicking pleasure


Thatā€™s the news for now, but we have some great episodes coming up this week: Louis Pilfold, the creator of the Gleam, on Wednesday & Adam Jacob, from System Initiative, on Friday!

Have a great week, send our shiny new website to a friend who might dig it & Iā€™ll talk to you again real soon. šŸ’š

ā€“Jerod