text stringlengths 0 1.8k |
|---|
[2467.08 --> 2468.76] There is tilt.dev as well. |
[2469.18 --> 2470.74] There's a couple like that. |
[2470.94 --> 2475.34] But what I really want to do, having listened to the GitHub code spaces episode on changelog, |
[2475.38 --> 2476.10] I forget the number. |
[2476.10 --> 2481.36] I, like, tweeted Corey, like, hey, we should talk. |
[2481.44 --> 2482.46] I said, yeah, sure, email me. |
[2482.54 --> 2484.70] And I didn't have time to follow up on that email. |
[2485.20 --> 2492.30] But I really want to do that because I see the potential of GitHub code spaces, but I would |
[2492.30 --> 2493.54] use it slightly differently. |
[2494.10 --> 2497.42] Now, we're always up for partners, aren't we, Adam? |
[2497.42 --> 2502.86] So, if GitHub wants to sponsor changelog with the GitHub code spaces, we would be more than |
[2502.86 --> 2505.34] happy to use it and help it improve. |
[2506.12 --> 2509.24] But my first go-to would be, is what I know, right? |
[2509.32 --> 2514.18] Like, bare metal server somewhere or Linodes or wherever, spin them up. |
[2514.78 --> 2516.10] And that's where crossplane comes in. |
[2516.14 --> 2518.98] There's, like, a couple of things happening in the background that will start coming together. |
[2519.36 --> 2522.96] There's a Equinix Metal episode with Zach coming. |
[2522.96 --> 2526.00] I think, 30, 29, I think. |
[2526.18 --> 2527.62] Actually, it came out. |
[2527.70 --> 2530.56] By the time you're listening to it, it came out, the episode with Zach. |
[2531.10 --> 2536.52] So, there's, like, a couple of things coming together which make me really excited and which, |
[2536.72 --> 2541.38] I think, setting anything locally for development, it is a time sink. |
[2542.46 --> 2548.08] And you should have environments which are pre-built for development in an automated way. |
[2548.84 --> 2550.72] And just click a button and you have it. |
[2550.72 --> 2554.70] And when you're finished with it, you take it down and you don't have to worry about it. |
[2555.20 --> 2568.10] You don't have to worry about upgrading PostgreSQL or are you running the right version of Erlang or should you install Docker or put up with Docker desktop updates which have been getting greedy and annoying in recent months, which is one of the reasons why I uninstalled it. |
[2568.10 --> 2572.78] And my main issue has always been I manage homebrew. |
[2573.00 --> 2574.52] I upgrade some things in there. |
[2575.04 --> 2578.50] I don't want to, you know, specifically upgrade particular things. |
[2578.62 --> 2582.88] So, I say upgrade all essentially or just brew upgrade after update. |
[2583.34 --> 2587.44] And next thing you know, Postgres is updated to the latest and my Postgres is broken. |
[2588.00 --> 2588.08] Exactly. |
[2588.32 --> 2589.58] And that was always the culprit. |
[2589.58 --> 2594.34] And then a couple times it was Erlang and that kind of thing. |
[2594.70 --> 2606.48] So, yeah, because my local hackery things that aren't really connected to a dev environment shouldn't overlap with my actual dev environment for the application. |
[2606.48 --> 2609.92] So, I'm kind of in that weird space where it's like my truck. |
[2610.02 --> 2612.22] I have a gas guzzling Ford F-150. |
[2612.68 --> 2616.34] I love the new EV F-150, the lightning coming out. |
[2616.80 --> 2620.64] I want to buy a new truck sometime soon because I'm due. |
[2620.74 --> 2622.12] It's like seven years old. |
[2622.90 --> 2626.12] But I don't want to buy a gas vehicle. |
[2626.28 --> 2627.66] I want to buy an electric vehicle. |
[2627.90 --> 2629.96] So, I don't want to spin up my own dev environment. |
[2629.96 --> 2637.66] I want to use code spaces or some prescribed dev space that I don't have to worry about. |
[2637.72 --> 2640.94] That's always just fresh because I'm me. |
[2641.08 --> 2642.02] My identity is me. |
[2642.34 --> 2649.20] You know, my trustworthiness or the application should or our config should so I can get access to a certain database. |
[2649.38 --> 2651.68] Maybe a drive-by contributor shouldn't get access to. |
[2652.24 --> 2653.10] That kind of thing. |
[2653.42 --> 2654.92] So, and even drive-by contributions. |
[2655.22 --> 2657.16] Like, those are harder to do probably. |
[2657.16 --> 2661.12] Maybe through .dev is somewhat easy if it's a typo or something like that. |
[2661.26 --> 2665.20] But if it's a contribution, I think it's much easier for us. |
[2666.14 --> 2670.14] So, I'm thinking of the GitHub code spaces experience. |
[2670.84 --> 2675.04] But maybe not necessarily running on Azure as it is today. |
[2675.54 --> 2679.86] But I'm not suggesting that we should all set up some bare metal servers. |
[2680.30 --> 2680.80] No way. |
[2681.78 --> 2684.62] It's an approach that our contributors should be able to use as well. |
[2684.74 --> 2685.50] And you're right. |
[2685.58 --> 2686.78] Identity should be baked in. |
[2687.16 --> 2688.16] So, our... |
[2688.84 --> 2689.96] But that's like the long term. |
[2690.22 --> 2690.88] So, short term. |
[2690.98 --> 2692.28] I think you want a short term. |
[2692.48 --> 2695.88] The short term answer is use your old machine. |
[2696.82 --> 2702.98] I would say short term answer would be can we get set up on code spaces in their current blessed way? |
[2702.98 --> 2710.42] And hope for a future where they have a more infinitely configurable version that's for the ways you want to use it. |
[2710.46 --> 2714.94] So, I'd say let's re-engage with Corey and GitHub on that front. |
[2715.04 --> 2715.58] I know they're willing. |
[2715.70 --> 2716.64] We've talked to them recently. |
[2716.90 --> 2717.88] So, we know they're willing. |
[2718.56 --> 2719.88] That gate has not closed. |
[2719.88 --> 2721.84] They want us to be on code spaces. |
[2722.34 --> 2722.66] Amazing. |
[2722.80 --> 2723.68] And leverage it that way. |
[2723.78 --> 2726.22] So, I say let's use it the way they want us to use it currently. |
[2727.34 --> 2728.16] Get going that way. |
[2728.34 --> 2731.94] And then whenever it needs to scale different ways than it can. |
[2732.30 --> 2735.28] Or you can use Gitpod to do it your own way with Equinix Metal. |
[2735.28 --> 2737.70] Because that's what Gitpod does, right? |
[2737.78 --> 2738.92] Like Gitpod lets you be anywhere. |
[2738.98 --> 2739.52] They're agnostic. |
[2739.78 --> 2744.58] Whereas code spaces is simply GitHub, simply Azure infrastructure. |
[2745.66 --> 2750.92] So, I'm happy if the changelog org would have this capability. |
[2751.30 --> 2757.28] If GitHub code spaces was part of the changelog org and we could use it out of the box, I think that would be amazing, right? |
[2757.32 --> 2764.44] So, if we can contribute to that and we can make sure that anyone wanting to contribute to the changelog app, we could get that working. |
[2764.44 --> 2767.14] Very well with code spaces, which currently isn't. |
[2768.04 --> 2768.84] That, you're right. |
[2768.90 --> 2770.52] That is a good short-term solution. |
[2770.76 --> 2774.18] So, I think you just gave me a Christmas gift. |
[2774.18 --> 2774.58] I'm not going to set it up locally. |
[2774.68 --> 2775.36] I'll wait. |
[2776.30 --> 2779.46] I'm going to wait for my Christmas gift, which is code spaces wrapped in a bow. |
[2780.16 --> 2785.58] The challenge with this path being short-term is that Gerhard is the most organized podcaster in the universe. |
[2785.58 --> 2787.90] And he's scheduling into March and April. |
[2789.88 --> 2790.24] I know. |
[2790.36 --> 2791.70] So, that doesn't sound very short-term to me. |
[2792.04 --> 2792.84] I'll need to make room. |
[2792.84 --> 2796.12] I'll need to, like, I don't know, someone cancel an interview, maybe? |
[2796.74 --> 2797.78] Well, here's what can happen. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.