text stringlengths 0 1.82k |
|---|
• Future replacements for current data science tools in the Go language |
• Shift in community towards accepting multiple languages for data science tasks |
• Discussion of various programming languages used in data science, including R, Python, JavaScript, Go, and Java Scala |
• Introduction of Pachyderm as an interesting project for big data workflows |
• Exploration of Go libraries for data science, such as Gonum and Gota |
• Portability of Python libraries to Go for data processing tasks |
• Efficiency of writing custom code in Go versus relying on dependencies |
• Discussion of the "A little copying is better than a little dependency" mindset in Go development |
• Advice on getting started with data science in Go |
• Importance of mindset when approaching data science in Go |
• Resources for learning data science in Go (Peter's resources, Dave Cheney's) |
• Jupyter kernel for Go and interactive data exploration |
• Existing projects that demonstrate data science capabilities in Go (InfluxDB, Pachyderm) |
• Live demo of data science process using only Go at GopherCon |
• Go notebooks and interactivity with Jupyter |
• Brief overview of Jupyter and its ecosystem |
• Jupyter notebook and Go kernel |
• Carlisia's experience setting up Jupyter and using the Go kernel for note-taking and development |
• Discussion of Vim Go and Neovim as tools for improving development workflow |
• Daniel Whitenack mentions Vim Go and Neovim, and thanks Fatih Arslan for his work on these projects |
• Erik St. Martin talks about Nvim and its benefits over regular Vim |
• Promoting GopherCon and encouraging listeners to attend and participate in panels with speakers |
**Erik St. Martin:** It's Go Time! A weekly podcast where we discuss interesting topics around the Go programming language, the community and everything in between. If you currently write Go or aspire to, this is the show for you. |
Welcome back for another episode of Go Time. This is episode number four. Today we'll be talking about Gopher data science and other interesting news and projects we've come across this week. I'm Erik St. Martin and with me is always our other amazing hosts, Brian Ketelsen - say hello, Brian. |
**Brian Ketelsen:** Hello! |
**Erik St. Martin:** And also Carlisia Campos. Say hello, Carlisia. |
**Carlisia Thompson:** Glad to be here, hi! |
**Erik St. Martin:** And for anybody who's already listening, today we're joined by Daniel Whitenack, who is very vested in Gopher data science. He's also going to be speaking at GopherCon this year about it. How are you, Daniel? |
**Daniel Whitenack:** Good, good to be here. |
**Erik St. Martin:** So let's kick this episode off by talking about anything we've kind of run across this weeks in news and just random articles and things. What's everybody got? |
**Brian Ketelsen:** The biggest thing this week is the feature freeze for Go 1.7. It was announced on the Golang-nuts and Golang-dev mailing list. There's a lot of changes in this, with the SSA and compiler changes, so everybody out there needs to download Go 1.7 and compile it, test your programs, because this is a re... |
**Carlisia Thompson:** I saw something about binaries. Is it vendoring binaries? I didn't have a chance to investigate, I was super-interested. Does anybody know? |
**Daniel Whitenack:** Yeah, I think it was binary-only packages, without providing the source. |
**Brian Ketelsen:** Exactly, so you can get a binary on your package now. |
**Carlisia Thompson:** So you can do it both ways? |
**Brian Ketelsen:** Correct. If you want to release a precompiled package that was only a binary with no source, you could do that by giving somebody a URL to a go get, or to use go get. |
**Carlisia Thompson:** Oh, I see what you're saying, gotcha. |
**Erik St. Martin:** Yeah, so kind of more along the lines of like the commercial packages and libraries that you can buy, say, for the Windows side of the world. |
**Carlisia Thompson:** So then if I'm using your package as a binary, I can pop it in my projects and use it as a binary? |
**Brian Ketelsen:** I don't know if it applies to precompiled libraries. I think it was only commands, but it would be interesting to see if it actually applied to the library files, the A files. |
**Erik St. Martin:** I have to look more into that. I briefly saw something about that, and I kind of breezed over it, I've been really busy this week. But there's something like 300 closed tickets for that release. |
**Daniel Whitenack:** Exciting. I'm excited for the compile times. |
**Erik St. Martin:** Yeah, me too. I can wait to get back to 1.4 speeds. |
**Brian Ketelsen:** We're getting closer. It's still slower that 1.4, but we've regained a lot of that lost territory, and that makes everybody happy. |
**Erik St. Martin:** The other interesting thing that I saw this week too was Brad and Andrew's live coding sessions. Did you guys see that? Where they're putting out a callout for people who want live code reviews. |
**Brian Ketelsen:** That's frightening. |
**Carlisia Thompson:** I didn't see that, but that sounds great. |
**Daniel Whitenack:** I didn't see it either, but I would love to participate in that. |
**Carlisia Thompson:** I've seen them doing it in the past, and it's great. |
**Brian Ketelsen:** I don't know... If you didn't have impostor syndrome before, imagine Brad and Andrew tearing up your code. They're both great guys, so don't get me wrong, but that is a tough crowd to please. |
**Erik St. Martin:** I don't know, I think that it would just make my own thoughts of myself come to light. I'd be like, "I knew it. See?" \[laughter\] |
**Brian Ketelsen:** I knew I was a terrible coder. Yeah... GoTimeFM, where we talk about our impostor syndrome for an hour. \[laughter\] There's another big news item this week, and that was Peter Bourgon's article, his update of his Go Best Practices talk from 2014. He updated that to 2016, and there's a lot of really... |
**Daniel Whitenack:** Yeah, I think it's gonna take a while for me to unpack, but I think it's one of those things... You know, I have a bookmark that I'm gonna visit every week, and as I'm implementing different things, I think referencing that and just seeing if I'm doing things in a sane way is gonna be great. |
**Erik St. Martin:** I think that that talk was a favorite, still to this day, from GopherCon 2014. People really loved that talk, so it's fun to see him go back and kind of reflect on his thoughts and to shoot down the things that he thought were the way. Although I don't know whether he fully dismissed any of the con... |
**Brian Ketelsen:** Yeah, something this big takes a long time to internalize all of it. I would love to take this article, mix it with Dave Cheney's error-handling article from a week or two ago, and just put it under my pillow and sleep on it every night, hoping that I could absorb all of that at once. That's be grea... |
**Carlisia Thompson:** I'm holding myself back, as I don't wanna be such a big fan girl, but for people new to the community and to Go, Peter is definitely somebody to absorb. I would say Peter and Dave Cheney are at the top of my list as far as best practices and things I think are best to follow. |
**Daniel Whitenack:** Yeah, I would agree, and I think coming into Go not too long ago, of course you search around different Stack Overflow responses and whatever, and you can really get a mixed bag of ideas about - like Erik said - about error handling or what have you. But going to these resources, I found, gives so... |
**Erik St. Martin:** I'm interested to see some more best practices too, just to kind of compare and contrast, because I think people have different success stories with different things, and especially when it comes to vendoring, that can be a hot topic. We could probably talk for a full episode about vendoring. |
**Brian Ketelsen:** I think we could have an entire GopherCon on vendoring, and still not get any consensus from anybody. \[laughter\] |
**Carlisia Thompson:** Who needs consensus? |
**Brian Ketelsen:** Nobody needs consensus, good point. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.