Changelog News
Developer news worth your attention
Jerod here! đ
If you need an uplifting story that displays the human spirit triumphing over tyranny, look no further than your local Taco Bell drive-through.
My favorite fast food chain has been forced to rethink their AI ordering system after one heroic patron crashed it by ordering 18,000 waters. Now thatâs what I call High Quality H2O
Ok, letâs get into this weekâs news.
đ§ Python documentary companion pod
Our friends at Cult.Repo launched their epic Python documentary on August 28th! To celebrate, we sat down with Travis Oliphant âcreator of NumPy, SciPy, and moreâ to get his perspective on how Python took over the software world.
Stick around for the twist ending! We set aside Python and dissect Travisâ big idea to make open source projects financially sustainable through direct investment. đ„ VIDEO
đ€Ź Next.js is infuriating
Dominik Meca finally decided to write a blog post. Because anger is the best motivator. And heâs angry at Next.js:
The Next.js devs have a vision and itâs either their way or the highway. Note that if it was just the middleware, I wouldnât be sitting here, wasting away my weekend, ranting about a React framework. Believe it or not, Iâve got better things to do. Itâs constant pain you encounter daily when working with Next.js.
After complaining ranting some more, Dominik points to the issue tracker and calls it a dumpster fire, which I have a hard time disagreeing with.
The top HN comments on this post (400+ as I write this) are in vehemently agree with him. Iâd summarize the core issue as âtoo many layers of abstractionâ with a sprinkle of ânot enough extensibilityâ and a dash of âVercel-based feature roadmapââŠ
âïž Open source is one person
Josh Bressers was offended by The Registerâs recent story titled Putin on the code: DoD reportedly relies on utility by Russian dev:
If youâre not real smrt, it seems like pointing out an open source project is written by one person in a country you donât like is a bad thing. It could be. But it also could be the software running THE WHOLE F****ING PLANET is written by one person. In a country. But we have no idea which country. Itâs not the same person mind you, but itâs one person.
Josh goes on to point out (with receipts) that almost all open source is literally one person:
A project exists called ecosyste.ms that catalogs a lot of open source. Most of it I would guess, but not all. They currently have 11.8 million open source projects in their data⊠So what do we mean by one person is open source. What I mean is if we look at all the projects that ecosyste.ms is tracking, how many have a single person maintaining that project? Itâs about 7 million.
He also looks at npm package downloads and found that of the projects with over one million downloads this month (a proxy for usefulness), ~6,000 of them have solo maintainers while ~6,800 of them have more than one maintainer.
đȘ Why âCopy as cURLâ is so useful
In this article, Huon Wilson does an excellent job describing the usefulness of web browser dev toolsâ âCopy as cURLâ functionality and how best to work with its output to get stuff done.
âCopy as cURLâ gives bulky curl CLI invocation that captures almost exactly what the browser sent to the server, explicitly including all headers, authentication information, and any request data, in a directly executable way. Being executable means it can be used to easily replay the request as the browser sent it.
Huon says this is great for unambiguous communication with other people and easy edit/run debugging loops because itâs executable and easily modified in a shell script. There are downsides to using this technique pervasively, such as accidentally sharing secrets in pasted output, and verbosity, because the output can sometimes be very large.
đ° Bring your own agent to Zed
Thanks to Zed for sponsoring Changelog News
You shouldnât have to settle for subpar editing environments in order to use the AI agent of your choice.
Zed is a high-performance, open source code editor built for flow, collaboration, and speed. And they just launched the Agent Client Protocol (ACP) so you can build and use multiple external agents directly in Zed. Yes, you can now interact with third-party agents directly within Zed! To make this possible, they created ACP and partnered with Google to integrate Gemini CLI as the initial reference implementation.
Write your own agent, or fork Gemini CLI. Use it in Zed, or bring it to another ACP-compatible editor. This is AI tooling the way it should be: flexible, fast, and fully yours.
Head to zed.dev/blog to learn more.
đ§ž Bear is now source-available
Bear, a âprivacy-first, no-nonsense, super-fast blogging platformâ, was MIT licensed until yesterday. Herman Martinus, Bearâs creator, explains why he decided to change it:
Unfortunately over the years there have been cases of people forking the project in the attempt to set up a competing service. And it hurts. It hurts to see something youâve worked so hard on for so long get copied and distributed with only a few hours of modification. It hurts to have poured so much love into a piece of software to see it turned against you and threaten your livelihood. It hurts to believe in open-source and then be bitten by it.
He decided to adopt the Elastic License, which is almost identical to the MIT but with the stipulation that the software cannot be provided as a hosted or managed service. Herman cites sixth other projects that have made a similar change in the past few years, and concludes:
Weâre entering a new age of AI powered coding, where creating a competing product only involves typing âCreate a fork of this repo and change its name to something cool and deploy it on an EC2 instanceâ.
While Bearâs code is good, what makes the platform special is the people who use it, and the commitment to longevity.
I will ensure the platform is taken care of, even if it means backtracking on what people can do with the code itself.
đž The hidden costs of dependency bloat
Nawaz Dhandala unpacks why dependency bloat is such a pervasive problem:
Dependency bloat has become the silent productivity drag on software projects. Itâs not just about the size of your node_modules folder or the length of your requirements.txt. Itâs about the hidden costs that compound over time, making your codebase harder to maintain, your applications less secure, and your development process slower and more frustrating.
I like some of his advice on how to prevent dependency bloat in the first place.
- Question every addition
- Regular dependency audits
- Embrace minimalism
- Monitor your attack surface
- Foster a culture of ownership
These steps, of course, can be taken too far. The âyinâ to Dependency Hellâs âyangâ is Not Invented Here syndrome.
đïž Action absorbs anxiety
Arun Gupta, now a âfree agentâ after his surprise exit from Intel, joins us to discuss how heâs dealing with his first job hunt since the 1990s. Along the way, we talk about agentic coding strategies, what GPT-5âs release implies about the future, and more. (US buys 10% of Intel)++ đ„ VIDEO
đ§° A new kind of Ruby management tool
André Arko:
At this point, Iâve been using âuvâ for almost a year and I have to say, it is really, really good. The combination of speed, reliability, and functionality creates a spectacularly good experience. No more changing a package as you install something new only to realize later you broke something old, no more setting up dependencies manually only to have the cronned script break later.
About a month ago, I decided that if there was no tool like this for Ruby, I would make one rather than keep dreaming about it. I want to bring all the tricks and innovations of cargo, npm, and uv into a tool for Ruby: ârvâ
đ„· VIM Master
This in-browser game teaches core Vim motions and editing commands through short, focused levels.
đ Martin Fowler on LLMs and software dev
Thoughts on LLMs: everyoneâs got âem, but not everyoneâs are worth paying attention to. Martin Fowlerâs are. For instance:
My former colleague Rebecca Parsons, has been saying for a long time that hallucinations arenât a bug of LLMs, they are a feature. Indeed they are the feature. All an LLM does is produce hallucinations, itâs just that we find some of them useful.
and:
Iâve often heard, with decent reason, an LLM compared to a junior colleague. But I find LLMs are quite happy to say âall tests greenâ, yet when I run them, there are failures. If that was a junior engineerâs behavior, how long would it be before H.R. was involved?
đ Donât forget your (un)ordered list
- SMS URLs
- UncertainâšTâ©
- The ROI of exercise
- Donât build multi-agents
- Are we decentralized yet?
- An illustrated guide to OAuth
- Big O notation, visually explained
- Svelte component suite for data-driven apps
- Indirect prompt injection in Perplexity Comet
- Extracted system prompts from popular chatbots
- A tool that helps keep your GitHub Actions updated
- Survey: Seniors ship 2.5x more AI code than Juniors
- Self-hosted, web-based server management platform
- Querying billions of GitHub events using Modal and DuckDB
- Run Claude Code headlessly in a loop forever and see what happens
Thatâs the news for now, but we have some great episodes coming up!
- On Wed: Jim Remsik on organizing 6 (!) confs this fall
- On Fri: Christian Rocha on Charmâs new coding bestie
Have yourself a great week,
forward this to a friend who might dig it,
and Iâll talk to you again real soon. đ
âJerod