text stringlengths 0 2.35k |
|---|
**Ian Lopshire:** \[56:06\] I do kind of agree with Kris here, that it's changed a bit. I don't know if I would say it's changed and become worse for experienced people that wanna write code a particular way, but it does seem to be more -- almost academic, instead of practical. Especially modules, and maybe generics as... |
**Kris Brandow:** Yeah. |
**Ian Lopshire:** I don't know if we need a fork, but I do agree that there's been a change some way; a shift in culture, or something. |
**Kris Brandow:** I feel like that's a good way of putting it. It does feel like it's shifted from a practical to a more academic, more research-style thing. Once again, this doesn't have to be like a fork-fork, like we have to have completely separate development teams. Maybe it's like an extended conversation that we... |
**Jerod Santo:** Well, while we're here, let's have a forked Go naming brainstorming session. I'm thinking, "NoGo", I'm thinking "Gone", I'm thinking "Stop", or... |
**Ian Lopshire:** Stay... |
**Jerod Santo:** "Stay..." \[laughs\] Go 2? Oh, GoTo, not Go 2... Alright. Any other potential fork names? We're gonna have to ideate this a bit... |
**Kris Brandow:** Maybe Og... |
**Jerod Santo:** There you go, rearrange the letters. |
**Kris Brandow:** You could steal the mascot and just call it Gopher... |
**Ian Lopshire:** Please don't call it Gopher... \[laughs\] |
**Jerod Santo:** \[laughs\] Like the old networking protocol, Gopher? |
**Kris Brandow:** We could call it Hoard, because Gophers are hoarders, so that could be a fun name... |
**Jerod Santo:** I'm glad you put a d at the end of that. |
**Kris Brandow:** Yes, HoarD. |
**Jerod Santo:** Please enunciate. Okay... Submit your Go fork names in the comments or on the Twitter poll for this particular unpopular opinion. I'm thinking that one's gonna be -- |
**Kris Brandow:** Oh, God. Someone said Go++, or Go\#. |
**Jerod Santo:** Go\# ! |
**Ian Lopshire:** Go\# ! I'm sticking with that one. |
**Jerod Santo:** We've got IaGo... I'm assuming that's a Lion King reference... Alright, let me share my unpopular opinion here. So on episode \#192 Ashley Jeffs had what was in my opinion the most unpop of all times. His opinion was that people who vote in Twitter polls are losers. Did you guys hear that one? He says ... |
So based on that empirical evidence, I can with confidence state that my unpopular opinion is that people who vote on Twitter polls are winners, and they should tweet more. Everybody cares about your opinion, and it does matter! |
**Kris Brandow:** \[laughs\] |
**Ian Lopshire:** I feel like that one is going to be unpopular. |
**Jerod Santo:** I think it might. \[laughs\] |
**Kris Brandow:** I think people are just gonna be in spite just voting that... Like, yeah, that's unpopular, just to -- yeah. |
**Jerod Santo:** Well, time will tell. Please follow @GoTimeFM on Twitter and vote your opinion. Do you think you're actually a winner, or a loser? We will find out on Twitter. That has been our show for this week. I appreciate you all letting me crash the party and ask my newbie/outsider questions. Hopefully, there ar... |
**Ian Lopshire:** I'm glad to be here. |
**Jerod Santo:** Kris, you were also here, as Mat Ryer would say... |
**Kris Brandow:** \[laughs\] |
**Jerod Santo:** But I'll say thank you for hanging out and sharing your wisdom and your spicy hot takes... A Go fork - I had never seen that one coming. |
**Kris Brandow:** Yeah. |
**Jerod Santo:** But that's Go Time for this week. We'll talk to y'all next week. |
• Definition of bloat in Go programming |
• Types of bloat: code bloat (large codebases) vs binary bloat (large deployment sizes) |
• Impact of imports on code size, using protobuf and gRPC as examples |
• Statistics on lines of code imported from protobuf (27,000) and gRPC (100,000+) |
• Discussion of why people might prefer smaller libraries like Net RPC over larger ones like gRPC |
• Code bloat and its impact on build times |
• The importance of reviewing and maintaining code dependencies |
• Tools for analyzing and visualizing dependencies (Goda) |
• Principles for choosing packages with minimal dependencies |
• Trade-offs between package size and complexity vs. maintainability |
• Codebase organization and dependency relationships in large projects |
• Cyclic dependencies in Go codebases can lead to maintainability issues |
• Binary bloat: large binaries are becoming more common, but may not be a concern for many users due to fast upload speeds |
• Small devices (e.g. Raspberry Pi) have limited storage and may be affected by binary size |
• TinyGo is an attempt to address the problem of small device limitations by creating a smaller standard library |
• Nostalgia: discussion about older computers, floppy disks, and other retro tech |
• Using Go with TinyGo for embedded devices |
• Debouncing code in TinyGo for handling button noise |
• Comparing Go and C for structured programming |
• Discussion on binary bloat and its impact on small devices |
• Advantages of using TinyGo for web development (WASM) |
• Fmt package size and dependencies contributing to binary bloat |
• The benefits and drawbacks of Rust's macro processing and its impact on code complexity |
• Code bloat and its relation to technical debt in large projects |
• Strategies for managing complexity, including testing, mocking, and integration testing |
• Definitions of technical debt, including concepts of cost, prioritization, and mortgage analogy |
• Technical debt as the difference between an ideal state and a current state of maintainability or effort required to maintain a codebase |
• Designing for flexibility and change |
• Avoiding "unchangeable decision" thinking and prioritizing adaptability |
• Importance of upfront design and thinking through possible futures |
• Abstraction and designing the right abstractions from the start |
• Deletability: designing things so they can be easily deleted or removed |
• Practicing abstraction and getting it wrong as a learning process |
• Designing features for specific use cases vs general solutions |
• Reviewing dependencies and codebases with similar standards as own codebase |
• Responsibility for reviewing and maintaining dependencies |
• Approaches to reviewing dependencies (e.g., reading every line, looking at code quality) |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.