text stringlengths 0 1.49k |
|---|
[3198.06 --> 3198.66] Thanks for listening. |
• Introduction to episode 33 of GoTime |
• Guests: Kelsey Hightower and Carlisia Thompson, with Mat Ryer as the main guest |
• Mat Ryer's backstory on how he started programming and discovered Go |
• Discussion of how Go has grown in popularity over the past few years |
• The role of sysadmins in adopting and promoting Go |
• Comparison of Go to Ruby and Rails, and how Docker may have played a similar role for Go as Rails did for Ruby |
• Conversation about future developments for building web applications with Go, including Go Buffalo |
• Docker's containerization revolutionized app deployment, making it more reproducible. |
• Go benefited from Docker and other serious projects, feeling more mature and stable. |
• The single-binary feature of Go made it appealing for rapid prototyping and development. |
• Mat Ryer's projects, such as Bitbar, demonstrated the value of abstraction and community engagement. |
• GitHub stars serve as a reliable indicator of interest and appreciation for projects. |
• Twitter likes vs. GitHub stars: while Twitter is used to acknowledge content, GitHub stars represent genuine interest. |
• Gopherize Me was created as a way to let users build their own personalized gophers |
• Mat Ryer built the initial version in less than 5 hours using Google Cloud Storage and AppEngine |
• The site has had over 15,000 users and has been improved with additional features and scalability enhancements |
• Go's ability to handle concurrent tasks and scale makes it a popular choice for rapid development and deployment |
• Mat Ryer attributes the success of Gopherize Me to its grassroots effort and community involvement |
• Importance of rewriting code and learning from mistakes |
• Benefits of Test-Driven Development (TDD) in software development |
• Go 1.8 features, including improved defer performance and clean shutdown |
• Use of minimalistic languages like Go to simplify coding and improve productivity |
• Value of knowledge gained through experimentation and prototyping over preserving original code |
• Discussion on providing resources for understanding new features in Golang |
• Review of notable changes in Golang 1.8, including mutex contention profiling and GC latency improvements |
• Packaging efforts and the release of a package management implementation for Go |
• Dependency management and the role of tools like "drop" in resolving dependencies |
• Introduction to The App Project, a framework for building GUI applications in Go |
• Discussion on the potential overreach of using a single language (Go) for all programming tasks. |
• The relationship between enjoyment and productivity when working with a programming language |
• Context-switching and the cost of learning multiple languages |
• Personal preference and habit in choosing a programming language |
• Language education and its impact on communication and community participation |
• The prevalence of using a dominant language or default language to avoid context-switching |
• Attempting to bring serverless functions to Kubernetes |
• Serverless is not just about functions as a service, but about focusing on the application and removing management of infrastructure |
• Event-driven programming is a key benefit of serverless architecture |
• Cloud-native software stack initiatives, such as CNCF, are important for fostering community and ensuring long-term project sustainability |
• Various open-source projects and tools were mentioned as being useful or noteworthy, including Visual Studio Code, Gqrx, GNU Radio, and the Go newsletter. |
• Discussion of a cool API and its potential uses |
• Gopherize Me service and personalized gophers on various products |
• Satire about the gophers taking over the world and creating too many combinations |
• Show closing and thank you to listeners, sponsors, and upcoming schedule |
**Erik St. Martin:** Welcome back everybody to another episode of GoTime. Today's episode is number 33, and our sponsors for today's show are Backtrace and Ardan Labs' Ultimate Go Series of training. |
Today on the show for hosts we have myself, Erik St. Martin... Brian Ketelsen could not be with us due to a family emergency, but Kelsey Hightower has graciously stood in to take Brian's place today. |
**Kelsey Hightower:** Yeah, just like your Go runtime, we're going to even upgrade your host. \[laughter\] We have a few bug fixes, a few patches, but I think you're gonna like what you get. |
**Erik St. Martin:** And we also have Carlisia Pinto on the call... |
**Carlisia Thompson:** Hi, everybody. |
**Erik St. Martin:** And our guest for today - he's been speaking a lot and is also an author... Welcome, Mat Ryer. |
**Mat Ryer:** Hey, thank you! Good to be here! |
**Erik St. Martin:** For those who aren't familiar with who you are and the things you're working on, do you wanna give just a little bit of a backstory and then we'll kind of get into some interesting stuff you've been working on? |
**Mat Ryer:** Yeah, sure. So I started programming when I was really little, with my dad. We used to type content out of magazines, little BASIC programs to make things work, and then we'd play around with it, change variables, see if we could break it and see what we could do with it. I just loved that. I loved the fa... |
I'm very lucky to do that now as a career, and Go is a very interesting choice for me, because I started it when I was gonna build something for Google App Engine, and it was either Java or Python, or there was these weird little experimental language called Go. That was a very appealing thing because of this nature th... |
It's great, and that's kind of why I talk about it all the time and why I use it... Basically, almost exclusively now I write in Go. |
**Erik St. Martin:** It's kind of funny, and I know Kelsey's been in the community for a couple years, and same with Carlisia... It's interesting to reminisce on just a couple years ago you could have a conversation with other tech people and mention Go and they're like "What's that?" and now it's so much bigger... it'... |
**Mat Ryer:** Yeah, absolutely. |
**Erik St. Martin:** When did you jump in, Carlisia? |
**Carlisia Thompson:** I got started with this whole thing when I went to GopherCon in 2015, and when I got back I started doing it on the side, learning and getting involved with the community, and going to the Go meetups in San Diego. |
**Erik St. Martin:** And Kelsey, you spoke at the first GopherCon, so you were using Go for quite a while before then, too. Were you pre-1.0? |
**Kelsey Hightower:** \[03:56\] Yeah, I think during the pre-1.0 days I was at Puppet Labs still, where everything was written in Ruby, and we were exploring a replacement that had to be cross-platform. We wanted something faster, so C++ was on the table. We were doing Clojure at the time, and I think Go was a bit too ... |
**Mat Ryer:** Actually, I remember... Kelsey, I was at the first GopherCon where you did your talk on Gopher sysadmins. That was the time that we decided to build something that we could put into production, because before that it felt like this was an experimental language, and you were talking about using this... And... |
I looked up the presentation just before this, and just a bit of trivia... Your last slide in that presentation is titled, "It's GoTime!" \[laughter\] |
**Kelsey Hightower:** Yes, that is a good observation! And you bring up a good point, because I think the Go community, if you look at most of the popular projects that are in Go, things like Docker, Hacker, Terraform - all these systems oriented tools Consul, Etcd databases, and I think that the maturity that's requir... |
**Erik St. Martin:** It's interesting that you point that out though. We tend to view sysadmins as kind of like the gatekeepers to production, and ultimately they take ownership. The DevOps role has changed that a bit in the recent years, but before you had to throw it over the fence and the system administration side ... |
**Mat Ryer:** Yeah, and Go was a systems language in a lot of people's minds for a long time. I've been building websites in Go for a while, but it's not as easy as it is in Rails. At least it's not yet. I'm quite hopeful for Go Buffalo, because I think what Mark Bates is doing on Go Buffalo I think is going to bring s... |
Because actually Ruby was never -- no one would know Ruby if it weren't for Rails. Go has taken off without its Rails, but we might see a much bigger explosion in the use of the language, once we can make building web very easy and enjoyable. |
**Kelsey Hightower:** \[07:42\] I always think about that... You brought up a good point - Rails did a lot for Ruby, and I would say maybe Docker did the same thing for Golang. Docker adopted Go really early on, and I think most people -- because they attracted a huge open source community of contributors, and I can ev... |
**Erik St. Martin:** I think it was kind of like a perfect storm though too, because even when I first started getting into Go, Docker hadn't really been released yet, but Heroku was doing Doozer and Etcd, and then Consul came out... So it was really this perfect storm of distributed systems outside of your major Googl... |
**Mat Ryer:** Yeah, but the other thing is Docker and all those early projects - they're kind of serious things, I think. Rails, you can kind of build fun apps, and the performance wasn't a primary concern; productivity was, performance of the dev team was something that they care about being rapid in all this. And it ... |
I think Go benefitted from some of those projects, because they just felt grown-up and it felt more serious, and stable, like you could use it in production. |
**Kelsey Hightower:** Looking back, I think one of the biggest sticking points for Go was the ability to create that single binary, as we entered the GitHub era where you build an idea and you throw it on GitHub. But I can remember a lot of things you would try on GitHub, especially if it was written in NodeJS or Rails... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.