text
stringlengths
0
2.35k
[2099.84 --> 2100.58] I use Minder.
[2101.06 --> 2103.50] You know, it's where you let to dump your actual mind directly.
[2104.64 --> 2105.20] That's cool.
[2105.28 --> 2106.04] Is it text?
[2106.16 --> 2106.64] Is it visual?
[2107.16 --> 2107.96] It's more like a feeling.
[2108.06 --> 2108.54] Just hex.
[2108.74 --> 2111.66] Remember the feeling you used to get when there was somebody being wrong on the internet?
[2111.66 --> 2112.94] It's like that all the time.
[2114.02 --> 2115.22] Is it XML, though?
[2115.50 --> 2118.12] No, you just plug directly into your brain computer interface,
[2118.28 --> 2120.12] and you're just really mad right away.
[2120.30 --> 2120.80] Oh, I love it.
[2120.98 --> 2121.66] Yeah, it's beautiful.
[2121.66 --> 2142.08] This episode is brought to you by our friends at LaunchDarkly,
[2142.28 --> 2144.20] feature management for the modern enterprise,
[2144.54 --> 2146.76] power testing in production at any scale.
[2146.94 --> 2147.78] Here's how it works.
[2147.78 --> 2152.68] LaunchDarkly enables development teams and operation teams to deploy code at any time,
[2152.94 --> 2155.24] even if a feature isn't ready to be released to users.
[2155.60 --> 2158.90] Wrapping code with feature flags gives you the safety to test new features
[2158.90 --> 2163.50] and infrastructure in your production environments without impacting the wrong end users.
[2163.92 --> 2165.20] When you're ready to release more widely,
[2165.50 --> 2168.34] update the flag status and the changes are made instantaneously
[2168.34 --> 2170.28] by the real-time streaming architecture.
[2170.70 --> 2174.96] Eliminate risk, deliver value, get started for free today at LaunchDarkly.com.
[2175.30 --> 2176.98] Again, LaunchDarkly.com.
[2176.98 --> 2179.16] And by our friends at Retool.
[2179.46 --> 2183.22] Retool helps teams focus on product development and customer value,
[2183.50 --> 2185.96] not building and maintaining internal tools.
[2186.48 --> 2189.34] It's a low-code platform built specifically for developers.
[2189.92 --> 2193.06] No more UI libraries, no more hacking together data sources,
[2193.48 --> 2195.76] and no more worrying about access controls.
[2196.32 --> 2199.60] Start shipping internal apps that move your business forward in minutes
[2199.60 --> 2204.22] with basically zero uptime, reliability, or maintenance burden on your team.
[2204.22 --> 2206.28] Some of the best teams out there trust Retool.
[2206.40 --> 2213.58] Brex, Coinbase, Plaid, DoorDash, LegalGenius, Amazon, Allbirds, Peloton, and so many more.
[2213.92 --> 2218.66] The developers at these teams trust Retool as their platform to build their internal tools,
[2218.82 --> 2220.10] and that means you can too.
[2220.10 --> 2223.46] It's free to try, so head to retool.com slash changelog.
[2223.58 --> 2227.18] Again, retool.com slash changelog.
[2227.18 --> 2252.04] Rage Cage talked about wanting more module features.
[2252.04 --> 2256.78] They're really like workspaces that came in 118, but what about that?
[2256.92 --> 2259.08] Like, do you think Go is doing all right with modules?
[2259.28 --> 2260.94] Do you think we need to do better?
[2261.10 --> 2262.80] Are there things in particular we should look at?
[2263.04 --> 2264.26] Oh, modules and packages.
[2264.58 --> 2265.92] Oh, that was a thing.
[2266.02 --> 2268.98] Like, right in the beginning, everyone was complaining back in those days.
[2269.06 --> 2272.52] They're like, you know, I just want to pull in code from anywhere, do whatever I want.
[2272.90 --> 2275.08] You know, they were looking at JavaScript with envy.
[2275.34 --> 2278.48] That was before JavaScript was responsible for all those forest fires.
[2278.48 --> 2280.44] I knew that.
[2281.40 --> 2283.82] It was just too many cursors spinning all at once.
[2283.92 --> 2285.96] Suddenly, boom, caught on fire.
[2286.24 --> 2286.70] It was terrible.
[2286.92 --> 2288.64] Yeah, it turns out computers can sweat.
[2289.08 --> 2289.30] Yeah.
[2289.42 --> 2291.66] And then they set on fire and burn down forests.
[2291.76 --> 2292.64] Well, that's horrific.
[2292.82 --> 2294.48] I always knew we couldn't trust JavaScript.
[2294.88 --> 2295.36] I mean, literally.
[2295.98 --> 2301.84] But yeah, managing packages and then rando packages showing up just because, like,
[2302.04 --> 2306.48] somebody got mad on the internet one day and they decided their package was going to turn hostile
[2306.48 --> 2310.18] and then somebody else was like, hey, come with me.
[2310.28 --> 2311.64] Like, here, have a bunch of drinks.
[2311.64 --> 2314.64] And then, like, hey, is that your 2FA device?
[2314.82 --> 2318.82] And wouldn't it be funny if somebody put this code in your repo and, like, you wake up in the morning
[2318.82 --> 2321.72] and, like, there's people looking for you in helicopters?
[2322.44 --> 2325.76] That never would have happened if they'd only address some of the security.
[2326.02 --> 2326.84] That was not me.
[2327.24 --> 2329.86] That was somebody else who looked just like me and who got away.
[2330.06 --> 2330.10] Yeah.
[2330.14 --> 2330.88] But that was not me.
[2330.98 --> 2331.30] No, no.
[2331.52 --> 2331.70] Yeah.
[2331.70 --> 2339.76] Anyway, package management and modules and module protection and also being able to consume code
[2339.76 --> 2344.50] from other languages and not have to rewrite everything in a single language, you know,
[2344.58 --> 2349.60] that really would have made a big difference because if we had only had that, then there
[2349.60 --> 2355.04] would have been the biopharmaceutical rebellion that occurred in 2039.
[2355.42 --> 2359.60] That was a real problem because all of a sudden you couldn't get the pills you needed the program
[2359.60 --> 2360.06] anymore.
[2360.06 --> 2362.82] It was all biointerfaces at that point.
[2363.04 --> 2368.18] You know, Windows 9000 came out and it only supported the biological interface.
[2368.56 --> 2368.66] Yeah.
[2368.92 --> 2372.52] You know, I guess it was like what came after biometric was just plugged directly in.
[2373.06 --> 2373.56] I don't know.
[2373.72 --> 2373.90] Yeah.
[2374.06 --> 2375.68] Just get clippy straight in your brain.
[2376.16 --> 2380.90] We could have avoided a lot of that if we'd only done proper security management of packages
[2380.90 --> 2382.72] and if we'd only taken all that seriously.
[2383.06 --> 2383.70] Mm-hmm.
[2384.16 --> 2385.22] That is important.
[2385.22 --> 2392.00] Another thing that is interesting, Roberto Guerra is asking if, or saying we should just
[2392.00 --> 2395.54] not implement JS like promises and so on, and it will be great.
[2396.06 --> 2396.36] Well.
[2396.60 --> 2397.66] Is it looking promising?
[2398.06 --> 2403.88] It's going back to that semantic warfare against the concepts of the Go programming language.
[2403.88 --> 2406.74] Like, we don't promise you.
[2407.02 --> 2407.30] Okay?