text stringlengths 0 1.49k |
|---|
[180.82 --> 185.92] It was all about the GoPath and the fact that you have to clone this repository in the right |
[185.92 --> 187.38] place in your first system. |
[187.62 --> 193.52] And that's a completely extraneous process to any developer that comes from other languages. |
[193.52 --> 196.38] So that's what Hello Gopher is solving. |
[197.08 --> 197.20] Yeah. |
[197.28 --> 202.26] It's funny because it was yesterday or the day before I had a friend who had a similar |
[202.26 --> 205.28] issue with that kind of like, where do you check out the code to? |
[205.38 --> 209.72] Because most of the time you're used to just pulling it to wherever you happen to store |
[209.72 --> 210.20] your code. |
[210.30 --> 213.50] It doesn't have to be in a specific spot on your hard drive. |
[214.36 --> 218.16] And then the other side of it that gets confusing is how do you contribute back? |
[218.16 --> 220.28] You know, that's a common confusion. |
[220.54 --> 222.52] Like, OK, so I want to commit something. |
[222.66 --> 227.40] So I fork this repo, but now it's not in the right place. |
[227.40 --> 229.28] And how do I change my import path? |
[229.36 --> 235.78] And it's not immediately clear that you could just set your fork as a different remote for |
[235.78 --> 236.92] the Git repository. |
[237.42 --> 242.44] So there is a lot of confusion with that because the paths are explicit that way. |
[243.02 --> 243.18] Yeah. |
[243.18 --> 248.74] A number of times I've seen like PRs that have all the import paths changed to the fork |
[248.74 --> 251.84] and the person being like, oh, yeah, you can remove that. |
[251.90 --> 255.48] I just had to do that to make it work on my machine. |
[256.06 --> 258.74] And every time it's this little, you know, learning process. |
[259.44 --> 263.98] So Hello Gopher is actually meant to like get you through your first PR without needing |
[263.98 --> 265.56] to set up GoPath at all. |
[265.56 --> 273.18] So the project just builds, tests, runs GoFMT, GoInports without any need to set up GoPath. |
[273.72 --> 277.98] So have you had pretty good success at Cloudflare with that, with people being able to just |
[277.98 --> 279.92] grab a project and work on it? |
[280.30 --> 285.66] Yeah, I definitely like shadowed a number of people through the different revisions of |
[285.66 --> 286.10] Hello Gopher. |
[286.38 --> 287.82] It looks like a simple project. |
[288.00 --> 294.34] It's, you know, 110 lines of makefile, but it went through so many changes even before |
[294.34 --> 295.24] the Git history. |
[295.56 --> 298.08] And I like try to smooth over. |
[298.18 --> 302.12] I'm pretty happy about like how people pick it up and use it these days. |
[302.74 --> 308.92] A user at some point like reported an issue and I just like nudged them towards one section |
[308.92 --> 313.22] of the docs and they reported immediately after being like, oh, yes, got it. |
[313.28 --> 313.98] It worked. |
[314.32 --> 315.36] That was awesome. |
[316.18 --> 319.10] That was like, yes, this works moment. |
[320.16 --> 320.96] That's nice. |
[321.48 --> 323.80] Brian, Carly, have you guys had a chance to play with it yet? |
[324.24 --> 324.54] No. |
[324.54 --> 330.00] No, I've been watching the video on the GitHub repository and actually I'm watching it again |
[330.00 --> 330.22] now. |
[330.32 --> 330.94] It's kind of cool. |
[331.50 --> 334.48] I'm surprised that you were able to do this so elegantly. |
[334.48 --> 339.36] I didn't play with it and I actually didn't know about it until today. |
[339.36 --> 345.66] And I wish I had because I helped organize the Gopher meetup in San Diego. |
[346.26 --> 349.90] And at every meeting there is somebody, at least one person who doesn't have the GoPath |
[349.90 --> 350.36] set up. |
[350.46 --> 354.32] And I would have been glad to just point them to this instruction. |
[354.32 --> 361.98] I feel like every language has like that hurdle to get set up when you're not familiar with |
[361.98 --> 362.62] the environment. |
[362.94 --> 367.04] You know, like I did Ruby for a long time and it never really occurred to me how complicated |
[367.04 --> 369.56] it is to set up a Ruby development environment. |
[369.78 --> 370.34] Oh, my gosh. |
[370.68 --> 370.94] Yeah. |
[371.16 --> 372.52] Until you try to help somebody. |
[373.16 --> 373.34] Yeah. |
[373.34 --> 376.10] I had to build a whole Linux live CD for that. |
[376.22 --> 377.90] Like how many steps there are. |
[377.98 --> 383.70] It's like you have to start explaining Bundler and RBMV or what was the other one? |
[384.62 --> 385.06] RVM. |
[385.52 --> 385.72] Yeah. |
[385.84 --> 386.16] RVM. |
[386.32 --> 391.54] And then they have now they have like a Ruby build one where it kind of builds tools in |
[391.54 --> 392.30] your path too. |
[392.44 --> 396.78] But still, you know, it gets confusing having to remember all these things and set them up. |
[396.94 --> 402.26] And, you know, now we have GoPath and we have vendoring and you're downloading projects |
[402.26 --> 403.80] with the vendor stuff. |
[403.80 --> 408.20] So, yeah, it gets confusing and we forget about it because we've been doing it for so long. |
[408.30 --> 412.74] It's just kind of part of what we do until somebody who's not familiar with the environment |
[412.74 --> 414.48] is like, well, how do I set this thing up? |
[415.06 --> 418.28] But with 1.8, we're not going to have this problem anymore, right? |
[418.74 --> 420.36] This is all going to go away. |
[420.84 --> 422.60] This particular problem won't go away. |
[422.78 --> 422.98] No. |
[423.28 --> 426.58] If you're setting it up the first time, unless you want in a specific place. |
[427.16 --> 428.68] You're still going to have a GoPath. |
[428.80 --> 432.68] It will just be automatically set for you if you haven't set it. |
[433.26 --> 438.28] So we'll still have the confusion that new developers get when they still don't understand |
[438.28 --> 440.28] what a GoPath is and why they need to use it. |
[440.80 --> 440.90] Yeah. |
[440.94 --> 442.76] The default GoPath solves one problem. |
[442.76 --> 445.40] And it's that now you can just write GoGet. |
[445.94 --> 451.12] And that is enough as instructions to install something, probably, most of the times. |
[451.56 --> 455.22] But it's definitely not enough for anyone that just wants to Git clone. |
[455.44 --> 459.66] And it's not enough for someone that wants to contribute because they will still have opinions |
[459.66 --> 462.12] about where they want the project to be, et cetera. |
[462.12 --> 469.44] Now, do you require any special project organization or will this work with any project structure? |
[470.18 --> 476.46] So the point of Hello Gopher, also to avoid that Ruby 100 different tools scenario, is that |
[476.46 --> 479.80] it works drop-in on normal GoGetable projects. |
[480.28 --> 482.22] It's not a different build tool. |
[482.22 --> 487.68] It's just something that wraps things and does horrible black magic with sim links that you |
[487.68 --> 494.18] shouldn't look into so that it just has a fake GoPath that points to your repository. |
[494.52 --> 498.28] But it's still the normal Go structure that we're used to. |
[498.28 --> 501.78] It's also completely compatible with anything you already have. |
[501.96 --> 507.12] And it doesn't get on your colleague's toes if they actually have GoPath set up, et cetera. |
[507.74 --> 508.08] Nice. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.