This week we’re catching up on the news! Kris is joined by Ian to discuss some of the recent news from around the Go community. Listen in to hear whether the co-hosts believe there’s software that shouldn’t be written in Go, their thoughts on if Go is evolving in the right direction & whether common nouns make good package names.
Featuring
Sponsors
Neo4j – Is your code getting dragged down by JOINs and long query times? The problem might be your database…Try simplifying the complex with graphs. Stop asking relational databases to do more than they were made for. Graphs work well for use cases with lots of data connections like supply chain, fraud detection, real-time analytics, and genAI. With Neo4j, you can code in your favorite programming language and against any driver. Plus, it’s easy to integrate into your tech stack.
Speakeasy – Production-ready, Enterprise-resilient, best-in-class SDKs crafted in minutes. Speakeasy takes care of the entire SDK workflow to save you significant time, delivering SDKs to your customers in minutes with just a few clicks! Create your first SDK for free!
Notes & Links
- What software shouldn’t you write in Go?
- The myth of Go garbage collection hindering “real-time” software?
- The long-overdue problem coming for some people in Go 1.23
- Don’t name packages common nouns
- Alternatives to Makefiles written in Go
- Go evolves in the wrong direction
- Teaching Concurrency
- Computation and State Machines
Chapters
| Chapter Number | Chapter Start Time | Chapter Title |
| 1 | 00:00 | It's Go Time! |
| 2 | 00:41 | Sponsor: Neo4j |
| 3 | 01:43 | Intro |
| 4 | 02:37 | Go evolves in the wrong direction |
| 5 | 13:02 | What NOT to write in Go |
| 6 | 20:29 | Teaching concurrency |
| 7 | 27:23 | Make in Go |
| 8 | 32:06 | Sponsor: Speakeasy |
| 9 | 35:44 | Go's overdue problem |
| 10 | 41:39 | Don't name packages common nouns |
| 11 | 50:03 | Unpopular Opinions! |
| 12 | 50:33 | Kris' unpop |
| 13 | 1:05:29 | Ian's unpop |