Why GitHub actually won (News)

16 Sep 2024 · 8 min

Ask about this episode

Ask anything about it. ChatGPT or Claude reads this page and answers with the times it was said.

Connect VO and ask about every podcast you hear, including the moments you saved. Add to ChatGPT · Add to Claude

In short

The Changelog Podcast Episode Notes

Episode Title

Why GitHub Actually Won (News) Date: September 16, 2024 Hosts: Jared and Scott Chacon

---

Episode Overview In this episode, the hosts discuss key developments in the world of software development, focusing on GitHub's success, the significance of the Open Source Pledge, and interesting AI advancements. The episode also touches on the resurgence of PHP, particularly due to the Laravel framework, and notable fundraising events in the industry.

Key Topics

  1. Why GitHub Actually Won
  2. Scott Chacon's Insight:
  3. GitHub's success can be boiled down to two primary reasons:
  4. Timing: GitHub launched at a pivotal moment for code collaboration.
  5. Taste: The founders possessed an acute understanding of developer needs.
  6. Historical Context:
  7. Scott notes that many previous ventures by the co-founders failed, highlighting the unpredictable nature of success tied to timing.
  • Developer Experience (DevEx):
  • GitHub focused on improving developer experience rather than catering to advertisers or executives.
  • This approach was innovative during the platform's inception in 2008 and set a standard for modern developer tools.
  1. The Open Source Pledge
  2. Sentry's Initiative:
  3. Chad Whitaker and Sentry have created a pledge for companies to support open source software.
  4. Call to Action: Companies are encouraged to financially support maintainers to prevent burnout and maintain software quality.
  5. Importance: This pledge addresses issues highlighted by previous high-profile vulnerabilities (e.g., Log4J, Heartbleed).
  1. AI and Personal Legacy
  2. Benj Edwards' Project:
  3. Edwards used AI to replicate his late father's handwriting, raising ethical questions about authenticity and media representation.
  4. This project reflects broader trends in using technology for personal remembrance and connection.
  1. The PHP Resurgence
  2. Dave Kiss's Perspective:
  3. PHP is experiencing renewed popularity, largely due to the Laravel framework.
  4. Laravel's Impact: Kiss describes his positive experience creating a trivial Laravel app, showcasing the framework's appeal and ease of use.
  1. Laravel's Funding Success
  2. Taylor Otwell's Achievement:
  3. Taylor Otwell and the Laravel team raised $57 million in Series A funding.
  4. Otwell's journey from creating Laravel as a personal project to leading a successful framework highlights the potential growth of open-source projects.

Sponsored Segment

Warpstream

  • Product Overview:
  • Warpstream offers a deployment model for Kafka-compatible data streaming that eliminates costs associated with local disks and networking fees.
  • Key Features:
  • Zero disk architecture reduces storage costs.
  • Eliminates interzone networking fees for cost efficiency.
  • Stateless architecture simplifies operation management.

Conclusion

  • Additional Information:
  • Listeners are encouraged to check out the ChangeLog newsletter for more stories, including open-source company funding insights and programming language rankings from RedMonk.
  • Upcoming Episodes:
  • Features on codebase quality and ongoing improvement in software development practices.

Call to Action

  • Encourage listeners to leave a five-star review and participate in upcoming discussions.

---

This episode encapsulates the triumphs and challenges within software development, emphasizing the importance of timing, innovation, and community support in the tech landscape.

Written by AI. May contain mistakes. Listen to the episode to check what was said.

Hear the part that matters, and keep it.Open this episode in VO. Double tap your headphones to save a moment as you listen.
Get VO free

Transcript

Automatic transcript. May contain errors.

0:05What up nerds? I'm Jared and this is Changelog news for the week of Monday September 16th 2024. A dear friend of mine fell prey to a post-acquisition layoff alongside about 30 % of the company, and he's looking for work. He's a super solid network engineer who taught me a bunch with decades of experience. I'll take any leads you might have. Please hit me up. Okay, let's get into this week's news. Why GitHub actually won. Scott Chacon writes up his insider's take on why GitHub became the de facto code collaboration site. Here's the quick version. Quote, I can boil it down to exactly two reasons that happen to resonate with each other at the perfect frequency.

0:57One, GitHub started at the right time. Two, GitHub had good taste. All four GitHub co-founders had flops both before and after GitHub. Chris and PJ couldn't quite make fam spam work before GitHub, Tom and I couldn't quite make Chatterbug explode after GitHub. I think both of these ventures had good taste and great product, but it wasn't the right place or time or market or whatever for them to become GitHub level, end quote. One of the problems with success is that so much of it relies on timing, which is one of the big things we cannot control. What we can control, however, is what we decide to build.

1:38Here's Scott again. We cared about the developer experience and had the creativity to throw away assumptions about what it was supposed to be and build how we wanted to work. Everyone else tried to build what they thought they could sell to advertisers or CTOs. End quote. This DevEx focused strategy is commonplace today, but it was avant-garde back in 2008. Definitely read Scott's entire post for the full history lesson on what developer tooling looked like back when GitHub entered the scene. The open source pledge. Chad Whitaker and our longtime sponsors slash friends at Sentry have been leading the way on corporate open source support for a while.

