Open source regrets (News)

0:28What up nerds? days and how everyone does the math to see how much everyone else is worth. Ben concludes, quote, we don't do the math to measure ourselves. We do the math to compare ourselves, end quote. So true, but that's just the setup. The money quote is a footnote to that sentence. Quote, the recent grad is troubled by how much the designer who got the job they want makes. The designer is troubled by how much the engineer makes. The engineer by the researcher. The The second thought I'd like to share comes from a not at all recent man named Job. After receiving news that he lost everything to raiders and a mighty wind, Job said, quote,

1:30Okay, let's get into the news. Open source regrets. A recent Akron News Ask HN thread piqued my interest. Maybe it will yours as well. Here's the question. Open source is usually seen as a win for learning, visibility, and the community. But have you ever regretted it? Maybe it became a burden to maintain, attracted the wrong users, or got used in ways you didn't expect? Would love to hear your experience, good or bad. Now, I'm about as pro-open source as devs come, but only a purist would say it's always an unadulterated win. This thread is filled with people sharing their open source regrets, which are worth hearing about.

2:09Here's one, for instance. Quote, when I was about 14, I open sourced a script to auto-configure X11's XRander. It was pretty lousy, had several bugs. I mentioned it on a KDE mailing list, and a KDE core contributor told me it was embarrassing code and to kill myself. I took it pretty hard and didn't contribute to KDE or X11 ever again. Probably took me about a year to build up the desire to code again. End quote. That was a singular event for this person, but still, just awful. Here's another one, which is more longitudinal. Quote, To be honest, I do regret it. After 20 years of working on FOSS projects, I've invested enormous amounts of time, effort, and money into these and other free slash open source initiatives.

2:50It was enjoyable initially. there's something addictive about receiving praise from strangers and unknown communities. You keep going because it feels good and you develop a sense of moral superiority. But years later, when the people closest to you are no longer around, you pause and reflect on how much energy you devoted to random strangers instead of those who shared your life. If I had invested even 1 % of the time and effort I put into FOSS projects into my relationships with loved ones, they would have been so much happier. Now I'm left wondering, what the hell I was doing all those years?

3:21github's latest ceo says farewell thomas domke is stepping down as github's ceo so he can build another startup in his announcement post thomas says quote over a decade ago my family and i made the leap to move from germany to the united states after the sale of my startup to microsoft in the years since i've had the privilege of working with many exceptional human beings including hubbers microsofties customers partners our github stars open source maintainers and developers around the world who've helped us shape GitHub. Still, after all this time, my startup roots have been tugging on me and I've decided to leave GitHub to become a founder again.

3:59End quote. Thomas took the reins in 2021 when Nat Friedman stepped down after taking the reins in 2018 when Chris Wanstraw stepped down after the Microsoft acquisition. Who will take the reins next? We don't know yet. HTTP2. The sequel is always worse. James Kittle breaks down HTTP2 from a security perspective and finds it breaks down pretty easily. Quote, HTTP2 is easily mistaken for a transport layer protocol that can be swapped in with zero security implications for the website behind it. In this paper, I'll introduce multiple new classes of HTTP2 exclusive threats caused by both implementation flaws and RFC imperfections.

4:40End quote. James shows how these flaws enable H2 exclusive desync attacks with case studies targeting some pretty high profile websites. It's now time for sponsored news. Augment Code has GPT-5. Augment Code has GPT-5 y 'all. Until now, Augment ran only on Cloud Sonnet 4. They've added GPT-5 and a model picker so you can select the right engine per task. Sonnet stays the default. GPT-5 is there when you want extra caution and cross-file brainpower. They tested both on the same coding chores. They tested single-file edits, multi-file refactors, bug fixes, and they found a clear trade-off. Sonnet equals speed and decisiveness.

5:23GPT-5 equals completeness and stronger cross-file reasoning. This enables better task alignment. Quick tweak? Sonnet's your go-to. Big refactor or careful logic rewrite? GPT-5 brings that extra context and TLC. The picker also delivers resiliency and continuity smarter routing, and cost latency control. If one model slows down or drifts in quality, you can instantly switch without breaking your flow. Over time, Augment can learn your preferences and even auto-route. Sonnet for quick diffs and GPT-5 for the heavy lifts. Learn more and start testing GPT-5 for yourself at augmentcode.com and follow that link to read the rest of their announcement post in the newsletter.

6:04PHP 8.5 adds pipe operator. The pipe operator is the coolest. and PHP is going to have it this November when version 8.5 ships. Here's some history. The pipe operator appears in many languages, mostly in the functional world. F-sharp has essentially the exact same operator, as does OCaml. Elixir has a slightly fancier version, which we considered but ultimately decided against for now. And numerous PHP libraries exist in the wild that offer similar capability with many extra expensive steps. The story for PHP pipes, though, begins with Hack slash HHVM Facebook's PHP fork knee-competitive implementation.

6:43Hack included many features beyond what PHP 5 of the day offered. Many of them eventually ended up in later PHP versions. One of its features was a unique spin on a pipe operator. End quote. Sarah Goleman started the effort to bring Hack's pipes to PHP directly in 2016. Fast forward to 2025, and Larry Garfield finally got it done. Meanwhile, JavaScript's pipe operator is still a stage two draft. Copyright suit could financially ruin AI industry. Many of our conversations around the future of tech after the AI upheaval have included a sometimes explicit, sometimes implicit, big but. You know, like, but.

7:21Something could happen that radically changes the AI course we're currently on. Turns out the largest copyright class action suit of all times might prove to be that Kalapidgian butt we've been alluding to. Quote, AI industry groups are urging an appeals court to block what they say is the largest copyright class action ever certified. They've warned that a single lawsuit raised by three authors over Anthropics AI training now threatens to financially ruin the entire AI industry if up to 7 million claimants end up joining the litigation and forcing a settlement. End quote. If the appeals court denies Anthropic's petition, they could face a$150 ,000 fine for each of those 7 million claimants whose works span a century of publishing history.

8:05Quote, confronted with such extreme potential damages, Anthropic may lose its right to raise valid defenses of its AI training, deciding it would be more prudent to settle, the company argued. And that could set an alarming precedent considering all the other lawsuits generative AI companies face over training on copyrighted materials. End quote. Yikes. All eyes will be fixed on this butt until further notice. That's the news for now, but go and subscribe to the Changelog newsletter for the full scoop of links worth clicking on, such as Sit on Your Ass Development, You Might Not Need Tmux, and Oyaml.wtf.

8:44Get in on the newsletter at changelog.news. Last week on the pod, we shipped our shows from Denver. Nora Jones on Wednesday, and Kaizen with Gerhard Lazu, on Friday. Scroll up in your feed and listen to those if you haven't yet. And stay tuned for some awesome pods this week. On Wednesday, Dr. Evelina Kudis joins us to talk biocomputing. And on Friday, Brian Cantrell from Oxide Computer is on Changelog and Friends discussing their$100 million raise. Have yourself a great week. Like, subscribe, and five-star review us if you like the show, and I'll talk to you again real soon.

9:26Game on.