text
stringlengths
0
2.46k
**Jerod Santo:** Right. Let's reel back and do our job of being good interviewers and say "What's the downside?" What's the cons? Where does it struggle? Help us get some balance back into this. We've been effusive for the last ten minutes, and we need to balance it out. What's maybe left undone, or painful today, Brig...
**Brigit Murtaugh:** I think that some of the next things we're really thinking about is - we've made a lot of changes over the past year, from open sourcing the spec, and the CLI, to now moving to these new contribution models for templates, and features, and having indices for them, and all that kind of stuff... And ...
\[01:01:59.11\] So I think getting feedback on some of those key choices that we're starting to make... We're really open to that feedback of "Hey, if this isn't clear to users, we want to make it a good experience." So we don't want to say "Hey, well, too bad. We thought this was clearest and simplest, so you need to ...
And then - yeah, I think it's cool too seeing the other kinds of like templates and features that folks contribute. For instance, is the contribution process clear for how I would publish? And is it clear that "Hey, I could totally choose to publish this for the whole community, or I could also leave this private just ...
**Adam Stacoviak:** So this Go template we're looking at, that's been the example we've used here... So on line six, it references an image, what Jerod mentioned before... It's an mcr.microsoft.com/ whatever URL, and it's an image. So are you saying that -- because one line above that it says "...or use a Docker file o...
**Brigit Murtaugh:** Correct, yeah. And then if you go actually to the github.com/devcontainers/images, then you can see what's contained in that Go image. And you'll see "Okay, there's the actual Docker file." So ultimately, there is one; we're just saying, "Hey, maybe it'll be clearer, or less cluttery if we don't ha...
And we also added that comment that you saw there in line five, "...or use a Docker file or Docker Compose", after we'd gotten some feedback of "Hey, how can I use a Docker file?" Or "Hey, I used to know there were Docker files in your templates, but I'm not seeing them anymore." So it's cool that you saw that comment ...
**Adam Stacoviak:** Yeah. Magic is good once you've -- it's a graduate-into. Magic is good, I guess, out the gate, but for the most part, your kind of primary target audience, at least right now, wants to know all the lines. "Let me compose that Docker file for myself. Or at least tell me --" Maybe there's two variants...
**Jerod Santo:** \[01:05:37.29\] Anything left unsaid, Brigit? Anything you've been waiting for us to ask you, and we just haven't got around to it, because we're adults? Or have we covered it all?
**Brigit Murtaugh:** We covered all the key parts, from - yeah, talking about what containers are, the open spec, of you getting excited about it and becoming endorsers for us here... \[laughter\] So we've really come full circle.
**Jerod Santo:** I'm gonna put these sound bites on the homepage, and really get people using it.
**Adam Stacoviak:** Yeah, for sure. What's a good first step, if we're giving the audience -- maybe they've started out like us, apprehensive at first, and curious, and learning, and asking questions, and now we're sales folks for the Dev Containers spec now (that's Jerod and I), what about our listeners? So if they're...
**Brigit Murtaugh:** Yeah, I would say in an editor environment of your choosing... We talked about VS Code and Codespaces a lot, so those are great ones to start out with... Just try out adding a dev container, and building within it, and seeing "Hey, okay, how does my interface look compared to what I'm used to local...
Once you get up and running with it, just a couple of steps or commands there, it should hopefully be pretty straightforward, and then from there you can become even more productive in them. So I recommend checking out - with containers.dev you can kind of get an overview of the things that we talked about today, and t...
**Adam Stacoviak:** Yeah, I messed up there. I said devcontainers.dev. Sorry about that.
**Brigit Murtaugh:** No worries.
**Adam Stacoviak:** Containers.dev, for posterity and clarification's sake. Containers.dev... Just kidding. I had to say it real loud... \[laughter\]
**Brigit Murtaugh:** Say it five times real fast.
**Adam Stacoviak:** Ah...! Maintainer, maintainer, maintainer. Brigit, it's been awesome. Thank you so much for joining us and taking us into this new world. We're going to explore it a bit ourselves, and encourage those who we see to do so as well. Thank you for coming on the show. We appreciate you.
**Jerod Santo:** Yeah, totally.
**Brigit Murtaugh:** It sounds great. Thank you so much.