text stringlengths 0 1.49k |
|---|
**Carlisia Thompson:** But not committing it? Just committing on one machine, or...? |
**Brian Ketelsen:** Yeah, just saving it on one machine, and then it gets synchronized to other machines... And something happened - I don't know, I deleted something somewhere and it ended up wiping out the entire source directory for my Go stuff, and everything that wasn't committed to GitHub got lost, and it made me... |
**Mark Bates:** That's painful. |
**Brian Ketelsen:** It was. I stopped using SyncThing at that point. |
**Mark Bates:** Do these tools all work on your Windows machine, or...? |
**Brian Ketelsen:** Yes, so far all of them do. I wish I could remember what I did. I'm sure it was a user error, and I don't want to speak poorly of SyncThing because lots of people use SyncThing very successfully, so I'll take all of the blame for my user error there, but I haven't used it since. |
**Erik St. Martin:** So basically it's not a SyncThing thing, it's that you're scared you're gonna screw it up again, it's what you're saying...? |
**Brian Ketelsen:** Exactly, I'm positive that I'll do something foolish and lose source code again. I don't wanna do that. |
**Mark Bates:** I do all of my development in Dropbox. |
**Brian Ketelsen:** Dropbox? |
**Erik St. Martin:** I did that early, early on, but I stopped doing it. |
**Mark Bates:** Yeah, I do everything in Dropbox. |
**Carlisia Thompson:** Yeah, I had a bad experience with Dropbox. |
**Brian Ketelsen:** It sounds like everybody's vodka story. \[laughter\] "Yeah, I drank too much Dropbox once. It was bad." |
**Mark Bates:** Yeah, knock on wood... In five or six years I've never had anything bad happen, and almost my entire home folder is in there. |
**Carlisia Thompson:** Just Git commit, you'll be fine. |
**Erik St. Martin:** See, so that's the scary thing about having a hundred percent synchronization over a backup strategy, right? If you destroy the file in one place, you destroy it everywhere. |
**Mark Bates:** See, Dropbox offers history. |
**Erik St. Martin:** It does. |
**Brian Ketelsen:** Well, again... I'm sure it was a user error. PEBKAC. |
So the last awesome tool I found is called Prism, and there's an article on Medium today... Let me copy and paste that URL. |
**Mark Bates:** Is Medium still going today? |
**Brian Ketelsen:** Oh, just for today. |
**Carlisia Thompson:** It's up right now, but who knows...? |
**Brian Ketelsen:** Yeah, who knows...? So Prism is a pretty nifty open source profiling tool for Go code, and the thing that I really like about Prism is that it shows historical diffs over time. So you can run a profile on your app, and it has pretty decent-looking output - better than pprof, obviously - and as you m... |
\[43:57\] It's really neat to show historical changes in your profiling. And it's got a nice interface, it looks really easy to use... I have not yet tried to use it, but it looks pretty nice. So Prism... I don't even remember what company released it, but it looked pretty cool. |
**Erik St. Martin:** Yeah, I haven't played with it myself personally, but I love the aesthetics of it, the comparison against previous versions. And the name is cool too, Prism. And it's inspecting stuff, monitoring stuff... |
**Brian Ketelsen:** Yeah, it sounds like a CIA Black Ops project - Prism. |
**Erik St. Martin:** I wanna say those were kind of the core things this week that we ran across... There was probably some other stuff, but two weeks away is a long time. |
**Brian Ketelsen:** It is. |
**Carlisia Thompson:** And by 'we', we mean Brian. \[laughter\] We're just riding on your back, Brian. |
**Erik St. Martin:** Hey, in my defense, I dropped the Grumpy link in the GoTime FM channel for the hosts a while back (a couple days ago, something like that). |
**Brian Ketelsen:** Only after I saw it, though. It's too late. Nice try. |
**Erik St. Martin:** Can I say that then? |
**Brian Ketelsen:** Yes. |
**Erik St. Martin:** Does that count? I saw all the stuff first; I just was lazy and decided to let you do it. |
**Brian Ketelsen:** Yep, that's fine. Nobody will believe it, though. |
**Erik St. Martin:** Works for me. So let's move on to \#FreeSoftwareFriday. This is the part of the show where we give shout outs to projects and people that make all of our lives easier. Who wants to go first? \[pause\] Nobody? |
**Carlisia Thompson:** I can go first. I wanna give a shout out to this library called Refresh. It sounds very cool, I'm actually gonna start using it. I just found out about it, and guess what? It was written by our guest. |
**Brian Ketelsen:** What? |
**Carlisia Thompson:** Yeah. |
**Mark Bates:** I know. |
**Carlisia Thompson:** So basically, if you're working with a Go project and you run this library, if you change your Go files, you will -- what is it, Mark? Why don't you explain it? I know what it does, I'm just having trouble explaining it. |
**Mark Bates:** It's pretty simple; there are actually a few of these types of libraries out there, but essentially it watches your file system using the fsnotify package, and as your Go files change, or files that you say "I'm watching" change, it will rebuild your Go binary and start it back up again. |
**Brian Ketelsen:** Does that use ionotify under the background? |
**Mark Bates:** Fsnotify. |
**Brian Ketelsen:** Fsnotify, I'm sorry, my bad. Sorry, Nathan. |
**Mark Bates:** It also offers a webhook that you can put into your Go code that will show you in your web browser what error has occurred compiling your app. |
**Brian Ketelsen:** Nice. |
**Carlisia Thompson:** I have something embarrassing to share, but I will because I don't care. I lost half a day one time doing work and checking my work manually, and the changes weren't appearing, and I thought because I was just doing it wrong, and I forgot that I had to rebuild my binary... \[laughter\] Oh my god.... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.