text
stringlengths
0
2.46k
[3448.12 --> 3449.60] are all the same Go environment.
[3449.60 --> 3452.52] For example, let's say they're learning Go or they're learning Python as their first
[3452.52 --> 3456.98] language, you know, like wouldn't dev containers be amazing in that scenario where it's just
[3456.98 --> 3462.28] like, well, if you have Docker installed and you can, you know, borrow this template, which
[3462.28 --> 3463.00] is pretty easy, right?
[3463.02 --> 3464.42] Like you just copy it down.
[3464.78 --> 3465.14] Wow.
[3465.20 --> 3469.98] That teacher or whoever's leading that class has just got like a star next to their name
[3469.98 --> 3475.22] because wow, they got six machines up running a Go space or a Python space that a kid can
[3475.22 --> 3479.30] play with essentially pretty quickly rather than the whole song and dance.
[3479.58 --> 3480.02] Yeah.
[3480.14 --> 3484.56] I love that you brought that up too, because education is the space that we've really identified
[3484.56 --> 3489.98] too, that these could be super helpful in, especially in some of the more cloud powered
[3489.98 --> 3494.56] or automated tools like Codespaces or other ones of like, I don't even have to like install
[3494.56 --> 3495.28] anything locally.
[3495.28 --> 3498.12] I can just go to the cloud and have everything that I need there.
[3498.50 --> 3502.32] But I think that's an awesome opportunity in education because we've gotten feedback from
[3502.32 --> 3507.82] educators and students alike that, hey, at the beginning of a new semester, I have to spend
[3507.82 --> 3511.26] first few days or weeks just getting everything I need for this class.
[3511.44 --> 3515.46] And if I'm maybe studying computer science, I have a bunch of different dependencies that I
[3515.46 --> 3517.18] need across a bunch of different classes.
[3517.18 --> 3522.52] So like, what if either my professor added a dev container or us as a class, we had some
[3522.52 --> 3524.44] dev container configuration that we could share.
[3524.86 --> 3528.72] So it's like, oh, don't even worry about like, which version of Python do I need for this
[3528.72 --> 3529.70] class or that class?
[3529.78 --> 3530.52] Like, hey, no worries.
[3530.54 --> 3531.52] It's just in the dev container.
[3531.64 --> 3532.24] Go grab it.
[3533.42 --> 3533.82] Yeah.
[3534.02 --> 3535.24] That's music to my ears.
[3535.74 --> 3536.14] For sure.
[3536.38 --> 3541.70] It's also roots from the original GitHub inception, which was permission to mess up.
[3542.30 --> 3544.62] Like this is the ultimate permission just to play, right?
[3544.62 --> 3552.78] Like if, if I'm go curious and this go container is, you know, one dev container dot json away,
[3552.88 --> 3554.84] Jared, as you said before, that's so cool.
[3555.20 --> 3558.28] Like just one dev container dot json away.
[3559.14 --> 3560.06] That's so cool.
[3560.66 --> 3561.52] A semi tangent.
[3561.60 --> 3563.72] I've kind of played with this in my, in a different world.
[3563.80 --> 3567.44] I've been tinkering with prox mox and containers and stuff like that.
[3567.44 --> 3569.74] And I'm doing a lot of like home labby stuff.
[3569.74 --> 3575.70] And like, I've been playing with true NAS and other things more so because prox mox makes it so
[3575.70 --> 3579.28] easy to spin up a brand new Ubuntu image or a Debian image or whatever I want to do.
[3579.70 --> 3582.90] And there's just a cool world out there where it's like the same thing, but in the
[3582.90 --> 3584.92] developer environment space.
[3585.24 --> 3590.92] And, you know, that to me is just like so awesome because you don't have to figure out how do I
[3590.92 --> 3593.72] create a Go environment or a Python environment?
[3594.34 --> 3598.70] I mean, you can, if you're going out your own route in your own bespoke way, but like you had
[3598.70 --> 3601.98] said, for the most part, you've got a lot of templates that get you started or at least spark
[3601.98 --> 3604.38] your curiosity to understand how can this be leveraged?
[3604.72 --> 3606.26] It's just that easy.
[3606.70 --> 3607.36] Yeah, absolutely.
[3607.66 --> 3609.56] That's what we're hoping for to make it just that easy.
[3610.78 --> 3611.80] Jared's just over here laughing.
[3612.10 --> 3612.54] Come on, Jared.
[3612.54 --> 3614.50] Well, Bridget, you turned us into salespeople for you.
[3614.56 --> 3616.38] He's like, it's just that easy.
[3616.96 --> 3617.94] Yeah, I love it.
[3618.02 --> 3620.90] Like within an hour, I'm like, oh, I don't even have to be saying it.
[3621.10 --> 3621.88] What are the pros?
[3622.14 --> 3622.80] We're converted.
[3623.06 --> 3623.64] We're converts.
[3624.00 --> 3624.56] Anything like that.
[3624.70 --> 3625.14] Thank you.
[3625.24 --> 3627.64] Bridget just sits back and lets us get excited about it.
[3627.66 --> 3628.96] She's like, yes, we've got it.
[3629.38 --> 3631.14] This is your adoption strategy, isn't it?
[3631.14 --> 3631.44] It works.
[3632.24 --> 3633.16] This is good.
[3633.96 --> 3634.24] Yeah.
[3634.40 --> 3635.64] You just got to find the right podcast.
[3636.18 --> 3636.28] Right.
[3636.76 --> 3642.28] Let's reel back and do our job of being, you know, good interviewers and say, what's the
[3642.28 --> 3643.54] downside?
[3643.86 --> 3644.78] What's the cons?
[3644.94 --> 3645.94] Where does it struggle?
[3646.58 --> 3649.10] Help us get some balance back into this.
[3649.10 --> 3652.22] We've been, we've been effusive for the last 10 minutes and we need to balance it out.
[3652.34 --> 3656.24] What's, what's maybe left undone or, or painful today?
[3656.38 --> 3657.16] Bridget, help us out.
[3657.62 --> 3662.86] I think that some of the next things we're really thinking about is we've made a lot of
[3662.86 --> 3667.54] changes over the past year from open sourcing the spec in the CLI to now moving to these
[3667.54 --> 3672.66] new contribution models for templates and features and having indices for them and all
[3672.66 --> 3673.50] that kind of stuff.
[3673.86 --> 3678.28] And with that, now that it's like, feels like we have the major building blocks in place
[3678.28 --> 3679.68] with the spec in the CLI.
[3679.68 --> 3683.82] But it's like really getting more user feedback of like, for instance, some of the questions
[3683.82 --> 3685.54] you both have posed of, oh, okay.
[3685.64 --> 3688.54] So it looks like the templates are just referencing an image.
[3688.68 --> 3690.22] Like, is that clear to folks?
[3690.24 --> 3695.70] Because we hosted a previous set of dev container templates or we previously called them definitions
[3695.70 --> 3697.68] and those had Docker files in them.
[3697.74 --> 3701.58] But we thought that as part of like the spec here with some simplification and with these
[3701.58 --> 3705.66] new images that were post publishing more publicly in this images repo.
[3706.16 --> 3707.82] Hey, like, let's just reference an image there.
[3707.82 --> 3711.84] It feels like that might be more straightforward, but that may not be everyone's scenario or
[3711.84 --> 3715.92] expectation going in, especially for people who are already using dev containers and more
[3715.92 --> 3718.00] familiar with the old model or the old rebuild.
[3718.34 --> 3723.80] So I think getting feedback on some of those like key choices that we're starting to make
[3723.80 --> 3728.54] and it's, we're really open to that feedback of, hey, like if this isn't clear to users,