text stringlengths 0 1.49k |
|---|
**Erik St. Martin:** I don't even remember that, was there? |
**Brian Ketelsen:** There was. There was a Go cross-compiler or a Go JVM backend, but it was really early. I don't remember it working very well at all, and they just kind of fizzled. |
**Filippo Valsorda:** I wonder if you can still do that through either gccgo or Clang backends... |
**Brian Ketelsen:** Well, you can do lots of stuff with llvm and Clang, so... I know that's how GopherJS is getting a lot of things done. |
**Erik St. Martin:** Speaking of gccgo, does anybody know how widely used that is? |
**Brian Ketelsen:** No. |
**Erik St. Martin:** Me neither. It seems to be still maintained, but I haven't really heard much about it or any particular projects using it, so... It would be interesting. |
**Brian Ketelsen:** Maybe Ian knows. Ian Lance Taylor, if you're out there - we need to know who's using gccgo, and where and why. So this is an open invitation to come on the show and talk to us about gccgo. |
**Erik St. Martin:** That's true, we should get him on the show and talk about it. |
**Brian Ketelsen:** That reminds me of an embarrassing moment at the first GopherCon - this is totally an aside... Somebody walked up to me and said they were using gccgo and they had this big problem and they didn't know what to do or how to fix it... So I just walked over to Ian and I said, "Hey, Ian, somebody's got ... |
**Filippo Valsorda:** At the last GopherCon I had a bit of an embarrassing moment when I discovered after the fact that one of the questions that I kind of quickly answered/brushed off at my cgo talk was from Ian... \[laughs\] I felt pretty bad over that... |
**Erik St. Martin:** Who was it -- we were at the speakers' dinner and they were sitting next to Dmitri? |
**Brian Ketelsen:** Oh, shush... We don't need to bring this up. No, no, no, no, no. That was me. |
**Erik St. Martin:** No, no, no, it was one of the other speakers. He was talking about the race detector, and Dmitri was just like, "Thank you!" \[laughter\] Alright, did anybody have any other projects or news they wanna talk about before we wrap this thing up? |
**Brian Ketelsen:** We hit it all. |
**Erik St. Martin:** Alright. |
**Carlisia Thompson:** Good work! |
**Erik St. Martin:** Well, huge thank you to everybody on the show, thanks to all the listeners listening right now. Huge shoutout to our sponsors, StackImpact and Ardan Labs. If you haven't checked them out, please do. We will put links in the show notes. Definitely share this show with friends and colleagues. An easy... |
**Brian Ketelsen:** You know, he probably rushed to finish the gopherize-me thing just before he was gonna be on the show. \[laughter\] |
**Carlisia Thompson:** Good for us! |
**Brian Ketelsen:** Now I understand everything. |
**Filippo Valsorda:** Well, everyone, thank you very much for having me. Last fun fact: in Florence, after GoLab, I was just going around, looking for a place to have lunch... We literally picked a random one and don't I meet Mat Ryer while I'm getting out, sitting at a table just across the room. |
**Carlisia Thompson:** Gophers attract Gophers. |
**Brian Ketelsen:** Wow! |
**Filippo Valsorda:** Yup. Alright, thank you everyone. |
**Brian Ketelsen:** Thank you. |
**Carlisia Thompson:** Thank you, Filippo. Bye! |
**Filippo Valsorda:** Bye! |
• Introduction to Go Time podcast |
• Sponsorship by Stack Impact and Arden Labs' series of Go Training |
• Guest introduction: Filippo Valsorda, Cloudflare employee working on Go projects |
• Hello Gopher project explained: |
• Simplifying the process for non-Go developers at Cloudflare |
• Solving issues with GoPath and repository setup |
• Providing a straightforward way to bootstrap a project without needing to set up GoPath |
• Discussion of common confusions and challenges with GoPath and contributing to repositories |
• The user is happy with the adoption of a tool or feature |
• A user reported an issue that was resolved by referring to documentation |
• Brian and Carly haven't had a chance to try out the tool yet |
• GoPath is mentioned as a solution for setting up development environments in Go |
• It's discussed how GoPath solves one problem but not all, especially for contributing and Git cloning |
• Hello Gopher is introduced as a drop-in replacement that works with normal Go projects |
• Hello Gopher is compatible with existing Go structures and doesn't interfere with colleague's settings |
• The tool is agnostic to the vendoring tool used |
• The speaker discusses the demo "WhoAmI" which uses public SSH keys from GitHub |
• WhoAmI uses the GitHub API to collect and match public keys with their corresponding user profiles |
• The tool logs in users via keyboard-interactive login, even if they don't have any matching public keys |
• It then attempts to find a matching username and surname by cross-referencing the matched keys with a database |
• The speaker runs into issues trying to test the demo on their own machine due to multiple SSH keys being used |
• They discuss potential uses of the tool, including exposing information leakage via SSH login |
• Implementing TLS 1.3 protocol |
• Using CryptoTLS instead of OpenSSL for TLS implementation |
• Cloudflare's deployment of TLS 1.3 stack in Go |
• Fallback system for TLS 1.2 in case of failure |
• Comparison of security and bug tracking between CryptoTLS and OpenSSL |
• Recommendation to use Go's native TLS implementation instead of OpenSSL |
• TLS 1.3 offers improved performance and robustness over TLS 1.2 |
• TLS 1.3 cuts an entire round trip of communication with the server |
• This results in significant latency reduction, especially on mobile networks |
• The Cloudflare crypto team's work includes deploying code to the world and researching secure protocols |
• A talk by Filippo (or George Dunkesley) discussed the black magic of Sego and how to make it tolerable |
• There is a talk on TLS 1.3 given at 33C3, but no published material on the Go part |
• Discussion of an attempt to SSH into an HTTP server, highlighting the differences between protocols |
• Introduction and advertisement for Stack Impact, a performance monitoring service for Go applications |
• Filippo's work on crypto and TLS at Cloudflare and his interest in Caddy |
• The reproducibility of Go binaries, allowing for identical builds across different machines |
• The concept of binary transparency, where builds are logged to prevent backdoors from being hidden |
• The challenges of achieving reproducible builds with other languages and projects, such as Debian |
• Go supports multiple architectures and operating systems |
• The resulting binary would change for different platforms (Windows, Linux, ARM) |
• 32-bit Spark is not supported on a Raspberry Pi |
• Go can run on mainframes and other legacy systems |
• Latency profiling and Camly Store are being discussed in the show document |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.