WEBVTT Kind: captions Language: en 00:00:00.880 --> 00:00:03.990 align:start position:0% Hey<00:00:01.199> guys,<00:00:01.439> it's<00:00:01.600> your<00:00:01.760> boy<00:00:02.000> Zach. 00:00:03.990 --> 00:00:04.000 align:start position:0% Hey guys, it's your boy Zach. 00:00:04.000 --> 00:00:07.430 align:start position:0% Hey guys, it's your boy Zach. Um,<00:00:04.880> I<00:00:05.200> am<00:00:05.520> hanging<00:00:05.839> out<00:00:06.240> by<00:00:06.480> a<00:00:06.720> river<00:00:06.960> again. 00:00:07.430 --> 00:00:07.440 align:start position:0% Um, I am hanging out by a river again. 00:00:07.440 --> 00:00:09.910 align:start position:0% Um, I am hanging out by a river again. As<00:00:07.600> you<00:00:07.759> can<00:00:07.919> see,<00:00:08.960> I<00:00:09.200> had<00:00:09.360> to<00:00:09.519> wait<00:00:09.679> for<00:00:09.760> a 00:00:09.910 --> 00:00:09.920 align:start position:0% As you can see, I had to wait for a 00:00:09.920 --> 00:00:12.709 align:start position:0% As you can see, I had to wait for a freight<00:00:10.240> train<00:00:10.480> to<00:00:10.639> pass.<00:00:11.280> There's<00:00:11.519> a<00:00:12.480> train 00:00:12.709 --> 00:00:12.719 align:start position:0% freight train to pass. There's a train 00:00:12.719 --> 00:00:14.310 align:start position:0% freight train to pass. There's a train that<00:00:12.880> passes<00:00:13.280> on<00:00:13.440> the<00:00:13.519> other<00:00:13.679> side<00:00:13.840> there<00:00:14.080> a 00:00:14.310 --> 00:00:14.320 align:start position:0% that passes on the other side there a 00:00:14.320 --> 00:00:16.230 align:start position:0% that passes on the other side there a lot. 00:00:16.230 --> 00:00:16.240 align:start position:0% lot. 00:00:16.240 --> 00:00:19.349 align:start position:0% lot. Um,<00:00:17.119> but<00:00:17.359> you'll<00:00:17.680> still<00:00:17.840> hear<00:00:18.720> construction 00:00:19.349 --> 00:00:19.359 align:start position:0% Um, but you'll still hear construction 00:00:19.359 --> 00:00:23.189 align:start position:0% Um, but you'll still hear construction noises<00:00:19.920> and<00:00:21.359> the<00:00:21.680> geese<00:00:22.320> probably<00:00:22.960> cuz 00:00:23.189 --> 00:00:23.199 align:start position:0% noises and the geese probably cuz 00:00:23.199 --> 00:00:25.349 align:start position:0% noises and the geese probably cuz they're<00:00:23.439> hanging<00:00:23.680> out<00:00:23.920> down<00:00:24.160> there. 00:00:25.349 --> 00:00:25.359 align:start position:0% they're hanging out down there. 00:00:25.359 --> 00:00:27.670 align:start position:0% they're hanging out down there. Um, 00:00:27.670 --> 00:00:27.680 align:start position:0% Um, 00:00:27.680 --> 00:00:31.349 align:start position:0% Um, so,<00:00:29.119> uh,<00:00:29.439> yeah,<00:00:29.840> Bun<00:00:30.400> merged<00:00:30.880> their<00:00:31.119> big 00:00:31.349 --> 00:00:31.359 align:start position:0% so, uh, yeah, Bun merged their big 00:00:31.359 --> 00:00:36.150 align:start position:0% so, uh, yeah, Bun merged their big rewrite<00:00:32.640> today<00:00:33.520> from<00:00:33.760> Zigg<00:00:34.079> to<00:00:34.320> Rust.<00:00:35.760> And<00:00:35.920> I 00:00:36.150 --> 00:00:36.160 align:start position:0% rewrite today from Zigg to Rust. And I 00:00:36.160 --> 00:00:38.229 align:start position:0% rewrite today from Zigg to Rust. And I realized<00:00:36.480> this<00:00:36.719> is<00:00:36.880> a<00:00:37.120> bigger<00:00:37.520> story<00:00:37.760> than<00:00:38.000> I 00:00:38.229 --> 00:00:38.239 align:start position:0% realized this is a bigger story than I 00:00:38.239 --> 00:00:40.389 align:start position:0% realized this is a bigger story than I thought<00:00:38.320> it<00:00:38.559> was.<00:00:39.040> This<00:00:39.280> is,<00:00:39.600> I<00:00:39.920> think,<00:00:40.160> the 00:00:40.389 --> 00:00:40.399 align:start position:0% thought it was. This is, I think, the 00:00:40.399 --> 00:00:41.910 align:start position:0% thought it was. This is, I think, the first 00:00:41.910 --> 00:00:41.920 align:start position:0% first 00:00:41.920 --> 00:00:44.389 align:start position:0% first really<00:00:42.320> public<00:00:42.719> example<00:00:43.200> we<00:00:43.440> have<00:00:43.600> of<00:00:43.840> a<00:00:44.079> large 00:00:44.389 --> 00:00:44.399 align:start position:0% really public example we have of a large 00:00:44.399 --> 00:00:46.790 align:start position:0% really public example we have of a large scale<00:00:45.040> software<00:00:45.520> project<00:00:46.160> completely 00:00:46.790 --> 00:00:46.800 align:start position:0% scale software project completely 00:00:46.800 --> 00:00:48.310 align:start position:0% scale software project completely transitioning 00:00:48.310 --> 00:00:48.320 align:start position:0% transitioning 00:00:48.320 --> 00:00:52.150 align:start position:0% transitioning to<00:00:49.760> agentic<00:00:50.320> coding. 00:00:52.150 --> 00:00:52.160 align:start position:0% to agentic coding. 00:00:52.160 --> 00:00:54.069 align:start position:0% to agentic coding. you<00:00:52.399> know<00:00:52.559> the<00:00:52.719> the<00:00:52.879> the<00:00:53.520> initially<00:00:53.920> they 00:00:54.069 --> 00:00:54.079 align:start position:0% you know the the the initially they 00:00:54.079 --> 00:00:56.389 align:start position:0% you know the the the initially they wrote<00:00:54.239> it<00:00:54.399> in<00:00:54.559> Zigg<00:00:54.879> and<00:00:55.520> and<00:00:55.920> of<00:00:56.079> course<00:00:56.239> in 00:00:56.389 --> 00:00:56.399 align:start position:0% wrote it in Zigg and and of course in 00:00:56.399 --> 00:00:58.869 align:start position:0% wrote it in Zigg and and of course in the<00:00:56.559> early<00:00:56.800> days<00:00:57.039> it<00:00:57.199> was<00:00:57.360> handwritten<00:00:58.559> they 00:00:58.869 --> 00:00:58.879 align:start position:0% the early days it was handwritten they 00:00:58.879 --> 00:01:02.869 align:start position:0% the early days it was handwritten they started<00:01:00.000> using<00:01:00.480> Claude<00:01:00.960> extensively 00:01:02.869 --> 00:01:02.879 align:start position:0% started using Claude extensively 00:01:02.879 --> 00:01:05.429 align:start position:0% started using Claude extensively uh<00:01:03.039> the<00:01:03.280> last<00:01:03.440> couple<00:01:03.680> years<00:01:04.000> and<00:01:04.239> now<00:01:05.199> with 00:01:05.429 --> 00:01:05.439 align:start position:0% uh the last couple years and now with 00:01:05.439 --> 00:01:07.350 align:start position:0% uh the last couple years and now with this<00:01:05.680> rewrite<00:01:06.159> to<00:01:06.320> Rust<00:01:06.640> it's<00:01:06.880> completely 00:01:07.350 --> 00:01:07.360 align:start position:0% this rewrite to Rust it's completely 00:01:07.360 --> 00:01:10.070 align:start position:0% this rewrite to Rust it's completely written<00:01:07.600> by<00:01:07.920> Claude<00:01:09.200> and<00:01:09.360> I<00:01:09.520> realized<00:01:09.840> this<00:01:10.000> is 00:01:10.070 --> 00:01:10.080 align:start position:0% written by Claude and I realized this is 00:01:10.080 --> 00:01:14.070 align:start position:0% written by Claude and I realized this is actually<00:01:10.240> a<00:01:10.400> big<00:01:10.560> risk<00:01:11.920> because<00:01:12.479> if<00:01:12.799> this 00:01:14.070 --> 00:01:14.080 align:start position:0% actually a big risk because if this 00:01:14.080 --> 00:01:17.270 align:start position:0% actually a big risk because if this fails<00:01:14.640> and<00:01:14.799> and<00:01:15.200> the<00:01:15.360> the<00:01:15.680> project<00:01:16.000> becomes 00:01:17.270 --> 00:01:17.280 align:start position:0% fails and and the the project becomes 00:01:17.280 --> 00:01:20.950 align:start position:0% fails and and the the project becomes too<00:01:17.680> complex<00:01:18.960> for<00:01:19.200> Claude<00:01:19.680> to<00:01:20.320> continue<00:01:20.640> to 00:01:20.950 --> 00:01:20.960 align:start position:0% too complex for Claude to continue to 00:01:20.960 --> 00:01:24.070 align:start position:0% too complex for Claude to continue to maintain 00:01:24.070 --> 00:01:24.080 align:start position:0% 00:01:24.080 --> 00:01:26.469 align:start position:0% This<00:01:24.320> could<00:01:24.560> be<00:01:24.640> a<00:01:24.799> PR<00:01:25.200> disaster<00:01:25.920> not<00:01:26.159> just<00:01:26.240> for 00:01:26.469 --> 00:01:26.479 align:start position:0% This could be a PR disaster not just for 00:01:26.479 --> 00:01:29.270 align:start position:0% This could be a PR disaster not just for Anthropic<00:01:27.119> but<00:01:27.439> even<00:01:27.759> for 00:01:29.270 --> 00:01:29.280 align:start position:0% Anthropic but even for 00:01:29.280 --> 00:01:32.630 align:start position:0% Anthropic but even for all<00:01:29.840> frontier<00:01:30.400> AI<00:01:30.960> companies.<00:01:32.079> Remember<00:01:32.400> they 00:01:32.630 --> 00:01:32.640 align:start position:0% all frontier AI companies. Remember they 00:01:32.640 --> 00:01:35.910 align:start position:0% all frontier AI companies. Remember they all<00:01:32.880> pretty<00:01:33.119> much<00:01:33.759> pivoted<00:01:34.320> to<00:01:34.560> focus<00:01:34.880> on<00:01:35.520> on 00:01:35.910 --> 00:01:35.920 align:start position:0% all pretty much pivoted to focus on on 00:01:35.920 --> 00:01:39.910 align:start position:0% all pretty much pivoted to focus on on coding<00:01:37.360> the<00:01:37.600> last<00:01:37.920> year<00:01:38.159> or<00:01:38.479> two<00:01:39.119> because<00:01:39.439> they 00:01:39.910 --> 00:01:39.920 align:start position:0% coding the last year or two because they 00:01:39.920 --> 00:01:41.749 align:start position:0% coding the last year or two because they collectively<00:01:40.560> realized<00:01:41.119> this<00:01:41.280> is<00:01:41.439> where<00:01:41.600> the 00:01:41.749 --> 00:01:41.759 align:start position:0% collectively realized this is where the 00:01:41.759 --> 00:01:44.069 align:start position:0% collectively realized this is where the money<00:01:42.000> is,<00:01:42.560> right?<00:01:43.280> The<00:01:43.520> money<00:01:43.680> is<00:01:43.920> not 00:01:44.069 --> 00:01:44.079 align:start position:0% money is, right? The money is not 00:01:44.079 --> 00:01:46.950 align:start position:0% money is, right? The money is not getting<00:01:44.320> normies<00:01:44.799> to<00:01:44.960> pay<00:01:45.119> 10<00:01:45.360> bucks<00:01:45.600> a<00:01:45.759> month. 00:01:46.950 --> 00:01:46.960 align:start position:0% getting normies to pay 10 bucks a month. 00:01:46.960 --> 00:01:49.830 align:start position:0% getting normies to pay 10 bucks a month. The<00:01:47.280> money<00:01:47.439> is<00:01:47.759> in<00:01:48.479> getting<00:01:48.799> highly<00:01:49.200> paid 00:01:49.830 --> 00:01:49.840 align:start position:0% The money is in getting highly paid 00:01:49.840 --> 00:01:53.109 align:start position:0% The money is in getting highly paid programmers<00:01:50.479> to<00:01:50.799> pay<00:01:51.439> $200<00:01:52.000> a<00:01:52.240> month,<00:01:52.799> getting 00:01:53.109 --> 00:01:53.119 align:start position:0% programmers to pay $200 a month, getting 00:01:53.119 --> 00:01:55.910 align:start position:0% programmers to pay $200 a month, getting software<00:01:53.600> companies<00:01:54.000> to<00:01:54.159> pay<00:01:54.399> per<00:01:54.640> seat,<00:01:55.600> and 00:01:55.910 --> 00:01:55.920 align:start position:0% software companies to pay per seat, and 00:01:55.920 --> 00:01:58.230 align:start position:0% software companies to pay per seat, and of<00:01:56.079> course<00:01:56.320> paying<00:01:56.640> even<00:01:56.960> more<00:01:57.280> for<00:01:57.680> API 00:01:58.230 --> 00:01:58.240 align:start position:0% of course paying even more for API 00:01:58.240 --> 00:02:00.550 align:start position:0% of course paying even more for API usage. 00:02:00.550 --> 00:02:00.560 align:start position:0% usage. 00:02:00.560 --> 00:02:02.870 align:start position:0% usage. And<00:02:00.960> so<00:02:01.200> what<00:02:01.439> happens<00:02:01.600> if<00:02:01.840> a<00:02:02.159> big<00:02:02.479> project 00:02:02.870 --> 00:02:02.880 align:start position:0% And so what happens if a big project 00:02:02.880 --> 00:02:05.990 align:start position:0% And so what happens if a big project like<00:02:03.200> this<00:02:04.479> cuz<00:02:04.719> because<00:02:04.960> with<00:02:05.200> bun<00:02:05.600> this<00:02:05.759> is 00:02:05.990 --> 00:02:06.000 align:start position:0% like this cuz because with bun this is 00:02:06.000 --> 00:02:09.029 align:start position:0% like this cuz because with bun this is like<00:02:06.399> best<00:02:06.719> case<00:02:06.960> scenario<00:02:07.439> for 00:02:09.029 --> 00:02:09.039 align:start position:0% like best case scenario for 00:02:09.039 --> 00:02:11.110 align:start position:0% like best case scenario for agentic<00:02:09.599> coding,<00:02:10.080> right?<00:02:10.560> They<00:02:10.800> have<00:02:10.879> an 00:02:11.110 --> 00:02:11.120 align:start position:0% agentic coding, right? They have an 00:02:11.120 --> 00:02:13.430 align:start position:0% agentic coding, right? They have an unlimited<00:02:11.520> token<00:02:12.000> budget<00:02:12.400> because<00:02:12.720> they<00:02:13.200> of 00:02:13.430 --> 00:02:13.440 align:start position:0% unlimited token budget because they of 00:02:13.440 --> 00:02:15.990 align:start position:0% unlimited token budget because they of course<00:02:13.680> work<00:02:13.840> for<00:02:14.080> Anthropic<00:02:15.440> and<00:02:15.680> they<00:02:15.920> have 00:02:15.990 --> 00:02:16.000 align:start position:0% course work for Anthropic and they have 00:02:16.000 --> 00:02:18.470 align:start position:0% course work for Anthropic and they have an<00:02:16.160> unlimited<00:02:16.560> human<00:02:16.879> budget<00:02:17.599> because<00:02:18.239> they 00:02:18.470 --> 00:02:18.480 align:start position:0% an unlimited human budget because they 00:02:18.480 --> 00:02:22.150 align:start position:0% an unlimited human budget because they they<00:02:19.360> they<00:02:19.760> can<00:02:19.920> hire<00:02:20.319> the<00:02:20.720> best<00:02:21.680> programmers 00:02:22.150 --> 00:02:22.160 align:start position:0% they they can hire the best programmers 00:02:22.160 --> 00:02:25.110 align:start position:0% they they can hire the best programmers that<00:02:22.400> money<00:02:22.640> can<00:02:22.879> buy.<00:02:24.080> Um<00:02:24.560> they're<00:02:24.879> paying 00:02:25.110 --> 00:02:25.120 align:start position:0% that money can buy. Um they're paying 00:02:25.120 --> 00:02:27.430 align:start position:0% that money can buy. Um they're paying Silicon<00:02:25.599> Valley<00:02:26.000> salaries,<00:02:26.800> right?<00:02:27.280> They 00:02:27.430 --> 00:02:27.440 align:start position:0% Silicon Valley salaries, right? They 00:02:27.440 --> 00:02:28.949 align:start position:0% Silicon Valley salaries, right? They they're<00:02:27.680> hiring<00:02:28.080> people<00:02:28.239> who<00:02:28.480> can<00:02:28.720> probably 00:02:28.949 --> 00:02:28.959 align:start position:0% they're hiring people who can probably 00:02:28.959 --> 00:02:31.990 align:start position:0% they're hiring people who can probably run<00:02:29.120> circles<00:02:29.520> around<00:02:29.840> me. 00:02:31.990 --> 00:02:32.000 align:start position:0% run circles around me. 00:02:32.000 --> 00:02:34.869 align:start position:0% run circles around me. And<00:02:32.160> and<00:02:32.480> so<00:02:32.640> if<00:02:32.879> they<00:02:33.120> get<00:02:33.280> to<00:02:33.440> a<00:02:33.680> point<00:02:33.840> where 00:02:34.869 --> 00:02:34.879 align:start position:0% And and so if they get to a point where 00:02:34.879 --> 00:02:37.990 align:start position:0% And and so if they get to a point where this<00:02:35.200> codebase<00:02:36.080> becomes<00:02:37.120> unmaintainable 00:02:37.990 --> 00:02:38.000 align:start position:0% this codebase becomes unmaintainable 00:02:38.000 --> 00:02:41.750 align:start position:0% this codebase becomes unmaintainable even<00:02:38.239> for<00:02:38.480> Claude, 00:02:41.750 --> 00:02:41.760 align:start position:0% 00:02:41.760 --> 00:02:44.630 align:start position:0% that<00:02:42.000> would<00:02:42.160> be<00:02:42.560> a<00:02:42.879> pretty<00:02:43.120> big<00:02:43.280> disaster.<00:02:44.400> A 00:02:44.630 --> 00:02:44.640 align:start position:0% that would be a pretty big disaster. A 00:02:44.640 --> 00:02:46.390 align:start position:0% that would be a pretty big disaster. A lot<00:02:44.720> of<00:02:44.879> people<00:02:45.040> would<00:02:45.280> suddenly<00:02:45.680> be<00:02:45.920> like, 00:02:46.390 --> 00:02:46.400 align:start position:0% lot of people would suddenly be like, 00:02:46.400 --> 00:02:49.110 align:start position:0% lot of people would suddenly be like, uh,<00:02:47.680> okay,<00:02:48.080> maybe<00:02:48.239> we<00:02:48.480> still<00:02:48.640> need<00:02:48.800> to<00:02:48.959> think 00:02:49.110 --> 00:02:49.120 align:start position:0% uh, okay, maybe we still need to think 00:02:49.120 --> 00:02:52.630 align:start position:0% uh, okay, maybe we still need to think about<00:02:49.599> simplicity. 00:02:52.630 --> 00:02:52.640 align:start position:0% 00:02:52.640 --> 00:02:55.430 align:start position:0% But<00:02:52.879> if<00:02:53.040> they<00:02:53.360> prove<00:02:53.760> that<00:02:54.640> they<00:02:54.959> can<00:02:55.200> still 00:02:55.430 --> 00:02:55.440 align:start position:0% But if they prove that they can still 00:02:55.440 --> 00:02:58.150 align:start position:0% But if they prove that they can still maintain<00:02:55.840> it, 00:02:58.150 --> 00:02:58.160 align:start position:0% maintain it, 00:02:58.160 --> 00:03:00.710 align:start position:0% maintain it, um,<00:02:58.720> then<00:02:58.959> maybe<00:02:59.280> people<00:02:59.519> like<00:02:59.680> me<00:02:59.920> need<00:03:00.160> to 00:03:00.710 --> 00:03:00.720 align:start position:0% um, then maybe people like me need to 00:03:00.720 --> 00:03:02.790 align:start position:0% um, then maybe people like me need to re-evaluate. 00:03:02.790 --> 00:03:02.800 align:start position:0% re-evaluate. 00:03:02.800 --> 00:03:04.710 align:start position:0% re-evaluate. Again,<00:03:03.200> you<00:03:03.360> saw<00:03:03.519> in<00:03:03.680> my<00:03:03.840> last<00:03:04.000> video,<00:03:04.319> I'm<00:03:04.560> not 00:03:04.710 --> 00:03:04.720 align:start position:0% Again, you saw in my last video, I'm not 00:03:04.720 --> 00:03:07.430 align:start position:0% Again, you saw in my last video, I'm not against<00:03:05.040> AI.<00:03:05.599> I'm<00:03:05.840> I'm<00:03:06.319> in<00:03:06.560> favor<00:03:06.879> of<00:03:07.120> using 00:03:07.430 --> 00:03:07.440 align:start position:0% against AI. I'm I'm in favor of using 00:03:07.440 --> 00:03:10.550 align:start position:0% against AI. I'm I'm in favor of using it.<00:03:08.319> Um,<00:03:08.800> but<00:03:09.040> I<00:03:09.280> keep<00:03:09.440> it<00:03:09.599> on<00:03:09.760> a<00:03:09.920> short<00:03:10.159> leash. 00:03:10.550 --> 00:03:10.560 align:start position:0% it. Um, but I keep it on a short leash. 00:03:10.560 --> 00:03:12.949 align:start position:0% it. Um, but I keep it on a short leash. I<00:03:10.800> review<00:03:11.040> the<00:03:11.280> code<00:03:11.519> and<00:03:11.760> I<00:03:12.000> constantly<00:03:12.560> steer 00:03:12.949 --> 00:03:12.959 align:start position:0% I review the code and I constantly steer 00:03:12.959 --> 00:03:17.030 align:start position:0% I review the code and I constantly steer it<00:03:14.000> when<00:03:14.400> I<00:03:14.640> see<00:03:14.879> it<00:03:15.120> doing<00:03:16.239> making<00:03:16.560> a<00:03:16.800> solution 00:03:17.030 --> 00:03:17.040 align:start position:0% it when I see it doing making a solution 00:03:17.040 --> 00:03:20.390 align:start position:0% it when I see it doing making a solution that's<00:03:17.280> too<00:03:17.519> complex. 00:03:20.390 --> 00:03:20.400 align:start position:0% that's too complex. 00:03:20.400 --> 00:03:22.149 align:start position:0% that's too complex. They<00:03:20.560> I<00:03:20.879> don't<00:03:20.959> think<00:03:21.120> they're<00:03:21.280> using<00:03:21.519> AI<00:03:21.920> that 00:03:22.149 --> 00:03:22.159 align:start position:0% They I don't think they're using AI that 00:03:22.159 --> 00:03:24.710 align:start position:0% They I don't think they're using AI that way<00:03:22.560> at<00:03:22.800> Bun. 00:03:24.710 --> 00:03:24.720 align:start position:0% way at Bun. 00:03:24.720 --> 00:03:26.309 align:start position:0% way at Bun. There's<00:03:24.879> no<00:03:25.040> way<00:03:25.200> they<00:03:25.440> are<00:03:25.599> if<00:03:25.760> they're<00:03:26.080> if 00:03:26.309 --> 00:03:26.319 align:start position:0% There's no way they are if they're if 00:03:26.319 --> 00:03:29.110 align:start position:0% There's no way they are if they're if they're<00:03:26.640> doing<00:03:27.440> a<00:03:27.760> rewrite<00:03:28.159> like<00:03:28.400> this<00:03:28.640> in<00:03:28.879> a 00:03:29.110 --> 00:03:29.120 align:start position:0% they're doing a rewrite like this in a 00:03:29.120 --> 00:03:31.990 align:start position:0% they're doing a rewrite like this in a week<00:03:29.200> and<00:03:29.360> a<00:03:29.519> half. 00:03:31.990 --> 00:03:32.000 align:start position:0% week and a half. 00:03:32.000 --> 00:03:35.350 align:start position:0% week and a half. We'll<00:03:32.319> see.<00:03:33.599> I<00:03:33.840> mean,<00:03:34.480> I'm<00:03:34.799> actually<00:03:35.040> really 00:03:35.350 --> 00:03:35.360 align:start position:0% We'll see. I mean, I'm actually really 00:03:35.360 --> 00:03:40.070 align:start position:0% We'll see. I mean, I'm actually really interested.<00:03:35.840> I<00:03:36.000> want<00:03:36.159> to<00:03:36.319> see<00:03:37.519> um<00:03:38.239> if<00:03:39.599> what<00:03:39.840> I 00:03:40.070 --> 00:03:40.080 align:start position:0% interested. I want to see um if what I 00:03:40.080 --> 00:03:43.589 align:start position:0% interested. I want to see um if what I said<00:03:40.239> in<00:03:40.400> that<00:03:40.640> last<00:03:40.879> video<00:03:42.239> proves<00:03:42.640> true. 00:03:43.589 --> 00:03:43.599 align:start position:0% said in that last video proves true. 00:03:43.599 --> 00:03:45.990 align:start position:0% said in that last video proves true. Will<00:03:43.920> complexity<00:03:44.480> ever 00:03:45.990 --> 00:03:46.000 align:start position:0% Will complexity ever 00:03:46.000 --> 00:03:48.149 align:start position:0% Will complexity ever grow<00:03:46.560> so<00:03:46.879> fast<00:03:47.120> that<00:03:47.280> it<00:03:47.440> outstrips<00:03:48.000> the 00:03:48.149 --> 00:03:48.159 align:start position:0% grow so fast that it outstrips the 00:03:48.159 --> 00:03:51.589 align:start position:0% grow so fast that it outstrips the model's<00:03:48.560> ability<00:03:48.959> to<00:03:49.680> deal<00:03:49.920> with<00:03:50.080> it?<00:03:51.280> Okay, 00:03:51.589 --> 00:03:51.599 align:start position:0% model's ability to deal with it? Okay, 00:03:51.599 --> 00:03:53.509 align:start position:0% model's ability to deal with it? Okay, doing<00:03:51.840> the<00:03:52.080> initial<00:03:52.400> conversion<00:03:52.879> is<00:03:53.040> the<00:03:53.200> easy 00:03:53.509 --> 00:03:53.519 align:start position:0% doing the initial conversion is the easy 00:03:53.519 --> 00:03:55.190 align:start position:0% doing the initial conversion is the easy part.<00:03:53.760> We<00:03:53.920> know<00:03:54.080> these<00:03:54.319> models<00:03:54.720> are<00:03:54.879> good<00:03:54.959> at 00:03:55.190 --> 00:03:55.200 align:start position:0% part. We know these models are good at 00:03:55.200 --> 00:03:58.309 align:start position:0% part. We know these models are good at language<00:03:55.680> to<00:03:55.840> language<00:03:56.239> conversions. 00:03:58.309 --> 00:03:58.319 align:start position:0% language to language conversions. 00:03:58.319 --> 00:04:01.589 align:start position:0% language to language conversions. What<00:03:58.480> we<00:03:58.720> don't<00:03:58.959> know<00:03:59.280> is<00:03:59.760> what<00:04:00.080> happens<00:04:00.400> next. 00:04:01.589 --> 00:04:01.599 align:start position:0% What we don't know is what happens next. 00:04:01.599 --> 00:04:04.710 align:start position:0% What we don't know is what happens next. Will<00:04:01.840> they<00:04:02.080> be<00:04:02.239> able<00:04:02.400> to<00:04:02.640> maintain<00:04:04.000> and<00:04:04.400> add 00:04:04.710 --> 00:04:04.720 align:start position:0% Will they be able to maintain and add 00:04:04.720 --> 00:04:07.350 align:start position:0% Will they be able to maintain and add features<00:04:05.760> and<00:04:06.239> fix<00:04:06.560> bugs<00:04:06.959> without 00:04:07.350 --> 00:04:07.360 align:start position:0% features and fix bugs without 00:04:07.360 --> 00:04:09.750 align:start position:0% features and fix bugs without introducing<00:04:07.920> new<00:04:08.159> bugs? 00:04:09.750 --> 00:04:09.760 align:start position:0% introducing new bugs? 00:04:09.760 --> 00:04:12.229 align:start position:0% introducing new bugs? Um,<00:04:11.200> we're<00:04:11.360> going<00:04:11.439> to<00:04:11.599> have<00:04:11.680> to<00:04:11.840> find<00:04:12.000> out. 00:04:12.229 --> 00:04:12.239 align:start position:0% Um, we're going to have to find out. 00:04:12.239 --> 00:04:14.390 align:start position:0% Um, we're going to have to find out. There's<00:04:12.879> there's<00:04:13.280> already<00:04:13.519> one<00:04:13.760> bad<00:04:14.080> sign 00:04:14.390 --> 00:04:14.400 align:start position:0% There's there's already one bad sign 00:04:14.400 --> 00:04:17.349 align:start position:0% There's there's already one bad sign though.<00:04:15.360> If<00:04:15.599> you<00:04:15.680> look<00:04:15.760> at<00:04:15.920> that<00:04:16.160> PR,<00:04:16.959> the<00:04:17.120> new 00:04:17.349 --> 00:04:17.359 align:start position:0% though. If you look at that PR, the new 00:04:17.359 --> 00:04:19.909 align:start position:0% though. If you look at that PR, the new Rust<00:04:17.680> code<00:04:18.000> base<00:04:18.320> is<00:04:18.720> just<00:04:19.040> over<00:04:19.359> 1<00:04:19.600> million 00:04:19.909 --> 00:04:19.919 align:start position:0% Rust code base is just over 1 million 00:04:19.919 --> 00:04:22.790 align:start position:0% Rust code base is just over 1 million lines<00:04:20.799> of<00:04:21.120> code. 00:04:22.790 --> 00:04:22.800 align:start position:0% lines of code. 00:04:22.800 --> 00:04:24.950 align:start position:0% lines of code. Now,<00:04:23.120> the<00:04:23.360> original<00:04:23.680> Zig<00:04:24.080> code<00:04:24.320> base<00:04:24.639> was 00:04:24.950 --> 00:04:24.960 align:start position:0% Now, the original Zig code base was 00:04:24.960 --> 00:04:27.350 align:start position:0% Now, the original Zig code base was already<00:04:25.280> quite<00:04:25.600> large.<00:04:25.919> It<00:04:26.080> was<00:04:26.320> 640,000 00:04:27.350 --> 00:04:27.360 align:start position:0% already quite large. It was 640,000 00:04:27.360 --> 00:04:29.749 align:start position:0% already quite large. It was 640,000 lines. 00:04:29.749 --> 00:04:29.759 align:start position:0% lines. 00:04:29.759 --> 00:04:32.790 align:start position:0% lines. So,<00:04:30.160> this<00:04:30.560> rewrite 00:04:32.790 --> 00:04:32.800 align:start position:0% So, this rewrite 00:04:32.800 --> 00:04:34.870 align:start position:0% So, this rewrite by<00:04:33.120> Claude 00:04:34.870 --> 00:04:34.880 align:start position:0% by Claude 00:04:34.880 --> 00:04:38.550 align:start position:0% by Claude increased<00:04:36.240> the<00:04:36.560> size<00:04:36.960> of<00:04:37.199> the<00:04:37.360> the<00:04:37.919> codebase 00:04:38.550 --> 00:04:38.560 align:start position:0% increased the size of the the codebase 00:04:38.560 --> 00:04:41.670 align:start position:0% increased the size of the the codebase by<00:04:39.040> like<00:04:39.360> more<00:04:39.600> than<00:04:39.840> 60%. 00:04:41.670 --> 00:04:41.680 align:start position:0% by like more than 60%. 00:04:41.680 --> 00:04:44.950 align:start position:0% by like more than 60%. Think<00:04:41.919> about<00:04:42.080> how<00:04:42.320> crazy<00:04:42.639> that<00:04:42.880> is.<00:04:44.320> Rust<00:04:44.720> is 00:04:44.950 --> 00:04:44.960 align:start position:0% Think about how crazy that is. Rust is 00:04:44.960 --> 00:04:46.629 align:start position:0% Think about how crazy that is. Rust is actually<00:04:45.199> a<00:04:45.440> more<00:04:45.680> concise<00:04:46.080> language<00:04:46.479> than 00:04:46.629 --> 00:04:46.639 align:start position:0% actually a more concise language than 00:04:46.639 --> 00:04:48.950 align:start position:0% actually a more concise language than Zigg.<00:04:47.120> If<00:04:47.280> you<00:04:47.440> compare 00:04:48.950 --> 00:04:48.960 align:start position:0% Zigg. If you compare 00:04:48.960 --> 00:04:50.710 align:start position:0% Zigg. If you compare uh<00:04:49.120> equivalent<00:04:49.600> code,<00:04:50.000> the<00:04:50.160> Zig<00:04:50.400> code<00:04:50.560> is 00:04:50.710 --> 00:04:50.720 align:start position:0% uh equivalent code, the Zig code is 00:04:50.720 --> 00:04:54.230 align:start position:0% uh equivalent code, the Zig code is usually<00:04:51.120> longer<00:04:52.320> because<00:04:53.199> Zigg<00:04:53.680> requires<00:04:54.080> you 00:04:54.230 --> 00:04:54.240 align:start position:0% usually longer because Zigg requires you 00:04:54.240 --> 00:04:56.150 align:start position:0% usually longer because Zigg requires you to<00:04:54.880> do<00:04:55.040> more<00:04:55.280> things<00:04:55.440> explicitly.<00:04:56.000> It 00:04:56.150 --> 00:04:56.160 align:start position:0% to do more things explicitly. It 00:04:56.160 --> 00:04:57.189 align:start position:0% to do more things explicitly. It doesn't,<00:04:56.400> for<00:04:56.479> example,<00:04:56.720> it<00:04:56.880> doesn't<00:04:57.040> have 00:04:57.189 --> 00:04:57.199 align:start position:0% doesn't, for example, it doesn't have 00:04:57.199 --> 00:04:58.870 align:start position:0% doesn't, for example, it doesn't have destructors.<00:04:57.759> So,<00:04:57.919> the<00:04:58.080> cleanup<00:04:58.479> code<00:04:58.720> is 00:04:58.870 --> 00:04:58.880 align:start position:0% destructors. So, the cleanup code is 00:04:58.880 --> 00:05:02.230 align:start position:0% destructors. So, the cleanup code is always<00:04:59.440> explicitly<00:05:00.160> there. 00:05:02.230 --> 00:05:02.240 align:start position:0% always explicitly there. 00:05:02.240 --> 00:05:04.469 align:start position:0% always explicitly there. Zig<00:05:02.639> is<00:05:02.720> a<00:05:02.880> more<00:05:03.120> verbose<00:05:03.600> language<00:05:04.160> and 00:05:04.469 --> 00:05:04.479 align:start position:0% Zig is a more verbose language and 00:05:04.479 --> 00:05:06.550 align:start position:0% Zig is a more verbose language and somehow<00:05:04.800> the<00:05:05.040> rewrite 00:05:06.550 --> 00:05:06.560 align:start position:0% somehow the rewrite 00:05:06.560 --> 00:05:09.590 align:start position:0% somehow the rewrite exploded<00:05:07.280> the<00:05:07.440> line<00:05:07.759> count<00:05:08.800> from<00:05:09.120> Zigg<00:05:09.440> to 00:05:09.590 --> 00:05:09.600 align:start position:0% exploded the line count from Zigg to 00:05:09.600 --> 00:05:12.950 align:start position:0% exploded the line count from Zigg to Rust.<00:05:10.400> How<00:05:10.639> crazy<00:05:10.960> is<00:05:11.120> that? 00:05:12.950 --> 00:05:12.960 align:start position:0% Rust. How crazy is that? 00:05:12.960 --> 00:05:15.350 align:start position:0% Rust. How crazy is that? But<00:05:13.280> but<00:05:13.520> there's<00:05:14.240> even<00:05:14.560> more.<00:05:14.880> Just<00:05:15.039> to<00:05:15.199> put 00:05:15.350 --> 00:05:15.360 align:start position:0% But but there's even more. Just to put 00:05:15.360 --> 00:05:17.510 align:start position:0% But but there's even more. Just to put this<00:05:15.520> in<00:05:15.680> perspective,<00:05:16.560> there's<00:05:17.199> something 00:05:17.510 --> 00:05:17.520 align:start position:0% this in perspective, there's something 00:05:17.520 --> 00:05:19.990 align:start position:0% this in perspective, there's something even<00:05:17.759> more<00:05:18.000> crazy<00:05:18.320> here. 00:05:19.990 --> 00:05:20.000 align:start position:0% even more crazy here. 00:05:20.000 --> 00:05:21.830 align:start position:0% even more crazy here. I<00:05:20.240> don't<00:05:20.320> know<00:05:20.400> if<00:05:20.560> you're<00:05:21.199> familiar<00:05:21.600> with 00:05:21.830 --> 00:05:21.840 align:start position:0% I don't know if you're familiar with 00:05:21.840 --> 00:05:24.150 align:start position:0% I don't know if you're familiar with Bun. 00:05:24.150 --> 00:05:24.160 align:start position:0% Bun. 00:05:24.160 --> 00:05:26.629 align:start position:0% Bun. Bun<00:05:24.479> is<00:05:24.720> not<00:05:24.880> a<00:05:25.199> JavaScript<00:05:25.759> compiler,<00:05:26.479> just 00:05:26.629 --> 00:05:26.639 align:start position:0% Bun is not a JavaScript compiler, just 00:05:26.639 --> 00:05:31.189 align:start position:0% Bun is not a JavaScript compiler, just to<00:05:26.880> be<00:05:27.039> clear.<00:05:28.479> Um,<00:05:29.520> Bun<00:05:30.000> uses<00:05:30.320> a<00:05:30.560> JavaScript 00:05:31.189 --> 00:05:31.199 align:start position:0% to be clear. Um, Bun uses a JavaScript 00:05:31.199 --> 00:05:35.270 align:start position:0% to be clear. Um, Bun uses a JavaScript compiler,<00:05:32.560> right?<00:05:33.600> Um,<00:05:34.000> Bun<00:05:34.400> uses<00:05:34.720> JavaScript 00:05:35.270 --> 00:05:35.280 align:start position:0% compiler, right? Um, Bun uses JavaScript 00:05:35.280 --> 00:05:38.870 align:start position:0% compiler, right? Um, Bun uses JavaScript core,<00:05:36.560> which<00:05:37.199> uh<00:05:37.840> comes<00:05:38.080> from<00:05:38.240> the<00:05:38.400> WebKit 00:05:38.870 --> 00:05:38.880 align:start position:0% core, which uh comes from the WebKit 00:05:38.880 --> 00:05:40.390 align:start position:0% core, which uh comes from the WebKit project. 00:05:40.390 --> 00:05:40.400 align:start position:0% project. 00:05:40.400 --> 00:05:44.390 align:start position:0% project. and<00:05:40.639> then<00:05:41.199> they<00:05:41.520> just<00:05:41.759> wrap<00:05:42.080> it<00:05:43.120> and<00:05:43.919> implement 00:05:44.390 --> 00:05:44.400 align:start position:0% and then they just wrap it and implement 00:05:44.400 --> 00:05:47.350 align:start position:0% and then they just wrap it and implement the<00:05:44.560> node<00:05:44.880> API<00:05:45.759> as<00:05:46.080> well<00:05:46.160> as<00:05:46.400> their<00:05:46.639> own 00:05:47.350 --> 00:05:47.360 align:start position:0% the node API as well as their own 00:05:47.360 --> 00:05:49.350 align:start position:0% the node API as well as their own additional<00:05:48.080> standard<00:05:48.479> library.<00:05:49.039> That's<00:05:49.199> all 00:05:49.350 --> 00:05:49.360 align:start position:0% additional standard library. That's all 00:05:49.360 --> 00:05:51.749 align:start position:0% additional standard library. That's all bun<00:05:49.600> is<00:05:49.840> doing. 00:05:51.749 --> 00:05:51.759 align:start position:0% bun is doing. 00:05:51.759 --> 00:05:54.629 align:start position:0% bun is doing. I<00:05:52.080> think<00:05:52.160> you<00:05:52.400> can<00:05:52.560> agree<00:05:52.880> with<00:05:53.039> me<00:05:53.199> that<00:05:54.160> the 00:05:54.629 --> 00:05:54.639 align:start position:0% I think you can agree with me that the 00:05:54.639 --> 00:05:57.430 align:start position:0% I think you can agree with me that the JIT<00:05:55.039> compiler<00:05:55.600> for<00:05:55.840> JavaScript<00:05:56.400> is<00:05:56.639> the<00:05:56.880> more 00:05:57.430 --> 00:05:57.440 align:start position:0% JIT compiler for JavaScript is the more 00:05:57.440 --> 00:06:00.070 align:start position:0% JIT compiler for JavaScript is the more complex<00:05:57.919> part<00:05:58.160> of<00:05:58.400> this, 00:06:00.070 --> 00:06:00.080 align:start position:0% complex part of this, 00:06:00.080 --> 00:06:05.430 align:start position:0% complex part of this, not<00:06:00.320> the<00:06:00.560> wrapper<00:06:02.000> around<00:06:02.400> it<00:06:03.360> that<00:06:03.680> adds 00:06:05.430 --> 00:06:05.440 align:start position:0% not the wrapper around it that adds 00:06:05.440 --> 00:06:09.430 align:start position:0% not the wrapper around it that adds um<00:06:06.479> implements<00:06:06.880> the<00:06:07.039> node<00:06:07.360> API. 00:06:09.430 --> 00:06:09.440 align:start position:0% um implements the node API. 00:06:09.440 --> 00:06:12.870 align:start position:0% um implements the node API. Well,<00:06:09.680> I<00:06:09.840> looked<00:06:10.000> it<00:06:10.160> up.<00:06:10.400> JavaScript<00:06:10.960> Core 00:06:12.870 --> 00:06:12.880 align:start position:0% Well, I looked it up. JavaScript Core 00:06:12.880 --> 00:06:16.550 align:start position:0% Well, I looked it up. JavaScript Core the<00:06:13.360> uh<00:06:13.919> the<00:06:14.240> compiler<00:06:14.639> that<00:06:14.800> they're<00:06:15.039> using 00:06:16.550 --> 00:06:16.560 align:start position:0% the uh the compiler that they're using 00:06:16.560 --> 00:06:21.830 align:start position:0% the uh the compiler that they're using is<00:06:17.120> about<00:06:18.319> 590,000<00:06:19.440> lines<00:06:20.000> of<00:06:20.240> C++. 00:06:21.830 --> 00:06:21.840 align:start position:0% is about 590,000 lines of C++. 00:06:21.840 --> 00:06:25.430 align:start position:0% is about 590,000 lines of C++. It's<00:06:22.080> just<00:06:22.240> under<00:06:22.560> 600,000<00:06:23.280> lines. 00:06:25.430 --> 00:06:25.440 align:start position:0% It's just under 600,000 lines. 00:06:25.440 --> 00:06:27.909 align:start position:0% It's just under 600,000 lines. So<00:06:25.840> even<00:06:26.080> the<00:06:26.400> original<00:06:26.800> Zigg<00:06:27.199> codebase<00:06:27.680> of 00:06:27.909 --> 00:06:27.919 align:start position:0% So even the original Zigg codebase of 00:06:27.919 --> 00:06:31.110 align:start position:0% So even the original Zigg codebase of bun<00:06:28.319> was<00:06:28.560> already<00:06:29.039> larger 00:06:31.110 --> 00:06:31.120 align:start position:0% bun was already larger 00:06:31.120 --> 00:06:33.590 align:start position:0% bun was already larger in<00:06:31.440> line<00:06:31.759> count 00:06:33.590 --> 00:06:33.600 align:start position:0% in line count 00:06:33.600 --> 00:06:36.550 align:start position:0% in line count than<00:06:33.840> the<00:06:34.400> JIT<00:06:34.960> compiler, 00:06:36.550 --> 00:06:36.560 align:start position:0% than the JIT compiler, 00:06:36.560 --> 00:06:38.390 align:start position:0% than the JIT compiler, the<00:06:36.800> JavaScript<00:06:37.360> compiler<00:06:37.840> that<00:06:38.080> they're 00:06:38.390 --> 00:06:38.400 align:start position:0% the JavaScript compiler that they're 00:06:38.400 --> 00:06:40.150 align:start position:0% the JavaScript compiler that they're wrapping. 00:06:40.150 --> 00:06:40.160 align:start position:0% wrapping. 00:06:40.160 --> 00:06:42.710 align:start position:0% wrapping. And<00:06:40.400> now<00:06:40.639> with<00:06:40.800> this<00:06:41.039> Rust<00:06:41.440> rewrite,<00:06:42.400> it's 00:06:42.710 --> 00:06:42.720 align:start position:0% And now with this Rust rewrite, it's 00:06:42.720 --> 00:06:45.350 align:start position:0% And now with this Rust rewrite, it's nearly<00:06:43.120> double<00:06:43.919> the<00:06:44.240> line<00:06:44.560> count<00:06:45.039> of 00:06:45.350 --> 00:06:45.360 align:start position:0% nearly double the line count of 00:06:45.360 --> 00:06:47.670 align:start position:0% nearly double the line count of JavaScript<00:06:45.919> core.<00:06:46.319> How<00:06:46.639> [ __ ]<00:06:47.039> insane<00:06:47.440> is 00:06:47.670 --> 00:06:47.680 align:start position:0% JavaScript core. How [ __ ] insane is 00:06:47.680 --> 00:06:49.670 align:start position:0% JavaScript core. How [ __ ] insane is that? 00:06:49.670 --> 00:06:49.680 align:start position:0% that? 00:06:49.680 --> 00:06:52.230 align:start position:0% that? Like<00:06:49.919> what<00:06:50.080> the<00:06:50.240> hell<00:06:50.400> is<00:06:50.560> it<00:06:50.720> even<00:06:50.960> doing? 00:06:52.230 --> 00:06:52.240 align:start position:0% Like what the hell is it even doing? 00:06:52.240 --> 00:06:54.230 align:start position:0% Like what the hell is it even doing? What<00:06:52.400> is<00:06:52.560> it<00:06:52.800> actually<00:06:53.120> doing?<00:06:53.520> and<00:06:53.680> and<00:06:53.680> and 00:06:54.230 --> 00:06:54.240 align:start position:0% What is it actually doing? and and and 00:06:54.240 --> 00:06:56.550 align:start position:0% What is it actually doing? and and and explain<00:06:54.560> how<00:06:54.800> that<00:06:55.280> requires<00:06:55.919> double<00:06:56.319> the 00:06:56.550 --> 00:06:56.560 align:start position:0% explain how that requires double the 00:06:56.560 --> 00:06:59.909 align:start position:0% explain how that requires double the line<00:06:56.800> count<00:06:58.000> of<00:06:58.319> a 00:06:59.909 --> 00:06:59.919 align:start position:0% line count of a 00:06:59.919 --> 00:07:03.830 align:start position:0% line count of a very<00:07:01.360> advanced<00:07:02.240> featureful 00:07:03.830 --> 00:07:03.840 align:start position:0% very advanced featureful 00:07:03.840 --> 00:07:06.790 align:start position:0% very advanced featureful JavaScript<00:07:04.479> JIT<00:07:04.880> compiler.<00:07:05.919> Explain<00:07:06.319> that<00:07:06.560> to 00:07:06.790 --> 00:07:06.800 align:start position:0% JavaScript JIT compiler. Explain that to 00:07:06.800 --> 00:07:14.950 align:start position:0% JavaScript JIT compiler. Explain that to me. 00:07:14.950 --> 00:07:14.960 align:start position:0% 00:07:14.960 --> 00:07:17.909 align:start position:0% It's<00:07:15.199> going<00:07:15.280> to<00:07:15.440> be<00:07:15.520> very<00:07:15.840> interesting<00:07:16.639> to<00:07:16.960> see 00:07:17.909 --> 00:07:17.919 align:start position:0% It's going to be very interesting to see 00:07:17.919 --> 00:07:22.230 align:start position:0% It's going to be very interesting to see uh<00:07:18.639> what<00:07:18.880> the<00:07:19.039> limits<00:07:19.440> are. 00:07:22.230 --> 00:07:22.240 align:start position:0% uh what the limits are. 00:07:22.240 --> 00:07:25.350 align:start position:0% uh what the limits are. And<00:07:22.560> I<00:07:22.960> one<00:07:23.199> thing<00:07:23.360> I<00:07:23.759> can<00:07:24.000> predict<00:07:24.400> is<00:07:24.639> that 00:07:25.350 --> 00:07:25.360 align:start position:0% And I one thing I can predict is that 00:07:25.360 --> 00:07:27.189 align:start position:0% And I one thing I can predict is that the<00:07:25.599> line<00:07:25.840> count<00:07:26.080> is<00:07:26.240> not<00:07:26.400> going<00:07:26.479> to<00:07:26.560> stay<00:07:26.720> at<00:07:26.960> 1 00:07:27.189 --> 00:07:27.199 align:start position:0% the line count is not going to stay at 1 00:07:27.199 --> 00:07:29.189 align:start position:0% the line count is not going to stay at 1 million.<00:07:27.599> Guys, 00:07:29.189 --> 00:07:29.199 align:start position:0% million. Guys, 00:07:29.199 --> 00:07:31.270 align:start position:0% million. Guys, as<00:07:29.440> I<00:07:29.599> said<00:07:29.680> in<00:07:29.919> my<00:07:30.080> last<00:07:30.240> video,<00:07:30.639> complexity 00:07:31.270 --> 00:07:31.280 align:start position:0% as I said in my last video, complexity 00:07:31.280 --> 00:07:34.950 align:start position:0% as I said in my last video, complexity compounds<00:07:32.319> when<00:07:32.560> you<00:07:32.800> allow<00:07:33.280> a<00:07:33.440> a<00:07:34.000> complex 00:07:34.950 --> 00:07:34.960 align:start position:0% compounds when you allow a a complex 00:07:34.960 --> 00:07:37.510 align:start position:0% compounds when you allow a a complex solution<00:07:35.360> to<00:07:35.599> get<00:07:35.759> into<00:07:35.919> your<00:07:36.080> codebase. 00:07:37.510 --> 00:07:37.520 align:start position:0% solution to get into your codebase. 00:07:37.520 --> 00:07:39.909 align:start position:0% solution to get into your codebase. Every<00:07:38.080> change<00:07:38.639> after<00:07:38.960> that<00:07:39.280> has<00:07:39.440> to<00:07:39.599> be<00:07:39.759> more 00:07:39.909 --> 00:07:39.919 align:start position:0% Every change after that has to be more 00:07:39.919 --> 00:07:42.309 align:start position:0% Every change after that has to be more complex,<00:07:40.479> too. 00:07:42.309 --> 00:07:42.319 align:start position:0% complex, too. 00:07:42.319 --> 00:07:43.670 align:start position:0% complex, too. I<00:07:42.560> think<00:07:42.639> they're<00:07:42.880> going<00:07:42.960> to<00:07:43.039> be<00:07:43.199> adding<00:07:43.440> an 00:07:43.670 --> 00:07:43.680 align:start position:0% I think they're going to be adding an 00:07:43.680 --> 00:07:46.629 align:start position:0% I think they're going to be adding an insane<00:07:44.240> amount<00:07:44.800> of<00:07:45.120> code<00:07:45.360> to<00:07:45.599> this<00:07:45.919> project<00:07:46.400> in 00:07:46.629 --> 00:07:46.639 align:start position:0% insane amount of code to this project in 00:07:46.639 --> 00:07:49.749 align:start position:0% insane amount of code to this project in the<00:07:46.800> future<00:07:47.360> just<00:07:47.599> to<00:07:47.759> maintain<00:07:48.160> it. 00:07:49.749 --> 00:07:49.759 align:start position:0% the future just to maintain it. 00:07:49.759 --> 00:07:55.270 align:start position:0% the future just to maintain it. That's<00:07:50.000> my<00:07:50.240> prediction. 00:07:55.270 --> 00:07:55.280 align:start position:0% 00:07:55.280 --> 00:07:59.029 align:start position:0% you<00:07:55.520> know<00:07:56.000> um 00:07:59.029 --> 00:07:59.039 align:start position:0% 00:07:59.039 --> 00:08:00.869 align:start position:0% people<00:07:59.280> just<00:07:59.520> don't<00:07:59.759> really<00:08:00.000> appreciate<00:08:00.639> this 00:08:00.869 --> 00:08:00.879 align:start position:0% people just don't really appreciate this 00:08:00.879 --> 00:08:03.909 align:start position:0% people just don't really appreciate this this<00:08:01.360> entire<00:08:01.919> topic<00:08:02.319> of<00:08:02.879> complexity<00:08:03.599> and 00:08:03.909 --> 00:08:03.919 align:start position:0% this entire topic of complexity and 00:08:03.919 --> 00:08:07.510 align:start position:0% this entire topic of complexity and simplicity. 00:08:07.510 --> 00:08:07.520 align:start position:0% 00:08:07.520 --> 00:08:10.070 align:start position:0% I<00:08:07.759> think<00:08:07.840> it's<00:08:08.080> the<00:08:08.319> most<00:08:08.560> important 00:08:10.070 --> 00:08:10.080 align:start position:0% I think it's the most important 00:08:10.080 --> 00:08:13.350 align:start position:0% I think it's the most important topic<00:08:10.479> in<00:08:10.720> our<00:08:10.960> industry<00:08:12.319> and<00:08:12.639> almost<00:08:12.960> nobody 00:08:13.350 --> 00:08:13.360 align:start position:0% topic in our industry and almost nobody 00:08:13.360 --> 00:08:17.189 align:start position:0% topic in our industry and almost nobody can<00:08:13.599> even<00:08:13.919> talk<00:08:14.080> about<00:08:14.319> it<00:08:14.479> correctly. 00:08:17.189 --> 00:08:17.199 align:start position:0% can even talk about it correctly. 00:08:17.199 --> 00:08:19.589 align:start position:0% can even talk about it correctly. There's<00:08:17.520> a<00:08:17.680> lot<00:08:17.759> that<00:08:17.919> we<00:08:18.160> can<00:08:18.319> learn<00:08:19.199> by 00:08:19.589 --> 00:08:19.599 align:start position:0% There's a lot that we can learn by 00:08:19.599 --> 00:08:22.790 align:start position:0% There's a lot that we can learn by looking<00:08:19.840> at<00:08:20.080> other<00:08:20.319> domains. 00:08:22.790 --> 00:08:22.800 align:start position:0% looking at other domains. 00:08:22.800 --> 00:08:24.710 align:start position:0% looking at other domains. I'm<00:08:23.039> from<00:08:23.199> a<00:08:23.360> military<00:08:23.759> family.<00:08:24.160> Both<00:08:24.400> of<00:08:24.560> my 00:08:24.710 --> 00:08:24.720 align:start position:0% I'm from a military family. Both of my 00:08:24.720 --> 00:08:28.230 align:start position:0% I'm from a military family. Both of my parents<00:08:24.960> were<00:08:25.120> in<00:08:25.280> the<00:08:25.440> Navy.<00:08:26.160> My<00:08:26.479> dad 00:08:28.230 --> 00:08:28.240 align:start position:0% parents were in the Navy. My dad 00:08:28.240 --> 00:08:31.830 align:start position:0% parents were in the Navy. My dad uh<00:08:28.400> was<00:08:28.639> in<00:08:28.879> for<00:08:29.840> almost<00:08:30.160> four<00:08:30.479> decades.<00:08:31.199> He 00:08:31.830 --> 00:08:31.840 align:start position:0% uh was in for almost four decades. He 00:08:31.840 --> 00:08:34.949 align:start position:0% uh was in for almost four decades. He primarily<00:08:32.399> was<00:08:32.560> on<00:08:32.880> aircraft<00:08:33.360> carriers. 00:08:34.949 --> 00:08:34.959 align:start position:0% primarily was on aircraft carriers. 00:08:34.959 --> 00:08:37.750 align:start position:0% primarily was on aircraft carriers. He<00:08:35.200> was<00:08:35.279> an<00:08:35.440> ordinance. 00:08:37.750 --> 00:08:37.760 align:start position:0% He was an ordinance. 00:08:37.760 --> 00:08:39.750 align:start position:0% He was an ordinance. So,<00:08:38.080> as<00:08:38.320> a<00:08:38.479> kid,<00:08:38.719> of<00:08:38.880> course,<00:08:39.039> I<00:08:39.279> was<00:08:39.360> kind<00:08:39.519> of<00:08:39.519> a 00:08:39.750 --> 00:08:39.760 align:start position:0% So, as a kid, of course, I was kind of a 00:08:39.760 --> 00:08:43.269 align:start position:0% So, as a kid, of course, I was kind of a war<00:08:40.000> buff.<00:08:41.120> me<00:08:41.360> and<00:08:41.519> my<00:08:41.760> buddies,<00:08:42.080> we<00:08:42.320> would<00:08:43.039> we 00:08:43.269 --> 00:08:43.279 align:start position:0% war buff. me and my buddies, we would we 00:08:43.279 --> 00:08:48.870 align:start position:0% war buff. me and my buddies, we would we would<00:08:43.519> always<00:08:44.240> uh<00:08:45.440> you<00:08:45.680> know<00:08:46.480> uh<00:08:47.680> like<00:08:48.000> read 00:08:48.870 --> 00:08:48.880 align:start position:0% would always uh you know uh like read 00:08:48.880 --> 00:08:53.110 align:start position:0% would always uh you know uh like read World<00:08:49.040> War<00:08:49.279> II<00:08:49.519> books<00:08:50.000> and<00:08:50.720> uh<00:08:52.000> and<00:08:52.560> even<00:08:52.800> even 00:08:53.110 --> 00:08:53.120 align:start position:0% World War II books and uh and even even 00:08:53.120 --> 00:08:55.670 align:start position:0% World War II books and uh and even even dress<00:08:53.440> in<00:08:53.920> military<00:08:54.480> fatigues<00:08:55.040> and<00:08:55.200> stuff<00:08:55.360> as 00:08:55.670 --> 00:08:55.680 align:start position:0% dress in military fatigues and stuff as 00:08:55.680 --> 00:08:57.269 align:start position:0% dress in military fatigues and stuff as kids 00:08:57.269 --> 00:08:57.279 align:start position:0% kids 00:08:57.279 --> 00:09:00.710 align:start position:0% kids and<00:08:57.920> um<00:08:59.040> I<00:08:59.279> loved<00:08:59.600> reading<00:08:59.920> about<00:09:00.320> like 00:09:00.710 --> 00:09:00.720 align:start position:0% and um I loved reading about like 00:09:00.720 --> 00:09:03.670 align:start position:0% and um I loved reading about like nuclear<00:09:01.279> submarines<00:09:01.920> and<00:09:02.959> planes<00:09:03.360> like<00:09:03.519> the 00:09:03.670 --> 00:09:03.680 align:start position:0% nuclear submarines and planes like the 00:09:03.680 --> 00:09:06.150 align:start position:0% nuclear submarines and planes like the F-22. 00:09:06.150 --> 00:09:06.160 align:start position:0% F-22. 00:09:06.160 --> 00:09:08.150 align:start position:0% F-22. One<00:09:06.480> plane<00:09:06.720> I<00:09:06.880> did<00:09:07.040> not<00:09:07.200> appreciate<00:09:07.760> enough 00:09:08.150 --> 00:09:08.160 align:start position:0% One plane I did not appreciate enough 00:09:08.160 --> 00:09:10.070 align:start position:0% One plane I did not appreciate enough because<00:09:08.399> it's<00:09:08.720> not<00:09:08.880> nearly<00:09:09.120> as<00:09:09.360> sexy<00:09:09.760> is<00:09:09.920> the 00:09:10.070 --> 00:09:10.080 align:start position:0% because it's not nearly as sexy is the 00:09:10.080 --> 00:09:13.509 align:start position:0% because it's not nearly as sexy is the B-52<00:09:11.519> Stratofortress. 00:09:13.509 --> 00:09:13.519 align:start position:0% B-52 Stratofortress. 00:09:13.519 --> 00:09:15.750 align:start position:0% B-52 Stratofortress. Um,<00:09:13.839> which<00:09:14.160> arguably<00:09:14.720> is<00:09:15.120> one<00:09:15.360> of<00:09:15.440> the<00:09:15.600> most 00:09:15.750 --> 00:09:15.760 align:start position:0% Um, which arguably is one of the most 00:09:15.760 --> 00:09:18.790 align:start position:0% Um, which arguably is one of the most successful<00:09:16.959> projects<00:09:17.519> in<00:09:17.920> US<00:09:18.240> military 00:09:18.790 --> 00:09:18.800 align:start position:0% successful projects in US military 00:09:18.800 --> 00:09:20.630 align:start position:0% successful projects in US military history. 00:09:20.630 --> 00:09:20.640 align:start position:0% history. 00:09:20.640 --> 00:09:23.750 align:start position:0% history. Uh,<00:09:20.959> we<00:09:21.200> are<00:09:21.360> still<00:09:21.600> using<00:09:21.839> it<00:09:22.000> today<00:09:23.440> uh<00:09:23.600> in 00:09:23.750 --> 00:09:23.760 align:start position:0% Uh, we are still using it today uh in 00:09:23.760 --> 00:09:25.269 align:start position:0% Uh, we are still using it today uh in Iran. 00:09:25.269 --> 00:09:25.279 align:start position:0% Iran. 00:09:25.279 --> 00:09:28.470 align:start position:0% Iran. It<00:09:25.519> first<00:09:25.760> flew<00:09:26.080> in<00:09:26.320> 1952. 00:09:28.470 --> 00:09:28.480 align:start position:0% It first flew in 1952. 00:09:28.480 --> 00:09:29.990 align:start position:0% It first flew in 1952. Think<00:09:28.720> about<00:09:28.800> that.<00:09:29.040> It<00:09:29.279> first<00:09:29.440> flew<00:09:29.760> during 00:09:29.990 --> 00:09:30.000 align:start position:0% Think about that. It first flew during 00:09:30.000 --> 00:09:32.150 align:start position:0% Think about that. It first flew during the<00:09:30.160> Korean<00:09:30.560> War<00:09:31.040> and<00:09:31.279> we're<00:09:31.519> still<00:09:31.680> using<00:09:31.920> it 00:09:32.150 --> 00:09:32.160 align:start position:0% the Korean War and we're still using it 00:09:32.160 --> 00:09:34.790 align:start position:0% the Korean War and we're still using it nearly<00:09:32.560> 75<00:09:33.120> years<00:09:33.360> later. 00:09:34.790 --> 00:09:34.800 align:start position:0% nearly 75 years later. 00:09:34.800 --> 00:09:37.590 align:start position:0% nearly 75 years later. There's<00:09:35.040> a<00:09:35.200> lot<00:09:35.279> that<00:09:35.519> we<00:09:35.680> can<00:09:35.839> learn<00:09:37.279> about 00:09:37.590 --> 00:09:37.600 align:start position:0% There's a lot that we can learn about 00:09:37.600 --> 00:09:41.509 align:start position:0% There's a lot that we can learn about how<00:09:37.920> a<00:09:38.160> project<00:09:38.480> of<00:09:38.720> that<00:09:39.040> complexity 00:09:41.509 --> 00:09:41.519 align:start position:0% how a project of that complexity 00:09:41.519 --> 00:09:45.590 align:start position:0% how a project of that complexity was<00:09:41.920> able<00:09:42.720> to<00:09:43.279> continue<00:09:44.240> working<00:09:44.959> as<00:09:45.279> long<00:09:45.440> as 00:09:45.590 --> 00:09:45.600 align:start position:0% was able to continue working as long as 00:09:45.600 --> 00:09:47.750 align:start position:0% was able to continue working as long as it<00:09:45.839> has. 00:09:47.750 --> 00:09:47.760 align:start position:0% it has. 00:09:47.760 --> 00:09:49.670 align:start position:0% it has. Last<00:09:48.000> year,<00:09:48.320> I<00:09:48.560> came<00:09:48.800> across<00:09:49.040> a<00:09:49.279> random 00:09:49.670 --> 00:09:49.680 align:start position:0% Last year, I came across a random 00:09:49.680 --> 00:09:51.750 align:start position:0% Last year, I came across a random comment<00:09:50.000> on<00:09:50.240> Hacker<00:09:50.640> News<00:09:50.959> from<00:09:51.200> someone<00:09:51.519> who 00:09:51.750 --> 00:09:51.760 align:start position:0% comment on Hacker News from someone who 00:09:51.760 --> 00:09:54.790 align:start position:0% comment on Hacker News from someone who worked<00:09:52.080> on<00:09:52.240> the<00:09:52.399> B-52, 00:09:54.790 --> 00:09:54.800 align:start position:0% worked on the B-52, 00:09:54.800 --> 00:09:57.030 align:start position:0% worked on the B-52, and<00:09:55.600> he<00:09:55.920> said<00:09:56.080> something<00:09:56.320> that<00:09:56.560> really<00:09:56.800> stuck 00:09:57.030 --> 00:09:57.040 align:start position:0% and he said something that really stuck 00:09:57.040 --> 00:09:58.630 align:start position:0% and he said something that really stuck with<00:09:57.200> me.<00:09:57.440> He<00:09:57.600> said<00:09:57.760> that<00:09:58.000> the<00:09:58.240> thing<00:09:58.320> he 00:09:58.630 --> 00:09:58.640 align:start position:0% with me. He said that the thing he 00:09:58.640 --> 00:10:04.070 align:start position:0% with me. He said that the thing he learned<00:09:59.680> most<00:10:01.040> is<00:10:01.279> that<00:10:01.519> simplicity<00:10:02.080> is<00:10:02.320> king. 00:10:04.070 --> 00:10:04.080 align:start position:0% learned most is that simplicity is king. 00:10:04.080 --> 00:10:06.310 align:start position:0% learned most is that simplicity is king. Complexity<00:10:04.640> is<00:10:04.880> the<00:10:05.040> enemy.<00:10:05.760> That's<00:10:06.000> what<00:10:06.160> he 00:10:06.310 --> 00:10:06.320 align:start position:0% Complexity is the enemy. That's what he 00:10:06.320 --> 00:10:08.230 align:start position:0% Complexity is the enemy. That's what he said. 00:10:08.230 --> 00:10:08.240 align:start position:0% said. 00:10:08.240 --> 00:10:10.710 align:start position:0% said. I<00:10:08.480> imagine<00:10:08.880> anyone<00:10:09.200> who<00:10:09.440> works<00:10:09.680> on<00:10:09.920> a<00:10:10.320> really 00:10:10.710 --> 00:10:10.720 align:start position:0% I imagine anyone who works on a really 00:10:10.720 --> 00:10:12.790 align:start position:0% I imagine anyone who works on a really complicated<00:10:11.440> project<00:10:11.839> will<00:10:12.160> say<00:10:12.320> the<00:10:12.560> exact 00:10:12.790 --> 00:10:12.800 align:start position:0% complicated project will say the exact 00:10:12.800 --> 00:10:14.310 align:start position:0% complicated project will say the exact same<00:10:13.040> thing.<00:10:13.440> Someone<00:10:13.680> who<00:10:13.920> worked<00:10:14.079> on<00:10:14.160> the 00:10:14.310 --> 00:10:14.320 align:start position:0% same thing. Someone who worked on the 00:10:14.320 --> 00:10:18.550 align:start position:0% same thing. Someone who worked on the Apollo<00:10:14.800> program,<00:10:15.920> someone<00:10:16.160> who<00:10:16.399> worked<00:10:16.720> on<00:10:17.279> uh 00:10:18.550 --> 00:10:18.560 align:start position:0% Apollo program, someone who worked on uh 00:10:18.560 --> 00:10:21.350 align:start position:0% Apollo program, someone who worked on uh on<00:10:18.720> a<00:10:18.959> nuclear<00:10:19.360> submarine<00:10:19.839> or<00:10:20.079> whatever.<00:10:21.120> I 00:10:21.350 --> 00:10:21.360 align:start position:0% on a nuclear submarine or whatever. I 00:10:21.360 --> 00:10:22.550 align:start position:0% on a nuclear submarine or whatever. I bet<00:10:21.519> they<00:10:21.680> all<00:10:21.839> would<00:10:22.000> say<00:10:22.240> something 00:10:22.550 --> 00:10:22.560 align:start position:0% bet they all would say something 00:10:22.560 --> 00:10:24.949 align:start position:0% bet they all would say something similar. 00:10:24.949 --> 00:10:24.959 align:start position:0% similar. 00:10:24.959 --> 00:10:27.190 align:start position:0% similar. In<00:10:25.120> the<00:10:25.279> software<00:10:25.680> world,<00:10:25.920> we<00:10:26.160> just<00:10:26.399> don't 00:10:27.190 --> 00:10:27.200 align:start position:0% In the software world, we just don't 00:10:27.200 --> 00:10:30.150 align:start position:0% In the software world, we just don't appreciate<00:10:27.680> this<00:10:28.000> subject<00:10:28.640> enough.<00:10:29.680> It's<00:10:30.000> so 00:10:30.150 --> 00:10:30.160 align:start position:0% appreciate this subject enough. It's so 00:10:30.160 --> 00:10:31.750 align:start position:0% appreciate this subject enough. It's so much<00:10:30.320> easier<00:10:30.560> to<00:10:30.800> talk<00:10:30.959> about<00:10:31.200> concrete 00:10:31.750 --> 00:10:31.760 align:start position:0% much easier to talk about concrete 00:10:31.760 --> 00:10:34.630 align:start position:0% much easier to talk about concrete things<00:10:32.079> like<00:10:32.480> memory<00:10:32.880> safety.<00:10:34.160> You<00:10:34.320> can<00:10:34.480> point 00:10:34.630 --> 00:10:34.640 align:start position:0% things like memory safety. You can point 00:10:34.640 --> 00:10:37.030 align:start position:0% things like memory safety. You can point to<00:10:34.800> that.<00:10:35.680> You<00:10:35.839> can<00:10:36.000> point<00:10:36.160> to<00:10:36.399> memory<00:10:36.720> safety 00:10:37.030 --> 00:10:37.040 align:start position:0% to that. You can point to memory safety 00:10:37.040 --> 00:10:39.030 align:start position:0% to that. You can point to memory safety or<00:10:37.279> performance. 00:10:39.030 --> 00:10:39.040 align:start position:0% or performance. 00:10:39.040 --> 00:10:41.350 align:start position:0% or performance. Um,<00:10:39.440> you<00:10:39.600> can<00:10:39.760> point<00:10:39.920> to<00:10:40.000> a<00:10:40.240> CVE<00:10:40.880> that<00:10:41.120> was 00:10:41.350 --> 00:10:41.360 align:start position:0% Um, you can point to a CVE that was 00:10:41.360 --> 00:10:43.509 align:start position:0% Um, you can point to a CVE that was caused<00:10:41.680> by<00:10:41.920> a<00:10:42.160> memory<00:10:42.480> bug.<00:10:42.880> What<00:10:43.120> you<00:10:43.279> can't 00:10:43.509 --> 00:10:43.519 align:start position:0% caused by a memory bug. What you can't 00:10:43.519 --> 00:10:46.630 align:start position:0% caused by a memory bug. What you can't easily<00:10:44.000> point<00:10:44.240> to<00:10:44.480> is<00:10:44.959> complexity.<00:10:46.399> So, 00:10:46.630 --> 00:10:46.640 align:start position:0% easily point to is complexity. So, 00:10:46.640 --> 00:10:48.230 align:start position:0% easily point to is complexity. So, people<00:10:46.880> just<00:10:47.279> don't<00:10:47.519> talk<00:10:47.680> about<00:10:47.839> it.<00:10:48.079> They 00:10:48.230 --> 00:10:48.240 align:start position:0% people just don't talk about it. They 00:10:48.240 --> 00:10:49.829 align:start position:0% people just don't talk about it. They don't<00:10:48.399> appreciate<00:10:48.800> it.<00:10:49.040> They<00:10:49.279> can<00:10:49.360> only<00:10:49.600> talk 00:10:49.829 --> 00:10:49.839 align:start position:0% don't appreciate it. They can only talk 00:10:49.839 --> 00:10:54.389 align:start position:0% don't appreciate it. They can only talk about<00:10:50.079> the<00:10:51.040> benefits<00:10:52.480> of<00:10:53.200> a<00:10:53.600> very<00:10:53.920> complex 00:10:54.389 --> 00:10:54.399 align:start position:0% about the benefits of a very complex 00:10:54.399 --> 00:10:57.269 align:start position:0% about the benefits of a very complex language<00:10:54.880> like<00:10:55.120> Rust<00:10:55.519> or<00:10:55.760> C++.<00:10:56.640> They<00:10:56.880> can<00:10:56.959> only 00:10:57.269 --> 00:10:57.279 align:start position:0% language like Rust or C++. They can only 00:10:57.279 --> 00:10:58.949 align:start position:0% language like Rust or C++. They can only point<00:10:57.760> because<00:10:58.000> it's<00:10:58.240> much<00:10:58.399> easier<00:10:58.640> to<00:10:58.800> talk 00:10:58.949 --> 00:10:58.959 align:start position:0% point because it's much easier to talk 00:10:58.959 --> 00:11:01.670 align:start position:0% point because it's much easier to talk about<00:10:59.120> those<00:10:59.440> concrete<00:10:59.920> things.<00:11:01.360> Almost 00:11:01.670 --> 00:11:01.680 align:start position:0% about those concrete things. Almost 00:11:01.680 --> 00:11:04.310 align:start position:0% about those concrete things. Almost nobody<00:11:02.160> can<00:11:02.480> talk<00:11:02.720> about 00:11:04.310 --> 00:11:04.320 align:start position:0% nobody can talk about 00:11:04.320 --> 00:11:07.030 align:start position:0% nobody can talk about whether<00:11:04.640> those<00:11:04.959> languages<00:11:05.680> lead<00:11:06.000> to<00:11:06.560> greater 00:11:07.030 --> 00:11:07.040 align:start position:0% whether those languages lead to greater 00:11:07.040 --> 00:11:09.990 align:start position:0% whether those languages lead to greater complexity<00:11:07.600> and<00:11:07.920> whether<00:11:08.160> that<00:11:08.480> complexity 00:11:09.990 --> 00:11:10.000 align:start position:0% complexity and whether that complexity 00:11:10.000 --> 00:11:12.790 align:start position:0% complexity and whether that complexity is<00:11:10.320> harmful<00:11:10.880> in<00:11:11.120> the<00:11:11.279> long<00:11:11.440> run.<00:11:12.240> It's<00:11:12.480> so<00:11:12.640> much 00:11:12.790 --> 00:11:12.800 align:start position:0% is harmful in the long run. It's so much 00:11:12.800 --> 00:11:14.069 align:start position:0% is harmful in the long run. It's so much harder<00:11:13.040> to<00:11:13.200> talk<00:11:13.360> about<00:11:13.519> that.<00:11:13.760> It's<00:11:13.920> so 00:11:14.069 --> 00:11:14.079 align:start position:0% harder to talk about that. It's so 00:11:14.079 --> 00:11:15.670 align:start position:0% harder to talk about that. It's so abstract. 00:11:15.670 --> 00:11:15.680 align:start position:0% abstract. 00:11:15.680 --> 00:11:17.269 align:start position:0% abstract. And<00:11:15.839> yet<00:11:16.079> I<00:11:16.240> maintain<00:11:16.640> it's<00:11:16.880> the<00:11:17.120> most 00:11:17.269 --> 00:11:17.279 align:start position:0% And yet I maintain it's the most 00:11:17.279 --> 00:11:21.110 align:start position:0% And yet I maintain it's the most important<00:11:18.640> topic<00:11:19.200> in<00:11:19.519> our<00:11:19.760> field,<00:11:20.640> arguably 00:11:21.110 --> 00:11:21.120 align:start position:0% important topic in our field, arguably 00:11:21.120 --> 00:11:23.750 align:start position:0% important topic in our field, arguably in<00:11:21.360> any<00:11:21.600> field. 00:11:23.750 --> 00:11:23.760 align:start position:0% in any field. 00:11:23.760 --> 00:11:25.990 align:start position:0% in any field. But<00:11:24.000> our<00:11:24.320> field,<00:11:24.720> I<00:11:25.040> think,<00:11:25.279> has<00:11:25.600> less 00:11:25.990 --> 00:11:26.000 align:start position:0% But our field, I think, has less 00:11:26.000 --> 00:11:28.550 align:start position:0% But our field, I think, has less appreciation<00:11:26.720> for<00:11:26.959> it. 00:11:28.550 --> 00:11:28.560 align:start position:0% appreciation for it. 00:11:28.560 --> 00:11:31.350 align:start position:0% appreciation for it. I<00:11:28.720> think<00:11:28.880> Rich<00:11:29.120> Hickey<00:11:29.839> probably 00:11:31.350 --> 00:11:31.360 align:start position:0% I think Rich Hickey probably 00:11:31.360 --> 00:11:34.870 align:start position:0% I think Rich Hickey probably did<00:11:31.600> the<00:11:31.839> most<00:11:32.560> to<00:11:33.519> improve<00:11:34.000> our<00:11:34.320> ability<00:11:34.640> to 00:11:34.870 --> 00:11:34.880 align:start position:0% did the most to improve our ability to 00:11:34.880 --> 00:11:37.030 align:start position:0% did the most to improve our ability to talk<00:11:35.040> about<00:11:35.279> it. 00:11:37.030 --> 00:11:37.040 align:start position:0% talk about it. 00:11:37.040 --> 00:11:39.269 align:start position:0% talk about it. Um,<00:11:37.600> which<00:11:37.839> is<00:11:37.920> why<00:11:38.079> I<00:11:38.240> got<00:11:38.399> into<00:11:38.640> closure<00:11:39.040> back 00:11:39.269 --> 00:11:39.279 align:start position:0% Um, which is why I got into closure back 00:11:39.279 --> 00:11:43.269 align:start position:0% Um, which is why I got into closure back then.<00:11:40.720> But<00:11:40.959> here<00:11:41.120> we<00:11:41.360> are<00:11:41.680> 15<00:11:42.000> years<00:11:42.240> later<00:11:42.640> and 00:11:43.269 --> 00:11:43.279 align:start position:0% then. But here we are 15 years later and 00:11:43.279 --> 00:11:45.430 align:start position:0% then. But here we are 15 years later and um,<00:11:43.680> almost<00:11:44.079> nobody<00:11:44.399> in<00:11:44.560> our<00:11:44.720> field<00:11:45.040> can<00:11:45.279> talk 00:11:45.430 --> 00:11:45.440 align:start position:0% um, almost nobody in our field can talk 00:11:45.440 --> 00:11:51.990 align:start position:0% um, almost nobody in our field can talk about<00:11:45.680> it. 00:11:51.990 --> 00:11:52.000 align:start position:0% 00:11:52.000 --> 00:11:53.350 align:start position:0% So,<00:11:52.240> we're<00:11:52.480> about<00:11:52.640> to<00:11:52.800> find<00:11:52.959> out<00:11:53.120> how 00:11:53.350 --> 00:11:53.360 align:start position:0% So, we're about to find out how 00:11:53.360 --> 00:11:56.150 align:start position:0% So, we're about to find out how important<00:11:53.680> this<00:11:53.920> subject<00:11:54.320> is. 00:11:56.150 --> 00:11:56.160 align:start position:0% important this subject is. 00:11:56.160 --> 00:11:58.550 align:start position:0% important this subject is. A<00:11:56.399> million<00:11:56.720> [ __ ]<00:11:57.200> lines.<00:11:57.920> Are<00:11:58.160> you<00:11:58.320> kidding 00:11:58.550 --> 00:11:58.560 align:start position:0% A million [ __ ] lines. Are you kidding 00:11:58.560 --> 00:12:01.430 align:start position:0% A million [ __ ] lines. Are you kidding me? 00:12:01.430 --> 00:12:01.440 align:start position:0% me? 00:12:01.440 --> 00:12:03.430 align:start position:0% me? I<00:12:01.680> think<00:12:01.760> the<00:12:01.920> Rust<00:12:02.240> compiler<00:12:02.640> itself<00:12:02.959> is<00:12:03.200> 2 00:12:03.430 --> 00:12:03.440 align:start position:0% I think the Rust compiler itself is 2 00:12:03.440 --> 00:12:06.310 align:start position:0% I think the Rust compiler itself is 2 million<00:12:03.680> lines.<00:12:04.720> And<00:12:04.959> that's<00:12:05.519> a<00:12:05.760> Rust 00:12:06.310 --> 00:12:06.320 align:start position:0% million lines. And that's a Rust 00:12:06.320 --> 00:12:08.389 align:start position:0% million lines. And that's a Rust compiler. 00:12:08.389 --> 00:12:08.399 align:start position:0% compiler. 00:12:08.399 --> 00:12:11.030 align:start position:0% compiler. Bun<00:12:08.800> is<00:12:08.959> a<00:12:09.200> [ __ ]<00:12:09.760> wrapper<00:12:10.560> around 00:12:11.030 --> 00:12:11.040 align:start position:0% Bun is a [ __ ] wrapper around 00:12:11.040 --> 00:12:13.750 align:start position:0% Bun is a [ __ ] wrapper around JavaScript<00:12:11.680> 4<00:12:12.160> and<00:12:12.320> it's<00:12:12.639> already<00:12:13.120> half<00:12:13.440> the 00:12:13.750 --> 00:12:13.760 align:start position:0% JavaScript 4 and it's already half the 00:12:13.760 --> 00:12:16.710 align:start position:0% JavaScript 4 and it's already half the size<00:12:14.320> of<00:12:14.560> the<00:12:14.720> Rust<00:12:15.120> compiler. 00:12:16.710 --> 00:12:16.720 align:start position:0% size of the Rust compiler. 00:12:16.720 --> 00:12:19.269 align:start position:0% size of the Rust compiler. Am<00:12:16.880> I<00:12:17.040> going<00:12:17.279> insane<00:12:17.680> here?<00:12:17.920> Is<00:12:18.160> this<00:12:18.399> not<00:12:18.959> like 00:12:19.269 --> 00:12:19.279 align:start position:0% Am I going insane here? Is this not like 00:12:19.279 --> 00:12:28.310 align:start position:0% Am I going insane here? Is this not like completely<00:12:19.839> absurd? 00:12:28.310 --> 00:12:28.320 align:start position:0% 00:12:28.320 --> 00:12:31.990 align:start position:0% I'm<00:12:28.639> fascinated,<00:12:29.279> guys.<00:12:30.240> Look,<00:12:30.880> um<00:12:31.519> like<00:12:31.760> I 00:12:31.990 --> 00:12:32.000 align:start position:0% I'm fascinated, guys. Look, um like I 00:12:32.000 --> 00:12:35.910 align:start position:0% I'm fascinated, guys. Look, um like I said,<00:12:33.120> um<00:12:34.399> the<00:12:34.639> the<00:12:34.959> initial<00:12:35.279> rewrite<00:12:35.600> is<00:12:35.760> the 00:12:35.910 --> 00:12:35.920 align:start position:0% said, um the the initial rewrite is the 00:12:35.920 --> 00:12:37.829 align:start position:0% said, um the the initial rewrite is the easy<00:12:36.160> part.<00:12:36.560> The<00:12:36.959> interesting<00:12:37.360> question<00:12:37.600> is 00:12:37.829 --> 00:12:37.839 align:start position:0% easy part. The interesting question is 00:12:37.839 --> 00:12:39.910 align:start position:0% easy part. The interesting question is what<00:12:38.079> happens<00:12:38.399> next?<00:12:38.959> Can<00:12:39.200> this<00:12:39.440> actually<00:12:39.680> be 00:12:39.910 --> 00:12:39.920 align:start position:0% what happens next? Can this actually be 00:12:39.920 --> 00:12:42.470 align:start position:0% what happens next? Can this actually be maintained<00:12:40.399> or<00:12:40.639> not? 00:12:42.470 --> 00:12:42.480 align:start position:0% maintained or not? 00:12:42.480 --> 00:12:44.310 align:start position:0% maintained or not? you<00:12:42.720> know, 00:12:44.310 --> 00:12:44.320 align:start position:0% you know, 00:12:44.320 --> 00:12:47.750 align:start position:0% you know, um<00:12:45.680> I<00:12:46.000> I<00:12:46.240> I'<00:12:46.399> I've<00:12:46.800> already<00:12:47.120> stated<00:12:47.519> my 00:12:47.750 --> 00:12:47.760 align:start position:0% um I I I' I've already stated my 00:12:47.760 --> 00:12:49.509 align:start position:0% um I I I' I've already stated my position 00:12:49.509 --> 00:12:49.519 align:start position:0% position 00:12:49.519 --> 00:12:53.350 align:start position:0% position in<00:12:49.760> the<00:12:49.920> last<00:12:50.160> video.<00:12:51.440> Um 00:12:53.350 --> 00:12:53.360 align:start position:0% in the last video. Um 00:12:53.360 --> 00:12:56.550 align:start position:0% in the last video. Um I<00:12:53.680> think<00:12:53.839> complexity<00:12:54.480> compounds<00:12:55.519> and<00:12:56.320> a 00:12:56.550 --> 00:12:56.560 align:start position:0% I think complexity compounds and a 00:12:56.560 --> 00:12:58.230 align:start position:0% I think complexity compounds and a codebase<00:12:57.040> like<00:12:57.200> that<00:12:57.440> will<00:12:57.680> get<00:12:57.839> harder<00:12:58.079> and 00:12:58.230 --> 00:12:58.240 align:start position:0% codebase like that will get harder and 00:12:58.240 --> 00:13:02.230 align:start position:0% codebase like that will get harder and harder<00:12:58.720> to<00:12:59.440> maintain<00:13:00.000> over<00:13:00.639> over<00:13:01.040> time,<00:13:02.000> even 00:13:02.230 --> 00:13:02.240 align:start position:0% harder to maintain over over time, even 00:13:02.240 --> 00:13:06.710 align:start position:0% harder to maintain over over time, even by<00:13:02.800> frontier<00:13:03.360> AI<00:13:03.760> models. 00:13:06.710 --> 00:13:06.720 align:start position:0% by frontier AI models. 00:13:06.720 --> 00:13:09.430 align:start position:0% by frontier AI models. But<00:13:07.279> that's<00:13:07.519> all<00:13:07.839> theory. 00:13:09.430 --> 00:13:09.440 align:start position:0% But that's all theory. 00:13:09.440 --> 00:13:12.629 align:start position:0% But that's all theory. I<00:13:09.680> have<00:13:09.839> to<00:13:10.079> hand<00:13:10.240> it<00:13:10.399> to<00:13:10.560> them<00:13:11.120> because<00:13:12.399> the 00:13:12.629 --> 00:13:12.639 align:start position:0% I have to hand it to them because the 00:13:12.639 --> 00:13:15.509 align:start position:0% I have to hand it to them because the bun<00:13:13.040> team<00:13:13.200> is<00:13:14.000> um 00:13:15.509 --> 00:13:15.519 align:start position:0% bun team is um 00:13:15.519 --> 00:13:18.470 align:start position:0% bun team is um is<00:13:15.760> is<00:13:16.000> fearlessly<00:13:17.120> marching<00:13:17.519> forward<00:13:17.920> here 00:13:18.470 --> 00:13:18.480 align:start position:0% is is fearlessly marching forward here 00:13:18.480 --> 00:13:20.310 align:start position:0% is is fearlessly marching forward here and<00:13:18.880> we're<00:13:19.120> all<00:13:19.279> going<00:13:19.360> to<00:13:19.519> benefit<00:13:19.839> from<00:13:20.079> this 00:13:20.310 --> 00:13:20.320 align:start position:0% and we're all going to benefit from this 00:13:20.320 --> 00:13:22.069 align:start position:0% and we're all going to benefit from this as<00:13:20.560> a 00:13:22.069 --> 00:13:22.079 align:start position:0% as a 00:13:22.079 --> 00:13:24.710 align:start position:0% as a test<00:13:22.399> case,<00:13:23.519> you<00:13:23.680> know.<00:13:24.000> So,<00:13:24.240> I<00:13:24.399> got<00:13:24.480> to<00:13:24.560> give 00:13:24.710 --> 00:13:24.720 align:start position:0% test case, you know. So, I got to give 00:13:24.720 --> 00:13:27.990 align:start position:0% test case, you know. So, I got to give him<00:13:24.880> props<00:13:25.120> for<00:13:25.360> that.<00:13:26.720> Um<00:13:27.120> I<00:13:27.360> I'm<00:13:27.680> going<00:13:27.839> to 00:13:27.990 --> 00:13:28.000 align:start position:0% him props for that. Um I I'm going to 00:13:28.000 --> 00:13:29.590 align:start position:0% him props for that. Um I I'm going to pay<00:13:28.160> attention.<00:13:28.800> I<00:13:28.959> want<00:13:29.120> to<00:13:29.279> see<00:13:29.360> what 00:13:29.590 --> 00:13:29.600 align:start position:0% pay attention. I want to see what 00:13:29.600 --> 00:13:31.350 align:start position:0% pay attention. I want to see what happens. 00:13:31.350 --> 00:13:31.360 align:start position:0% happens. 00:13:31.360 --> 00:13:34.069 align:start position:0% happens. Um, 00:13:34.069 --> 00:13:34.079 align:start position:0% Um, 00:13:34.079 --> 00:13:35.829 align:start position:0% Um, if<00:13:34.320> anything, 00:13:35.829 --> 00:13:35.839 align:start position:0% if anything, 00:13:35.839 --> 00:13:37.750 align:start position:0% if anything, I<00:13:36.079> just<00:13:36.240> want<00:13:36.480> people<00:13:36.639> to<00:13:36.880> talk<00:13:37.120> about 00:13:37.750 --> 00:13:37.760 align:start position:0% I just want people to talk about 00:13:37.760 --> 00:13:41.509 align:start position:0% I just want people to talk about simplicity<00:13:38.639> and<00:13:38.959> complexity<00:13:39.680> a<00:13:40.000> lot<00:13:40.160> more. 00:13:41.509 --> 00:13:41.519 align:start position:0% simplicity and complexity a lot more. 00:13:41.519 --> 00:13:44.069 align:start position:0% simplicity and complexity a lot more. And<00:13:41.920> maybe<00:13:42.160> this<00:13:42.399> will<00:13:42.639> trigger<00:13:43.440> that<00:13:43.760> kind<00:13:43.920> of 00:13:44.069 --> 00:13:44.079 align:start position:0% And maybe this will trigger that kind of 00:13:44.079 --> 00:13:45.910 align:start position:0% And maybe this will trigger that kind of discussion<00:13:44.560> a<00:13:44.880> lot<00:13:44.959> more<00:13:45.360> because<00:13:45.680> people 00:13:45.910 --> 00:13:45.920 align:start position:0% discussion a lot more because people 00:13:45.920 --> 00:13:47.910 align:start position:0% discussion a lot more because people just<00:13:46.160> don't<00:13:46.399> talk<00:13:46.639> about<00:13:46.800> it<00:13:46.959> enough<00:13:47.440> in<00:13:47.680> our 00:13:47.910 --> 00:13:47.920 align:start position:0% just don't talk about it enough in our 00:13:47.920 --> 00:13:50.870 align:start position:0% just don't talk about it enough in our field.<00:13:48.880> They<00:13:49.120> they<00:13:49.519> barely<00:13:50.240> understand<00:13:50.720> what 00:13:50.870 --> 00:13:50.880 align:start position:0% field. They they barely understand what 00:13:50.880 --> 00:13:54.949 align:start position:0% field. They they barely understand what it<00:13:51.120> even<00:13:51.360> means.<00:13:52.800> Um,<00:13:53.200> but<00:13:53.519> we're<00:13:53.760> we're 00:13:54.949 --> 00:13:54.959 align:start position:0% it even means. Um, but we're we're 00:13:54.959 --> 00:13:59.750 align:start position:0% it even means. Um, but we're we're rapidly<00:13:55.680> reaching<00:13:56.079> a<00:13:56.399> point<00:13:56.720> where<00:13:57.839> um<00:13:58.959> you 00:13:59.750 --> 00:13:59.760 align:start position:0% rapidly reaching a point where um you 00:13:59.760 --> 00:14:02.710 align:start position:0% rapidly reaching a point where um you you<00:14:00.160> have<00:14:00.320> to<00:14:00.480> talk<00:14:00.639> about<00:14:00.800> it 00:14:02.710 --> 00:14:02.720 align:start position:0% you have to talk about it 00:14:02.720 --> 00:14:05.269 align:start position:0% you have to talk about it a<00:14:03.040> million<00:14:03.360> [ __ ]<00:14:03.760> lines.<00:14:04.639> Are<00:14:04.880> you<00:14:04.959> kidding 00:14:05.269 --> 00:14:05.279 align:start position:0% a million [ __ ] lines. Are you kidding 00:14:05.279 --> 00:14:13.189 align:start position:0% a million [ __ ] lines. Are you kidding me? 00:14:13.189 --> 00:14:13.199 align:start position:0% 00:14:13.199 --> 00:14:14.710 align:start position:0% Yeah. 00:14:14.710 --> 00:14:14.720 align:start position:0% Yeah. 00:14:14.720 --> 00:14:18.710 align:start position:0% Yeah. Well,<00:14:16.000> um 00:14:18.710 --> 00:14:18.720 align:start position:0% Well, um 00:14:18.720 --> 00:14:21.430 align:start position:0% Well, um we'll<00:14:18.959> see<00:14:19.040> if<00:14:19.199> I<00:14:19.360> turn<00:14:19.519> out<00:14:19.680> to<00:14:19.839> be<00:14:20.000> right. 00:14:21.430 --> 00:14:21.440 align:start position:0% we'll see if I turn out to be right. 00:14:21.440 --> 00:14:25.600 align:start position:0% we'll see if I turn out to be right. If<00:14:21.760> not,<00:14:22.000> then<00:14:22.560> screw<00:14:22.959> me.