text stringlengths 0 1.49k |
|---|
**Erik St. Martin:** Yeah, stack up more Mac minis in Adam's office. |
**Brian Ketelsen:** We gotta do a show entirely on Adam's setup and his little Mac minis... I think it's kind of crazy. |
**Erik St. Martin:** Yeah, so to explain what the limitation is - the way this actually works is all of us are on Skype and we are all called by different Skype accounts that are all running on separate Mac minis that are all mixed together in a mixing port that Adam Stacoviak of Changelog does. So he's hiding behind t... |
**Brian Ketelsen:** Nothing to see here, move along... |
**Erik St. Martin:** So huge thank you to all of our listeners, especially the people listening live right now. Huge shoutout to our sponsors for today's episode - Toptal and Compose; without them, we wouldn't have a show. Definitely share the show with fellow Go programmers. We are GoTime.fm online, @GoTimeFM on Twitt... |
**Carlisia Thompson:** Bye! |
**Brian Ketelsen:** Thanks for coming on, Charity. We really appreciate it! |
**Charity Majors:** My pleasure! Bye-bye! |
• The hosts discuss the i3 window manager with guest Michael Stapelberg, its creator |
• Background on i3 and its history, including why it was created and how it's used |
• Discussion of alternatives to i3, such as Divvy, and whether they are comparable |
• Michael Stapelberg's background in programming languages, including C, C++, Perl, and Go |
• Why he chose to use C for i3 despite having knowledge of other languages |
• His recent shift to Go as his favorite language, and why he prefers it over others |
• Discussion of the challenges and benefits of maintaining a large test suite like i3's |
• Go's simplicity and familiarity make it easy to learn |
• The language itself is not particularly innovative, but its features and ecosystem come together to create a compelling experience |
• Easy-to-read code makes it simple for developers to jump into new projects |
• Go's auto-formatter (gofmt) ensures consistency across the entire codebase |
• Most developers do not care about personal formatting preferences when using gofmt |
• The community has adopted gofmt as a standard, eliminating debates over formatting style |
• Configuring code formatting tools and their limitations |
• Discussion of desktop environments vs window managers |
• i3 window manager capabilities and customizability |
• Why i3 cannot be run natively on MacOS or Windows |
• Michael Stapelberg's work on gokrazy user space for Raspberry Pi |
• Custom Linux image with outdated base system was used on multiple Raspberry Pis |
• Desire for devices to auto-update and minimize attack surface |
• Gokrazy project provides a minimal, kernel-based Linux distribution with auto-updates |
• Project uses Travis CI for building and updating kernel and firmware |
• Automated testing and deployment of new images using GitHub pull requests |
• No dual BIOS functionality on Raspberry Pi hardware due to its limitations |
• Upgrading to higher-level development tools for faster development and lower costs |
• Using embedded devices with ARM architecture for hobby projects |
• Discussion of i3 (i3wm) window manager, its simplicity, and its potential drawbacks |
• Michael Stapelberg's job at Google working on the Go language in a capacity outside of the main team |
• Comparison between Google's internal software infrastructure and open source equivalents |
• Potential for open source to be influenced by or align with Google's internal tools |
• Michael Stapelberg shared his experience of requesting flash storage from an admin team and being surprised by their reaction |
• Google is following a trend of open-sourcing infrastructure, with recent releases including Abseil |
• The Go language team has a project to open-source part of the infrastructure, but specific plans are not yet clear |
• Kubernetes and other infrastructure tools have been made available as open-source alternatives to Google's proprietary offerings |
• The expanderr project provides automated error checking for Go code and is being integrated into various editors, including Vim |
• The speaker demonstrated a Go tool that expands whatever is under the cursor when invoked. |
• Error checking in Go is a hot topic and the speaker was unsure if others would like their tool. |
• The tool was well-received at a Go meetup in Zurich, with Robert Griesemer from the Go team present. |
• Speculation about adding a new keyword or syntax feature for error handling in Go. |
• Discussion of the benefits of explicit error handling in Go and its effects on end users. |
• Introduction to some interesting projects and news, including the Space Gophers screensaver for Mac and security updates to Go. |
• The group discusses their experiences with Go programming and how they "graduated" from stages of learning the language. |
• They reference a blog post about the 7 stages of becoming a Go programmer, which pokes fun at common misconceptions beginners have when learning the language. |
• The stages include things like believing goroutines will solve all problems and eventually realizing that abstractions are complicated. |
• The group shares their own experiences with these stages and how they came to appreciate the simplicity of Go programming. |
• They also discuss the popularity of the Go gopher mascot and how it has become a symbol of the language and community. |
• The conversation concludes with a shoutout to Ashley McNamara, who is promoting open source contributions beyond just coding. |
• Contributions to open-source projects can be made with minimal technical ability |
• Triage and recreation of issues is an important part of contributing |
• Documentation contributions require less technical expertise than coding |
• Posting incorrect information can lead to helpful corrections from others |
• Non-technical individuals can help by tracking down issues or providing context |
• The Emacs package Magit was mentioned as a useful tool for Git front-end |
• The terminal emulator Alacritty was discussed, its features and installation process |
• Rust compilation stability was addressed, with suggestions for using Rust Up |
• Stapelberg's farewell |
**Erik St. Martin:** Welcome back everybody to another episode of GoTime. Today's episode is number 59. On the show today we have myself, Erik St. Martin. Brian Ketelsen is also here... |
**Brian Ketelsen:** I'm so excited I can't even hold myself. |
**Erik St. Martin:** Right? |
**Brian Ketelsen:** It's just ridiculous. |
**Erik St. Martin:** And Carlisia Pinto... |
**Carlisia Thompson:** Hi, everybody! |
**Erik St. Martin:** And our special guest today, that Brian and I are particular fanboys of, is Michael Stapelberg, who among other things is the creator of i3 window manager, which you've probably only heard us mention a handful of times. |
**Brian Ketelsen:** A thousand times. |
**Erik St. Martin:** Michael, I know you do a lot more stuff, too... Do you wanna give everybody a little bit of background on you, your history and software development, and in particular getting into Go? |
**Michael Stapelberg:** Sure, yeah. The project that most people know me for is the [i3 window manager](https://i3wm.org/) by far. I started that project in 2009, so we're gonna have a nice ten-year anniversary pretty soon. The reason I started it back then was just that I was not very satisfied with the window manager... |
**Erik St. Martin:** Oh, nice! |
**Michael Stapelberg:** So that's that. It is a tiling window manager for power users or advanced users or programmers, or however you wanna choose the audience, but the idea is that we don't target beginners, so we don't have to be intuitive. That sounds a little bit strange at first, but it allows us to optimize for ... |
**Erik St. Martin:** One of the things I hate about my Mac is that there is no i3... |
**Brian Ketelsen:** Technically, there is, it's just not very useful. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.