What would you remove from Go?

When we talk about improving a programming language, we often think about what features we would add. Things like generics in Go, async/away in JS, etc. In this episode we take a different approach and talk about what we would remove from Go to make it better.

When we talk about improving a programming language, we often think about what features we would add. Things like generics in Go, async/away in JS, etc. In this episode we take a different approach and talk about what we would remove from Go to make it better.

Leave us a comment

Changelog++ members save 4 minutes on this episode because they made the ads disappear. Join today!

Sponsors:

Linode – Get $100 in free credit to get started on Linode – our cloud of choice and the home of Changelog.com. Head to linode.com/changelog
Retool – Retool makes it super simple to build back-office apps in hours, not days. The tool is is built by engineers, explicitly for engineers. Learn more and try it for free at retool.com/changelog
Equinix – Equinix Metal is built from the ground up to empower developers with low-latency, high performance infrastructure anywhere. Get $500 in free credit to play with plus a rad t-shirt at info.equinixmetal.com/changelog
Fastly – Our bandwidth partner. Fastly powers fast, secure, and scalable digital experiences. Move beyond your content delivery network to their powerful edge cloud platform. Learn more at fastly.com.

Featuring:

Daniel Martí – Twitter, GitHub, LinkedIn, WebsiteMat Ryer – Twitter, GitHub, LinkedIn, WebsiteJohnny Boursiquot – Twitter, GitHub, WebsiteJon Calhoun – Twitter, GitHub, Website

Show Notes:

Things in Go I Never Use (Mat at Gotham Go)
Label Breaks in Go
Go tips and tricks: almost everything about imports
When Should I Use One Liner if…else Statements in Go?
The container/list package
Understanding init in Go

Something missing or broken? PRs welcome!