2:23Now they've created a pledge for other orgs to join them in putting their money where their source is. Quote, whether you're a CEO, CFO, CTO, or just a dev, your company surely depends on open source software. It's time to pay the maintainers. Our companies feast at the open source table year after year. Through the open source pledge, we pay the maintainers of the software that we consume. This prevents the maintainer burnout that flares up in high-profile security incidents such as XZ, Log4J, and Heartbleed, end quote. Send this link to decision makers in your org and join the growing list of member companies who have taken the open source pledge.

3:07My dead father is writing me notes again. File this one under AI. Things are getting weird. Benj Edwards used an image synthesis model to reproduce his late father's handwriting. He fed it a bunch of journals his dad left behind and now part of him will live on in a dynamic way that was impossible a decade ago. I have a feeling this is just the beginning of a trend that will end with people recreating their dead loved ones almost entirely. Benj's thoughts after accomplishing this goal, quote, the results astounded me and raised deep questions about ethics, the authenticity of media artifacts, and the personal meaning behind handwriting itself.

3:55It's now time for sponsored news. Warpstream lets you bring your own cloud. Warpstream's BYOC deployment model for Kafka-compatible data streaming gives you the best of both worlds between self-hosted and cloud. This model also gives you a lot of zeros, and that's a good thing. Zero disks, because Warpstream's zero disk architecture eliminates local disks entirely and reduces storage costs by more than 24x. Zero interzone networking fees. More than 80 % of Kafka costs are not hardware, they're interzone networking fees. Because Warpstream runs on top of S3 compatible object storage and doesn't manually replicate data between zones, those fees are completely eliminated.

4:44Zero Ops Auto Scaling. WarpStream replaces stateful Kafka brokers with stateless agents, so your team can skip the weekly burden of partitioning rebalancing, scaling headaches, volume management, capacity planning, and more. Zero Access. WarpStream agents run on your VMs, in your cloud or VPC, and store data in your object storage buckets. Traffic flows seamlessly from producers to consumers without ever leaving your virtual private cloud. Here's a non-zero for you. WarpStream works in every cloud. They have native support for AWS S3, GCP GCS, and Azure Blob Storage. It also works with any cloud or self-hosted solution that has an S3-compatible object storage.

5:30Head to warpstream.com slash BYOC to learn more and get started for free. Once again, that's warpstream.com slash BYOC. Look out, kids. PHP is the new JavaScript. Dave Kiss explains the current hype and traction that PHP is getting mostly on X and a few YouTube channels. Quote, there's been a palpable shift in the air. You can sense it. People seem excited about PHP. What happened? Well, Laravel happened and has been happening. End quote. He goes on to build a trivial Laravel app with help from the Cursor AI code generator, of course, and sums up the experience as thus. Am I a convert? A newly minted PHP web artisan?

6:16You bet your bottom dollar I am. Depending on how critical you are of my AI coding approach, you might argue that I've still literally never touched a Laravel application. But I'll tell you what, Laravel makes PHP fun again. I'm here for it. Maybe you should be too. Laravel raises a$57 million Series A Speaking of PHP Taylor Otwell and the Laravel team have decided to take a big step with their wildly successful web framework Fortune.com published an exclusive on the raise as well as some background on Taylor's history Laravel's history and what it all means Quote Otwell is originally from Arkansas and early in his career worked at a trucking company as a programmer where he was first exposed to open source.

7:04He still lives in Arkansas, and rather than a rip, roaring growth story, Otwell started Laravel as a personal project more than a decade ago as he sought to build something he wanted. End quote. Taylor didn't just build something he wanted. He built something that has brought success to thousands, maybe hundreds of thousands of developers all around the world. Here's hoping he can navigate venture-funded open source as well as he's done so far. That is the news for now, but give the companion ChangeLog newsletter a quick scan for even more stories worth your attention, such as Lucas DaCosta, ongoing open source as a VC-backed company, a customizable select element for the web is in the works, and RedMonk's latest programming language rankings.

7:51Sign up if you haven't yet at changelog.com slash news. we have some great episodes coming up this week on wednesday jimmy miller tells us about the best worst codebase and on friday gerhard lazio is back for kaizen 16 have a great week leave us a five-star review if you dig our work and i'll talk to you again real soon

From the publisher

Scott Chacon writes up his insider take on GitHub's success, Sentry wants other companies to take the Open Source Pledge, Benj Edwards used AI to reproduce his late father's handwriting, Dave Kiss explains the current hype that PHP is getting & Taylor Otwell raises $57 million series A from Accel.

More from The Changelog: Software Development, Open Source

All 232 episodes
Why GitHub actually won (News)The Changelog: Software Development, Open Source · 8 min
Listen in VO