Datasets:
willtheorangeguy
/
2023-Changelog-Interviews-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
2.46k
[1900.16 --> 1903.22] And now all of a sudden you can run that same environment in code spaces.
[1903.22 --> 1912.50] You can get the VS Code extras as well as hopefully as time passes other tooling that adopts this spec.
[1913.24 --> 1918.94] So you're just you're really just a dev container JSON away from opening up that environment to lots more people.
[1919.50 --> 1920.48] Yeah, I like that statement.
[1920.60 --> 1922.08] You're a dev container JSON away.
[1922.38 --> 1924.10] You can use that as a tagline.
[1924.76 --> 1925.42] Oh, yeah.
[1925.82 --> 1926.44] I like that, too.
[1926.54 --> 1930.26] And you can even add you can even add more stuff to your dev container JSON.
[1930.26 --> 1936.94] So I was mentioning like, oh, what if I'm thinking I really just need Python in this project?
[1937.14 --> 1938.64] And like, how should I add it?
[1938.72 --> 1946.18] I could install it in the command line, but then either I have to install it locally or if I install it in the command line in my container, it'll get lost eventually.
[1946.18 --> 1950.50] If I kill this container, should I install it in the Docker file or somewhere else?
[1950.98 --> 1953.50] So we have this concept called dev container features.
[1953.50 --> 1964.06] So that's the steps that VS Code or code spaces or other tools can guide you through via checkboxes of, hey, here's a list of features and maybe just want to install one of them.
[1964.16 --> 1967.82] Maybe you want to install a bunch of them and then it'll list those in your dev container JSON.
[1968.60 --> 1974.80] And even if you're not using tooling like VS Code, you can just add those to your dev container JSON via a features property.
[1974.80 --> 1982.62] So you can say features and then name whatever feature you want to use and could be one you create or one that the community or someone in your company created.
[1982.88 --> 1986.44] And we have a list that community members contribute a feature.
[1986.60 --> 1991.00] So that way it's like, hey, I wrote this really awesome feature for something I work on or something that I use.
[1991.02 --> 1992.34] And I think other people want to use it.
[1992.64 --> 1994.00] You can add it to the index, too.
[1995.16 --> 1996.68] So how far do you go with that?
[1996.68 --> 2001.54] Because I expect, you know, we have so many different ways of specifying, you know, like editor config.
[2002.42 --> 2004.06] Then you got your VS Code config.
[2004.26 --> 2005.26] Maybe you got your Vim config.
[2005.44 --> 2006.82] Maybe you have your git ignore.
[2007.66 --> 2009.30] Of course, that's just a file that's in your repo.
[2009.42 --> 2014.86] But there's just so many different ways that we specify what how to configure our environments.
[2014.86 --> 2024.48] And some of those we want to be global across the project, linters, et cetera, style rules, maybe requirements for documentation.
[2024.48 --> 2026.74] I don't know, there's a thousand different things you can think of.
[2026.98 --> 2029.52] Some of those things are like personalized to the developer.
[2029.74 --> 2032.06] And then other things are like, no, this is the whole project.
[2032.20 --> 2033.40] What do you guys have found?
[2033.88 --> 2040.18] You probably have more experience with devcontainer.json files than anybody that are like smart things that people are doing to share.
[2040.56 --> 2043.72] And like, hey, go ahead and put your editor config right here in your dev container.
[2043.72 --> 2046.74] Or no, that should be a thing that lives somewhere else.
[2047.12 --> 2047.64] What are you finding?
[2047.64 --> 2056.62] I think the way you put it of is this something that the project really needs or is this something that I just like using or that I need is really a helpful distinction.
[2057.14 --> 2066.70] So I think if it's something that's super specific, like, hey, I like this editor theme or I like my editor sidebar configured this way or this specific editor setting.
[2066.70 --> 2074.22] If it's just a dev container that you're using for your own personal projects, then totally put UI and very specific things in it.
[2074.62 --> 2080.88] But if it feels like, hey, like probably not everyone is going to love the same VS code theme that I do.
[2081.00 --> 2087.50] It's like, OK, I can probably maybe not put that in a dev container that I'm sharing with my whole team or the open source community on this project.
[2087.50 --> 2102.92] So thinking about like, hey, if this project really needs this language or if maybe this linting tool is really helpful or maybe there are certain editor extensions like language support extensions like a Python or Java or C++ language extension for an editor.
[2103.44 --> 2110.60] Those are probably really helpful additions where, yeah, maybe for some development you wouldn't necessarily need it, but it's going to make the development experience a lot better.
[2110.60 --> 2116.48] And people aren't probably going to like strongly disagree of, no, I think my development experience is way worse than them.
[2116.60 --> 2126.22] Then I think adding those kinds of things in that feel like will be generally beneficial to open source community or the other teammates that you have on your project are great things to add.
[2126.32 --> 2127.58] And there's so many things.
[2127.58 --> 2129.64] So it can definitely be a lot of different options.
[2129.64 --> 2135.34] But just think about how generally applicable they are, I think, is the really helpful first or fundamental step there.
[2135.98 --> 2138.86] Is there room for a .local file for that in that case?
[2138.86 --> 2142.84] So maybe Jared and I, you know, we this moves forward and we keep loving it.
[2142.88 --> 2145.84] And there's a dev container.json in our repo.
[2145.98 --> 2150.50] But let's say I like a special flavor of something whenever I spin up my personalized container.
[2150.58 --> 2152.58] Can I have a dev container.local?
[2152.58 --> 2158.38] Is that a bad idea to have sort of a localized version where it's like, here's the dev container and here's what it does normally.
[2158.50 --> 2162.32] But after all that's done, give me this, this and this because I'm Adam.
[2162.72 --> 2164.68] Yeah, there's a few different ways you can handle it.
[2164.78 --> 2168.10] So depending on the editor environment you use.
[2168.10 --> 2170.06] So let's say you're using VS Code.
[2170.30 --> 2176.12] There's certain specific settings you may be able to take in your editor where then you don't even need to set certain things in your dev container.
[2176.12 --> 2179.40] Like VS Code has extensions to always install.
[2179.56 --> 2188.06] So you could like set a list of extensions that you always want there, which could include language extensions, but also include theming or other specific UI or key bindings or things like that.
[2188.06 --> 2192.18] But then thinking about other editors or if you don't want to use those kinds of extensions.
[2192.18 --> 2193.42] Think like it depends.
[2193.54 --> 2204.66] Like there could be, you could actually have multiple dev container jasons in a project and then you can, depending on how the supporting tool implements it, they can guide you for, hey, which one do you want to use right now when you're working on it?
[2204.66 --> 2207.34] So maybe you could have your own version that either.
[2207.42 --> 2213.24] Yeah, maybe you're not checking into source code if you don't want to confuse other people or that's maybe on your own branch that you have a few.
[2213.24 --> 2217.64] So that way you can kind of have it of, hey, like I specifically need this for this scenario.
[2217.78 --> 2221.62] So I'm going to have this kind of dev container here, but then I need this other kind of scenario.
[2221.72 --> 2223.04] So I'll have a secondary one.
[2223.42 --> 2229.70] It can also be helpful for maybe if you're working on a monorepo that has different dependencies for different sub parts of the project.
[2229.82 --> 2236.32] Then you can have multiple dev container jasons there depending on what you're specifically working on or what some of your other teammates are working on.
[2237.20 --> 2237.24] Interesting.
[2237.90 --> 2239.08] Keep my local flavors.
[2239.70 --> 2240.92] I like my local flavors, you know.
[2241.00 --> 2241.98] Gotta keep the local flavors.
[2241.98 --> 2242.94] You're special, man.
[2243.24 --> 2244.72] Keep it special.
[2245.46 --> 2254.06] So when it comes to adoption, I'm Googling around frantically as we talk, like looking like, okay, is the Vim community trying to do some of this?
[2254.14 --> 2256.74] Is the Emacs community trying to do stuff?
[2256.78 --> 2257.68] Some people are just switching.
[2257.94 --> 2258.92] They're just switching to VS Code.
[2259.40 --> 2265.76] Other people are like, you know, here's an open source implementation of VS Code's dev container API.
[2266.98 --> 2271.84] Here's a NeoVim thing that does some stuff with dev container.
[2271.84 --> 2280.04] So it seems like they're out there, but they're not like established, you know, 30 people supporting this one plugin, etc.
[2280.96 --> 2287.56] What do you think it's going to take to get more people on board and doing this and maybe even contributing to the spec?
[2287.56 --> 2291.34] So you kind of have like the editor side, but then you also have like the cloud provider side.
[2292.12 --> 2295.14] And you have two implementations, VS Code and Codespaces.
[2295.28 --> 2301.94] But on both sides, you have like the open source, like Vim, Emacs, you know, integrated into small projects like Sublime Text.
[2301.94 --> 2304.66] And then you have like Codespaces, Gitpod.
[2304.78 --> 2305.70] I'm sure there's other ones.
[2307.06 --> 2307.46] StackBlitz.
[2307.60 --> 2312.70] Like there's a lot of cloud IDE things or, you know, web dev things in the cloud.
[2312.94 --> 2317.52] And I'm just curious what adoption looks like or if there's a clear path to that.
[2317.96 --> 2324.34] I just wonder as an author of a spec what it feels like to like put a spec out there and hope that people use it, you know?
[2324.34 --> 2334.14] Yeah, when we first were announcing, hey, we're working on this spec and we open source this CLI, we announced it on, for instance, the VS Code blog or Codespaces channels too.
[2334.32 --> 2341.52] But we wanted to emphasize, hey, like even if you're finding out about it on the VS Code blog or something, the whole point is it's not just VS Code.
[2342.06 --> 2350.36] So I think like having that in our messaging has been really key because I think that since dev containers for a while were just a VS Code and a Codespaces thing,
[2350.36 --> 2357.50] some folks still totally understandably think, hey, like, well, if I'm not using those tools, I don't need to add a dev container to my project.