text stringlengths 0 1.49k |
|---|
**Erik St. Martin:** You should start making stuff up when people ask that... Like, "What's a gopher?" and you're like "It's kind of in the same family as a chupacabra..." \[laughter\] |
**Michael Stapelberg:** That's a good point, I'll remember that for next time. |
**Brian Ketelsen:** Alright, how about \#FreeSoftwareFriday? This is one of my favorite segments, where we give a shoutout to a person or a project that we love. I'd love to kick this one off with a shoutout to [Ashley McNamara](https://twitter.com/ashleymcnamara), who is not only an amazing technical person and progra... |
**Michael Stapelberg:** Yeah, I would really like to echo that and stress the point that really, if you think you wanna contribute to open source and you don't know how to program, there's still so many useful skills that you can bring to the table, and I really wish we would have more non-programmers in open source. I... |
**Carlisia Thompson:** I think this message also needs to be preached not only to beginners or people who are interested but not doing it, but also to veterans... Because sometimes we talk about making open source more accessible to beginners, and people say "Well, this codebase is so complicated..." If you don't have ... |
**Erik St. Martin:** Even triaging, because sometimes people who post issues are fly-by posting. "It crashes when I do such-and-such", and it's not enough for you to figure out, and often those are the things that get ignored for the longest time, because it's gonna take a time investment just to figure out how to recr... |
**Carlisia Thompson:** Yeah, and that reminds me to mention also that contributions to documentation might require less technical ability. At least at the beginning, you don't need to know a lot of technicalities about the project, but it's still hard and you still need to know the essence of what the project is about.... |
**Michael Stapelberg:** And also one point is you don't even need to know anything, because as soon as you post something that is wrong, as soon as you make a pull request that has a wrong documentation change, people will helpfully point out that it is wrong and what needs to be there. So the best way to get an answer... |
**Carlisia Thompson:** Absolutely. |
**Erik St. Martin:** \[01:04:03.19\] "I was working on something important, but you posted something wrong and I must stop!" \[laughter\] |
**Brian Ketelsen:** Exactly. |
**Carlisia Thompson:** "I must correct you!" |
**Erik St. Martin:** I had one of those moments the other night... My wife was heading upstairs to the bed or something, and I was like "I'll be up in a couple of minutes, I'm arguing with somebody on the internet." |
**Brian Ketelsen:** Yeah, somebody's wrong on the internet; I'll be there in a while. \[laughter\] |
**Carlisia Thompson:** Hey, I totally take advantage of that. I'm always "Hey, I think that that's how it should work." I have no idea, nobody corrects me. No, I'm kidding. |
**Erik St. Martin:** Did you have anything this week, Carlisia? |
**Carlisia Thompson:** No. |
**Erik St. Martin:** And how about you, Michael? Did you have a project or a maintainer you wanna give a shoutout to? |
**Michael Stapelberg:** Yeah, actually just today at work I was showing some of my colleagues an Emacs package that I've come to really appreciate, which is [magit](https://github.com/magit/magit). It is a Git front-end. It is integrated into Emacs, but you can also use it if you don't like Emacs at all, because it ess... |
That is just so convenient and so easy, and I use it all the time and I've come to realize that even though I'm a big command line user, these days whenever I have a Git-related thing that I wanna change, like I wanna commit a new conflict file or something, I'm at the point where I just start my Emacs to use Magit. It... |
**Brian Ketelsen:** Wow. |
**Erik St. Martin:** If only I used Emacs... |
**Brian Ketelsen:** Yeah, I'm afraid... |
**Michael Stapelberg:** You don't need to, that's what I'm saying. \[laughter\] |
**Erik St. Martin:** Alright, so mine this week - and this is probably the perfect episode for it - is called [Alacritty](https://jwilm.io/blog/announcing-alacritty/), and it's a terminal emulator that's GPU accelerated using OpenGL. It's written in Rust, so... I haven't contributed to it or anything... |
**Brian Ketelsen:** \[laughs\] Not yet. |
**Erik St. Martin:** But I have to say it is ridiculously fast. Window managers, I don't rotate through i3's there, but I've still struggled to find a terminal emulator that I really like. It's super fast, and it renders fonts and glyphs really nicely. |
No tabs. It's cross-platforms, so it'll work in all the places, but there's no things like you'd see out of iTerm2, like tabs and things like that. It really relies on your window manager to do that type of stuff. |
**Brian Ketelsen:** \[01:07:00.11\] So if you are on a Mac, you have to compile this yourself, but if you're running Arch - like most good people should - you can just install this from the AUR, which is awesome. |
**Erik St. Martin:** Yeah, I was actually kind of surprised that that was the only place that it was available as a pre-compiled package, because almost always Red Hat distributions and Ubuntu get it first, and you're usually the person who has to write the AUR... |
**Brian Ketelsen:** Yeah. I'm curious, and I don't mean this in a derogatory way at all, but the last couple times that I've tried to do compiling Rust applications from source, I've been bitten by the fact that Rust is still moving really quickly. Has it stabilized a bit, so that cloning some software and compiling it... |
**Erik St. Martin:** This is probably the only Rust thing that at least I've used knowingly, and I did compile it from source on an Ubuntu machine. You install (it's called) Rust Up first, and then that'll allow you to switch between the Rust versions, and that'll get you the latest stable release of Rust. And then thi... |
**Brian Ketelsen:** Oh, okay. |
**Erik St. Martin:** So it goes pretty quick. |
**Brian Ketelsen:** It's good to know. And do you use this daily, Alacritty? |
**Erik St. Martin:** Yes. |
**Brian Ketelsen:** Nice. Good to know. |
**Erik St. Martin:** Alright, so with that, I think that we are probably over-time, but I don't think anybody is complaining. It's been a ton of fun. We're so grateful to have you on the show, Michael... It's been a long time coming. |
**Brian Ketelsen:** We're not worthy... |
**Michael Stapelberg:** Thank you for having me. It was fun, thanks! |
**Erik St. Martin:** For the listeners, we are @GoTime.Fm. If you wanna be on the show, you have suggestions for guests or topics, file an issue at [ping](https://github.com/GoTimeFM/ping). We should be back to the normal studio next week, for anybody who's listening live now. We'll be back to the Changelog.com/live fo... |
With that, we'll see everybody next week! Bye, everybody! |
**Brian Ketelsen:** Thank you, Michael! |
**Carlisia Thompson:** Bye! Thank you, Michael. It was great! |
**Michael Stapelberg:** Anytime, bye-bye! |
• Background of Aaron Hnatiw, including his transition from criminology to computer security and how he ended up at Security Compass as a security researcher |
• How Aaron got interested in Go and started using it for scripting and contributing to projects |
• Teaching experience with Go: how Aaron taught third-year programmers using the language and resources such as the Go Tour and "The Go Programming Language" book |
• Comparison of Go to Python for security-related tasks, including ease of use and availability of libraries |
• Difficulty in using Go for InfoSec due to lack of libraries and knowledge of standard library |
• Importance of development background in contributing to InfoSec with Go |
• Aaron Hnatiw's experience with Go and learning from scratch |
• Using existing Python libraries as a starting point for creating equivalent Go libraries |
• The "CIA triad" and importance of understanding how technologies work to exploit vulnerabilities |
• Fuzzing and reproduction of breaking points as key skills in InfoSec |
• Importance of creative thinking, problem-solving, and deep diving into technologies for success in InfoSec |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.