WEBVTT Kind: captions Language: en 00:00:00.080 --> 00:00:04.190 align:start position:0% this<00:00:00.160> is<00:00:00.320> my<00:00:01.040> friend<00:00:02.040> hey<00:00:02.600> everybody<00:00:03.600> um<00:00:04.040> great 00:00:04.190 --> 00:00:04.200 align:start position:0% this is my friend hey everybody um great 00:00:04.200 --> 00:00:05.670 align:start position:0% this is my friend hey everybody um great to<00:00:04.279> be<00:00:04.400> here<00:00:04.480> in<00:00:04.560> Port<00:00:04.839> this<00:00:04.920> is 00:00:05.670 --> 00:00:05.680 align:start position:0% to be here in Port this is 00:00:05.680 --> 00:00:09.549 align:start position:0% to be here in Port this is awesome<00:00:06.680> happy 00:00:09.549 --> 00:00:09.559 align:start position:0% 00:00:09.559 --> 00:00:11.830 align:start position:0% P20<00:00:10.559> what<00:00:10.679> does<00:00:10.840> that 00:00:11.830 --> 00:00:11.840 align:start position:0% P20 what does that 00:00:11.840 --> 00:00:14.709 align:start position:0% P20 what does that mean<00:00:12.840> somebody's<00:00:13.280> birthday 00:00:14.709 --> 00:00:14.719 align:start position:0% mean somebody's birthday 00:00:14.719 --> 00:00:18.470 align:start position:0% mean somebody's birthday oh<00:00:15.719> um<00:00:16.480> welcome<00:00:16.800> here<00:00:17.240> uh<00:00:17.400> we<00:00:17.520> work<00:00:17.720> at<00:00:17.960> e 00:00:18.470 --> 00:00:18.480 align:start position:0% oh um welcome here uh we work at e 00:00:18.480 --> 00:00:19.470 align:start position:0% oh um welcome here uh we work at e together<00:00:18.720> and<00:00:18.880> a<00:00:18.960> lot<00:00:19.039> of<00:00:19.119> the<00:00:19.240> stuff<00:00:19.359> you're 00:00:19.470 --> 00:00:19.480 align:start position:0% together and a lot of the stuff you're 00:00:19.480 --> 00:00:21.509 align:start position:0% together and a lot of the stuff you're going<00:00:19.560> to<00:00:19.640> see<00:00:19.800> we<00:00:19.960> use<00:00:20.160> we<00:00:20.279> use<00:00:20.439> for<00:00:20.640> work 00:00:21.509 --> 00:00:21.519 align:start position:0% going to see we use we use for work 00:00:21.519 --> 00:00:22.950 align:start position:0% going to see we use we use for work we're<00:00:21.800> fortunate<00:00:22.199> enough<00:00:22.320> to<00:00:22.480> also<00:00:22.720> get<00:00:22.880> the 00:00:22.950 --> 00:00:22.960 align:start position:0% we're fortunate enough to also get the 00:00:22.960 --> 00:00:25.910 align:start position:0% we're fortunate enough to also get the word<00:00:23.160> you<00:00:23.240> know<00:00:23.880> time<00:00:24.199> so<00:00:24.359> it's<00:00:24.760> awesome<00:00:25.760> uh 00:00:25.910 --> 00:00:25.920 align:start position:0% word you know time so it's awesome uh 00:00:25.920 --> 00:00:27.310 align:start position:0% word you know time so it's awesome uh couple<00:00:26.199> notes 00:00:27.310 --> 00:00:27.320 align:start position:0% couple notes 00:00:27.320 --> 00:00:30.669 align:start position:0% couple notes first<00:00:28.320> um<00:00:28.880> we<00:00:29.119> have<00:00:29.400> boot<00:00:29.960> sckers<00:00:30.400> as<00:00:30.480> you<00:00:30.560> can 00:00:30.669 --> 00:00:30.679 align:start position:0% first um we have boot sckers as you can 00:00:30.679 --> 00:00:32.950 align:start position:0% first um we have boot sckers as you can see<00:00:30.840> we<00:00:30.960> have<00:00:31.080> a<00:00:31.199> kind<00:00:31.279> of<00:00:31.439> cool<00:00:32.200> logo<00:00:32.439> on<00:00:32.599> icon 00:00:32.950 --> 00:00:32.960 align:start position:0% see we have a kind of cool logo on icon 00:00:32.960 --> 00:00:34.549 align:start position:0% see we have a kind of cool logo on icon that's<00:00:33.160> courtesy<00:00:33.520> of<00:00:33.640> our<00:00:33.920> employer<00:00:34.320> it's<00:00:34.440> a 00:00:34.549 --> 00:00:34.559 align:start position:0% that's courtesy of our employer it's a 00:00:34.559 --> 00:00:37.190 align:start position:0% that's courtesy of our employer it's a little<00:00:34.800> cat<00:00:35.120> in<00:00:35.239> a<00:00:35.360> boot<00:00:36.200> makes<00:00:36.480> to<00:00:36.760> sense 00:00:37.190 --> 00:00:37.200 align:start position:0% little cat in a boot makes to sense 00:00:37.200 --> 00:00:39.590 align:start position:0% little cat in a boot makes to sense right<00:00:38.200> um<00:00:38.520> and<00:00:38.640> we<00:00:38.760> have<00:00:38.879> those<00:00:39.040> stickers<00:00:39.360> so 00:00:39.590 --> 00:00:39.600 align:start position:0% right um and we have those stickers so 00:00:39.600 --> 00:00:40.830 align:start position:0% right um and we have those stickers so if<00:00:39.680> you<00:00:39.760> have<00:00:39.960> questions<00:00:40.280> we<00:00:40.360> may<00:00:40.480> or<00:00:40.600> may<00:00:40.680> not 00:00:40.830 --> 00:00:40.840 align:start position:0% if you have questions we may or may not 00:00:40.840 --> 00:00:41.910 align:start position:0% if you have questions we may or may not have<00:00:40.960> questions<00:00:41.200> at<00:00:41.280> the<00:00:41.360> end<00:00:41.480> of<00:00:41.559> the<00:00:41.719> talk 00:00:41.910 --> 00:00:41.920 align:start position:0% have questions at the end of the talk 00:00:41.920 --> 00:00:43.310 align:start position:0% have questions at the end of the talk but<00:00:42.079> feel<00:00:42.239> free<00:00:42.440> if<00:00:42.559> you<00:00:42.680> see<00:00:42.800> us<00:00:42.920> just<00:00:43.039> to<00:00:43.160> pull 00:00:43.310 --> 00:00:43.320 align:start position:0% but feel free if you see us just to pull 00:00:43.320 --> 00:00:45.950 align:start position:0% but feel free if you see us just to pull us<00:00:43.480> aside<00:00:44.280> pester<00:00:44.719> us<00:00:44.920> with<00:00:45.120> your<00:00:45.480> your 00:00:45.950 --> 00:00:45.960 align:start position:0% us aside pester us with your your 00:00:45.960 --> 00:00:47.790 align:start position:0% us aside pester us with your your trickiest<00:00:46.440> questions<00:00:47.239> um<00:00:47.399> that's<00:00:47.520> the<00:00:47.640> reason 00:00:47.790 --> 00:00:47.800 align:start position:0% trickiest questions um that's the reason 00:00:47.800 --> 00:00:48.869 align:start position:0% trickiest questions um that's the reason we're<00:00:47.920> here<00:00:48.039> at<00:00:48.160> conference<00:00:48.440> is<00:00:48.520> to<00:00:48.640> hang<00:00:48.760> out 00:00:48.869 --> 00:00:48.879 align:start position:0% we're here at conference is to hang out 00:00:48.879 --> 00:00:50.150 align:start position:0% we're here at conference is to hang out with<00:00:49.039> people<00:00:49.239> and<00:00:49.480> answer<00:00:49.760> questions<00:00:50.039> and 00:00:50.150 --> 00:00:50.160 align:start position:0% with people and answer questions and 00:00:50.160 --> 00:00:51.549 align:start position:0% with people and answer questions and learn<00:00:50.399> new<00:00:50.600> stuff<00:00:50.800> so<00:00:50.960> feel<00:00:51.160> free<00:00:51.320> to<00:00:51.440> talk 00:00:51.549 --> 00:00:51.559 align:start position:0% learn new stuff so feel free to talk 00:00:51.559 --> 00:00:54.709 align:start position:0% learn new stuff so feel free to talk with<00:00:51.800> us<00:00:52.800> and<00:00:53.079> we<00:00:53.199> have<00:00:53.320> tons<00:00:53.520> of<00:00:53.640> stickers<00:00:54.079> too 00:00:54.709 --> 00:00:54.719 align:start position:0% with us and we have tons of stickers too 00:00:54.719 --> 00:00:55.830 align:start position:0% with us and we have tons of stickers too and<00:00:55.000> um<00:00:55.120> there<00:00:55.199> are<00:00:55.239> a<00:00:55.320> couple<00:00:55.520> things<00:00:55.680> you<00:00:55.760> can 00:00:55.830 --> 00:00:55.840 align:start position:0% and um there are a couple things you can 00:00:55.840 --> 00:00:56.830 align:start position:0% and um there are a couple things you can do<00:00:55.920> with<00:00:56.000> the<00:00:56.120> stickers<00:00:56.399> you<00:00:56.520> can<00:00:56.640> like<00:00:56.760> put 00:00:56.830 --> 00:00:56.840 align:start position:0% do with the stickers you can like put 00:00:56.840 --> 00:00:58.310 align:start position:0% do with the stickers you can like put them<00:00:56.960> on<00:00:57.039> your<00:00:57.199> laptop<00:00:57.719> or<00:00:57.879> some<00:00:58.000> people<00:00:58.199> put 00:00:58.310 --> 00:00:58.320 align:start position:0% them on your laptop or some people put 00:00:58.320 --> 00:01:00.270 align:start position:0% them on your laptop or some people put them<00:00:58.399> on<00:00:58.519> their<00:00:58.680> car<00:00:59.440> actually<00:00:59.640> a<00:00:59.760> new<00:01:00.079> thing<00:01:00.239> I 00:01:00.270 --> 00:01:00.280 align:start position:0% them on their car actually a new thing I 00:01:00.280 --> 00:01:01.229 align:start position:0% them on their car actually a new thing I mean<00:01:00.399> it<00:01:00.480> could<00:01:00.600> be<00:01:00.719> a<00:01:00.879> thing<00:01:01.000> it's<00:01:01.120> just 00:01:01.229 --> 00:01:01.239 align:start position:0% mean it could be a thing it's just 00:01:01.239 --> 00:01:03.709 align:start position:0% mean it could be a thing it's just putting<00:01:01.440> them<00:01:01.559> on<00:01:01.680> newborn<00:01:02.519> children<00:01:03.519> maybe 00:01:03.709 --> 00:01:03.719 align:start position:0% putting them on newborn children maybe 00:01:03.719 --> 00:01:05.510 align:start position:0% putting them on newborn children maybe that's<00:01:03.840> a<00:01:03.960> thing<00:01:04.080> we<00:01:04.199> want<00:01:04.320> to<00:01:04.479> do<00:01:04.720> I<00:01:04.760> don't 00:01:05.510 --> 00:01:05.520 align:start position:0% that's a thing we want to do I don't 00:01:05.520 --> 00:01:08.190 align:start position:0% that's a thing we want to do I don't know<00:01:06.520> um<00:01:07.119> the<00:01:07.400> final<00:01:07.640> note<00:01:07.840> is<00:01:07.920> we're<00:01:08.040> going<00:01:08.119> to 00:01:08.190 --> 00:01:08.200 align:start position:0% know um the final note is we're going to 00:01:08.200 --> 00:01:09.910 align:start position:0% know um the final note is we're going to do<00:01:08.320> a<00:01:08.400> lot<00:01:08.520> of<00:01:08.759> interactive<00:01:09.280> demonstration 00:01:09.910 --> 00:01:09.920 align:start position:0% do a lot of interactive demonstration 00:01:09.920 --> 00:01:13.550 align:start position:0% do a lot of interactive demonstration coding<00:01:10.360> which<00:01:10.840> is<00:01:11.840> fairly<00:01:12.200> dangerous<00:01:12.799> always 00:01:13.550 --> 00:01:13.560 align:start position:0% coding which is fairly dangerous always 00:01:13.560 --> 00:01:15.109 align:start position:0% coding which is fairly dangerous always um<00:01:13.759> so<00:01:14.000> as<00:01:14.080> a<00:01:14.240> precaution<00:01:14.720> we've<00:01:14.880> done<00:01:15.000> a 00:01:15.109 --> 00:01:15.119 align:start position:0% um so as a precaution we've done a 00:01:15.119 --> 00:01:16.390 align:start position:0% um so as a precaution we've done a couple<00:01:15.360> things<00:01:15.560> including<00:01:15.960> you<00:01:16.040> know<00:01:16.159> turning 00:01:16.390 --> 00:01:16.400 align:start position:0% couple things including you know turning 00:01:16.400 --> 00:01:18.270 align:start position:0% couple things including you know turning the<00:01:16.560> Wi-Fi<00:01:16.880> off<00:01:17.040> on<00:01:17.159> this<00:01:17.360> machine<00:01:17.759> and 00:01:18.270 --> 00:01:18.280 align:start position:0% the Wi-Fi off on this machine and 00:01:18.280 --> 00:01:20.870 align:start position:0% the Wi-Fi off on this machine and prepared<00:01:18.880> screenshots<00:01:19.320> of<00:01:19.520> code<00:01:20.520> but<00:01:20.680> most 00:01:20.870 --> 00:01:20.880 align:start position:0% prepared screenshots of code but most 00:01:20.880 --> 00:01:22.950 align:start position:0% prepared screenshots of code but most importantly<00:01:21.320> our<00:01:21.479> friend<00:01:21.759> and<00:01:21.960> Associate<00:01:22.720> uh 00:01:22.950 --> 00:01:22.960 align:start position:0% importantly our friend and Associate uh 00:01:22.960 --> 00:01:25.190 align:start position:0% importantly our friend and Associate uh Dave<00:01:23.240> Arwood<00:01:23.600> is<00:01:23.680> in<00:01:23.799> the<00:01:23.960> audience<00:01:24.600> and<00:01:24.920> after 00:01:25.190 --> 00:01:25.200 align:start position:0% Dave Arwood is in the audience and after 00:01:25.200 --> 00:01:26.990 align:start position:0% Dave Arwood is in the audience and after any<00:01:25.439> catastrophic<00:01:26.000> failure<00:01:26.439> his<00:01:26.640> task<00:01:26.880> will 00:01:26.990 --> 00:01:27.000 align:start position:0% any catastrophic failure his task will 00:01:27.000 --> 00:01:29.469 align:start position:0% any catastrophic failure his task will be<00:01:27.119> to<00:01:27.200> start<00:01:27.400> with<00:01:27.560> slow<00:01:27.840> clap<00:01:28.799> so<00:01:28.920> I<00:01:29.040> just<00:01:29.240> ask 00:01:29.469 --> 00:01:29.479 align:start position:0% be to start with slow clap so I just ask 00:01:29.479 --> 00:01:31.469 align:start position:0% be to start with slow clap so I just ask you<00:01:29.640> join<00:01:30.119> him<00:01:30.759> and<00:01:30.880> we<00:01:30.960> can<00:01:31.119> lighten<00:01:31.360> the 00:01:31.469 --> 00:01:31.479 align:start position:0% you join him and we can lighten the 00:01:31.479 --> 00:01:35.590 align:start position:0% you join him and we can lighten the moment<00:01:32.479> that<00:01:32.880> way<00:01:33.880> anyway<00:01:34.680> I'll<00:01:34.880> I'll<00:01:35.079> let 00:01:35.590 --> 00:01:35.600 align:start position:0% moment that way anyway I'll I'll let 00:01:35.600 --> 00:01:37.630 align:start position:0% moment that way anyway I'll I'll let Misha<00:01:35.920> actually<00:01:36.119> get<00:01:36.200> to<00:01:36.320> the<00:01:36.399> real 00:01:37.630 --> 00:01:37.640 align:start position:0% Misha actually get to the real 00:01:37.640 --> 00:01:39.990 align:start position:0% Misha actually get to the real presentation<00:01:38.640> yeah<00:01:38.960> a<00:01:39.119> new<00:01:39.399> build<00:01:39.680> tool 00:01:39.990 --> 00:01:40.000 align:start position:0% presentation yeah a new build tool 00:01:40.000 --> 00:01:41.350 align:start position:0% presentation yeah a new build tool another 00:01:41.350 --> 00:01:41.360 align:start position:0% another 00:01:41.360 --> 00:01:46.540 align:start position:0% another one<00:01:42.360> uh<00:01:42.840> such<00:01:43.240> excit<00:01:44.240> yeah<00:01:45.240> thank<00:01:45.439> you<00:01:45.960> thank 00:01:46.540 --> 00:01:46.550 align:start position:0% one uh such excit yeah thank you thank 00:01:46.550 --> 00:01:48.630 align:start position:0% one uh such excit yeah thank you thank [Applause] 00:01:48.630 --> 00:01:48.640 align:start position:0% [Applause] 00:01:48.640 --> 00:01:51.910 align:start position:0% [Applause] you<00:01:49.640> but<00:01:49.960> uh<00:01:50.719> I<00:01:50.799> mean<00:01:50.960> anybody<00:01:51.320> who<00:01:51.520> who<00:01:51.640> makes 00:01:51.910 --> 00:01:51.920 align:start position:0% you but uh I mean anybody who who makes 00:01:51.920 --> 00:01:53.709 align:start position:0% you but uh I mean anybody who who makes applications<00:01:52.439> nowadays<00:01:52.840> is<00:01:53.000> involved<00:01:53.439> with 00:01:53.709 --> 00:01:53.719 align:start position:0% applications nowadays is involved with 00:01:53.719 --> 00:01:55.950 align:start position:0% applications nowadays is involved with you<00:01:53.880> know<00:01:54.560> complicated<00:01:55.200> things<00:01:55.719> web 00:01:55.950 --> 00:01:55.960 align:start position:0% you know complicated things web 00:01:55.960 --> 00:01:57.590 align:start position:0% you know complicated things web applications<00:01:56.479> especially<00:01:56.920> they<00:01:57.039> seem<00:01:57.320> so 00:01:57.590 --> 00:01:57.600 align:start position:0% applications especially they seem so 00:01:57.600 --> 00:01:59.550 align:start position:0% applications especially they seem so simple<00:01:58.320> but<00:01:58.439> when<00:01:58.560> you<00:01:58.759> actually<00:01:59.159> get<00:01:59.320> to<00:01:59.439> the 00:01:59.550 --> 00:01:59.560 align:start position:0% simple but when you actually get to the 00:01:59.560 --> 00:02:01.830 align:start position:0% simple but when you actually get to the bottom<00:02:00.200> and<00:02:00.280> you<00:02:00.399> start<00:02:00.680> deploying<00:02:01.159> them<00:02:01.719> they 00:02:01.830 --> 00:02:01.840 align:start position:0% bottom and you start deploying them they 00:02:01.840 --> 00:02:03.270 align:start position:0% bottom and you start deploying them they end<00:02:01.960> up<00:02:02.079> being<00:02:02.320> pretty<00:02:02.560> complicated<00:02:03.039> and<00:02:03.159> the 00:02:03.270 --> 00:02:03.280 align:start position:0% end up being pretty complicated and the 00:02:03.280 --> 00:02:06.389 align:start position:0% end up being pretty complicated and the build<00:02:03.600> is<00:02:04.560> surprisingly<00:02:05.479> complex<00:02:05.960> and 00:02:06.389 --> 00:02:06.399 align:start position:0% build is surprisingly complex and 00:02:06.399 --> 00:02:08.869 align:start position:0% build is surprisingly complex and difficult<00:02:06.600> to<00:02:06.759> do<00:02:07.439> you<00:02:07.600> have<00:02:07.759> like<00:02:08.039> five<00:02:08.239> jbms 00:02:08.869 --> 00:02:08.879 align:start position:0% difficult to do you have like five jbms 00:02:08.879 --> 00:02:11.430 align:start position:0% difficult to do you have like five jbms running<00:02:09.640> like<00:02:09.800> make<00:02:10.080> files<00:02:10.520> and<00:02:10.640> all<00:02:10.800> kinds<00:02:11.000> of 00:02:11.430 --> 00:02:11.440 align:start position:0% running like make files and all kinds of 00:02:11.440 --> 00:02:14.470 align:start position:0% running like make files and all kinds of things<00:02:12.440> uh<00:02:13.040> but<00:02:13.239> you<00:02:13.360> know<00:02:13.480> being<00:02:13.760> closure 00:02:14.470 --> 00:02:14.480 align:start position:0% things uh but you know being closure 00:02:14.480 --> 00:02:15.710 align:start position:0% things uh but you know being closure people<00:02:14.800> people<00:02:15.040> interested<00:02:15.360> in<00:02:15.440> closure 00:02:15.710 --> 00:02:15.720 align:start position:0% people people interested in closure 00:02:15.720 --> 00:02:17.270 align:start position:0% people people interested in closure anyway<00:02:16.040> we<00:02:16.160> recognize<00:02:16.560> the<00:02:16.680> need<00:02:16.800> to<00:02:16.959> manage 00:02:17.270 --> 00:02:17.280 align:start position:0% anyway we recognize the need to manage 00:02:17.280 --> 00:02:19.430 align:start position:0% anyway we recognize the need to manage complexity<00:02:17.840> that's<00:02:17.959> why<00:02:18.080> we<00:02:18.200> use<00:02:18.360> closure<00:02:19.280> it 00:02:19.430 --> 00:02:19.440 align:start position:0% complexity that's why we use closure it 00:02:19.440 --> 00:02:21.790 align:start position:0% complexity that's why we use closure it provides<00:02:19.720> us<00:02:19.959> abstractions<00:02:20.680> and<00:02:21.280> all<00:02:21.480> these 00:02:21.790 --> 00:02:21.800 align:start position:0% provides us abstractions and all these 00:02:21.800 --> 00:02:23.910 align:start position:0% provides us abstractions and all these ways<00:02:22.000> that<00:02:22.120> we<00:02:22.239> can<00:02:22.360> manage<00:02:22.680> complexity<00:02:23.360> but 00:02:23.910 --> 00:02:23.920 align:start position:0% ways that we can manage complexity but 00:02:23.920 --> 00:02:25.830 align:start position:0% ways that we can manage complexity but the<00:02:24.040> build<00:02:24.280> tooling<00:02:24.879> hasn't<00:02:25.200> really<00:02:25.480> kept<00:02:25.680> up 00:02:25.830 --> 00:02:25.840 align:start position:0% the build tooling hasn't really kept up 00:02:25.840 --> 00:02:28.790 align:start position:0% the build tooling hasn't really kept up with<00:02:26.000> that<00:02:26.160> there's<00:02:26.400> no<00:02:26.720> ways<00:02:27.040> to<00:02:27.440> make<00:02:28.440> uh<00:02:28.680> you 00:02:28.790 --> 00:02:28.800 align:start position:0% with that there's no ways to make uh you 00:02:28.800 --> 00:02:30.830 align:start position:0% with that there's no ways to make uh you know<00:02:29.000> small<00:02:29.280> modules<00:02:29.920> we<00:02:30.000> can<00:02:30.160> compose<00:02:30.640> to 00:02:30.830 --> 00:02:30.840 align:start position:0% know small modules we can compose to 00:02:30.840 --> 00:02:34.470 align:start position:0% know small modules we can compose to manage<00:02:31.200> complexity<00:02:31.760> encapsulate<00:02:32.760> things<00:02:33.760> um 00:02:34.470 --> 00:02:34.480 align:start position:0% manage complexity encapsulate things um 00:02:34.480 --> 00:02:37.190 align:start position:0% manage complexity encapsulate things um so<00:02:34.680> the<00:02:34.800> real<00:02:35.160> problem<00:02:35.760> in<00:02:35.879> our<00:02:36.080> opinion<00:02:37.000> is 00:02:37.190 --> 00:02:37.200 align:start position:0% so the real problem in our opinion is 00:02:37.200 --> 00:02:40.790 align:start position:0% so the real problem in our opinion is that<00:02:37.360> builds<00:02:37.800> which<00:02:37.920> is<00:02:38.000> all<00:02:38.160> right<00:02:38.360> opinion 00:02:40.790 --> 00:02:40.800 align:start position:0% that builds which is all right opinion 00:02:40.800 --> 00:02:43.949 align:start position:0% that builds which is all right opinion right<00:02:41.800> we<00:02:41.920> are<00:02:42.200> unanimous<00:02:43.200> that<00:02:43.360> builds<00:02:43.680> are 00:02:43.949 --> 00:02:43.959 align:start position:0% right we are unanimous that builds are 00:02:43.959 --> 00:02:46.270 align:start position:0% right we are unanimous that builds are processes<00:02:44.480> they're<00:02:44.680> not<00:02:45.159> specifications<00:02:46.159> in 00:02:46.270 --> 00:02:46.280 align:start position:0% processes they're not specifications in 00:02:46.280 --> 00:02:47.309 align:start position:0% processes they're not specifications in other<00:02:46.400> words<00:02:46.640> like<00:02:46.720> you<00:02:46.840> can't<00:02:47.000> make<00:02:47.120> a 00:02:47.309 --> 00:02:47.319 align:start position:0% other words like you can't make a 00:02:47.319 --> 00:02:49.350 align:start position:0% other words like you can't make a program<00:02:47.680> a<00:02:47.800> closure<00:02:48.239> program<00:02:48.680> that's<00:02:49.080> just<00:02:49.200> a 00:02:49.350 --> 00:02:49.360 align:start position:0% program a closure program that's just a 00:02:49.360 --> 00:02:51.550 align:start position:0% program a closure program that's just a big<00:02:49.560> map<00:02:49.840> of<00:02:50.440> things<00:02:50.680> you<00:02:50.800> want<00:02:50.959> it<00:02:51.080> to<00:02:51.200> do<00:02:51.440> in 00:02:51.550 --> 00:02:51.560 align:start position:0% big map of things you want it to do in 00:02:51.560 --> 00:02:53.390 align:start position:0% big map of things you want it to do in some<00:02:51.760> big<00:02:51.959> specification<00:02:52.640> and<00:02:52.800> then<00:02:53.159> you<00:02:53.280> know 00:02:53.390 --> 00:02:53.400 align:start position:0% some big specification and then you know 00:02:53.400 --> 00:02:55.270 align:start position:0% some big specification and then you know it'll<00:02:53.599> generate<00:02:54.000> some<00:02:54.239> program<00:02:54.640> that<00:02:54.760> will 00:02:55.270 --> 00:02:55.280 align:start position:0% it'll generate some program that will 00:02:55.280 --> 00:02:57.309 align:start position:0% it'll generate some program that will fulfill<00:02:55.640> all<00:02:55.800> your<00:02:55.959> wildest<00:02:56.319> dreams<00:02:57.040> now<00:02:57.200> you 00:02:57.309 --> 00:02:57.319 align:start position:0% fulfill all your wildest dreams now you 00:02:57.319 --> 00:02:59.949 align:start position:0% fulfill all your wildest dreams now you have<00:02:57.440> to<00:02:57.720> process<00:02:58.319> that<00:02:59.319> you<00:02:59.440> know<00:02:59.599> does 00:02:59.949 --> 00:02:59.959 align:start position:0% have to process that you know does 00:02:59.959 --> 00:03:02.470 align:start position:0% have to process that you know does things<00:03:00.159> sequentially<00:03:01.000> basically<00:03:02.000> and<00:03:02.319> most 00:03:02.470 --> 00:03:02.480 align:start position:0% things sequentially basically and most 00:03:02.480 --> 00:03:03.789 align:start position:0% things sequentially basically and most of<00:03:02.560> the<00:03:02.680> tools<00:03:02.959> that<00:03:03.040> are<00:03:03.200> out<00:03:03.360> there<00:03:03.519> now 00:03:03.789 --> 00:03:03.799 align:start position:0% of the tools that are out there now 00:03:03.799 --> 00:03:06.949 align:start position:0% of the tools that are out there now Maven<00:03:04.280> ant<00:03:04.840> whatever<00:03:05.159> all<00:03:05.239> of<00:03:05.400> them<00:03:06.200> are 00:03:06.949 --> 00:03:06.959 align:start position:0% Maven ant whatever all of them are 00:03:06.959 --> 00:03:08.110 align:start position:0% Maven ant whatever all of them are oriented<00:03:07.400> around<00:03:07.599> trying<00:03:07.799> to<00:03:07.920> make<00:03:08.000> a 00:03:08.110 --> 00:03:08.120 align:start position:0% oriented around trying to make a 00:03:08.120 --> 00:03:10.350 align:start position:0% oriented around trying to make a declarative<00:03:08.720> specification<00:03:09.720> for<00:03:09.959> what<00:03:10.120> you 00:03:10.350 --> 00:03:10.360 align:start position:0% declarative specification for what you 00:03:10.360 --> 00:03:12.710 align:start position:0% declarative specification for what you want<00:03:11.000> your<00:03:11.200> outcome<00:03:11.599> to<00:03:11.799> be<00:03:12.239> Gradle<00:03:12.599> is 00:03:12.710 --> 00:03:12.720 align:start position:0% want your outcome to be Gradle is 00:03:12.720 --> 00:03:14.110 align:start position:0% want your outcome to be Gradle is actually<00:03:12.920> kind<00:03:13.040> of<00:03:13.120> an<00:03:13.239> exception<00:03:13.840> if<00:03:13.959> you're 00:03:14.110 --> 00:03:14.120 align:start position:0% actually kind of an exception if you're 00:03:14.120 --> 00:03:16.350 align:start position:0% actually kind of an exception if you're familiar<00:03:14.440> with<00:03:14.560> Gradle<00:03:15.080> it's<00:03:15.319> sort<00:03:15.519> of<00:03:15.720> the 00:03:16.350 --> 00:03:16.360 align:start position:0% familiar with Gradle it's sort of the 00:03:16.360 --> 00:03:20.509 align:start position:0% familiar with Gradle it's sort of the the<00:03:16.519> boot<00:03:16.920> of<00:03:17.120> the<00:03:17.360> JV<00:03:18.360> sort<00:03:18.599> of<00:03:19.200> is 00:03:20.509 --> 00:03:20.519 align:start position:0% the boot of the JV sort of is 00:03:20.519 --> 00:03:22.670 align:start position:0% the boot of the JV sort of is is<00:03:21.519> but<00:03:21.680> basically<00:03:22.000> we're<00:03:22.200> programmers<00:03:22.599> we 00:03:22.670 --> 00:03:22.680 align:start position:0% is but basically we're programmers we 00:03:22.680 --> 00:03:25.190 align:start position:0% is but basically we're programmers we need<00:03:22.799> to<00:03:22.879> be<00:03:22.959> able<00:03:23.120> to<00:03:23.280> program<00:03:24.000> we<00:03:24.120> don't<00:03:25.080> we 00:03:25.190 --> 00:03:25.200 align:start position:0% need to be able to program we don't we 00:03:25.200 --> 00:03:26.309 align:start position:0% need to be able to program we don't we don't<00:03:25.360> want<00:03:25.519> something<00:03:25.720> to<00:03:25.840> generate<00:03:26.159> a 00:03:26.309 --> 00:03:26.319 align:start position:0% don't want something to generate a 00:03:26.319 --> 00:03:28.070 align:start position:0% don't want something to generate a program<00:03:26.680> for<00:03:26.920> us<00:03:27.200> we<00:03:27.280> want<00:03:27.400> to<00:03:27.560> be<00:03:27.680> able<00:03:27.840> to<00:03:28.040> I 00:03:28.070 --> 00:03:28.080 align:start position:0% program for us we want to be able to I 00:03:28.080 --> 00:03:30.070 align:start position:0% program for us we want to be able to I mean<00:03:28.239> List<00:03:28.599> gives<00:03:28.799> us<00:03:28.959> all<00:03:29.120> the<00:03:29.239> tools<00:03:29.840> that<00:03:30.000> we 00:03:30.070 --> 00:03:30.080 align:start position:0% mean List gives us all the tools that we 00:03:30.080 --> 00:03:31.949 align:start position:0% mean List gives us all the tools that we can<00:03:30.200> use<00:03:30.400> to<00:03:30.680> generate<00:03:31.000> our<00:03:31.159> own<00:03:31.360> programs<00:03:31.840> the 00:03:31.949 --> 00:03:31.959 align:start position:0% can use to generate our own programs the 00:03:31.959 --> 00:03:36.429 align:start position:0% can use to generate our own programs the way<00:03:32.120> we<00:03:32.640> want<00:03:33.879> so<00:03:34.879> boot<00:03:35.400> is<00:03:35.720> what<00:03:35.879> we<00:03:36.040> develop 00:03:36.429 --> 00:03:36.439 align:start position:0% way we want so boot is what we develop 00:03:36.439 --> 00:03:38.670 align:start position:0% way we want so boot is what we develop to<00:03:36.640> solve<00:03:36.879> our<00:03:37.040> own<00:03:37.319> problem<00:03:37.640> and<00:03:38.000> fulfill<00:03:38.400> our 00:03:38.670 --> 00:03:38.680 align:start position:0% to solve our own problem and fulfill our 00:03:38.680 --> 00:03:42.229 align:start position:0% to solve our own problem and fulfill our our<00:03:38.840> wildest<00:03:39.599> dreams<00:03:40.599> and<00:03:41.040> uh<00:03:41.640> the<00:03:41.760> main<00:03:42.000> idea 00:03:42.229 --> 00:03:42.239 align:start position:0% our wildest dreams and uh the main idea 00:03:42.239 --> 00:03:44.470 align:start position:0% our wildest dreams and uh the main idea of<00:03:42.319> it<00:03:42.439> is<00:03:42.560> that<00:03:42.680> you<00:03:42.760> can<00:03:42.879> make<00:03:43.080> small<00:03:43.480> parts 00:03:44.470 --> 00:03:44.480 align:start position:0% of it is that you can make small parts 00:03:44.480 --> 00:03:46.509 align:start position:0% of it is that you can make small parts that<00:03:44.640> each<00:03:44.840> do<00:03:45.120> one<00:03:45.400> thing<00:03:45.799> they<00:03:45.920> only<00:03:46.080> do<00:03:46.280> one 00:03:46.509 --> 00:03:46.519 align:start position:0% that each do one thing they only do one 00:03:46.519 --> 00:03:48.670 align:start position:0% that each do one thing they only do one thing<00:03:47.280> and<00:03:47.439> they<00:03:47.560> do<00:03:47.760> that<00:03:47.920> one<00:03:48.080> thing<00:03:48.319> well 00:03:48.670 --> 00:03:48.680 align:start position:0% thing and they do that one thing well 00:03:48.680 --> 00:03:51.710 align:start position:0% thing and they do that one thing well and<00:03:48.799> if<00:03:48.920> you<00:03:49.080> look<00:03:49.200> at<00:03:49.400> tools<00:03:49.920> like<00:03:50.319> Lan<00:03:50.959> or 00:03:51.710 --> 00:03:51.720 align:start position:0% and if you look at tools like Lan or 00:03:51.720 --> 00:03:54.149 align:start position:0% and if you look at tools like Lan or Maven<00:03:52.159> or<00:03:52.280> whatever<00:03:52.720> if<00:03:52.799> you<00:03:52.920> have<00:03:53.040> a<00:03:53.200> really 00:03:54.149 --> 00:03:54.159 align:start position:0% Maven or whatever if you have a really 00:03:54.159 --> 00:03:57.470 align:start position:0% Maven or whatever if you have a really successful<00:03:55.159> uh<00:03:55.400> plugin<00:03:56.120> it<00:03:56.239> ends<00:03:56.480> up<00:03:57.040> evolving 00:03:57.470 --> 00:03:57.480 align:start position:0% successful uh plugin it ends up evolving 00:03:57.480 --> 00:03:59.390 align:start position:0% successful uh plugin it ends up evolving into<00:03:57.680> a<00:03:57.799> build<00:03:58.000> tool<00:03:58.239> of<00:03:58.400> its<00:03:58.519> own<00:03:59.120> doing 00:03:59.390 --> 00:03:59.400 align:start position:0% into a build tool of its own doing 00:03:59.400 --> 00:04:01.229 align:start position:0% into a build tool of its own doing everything 00:04:01.229 --> 00:04:01.239 align:start position:0% everything 00:04:01.239 --> 00:04:04.270 align:start position:0% everything and<00:04:02.239> it's<00:04:02.439> much<00:04:02.640> better<00:04:02.879> to<00:04:03.000> do<00:04:03.519> to<00:04:03.680> have<00:04:04.079> many 00:04:04.270 --> 00:04:04.280 align:start position:0% and it's much better to do to have many 00:04:04.280 --> 00:04:05.550 align:start position:0% and it's much better to do to have many things<00:04:04.480> that<00:04:04.640> each<00:04:04.799> do<00:04:05.040> one<00:04:05.200> thing<00:04:05.360> that<00:04:05.480> you 00:04:05.550 --> 00:04:05.560 align:start position:0% things that each do one thing that you 00:04:05.560 --> 00:04:07.110 align:start position:0% things that each do one thing that you can<00:04:05.760> compose<00:04:06.120> yourself<00:04:06.480> the<00:04:06.599> user<00:04:06.920> can 00:04:07.110 --> 00:04:07.120 align:start position:0% can compose yourself the user can 00:04:07.120 --> 00:04:09.630 align:start position:0% can compose yourself the user can compose<00:04:07.439> himself<00:04:08.439> then<00:04:08.799> have<00:04:08.920> a<00:04:09.040> monolithic 00:04:09.630 --> 00:04:09.640 align:start position:0% compose himself then have a monolithic 00:04:09.640 --> 00:04:11.030 align:start position:0% compose himself then have a monolithic program<00:04:10.000> that<00:04:10.360> now<00:04:10.480> has<00:04:10.599> made<00:04:10.760> all<00:04:10.879> these 00:04:11.030 --> 00:04:11.040 align:start position:0% program that now has made all these 00:04:11.040 --> 00:04:12.390 align:start position:0% program that now has made all these choices<00:04:11.400> for 00:04:12.390 --> 00:04:12.400 align:start position:0% choices for 00:04:12.400 --> 00:04:16.069 align:start position:0% choices for you<00:04:13.400> and<00:04:14.280> uh<00:04:14.920> although<00:04:15.280> like<00:04:15.439> small<00:04:15.760> things<00:04:15.959> it 00:04:16.069 --> 00:04:16.079 align:start position:0% you and uh although like small things it 00:04:16.079 --> 00:04:17.590 align:start position:0% you and uh although like small things it doesn't<00:04:16.359> really<00:04:16.560> help<00:04:16.759> you<00:04:16.880> if<00:04:16.959> you<00:04:17.120> have<00:04:17.320> many 00:04:17.590 --> 00:04:17.600 align:start position:0% doesn't really help you if you have many 00:04:17.600 --> 00:04:19.509 align:start position:0% doesn't really help you if you have many small<00:04:17.919> things<00:04:18.320> and<00:04:18.400> you<00:04:18.560> can't<00:04:18.799> compose<00:04:19.120> them 00:04:19.509 --> 00:04:19.519 align:start position:0% small things and you can't compose them 00:04:19.519 --> 00:04:21.830 align:start position:0% small things and you can't compose them uniformly<00:04:20.519> so<00:04:21.040> you<00:04:21.160> know<00:04:21.320> that's<00:04:21.479> why<00:04:21.600> you<00:04:21.680> end 00:04:21.830 --> 00:04:21.840 align:start position:0% uniformly so you know that's why you end 00:04:21.840 --> 00:04:23.629 align:start position:0% uniformly so you know that's why you end up<00:04:22.000> having<00:04:22.160> a<00:04:22.280> big<00:04:22.440> monolithic<00:04:23.199> composition 00:04:23.629 --> 00:04:23.639 align:start position:0% up having a big monolithic composition 00:04:23.639 --> 00:04:24.790 align:start position:0% up having a big monolithic composition of<00:04:23.840> them<00:04:24.040> because<00:04:24.240> that's<00:04:24.360> the<00:04:24.479> only<00:04:24.639> way<00:04:24.720> you 00:04:24.790 --> 00:04:24.800 align:start position:0% of them because that's the only way you 00:04:24.800 --> 00:04:26.510 align:start position:0% of them because that's the only way you can<00:04:24.960> compose<00:04:25.280> them<00:04:25.440> such<00:04:25.600> that<00:04:25.720> it 00:04:26.510 --> 00:04:26.520 align:start position:0% can compose them such that it 00:04:26.520 --> 00:04:29.310 align:start position:0% can compose them such that it works<00:04:27.520> so<00:04:27.680> basically<00:04:28.000> our<00:04:28.160> tool<00:04:28.600> empowers<00:04:29.120> you 00:04:29.310 --> 00:04:29.320 align:start position:0% works so basically our tool empowers you 00:04:29.320 --> 00:04:31.270 align:start position:0% works so basically our tool empowers you to<00:04:29.479> take<00:04:29.840> these<00:04:30.000> small<00:04:30.240> pieces<00:04:30.840> put<00:04:31.000> them 00:04:31.270 --> 00:04:31.280 align:start position:0% to take these small pieces put them 00:04:31.280 --> 00:04:34.990 align:start position:0% to take these small pieces put them together<00:04:31.560> on<00:04:31.680> the<00:04:32.000> fly<00:04:33.000> to<00:04:33.199> make<00:04:33.400> a<00:04:33.560> new<00:04:33.800> build 00:04:34.990 --> 00:04:35.000 align:start position:0% together on the fly to make a new build 00:04:35.000 --> 00:04:37.070 align:start position:0% together on the fly to make a new build process<00:04:36.000> uh<00:04:36.160> it's<00:04:36.320> pretty<00:04:36.520> normal<00:04:36.880> that<00:04:36.960> it 00:04:37.070 --> 00:04:37.080 align:start position:0% process uh it's pretty normal that it 00:04:37.080 --> 00:04:39.230 align:start position:0% process uh it's pretty normal that it uses<00:04:37.400> ma<00:04:37.680> Maven<00:04:38.039> for<00:04:38.199> dependency<00:04:38.680> resolution 00:04:39.230 --> 00:04:39.240 align:start position:0% uses ma Maven for dependency resolution 00:04:39.240 --> 00:04:41.430 align:start position:0% uses ma Maven for dependency resolution so<00:04:39.520> all<00:04:39.680> the<00:04:39.840> things<00:04:40.039> for<00:04:40.680> you<00:04:40.800> know<00:04:41.039> for<00:04:41.280> these 00:04:41.430 --> 00:04:41.440 align:start position:0% so all the things for you know for these 00:04:41.440 --> 00:04:44.950 align:start position:0% so all the things for you know for these other<00:04:41.639> systems<00:04:42.039> Maven<00:04:42.320> and<00:04:42.440> Lan<00:04:42.800> will<00:04:43.240> work<00:04:44.240> um 00:04:44.950 --> 00:04:44.960 align:start position:0% other systems Maven and Lan will work um 00:04:44.960 --> 00:04:46.510 align:start position:0% other systems Maven and Lan will work um and<00:04:45.160> we<00:04:45.280> use<00:04:45.440> it<00:04:45.680> to<00:04:45.800> build<00:04:46.039> closure<00:04:46.360> en 00:04:46.510 --> 00:04:46.520 align:start position:0% and we use it to build closure en 00:04:46.520 --> 00:04:49.629 align:start position:0% and we use it to build closure en closure<00:04:46.840> script<00:04:47.680> at<00:04:48.199> adzerk<00:04:49.199> and<00:04:49.280> it<00:04:49.400> has<00:04:49.479> a 00:04:49.629 --> 00:04:49.639 align:start position:0% closure script at adzerk and it has a 00:04:49.639 --> 00:04:51.830 align:start position:0% closure script at adzerk and it has a website<00:04:50.320> so<00:04:50.479> you<00:04:50.560> can<00:04:50.720> go<00:04:50.880> there<00:04:51.080> you<00:04:51.199> can 00:04:51.830 --> 00:04:51.840 align:start position:0% website so you can go there you can 00:04:51.840 --> 00:04:55.590 align:start position:0% website so you can go there you can ignore<00:04:52.160> us<00:04:52.360> right<00:04:52.520> now<00:04:52.759> and<00:04:52.880> just<00:04:53.000> go<00:04:53.120> to<00:04:53.240> the 00:04:55.590 --> 00:04:55.600 align:start position:0% 00:04:55.600 --> 00:04:58.510 align:start position:0% website<00:04:56.600> so<00:04:57.199> um<00:04:57.919> like<00:04:58.039> I<00:04:58.120> said<00:04:58.240> we're<00:04:58.360> going<00:04:58.440> to 00:04:58.510 --> 00:04:58.520 align:start position:0% website so um like I said we're going to 00:04:58.520 --> 00:04:59.870 align:start position:0% website so um like I said we're going to do<00:04:58.639> some<00:04:58.720> sort<00:04:58.880> of<00:04:58.960> interactive<00:04:59.400> stuff<00:04:59.720> one<00:04:59.800> of 00:04:59.870 --> 00:04:59.880 align:start position:0% do some sort of interactive stuff one of 00:04:59.880 --> 00:05:01.150 align:start position:0% do some sort of interactive stuff one of the<00:04:59.960> cool<00:05:00.120> things<00:05:00.280> about<00:05:00.520> boot<00:05:00.840> is<00:05:00.960> that<00:05:01.080> you 00:05:01.150 --> 00:05:01.160 align:start position:0% the cool things about boot is that you 00:05:01.160 --> 00:05:02.590 align:start position:0% the cool things about boot is that you can<00:05:01.320> start<00:05:01.520> building<00:05:01.880> things<00:05:02.039> and<00:05:02.160> using<00:05:02.400> it 00:05:02.590 --> 00:05:02.600 align:start position:0% can start building things and using it 00:05:02.600 --> 00:05:03.629 align:start position:0% can start building things and using it without<00:05:02.800> really<00:05:03.000> having<00:05:03.199> any<00:05:03.360> kind<00:05:03.479> of 00:05:03.629 --> 00:05:03.639 align:start position:0% without really having any kind of 00:05:03.639 --> 00:05:05.710 align:start position:0% without really having any kind of descriptor<00:05:04.120> file<00:05:04.360> or<00:05:04.560> project<00:05:04.919> file<00:05:05.520> or 00:05:05.710 --> 00:05:05.720 align:start position:0% descriptor file or project file or 00:05:05.720 --> 00:05:08.230 align:start position:0% descriptor file or project file or notion<00:05:05.960> of<00:05:06.080> a<00:05:06.240> project<00:05:06.560> at<00:05:06.680> all<00:05:07.520> and<00:05:07.880> for<00:05:08.039> this 00:05:08.230 --> 00:05:08.240 align:start position:0% notion of a project at all and for this 00:05:08.240 --> 00:05:09.950 align:start position:0% notion of a project at all and for this example<00:05:08.639> project<00:05:09.120> I<00:05:09.199> know<00:05:09.360> this<00:05:09.440> some<00:05:09.600> closure 00:05:09.950 --> 00:05:09.960 align:start position:0% example project I know this some closure 00:05:09.960 --> 00:05:12.230 align:start position:0% example project I know this some closure project<00:05:10.199> so<00:05:10.360> we<00:05:10.479> chose<00:05:10.919> Java<00:05:11.720> now<00:05:11.880> we<00:05:12.000> all<00:05:12.120> need 00:05:12.230 --> 00:05:12.240 align:start position:0% project so we chose Java now we all need 00:05:12.240 --> 00:05:14.830 align:start position:0% project so we chose Java now we all need to<00:05:12.360> build<00:05:12.680> and<00:05:12.840> love<00:05:13.120> Java<00:05:13.680> software<00:05:14.639> actually 00:05:14.830 --> 00:05:14.840 align:start position:0% to build and love Java software actually 00:05:14.840 --> 00:05:17.189 align:start position:0% to build and love Java software actually that's<00:05:15.039> probably<00:05:15.199> not<00:05:15.320> true<00:05:15.520> maybe<00:05:15.759> it<00:05:15.919> is<00:05:16.880> um 00:05:17.189 --> 00:05:17.199 align:start position:0% that's probably not true maybe it is um 00:05:17.199 --> 00:05:19.710 align:start position:0% that's probably not true maybe it is um but<00:05:17.479> for<00:05:17.639> the<00:05:17.800> purposes<00:05:18.120> of<00:05:18.400> demonstrating<00:05:19.400> uh 00:05:19.710 --> 00:05:19.720 align:start position:0% but for the purposes of demonstrating uh 00:05:19.720 --> 00:05:22.150 align:start position:0% but for the purposes of demonstrating uh the<00:05:19.960> facilities<00:05:20.360> of<00:05:20.520> boot<00:05:21.080> we<00:05:21.240> chose<00:05:21.560> to<00:05:22.000> make 00:05:22.150 --> 00:05:22.160 align:start position:0% the facilities of boot we chose to make 00:05:22.160 --> 00:05:23.670 align:start position:0% the facilities of boot we chose to make a<00:05:22.280> small<00:05:22.520> Java<00:05:22.840> project<00:05:23.160> so<00:05:23.280> there's<00:05:23.440> this 00:05:23.670 --> 00:05:23.680 align:start position:0% a small Java project so there's this 00:05:23.680 --> 00:05:26.510 align:start position:0% a small Java project so there's this Java<00:05:23.960> hello<00:05:24.199> world<00:05:24.600> file<00:05:25.600> and<00:05:25.960> the<00:05:26.160> process 00:05:26.510 --> 00:05:26.520 align:start position:0% Java hello world file and the process 00:05:26.520 --> 00:05:29.430 align:start position:0% Java hello world file and the process that<00:05:26.720> Java<00:05:27.000> converts<00:05:27.560> Java<00:05:28.120> source<00:05:28.479> code<00:05:28.800> into 00:05:29.430 --> 00:05:29.440 align:start position:0% that Java converts Java source code into 00:05:29.440 --> 00:05:31.870 align:start position:0% that Java converts Java source code into um<00:05:29.840> jbm<00:05:30.319> bite<00:05:30.600> code<00:05:31.360> it's<00:05:31.560> kind<00:05:31.720> of 00:05:31.870 --> 00:05:31.880 align:start position:0% um jbm bite code it's kind of 00:05:31.880 --> 00:05:33.590 align:start position:0% um jbm bite code it's kind of Representative<00:05:32.520> of<00:05:32.840> of<00:05:33.000> all<00:05:33.199> the<00:05:33.319> things<00:05:33.479> that 00:05:33.590 --> 00:05:33.600 align:start position:0% Representative of of all the things that 00:05:33.600 --> 00:05:35.510 align:start position:0% Representative of of all the things that build<00:05:33.840> tools<00:05:34.080> do<00:05:34.240> even<00:05:34.400> if<00:05:34.479> they're<00:05:34.639> not<00:05:34.840> Java 00:05:35.510 --> 00:05:35.520 align:start position:0% build tools do even if they're not Java 00:05:35.520 --> 00:05:37.909 align:start position:0% build tools do even if they're not Java in<00:05:35.639> the<00:05:35.759> web's<00:05:36.199> you<00:05:36.319> know<00:05:37.160> domain<00:05:37.600> we<00:05:37.759> we're 00:05:37.909 --> 00:05:37.919 align:start position:0% in the web's you know domain we we're 00:05:37.919 --> 00:05:39.590 align:start position:0% in the web's you know domain we we're doing<00:05:38.199> various<00:05:38.479> Transformations<00:05:39.120> on<00:05:39.520> you 00:05:39.590 --> 00:05:39.600 align:start position:0% doing various Transformations on you 00:05:39.600 --> 00:05:41.710 align:start position:0% doing various Transformations on you know<00:05:39.759> CSS<00:05:40.360> pre-processors<00:05:41.160> and<00:05:41.319> converting 00:05:41.710 --> 00:05:41.720 align:start position:0% know CSS pre-processors and converting 00:05:41.720 --> 00:05:43.710 align:start position:0% know CSS pre-processors and converting and<00:05:41.880> optimizing<00:05:42.440> JavaScript<00:05:43.400> so<00:05:43.520> we<00:05:43.600> just 00:05:43.710 --> 00:05:43.720 align:start position:0% and optimizing JavaScript so we just 00:05:43.720 --> 00:05:44.790 align:start position:0% and optimizing JavaScript so we just chose<00:05:44.039> Java<00:05:44.280> because<00:05:44.440> it's<00:05:44.600> kind<00:05:44.680> of 00:05:44.790 --> 00:05:44.800 align:start position:0% chose Java because it's kind of 00:05:44.800 --> 00:05:46.150 align:start position:0% chose Java because it's kind of Representative<00:05:45.360> of<00:05:45.520> that<00:05:45.720> thing<00:05:45.840> that<00:05:45.960> bu 00:05:46.150 --> 00:05:46.160 align:start position:0% Representative of that thing that bu 00:05:46.160 --> 00:05:47.870 align:start position:0% Representative of that thing that bu tools<00:05:46.400> do<00:05:46.680> which<00:05:46.800> is<00:05:47.039> they<00:05:47.160> turn<00:05:47.440> one<00:05:47.600> kind<00:05:47.720> of 00:05:47.870 --> 00:05:47.880 align:start position:0% tools do which is they turn one kind of 00:05:47.880 --> 00:05:50.029 align:start position:0% tools do which is they turn one kind of thing<00:05:48.199> into<00:05:48.440> another<00:05:48.680> kind<00:05:48.800> of 00:05:50.029 --> 00:05:50.039 align:start position:0% thing into another kind of 00:05:50.039 --> 00:05:53.070 align:start position:0% thing into another kind of thing<00:05:51.039> so<00:05:51.240> Misha<00:05:51.479> is<00:05:51.560> showing<00:05:51.840> off<00:05:52.039> now<00:05:52.360> is<00:05:52.759> uh 00:05:53.070 --> 00:05:53.080 align:start position:0% thing so Misha is showing off now is uh 00:05:53.080 --> 00:05:57.230 align:start position:0% thing so Misha is showing off now is uh little<00:05:54.000> boot<00:05:54.319> command<00:05:54.639> line<00:05:55.080> action<00:05:56.080> um<00:05:57.039> you 00:05:57.230 --> 00:05:57.240 align:start position:0% little boot command line action um you 00:05:57.240 --> 00:05:58.590 align:start position:0% little boot command line action um you type<00:05:57.400> in<00:05:57.520> the<00:05:57.639> boot<00:05:57.840> command<00:05:58.160> it<00:05:58.280> emits<00:05:58.520> a 00:05:58.590 --> 00:05:58.600 align:start position:0% type in the boot command it emits a 00:05:58.600 --> 00:06:00.230 align:start position:0% type in the boot command it emits a tremendous<00:05:59.000> amount<00:05:59.199> of<00:05:59.360> things 00:06:00.230 --> 00:06:00.240 align:start position:0% tremendous amount of things 00:06:00.240 --> 00:06:02.909 align:start position:0% tremendous amount of things which<00:06:01.160> he's<00:06:01.319> still<00:06:01.479> scrolling<00:06:01.960> through<00:06:02.440> but 00:06:02.909 --> 00:06:02.919 align:start position:0% which he's still scrolling through but 00:06:02.919 --> 00:06:04.830 align:start position:0% which he's still scrolling through but uh<00:06:03.280> on<00:06:03.600> you<00:06:03.680> know<00:06:03.800> a<00:06:03.919> smaller<00:06:04.199> font<00:06:04.440> size<00:06:04.639> it's 00:06:04.830 --> 00:06:04.840 align:start position:0% uh on you know a smaller font size it's 00:06:04.840 --> 00:06:06.230 align:start position:0% uh on you know a smaller font size it's actually<00:06:05.039> fairly<00:06:05.440> readable<00:06:05.840> and<00:06:06.080> well 00:06:06.230 --> 00:06:06.240 align:start position:0% actually fairly readable and well 00:06:06.240 --> 00:06:08.189 align:start position:0% actually fairly readable and well organized<00:06:06.639> and<00:06:06.759> nicely<00:06:07.039> formatted<00:06:08.000> and<00:06:08.120> it 00:06:08.189 --> 00:06:08.199 align:start position:0% organized and nicely formatted and it 00:06:08.199 --> 00:06:10.390 align:start position:0% organized and nicely formatted and it shows<00:06:08.560> all<00:06:08.720> of<00:06:08.919> the<00:06:09.120> options<00:06:09.639> and<00:06:09.880> tasks<00:06:10.280> and 00:06:10.390 --> 00:06:10.400 align:start position:0% shows all of the options and tasks and 00:06:10.400 --> 00:06:13.390 align:start position:0% shows all of the options and tasks and so<00:06:10.560> on<00:06:10.800> that<00:06:11.280> uh<00:06:11.759> it<00:06:11.919> it 00:06:13.390 --> 00:06:13.400 align:start position:0% so on that uh it it 00:06:13.400 --> 00:06:16.189 align:start position:0% so on that uh it it supports<00:06:14.400> and<00:06:14.759> one<00:06:14.880> of<00:06:15.039> the<00:06:15.240> tasks<00:06:16.000> that<00:06:16.120> you 00:06:16.189 --> 00:06:16.199 align:start position:0% supports and one of the tasks that you 00:06:16.199 --> 00:06:18.430 align:start position:0% supports and one of the tasks that you can<00:06:16.360> run<00:06:16.680> is<00:06:16.800> the<00:06:16.919> Java<00:06:17.240> C<00:06:17.520> task<00:06:17.960> and<00:06:18.199> what<00:06:18.319> he 00:06:18.430 --> 00:06:18.440 align:start position:0% can run is the Java C task and what he 00:06:18.440 --> 00:06:19.830 align:start position:0% can run is the Java C task and what he shows<00:06:18.680> off<00:06:18.880> there<00:06:19.039> is<00:06:19.120> that<00:06:19.319> every<00:06:19.520> single 00:06:19.830 --> 00:06:19.840 align:start position:0% shows off there is that every single 00:06:19.840 --> 00:06:23.270 align:start position:0% shows off there is that every single task<00:06:20.199> also<00:06:20.440> supports<00:06:20.880> this<00:06:21.280> d-h<00:06:22.280> option<00:06:23.080> so 00:06:23.270 --> 00:06:23.280 align:start position:0% task also supports this d-h option so 00:06:23.280 --> 00:06:24.749 align:start position:0% task also supports this d-h option so every<00:06:23.479> task<00:06:23.840> you<00:06:24.080> you<00:06:24.160> can<00:06:24.319> access<00:06:24.560> at<00:06:24.680> the 00:06:24.749 --> 00:06:24.759 align:start position:0% every task you you can access at the 00:06:24.759 --> 00:06:28.189 align:start position:0% every task you you can access at the command<00:06:25.080> line<00:06:25.880> um<00:06:26.039> will<00:06:26.280> have<00:06:27.120> some<00:06:27.800> possibly 00:06:28.189 --> 00:06:28.199 align:start position:0% command line um will have some possibly 00:06:28.199 --> 00:06:29.749 align:start position:0% command line um will have some possibly no<00:06:28.919> well<00:06:29.039> it<00:06:29.120> would<00:06:29.240> definitely<00:06:29.599> have 00:06:29.749 --> 00:06:29.759 align:start position:0% no well it would definitely have 00:06:29.759 --> 00:06:31.110 align:start position:0% no well it would definitely have documentation<00:06:30.199> that<00:06:30.360> documentation<00:06:30.840> may<00:06:31.000> be 00:06:31.110 --> 00:06:31.120 align:start position:0% documentation that documentation may be 00:06:31.120 --> 00:06:33.629 align:start position:0% documentation that documentation may be sparse<00:06:31.560> in<00:06:31.639> the<00:06:31.720> case<00:06:31.840> of<00:06:32.000> java<00:06:32.280> C<00:06:33.120> it's<00:06:33.319> just 00:06:33.629 --> 00:06:33.639 align:start position:0% sparse in the case of java C it's just 00:06:33.639 --> 00:06:36.110 align:start position:0% sparse in the case of java C it's just showing<00:06:33.960> us<00:06:34.080> that<00:06:34.199> we<00:06:34.360> have<00:06:34.520> no<00:06:35.120> options 00:06:36.110 --> 00:06:36.120 align:start position:0% showing us that we have no options 00:06:36.120 --> 00:06:38.830 align:start position:0% showing us that we have no options there's<00:06:36.319> also<00:06:36.520> boot<00:06:36.840> DB<00:06:37.599> which<00:06:37.759> will<00:06:37.880> show<00:06:38.120> you 00:06:38.830 --> 00:06:38.840 align:start position:0% there's also boot DB which will show you 00:06:38.840 --> 00:06:41.629 align:start position:0% there's also boot DB which will show you um<00:06:39.599> the<00:06:39.800> version<00:06:40.240> of<00:06:40.400> boot<00:06:40.840> and<00:06:41.120> various 00:06:41.629 --> 00:06:41.639 align:start position:0% um the version of boot and various 00:06:41.639 --> 00:06:44.029 align:start position:0% um the version of boot and various relevant<00:06:42.520> boot<00:06:42.840> pieces<00:06:43.080> of 00:06:44.029 --> 00:06:44.039 align:start position:0% relevant boot pieces of 00:06:44.039 --> 00:06:47.430 align:start position:0% relevant boot pieces of information<00:06:45.199> um<00:06:46.199> so<00:06:46.720> what<00:06:46.840> we're<00:06:46.960> going<00:06:47.039> to<00:06:47.199> do 00:06:47.430 --> 00:06:47.440 align:start position:0% information um so what we're going to do 00:06:47.440 --> 00:06:49.110 align:start position:0% information um so what we're going to do is<00:06:47.720> start<00:06:48.120> working<00:06:48.360> on<00:06:48.479> this<00:06:48.639> Java<00:06:48.880> project 00:06:49.110 --> 00:06:49.120 align:start position:0% is start working on this Java project 00:06:49.120 --> 00:06:49.990 align:start position:0% is start working on this Java project from<00:06:49.240> the<00:06:49.319> command<00:06:49.599> line<00:06:49.720> we're<00:06:49.840> going<00:06:49.919> to 00:06:49.990 --> 00:06:50.000 align:start position:0% from the command line we're going to 00:06:50.000 --> 00:06:52.469 align:start position:0% from the command line we're going to start<00:06:50.199> compiling<00:06:50.680> some<00:06:50.919> Java<00:06:51.160> source<00:06:51.479> code<00:06:52.319> so 00:06:52.469 --> 00:06:52.479 align:start position:0% start compiling some Java source code so 00:06:52.479 --> 00:06:55.350 align:start position:0% start compiling some Java source code so in<00:06:52.599> the<00:06:52.720> source<00:06:53.039> directory<00:06:53.639> is<00:06:53.759> our<00:06:54.000> Java<00:06:54.360> file 00:06:55.350 --> 00:06:55.360 align:start position:0% in the source directory is our Java file 00:06:55.360 --> 00:06:57.589 align:start position:0% in the source directory is our Java file and<00:06:55.840> boot<00:06:56.160> is<00:06:56.280> going<00:06:56.440> to<00:06:56.960> or<00:06:57.160> Misha<00:06:57.440> is<00:06:57.520> going 00:06:57.589 --> 00:06:57.599 align:start position:0% and boot is going to or Misha is going 00:06:57.599 --> 00:06:59.629 align:start position:0% and boot is going to or Misha is going to<00:06:57.759> inform<00:06:58.120> boot<00:06:58.479> about<00:06:58.720> this<00:06:58.840> source<00:06:59.120> file<00:06:59.319> by 00:06:59.629 --> 00:06:59.639 align:start position:0% to inform boot about this source file by 00:06:59.639 --> 00:07:01.790 align:start position:0% to inform boot about this source file by adding<00:07:00.199> The<00:07:00.319> Source<00:07:00.599> directory<00:07:01.039> to<00:07:01.319> to<00:07:01.520> what 00:07:01.790 --> 00:07:01.800 align:start position:0% adding The Source directory to to what 00:07:01.800 --> 00:07:04.070 align:start position:0% adding The Source directory to to what what<00:07:01.879> we<00:07:02.000> call<00:07:02.560> Boots<00:07:02.960> Source<00:07:03.280> or<00:07:03.479> resource 00:07:04.070 --> 00:07:04.080 align:start position:0% what we call Boots Source or resource 00:07:04.080 --> 00:07:06.029 align:start position:0% what we call Boots Source or resource paths<00:07:05.080> and<00:07:05.199> that's<00:07:05.360> kind<00:07:05.479> of<00:07:05.639> like<00:07:05.759> adding 00:07:06.029 --> 00:07:06.039 align:start position:0% paths and that's kind of like adding 00:07:06.039 --> 00:07:07.790 align:start position:0% paths and that's kind of like adding that<00:07:06.160> directory<00:07:06.520> to<00:07:06.639> boots<00:07:06.960> class 00:07:07.790 --> 00:07:07.800 align:start position:0% that directory to boots class 00:07:07.800 --> 00:07:11.430 align:start position:0% that directory to boots class path<00:07:08.800> then<00:07:08.960> we're<00:07:09.120> executing<00:07:09.560> a<00:07:09.800> task<00:07:10.440> show 00:07:11.430 --> 00:07:11.440 align:start position:0% path then we're executing a task show 00:07:11.440 --> 00:07:12.869 align:start position:0% path then we're executing a task show and<00:07:11.599> show<00:07:11.919> is<00:07:12.000> a<00:07:12.160> task<00:07:12.400> that<00:07:12.479> comes<00:07:12.639> in<00:07:12.759> with 00:07:12.869 --> 00:07:12.879 align:start position:0% and show is a task that comes in with 00:07:12.879 --> 00:07:15.510 align:start position:0% and show is a task that comes in with food<00:07:13.160> and<00:07:13.240> it's<00:07:13.440> sort<00:07:13.560> of<00:07:13.680> a<00:07:13.840> diagnostic<00:07:14.560> task 00:07:15.510 --> 00:07:15.520 align:start position:0% food and it's sort of a diagnostic task 00:07:15.520 --> 00:07:17.070 align:start position:0% food and it's sort of a diagnostic task uh<00:07:15.800> it's<00:07:15.960> kind<00:07:16.080> of<00:07:16.199> like<00:07:16.319> a<00:07:16.440> task<00:07:16.680> that<00:07:16.759> you<00:07:16.879> can 00:07:17.070 --> 00:07:17.080 align:start position:0% uh it's kind of like a task that you can 00:07:17.080 --> 00:07:18.550 align:start position:0% uh it's kind of like a task that you can use<00:07:17.280> to<00:07:17.440> see<00:07:17.639> what<00:07:17.800> boot<00:07:18.080> is<00:07:18.199> doing<00:07:18.400> in<00:07:18.479> the 00:07:18.550 --> 00:07:18.560 align:start position:0% use to see what boot is doing in the 00:07:18.560 --> 00:07:20.469 align:start position:0% use to see what boot is doing in the middle<00:07:18.840> of<00:07:19.120> of<00:07:19.199> a<00:07:19.319> pipeline<00:07:19.720> or<00:07:19.879> a<00:07:20.000> series<00:07:20.240> of 00:07:20.469 --> 00:07:20.479 align:start position:0% middle of of a pipeline or a series of 00:07:20.479 --> 00:07:23.629 align:start position:0% middle of of a pipeline or a series of tasks<00:07:21.360> and<00:07:21.440> in<00:07:21.599> particular<00:07:21.960> the<00:07:22.160> DF<00:07:23.120> uh<00:07:23.280> option 00:07:23.629 --> 00:07:23.639 align:start position:0% tasks and in particular the DF uh option 00:07:23.639 --> 00:07:25.629 align:start position:0% tasks and in particular the DF uh option on<00:07:23.919> on<00:07:24.120> show<00:07:24.800> will<00:07:24.960> print<00:07:25.160> out<00:07:25.240> the<00:07:25.360> value<00:07:25.560> of 00:07:25.629 --> 00:07:25.639 align:start position:0% on on show will print out the value of 00:07:25.639 --> 00:07:27.869 align:start position:0% on on show will print out the value of the<00:07:25.759> file<00:07:26.039> set<00:07:26.199> and<00:07:26.280> the<00:07:26.400> file<00:07:26.639> set<00:07:26.840> is<00:07:27.080> the<00:07:27.680> the 00:07:27.869 --> 00:07:27.879 align:start position:0% the file set and the file set is the the 00:07:27.879 --> 00:07:29.710 align:start position:0% the file set and the file set is the the build<00:07:28.280> context<00:07:28.720> or<00:07:28.840> the<00:07:28.960> set<00:07:29.080> of<00:07:29.199> files<00:07:29.639> that 00:07:29.710 --> 00:07:29.720 align:start position:0% build context or the set of files that 00:07:29.720 --> 00:07:32.390 align:start position:0% build context or the set of files that the<00:07:29.759> build<00:07:29.960> is<00:07:30.080> currently<00:07:30.440> operating<00:07:31.199> on<00:07:32.199> now 00:07:32.390 --> 00:07:32.400 align:start position:0% the build is currently operating on now 00:07:32.400 --> 00:07:34.390 align:start position:0% the build is currently operating on now me<00:07:32.639> is<00:07:32.759> showing<00:07:33.080> us<00:07:33.360> chaining<00:07:33.879> together<00:07:34.160> these 00:07:34.390 --> 00:07:34.400 align:start position:0% me is showing us chaining together these 00:07:34.400 --> 00:07:37.350 align:start position:0% me is showing us chaining together these paths<00:07:34.879> so<00:07:35.120> we<00:07:35.440> start<00:07:35.720> off<00:07:35.960> by<00:07:36.680> informing<00:07:37.039> boot 00:07:37.350 --> 00:07:37.360 align:start position:0% paths so we start off by informing boot 00:07:37.360 --> 00:07:41.469 align:start position:0% paths so we start off by informing boot about<00:07:37.639> our<00:07:37.800> source<00:07:38.199> Rec<00:07:39.199> Pap 00:07:41.469 --> 00:07:41.479 align:start position:0% about our source Rec Pap 00:07:41.479 --> 00:07:45.550 align:start position:0% about our source Rec Pap there<00:07:42.479> to<00:07:42.639> do<00:07:43.120> source<00:07:44.120> so<00:07:44.400> DS<00:07:44.919> takes<00:07:45.080> a<00:07:45.199> source 00:07:45.550 --> 00:07:45.560 align:start position:0% there to do source so DS takes a source 00:07:45.560 --> 00:07:47.629 align:start position:0% there to do source so DS takes a source directory<00:07:46.319> then<00:07:46.440> we<00:07:46.599> call<00:07:46.759> the<00:07:46.879> show<00:07:47.240> task 00:07:47.629 --> 00:07:47.639 align:start position:0% directory then we call the show task 00:07:47.639 --> 00:07:49.589 align:start position:0% directory then we call the show task which<00:07:47.800> prints<00:07:48.080> the<00:07:48.199> file<00:07:48.520> set<00:07:49.120> program<00:07:49.400> you 00:07:49.589 --> 00:07:49.599 align:start position:0% which prints the file set program you 00:07:49.599 --> 00:07:50.990 align:start position:0% which prints the file set program you guys<00:07:49.960> so 00:07:50.990 --> 00:07:51.000 align:start position:0% guys so 00:07:51.000 --> 00:07:55.550 align:start position:0% guys so good<00:07:52.000> um<00:07:52.919> then<00:07:53.879> we<00:07:54.080> type<00:07:54.280> it<00:07:54.440> to<00:07:54.680> the<00:07:54.840> Java<00:07:55.159> C 00:07:55.550 --> 00:07:55.560 align:start position:0% good um then we type it to the Java C 00:07:55.560 --> 00:07:57.589 align:start position:0% good um then we type it to the Java C task<00:07:56.240> which<00:07:56.440> compiles<00:07:56.960> Java<00:07:57.280> and<00:07:57.400> then<00:07:57.479> we 00:07:57.589 --> 00:07:57.599 align:start position:0% task which compiles Java and then we 00:07:57.599 --> 00:07:59.670 align:start position:0% task which compiles Java and then we show<00:07:57.840> the<00:07:57.960> file<00:07:58.199> set<00:07:58.440> again<00:07:58.960> now<00:07:59.319> the<00:07:59.560> the 00:07:59.670 --> 00:07:59.680 align:start position:0% show the file set again now the the 00:07:59.680 --> 00:08:01.350 align:start position:0% show the file set again now the the difference<00:08:00.039> between<00:08:00.400> the<00:08:00.560> first<00:08:00.879> file<00:08:01.199> set 00:08:01.350 --> 00:08:01.360 align:start position:0% difference between the first file set 00:08:01.360 --> 00:08:02.990 align:start position:0% difference between the first file set and<00:08:01.440> the<00:08:01.560> second<00:08:01.800> file<00:08:02.039> set<00:08:02.199> is<00:08:02.319> this<00:08:02.520> do<00:08:02.759> class 00:08:02.990 --> 00:08:03.000 align:start position:0% and the second file set is this do class 00:08:03.000 --> 00:08:05.589 align:start position:0% and the second file set is this do class file<00:08:03.280> clearly<00:08:04.159> a<00:08:04.360> Java<00:08:04.680> has<00:08:04.879> been<00:08:05.039> compiled 00:08:05.589 --> 00:08:05.599 align:start position:0% file clearly a Java has been compiled 00:08:05.599 --> 00:08:09.749 align:start position:0% file clearly a Java has been compiled and<00:08:05.720> there<00:08:05.800> it<00:08:05.960> is<00:08:06.120> the<00:08:06.479> class<00:08:07.199> file<00:08:08.199> so<00:08:08.599> um<00:08:09.599> we 00:08:09.749 --> 00:08:09.759 align:start position:0% and there it is the class file so um we 00:08:09.759 --> 00:08:11.950 align:start position:0% and there it is the class file so um we have<00:08:09.960> a<00:08:10.159> slide<00:08:10.759> to<00:08:11.199> to<00:08:11.319> show<00:08:11.560> a<00:08:11.639> little<00:08:11.800> bit 00:08:11.950 --> 00:08:11.960 align:start position:0% have a slide to to show a little bit 00:08:11.960 --> 00:08:13.270 align:start position:0% have a slide to to show a little bit more<00:08:12.120> about<00:08:12.319> what's<00:08:12.479> going<00:08:12.599> on<00:08:12.759> let<00:08:12.879> mea<00:08:13.159> take 00:08:13.270 --> 00:08:13.280 align:start position:0% more about what's going on let mea take 00:08:13.280 --> 00:08:15.070 align:start position:0% more about what's going on let mea take it<00:08:13.440> away<00:08:14.039> yeah<00:08:14.159> this<00:08:14.240> is<00:08:14.360> pretty<00:08:14.560> typical<00:08:15.000> this 00:08:15.070 --> 00:08:15.080 align:start position:0% it away yeah this is pretty typical this 00:08:15.080 --> 00:08:18.149 align:start position:0% it away yeah this is pretty typical this is<00:08:15.240> how<00:08:15.639> pretty<00:08:15.800> much<00:08:16.080> every<00:08:16.720> boot<00:08:17.440> invocation 00:08:18.149 --> 00:08:18.159 align:start position:0% is how pretty much every boot invocation 00:08:18.159 --> 00:08:20.990 align:start position:0% is how pretty much every boot invocation Works<00:08:19.159> uh<00:08:19.240> you<00:08:19.360> build<00:08:19.639> up<00:08:19.919> a<00:08:20.360> a<00:08:20.479> pipeline<00:08:20.840> so 00:08:20.990 --> 00:08:21.000 align:start position:0% Works uh you build up a a pipeline so 00:08:21.000 --> 00:08:24.589 align:start position:0% Works uh you build up a a pipeline so you<00:08:21.080> can<00:08:21.159> see<00:08:21.360> showus<00:08:21.919> F<00:08:22.199> Java<00:08:22.520> c<00:08:22.759> showus<00:08:23.400> f<00:08:24.400> uh 00:08:24.589 --> 00:08:24.599 align:start position:0% you can see showus F Java c showus f uh 00:08:24.599 --> 00:08:26.149 align:start position:0% you can see showus F Java c showus f uh what<00:08:24.800> gets<00:08:25.039> injected<00:08:25.440> into<00:08:25.639> the<00:08:25.759> beginning<00:08:26.039> of 00:08:26.149 --> 00:08:26.159 align:start position:0% what gets injected into the beginning of 00:08:26.159 --> 00:08:28.670 align:start position:0% what gets injected into the beginning of the<00:08:26.319> pipeline<00:08:26.919> is<00:08:27.039> your<00:08:27.240> source<00:08:27.599> files<00:08:28.560> and 00:08:28.670 --> 00:08:28.680 align:start position:0% the pipeline is your source files and 00:08:28.680 --> 00:08:30.110 align:start position:0% the pipeline is your source files and that<00:08:28.800> becomes<00:08:29.039> a<00:08:29.159> file<00:08:29.599> set<00:08:29.720> which<00:08:29.840> we'll<00:08:29.960> talk 00:08:30.110 --> 00:08:30.120 align:start position:0% that becomes a file set which we'll talk 00:08:30.120 --> 00:08:32.269 align:start position:0% that becomes a file set which we'll talk about<00:08:30.280> in<00:08:30.360> a<00:08:30.479> little<00:08:30.639> bit<00:08:31.319> uh<00:08:31.400> each<00:08:31.680> task<00:08:32.080> takes 00:08:32.269 --> 00:08:32.279 align:start position:0% about in a little bit uh each task takes 00:08:32.279 --> 00:08:34.990 align:start position:0% about in a little bit uh each task takes a<00:08:32.440> file<00:08:32.680> set<00:08:32.919> as<00:08:33.120> input<00:08:33.800> does<00:08:33.959> some<00:08:34.120> kind<00:08:34.240> of 00:08:34.990 --> 00:08:35.000 align:start position:0% a file set as input does some kind of 00:08:35.000 --> 00:08:37.949 align:start position:0% a file set as input does some kind of processing<00:08:36.000> um<00:08:36.599> either<00:08:36.880> adds<00:08:37.320> removes 00:08:37.949 --> 00:08:37.959 align:start position:0% processing um either adds removes 00:08:37.959 --> 00:08:40.469 align:start position:0% processing um either adds removes modifies<00:08:38.839> files<00:08:39.159> to<00:08:39.360> create<00:08:39.640> a<00:08:39.800> new<00:08:40.039> file<00:08:40.320> set 00:08:40.469 --> 00:08:40.479 align:start position:0% modifies files to create a new file set 00:08:40.479 --> 00:08:42.350 align:start position:0% modifies files to create a new file set a<00:08:40.599> new<00:08:40.760> immutable<00:08:41.240> file<00:08:41.479> set<00:08:41.719> object<00:08:42.000> which<00:08:42.120> it 00:08:42.350 --> 00:08:42.360 align:start position:0% a new immutable file set object which it 00:08:42.360 --> 00:08:45.910 align:start position:0% a new immutable file set object which it passes<00:08:42.640> to<00:08:42.800> the<00:08:42.919> next<00:08:43.240> task<00:08:44.039> and<00:08:44.200> so<00:08:44.800> on<00:08:45.800> uh 00:08:45.910 --> 00:08:45.920 align:start position:0% passes to the next task and so on uh 00:08:45.920 --> 00:08:47.230 align:start position:0% passes to the next task and so on uh this<00:08:46.000> will<00:08:46.120> be<00:08:46.240> familiar<00:08:46.680> if<00:08:46.800> you're<00:08:47.160> if 00:08:47.230 --> 00:08:47.240 align:start position:0% this will be familiar if you're if 00:08:47.240 --> 00:08:49.150 align:start position:0% this will be familiar if you're if you're<00:08:47.440> familiar<00:08:47.800> with<00:08:48.000> like<00:08:48.160> ring<00:08:48.959> uh<00:08:49.040> the 00:08:49.150 --> 00:08:49.160 align:start position:0% you're familiar with like ring uh the 00:08:49.160 --> 00:08:52.310 align:start position:0% you're familiar with like ring uh the middleware 00:08:52.310 --> 00:08:52.320 align:start position:0% 00:08:52.320 --> 00:08:55.670 align:start position:0% pattern<00:08:53.320> so<00:08:53.720> to<00:08:53.920> install<00:08:54.279> a<00:08:54.399> jar 00:08:55.670 --> 00:08:55.680 align:start position:0% pattern so to install a jar 00:08:55.680 --> 00:08:57.750 align:start position:0% pattern so to install a jar now<00:08:56.680> so<00:08:56.800> we're<00:08:56.920> just<00:08:57.000> going<00:08:57.120> to<00:08:57.240> keep<00:08:57.399> rolling 00:08:57.750 --> 00:08:57.760 align:start position:0% now so we're just going to keep rolling 00:08:57.760 --> 00:08:59.630 align:start position:0% now so we're just going to keep rolling with<00:08:57.920> adding<00:08:58.200> Tas<00:08:58.440> on<00:08:58.720> this<00:08:58.839> thing<00:08:59.040> doing<00:08:59.200> more 00:08:59.630 --> 00:08:59.640 align:start position:0% with adding Tas on this thing doing more 00:08:59.640 --> 00:09:01.350 align:start position:0% with adding Tas on this thing doing more more<00:09:00.079> doing<00:09:00.320> more<00:09:00.440> and<00:09:00.560> more<00:09:00.760> things<00:09:00.959> so<00:09:01.200> right 00:09:01.350 --> 00:09:01.360 align:start position:0% more doing more and more things so right 00:09:01.360 --> 00:09:03.350 align:start position:0% more doing more and more things so right now<00:09:01.480> we've<00:09:01.640> got<00:09:01.720> our<00:09:01.880> Java<00:09:02.200> project<00:09:02.480> compiling 00:09:03.350 --> 00:09:03.360 align:start position:0% now we've got our Java project compiling 00:09:03.360 --> 00:09:05.310 align:start position:0% now we've got our Java project compiling and<00:09:03.839> maybe<00:09:04.079> we<00:09:04.200> want<00:09:04.279> to<00:09:04.519> turn<00:09:04.680> it<00:09:04.800> into<00:09:04.959> a<00:09:05.079> jar 00:09:05.310 --> 00:09:05.320 align:start position:0% and maybe we want to turn it into a jar 00:09:05.320 --> 00:09:06.590 align:start position:0% and maybe we want to turn it into a jar file<00:09:05.519> that's<00:09:05.720> executable<00:09:06.279> because<00:09:06.399> we<00:09:06.480> need 00:09:06.590 --> 00:09:06.600 align:start position:0% file that's executable because we need 00:09:06.600 --> 00:09:08.110 align:start position:0% file that's executable because we need to<00:09:06.839> send<00:09:07.079> this<00:09:07.200> important<00:09:07.519> program<00:09:07.880> someone 00:09:08.110 --> 00:09:08.120 align:start position:0% to send this important program someone 00:09:08.120 --> 00:09:10.310 align:start position:0% to send this important program someone else<00:09:09.120> inside<00:09:09.360> our<00:09:09.560> business<00:09:09.839> land<00:09:10.160> or 00:09:10.310 --> 00:09:10.320 align:start position:0% else inside our business land or 00:09:10.320 --> 00:09:13.790 align:start position:0% else inside our business land or whatever<00:09:10.600> the<00:09:10.760> case<00:09:11.120> is<00:09:12.120> so<00:09:13.040> um<00:09:13.320> what<00:09:13.440> m<00:09:13.680> is 00:09:13.790 --> 00:09:13.800 align:start position:0% whatever the case is so um what m is 00:09:13.800 --> 00:09:16.030 align:start position:0% whatever the case is so um what m is doing<00:09:14.040> is<00:09:14.120> he's<00:09:14.279> introduced<00:09:14.680> the<00:09:14.800> Palm<00:09:15.160> task 00:09:16.030 --> 00:09:16.040 align:start position:0% doing is he's introduced the Palm task 00:09:16.040 --> 00:09:18.030 align:start position:0% doing is he's introduced the Palm task pal<00:09:16.320> is<00:09:16.440> a<00:09:16.640> task<00:09:17.079> that<00:09:17.279> takes<00:09:17.480> a<00:09:17.640> number<00:09:17.839> of 00:09:18.030 --> 00:09:18.040 align:start position:0% pal is a task that takes a number of 00:09:18.040 --> 00:09:19.750 align:start position:0% pal is a task that takes a number of options<00:09:18.399> like-<00:09:18.880> p<00:09:19.120> is<00:09:19.200> the<00:09:19.320> name<00:09:19.440> of<00:09:19.560> the 00:09:19.750 --> 00:09:19.760 align:start position:0% options like- p is the name of the 00:09:19.760 --> 00:09:22.230 align:start position:0% options like- p is the name of the project-<00:09:20.680> V<00:09:20.920> is<00:09:21.040> the<00:09:21.120> version<00:09:21.360> of<00:09:21.480> the<00:09:21.640> project 00:09:22.230 --> 00:09:22.240 align:start position:0% project- V is the version of the project 00:09:22.240 --> 00:09:23.550 align:start position:0% project- V is the version of the project those<00:09:22.360> are<00:09:22.480> the<00:09:22.600> two<00:09:22.720> pieces<00:09:22.959> of<00:09:23.040> information 00:09:23.550 --> 00:09:23.560 align:start position:0% those are the two pieces of information 00:09:23.560 --> 00:09:25.230 align:start position:0% those are the two pieces of information information<00:09:24.160> a<00:09:24.320> program<00:09:24.600> needs<00:09:24.800> to<00:09:24.920> make<00:09:25.000> a 00:09:25.230 --> 00:09:25.240 align:start position:0% information a program needs to make a 00:09:25.240 --> 00:09:27.910 align:start position:0% information a program needs to make a pal<00:09:25.440> XML<00:09:25.880> file<00:09:26.519> and<00:09:26.640> a<00:09:26.760> pal<00:09:26.959> XML<00:09:27.320> file<00:09:27.519> is<00:09:27.680> that 00:09:27.910 --> 00:09:27.920 align:start position:0% pal XML file and a pal XML file is that 00:09:27.920 --> 00:09:31.030 align:start position:0% pal XML file and a pal XML file is that descriptor<00:09:28.399> that<00:09:28.480> goes<00:09:28.640> into<00:09:28.880> m 00:09:31.030 --> 00:09:31.040 align:start position:0% descriptor that goes into m 00:09:31.040 --> 00:09:34.630 align:start position:0% descriptor that goes into m uh<00:09:31.279> then<00:09:31.440> he's<00:09:31.680> typing<00:09:32.120> that<00:09:32.560> to<00:09:32.959> the<00:09:33.160> jar<00:09:33.720> task 00:09:34.630 --> 00:09:34.640 align:start position:0% uh then he's typing that to the jar task 00:09:34.640 --> 00:09:36.110 align:start position:0% uh then he's typing that to the jar task which<00:09:34.920> takes<00:09:35.160> all<00:09:35.360> the<00:09:35.480> things<00:09:35.640> in<00:09:35.720> the<00:09:35.839> file 00:09:36.110 --> 00:09:36.120 align:start position:0% which takes all the things in the file 00:09:36.120 --> 00:09:38.150 align:start position:0% which takes all the things in the file set<00:09:36.279> and<00:09:36.360> puts<00:09:36.560> them<00:09:36.680> into<00:09:36.839> a<00:09:36.959> jar<00:09:37.600> in<00:09:37.680> a<00:09:37.880> Java 00:09:38.150 --> 00:09:38.160 align:start position:0% set and puts them into a jar in a Java 00:09:38.160 --> 00:09:40.949 align:start position:0% set and puts them into a jar in a Java archive<00:09:38.560> file<00:09:39.519> and<00:09:39.640> that<00:09:39.800> picks<00:09:40.000> an<00:09:40.160> option-<00:09:40.680> m 00:09:40.949 --> 00:09:40.959 align:start position:0% archive file and that picks an option- m 00:09:40.959 --> 00:09:42.550 align:start position:0% archive file and that picks an option- m and<00:09:41.120> that<00:09:41.279> specifies<00:09:41.800> what<00:09:41.920> is<00:09:42.040> the<00:09:42.200> main 00:09:42.550 --> 00:09:42.560 align:start position:0% and that specifies what is the main 00:09:42.560 --> 00:09:44.430 align:start position:0% and that specifies what is the main class<00:09:43.000> in<00:09:43.240> the<00:09:43.480> artifact<00:09:43.959> which<00:09:44.040> in<00:09:44.120> our<00:09:44.279> case 00:09:44.430 --> 00:09:44.440 align:start position:0% class in the artifact which in our case 00:09:44.440 --> 00:09:47.550 align:start position:0% class in the artifact which in our case is<00:09:44.519> this<00:09:44.680> boot.<00:09:45.120> demo<00:09:45.519> Java<00:09:46.120> class<00:09:47.120> so<00:09:47.279> in<00:09:47.360> one 00:09:47.550 --> 00:09:47.560 align:start position:0% is this boot. demo Java class so in one 00:09:47.560 --> 00:09:49.870 align:start position:0% is this boot. demo Java class so in one fail<00:09:47.800> swoop<00:09:48.360> he<00:09:48.600> has<00:09:48.880> compiled<00:09:49.240> the<00:09:49.440> Java 00:09:49.870 --> 00:09:49.880 align:start position:0% fail swoop he has compiled the Java 00:09:49.880 --> 00:09:52.870 align:start position:0% fail swoop he has compiled the Java created<00:09:50.160> a<00:09:50.279> p<00:09:50.600> file<00:09:51.360> created<00:09:51.640> a<00:09:51.760> jar<00:09:52.079> file 00:09:52.870 --> 00:09:52.880 align:start position:0% created a p file created a jar file 00:09:52.880 --> 00:09:54.350 align:start position:0% created a p file created a jar file specified<00:09:53.360> in<00:09:53.440> the<00:09:53.560> jar<00:09:53.800> file<00:09:53.959> what<00:09:54.040> the<00:09:54.120> main 00:09:54.350 --> 00:09:54.360 align:start position:0% specified in the jar file what the main 00:09:54.360 --> 00:09:55.710 align:start position:0% specified in the jar file what the main class<00:09:54.560> is<00:09:54.680> and<00:09:54.800> installed<00:09:55.120> it<00:09:55.200> to<00:09:55.320> his<00:09:55.480> local 00:09:55.710 --> 00:09:55.720 align:start position:0% class is and installed it to his local 00:09:55.720 --> 00:09:56.670 align:start position:0% class is and installed it to his local Maven 00:09:56.670 --> 00:09:56.680 align:start position:0% Maven 00:09:56.680 --> 00:09:59.389 align:start position:0% Maven repository<00:09:57.680> now<00:09:57.800> at<00:09:57.959> this<00:09:58.120> point<00:09:58.360> we<00:09:58.480> can<00:09:58.959> um 00:09:59.389 --> 00:09:59.399 align:start position:0% repository now at this point we can um 00:09:59.399 --> 00:10:02.829 align:start position:0% repository now at this point we can um boot<00:10:00.160> DD<00:10:01.160> we<00:10:01.240> can<00:10:01.399> supply<00:10:01.760> the<00:10:01.920> DD<00:10:02.440> option<00:10:02.680> to 00:10:02.829 --> 00:10:02.839 align:start position:0% boot DD we can supply the DD option to 00:10:02.839 --> 00:10:05.550 align:start position:0% boot DD we can supply the DD option to boot<00:10:03.519> and<00:10:03.640> what-<00:10:04.000> D<00:10:04.240> does<00:10:04.480> is<00:10:04.560> it<00:10:04.720> takes<00:10:05.000> a<00:10:05.160> na 00:10:05.550 --> 00:10:05.560 align:start position:0% boot and what- D does is it takes a na 00:10:05.560 --> 00:10:06.870 align:start position:0% boot and what- D does is it takes a na artifact<00:10:06.000> name<00:10:06.200> this<00:10:06.320> could<00:10:06.440> be<00:10:06.519> something<00:10:06.720> a 00:10:06.870 --> 00:10:06.880 align:start position:0% artifact name this could be something a 00:10:06.880 --> 00:10:08.710 align:start position:0% artifact name this could be something a clojars<00:10:07.279> or<00:10:07.600> it<00:10:07.680> could<00:10:07.839> be<00:10:08.240> in<00:10:08.360> this<00:10:08.519> case 00:10:08.710 --> 00:10:08.720 align:start position:0% clojars or it could be in this case 00:10:08.720 --> 00:10:10.910 align:start position:0% clojars or it could be in this case something<00:10:09.079> local<00:10:10.079> and<00:10:10.200> then<00:10:10.320> runs<00:10:10.600> another 00:10:10.910 --> 00:10:10.920 align:start position:0% something local and then runs another 00:10:10.920 --> 00:10:12.310 align:start position:0% something local and then runs another task<00:10:11.240> and<00:10:11.320> one<00:10:11.440> of<00:10:11.519> the<00:10:11.640> tasks<00:10:11.880> we<00:10:12.040> have<00:10:12.160> is 00:10:12.310 --> 00:10:12.320 align:start position:0% task and one of the tasks we have is 00:10:12.320 --> 00:10:14.590 align:start position:0% task and one of the tasks we have is repple<00:10:12.720> and<00:10:12.839> that<00:10:12.920> starts<00:10:13.160> to<00:10:13.240> boot<00:10:13.480> repple<00:10:14.440> so 00:10:14.590 --> 00:10:14.600 align:start position:0% repple and that starts to boot repple so 00:10:14.600 --> 00:10:17.350 align:start position:0% repple and that starts to boot repple so we're<00:10:14.760> in<00:10:14.880> a<00:10:15.079> context<00:10:15.640> now<00:10:15.959> where<00:10:16.399> uh<00:10:16.600> boot<00:10:16.959> is 00:10:17.350 --> 00:10:17.360 align:start position:0% we're in a context now where uh boot is 00:10:17.360 --> 00:10:19.350 align:start position:0% we're in a context now where uh boot is is<00:10:17.519> informed<00:10:18.000> about<00:10:18.200> our<00:10:18.360> boot<00:10:18.680> d<00:10:18.880> demo 00:10:19.350 --> 00:10:19.360 align:start position:0% is informed about our boot d demo 00:10:19.360 --> 00:10:21.630 align:start position:0% is informed about our boot d demo artifact<00:10:20.360> which<00:10:20.519> was<00:10:20.640> installed<00:10:21.040> locally<00:10:21.519> and 00:10:21.630 --> 00:10:21.640 align:start position:0% artifact which was installed locally and 00:10:21.640 --> 00:10:23.829 align:start position:0% artifact which was installed locally and now<00:10:21.800> from<00:10:21.959> the<00:10:22.079> reppel<00:10:23.000> there's<00:10:23.160> a<00:10:23.360> little 00:10:23.829 --> 00:10:23.839 align:start position:0% now from the reppel there's a little 00:10:23.839 --> 00:10:25.389 align:start position:0% now from the reppel there's a little song<00:10:24.079> and<00:10:24.200> dance<00:10:24.440> we<00:10:24.519> need<00:10:24.640> to<00:10:24.760> do<00:10:24.880> to<00:10:25.040> call<00:10:25.240> a 00:10:25.389 --> 00:10:25.399 align:start position:0% song and dance we need to do to call a 00:10:25.399 --> 00:10:27.910 align:start position:0% song and dance we need to do to call a Java<00:10:25.680> static<00:10:26.000> method<00:10:26.440> a<00:10:26.640> main<00:10:26.920> method<00:10:27.279> but 00:10:27.910 --> 00:10:27.920 align:start position:0% Java static method a main method but 00:10:27.920 --> 00:10:29.310 align:start position:0% Java static method a main method but sure<00:10:28.120> enough<00:10:28.399> that<00:10:28.519> class<00:10:28.760> existed<00:10:29.040> on<00:10:29.120> the 00:10:29.310 --> 00:10:29.320 align:start position:0% sure enough that class existed on the 00:10:29.320 --> 00:10:30.870 align:start position:0% sure enough that class existed on the class<00:10:29.600> pth<00:10:29.839> when<00:10:29.920> we<00:10:30.079> just<00:10:30.200> compiled<00:10:30.560> and 00:10:30.870 --> 00:10:30.880 align:start position:0% class pth when we just compiled and 00:10:30.880 --> 00:10:33.829 align:start position:0% class pth when we just compiled and solved<00:10:31.200> and<00:10:31.320> we<00:10:31.440> just<00:10:31.519> run<00:10:31.720> a<00:10:31.839> composure 00:10:33.829 --> 00:10:33.839 align:start position:0% solved and we just run a composure 00:10:33.839 --> 00:10:41.750 align:start position:0% solved and we just run a composure so 00:10:41.750 --> 00:10:41.760 align:start position:0% 00:10:41.760 --> 00:10:44.069 align:start position:0% yeah 00:10:44.069 --> 00:10:44.079 align:start position:0% yeah 00:10:44.079 --> 00:10:49.269 align:start position:0% yeah so<00:10:45.160> now<00:10:46.160> uh<00:10:46.320> we<00:10:46.440> have<00:10:46.680> added<00:10:47.680> the<00:10:48.680> uh<00:10:48.839> Source 00:10:49.269 --> 00:10:49.279 align:start position:0% so now uh we have added the uh Source 00:10:49.279 --> 00:10:51.509 align:start position:0% so now uh we have added the uh Source path<00:10:49.920> again<00:10:50.200> to<00:10:50.399> boot<00:10:50.680> and<00:10:50.880> we<00:10:51.120> went<00:10:51.279> straight 00:10:51.509 --> 00:10:51.519 align:start position:0% path again to boot and we went straight 00:10:51.519 --> 00:10:54.590 align:start position:0% path again to boot and we went straight into<00:10:51.680> boot 00:10:54.590 --> 00:10:54.600 align:start position:0% 00:10:54.600 --> 00:10:57.829 align:start position:0% reel<00:10:55.600> man<00:10:55.720> I'm<00:10:55.839> on<00:10:56.040> fire 00:10:57.829 --> 00:10:57.839 align:start position:0% reel man I'm on fire 00:10:57.839 --> 00:11:01.110 align:start position:0% reel man I'm on fire today<00:10:58.839> there<00:10:58.959> we<00:10:59.079> go<00:10:59.480> guys<00:10:59.839> yeah<00:11:00.639> okay<00:11:00.839> so<00:11:01.000> he's 00:11:01.110 --> 00:11:01.120 align:start position:0% today there we go guys yeah okay so he's 00:11:01.120 --> 00:11:04.710 align:start position:0% today there we go guys yeah okay so he's in<00:11:01.240> a<00:11:01.399> reppel<00:11:02.399> and<00:11:02.959> um<00:11:03.519> the-<00:11:03.920> s<00:11:04.200> option<00:11:04.440> I<00:11:04.519> said 00:11:04.710 --> 00:11:04.720 align:start position:0% in a reppel and um the- s option I said 00:11:04.720 --> 00:11:06.470 align:start position:0% in a reppel and um the- s option I said it<00:11:04.880> adds<00:11:05.120> to<00:11:05.240> the<00:11:05.399> file<00:11:05.639> set<00:11:05.839> or<00:11:05.959> an<00:11:06.079> informed 00:11:06.470 --> 00:11:06.480 align:start position:0% it adds to the file set or an informed 00:11:06.480 --> 00:11:09.069 align:start position:0% it adds to the file set or an informed boot<00:11:06.800> about<00:11:06.959> where<00:11:07.120> Source<00:11:07.760> locations<00:11:08.240> are 00:11:09.069 --> 00:11:09.079 align:start position:0% boot about where Source locations are 00:11:09.079 --> 00:11:10.310 align:start position:0% boot about where Source locations are one<00:11:09.200> of<00:11:09.320> the<00:11:09.399> principles<00:11:09.760> in<00:11:09.880> boot<00:11:10.079> is<00:11:10.200> that 00:11:10.310 --> 00:11:10.320 align:start position:0% one of the principles in boot is that 00:11:10.320 --> 00:11:11.350 align:start position:0% one of the principles in boot is that everything<00:11:10.519> you<00:11:10.639> can<00:11:10.760> do<00:11:10.880> at<00:11:11.000> the<00:11:11.079> command 00:11:11.350 --> 00:11:11.360 align:start position:0% everything you can do at the command 00:11:11.360 --> 00:11:12.910 align:start position:0% everything you can do at the command line<00:11:11.560> should<00:11:11.680> be<00:11:11.839> possible<00:11:12.079> at<00:11:12.160> the<00:11:12.279> r<00:11:12.680> vice 00:11:12.910 --> 00:11:12.920 align:start position:0% line should be possible at the r vice 00:11:12.920 --> 00:11:14.790 align:start position:0% line should be possible at the r vice versa<00:11:13.519> well<00:11:13.839> it's<00:11:14.000> not<00:11:14.160> really<00:11:14.320> possible<00:11:14.560> to 00:11:14.790 --> 00:11:14.800 align:start position:0% versa well it's not really possible to 00:11:14.800 --> 00:11:19.310 align:start position:0% versa well it's not really possible to the<00:11:14.839> other<00:11:15.320> direction<00:11:16.320> um<00:11:16.480> but<00:11:16.600> we<00:11:16.880> try<00:11:17.880> so<00:11:18.680> the 00:11:19.310 --> 00:11:19.320 align:start position:0% the other direction um but we try so the 00:11:19.320 --> 00:11:23.470 align:start position:0% the other direction um but we try so the um<00:11:19.880> set<00:11:20.160> end<00:11:20.560> function<00:11:21.079> will<00:11:21.560> take<00:11:22.560> uh<00:11:23.040> various 00:11:23.470 --> 00:11:23.480 align:start position:0% um set end function will take uh various 00:11:23.480 --> 00:11:26.069 align:start position:0% um set end function will take uh various options<00:11:24.120> that<00:11:24.320> inform<00:11:24.720> you<00:11:24.839> know<00:11:25.240> set<00:11:25.920> and 00:11:26.069 --> 00:11:26.079 align:start position:0% options that inform you know set and 00:11:26.079 --> 00:11:27.590 align:start position:0% options that inform you know set and alter<00:11:26.480> Global<00:11:26.760> build<00:11:27.079> context<00:11:27.440> and<00:11:27.519> the 00:11:27.590 --> 00:11:27.600 align:start position:0% alter Global build context and the 00:11:27.600 --> 00:11:29.430 align:start position:0% alter Global build context and the source<00:11:27.920> path<00:11:28.079> is<00:11:28.200> one<00:11:28.279> of<00:11:28.440> those<00:11:28.639> things<00:11:29.320> so 00:11:29.430 --> 00:11:29.440 align:start position:0% source path is one of those things so 00:11:29.440 --> 00:11:31.030 align:start position:0% source path is one of those things so that<00:11:29.560> set<00:11:29.800> M<00:11:29.959> call<00:11:30.200> he<00:11:30.320> just<00:11:30.440> made<00:11:30.720> is 00:11:31.030 --> 00:11:31.040 align:start position:0% that set M call he just made is 00:11:31.040 --> 00:11:33.269 align:start position:0% that set M call he just made is analogous<00:11:31.480> to<00:11:31.600> the-<00:11:32.040> S<00:11:32.320> option<00:11:32.639> we<00:11:32.839> passed<00:11:33.120> to 00:11:33.269 --> 00:11:33.279 align:start position:0% analogous to the- S option we passed to 00:11:33.279 --> 00:11:35.269 align:start position:0% analogous to the- S option we passed to boot<00:11:33.560> when<00:11:33.680> we<00:11:33.800> were<00:11:34.000> showing<00:11:34.240> the<00:11:34.360> previous 00:11:35.269 --> 00:11:35.279 align:start position:0% boot when we were showing the previous 00:11:35.279 --> 00:11:37.590 align:start position:0% boot when we were showing the previous example<00:11:36.279> so<00:11:36.480> now<00:11:36.600> that<00:11:36.760> boot<00:11:37.000> knows<00:11:37.320> where<00:11:37.480> our 00:11:37.590 --> 00:11:37.600 align:start position:0% example so now that boot knows where our 00:11:37.600 --> 00:11:40.670 align:start position:0% example so now that boot knows where our Java<00:11:37.920> code<00:11:38.200> is<00:11:38.839> we<00:11:38.959> can<00:11:39.160> actually<00:11:40.040> create<00:11:40.440> the 00:11:40.670 --> 00:11:40.680 align:start position:0% Java code is we can actually create the 00:11:40.680 --> 00:11:42.670 align:start position:0% Java code is we can actually create the and<00:11:41.000> initialize<00:11:41.480> this<00:11:41.639> boot<00:11:41.920> pipeline<00:11:42.519> from 00:11:42.670 --> 00:11:42.680 align:start position:0% and initialize this boot pipeline from 00:11:42.680 --> 00:11:44.790 align:start position:0% and initialize this boot pipeline from the<00:11:42.800> rapple<00:11:43.399> using<00:11:43.680> this<00:11:43.800> boot<00:11:44.079> macro<00:11:44.600> which 00:11:44.790 --> 00:11:44.800 align:start position:0% the rapple using this boot macro which 00:11:44.800 --> 00:11:47.230 align:start position:0% the rapple using this boot macro which also<00:11:45.000> takes<00:11:45.320> a<00:11:45.440> series<00:11:45.680> of<00:11:45.880> tasks<00:11:46.839> of<00:11:46.959> course 00:11:47.230 --> 00:11:47.240 align:start position:0% also takes a series of tasks of course 00:11:47.240 --> 00:11:48.829 align:start position:0% also takes a series of tasks of course the<00:11:47.480> the<00:11:47.760> calling<00:11:48.079> Convention<00:11:48.399> of<00:11:48.480> the<00:11:48.600> task 00:11:48.829 --> 00:11:48.839 align:start position:0% the the calling Convention of the task 00:11:48.839 --> 00:11:50.110 align:start position:0% the the calling Convention of the task is<00:11:49.000> different<00:11:49.240> than<00:11:49.360> it<00:11:49.440> is<00:11:49.560> on<00:11:49.680> the<00:11:49.800> command 00:11:50.110 --> 00:11:50.120 align:start position:0% is different than it is on the command 00:11:50.120 --> 00:11:51.310 align:start position:0% is different than it is on the command line<00:11:50.320> because<00:11:50.440> you<00:11:50.519> know<00:11:50.760> these<00:11:50.839> are<00:11:50.959> clearly 00:11:51.310 --> 00:11:51.320 align:start position:0% line because you know these are clearly 00:11:51.320 --> 00:11:53.949 align:start position:0% line because you know these are clearly functions<00:11:51.639> we're<00:11:52.160> calling<00:11:53.160> uh<00:11:53.399> and<00:11:53.600> it's 00:11:53.949 --> 00:11:53.959 align:start position:0% functions we're calling uh and it's 00:11:53.959 --> 00:11:55.710 align:start position:0% functions we're calling uh and it's stringing<00:11:54.680> together<00:11:55.000> the<00:11:55.120> results<00:11:55.440> of<00:11:55.560> those 00:11:55.710 --> 00:11:55.720 align:start position:0% stringing together the results of those 00:11:55.720 --> 00:11:58.389 align:start position:0% stringing together the results of those function<00:11:56.000> calls<00:11:56.760> somehow<00:11:57.760> um<00:11:58.279> but 00:11:58.389 --> 00:11:58.399 align:start position:0% function calls somehow um but 00:11:58.399 --> 00:12:00.350 align:start position:0% function calls somehow um but nevertheless<00:11:58.920> it<00:11:59.000> works<00:11:59.600> and<00:11:59.800> does<00:12:00.040> the<00:12:00.120> same 00:12:00.350 --> 00:12:00.360 align:start position:0% nevertheless it works and does the same 00:12:00.360 --> 00:12:02.509 align:start position:0% nevertheless it works and does the same exact<00:12:00.680> thing<00:12:00.959> so<00:12:01.240> we<00:12:01.560> would<00:12:01.760> if<00:12:01.880> we<00:12:02.279> open 00:12:02.509 --> 00:12:02.519 align:start position:0% exact thing so we would if we open 00:12:02.519 --> 00:12:04.190 align:start position:0% exact thing so we would if we open another<00:12:02.760> reel<00:12:03.000> now<00:12:03.160> to<00:12:03.360> boot<00:12:03.600> DB<00:12:03.959> we<00:12:04.040> would 00:12:04.190 --> 00:12:04.200 align:start position:0% another reel now to boot DB we would 00:12:04.200 --> 00:12:06.550 align:start position:0% another reel now to boot DB we would find<00:12:04.399> the<00:12:04.480> same<00:12:04.680> result<00:12:05.040> we<00:12:05.120> could<00:12:05.360> add<00:12:05.560> this 00:12:06.550 --> 00:12:06.560 align:start position:0% find the same result we could add this 00:12:06.560 --> 00:12:08.350 align:start position:0% find the same result we could add this dependency<00:12:07.240> which<00:12:07.360> is<00:12:07.480> installed<00:12:07.839> locally<00:12:08.160> to 00:12:08.350 --> 00:12:08.360 align:start position:0% dependency which is installed locally to 00:12:08.360 --> 00:12:10.389 align:start position:0% dependency which is installed locally to our<00:12:08.680> our 00:12:10.389 --> 00:12:10.399 align:start position:0% our our 00:12:10.399 --> 00:12:14.870 align:start position:0% our our reppel<00:12:11.399> um<00:12:11.680> one<00:12:11.880> nice<00:12:12.120> thing<00:12:12.480> yeah<00:12:12.839> so<00:12:13.839> uh<00:12:14.760> if 00:12:14.870 --> 00:12:14.880 align:start position:0% reppel um one nice thing yeah so uh if 00:12:14.880 --> 00:12:17.110 align:start position:0% reppel um one nice thing yeah so uh if you<00:12:15.000> look<00:12:15.240> at<00:12:15.480> what<00:12:15.800> the<00:12:16.240> so<00:12:16.440> this<00:12:16.600> Java<00:12:16.880> C 00:12:17.110 --> 00:12:17.120 align:start position:0% you look at what the so this Java C 00:12:17.120 --> 00:12:19.509 align:start position:0% you look at what the so this Java C thing<00:12:17.240> we're<00:12:17.399> calling<00:12:17.639> a<00:12:18.079> function<00:12:19.079> what<00:12:19.240> is 00:12:19.509 --> 00:12:19.519 align:start position:0% thing we're calling a function what is 00:12:19.519 --> 00:12:21.430 align:start position:0% thing we're calling a function what is that<00:12:20.440> well<00:12:20.600> we<00:12:20.680> can<00:12:20.800> call<00:12:20.959> it<00:12:21.120> without<00:12:21.320> the 00:12:21.430 --> 00:12:21.440 align:start position:0% that well we can call it without the 00:12:21.440 --> 00:12:23.310 align:start position:0% that well we can call it without the boot<00:12:21.680> macro<00:12:22.199> and<00:12:22.320> we'll<00:12:22.480> see<00:12:22.680> that<00:12:22.800> it<00:12:22.920> is<00:12:23.199> it's 00:12:23.310 --> 00:12:23.320 align:start position:0% boot macro and we'll see that it is it's 00:12:23.320 --> 00:12:25.030 align:start position:0% boot macro and we'll see that it is it's a<00:12:23.440> function<00:12:23.720> call<00:12:23.920> and<00:12:24.040> it<00:12:24.120> seems<00:12:24.279> to<00:12:24.600> return 00:12:25.030 --> 00:12:25.040 align:start position:0% a function call and it seems to return 00:12:25.040 --> 00:12:25.949 align:start position:0% a function call and it seems to return another 00:12:25.949 --> 00:12:25.959 align:start position:0% another 00:12:25.959 --> 00:12:28.790 align:start position:0% another function<00:12:26.959> and<00:12:27.480> um<00:12:27.920> by<00:12:28.079> itself<00:12:28.360> it's<00:12:28.519> also<00:12:28.680> a 00:12:28.790 --> 00:12:28.800 align:start position:0% function and um by itself it's also a 00:12:28.800 --> 00:12:30.509 align:start position:0% function and um by itself it's also a function<00:12:29.240> various<00:12:29.800> we're<00:12:30.079> generating 00:12:30.509 --> 00:12:30.519 align:start position:0% function various we're generating 00:12:30.519 --> 00:12:32.710 align:start position:0% function various we're generating thingses<00:12:30.839> these<00:12:30.920> are<00:12:31.079> closure<00:12:31.440> functions<00:12:32.279> a 00:12:32.710 --> 00:12:32.720 align:start position:0% thingses these are closure functions a 00:12:32.720 --> 00:12:36.269 align:start position:0% thingses these are closure functions a function<00:12:33.440> it<00:12:33.560> is<00:12:33.760> a 00:12:36.269 --> 00:12:36.279 align:start position:0% 00:12:36.279 --> 00:12:38.750 align:start position:0% function<00:12:37.279> so<00:12:38.160> what<00:12:38.279> we're<00:12:38.399> doing<00:12:38.600> with<00:12:38.680> the 00:12:38.750 --> 00:12:38.760 align:start position:0% function so what we're doing with the 00:12:38.760 --> 00:12:40.150 align:start position:0% function so what we're doing with the boot<00:12:39.000> macro<00:12:39.360> and<00:12:39.480> what<00:12:39.600> we<00:12:39.680> were<00:12:39.800> doing<00:12:39.959> at<00:12:40.079> the 00:12:40.150 --> 00:12:40.160 align:start position:0% boot macro and what we were doing at the 00:12:40.160 --> 00:12:41.949 align:start position:0% boot macro and what we were doing at the command<00:12:40.440> line<00:12:40.600> were<00:12:40.800> both<00:12:41.040> actually<00:12:41.360> function 00:12:41.949 --> 00:12:41.959 align:start position:0% command line were both actually function 00:12:41.959 --> 00:12:43.949 align:start position:0% command line were both actually function composition<00:12:42.920> slightly<00:12:43.199> different<00:12:43.440> syntax 00:12:43.949 --> 00:12:43.959 align:start position:0% composition slightly different syntax 00:12:43.959 --> 00:12:47.750 align:start position:0% composition slightly different syntax used<00:12:44.360> to<00:12:44.720> perform<00:12:45.519> the 00:12:47.750 --> 00:12:47.760 align:start position:0% used to perform the 00:12:47.760 --> 00:12:52.590 align:start position:0% used to perform the composition<00:12:48.800> so<00:12:49.800> we<00:12:50.000> actually<00:12:50.880> have<00:12:51.880> yeah<00:12:52.279> so 00:12:52.590 --> 00:12:52.600 align:start position:0% composition so we actually have yeah so 00:12:52.600 --> 00:12:55.069 align:start position:0% composition so we actually have yeah so um<00:12:52.959> yeah<00:12:53.480> go<00:12:53.560> ahead<00:12:54.240> yeah<00:12:54.399> so<00:12:54.680> what<00:12:54.760> we<00:12:54.880> did 00:12:55.069 --> 00:12:55.079 align:start position:0% um yeah go ahead yeah so what we did 00:12:55.079 --> 00:12:57.269 align:start position:0% um yeah go ahead yeah so what we did just<00:12:55.240> now<00:12:55.480> is<00:12:55.639> we<00:12:55.760> built<00:12:55.959> up<00:12:56.120> this<00:12:56.320> Pipeline 00:12:57.269 --> 00:12:57.279 align:start position:0% just now is we built up this Pipeline 00:12:57.279 --> 00:12:58.790 align:start position:0% just now is we built up this Pipeline and<00:12:57.560> we<00:12:57.680> did<00:12:57.800> it<00:12:57.920> in<00:12:58.000> the<00:12:58.120> command<00:12:58.399> line<00:12:58.600> at<00:12:58.720> the 00:12:58.790 --> 00:12:58.800 align:start position:0% and we did it in the command line at the 00:12:58.800 --> 00:13:00.590 align:start position:0% and we did it in the command line at the rep<00:12:59.600> and<00:12:59.680> it's<00:12:59.839> important<00:13:00.120> that<00:13:00.199> you<00:13:00.320> be<00:13:00.440> able 00:13:00.590 --> 00:13:00.600 align:start position:0% rep and it's important that you be able 00:13:00.600 --> 00:13:02.629 align:start position:0% rep and it's important that you be able to<00:13:00.720> do<00:13:00.920> them<00:13:01.240> both<00:13:01.480> ways<00:13:01.920> because<00:13:02.360> when<00:13:02.440> you're 00:13:02.629 --> 00:13:02.639 align:start position:0% to do them both ways because when you're 00:13:02.639 --> 00:13:05.069 align:start position:0% to do them both ways because when you're building<00:13:03.160> you<00:13:03.279> need<00:13:03.440> to<00:13:03.600> explore<00:13:03.959> a<00:13:04.120> bit<00:13:04.839> and 00:13:05.069 --> 00:13:05.079 align:start position:0% building you need to explore a bit and 00:13:05.079 --> 00:13:07.269 align:start position:0% building you need to explore a bit and so<00:13:05.279> this<00:13:05.360> is<00:13:05.480> what<00:13:05.600> the<00:13:05.680> pipeline<00:13:06.079> looks 00:13:07.269 --> 00:13:07.279 align:start position:0% so this is what the pipeline looks 00:13:07.279 --> 00:13:10.310 align:start position:0% so this is what the pipeline looks like<00:13:08.320> um<00:13:09.320> it's<00:13:09.480> kind<00:13:09.600> of<00:13:09.720> similar<00:13:10.000> to<00:13:10.160> what<00:13:10.240> you 00:13:10.310 --> 00:13:10.320 align:start position:0% like um it's kind of similar to what you 00:13:10.320 --> 00:13:11.990 align:start position:0% like um it's kind of similar to what you would<00:13:10.440> do<00:13:10.560> in<00:13:10.639> Unix<00:13:11.120> you<00:13:11.199> know<00:13:11.320> Unix<00:13:11.639> is<00:13:11.800> really 00:13:11.990 --> 00:13:12.000 align:start position:0% would do in Unix you know Unix is really 00:13:12.000 --> 00:13:13.470 align:start position:0% would do in Unix you know Unix is really powerful<00:13:12.399> for<00:13:12.600> having<00:13:12.959> you<00:13:13.040> know<00:13:13.160> it's<00:13:13.320> well 00:13:13.470 --> 00:13:13.480 align:start position:0% powerful for having you know it's well 00:13:13.480 --> 00:13:15.829 align:start position:0% powerful for having you know it's well known<00:13:13.720> for<00:13:14.000> the<00:13:14.199> the<00:13:14.320> power<00:13:14.480> of<00:13:14.680> small<00:13:14.920> tools 00:13:15.829 --> 00:13:15.839 align:start position:0% known for the the power of small tools 00:13:15.839 --> 00:13:17.990 align:start position:0% known for the the power of small tools and<00:13:16.079> an<00:13:16.240> interface<00:13:16.920> between<00:13:17.240> the<00:13:17.360> small<00:13:17.600> tools 00:13:17.990 --> 00:13:18.000 align:start position:0% and an interface between the small tools 00:13:18.000 --> 00:13:19.430 align:start position:0% and an interface between the small tools that<00:13:18.079> you<00:13:18.160> can<00:13:18.360> chain<00:13:18.639> them<00:13:18.920> together<00:13:19.160> in 00:13:19.430 --> 00:13:19.440 align:start position:0% that you can chain them together in 00:13:19.440 --> 00:13:22.150 align:start position:0% that you can chain them together in different<00:13:20.120> different<00:13:20.480> ways<00:13:20.959> to<00:13:21.160> do<00:13:21.519> a<00:13:21.839> large 00:13:22.150 --> 00:13:22.160 align:start position:0% different different ways to do a large 00:13:22.160 --> 00:13:24.269 align:start position:0% different different ways to do a large number<00:13:22.360> of<00:13:22.720> things<00:13:23.720> and<00:13:23.920> that's<00:13:24.040> what<00:13:24.160> the 00:13:24.269 --> 00:13:24.279 align:start position:0% number of things and that's what the 00:13:24.279 --> 00:13:25.990 align:start position:0% number of things and that's what the boot<00:13:24.839> that's<00:13:24.959> what<00:13:25.120> boot<00:13:25.399> provides<00:13:25.760> with<00:13:25.880> the 00:13:25.990 --> 00:13:26.000 align:start position:0% boot that's what boot provides with the 00:13:26.000 --> 00:13:28.150 align:start position:0% boot that's what boot provides with the boot<00:13:26.320> executable<00:13:27.279> and<00:13:27.399> the<00:13:27.480> boot<00:13:27.720> macro<00:13:28.079> if 00:13:28.150 --> 00:13:28.160 align:start position:0% boot executable and the boot macro if 00:13:28.160 --> 00:13:30.030 align:start position:0% boot executable and the boot macro if you're<00:13:28.320> in<00:13:28.480> the<00:13:28.760> if<00:13:28.839> you're<00:13:28.959> in<00:13:29.160> the<00:13:29.240> repel<00:13:29.880> and 00:13:30.030 --> 00:13:30.040 align:start position:0% you're in the if you're in the repel and 00:13:30.040 --> 00:13:32.189 align:start position:0% you're in the if you're in the repel and basically<00:13:30.519> what<00:13:31.160> what's<00:13:31.399> being<00:13:31.680> provided 00:13:32.189 --> 00:13:32.199 align:start position:0% basically what what's being provided 00:13:32.199 --> 00:13:35.509 align:start position:0% basically what what's being provided here<00:13:32.959> is<00:13:33.760> the<00:13:34.199> the<00:13:34.440> abstra<00:13:34.920> the<00:13:35.079> process 00:13:35.509 --> 00:13:35.519 align:start position:0% here is the the abstra the process 00:13:35.519 --> 00:13:37.829 align:start position:0% here is the the abstra the process abstraction<00:13:36.480> and<00:13:36.600> the<00:13:36.760> connective<00:13:37.600> so<00:13:37.720> you 00:13:37.829 --> 00:13:37.839 align:start position:0% abstraction and the connective so you 00:13:37.839 --> 00:13:39.949 align:start position:0% abstraction and the connective so you need<00:13:37.959> to<00:13:38.160> have<00:13:38.399> these<00:13:38.560> little<00:13:38.920> processes<00:13:39.839> that 00:13:39.949 --> 00:13:39.959 align:start position:0% need to have these little processes that 00:13:39.959 --> 00:13:42.430 align:start position:0% need to have these little processes that all<00:13:40.199> communicate<00:13:41.199> meaning<00:13:41.600> they<00:13:42.160> that<00:13:42.320> they 00:13:42.430 --> 00:13:42.440 align:start position:0% all communicate meaning they that they 00:13:42.440 --> 00:13:45.069 align:start position:0% all communicate meaning they that they take<00:13:42.680> the<00:13:42.880> same<00:13:43.160> kind<00:13:43.279> of<00:13:43.480> connective<00:13:44.480> object 00:13:45.069 --> 00:13:45.079 align:start position:0% take the same kind of connective object 00:13:45.079 --> 00:13:47.550 align:start position:0% take the same kind of connective object as<00:13:45.240> input<00:13:45.639> and<00:13:45.800> they<00:13:46.600> emit<00:13:46.920> the<00:13:47.040> same<00:13:47.279> kind<00:13:47.399> of 00:13:47.550 --> 00:13:47.560 align:start position:0% as input and they emit the same kind of 00:13:47.560 --> 00:13:49.110 align:start position:0% as input and they emit the same kind of connect<00:13:47.920> Bo<00:13:48.160> so<00:13:48.240> you<00:13:48.320> can<00:13:48.480> connect<00:13:48.720> them<00:13:48.839> all 00:13:49.110 --> 00:13:49.120 align:start position:0% connect Bo so you can connect them all 00:13:49.120 --> 00:13:52.069 align:start position:0% connect Bo so you can connect them all together<00:13:49.720> in<00:13:49.880> Unix<00:13:50.440> the<00:13:50.839> uh<00:13:51.240> the<00:13:51.440> process<00:13:51.720> is<00:13:51.839> a 00:13:52.069 --> 00:13:52.079 align:start position:0% together in Unix the uh the process is a 00:13:52.079 --> 00:13:54.590 align:start position:0% together in Unix the uh the process is a program<00:13:53.079> and<00:13:53.320> they<00:13:53.519> pass<00:13:53.800> text<00:13:54.160> between<00:13:54.480> each 00:13:54.590 --> 00:13:54.600 align:start position:0% program and they pass text between each 00:13:54.600 --> 00:13:56.990 align:start position:0% program and they pass text between each other<00:13:55.399> with<00:13:55.560> boot<00:13:55.920> you<00:13:56.079> have<00:13:56.320> the<00:13:56.519> task<00:13:56.880> which 00:13:56.990 --> 00:13:57.000 align:start position:0% other with boot you have the task which 00:13:57.000 --> 00:13:59.110 align:start position:0% other with boot you have the task which is<00:13:57.079> a<00:13:57.360> function<00:13:58.360> a<00:13:58.440> special<00:13:58.680> kind<00:13:58.800> of<00:13:58.880> fun 00:13:59.110 --> 00:13:59.120 align:start position:0% is a function a special kind of fun 00:13:59.120 --> 00:14:01.430 align:start position:0% is a function a special kind of fun function<00:13:59.880> and<00:14:00.320> uh<00:14:00.680> the<00:14:00.800> thing<00:14:00.920> that<00:14:01.000> they<00:14:01.199> pass 00:14:01.430 --> 00:14:01.440 align:start position:0% function and uh the thing that they pass 00:14:01.440 --> 00:14:03.150 align:start position:0% function and uh the thing that they pass between<00:14:01.839> themselves<00:14:02.279> is<00:14:02.440> this<00:14:02.600> immutable 00:14:03.150 --> 00:14:03.160 align:start position:0% between themselves is this immutable 00:14:03.160 --> 00:14:04.629 align:start position:0% between themselves is this immutable file 00:14:04.629 --> 00:14:04.639 align:start position:0% file 00:14:04.639 --> 00:14:06.949 align:start position:0% file set<00:14:05.639> so<00:14:05.800> here's<00:14:05.959> what<00:14:06.079> a<00:14:06.240> task<00:14:06.519> looks<00:14:06.759> like 00:14:06.949 --> 00:14:06.959 align:start position:0% set so here's what a task looks like 00:14:06.959 --> 00:14:11.829 align:start position:0% set so here's what a task looks like basically<00:14:07.920> it<00:14:08.079> is<00:14:08.399> a<00:14:08.600> task<00:14:08.920> is<00:14:09.560> um<00:14:10.240> a<00:14:10.839> function 00:14:11.829 --> 00:14:11.839 align:start position:0% basically it is a task is um a function 00:14:11.839 --> 00:14:13.949 align:start position:0% basically it is a task is um a function uh<00:14:12.120> dep<00:14:12.440> task<00:14:12.720> actually<00:14:13.079> returns<00:14:13.440> a<00:14:13.600> function 00:14:13.949 --> 00:14:13.959 align:start position:0% uh dep task actually returns a function 00:14:13.959 --> 00:14:16.110 align:start position:0% uh dep task actually returns a function it's<00:14:14.160> just<00:14:14.360> it<00:14:14.480> adds<00:14:14.680> some<00:14:14.800> metadata<00:14:15.800> so<00:14:15.920> it's 00:14:16.110 --> 00:14:16.120 align:start position:0% it's just it adds some metadata so it's 00:14:16.120 --> 00:14:18.829 align:start position:0% it's just it adds some metadata so it's basically<00:14:16.440> defund<00:14:17.000> plus<00:14:17.480> metadata<00:14:18.480> takes<00:14:18.680> an 00:14:18.829 --> 00:14:18.839 align:start position:0% basically defund plus metadata takes an 00:14:18.839 --> 00:14:20.790 align:start position:0% basically defund plus metadata takes an argument<00:14:19.639> which<00:14:19.720> is<00:14:19.880> how<00:14:20.040> you<00:14:20.240> configure 00:14:20.790 --> 00:14:20.800 align:start position:0% argument which is how you configure 00:14:20.800 --> 00:14:22.670 align:start position:0% argument which is how you configure that's<00:14:21.000> how<00:14:21.120> you<00:14:21.279> parameterize<00:14:22.000> tasks<00:14:22.440> so<00:14:22.560> the 00:14:22.670 --> 00:14:22.680 align:start position:0% that's how you parameterize tasks so the 00:14:22.680 --> 00:14:26.509 align:start position:0% that's how you parameterize tasks so the command<00:14:22.920> line<00:14:23.120> options<00:14:23.399> went<00:14:23.920> there<00:14:25.120> um<00:14:26.120> the 00:14:26.509 --> 00:14:26.519 align:start position:0% command line options went there um the 00:14:26.519 --> 00:14:30.350 align:start position:0% command line options went there um the yellow<00:14:27.519> is<00:14:27.920> where<00:14:28.279> a<00:14:28.560> task<00:14:28.839> can<00:14:29.199> actually<00:14:29.920> uh 00:14:30.350 --> 00:14:30.360 align:start position:0% yellow is where a task can actually uh 00:14:30.360 --> 00:14:32.550 align:start position:0% yellow is where a task can actually uh can<00:14:30.600> have<00:14:31.079> accumulated<00:14:31.680> state<00:14:32.160> so<00:14:32.279> it's<00:14:32.399> sort 00:14:32.550 --> 00:14:32.560 align:start position:0% can have accumulated state so it's sort 00:14:32.560 --> 00:14:35.590 align:start position:0% can have accumulated state so it's sort of<00:14:32.720> like<00:14:32.839> a<00:14:32.959> stateful<00:14:33.800> transducer<00:14:34.800> um<00:14:35.399> if<00:14:35.480> you 00:14:35.590 --> 00:14:35.600 align:start position:0% of like a stateful transducer um if you 00:14:35.600 --> 00:14:37.710 align:start position:0% of like a stateful transducer um if you know<00:14:35.759> about<00:14:36.040> those<00:14:36.279> or<00:14:37.079> you<00:14:37.199> know<00:14:37.320> if<00:14:37.399> you<00:14:37.560> had 00:14:37.710 --> 00:14:37.720 align:start position:0% know about those or you know if you had 00:14:37.720 --> 00:14:40.030 align:start position:0% know about those or you know if you had a<00:14:38.199> a<00:14:38.279> middleware<00:14:38.839> factory<00:14:39.240> you<00:14:39.399> could<00:14:39.880> have 00:14:40.030 --> 00:14:40.040 align:start position:0% a a middleware factory you could have 00:14:40.040 --> 00:14:42.910 align:start position:0% a a middleware factory you could have state<00:14:40.600> there<00:14:41.600> um<00:14:41.880> and<00:14:42.040> then<00:14:42.360> the<00:14:42.480> green<00:14:42.720> and 00:14:42.910 --> 00:14:42.920 align:start position:0% state there um and then the green and 00:14:42.920 --> 00:14:45.710 align:start position:0% state there um and then the green and blue<00:14:43.600> is<00:14:43.800> the<00:14:43.959> standard<00:14:44.320> middleware<00:14:44.800> pattern 00:14:45.710 --> 00:14:45.720 align:start position:0% blue is the standard middleware pattern 00:14:45.720 --> 00:14:49.310 align:start position:0% blue is the standard middleware pattern where<00:14:45.920> you<00:14:46.079> have<00:14:46.360> a<00:14:46.519> Handler<00:14:47.320> that<00:14:47.759> um<00:14:48.360> passes 00:14:49.310 --> 00:14:49.320 align:start position:0% where you have a Handler that um passes 00:14:49.320 --> 00:14:53.069 align:start position:0% where you have a Handler that um passes after<00:14:49.800> processing<00:14:50.800> the<00:14:51.199> uh<00:14:52.199> the<00:14:52.360> file<00:14:52.639> set<00:14:52.880> it 00:14:53.069 --> 00:14:53.079 align:start position:0% after processing the uh the file set it 00:14:53.079 --> 00:14:54.670 align:start position:0% after processing the uh the file set it passes<00:14:53.320> it<00:14:53.440> to<00:14:53.519> the<00:14:53.600> next<00:14:53.839> Handler<00:14:54.320> which<00:14:54.480> then 00:14:54.670 --> 00:14:54.680 align:start position:0% passes it to the next Handler which then 00:14:54.680 --> 00:14:56.710 align:start position:0% passes it to the next Handler which then continues<00:14:55.440> so<00:14:55.560> you<00:14:55.720> have<00:14:55.880> layers<00:14:56.160> of 00:14:56.710 --> 00:14:56.720 align:start position:0% continues so you have layers of 00:14:56.720 --> 00:14:59.069 align:start position:0% continues so you have layers of middleware<00:14:57.720> uh<00:14:57.839> we<00:14:57.920> have<00:14:58.040> a<00:14:58.120> little<00:14:58.360> macro 00:14:59.069 --> 00:14:59.079 align:start position:0% middleware uh we have a little macro 00:14:59.079 --> 00:15:00.470 align:start position:0% middleware uh we have a little macro that<00:14:59.199> allows<00:14:59.480> you<00:14:59.560> to<00:14:59.680> simplify<00:15:00.120> this<00:15:00.240> in<00:15:00.360> a 00:15:00.470 --> 00:15:00.480 align:start position:0% that allows you to simplify this in a 00:15:00.480 --> 00:15:03.389 align:start position:0% that allows you to simplify this in a lot<00:15:00.600> of<00:15:01.079> cases<00:15:02.079> um<00:15:02.759> sometimes<00:15:02.920> you<00:15:03.040> can't<00:15:03.199> use 00:15:03.389 --> 00:15:03.399 align:start position:0% lot of cases um sometimes you can't use 00:15:03.399 --> 00:15:06.110 align:start position:0% lot of cases um sometimes you can't use this<00:15:03.759> but<00:15:04.759> this<00:15:04.880> is<00:15:05.240> this<00:15:05.360> is<00:15:05.560> essentially 00:15:06.110 --> 00:15:06.120 align:start position:0% this but this is this is essentially 00:15:06.120 --> 00:15:09.310 align:start position:0% this but this is this is essentially what<00:15:06.279> a<00:15:06.519> task<00:15:06.800> is<00:15:07.399> doing<00:15:08.399> so<00:15:08.560> you<00:15:08.759> have 00:15:09.310 --> 00:15:09.320 align:start position:0% what a task is doing so you have 00:15:09.320 --> 00:15:13.990 align:start position:0% what a task is doing so you have accumulated<00:15:09.920> State 00:15:13.990 --> 00:15:14.000 align:start position:0% 00:15:14.000 --> 00:15:18.030 align:start position:0% Handler<00:15:15.000> so<00:15:15.480> now<00:15:15.680> we<00:15:15.920> have<00:15:16.839> uh<00:15:17.240> shown<00:15:17.759> how<00:15:17.920> we 00:15:18.030 --> 00:15:18.040 align:start position:0% Handler so now we have uh shown how we 00:15:18.040 --> 00:15:21.470 align:start position:0% Handler so now we have uh shown how we can<00:15:18.240> compose<00:15:19.160> pre-existing<00:15:20.079> tasks<00:15:21.079> um<00:15:21.320> but 00:15:21.470 --> 00:15:21.480 align:start position:0% can compose pre-existing tasks um but 00:15:21.480 --> 00:15:24.269 align:start position:0% can compose pre-existing tasks um but Misha's<00:15:21.959> had<00:15:22.120> to<00:15:22.759> uh<00:15:23.000> type<00:15:23.240> in<00:15:24.079> that 00:15:24.269 --> 00:15:24.279 align:start position:0% Misha's had to uh type in that 00:15:24.279 --> 00:15:25.870 align:start position:0% Misha's had to uh type in that composition<00:15:24.720> multiple<00:15:25.040> times<00:15:25.320> Now<00:15:25.519> command 00:15:25.870 --> 00:15:25.880 align:start position:0% composition multiple times Now command 00:15:25.880 --> 00:15:28.350 align:start position:0% composition multiple times Now command line<00:15:26.399> reppel<00:15:27.399> and<00:15:27.560> he<00:15:27.680> might<00:15:27.800> just<00:15:27.920> St<00:15:28.120> off<00:15:28.240> the 00:15:28.350 --> 00:15:28.360 align:start position:0% line reppel and he might just St off the 00:15:28.360 --> 00:15:29.949 align:start position:0% line reppel and he might just St off the stage<00:15:29.000> do<00:15:29.079> it<00:15:29.240> again<00:15:29.440> so<00:15:29.600> we're<00:15:29.720> going<00:15:29.839> to 00:15:29.949 --> 00:15:29.959 align:start position:0% stage do it again so we're going to 00:15:29.959 --> 00:15:32.430 align:start position:0% stage do it again so we're going to introduce<00:15:30.360> a<00:15:30.480> new<00:15:30.720> thing<00:15:31.639> uh<00:15:31.759> this<00:15:31.920> death<00:15:32.199> task 00:15:32.430 --> 00:15:32.440 align:start position:0% introduce a new thing uh this death task 00:15:32.440 --> 00:15:34.670 align:start position:0% introduce a new thing uh this death task which<00:15:32.560> you<00:15:32.639> saw<00:15:32.759> in<00:15:32.880> the<00:15:33.079> slide<00:15:34.079> death<00:15:34.319> task<00:15:34.560> is 00:15:34.670 --> 00:15:34.680 align:start position:0% which you saw in the slide death task is 00:15:34.680 --> 00:15:37.389 align:start position:0% which you saw in the slide death task is a<00:15:34.759> way<00:15:34.880> for<00:15:35.000> you<00:15:35.120> to<00:15:35.360> name<00:15:36.199> compositions<00:15:37.199> of 00:15:37.389 --> 00:15:37.399 align:start position:0% a way for you to name compositions of 00:15:37.399 --> 00:15:38.670 align:start position:0% a way for you to name compositions of either<00:15:37.639> existing<00:15:38.000> things<00:15:38.240> or<00:15:38.360> a<00:15:38.480> new 00:15:38.670 --> 00:15:38.680 align:start position:0% either existing things or a new 00:15:38.680 --> 00:15:41.590 align:start position:0% either existing things or a new functionality<00:15:39.680> so<00:15:39.959> defining<00:15:40.279> a<00:15:40.519> task<00:15:41.199> is<00:15:41.440> like 00:15:41.590 --> 00:15:41.600 align:start position:0% functionality so defining a task is like 00:15:41.600 --> 00:15:43.990 align:start position:0% functionality so defining a task is like creating<00:15:41.880> a<00:15:42.000> Plugin<00:15:42.399> or<00:15:42.600> extending<00:15:43.120> boot<00:15:43.800> um 00:15:43.990 --> 00:15:44.000 align:start position:0% creating a Plugin or extending boot um 00:15:44.000 --> 00:15:45.509 align:start position:0% creating a Plugin or extending boot um like<00:15:44.079> I<00:15:44.160> said<00:15:44.399> can<00:15:44.720> use<00:15:44.839> it<00:15:44.959> to<00:15:45.120> compose 00:15:45.509 --> 00:15:45.519 align:start position:0% like I said can use it to compose 00:15:45.519 --> 00:15:47.230 align:start position:0% like I said can use it to compose existing<00:15:45.880> things<00:15:46.480> or<00:15:46.680> this<00:15:46.759> is<00:15:46.880> the<00:15:47.040> place 00:15:47.230 --> 00:15:47.240 align:start position:0% existing things or this is the place 00:15:47.240 --> 00:15:49.030 align:start position:0% existing things or this is the place where<00:15:47.360> you<00:15:47.639> might<00:15:48.120> Implement<00:15:48.519> new 00:15:49.030 --> 00:15:49.040 align:start position:0% where you might Implement new 00:15:49.040 --> 00:15:51.269 align:start position:0% where you might Implement new functionality<00:15:50.040> here<00:15:50.279> we're<00:15:50.720> just<00:15:50.920> composing 00:15:51.269 --> 00:15:51.279 align:start position:0% functionality here we're just composing 00:15:51.279 --> 00:15:52.749 align:start position:0% functionality here we're just composing the<00:15:51.440> existing<00:15:51.759> things<00:15:52.000> like<00:15:52.120> we<00:15:52.240> did<00:15:52.440> before 00:15:52.749 --> 00:15:52.759 align:start position:0% the existing things like we did before 00:15:52.759 --> 00:15:54.269 align:start position:0% the existing things like we did before but<00:15:52.880> we're<00:15:53.040> just<00:15:53.160> giving<00:15:53.600> this<00:15:53.759> whole<00:15:54.000> process 00:15:54.269 --> 00:15:54.279 align:start position:0% but we're just giving this whole process 00:15:54.279 --> 00:15:55.629 align:start position:0% but we're just giving this whole process a<00:15:54.440> name 00:15:55.629 --> 00:15:55.639 align:start position:0% a name 00:15:55.639 --> 00:15:58.430 align:start position:0% a name build<00:15:56.639> now<00:15:56.920> the<00:15:57.319> uh<00:15:57.440> you'll<00:15:57.639> notice<00:15:57.920> the<00:15:58.079> long 00:15:58.430 --> 00:15:58.440 align:start position:0% build now the uh you'll notice the long 00:15:58.440 --> 00:16:00.590 align:start position:0% build now the uh you'll notice the long options<00:15:59.240> that<00:15:59.440> the<00:15:59.680> task<00:16:00.079> con<00:16:00.279> structor 00:16:00.590 --> 00:16:00.600 align:start position:0% options that the task con structor 00:16:00.600 --> 00:16:02.470 align:start position:0% options that the task con structor functions<00:16:00.880> are<00:16:01.079> taking<00:16:01.440> like<00:16:01.680> colon<00:16:02.120> project 00:16:02.470 --> 00:16:02.480 align:start position:0% functions are taking like colon project 00:16:02.480 --> 00:16:06.269 align:start position:0% functions are taking like colon project oron<00:16:03.360> main<00:16:04.360> um<00:16:05.040> those<00:16:05.240> are<00:16:05.480> the<00:16:05.600> same<00:16:05.959> options 00:16:06.269 --> 00:16:06.279 align:start position:0% oron main um those are the same options 00:16:06.279 --> 00:16:08.230 align:start position:0% oron main um those are the same options we<00:16:06.399> were<00:16:06.600> passing<00:16:06.959> on<00:16:07.120> the<00:16:07.240> command<00:16:07.600> line 00:16:08.230 --> 00:16:08.240 align:start position:0% we were passing on the command line 00:16:08.240 --> 00:16:10.150 align:start position:0% we were passing on the command line they're<00:16:08.440> just<00:16:08.560> the<00:16:08.759> long<00:16:09.120> options<00:16:09.680> so<00:16:09.920> boot 00:16:10.150 --> 00:16:10.160 align:start position:0% they're just the long options so boot 00:16:10.160 --> 00:16:11.590 align:start position:0% they're just the long options so boot supports<00:16:10.519> short<00:16:10.759> and<00:16:10.920> long<00:16:11.120> options<00:16:11.399> at<00:16:11.519> the 00:16:11.590 --> 00:16:11.600 align:start position:0% supports short and long options at the 00:16:11.600 --> 00:16:13.470 align:start position:0% supports short and long options at the command<00:16:11.920> line<00:16:12.399> and<00:16:12.519> in<00:16:12.600> the<00:16:12.720> reppel<00:16:13.120> all<00:16:13.319> the 00:16:13.470 --> 00:16:13.480 align:start position:0% command line and in the reppel all the 00:16:13.480 --> 00:16:15.710 align:start position:0% command line and in the reppel all the options<00:16:13.759> are<00:16:13.959> keyword<00:16:14.279> arguments<00:16:14.800> that 00:16:15.710 --> 00:16:15.720 align:start position:0% options are keyword arguments that 00:16:15.720 --> 00:16:19.949 align:start position:0% options are keyword arguments that are<00:16:16.720> match<00:16:16.920> up<00:16:17.079> with<00:16:17.160> the<00:16:17.279> long<00:16:17.480> options 00:16:19.949 --> 00:16:19.959 align:start position:0% are match up with the long options 00:16:19.959 --> 00:16:24.189 align:start position:0% are match up with the long options line<00:16:21.319> um<00:16:22.319> so<00:16:23.000> did<00:16:23.120> you<00:16:23.360> yeah<00:16:23.480> did<00:16:23.600> you<00:16:23.720> do<00:16:23.920> doc 00:16:24.189 --> 00:16:24.199 align:start position:0% line um so did you yeah did you do doc 00:16:24.199 --> 00:16:28.269 align:start position:0% line um so did you yeah did you do doc on<00:16:25.000> build<00:16:26.000> yeah<00:16:26.920> so<00:16:27.079> one<00:16:27.160> of<00:16:27.279> the<00:16:27.360> things<00:16:27.600> deas 00:16:28.269 --> 00:16:28.279 align:start position:0% on build yeah so one of the things deas 00:16:28.279 --> 00:16:31.350 align:start position:0% on build yeah so one of the things deas does<00:16:28.759> uh<00:16:29.199> so<00:16:29.519> tasks<00:16:29.800> are<00:16:30.000> regular<00:16:30.360> functions 00:16:31.350 --> 00:16:31.360 align:start position:0% does uh so tasks are regular functions 00:16:31.360 --> 00:16:33.110 align:start position:0% does uh so tasks are regular functions but<00:16:31.519> we<00:16:31.680> prefer<00:16:31.959> using<00:16:32.199> the<00:16:32.319> death<00:16:32.560> task<00:16:32.759> macro 00:16:33.110 --> 00:16:33.120 align:start position:0% but we prefer using the death task macro 00:16:33.120 --> 00:16:34.990 align:start position:0% but we prefer using the death task macro to<00:16:33.199> create<00:16:33.480> them<00:16:33.720> just<00:16:33.920> because<00:16:34.399> they<00:16:34.800> have 00:16:34.990 --> 00:16:35.000 align:start position:0% to create them just because they have 00:16:35.000 --> 00:16:37.150 align:start position:0% to create them just because they have metadata<00:16:35.480> on<00:16:35.600> them<00:16:35.800> that<00:16:35.920> who<00:16:36.199> can<00:16:36.360> use<00:16:36.560> to 00:16:37.150 --> 00:16:37.160 align:start position:0% metadata on them that who can use to 00:16:37.160 --> 00:16:40.430 align:start position:0% metadata on them that who can use to inform<00:16:37.519> itself<00:16:37.920> about<00:16:38.360> them<00:16:39.360> here<00:16:40.040> is<00:16:40.319> the 00:16:40.430 --> 00:16:40.440 align:start position:0% inform itself about them here is the 00:16:40.440 --> 00:16:42.230 align:start position:0% inform itself about them here is the Misha<00:16:40.680> is<00:16:40.800> showing<00:16:41.079> that<00:16:41.160> the<00:16:41.279> build<00:16:41.600> task<00:16:42.000> has 00:16:42.230 --> 00:16:42.240 align:start position:0% Misha is showing that the build task has 00:16:42.240 --> 00:16:44.350 align:start position:0% Misha is showing that the build task has a<00:16:42.399> documentation<00:16:42.959> scen<00:16:43.399> and<00:16:43.600> and<00:16:43.839> supports 00:16:44.350 --> 00:16:44.360 align:start position:0% a documentation scen and and supports 00:16:44.360 --> 00:16:46.269 align:start position:0% a documentation scen and and supports Dash<00:16:45.360> which<00:16:45.519> was<00:16:45.759> functionality 00:16:46.269 --> 00:16:46.279 align:start position:0% Dash which was functionality 00:16:46.279 --> 00:16:48.590 align:start position:0% Dash which was functionality automatically<00:16:46.800> provided<00:16:47.120> by<00:16:47.480> death<00:16:47.759> task<00:16:48.360> and 00:16:48.590 --> 00:16:48.600 align:start position:0% automatically provided by death task and 00:16:48.600 --> 00:16:51.470 align:start position:0% automatically provided by death task and all<00:16:48.720> the<00:16:48.839> other<00:16:49.040> tasks<00:16:49.399> also<00:16:49.639> can<00:16:49.800> be<00:16:50.759> um 00:16:51.470 --> 00:16:51.480 align:start position:0% all the other tasks also can be um 00:16:51.480 --> 00:16:53.110 align:start position:0% all the other tasks also can be um researched<00:16:51.959> at<00:16:52.040> the<00:16:52.120> command<00:16:52.440> line<00:16:52.720> or<00:16:52.920> at<00:16:53.000> the 00:16:53.110 --> 00:16:53.120 align:start position:0% researched at the command line or at the 00:16:53.120 --> 00:16:56.350 align:start position:0% researched at the command line or at the rep<00:16:53.519> same 00:16:56.350 --> 00:16:56.360 align:start position:0% 00:16:56.360 --> 00:16:59.230 align:start position:0% way<00:16:57.360> so<00:16:57.519> we<00:16:57.639> have<00:16:57.720> a<00:16:57.920> problem<00:16:58.160> with<00:16:58.240> our<00:16:58.480> thing 00:16:59.230 --> 00:16:59.240 align:start position:0% way so we have a problem with our thing 00:16:59.240 --> 00:17:01.949 align:start position:0% way so we have a problem with our thing no<00:16:59.399> worries<00:16:59.920> I<00:17:00.040> have<00:17:00.319> RL<00:17:00.759> wrap<00:17:01.279> going<00:17:01.440> on<00:17:01.639> here 00:17:01.949 --> 00:17:01.959 align:start position:0% no worries I have RL wrap going on here 00:17:01.959 --> 00:17:06.150 align:start position:0% no worries I have RL wrap going on here oh<00:17:02.199> nice<00:17:03.079> yeah<00:17:03.920> fix<00:17:04.400> it<00:17:05.400> so<00:17:05.559> the<00:17:05.720> problem<00:17:06.000> is 00:17:06.150 --> 00:17:06.160 align:start position:0% oh nice yeah fix it so the problem is 00:17:06.160 --> 00:17:09.470 align:start position:0% oh nice yeah fix it so the problem is that<00:17:06.480> the<00:17:07.120> project<00:17:08.000> or<00:17:08.199> the<00:17:08.520> Palm<00:17:08.839> task<00:17:09.160> needs 00:17:09.470 --> 00:17:09.480 align:start position:0% that the project or the Palm task needs 00:17:09.480 --> 00:17:11.429 align:start position:0% that the project or the Palm task needs in<00:17:09.640> addition<00:17:09.959> to<00:17:10.559> the<00:17:10.720> name<00:17:10.880> of<00:17:11.000> the<00:17:11.160> project 00:17:11.429 --> 00:17:11.439 align:start position:0% in addition to the name of the project 00:17:11.439 --> 00:17:14.029 align:start position:0% in addition to the name of the project needs<00:17:11.839> a<00:17:12.000> version<00:17:12.360> we<00:17:12.480> only<00:17:12.799> Supply<00:17:13.799> the<00:17:13.919> name 00:17:14.029 --> 00:17:14.039 align:start position:0% needs a version we only Supply the name 00:17:14.039 --> 00:17:16.630 align:start position:0% needs a version we only Supply the name of<00:17:14.160> the<00:17:14.559> project<00:17:15.559> so<00:17:15.839> V<00:17:16.079> is<00:17:16.160> going<00:17:16.280> to<00:17:16.400> provide 00:17:16.630 --> 00:17:16.640 align:start position:0% of the project so V is going to provide 00:17:16.640 --> 00:17:19.309 align:start position:0% of the project so V is going to provide the<00:17:16.839> version<00:17:17.760> long<00:17:18.079> option 00:17:19.309 --> 00:17:19.319 align:start position:0% the version long option 00:17:19.319 --> 00:17:21.350 align:start position:0% the version long option 0.1<00:17:20.319> or<00:17:20.480> who<00:17:20.600> knows<00:17:20.799> maybe<00:17:20.919> we're<00:17:21.039> ready<00:17:21.199> for 00:17:21.350 --> 00:17:21.360 align:start position:0% 0.1 or who knows maybe we're ready for 00:17:21.360 --> 00:17:26.710 align:start position:0% 0.1 or who knows maybe we're ready for 1.0<00:17:21.959> we<00:17:22.120> type<00:17:22.280> it 00:17:26.710 --> 00:17:26.720 align:start position:0% 00:17:26.720 --> 00:17:29.430 align:start position:0% in<00:17:27.720> okay<00:17:27.919> then<00:17:28.039> we<00:17:28.120> do<00:17:28.319> jar 00:17:29.430 --> 00:17:29.440 align:start position:0% in okay then we do jar 00:17:29.440 --> 00:17:30.830 align:start position:0% in okay then we do jar let<00:17:29.559> me 00:17:30.830 --> 00:17:30.840 align:start position:0% let me 00:17:30.840 --> 00:17:33.590 align:start position:0% let me install<00:17:31.840> could<00:17:32.080> probably<00:17:32.280> just<00:17:32.520> type 00:17:33.590 --> 00:17:33.600 align:start position:0% install could probably just type 00:17:33.600 --> 00:17:36.029 align:start position:0% install could probably just type that<00:17:34.600> okay<00:17:34.799> don't<00:17:35.000> worry<00:17:35.280> about<00:17:35.559> that<00:17:35.919> that 00:17:36.029 --> 00:17:36.039 align:start position:0% that okay don't worry about that that 00:17:36.039 --> 00:17:38.110 align:start position:0% that okay don't worry about that that warning<00:17:36.400> is<00:17:36.559> totally<00:17:37.000> cool<00:17:37.440> totally<00:17:37.799> normal 00:17:38.110 --> 00:17:38.120 align:start position:0% warning is totally cool totally normal 00:17:38.120 --> 00:17:39.430 align:start position:0% warning is totally cool totally normal it's<00:17:38.280> going<00:17:38.360> to<00:17:38.520> work<00:17:38.799> it's<00:17:38.960> going<00:17:39.039> to<00:17:39.160> work<00:17:39.320> I 00:17:39.430 --> 00:17:39.440 align:start position:0% it's going to work it's going to work I 00:17:39.440 --> 00:17:43.270 align:start position:0% it's going to work it's going to work I know<00:17:39.799> watch<00:17:40.919> watch<00:17:41.919> see<00:17:42.760> told<00:17:43.000> you<00:17:43.120> it's<00:17:43.200> going 00:17:43.270 --> 00:17:43.280 align:start position:0% know watch watch see told you it's going 00:17:43.280 --> 00:17:44.180 align:start position:0% know watch watch see told you it's going to 00:17:44.180 --> 00:17:44.190 align:start position:0% to 00:17:44.190 --> 00:17:46.909 align:start position:0% to [Applause] 00:17:46.909 --> 00:17:46.919 align:start position:0% [Applause] 00:17:46.919 --> 00:17:48.990 align:start position:0% [Applause] work<00:17:47.919> got<00:17:48.039> a<00:17:48.160> warning<00:17:48.440> it's<00:17:48.600> going<00:17:48.679> to<00:17:48.799> be 00:17:48.990 --> 00:17:49.000 align:start position:0% work got a warning it's going to be 00:17:49.000 --> 00:17:52.110 align:start position:0% work got a warning it's going to be awesome 00:17:52.110 --> 00:17:52.120 align:start position:0% 00:17:52.120 --> 00:17:55.909 align:start position:0% warning<00:17:53.280> so<00:17:54.280> now<00:17:54.440> we've<00:17:54.600> created<00:17:55.240> our<00:17:55.400> own<00:17:55.600> new 00:17:55.909 --> 00:17:55.919 align:start position:0% warning so now we've created our own new 00:17:55.919 --> 00:17:57.070 align:start position:0% warning so now we've created our own new name<00:17:56.120> task<00:17:56.400> it<00:17:56.480> doesn't<00:17:56.720> actually<00:17:56.919> do 00:17:57.070 --> 00:17:57.080 align:start position:0% name task it doesn't actually do 00:17:57.080 --> 00:17:59.070 align:start position:0% name task it doesn't actually do anything<00:17:57.320> new<00:17:57.559> it<00:17:57.840> just<00:17:58.039> composes<00:17:58.480> existing 00:17:59.070 --> 00:17:59.080 align:start position:0% anything new it just composes existing 00:17:59.080 --> 00:18:00.669 align:start position:0% anything new it just composes existing things<00:17:59.600> but<00:17:59.720> for<00:17:59.840> a<00:17:59.919> lot<00:18:00.039> of<00:18:00.159> projects<00:18:00.520> that's 00:18:00.669 --> 00:18:00.679 align:start position:0% things but for a lot of projects that's 00:18:00.679 --> 00:18:03.190 align:start position:0% things but for a lot of projects that's exactly<00:18:01.080> and<00:18:01.240> only<00:18:01.440> what<00:18:01.520> you<00:18:01.600> need<00:18:01.760> to<00:18:02.039> do<00:18:03.039> a 00:18:03.190 --> 00:18:03.200 align:start position:0% exactly and only what you need to do a 00:18:03.200 --> 00:18:04.990 align:start position:0% exactly and only what you need to do a cool<00:18:03.440> thing<00:18:03.720> is<00:18:03.880> that<00:18:04.080> this<00:18:04.280> new<00:18:04.559> task<00:18:04.840> we 00:18:04.990 --> 00:18:05.000 align:start position:0% cool thing is that this new task we 00:18:05.000 --> 00:18:06.870 align:start position:0% cool thing is that this new task we created<00:18:05.360> is<00:18:05.520> first<00:18:05.799> class<00:18:06.120> in<00:18:06.200> the<00:18:06.320> sense<00:18:06.600> that 00:18:06.870 --> 00:18:06.880 align:start position:0% created is first class in the sense that 00:18:06.880 --> 00:18:08.470 align:start position:0% created is first class in the sense that you<00:18:06.960> can<00:18:07.120> call<00:18:07.320> it<00:18:07.520> compose<00:18:07.840> it<00:18:08.080> just<00:18:08.200> like<00:18:08.360> any 00:18:08.470 --> 00:18:08.480 align:start position:0% you can call it compose it just like any 00:18:08.480 --> 00:18:10.789 align:start position:0% you can call it compose it just like any of<00:18:08.559> the<00:18:08.679> built-in<00:18:09.080> tasks<00:18:10.080> here<00:18:10.320> Misha<00:18:10.679> has 00:18:10.789 --> 00:18:10.799 align:start position:0% of the built-in tasks here Misha has 00:18:10.799 --> 00:18:12.789 align:start position:0% of the built-in tasks here Misha has composed<00:18:11.200> it<00:18:11.400> with<00:18:11.640> the<00:18:11.799> watch<00:18:12.080> task<00:18:12.480> which<00:18:12.559> is 00:18:12.789 --> 00:18:12.799 align:start position:0% composed it with the watch task which is 00:18:12.799 --> 00:18:14.190 align:start position:0% composed it with the watch task which is one<00:18:12.919> of<00:18:13.039> the<00:18:13.120> built-in<00:18:13.480> tasks<00:18:13.720> of<00:18:13.880> boot<00:18:14.120> that 00:18:14.190 --> 00:18:14.200 align:start position:0% one of the built-in tasks of boot that 00:18:14.200 --> 00:18:16.230 align:start position:0% one of the built-in tasks of boot that is<00:18:14.320> composable<00:18:14.720> with<00:18:14.880> a<00:18:15.320> task<00:18:15.799> it's<00:18:15.960> not 00:18:16.230 --> 00:18:16.240 align:start position:0% is composable with a task it's not 00:18:16.240 --> 00:18:18.710 align:start position:0% is composable with a task it's not particularly<00:18:16.919> special<00:18:17.919> the<00:18:18.080> watch<00:18:18.320> task 00:18:18.710 --> 00:18:18.720 align:start position:0% particularly special the watch task 00:18:18.720 --> 00:18:21.110 align:start position:0% particularly special the watch task leverages<00:18:19.240> the<00:18:19.440> fact<00:18:19.799> that<00:18:20.120> like<00:18:20.760> any 00:18:21.110 --> 00:18:21.120 align:start position:0% leverages the fact that like any 00:18:21.120 --> 00:18:22.830 align:start position:0% leverages the fact that like any function<00:18:21.880> that<00:18:22.000> follows<00:18:22.240> this<00:18:22.360> middleware 00:18:22.830 --> 00:18:22.840 align:start position:0% function that follows this middleware 00:18:22.840 --> 00:18:24.830 align:start position:0% function that follows this middleware pattern<00:18:23.120> we<00:18:23.240> showed<00:18:23.960> inside<00:18:24.240> the<00:18:24.360> innermost 00:18:24.830 --> 00:18:24.840 align:start position:0% pattern we showed inside the innermost 00:18:24.840 --> 00:18:26.390 align:start position:0% pattern we showed inside the innermost function<00:18:25.240> which<00:18:25.360> is<00:18:25.559> the<00:18:25.760> piece<00:18:25.919> of<00:18:26.039> code<00:18:26.280> that 00:18:26.390 --> 00:18:26.400 align:start position:0% function which is the piece of code that 00:18:26.400 --> 00:18:28.789 align:start position:0% function which is the piece of code that actually<00:18:26.679> does<00:18:26.960> the<00:18:27.120> logic<00:18:28.039> Tas<00:18:28.360> has<00:18:28.480> the 00:18:28.789 --> 00:18:28.799 align:start position:0% actually does the logic Tas has the 00:18:28.799 --> 00:18:31.350 align:start position:0% actually does the logic Tas has the opportunity<00:18:29.320> not<00:18:29.720> to<00:18:29.919> call<00:18:30.559> the<00:18:30.679> next<00:18:30.919> pass<00:18:31.200> or 00:18:31.350 --> 00:18:31.360 align:start position:0% opportunity not to call the next pass or 00:18:31.360 --> 00:18:33.870 align:start position:0% opportunity not to call the next pass or to<00:18:31.520> call<00:18:31.679> it<00:18:31.840> multiple<00:18:32.400> times<00:18:33.400> what<00:18:33.520> the<00:18:33.640> watch 00:18:33.870 --> 00:18:33.880 align:start position:0% to call it multiple times what the watch 00:18:33.880 --> 00:18:35.590 align:start position:0% to call it multiple times what the watch pass<00:18:34.159> does<00:18:34.360> is<00:18:34.480> it<00:18:34.640> has<00:18:34.720> a<00:18:34.880> handle<00:18:35.240> to<00:18:35.440> that 00:18:35.590 --> 00:18:35.600 align:start position:0% pass does is it has a handle to that 00:18:35.600 --> 00:18:38.590 align:start position:0% pass does is it has a handle to that next<00:18:36.080> Handler<00:18:37.080> and<00:18:37.600> uh<00:18:37.760> it<00:18:37.960> is<00:18:38.120> monitoring<00:18:38.520> The 00:18:38.590 --> 00:18:38.600 align:start position:0% next Handler and uh it is monitoring The 00:18:38.600 --> 00:18:39.710 align:start position:0% next Handler and uh it is monitoring The Source<00:18:38.880> directories<00:18:39.240> and<00:18:39.360> when<00:18:39.440> the<00:18:39.520> source 00:18:39.710 --> 00:18:39.720 align:start position:0% Source directories and when the source 00:18:39.720 --> 00:18:41.510 align:start position:0% Source directories and when the source directories<00:18:40.159> change<00:18:40.600> it<00:18:40.760> calls<00:18:41.000> that 00:18:41.510 --> 00:18:41.520 align:start position:0% directories change it calls that 00:18:41.520 --> 00:18:43.830 align:start position:0% directories change it calls that function<00:18:42.520> um<00:18:42.640> so<00:18:42.840> because<00:18:43.080> f<00:18:43.280> are<00:18:43.440> functions 00:18:43.830 --> 00:18:43.840 align:start position:0% function um so because f are functions 00:18:43.840 --> 00:18:44.950 align:start position:0% function um so because f are functions that's 00:18:44.950 --> 00:18:44.960 align:start position:0% that's 00:18:44.960 --> 00:18:48.630 align:start position:0% that's totally<00:18:45.960> it's<00:18:46.120> even<00:18:46.320> fun<00:18:46.559> to<00:18:46.760> do<00:18:47.480> honestly<00:18:48.480> so 00:18:48.630 --> 00:18:48.640 align:start position:0% totally it's even fun to do honestly so 00:18:48.640 --> 00:18:49.909 align:start position:0% totally it's even fun to do honestly so now<00:18:48.760> we've<00:18:48.919> been<00:18:49.039> doing<00:18:49.200> a<00:18:49.280> lot<00:18:49.400> of<00:18:49.520> typing<00:18:49.799> in 00:18:49.909 --> 00:18:49.919 align:start position:0% now we've been doing a lot of typing in 00:18:49.919 --> 00:18:51.590 align:start position:0% now we've been doing a lot of typing in the<00:18:50.039> repple<00:18:50.480> on<00:18:50.600> the<00:18:50.720> command<00:18:51.000> line<00:18:51.200> and<00:18:51.400> stuff 00:18:51.590 --> 00:18:51.600 align:start position:0% the repple on the command line and stuff 00:18:51.600 --> 00:18:54.149 align:start position:0% the repple on the command line and stuff like<00:18:51.799> that<00:18:52.240> but<00:18:52.360> the<00:18:52.480> more<00:18:52.760> stute<00:18:53.080> abuse<00:18:53.840> will 00:18:54.149 --> 00:18:54.159 align:start position:0% like that but the more stute abuse will 00:18:54.159 --> 00:18:56.630 align:start position:0% like that but the more stute abuse will say<00:18:55.159> ah<00:18:55.559> what<00:18:55.679> if<00:18:55.799> you<00:18:55.919> could<00:18:56.039> put<00:18:56.200> that<00:18:56.320> in<00:18:56.440> a 00:18:56.630 --> 00:18:56.640 align:start position:0% say ah what if you could put that in a 00:18:56.640 --> 00:18:59.549 align:start position:0% say ah what if you could put that in a file<00:18:57.200> then<00:18:57.320> you'd<00:18:57.559> really<00:18:57.760> beet 00:18:59.549 --> 00:18:59.559 align:start position:0% file then you'd really beet 00:18:59.559 --> 00:19:01.390 align:start position:0% file then you'd really beet and<00:18:59.720> it<00:18:59.880> turns<00:19:00.200> out<00:19:00.559> that<00:19:00.799> yes<00:19:00.960> it's<00:19:01.120> occurred 00:19:01.390 --> 00:19:01.400 align:start position:0% and it turns out that yes it's occurred 00:19:01.400 --> 00:19:04.390 align:start position:0% and it turns out that yes it's occurred to<00:19:01.520> us<00:19:01.799> too<00:19:02.799> uh<00:19:03.559> the<00:19:03.720> first<00:19:03.919> thing<00:19:04.080> you<00:19:04.240> might 00:19:04.390 --> 00:19:04.400 align:start position:0% to us too uh the first thing you might 00:19:04.400 --> 00:19:05.870 align:start position:0% to us too uh the first thing you might want<00:19:04.480> to<00:19:04.919> the<00:19:05.000> original<00:19:05.280> idea<00:19:05.480> was<00:19:05.559> we<00:19:05.760> just 00:19:05.870 --> 00:19:05.880 align:start position:0% want to the original idea was we just 00:19:05.880 --> 00:19:08.270 align:start position:0% want to the original idea was we just take<00:19:05.960> a<00:19:06.039> screenshot<00:19:06.480> of<00:19:06.559> the<00:19:06.960> rep<00:19:07.960> check<00:19:08.159> that 00:19:08.270 --> 00:19:08.280 align:start position:0% take a screenshot of the rep check that 00:19:08.280 --> 00:19:10.110 align:start position:0% take a screenshot of the rep check that in<00:19:08.400> the<00:19:08.520> CVS<00:19:09.039> I<00:19:09.120> keep<00:19:09.280> telling<00:19:09.520> you<00:19:09.679> it<00:19:09.799> doesn't 00:19:10.110 --> 00:19:10.120 align:start position:0% in the CVS I keep telling you it doesn't 00:19:10.120 --> 00:19:11.990 align:start position:0% in the CVS I keep telling you it doesn't work<00:19:10.480> that<00:19:10.679> way<00:19:11.200> I<00:19:11.280> mean<00:19:11.440> look<00:19:11.559> at<00:19:11.679> this<00:19:11.880> like 00:19:11.990 --> 00:19:12.000 align:start position:0% work that way I mean look at this like 00:19:12.000 --> 00:19:13.669 align:start position:0% work that way I mean look at this like we<00:19:12.159> have<00:19:12.320> a<00:19:12.440> screenshot<00:19:13.039> here<00:19:13.360> which<00:19:13.480> is 00:19:13.669 --> 00:19:13.679 align:start position:0% we have a screenshot here which is 00:19:13.679 --> 00:19:14.870 align:start position:0% we have a screenshot here which is pretty<00:19:13.840> sweet 00:19:14.870 --> 00:19:14.880 align:start position:0% pretty sweet 00:19:14.880 --> 00:19:17.070 align:start position:0% pretty sweet beautiful<00:19:15.880> that's<00:19:16.000> not<00:19:16.159> how<00:19:16.280> you<00:19:16.360> do<00:19:16.520> it<00:19:16.720> all 00:19:17.070 --> 00:19:17.080 align:start position:0% beautiful that's not how you do it all 00:19:17.080 --> 00:19:19.710 align:start position:0% beautiful that's not how you do it all right<00:19:18.080> uh<00:19:18.240> so<00:19:18.440> you<00:19:18.600> can<00:19:18.880> boot<00:19:19.159> does<00:19:19.400> actually 00:19:19.710 --> 00:19:19.720 align:start position:0% right uh so you can boot does actually 00:19:19.720 --> 00:19:22.110 align:start position:0% right uh so you can boot does actually support<00:19:20.440> just<00:19:20.640> making<00:19:21.280> you<00:19:21.360> know<00:19:21.520> an<00:19:21.679> ad<00:19:21.919> hoc 00:19:22.110 --> 00:19:22.120 align:start position:0% support just making you know an ad hoc 00:19:22.120 --> 00:19:24.430 align:start position:0% support just making you know an ad hoc script<00:19:22.559> with<00:19:22.799> closure<00:19:23.159> in<00:19:23.280> it<00:19:23.919> and<00:19:24.080> you<00:19:24.200> have 00:19:24.430 --> 00:19:24.440 align:start position:0% script with closure in it and you have 00:19:24.440 --> 00:19:26.390 align:start position:0% script with closure in it and you have access<00:19:24.679> to<00:19:24.840> all<00:19:25.039> the<00:19:25.200> boot<00:19:25.919> the<00:19:26.080> the<00:19:26.159> boot 00:19:26.390 --> 00:19:26.400 align:start position:0% access to all the boot the the boot 00:19:26.400 --> 00:19:27.750 align:start position:0% access to all the boot the the boot Library<00:19:26.799> stuff<00:19:27.039> so<00:19:27.120> you<00:19:27.200> can<00:19:27.320> actually<00:19:27.520> make<00:19:27.640> a 00:19:27.750 --> 00:19:27.760 align:start position:0% Library stuff so you can actually make a 00:19:27.760 --> 00:19:30.390 align:start position:0% Library stuff so you can actually make a build<00:19:28.000> like<00:19:28.159> this<00:19:28.720> bang<00:19:28.960> at<00:19:29.039> the<00:19:29.240> top<00:19:30.080> um<00:19:30.200> make 00:19:30.390 --> 00:19:30.400 align:start position:0% build like this bang at the top um make 00:19:30.400 --> 00:19:32.070 align:start position:0% build like this bang at the top um make the<00:19:30.559> file<00:19:30.880> executable<00:19:31.440> you<00:19:31.559> have<00:19:31.679> a<00:19:31.799> main 00:19:32.070 --> 00:19:32.080 align:start position:0% the file executable you have a main 00:19:32.080 --> 00:19:33.750 align:start position:0% the file executable you have a main method<00:19:32.440> down<00:19:32.640> there<00:19:33.080> that<00:19:33.200> can<00:19:33.360> take 00:19:33.750 --> 00:19:33.760 align:start position:0% method down there that can take 00:19:33.760 --> 00:19:35.950 align:start position:0% method down there that can take arguments<00:19:34.760> and<00:19:35.000> you<00:19:35.120> can<00:19:35.360> you<00:19:35.440> can<00:19:35.559> build<00:19:35.799> your 00:19:35.950 --> 00:19:35.960 align:start position:0% arguments and you can you can build your 00:19:35.960 --> 00:19:38.190 align:start position:0% arguments and you can you can build your project<00:19:36.240> like<00:19:36.360> this<00:19:36.480> it'll<00:19:36.720> totally<00:19:37.080> work<00:19:38.080> uh 00:19:38.190 --> 00:19:38.200 align:start position:0% project like this it'll totally work uh 00:19:38.200 --> 00:19:39.549 align:start position:0% project like this it'll totally work uh but<00:19:38.360> what<00:19:38.480> you<00:19:38.720> give<00:19:38.880> up<00:19:39.080> here<00:19:39.240> is<00:19:39.360> that<00:19:39.480> you 00:19:39.549 --> 00:19:39.559 align:start position:0% but what you give up here is that you 00:19:39.559 --> 00:19:41.070 align:start position:0% but what you give up here is that you have<00:19:39.640> to<00:19:39.840> process<00:19:40.159> the<00:19:40.280> arguments<00:19:40.760> yourself 00:19:41.070 --> 00:19:41.080 align:start position:0% have to process the arguments yourself 00:19:41.080 --> 00:19:43.350 align:start position:0% have to process the arguments yourself you<00:19:41.240> can't<00:19:41.440> be<00:19:41.640> composing<00:19:42.600> different<00:19:42.960> tasks 00:19:43.350 --> 00:19:43.360 align:start position:0% you can't be composing different tasks 00:19:43.360 --> 00:19:45.750 align:start position:0% you can't be composing different tasks on<00:19:43.480> the<00:19:43.640> command<00:19:43.960> line<00:19:44.159> like<00:19:44.360> this<00:19:45.280> um<00:19:45.480> if<00:19:45.600> you 00:19:45.750 --> 00:19:45.760 align:start position:0% on the command line like this um if you 00:19:45.760 --> 00:19:47.110 align:start position:0% on the command line like this um if you if<00:19:45.880> you<00:19:46.000> have<00:19:46.159> just<00:19:46.280> an<00:19:46.480> executable<00:19:47.000> where 00:19:47.110 --> 00:19:47.120 align:start position:0% if you have just an executable where 00:19:47.120 --> 00:19:48.630 align:start position:0% if you have just an executable where you're<00:19:47.280> handling<00:19:47.720> the<00:19:48.159> the<00:19:48.280> things<00:19:48.400> in<00:19:48.559> the 00:19:48.630 --> 00:19:48.640 align:start position:0% you're handling the the things in the 00:19:48.640 --> 00:19:53.270 align:start position:0% you're handling the the things in the main<00:19:48.880> method<00:19:49.280> so<00:19:50.280> um<00:19:50.480> boot<00:19:50.880> does<00:19:51.799> uh<00:19:52.799> boot<00:19:53.039> will 00:19:53.270 --> 00:19:53.280 align:start position:0% main method so um boot does uh boot will 00:19:53.280 --> 00:19:55.789 align:start position:0% main method so um boot does uh boot will will<00:19:53.440> look<00:19:53.559> for<00:19:53.720> a<00:19:53.840> file<00:19:54.080> called<00:19:54.240> build.<00:19:54.799> boot 00:19:55.789 --> 00:19:55.799 align:start position:0% will look for a file called build. boot 00:19:55.799 --> 00:19:57.789 align:start position:0% will look for a file called build. boot in<00:19:55.919> the<00:19:56.080> project<00:19:56.400> directory<00:19:57.200> and<00:19:57.480> it'll 00:19:57.789 --> 00:19:57.799 align:start position:0% in the project directory and it'll 00:19:57.799 --> 00:19:59.350 align:start position:0% in the project directory and it'll evaluate<00:19:58.200> the<00:19:58.280> code<00:19:58.480> in<00:19:58.799> there<00:19:59.000> and<00:19:59.159> then 00:19:59.350 --> 00:19:59.360 align:start position:0% evaluate the code in there and then 00:19:59.360 --> 00:20:01.270 align:start position:0% evaluate the code in there and then it'll<00:19:59.600> take<00:19:59.760> your<00:19:59.880> command<00:20:00.200> line<00:20:00.440> options<00:20:01.120> and 00:20:01.270 --> 00:20:01.280 align:start position:0% it'll take your command line options and 00:20:01.280 --> 00:20:02.669 align:start position:0% it'll take your command line options and build<00:20:01.440> a<00:20:01.600> pipeline<00:20:01.960> out<00:20:02.080> of<00:20:02.200> them<00:20:02.360> so<00:20:02.480> in<00:20:02.559> other 00:20:02.669 --> 00:20:02.679 align:start position:0% build a pipeline out of them so in other 00:20:02.679 --> 00:20:04.710 align:start position:0% build a pipeline out of them so in other words<00:20:02.880> it<00:20:02.960> generates<00:20:03.400> the<00:20:03.559> main<00:20:03.880> method<00:20:04.280> for 00:20:04.710 --> 00:20:04.720 align:start position:0% words it generates the main method for 00:20:04.720 --> 00:20:07.590 align:start position:0% words it generates the main method for you<00:20:05.720> uh<00:20:06.240> at<00:20:06.400> run<00:20:06.679> time<00:20:06.960> when<00:20:07.120> you<00:20:07.360> when<00:20:07.480> you 00:20:07.590 --> 00:20:07.600 align:start position:0% you uh at run time when you when you 00:20:07.600 --> 00:20:09.630 align:start position:0% you uh at run time when you when you call<00:20:07.840> it<00:20:08.679> and<00:20:08.799> so<00:20:08.919> you<00:20:09.039> can<00:20:09.159> use<00:20:09.320> this<00:20:09.440> to 00:20:09.630 --> 00:20:09.640 align:start position:0% call it and so you can use this to 00:20:09.640 --> 00:20:10.990 align:start position:0% call it and so you can use this to Define<00:20:10.000> tasks<00:20:10.320> and<00:20:10.440> things<00:20:10.640> like<00:20:10.760> that<00:20:10.880> in 00:20:10.990 --> 00:20:11.000 align:start position:0% Define tasks and things like that in 00:20:11.000 --> 00:20:12.830 align:start position:0% Define tasks and things like that in your<00:20:11.120> build.<00:20:11.520> boot<00:20:11.760> which<00:20:11.840> you<00:20:11.919> can<00:20:12.080> then 00:20:12.830 --> 00:20:12.840 align:start position:0% your build. boot which you can then 00:20:12.840 --> 00:20:15.630 align:start position:0% your build. boot which you can then use<00:20:13.840> from<00:20:14.039> the<00:20:14.159> command 00:20:15.630 --> 00:20:15.640 align:start position:0% use from the command 00:20:15.640 --> 00:20:18.430 align:start position:0% use from the command line<00:20:16.640> so<00:20:16.799> we<00:20:16.919> want<00:20:17.039> to<00:20:17.120> show<00:20:17.320> that<00:20:17.520> yeah 00:20:18.430 --> 00:20:18.440 align:start position:0% line so we want to show that yeah 00:20:18.440 --> 00:20:20.990 align:start position:0% line so we want to show that yeah yes<00:20:19.440> so<00:20:19.600> the<00:20:19.679> first<00:20:19.880> cool<00:20:20.159> thing<00:20:20.440> now<00:20:20.559> that<00:20:20.760> our 00:20:20.990 --> 00:20:21.000 align:start position:0% yes so the first cool thing now that our 00:20:21.000 --> 00:20:23.110 align:start position:0% yes so the first cool thing now that our task<00:20:21.280> is<00:20:21.360> in<00:20:21.480> a<00:20:21.640> file<00:20:21.919> and<00:20:22.039> it<00:20:22.280> has<00:20:22.799> is<00:20:22.880> in<00:20:23.000> a 00:20:23.110 --> 00:20:23.120 align:start position:0% task is in a file and it has is in a 00:20:23.120 --> 00:20:25.110 align:start position:0% task is in a file and it has is in a build.<00:20:23.559> boot<00:20:23.799> which<00:20:23.880> is<00:20:24.000> this<00:20:24.200> extension<00:20:24.640> that 00:20:25.110 --> 00:20:25.120 align:start position:0% build. boot which is this extension that 00:20:25.120 --> 00:20:27.870 align:start position:0% build. boot which is this extension that boot<00:20:25.360> semi<00:20:25.720> magically<00:20:26.039> knows<00:20:26.679> about<00:20:27.679> we<00:20:27.799> can 00:20:27.870 --> 00:20:27.880 align:start position:0% boot semi magically knows about we can 00:20:27.880 --> 00:20:29.710 align:start position:0% boot semi magically knows about we can do<00:20:28.039> boot<00:20:28.280> d8 00:20:29.710 --> 00:20:29.720 align:start position:0% do boot d8 00:20:29.720 --> 00:20:32.070 align:start position:0% do boot d8 and<00:20:30.320> the<00:20:30.440> task<00:20:30.720> that<00:20:30.840> we<00:20:30.960> created<00:20:31.320> will<00:20:31.480> show 00:20:32.070 --> 00:20:32.080 align:start position:0% and the task that we created will show 00:20:32.080 --> 00:20:33.510 align:start position:0% and the task that we created will show up<00:20:32.320> right<00:20:32.480> alongside<00:20:32.919> all<00:20:33.000> the<00:20:33.120> built-in 00:20:33.510 --> 00:20:33.520 align:start position:0% up right alongside all the built-in 00:20:33.520 --> 00:20:36.830 align:start position:0% up right alongside all the built-in tasks<00:20:33.919> with<00:20:34.039> a<00:20:34.200> documentation<00:20:34.799> string<00:20:35.799> a<00:20:35.960> PO 00:20:36.830 --> 00:20:36.840 align:start position:0% tasks with a documentation string a PO 00:20:36.840 --> 00:20:38.830 align:start position:0% tasks with a documentation string a PO documentation<00:20:37.840> but 00:20:38.830 --> 00:20:38.840 align:start position:0% documentation but 00:20:38.840 --> 00:20:40.870 align:start position:0% documentation but exist<00:20:39.840> and<00:20:39.960> you'll<00:20:40.120> notice<00:20:40.360> there's<00:20:40.480> an<00:20:40.600> ex 00:20:40.870 --> 00:20:40.880 align:start position:0% exist and you'll notice there's an ex 00:20:40.880 --> 00:20:42.110 align:start position:0% exist and you'll notice there's an ex extra<00:20:41.120> new<00:20:41.280> line<00:20:41.480> there<00:20:41.640> between<00:20:41.840> the<00:20:41.919> built 00:20:42.110 --> 00:20:42.120 align:start position:0% extra new line there between the built 00:20:42.120 --> 00:20:43.950 align:start position:0% extra new line there between the built on<00:20:42.280> ones<00:20:42.480> and<00:20:42.640> the<00:20:42.720> ones<00:20:42.880> in<00:20:43.000> your<00:20:43.200> project<00:20:43.640> so 00:20:43.950 --> 00:20:43.960 align:start position:0% on ones and the ones in your project so 00:20:43.960 --> 00:20:45.190 align:start position:0% on ones and the ones in your project so typically<00:20:44.320> you<00:20:44.440> know<00:20:44.559> we'll<00:20:44.799> create<00:20:45.039> these 00:20:45.190 --> 00:20:45.200 align:start position:0% typically you know we'll create these 00:20:45.200 --> 00:20:48.149 align:start position:0% typically you know we'll create these build<00:20:45.960> uh<00:20:46.080> files<00:20:46.400> for<00:20:46.559> a<00:20:46.720> project<00:20:46.960> of<00:20:47.080> ours<00:20:48.000> and 00:20:48.149 --> 00:20:48.159 align:start position:0% build uh files for a project of ours and 00:20:48.159 --> 00:20:49.990 align:start position:0% build uh files for a project of ours and they're<00:20:48.559> self-documented<00:20:49.440> to<00:20:49.600> the<00:20:49.760> extent 00:20:49.990 --> 00:20:50.000 align:start position:0% they're self-documented to the extent 00:20:50.000 --> 00:20:51.789 align:start position:0% they're self-documented to the extent that<00:20:50.120> at<00:20:50.200> least<00:20:50.320> the<00:20:50.400> user<00:20:50.640> who<00:20:50.799> types<00:20:51.000> bo-<00:20:51.679> is 00:20:51.789 --> 00:20:51.799 align:start position:0% that at least the user who types bo- is 00:20:51.799 --> 00:20:53.190 align:start position:0% that at least the user who types bo- is able<00:20:51.960> to<00:20:52.240> discover<00:20:52.440> the<00:20:52.559> pass<00:20:52.799> available 00:20:53.190 --> 00:20:53.200 align:start position:0% able to discover the pass available 00:20:53.200 --> 00:20:55.149 align:start position:0% able to discover the pass available that's<00:20:53.320> a<00:20:53.400> lot<00:20:53.559> like<00:20:53.640> you<00:20:53.720> know<00:20:54.360> or<00:20:54.559> ant<00:20:54.799> show 00:20:55.149 --> 00:20:55.159 align:start position:0% that's a lot like you know or ant show 00:20:55.159 --> 00:20:57.230 align:start position:0% that's a lot like you know or ant show or 00:20:57.230 --> 00:20:57.240 align:start position:0% or 00:20:57.240 --> 00:21:00.390 align:start position:0% or whatever<00:20:58.240> um 00:21:00.390 --> 00:21:00.400 align:start position:0% whatever um 00:21:00.400 --> 00:21:02.549 align:start position:0% whatever um yes<00:21:01.400> here<00:21:01.559> we 00:21:02.549 --> 00:21:02.559 align:start position:0% yes here we 00:21:02.559 --> 00:21:06.190 align:start position:0% yes here we go<00:21:03.559> and<00:21:03.840> that's<00:21:04.000> the<00:21:04.200> go<00:21:04.960> so<00:21:05.559> the<00:21:05.679> same<00:21:05.919> way<00:21:06.120> we 00:21:06.190 --> 00:21:06.200 align:start position:0% go and that's the go so the same way we 00:21:06.200 --> 00:21:07.789 align:start position:0% go and that's the go so the same way we can<00:21:06.320> use<00:21:06.600> watch<00:21:06.760> at<00:21:06.880> the<00:21:07.000> reel<00:21:07.360> to<00:21:07.520> compose 00:21:07.789 --> 00:21:07.799 align:start position:0% can use watch at the reel to compose 00:21:07.799 --> 00:21:09.270 align:start position:0% can use watch at the reel to compose with<00:21:07.960> this<00:21:08.120> thing<00:21:08.400> at<00:21:08.520> the<00:21:08.600> command<00:21:08.919> line<00:21:09.159> it 00:21:09.270 --> 00:21:09.280 align:start position:0% with this thing at the command line it 00:21:09.280 --> 00:21:12.269 align:start position:0% with this thing at the command line it also<00:21:09.480> composes<00:21:09.960> with<00:21:10.240> you<00:21:10.360> know<00:21:10.600> watch<00:21:11.279> so 00:21:12.269 --> 00:21:12.279 align:start position:0% also composes with you know watch so 00:21:12.279 --> 00:21:14.110 align:start position:0% also composes with you know watch so doing<00:21:12.559> all<00:21:12.679> the<00:21:12.840> same<00:21:13.159> stuff<00:21:13.640> we've<00:21:13.960> just 00:21:14.110 --> 00:21:14.120 align:start position:0% doing all the same stuff we've just 00:21:14.120 --> 00:21:15.549 align:start position:0% doing all the same stuff we've just slightly<00:21:14.559> changed<00:21:14.919> the<00:21:15.039> format<00:21:15.360> that<00:21:15.440> we're 00:21:15.549 --> 00:21:15.559 align:start position:0% slightly changed the format that we're 00:21:15.559 --> 00:21:17.590 align:start position:0% slightly changed the format that we're storing<00:21:16.240> the<00:21:16.400> build<00:21:16.720> programming<00:21:17.159> and<00:21:17.480> a 00:21:17.590 --> 00:21:17.600 align:start position:0% storing the build programming and a 00:21:17.600 --> 00:21:19.070 align:start position:0% storing the build programming and a build<00:21:17.840> up<00:21:18.000> we 00:21:19.070 --> 00:21:19.080 align:start position:0% build up we 00:21:19.080 --> 00:21:21.789 align:start position:0% build up we F<00:21:20.080> so<00:21:20.440> again<00:21:20.640> we<00:21:20.720> can<00:21:20.840> you<00:21:20.919> know<00:21:21.120> make<00:21:21.480> full 00:21:21.789 --> 00:21:21.799 align:start position:0% F so again we can you know make full 00:21:21.799 --> 00:21:24.190 align:start position:0% F so again we can you know make full pipelines<00:21:22.320> that<00:21:22.440> show<00:21:22.679> the 00:21:24.190 --> 00:21:24.200 align:start position:0% pipelines that show the 00:21:24.200 --> 00:21:27.510 align:start position:0% pipelines that show the things<00:21:25.200> and<00:21:25.640> uh<00:21:25.960> it's<00:21:26.200> pretty 00:21:27.510 --> 00:21:27.520 align:start position:0% things and uh it's pretty 00:21:27.520 --> 00:21:30.870 align:start position:0% things and uh it's pretty sweet<00:21:28.559> let<00:21:28.679> make<00:21:28.799> a<00:21:28.880> new<00:21:29.080> task<00:21:29.600> guys<00:21:30.600> so<00:21:30.760> at 00:21:30.870 --> 00:21:30.880 align:start position:0% sweet let make a new task guys so at 00:21:30.880 --> 00:21:33.230 align:start position:0% sweet let make a new task guys so at this<00:21:31.039> point<00:21:31.240> we've<00:21:31.440> only<00:21:31.760> composed<00:21:32.679> new<00:21:33.080> uh 00:21:33.230 --> 00:21:33.240 align:start position:0% this point we've only composed new uh 00:21:33.240 --> 00:21:35.149 align:start position:0% this point we've only composed new uh existing<00:21:33.640> things<00:21:33.919> and<00:21:34.080> given<00:21:34.240> a<00:21:34.360> name<00:21:34.559> to<00:21:34.720> that 00:21:35.149 --> 00:21:35.159 align:start position:0% existing things and given a name to that 00:21:35.159 --> 00:21:37.510 align:start position:0% existing things and given a name to that composition<00:21:36.159> but<00:21:36.720> one<00:21:36.840> of<00:21:36.960> the<00:21:37.039> more<00:21:37.200> exciting 00:21:37.510 --> 00:21:37.520 align:start position:0% composition but one of the more exciting 00:21:37.520 --> 00:21:38.870 align:start position:0% composition but one of the more exciting things<00:21:37.679> about<00:21:37.799> Bo<00:21:38.039> to<00:21:38.159> us<00:21:38.440> is<00:21:38.520> that<00:21:38.640> it<00:21:38.720> gives 00:21:38.870 --> 00:21:38.880 align:start position:0% things about Bo to us is that it gives 00:21:38.880 --> 00:21:41.070 align:start position:0% things about Bo to us is that it gives you<00:21:39.000> the<00:21:39.080> tools<00:21:39.320> you<00:21:39.480> need<00:21:40.080> to<00:21:40.279> create<00:21:40.840> new 00:21:41.070 --> 00:21:41.080 align:start position:0% you the tools you need to create new 00:21:41.080 --> 00:21:44.789 align:start position:0% you the tools you need to create new kinds<00:21:41.279> of<00:21:41.919> tasks<00:21:43.000> um<00:21:44.000> so<00:21:44.200> for<00:21:44.320> instance<00:21:44.640> one 00:21:44.789 --> 00:21:44.799 align:start position:0% kinds of tasks um so for instance one 00:21:44.799 --> 00:21:46.350 align:start position:0% kinds of tasks um so for instance one thing<00:21:44.919> you<00:21:45.039> might<00:21:45.320> need<00:21:45.480> to<00:21:45.640> do<00:21:46.000> which<00:21:46.120> is 00:21:46.350 --> 00:21:46.360 align:start position:0% thing you might need to do which is 00:21:46.360 --> 00:21:48.350 align:start position:0% thing you might need to do which is extremely<00:21:47.360> important<00:21:47.679> in<00:21:47.840> some<00:21:47.960> businesses 00:21:48.350 --> 00:21:48.360 align:start position:0% extremely important in some businesses 00:21:48.360 --> 00:21:50.990 align:start position:0% extremely important in some businesses is<00:21:48.480> you<00:21:48.600> need<00:21:48.720> to<00:21:48.840> convert<00:21:49.279> Java<00:21:50.279> into<00:21:50.480> for 00:21:50.990 --> 00:21:51.000 align:start position:0% is you need to convert Java into for 00:21:51.000 --> 00:21:52.630 align:start position:0% is you need to convert Java into for train 00:21:52.630 --> 00:21:52.640 align:start position:0% train 00:21:52.640 --> 00:21:55.990 align:start position:0% train and<00:21:53.640> true 00:21:55.990 --> 00:21:56.000 align:start position:0% and true 00:21:56.000 --> 00:21:58.990 align:start position:0% and true fact<00:21:57.000> this<00:21:57.080> is<00:21:57.320> actually<00:21:57.760> little<00:21:58.080> known<00:21:58.679> but 00:21:58.990 --> 00:21:59.000 align:start position:0% fact this is actually little known but 00:21:59.000 --> 00:22:00.990 align:start position:0% fact this is actually little known but you<00:21:59.159> know<00:21:59.760> check 00:22:00.990 --> 00:22:01.000 align:start position:0% you know check 00:22:01.000 --> 00:22:03.430 align:start position:0% you know check Wikipedia<00:22:02.000> uh<00:22:02.320> P<00:22:02.559> train<00:22:02.799> is<00:22:02.960> actually<00:22:03.200> just<00:22:03.320> an 00:22:03.430 --> 00:22:03.440 align:start position:0% Wikipedia uh P train is actually just an 00:22:03.440 --> 00:22:05.630 align:start position:0% Wikipedia uh P train is actually just an uppercase<00:22:04.000> version<00:22:04.240> of 00:22:05.630 --> 00:22:05.640 align:start position:0% uppercase version of 00:22:05.640 --> 00:22:10.669 align:start position:0% uppercase version of job<00:22:06.640> so<00:22:06.760> it's<00:22:06.919> really<00:22:07.120> quite 00:22:10.669 --> 00:22:10.679 align:start position:0% 00:22:10.679 --> 00:22:13.470 align:start position:0% trivial<00:22:11.679> unfortunately<00:22:12.600> this<00:22:12.679> is<00:22:12.840> kind<00:22:12.960> of<00:22:13.120> a 00:22:13.470 --> 00:22:13.480 align:start position:0% trivial unfortunately this is kind of a 00:22:13.480 --> 00:22:14.950 align:start position:0% trivial unfortunately this is kind of a controversial<00:22:14.080> view<00:22:14.279> so<00:22:14.400> we<00:22:14.559> haven't<00:22:14.720> built 00:22:14.950 --> 00:22:14.960 align:start position:0% controversial view so we haven't built 00:22:14.960 --> 00:22:16.710 align:start position:0% controversial view so we haven't built his<00:22:15.200> tasking<00:22:15.480> to<00:22:15.600> boot<00:22:15.919> yet<00:22:16.360> so<00:22:16.520> we're<00:22:16.640> going 00:22:16.710 --> 00:22:16.720 align:start position:0% his tasking to boot yet so we're going 00:22:16.720 --> 00:22:19.549 align:start position:0% his tasking to boot yet so we're going to<00:22:16.840> have<00:22:16.919> an<00:22:17.039> opportunity<00:22:17.640> here<00:22:17.840> to<00:22:18.279> um<00:22:18.960> to<00:22:19.240> to 00:22:19.549 --> 00:22:19.559 align:start position:0% to have an opportunity here to um to to 00:22:19.559 --> 00:22:22.149 align:start position:0% to have an opportunity here to um to to to<00:22:19.840> write<00:22:20.120> a<00:22:20.320> Java<00:22:20.679> to<00:22:20.840> Fortran 00:22:22.149 --> 00:22:22.159 align:start position:0% to write a Java to Fortran 00:22:22.159 --> 00:22:24.830 align:start position:0% to write a Java to Fortran transpiler<00:22:23.159> for<00:22:23.400> your 00:22:24.830 --> 00:22:24.840 align:start position:0% transpiler for your 00:22:24.840 --> 00:22:26.710 align:start position:0% transpiler for your satisfaction<00:22:25.840> yeah<00:22:26.080> let's<00:22:26.279> talk<00:22:26.400> about<00:22:26.559> the 00:22:26.710 --> 00:22:26.720 align:start position:0% satisfaction yeah let's talk about the 00:22:26.720 --> 00:22:28.149 align:start position:0% satisfaction yeah let's talk about the file<00:22:26.960> set<00:22:27.120> a<00:22:27.240> little<00:22:27.440> bit<00:22:27.880> because<00:22:28.039> we're 00:22:28.149 --> 00:22:28.159 align:start position:0% file set a little bit because we're 00:22:28.159 --> 00:22:30.350 align:start position:0% file set a little bit because we're going<00:22:28.240> to<00:22:28.320> be<00:22:28.720> dealing<00:22:29.000> with<00:22:29.080> it<00:22:29.200> in<00:22:29.279> a<00:22:29.440> minute 00:22:30.350 --> 00:22:30.360 align:start position:0% going to be dealing with it in a minute 00:22:30.360 --> 00:22:33.029 align:start position:0% going to be dealing with it in a minute um<00:22:30.760> file<00:22:31.039> set<00:22:31.240> can<00:22:31.440> be<00:22:32.120> the<00:22:32.279> main<00:22:32.640> the<00:22:32.760> main 00:22:33.029 --> 00:22:33.039 align:start position:0% um file set can be the main the main 00:22:33.039 --> 00:22:35.710 align:start position:0% um file set can be the main the main purpose<00:22:33.440> of<00:22:33.520> the<00:22:33.679> file<00:22:34.000> set<00:22:34.880> is<00:22:35.279> it<00:22:35.440> provides 00:22:35.710 --> 00:22:35.720 align:start position:0% purpose of the file set is it provides 00:22:35.720 --> 00:22:37.950 align:start position:0% purpose of the file set is it provides an<00:22:35.880> immutable<00:22:36.640> abstraction<00:22:37.200> that<00:22:37.320> we<00:22:37.440> can<00:22:37.640> use 00:22:37.950 --> 00:22:37.960 align:start position:0% an immutable abstraction that we can use 00:22:37.960 --> 00:22:40.350 align:start position:0% an immutable abstraction that we can use to<00:22:38.240> pass<00:22:38.559> information<00:22:39.120> between<00:22:39.520> tasks<00:22:40.080> why<00:22:40.200> is 00:22:40.350 --> 00:22:40.360 align:start position:0% to pass information between tasks why is 00:22:40.360 --> 00:22:42.029 align:start position:0% to pass information between tasks why is immutability<00:22:41.080> good<00:22:41.520> and<00:22:41.640> I<00:22:41.720> know<00:22:41.840> there's 00:22:42.029 --> 00:22:42.039 align:start position:0% immutability good and I know there's 00:22:42.039 --> 00:22:43.269 align:start position:0% immutability good and I know there's somebody<00:22:42.360> out<00:22:42.520> there<00:22:42.640> playing<00:22:42.840> a<00:22:42.960> drinking 00:22:43.269 --> 00:22:43.279 align:start position:0% somebody out there playing a drinking 00:22:43.279 --> 00:22:44.870 align:start position:0% somebody out there playing a drinking game<00:22:43.480> that<00:22:43.640> every<00:22:43.799> time<00:22:43.919> I<00:22:44.000> say<00:22:44.159> immutability 00:22:44.870 --> 00:22:44.880 align:start position:0% game that every time I say immutability 00:22:44.880 --> 00:22:47.950 align:start position:0% game that every time I say immutability has<00:22:45.000> to<00:22:45.200> like<00:22:45.360> drink<00:22:46.080> so<00:22:46.279> I'm<00:22:46.440> sorry<00:22:46.880> dude<00:22:47.880> but 00:22:47.950 --> 00:22:47.960 align:start position:0% has to like drink so I'm sorry dude but 00:22:47.960 --> 00:22:50.190 align:start position:0% has to like drink so I'm sorry dude but I'm<00:22:48.080> going<00:22:48.159> to<00:22:48.279> say<00:22:48.400> it<00:22:48.480> a<00:22:48.559> few<00:22:48.679> more<00:22:48.880> times<00:22:49.840> um 00:22:50.190 --> 00:22:50.200 align:start position:0% I'm going to say it a few more times um 00:22:50.200 --> 00:22:53.230 align:start position:0% I'm going to say it a few more times um immutability<00:22:51.200> you<00:22:51.320> be<00:22:51.480> wasted<00:22:51.799> by<00:22:51.919> like<00:22:52.000> 10 00:22:53.230 --> 00:22:53.240 align:start position:0% immutability you be wasted by like 10 00:22:53.240 --> 00:22:56.070 align:start position:0% immutability you be wasted by like 10 a.m.<00:22:54.240> so<00:22:54.440> immutability<00:22:55.039> is<00:22:55.200> great<00:22:55.480> because 00:22:56.070 --> 00:22:56.080 align:start position:0% a.m. so immutability is great because 00:22:56.080 --> 00:22:57.750 align:start position:0% a.m. so immutability is great because imagine<00:22:56.400> you<00:22:56.520> have<00:22:56.600> this<00:22:56.760> pipeline<00:22:57.120> of<00:22:57.279> tasks 00:22:57.750 --> 00:22:57.760 align:start position:0% imagine you have this pipeline of tasks 00:22:57.760 --> 00:23:00.470 align:start position:0% imagine you have this pipeline of tasks right<00:22:57.919> and<00:22:58.039> each<00:22:58.240> task<00:22:58.720> gets<00:22:58.880> a<00:22:59.039> file<00:22:59.320> set<00:23:00.240> and 00:23:00.470 --> 00:23:00.480 align:start position:0% right and each task gets a file set and 00:23:00.480 --> 00:23:02.110 align:start position:0% right and each task gets a file set and it<00:23:00.640> does<00:23:00.799> some<00:23:01.039> things<00:23:01.360> creates<00:23:01.600> a<00:23:01.720> new<00:23:01.880> file 00:23:02.110 --> 00:23:02.120 align:start position:0% it does some things creates a new file 00:23:02.120 --> 00:23:04.110 align:start position:0% it does some things creates a new file set<00:23:02.279> that<00:23:02.360> it<00:23:02.480> passes<00:23:02.720> on<00:23:02.799> to<00:23:03.000> next<00:23:03.279> guys<00:23:03.840> so<00:23:04.000> it 00:23:04.110 --> 00:23:04.120 align:start position:0% set that it passes on to next guys so it 00:23:04.120 --> 00:23:06.190 align:start position:0% set that it passes on to next guys so it can<00:23:04.279> hold<00:23:04.480> on<00:23:04.679> to<00:23:04.880> this<00:23:05.080> file<00:23:05.360> set<00:23:05.600> if<00:23:05.679> it's 00:23:06.190 --> 00:23:06.200 align:start position:0% can hold on to this file set if it's 00:23:06.200 --> 00:23:10.070 align:start position:0% can hold on to this file set if it's immutable<00:23:07.200> and<00:23:07.799> use<00:23:08.000> it<00:23:08.200> later<00:23:08.799> which<00:23:08.919> is<00:23:09.200> key 00:23:10.070 --> 00:23:10.080 align:start position:0% immutable and use it later which is key 00:23:10.080 --> 00:23:12.470 align:start position:0% immutable and use it later which is key so<00:23:10.480> otherwise<00:23:11.159> you<00:23:11.320> have<00:23:11.440> a<00:23:11.559> situation<00:23:12.279> where 00:23:12.470 --> 00:23:12.480 align:start position:0% so otherwise you have a situation where 00:23:12.480 --> 00:23:13.789 align:start position:0% so otherwise you have a situation where you<00:23:12.600> have<00:23:12.720> a<00:23:12.799> build<00:23:13.039> tool<00:23:13.320> where<00:23:13.520> they're 00:23:13.789 --> 00:23:13.799 align:start position:0% you have a build tool where they're 00:23:13.799 --> 00:23:15.510 align:start position:0% you have a build tool where they're passing<00:23:14.480> where<00:23:14.679> the<00:23:14.799> the<00:23:14.919> file<00:23:15.120> system<00:23:15.360> is 00:23:15.510 --> 00:23:15.520 align:start position:0% passing where the the file system is 00:23:15.520 --> 00:23:17.750 align:start position:0% passing where the the file system is mutable<00:23:16.279> right<00:23:16.760> so<00:23:16.960> what<00:23:17.120> happens<00:23:17.440> when<00:23:17.600> a 00:23:17.750 --> 00:23:17.760 align:start position:0% mutable right so what happens when a 00:23:17.760 --> 00:23:19.669 align:start position:0% mutable right so what happens when a task<00:23:18.120> wants<00:23:18.279> to<00:23:18.440> take<00:23:18.559> this<00:23:19.000> Java<00:23:19.279> file<00:23:19.559> and 00:23:19.669 --> 00:23:19.679 align:start position:0% task wants to take this Java file and 00:23:19.679 --> 00:23:21.510 align:start position:0% task wants to take this Java file and make<00:23:19.880> everything<00:23:20.120> uppercase<00:23:21.120> so<00:23:21.240> you<00:23:21.360> were 00:23:21.510 --> 00:23:21.520 align:start position:0% make everything uppercase so you were 00:23:21.520 --> 00:23:23.750 align:start position:0% make everything uppercase so you were typing<00:23:21.760> in<00:23:21.840> your<00:23:21.960> editor<00:23:22.679> happily<00:23:23.360> you<00:23:23.520> press 00:23:23.750 --> 00:23:23.760 align:start position:0% typing in your editor happily you press 00:23:23.760 --> 00:23:25.230 align:start position:0% typing in your editor happily you press the<00:23:23.840> build<00:23:24.159> button<00:23:24.440> and<00:23:24.600> now<00:23:24.880> everything's 00:23:25.230 --> 00:23:25.240 align:start position:0% the build button and now everything's 00:23:25.240 --> 00:23:27.750 align:start position:0% the build button and now everything's for<00:23:25.480> TR<00:23:25.760> and<00:23:25.880> you<00:23:25.960> don't<00:23:26.400> understand<00:23:26.600> it<00:23:27.320> right 00:23:27.750 --> 00:23:27.760 align:start position:0% for TR and you don't understand it right 00:23:27.760 --> 00:23:29.029 align:start position:0% for TR and you don't understand it right so 00:23:29.029 --> 00:23:29.039 align:start position:0% so 00:23:29.039 --> 00:23:31.549 align:start position:0% so yeah<00:23:29.200> and<00:23:29.360> mutability<00:23:29.919> is<00:23:30.120> key<00:23:30.440> because<00:23:31.159> tasks 00:23:31.549 --> 00:23:31.559 align:start position:0% yeah and mutability is key because tasks 00:23:31.559 --> 00:23:33.950 align:start position:0% yeah and mutability is key because tasks need<00:23:31.720> to<00:23:31.919> have<00:23:32.080> full<00:23:32.320> reain<00:23:32.799> to<00:23:33.279> modify<00:23:33.720> any 00:23:33.950 --> 00:23:33.960 align:start position:0% need to have full reain to modify any 00:23:33.960 --> 00:23:35.669 align:start position:0% need to have full reain to modify any file<00:23:34.360> because<00:23:34.840> what<00:23:34.960> we<00:23:35.080> want<00:23:35.200> to<00:23:35.360> achieve<00:23:35.559> in 00:23:35.669 --> 00:23:35.679 align:start position:0% file because what we want to achieve in 00:23:35.679 --> 00:23:37.390 align:start position:0% file because what we want to achieve in the<00:23:35.760> long<00:23:35.960> run<00:23:36.200> is<00:23:36.360> have<00:23:36.600> our<00:23:36.760> tools<00:23:37.080> doing 00:23:37.390 --> 00:23:37.400 align:start position:0% the long run is have our tools doing 00:23:37.400 --> 00:23:39.549 align:start position:0% the long run is have our tools doing more<00:23:37.679> and<00:23:37.880> us<00:23:38.039> doing<00:23:38.360> less<00:23:38.960> so<00:23:39.080> our<00:23:39.200> tools<00:23:39.440> need 00:23:39.549 --> 00:23:39.559 align:start position:0% more and us doing less so our tools need 00:23:39.559 --> 00:23:42.470 align:start position:0% more and us doing less so our tools need to<00:23:39.679> be<00:23:39.760> able<00:23:39.960> to<00:23:40.080> modify<00:23:40.919> anything<00:23:41.919> so<00:23:42.320> the 00:23:42.470 --> 00:23:42.480 align:start position:0% to be able to modify anything so the 00:23:42.480 --> 00:23:45.750 align:start position:0% to be able to modify anything so the solution<00:23:42.919> here<00:23:43.200> is<00:23:43.400> look<00:23:43.559> at<00:23:44.080> Git<00:23:45.080> You<00:23:45.200> Know 00:23:45.750 --> 00:23:45.760 align:start position:0% solution here is look at Git You Know 00:23:45.760 --> 00:23:47.510 align:start position:0% solution here is look at Git You Know listen<00:23:46.000> to<00:23:46.120> me<00:23:46.279> now<00:23:46.520> believe<00:23:46.799> me<00:23:46.960> later<00:23:47.360> it's 00:23:47.510 --> 00:23:47.520 align:start position:0% listen to me now believe me later it's 00:23:47.520 --> 00:23:48.990 align:start position:0% listen to me now believe me later it's like 00:23:48.990 --> 00:23:49.000 align:start position:0% like 00:23:49.000 --> 00:23:51.510 align:start position:0% like G<00:23:50.000> There's<00:23:50.240> real<00:23:50.520> files<00:23:50.880> underneath<00:23:51.320> because 00:23:51.510 --> 00:23:51.520 align:start position:0% G There's real files underneath because 00:23:51.520 --> 00:23:53.269 align:start position:0% G There's real files underneath because the<00:23:51.640> Java<00:23:51.960> class<00:23:52.240> path<00:23:52.480> is<00:23:52.559> a<00:23:52.679> real<00:23:52.880> thing<00:23:53.159> all 00:23:53.269 --> 00:23:53.279 align:start position:0% the Java class path is a real thing all 00:23:53.279 --> 00:23:55.510 align:start position:0% the Java class path is a real thing all the<00:23:53.400> jbm<00:23:53.760> tools<00:23:54.000> use<00:23:54.159> the<00:23:54.360> class<00:23:54.679> path<00:23:55.200> but<00:23:55.320> we 00:23:55.510 --> 00:23:55.520 align:start position:0% the jbm tools use the class path but we 00:23:55.520 --> 00:23:58.470 align:start position:0% the jbm tools use the class path but we provide<00:23:56.000> a<00:23:56.240> an<00:23:56.400> immutable<00:23:57.279> snapshot<00:23:57.919> of<00:23:58.039> it 00:23:58.470 --> 00:23:58.480 align:start position:0% provide a an immutable snapshot of it 00:23:58.480 --> 00:23:59.590 align:start position:0% provide a an immutable snapshot of it and<00:23:58.640> that's<00:23:58.799> the<00:23:58.960> information<00:23:59.279> that<00:23:59.400> gets 00:23:59.590 --> 00:23:59.600 align:start position:0% and that's the information that gets 00:23:59.600 --> 00:24:02.190 align:start position:0% and that's the information that gets passed<00:23:59.919> between<00:24:00.919> so<00:24:01.200> it's<00:24:01.400> immutable<00:24:01.960> it<00:24:02.080> has 00:24:02.190 --> 00:24:02.200 align:start position:0% passed between so it's immutable it has 00:24:02.200 --> 00:24:03.909 align:start position:0% passed between so it's immutable it has an<00:24:02.400> API<00:24:02.799> for<00:24:03.000> querying<00:24:03.360> it<00:24:03.520> meaning<00:24:03.720> you<00:24:03.799> can 00:24:03.909 --> 00:24:03.919 align:start position:0% an API for querying it meaning you can 00:24:03.919 --> 00:24:05.630 align:start position:0% an API for querying it meaning you can say<00:24:04.200> what's<00:24:04.400> in<00:24:04.559> the<00:24:04.720> file<00:24:05.000> set<00:24:05.279> and<00:24:05.360> it'll 00:24:05.630 --> 00:24:05.640 align:start position:0% say what's in the file set and it'll 00:24:05.640 --> 00:24:08.149 align:start position:0% say what's in the file set and it'll give<00:24:05.799> you<00:24:06.279> these<00:24:07.039> you<00:24:07.159> can<00:24:07.320> either<00:24:07.600> get<00:24:07.960> um 00:24:08.149 --> 00:24:08.159 align:start position:0% give you these you can either get um 00:24:08.159 --> 00:24:10.029 align:start position:0% give you these you can either get um actual<00:24:08.480> file<00:24:08.760> objects<00:24:09.080> or<00:24:09.279> just<00:24:09.440> the<00:24:09.600> relative 00:24:10.029 --> 00:24:10.039 align:start position:0% actual file objects or just the relative 00:24:10.039 --> 00:24:12.430 align:start position:0% actual file objects or just the relative path<00:24:10.279> in<00:24:10.440> the<00:24:10.600> in<00:24:10.679> the<00:24:10.799> class<00:24:11.159> path<00:24:12.080> um<00:24:12.200> you<00:24:12.279> can 00:24:12.430 --> 00:24:12.440 align:start position:0% path in the in the class path um you can 00:24:12.440 --> 00:24:15.070 align:start position:0% path in the in the class path um you can add<00:24:12.559> or<00:24:12.760> remove<00:24:13.159> things<00:24:13.720> which<00:24:14.480> returns<00:24:14.679> a<00:24:14.840> new 00:24:15.070 --> 00:24:15.080 align:start position:0% add or remove things which returns a new 00:24:15.080 --> 00:24:17.549 align:start position:0% add or remove things which returns a new immutable<00:24:15.559> file<00:24:15.840> set<00:24:16.120> object<00:24:17.120> and<00:24:17.240> you<00:24:17.360> can 00:24:17.549 --> 00:24:17.559 align:start position:0% immutable file set object and you can 00:24:17.559 --> 00:24:19.909 align:start position:0% immutable file set object and you can commit<00:24:18.000> which<00:24:18.120> is<00:24:18.200> a<00:24:18.360> mutating<00:24:18.919> function<00:24:19.720> that 00:24:19.909 --> 00:24:19.919 align:start position:0% commit which is a mutating function that 00:24:19.919 --> 00:24:22.669 align:start position:0% commit which is a mutating function that mutates<00:24:20.400> it<00:24:20.559> makes<00:24:20.960> the<00:24:21.080> underlying<00:24:21.720> files 00:24:22.669 --> 00:24:22.679 align:start position:0% mutates it makes the underlying files 00:24:22.679 --> 00:24:25.149 align:start position:0% mutates it makes the underlying files the<00:24:22.880> file<00:24:23.200> system<00:24:23.760> like<00:24:24.039> the<00:24:24.200> immutable<00:24:24.760> thing 00:24:25.149 --> 00:24:25.159 align:start position:0% the file system like the immutable thing 00:24:25.159 --> 00:24:27.430 align:start position:0% the file system like the immutable thing so<00:24:25.279> it's<00:24:25.480> like<00:24:25.679> restoring<00:24:26.200> from<00:24:26.440> backup<00:24:26.960> or 00:24:27.430 --> 00:24:27.440 align:start position:0% so it's like restoring from backup or 00:24:27.440 --> 00:24:29.430 align:start position:0% so it's like restoring from backup or you<00:24:27.559> know<00:24:27.720> checking<00:24:28.000> out<00:24:28.120> a<00:24:28.399> commit<00:24:28.679> and<00:24:28.960> get 00:24:29.430 --> 00:24:29.440 align:start position:0% you know checking out a commit and get 00:24:29.440 --> 00:24:30.990 align:start position:0% you know checking out a commit and get the<00:24:29.559> underly<00:24:30.000> files<00:24:30.240> are<00:24:30.360> like<00:24:30.480> the<00:24:30.600> working 00:24:30.990 --> 00:24:31.000 align:start position:0% the underly files are like the working 00:24:31.000 --> 00:24:33.669 align:start position:0% the underly files are like the working set<00:24:31.679> which<00:24:32.200> nobody<00:24:32.600> has<00:24:32.840> access<00:24:33.120> to<00:24:33.440> but<00:24:33.559> the 00:24:33.669 --> 00:24:33.679 align:start position:0% set which nobody has access to but the 00:24:33.679 --> 00:24:36.230 align:start position:0% set which nobody has access to but the internals<00:24:34.080> of<00:24:34.399> boot<00:24:35.399> and<00:24:35.559> you<00:24:35.720> interact<00:24:36.120> with 00:24:36.230 --> 00:24:36.240 align:start position:0% internals of boot and you interact with 00:24:36.240 --> 00:24:38.549 align:start position:0% internals of boot and you interact with that<00:24:36.480> by<00:24:36.600> making<00:24:36.919> commits<00:24:37.480> just<00:24:37.679> like<00:24:37.840> in<00:24:38.080> get 00:24:38.549 --> 00:24:38.559 align:start position:0% that by making commits just like in get 00:24:38.559 --> 00:24:43.990 align:start position:0% that by making commits just like in get to<00:24:38.760> this<00:24:38.960> file<00:24:39.279> set 00:24:43.990 --> 00:24:44.000 align:start position:0% 00:24:44.000 --> 00:24:46.909 align:start position:0% object<00:24:45.000> oh<00:24:45.279> this<00:24:45.360> is<00:24:45.520> my<00:24:45.720> part<00:24:46.240> I<00:24:46.320> fell<00:24:46.520> asleep 00:24:46.909 --> 00:24:46.919 align:start position:0% object oh this is my part I fell asleep 00:24:46.919 --> 00:24:53.149 align:start position:0% object oh this is my part I fell asleep wake<00:24:47.200> up<00:24:48.200> stage<00:24:49.120> um<00:24:50.120> yeah<00:24:50.399> so<00:24:51.039> here<00:24:51.279> is<00:24:52.159> uh 00:24:53.149 --> 00:24:53.159 align:start position:0% wake up stage um yeah so here is uh 00:24:53.159 --> 00:24:54.990 align:start position:0% wake up stage um yeah so here is uh there<00:24:53.320> are<00:24:53.600> expanded<00:24:53.960> build<00:24:54.159> out<00:24:54.520> our<00:24:54.600> for 00:24:54.990 --> 00:24:55.000 align:start position:0% there are expanded build out our for 00:24:55.000 --> 00:24:57.149 align:start position:0% there are expanded build out our for that<00:24:55.080> includes<00:24:55.399> our<00:24:55.559> Fortran<00:24:56.480> transpiler 00:24:57.149 --> 00:24:57.159 align:start position:0% that includes our Fortran transpiler 00:24:57.159 --> 00:25:02.549 align:start position:0% that includes our Fortran transpiler task<00:24:57.440> so<00:24:57.559> actually<00:24:57.760> I'm<00:24:58.600> here<00:24:59.840> for 00:25:02.549 --> 00:25:02.559 align:start position:0% task so actually I'm here for 00:25:02.559 --> 00:25:05.669 align:start position:0% task so actually I'm here for so<00:25:03.559> we<00:25:03.679> have<00:25:03.760> an<00:25:03.919> upcase<00:25:04.440> death<00:25:04.760> task<00:25:05.279> actually 00:25:05.669 --> 00:25:05.679 align:start position:0% so we have an upcase death task actually 00:25:05.679 --> 00:25:07.110 align:start position:0% so we have an upcase death task actually you<00:25:05.760> know<00:25:05.840> that<00:25:05.919> should<00:25:06.039> be<00:25:06.159> called<00:25:06.360> for<00:25:06.559> TR<00:25:06.799> or 00:25:07.110 --> 00:25:07.120 align:start position:0% you know that should be called for TR or 00:25:07.120 --> 00:25:09.870 align:start position:0% you know that should be called for TR or whatever<00:25:08.120> next<00:25:08.640> next<00:25:09.159> presentation<00:25:09.559> we<00:25:09.679> do 00:25:09.870 --> 00:25:09.880 align:start position:0% whatever next next presentation we do 00:25:09.880 --> 00:25:12.070 align:start position:0% whatever next next presentation we do that<00:25:10.399> so<00:25:10.520> we're<00:25:10.679> creating<00:25:11.159> a<00:25:11.279> death<00:25:11.559> TK<00:25:11.840> UPC 00:25:12.070 --> 00:25:12.080 align:start position:0% that so we're creating a death TK UPC 00:25:12.080 --> 00:25:13.830 align:start position:0% that so we're creating a death TK UPC case<00:25:12.360> and<00:25:12.440> it<00:25:12.559> has<00:25:12.679> a<00:25:12.880> documentation<00:25:13.440> string 00:25:13.830 --> 00:25:13.840 align:start position:0% case and it has a documentation string 00:25:13.840 --> 00:25:15.110 align:start position:0% case and it has a documentation string and<00:25:13.919> that<00:25:14.000> would<00:25:14.120> be<00:25:14.200> the<00:25:14.360> documentation<00:25:14.840> SC 00:25:15.110 --> 00:25:15.120 align:start position:0% and that would be the documentation SC 00:25:15.120 --> 00:25:17.750 align:start position:0% and that would be the documentation SC we<00:25:15.279> see<00:25:15.399> if<00:25:15.480> we<00:25:15.679> did<00:25:16.159> upase 00:25:17.750 --> 00:25:17.760 align:start position:0% we see if we did upase 00:25:17.760 --> 00:25:21.269 align:start position:0% we see if we did upase DH<00:25:18.840> next<00:25:19.840> we<00:25:20.039> have<00:25:20.360> an<00:25:20.520> opportunity<00:25:21.039> to 00:25:21.269 --> 00:25:21.279 align:start position:0% DH next we have an opportunity to 00:25:21.279 --> 00:25:23.630 align:start position:0% DH next we have an opportunity to configure<00:25:21.919> the<00:25:22.120> txk<00:25:22.679> so<00:25:22.880> maybe<00:25:23.080> our<00:25:23.200> fortrend 00:25:23.630 --> 00:25:23.640 align:start position:0% configure the txk so maybe our fortrend 00:25:23.640 --> 00:25:27.310 align:start position:0% configure the txk so maybe our fortrend files<00:25:23.960> Go<00:25:24.120> by<00:25:24.240> another<00:25:24.480> name<00:25:24.720> you<00:25:24.799> know<00:25:25.640> PHP<00:25:26.399> or 00:25:27.310 --> 00:25:27.320 align:start position:0% files Go by another name you know PHP or 00:25:27.320 --> 00:25:29.590 align:start position:0% files Go by another name you know PHP or C<00:25:27.679> maybe<00:25:27.880> are<00:25:28.080> also<00:25:28.399> P<00:25:28.559> TR<00:25:28.799> if<00:25:28.880> you<00:25:28.960> upcase<00:25:29.360> them 00:25:29.590 --> 00:25:29.600 align:start position:0% C maybe are also P TR if you upcase them 00:25:29.600 --> 00:25:31.430 align:start position:0% C maybe are also P TR if you upcase them they<00:25:29.760> actually<00:25:30.000> are 00:25:31.430 --> 00:25:31.440 align:start position:0% they actually are 00:25:31.440 --> 00:25:34.990 align:start position:0% they actually are true<00:25:32.600> um<00:25:33.600> so<00:25:33.760> this<00:25:33.840> is<00:25:34.000> where<00:25:34.120> you<00:25:34.240> can<00:25:34.480> add<00:25:34.799> add 00:25:34.990 --> 00:25:35.000 align:start position:0% true um so this is where you can add add 00:25:35.000 --> 00:25:36.710 align:start position:0% true um so this is where you can add add options<00:25:35.320> that<00:25:35.520> somehow<00:25:36.039> configure<00:25:36.559> or 00:25:36.710 --> 00:25:36.720 align:start position:0% options that somehow configure or 00:25:36.720 --> 00:25:38.630 align:start position:0% options that somehow configure or parameterize<00:25:37.399> this<00:25:37.600> task<00:25:37.880> so<00:25:38.159> inform<00:25:38.440> it<00:25:38.559> how 00:25:38.630 --> 00:25:38.640 align:start position:0% parameterize this task so inform it how 00:25:38.640 --> 00:25:42.070 align:start position:0% parameterize this task so inform it how to<00:25:38.760> do<00:25:38.880> this<00:25:39.200> job<00:25:40.200> now<00:25:40.440> inside<00:25:40.720> this<00:25:41.080> closure 00:25:42.070 --> 00:25:42.080 align:start position:0% to do this job now inside this closure 00:25:42.080 --> 00:25:43.630 align:start position:0% to do this job now inside this closure um<00:25:42.360> this<00:25:42.520> or<00:25:42.640> this<00:25:42.799> let<00:25:43.080> expression<00:25:43.520> we 00:25:43.630 --> 00:25:43.640 align:start position:0% um this or this let expression we 00:25:43.640 --> 00:25:44.830 align:start position:0% um this or this let expression we mentioned<00:25:43.880> earlier<00:25:44.279> this<00:25:44.399> is<00:25:44.480> a<00:25:44.600> place<00:25:44.720> where 00:25:44.830 --> 00:25:44.840 align:start position:0% mentioned earlier this is a place where 00:25:44.840 --> 00:25:46.669 align:start position:0% mentioned earlier this is a place where a<00:25:44.960> task<00:25:45.159> can<00:25:45.320> accumulate<00:25:45.799> State<00:25:46.399> and<00:25:46.559> what 00:25:46.669 --> 00:25:46.679 align:start position:0% a task can accumulate State and what 00:25:46.679 --> 00:25:48.950 align:start position:0% a task can accumulate State and what we're<00:25:46.840> doing<00:25:47.279> here<00:25:47.520> is<00:25:47.679> we're<00:25:47.919> initializing<00:25:48.640> a 00:25:48.950 --> 00:25:48.960 align:start position:0% we're doing here is we're initializing a 00:25:48.960 --> 00:25:52.110 align:start position:0% we're doing here is we're initializing a resource<00:25:49.960> that's<00:25:50.640> uh<00:25:51.240> invocations<00:25:51.840> of<00:25:51.960> this 00:25:52.110 --> 00:25:52.120 align:start position:0% resource that's uh invocations of this 00:25:52.120 --> 00:25:54.870 align:start position:0% resource that's uh invocations of this Tas<00:25:52.399> school<00:25:53.039> we<00:25:53.279> use<00:25:53.679> to<00:25:53.880> store<00:25:54.320> intermediate 00:25:54.870 --> 00:25:54.880 align:start position:0% Tas school we use to store intermediate 00:25:54.880 --> 00:25:56.630 align:start position:0% Tas school we use to store intermediate State<00:25:55.640> this<00:25:55.720> is<00:25:55.880> kind<00:25:56.000> of<00:25:56.120> what<00:25:56.240> your<00:25:56.399> file 00:25:56.630 --> 00:25:56.640 align:start position:0% State this is kind of what your file 00:25:56.640 --> 00:25:58.789 align:start position:0% State this is kind of what your file system<00:25:56.960> is<00:25:57.200> between<00:25:57.760> G<00:25:57.960> commit<00:25:58.520> this<00:25:58.600> is<00:25:58.679> the 00:25:58.789 --> 00:25:58.799 align:start position:0% system is between G commit this is the 00:25:58.799 --> 00:26:00.389 align:start position:0% system is between G commit this is the place<00:25:58.960> where<00:25:59.039> you're<00:25:59.200> doing<00:25:59.360> your<00:25:59.520> working 00:26:00.389 --> 00:26:00.399 align:start position:0% place where you're doing your working 00:26:00.399 --> 00:26:01.909 align:start position:0% place where you're doing your working you<00:26:00.600> prepare<00:26:01.000> things<00:26:01.320> and<00:26:01.399> when<00:26:01.520> you're<00:26:01.720> ready 00:26:01.909 --> 00:26:01.919 align:start position:0% you prepare things and when you're ready 00:26:01.919 --> 00:26:03.310 align:start position:0% you prepare things and when you're ready you<00:26:02.080> commit<00:26:02.320> them<00:26:02.399> to<00:26:02.520> the<00:26:02.600> file<00:26:02.840> set<00:26:03.080> but<00:26:03.200> in 00:26:03.310 --> 00:26:03.320 align:start position:0% you commit them to the file set but in 00:26:03.320 --> 00:26:05.029 align:start position:0% you commit them to the file set but in between<00:26:03.640> those<00:26:03.799> two<00:26:04.039> times<00:26:04.559> is<00:26:04.679> when<00:26:04.799> you<00:26:04.880> need 00:26:05.029 --> 00:26:05.039 align:start position:0% between those two times is when you need 00:26:05.039 --> 00:26:07.350 align:start position:0% between those two times is when you need to<00:26:05.200> work<00:26:05.440> with<00:26:05.679> sort<00:26:05.799> of<00:26:05.919> a<00:26:06.039> live<00:26:06.279> meable<00:26:06.640> thing 00:26:07.350 --> 00:26:07.360 align:start position:0% to work with sort of a live meable thing 00:26:07.360 --> 00:26:08.510 align:start position:0% to work with sort of a live meable thing this<00:26:07.520> kind<00:26:07.600> of<00:26:07.720> analogous<00:26:08.080> to<00:26:08.200> the<00:26:08.279> way<00:26:08.399> one 00:26:08.510 --> 00:26:08.520 align:start position:0% this kind of analogous to the way one 00:26:08.520 --> 00:26:10.350 align:start position:0% this kind of analogous to the way one works<00:26:08.679> with<00:26:08.840> transient<00:26:09.360> and<00:26:09.520> closure<00:26:10.240> you 00:26:10.350 --> 00:26:10.360 align:start position:0% works with transient and closure you 00:26:10.360 --> 00:26:11.789 align:start position:0% works with transient and closure you know<00:26:10.559> nobody<00:26:10.840> cares<00:26:11.120> as<00:26:11.200> long<00:26:11.320> as<00:26:11.399> it<00:26:11.520> happened 00:26:11.789 --> 00:26:11.799 align:start position:0% know nobody cares as long as it happened 00:26:11.799 --> 00:26:12.750 align:start position:0% know nobody cares as long as it happened inside<00:26:12.039> the 00:26:12.750 --> 00:26:12.760 align:start position:0% inside the 00:26:12.760 --> 00:26:14.549 align:start position:0% inside the function 00:26:14.549 --> 00:26:14.559 align:start position:0% function 00:26:14.559 --> 00:26:16.389 align:start position:0% function um 00:26:16.389 --> 00:26:16.399 align:start position:0% um 00:26:16.399 --> 00:26:20.430 align:start position:0% um next<00:26:17.399> inside<00:26:17.880> the<00:26:18.480> innermost<00:26:19.480> uh<00:26:19.720> function<00:26:20.240> of 00:26:20.430 --> 00:26:20.440 align:start position:0% next inside the innermost uh function of 00:26:20.440 --> 00:26:22.669 align:start position:0% next inside the innermost uh function of the<00:26:20.600> of<00:26:20.720> this<00:26:21.240> of<00:26:21.360> this<00:26:21.559> task<00:26:22.320> is<00:26:22.440> when<00:26:22.520> we're 00:26:22.669 --> 00:26:22.679 align:start position:0% the of this of this task is when we're 00:26:22.679 --> 00:26:24.710 align:start position:0% the of this of this task is when we're calling<00:26:23.000> a<00:26:23.159> f<00:26:23.640> a<00:26:23.799> function<00:26:24.080> called<00:26:24.279> upcase 00:26:24.710 --> 00:26:24.720 align:start position:0% calling a f a function called upcase 00:26:24.720 --> 00:26:26.510 align:start position:0% calling a f a function called upcase files<00:26:25.120> and<00:26:25.240> if<00:26:25.360> we<00:26:25.480> look<00:26:25.600> at<00:26:25.760> upcase<00:26:26.120> files<00:26:26.360> up 00:26:26.510 --> 00:26:26.520 align:start position:0% files and if we look at upcase files up 00:26:26.520 --> 00:26:27.909 align:start position:0% files and if we look at upcase files up here<00:26:26.679> it<00:26:26.760> takes<00:26:26.960> a<00:26:27.120> directory<00:26:27.559> a<00:26:27.679> working 00:26:27.909 --> 00:26:27.919 align:start position:0% here it takes a directory a working 00:26:27.919 --> 00:26:28.909 align:start position:0% here it takes a directory a working directory 00:26:28.909 --> 00:26:28.919 align:start position:0% directory 00:26:28.919 --> 00:26:30.110 align:start position:0% directory and<00:26:29.039> a<00:26:29.200> list<00:26:29.360> of 00:26:30.110 --> 00:26:30.120 align:start position:0% and a list of 00:26:30.120 --> 00:26:33.149 align:start position:0% and a list of files<00:26:31.120> um<00:26:31.600> and<00:26:32.159> inside<00:26:32.520> there<00:26:32.640> it<00:26:32.760> calls<00:26:33.039> a 00:26:33.149 --> 00:26:33.159 align:start position:0% files um and inside there it calls a 00:26:33.159 --> 00:26:35.669 align:start position:0% files um and inside there it calls a function<00:26:33.480> upcase<00:26:34.039> bang<00:26:34.960> now<00:26:35.200> this<00:26:35.320> is<00:26:35.440> such<00:26:35.559> a 00:26:35.669 --> 00:26:35.679 align:start position:0% function upcase bang now this is such a 00:26:35.679 --> 00:26:36.990 align:start position:0% function upcase bang now this is such a useful<00:26:35.960> thing<00:26:36.039> to<00:26:36.200> do<00:26:36.360> that<00:26:36.520> actually<00:26:36.919> I 00:26:36.990 --> 00:26:37.000 align:start position:0% useful thing to do that actually I 00:26:37.000 --> 00:26:40.029 align:start position:0% useful thing to do that actually I created<00:26:37.279> in<00:26:37.440> push<00:26:37.600> to<00:26:37.720> Clow<00:26:37.960> jars<00:26:38.799> a<00:26:38.960> little 00:26:40.029 --> 00:26:40.039 align:start position:0% created in push to Clow jars a little 00:26:40.039 --> 00:26:43.710 align:start position:0% created in push to Clow jars a little Library<00:26:41.039> it's<00:26:41.279> super<00:26:41.799> sweet<00:26:42.799> it<00:26:42.960> uppercases 00:26:43.710 --> 00:26:43.720 align:start position:0% Library it's super sweet it uppercases 00:26:43.720 --> 00:26:45.710 align:start position:0% Library it's super sweet it uppercases things<00:26:44.279> he<00:26:44.399> used<00:26:44.640> the<00:26:44.760> install<00:26:45.200> task<00:26:45.480> and 00:26:45.710 --> 00:26:45.720 align:start position:0% things he used the install task and 00:26:45.720 --> 00:26:48.389 align:start position:0% things he used the install task and everything<00:26:46.320> yes<00:26:47.320> yeah<00:26:47.679> yeah<00:26:47.799> I<00:26:47.880> was<00:26:48.240> pretty 00:26:48.389 --> 00:26:48.399 align:start position:0% everything yes yeah yeah I was pretty 00:26:48.399 --> 00:26:50.310 align:start position:0% everything yes yeah yeah I was pretty proud<00:26:48.720> myself<00:26:49.159> unfortunately<00:26:50.080> you<00:26:50.200> all 00:26:50.310 --> 00:26:50.320 align:start position:0% proud myself unfortunately you all 00:26:50.320 --> 00:26:51.630 align:start position:0% proud myself unfortunately you all weren't<00:26:50.559> around<00:26:50.760> to<00:26:50.880> Plat<00:26:51.120> when<00:26:51.200> I<00:26:51.320> did<00:26:51.440> it<00:26:51.559> but 00:26:51.630 --> 00:26:51.640 align:start position:0% weren't around to Plat when I did it but 00:26:51.640 --> 00:26:54.669 align:start position:0% weren't around to Plat when I did it but it<00:26:51.720> was<00:26:51.840> pretty<00:26:52.320> awesome<00:26:53.320> um<00:26:53.919> so<00:26:54.159> inside<00:26:54.480> this 00:26:54.669 --> 00:26:54.679 align:start position:0% it was pretty awesome um so inside this 00:26:54.679 --> 00:26:55.990 align:start position:0% it was pretty awesome um so inside this task<00:26:55.000> we're<00:26:55.159> calling<00:26:55.440> this<00:26:55.600> function<00:26:55.880> and 00:26:55.990 --> 00:26:56.000 align:start position:0% task we're calling this function and 00:26:56.000 --> 00:26:57.630 align:start position:0% task we're calling this function and this<00:26:56.120> is<00:26:56.559> really<00:26:56.840> typical<00:26:57.159> of<00:26:57.240> a<00:26:57.320> lot<00:26:57.440> of<00:26:57.520> the 00:26:57.630 --> 00:26:57.640 align:start position:0% this is really typical of a lot of the 00:26:57.640 --> 00:26:58.909 align:start position:0% this is really typical of a lot of the tasks<00:26:57.880> we've<00:26:58.000> written<00:26:58.279> so<00:26:58.480> far<00:26:58.640> there<00:26:58.720> are 00:26:58.909 --> 00:26:58.919 align:start position:0% tasks we've written so far there are 00:26:58.919 --> 00:27:00.510 align:start position:0% tasks we've written so far there are existing<00:26:59.399> things<00:26:59.640> that<00:26:59.760> have<00:26:59.880> been<00:27:00.039> written 00:27:00.510 --> 00:27:00.520 align:start position:0% existing things that have been written 00:27:00.520 --> 00:27:02.149 align:start position:0% existing things that have been written to<00:27:00.679> convert<00:27:01.000> one<00:27:01.159> kind<00:27:01.279> of<00:27:01.440> file<00:27:01.640> to<00:27:01.799> another 00:27:02.149 --> 00:27:02.159 align:start position:0% to convert one kind of file to another 00:27:02.159 --> 00:27:03.310 align:start position:0% to convert one kind of file to another whether<00:27:02.279> it's<00:27:02.399> you<00:27:02.559> en<00:27:02.679> closure<00:27:02.960> script<00:27:03.200> or 00:27:03.310 --> 00:27:03.320 align:start position:0% whether it's you en closure script or 00:27:03.320 --> 00:27:07.590 align:start position:0% whether it's you en closure script or scss<00:27:04.080> or<00:27:05.080> whatever<00:27:06.080> and<00:27:06.320> we<00:27:06.480> write<00:27:06.720> tasks<00:27:07.120> to 00:27:07.590 --> 00:27:07.600 align:start position:0% scss or whatever and we write tasks to 00:27:07.600 --> 00:27:09.149 align:start position:0% scss or whatever and we write tasks to wrap<00:27:07.960> and<00:27:08.080> sort<00:27:08.240> of<00:27:08.399> sanitize<00:27:09.000> that 00:27:09.149 --> 00:27:09.159 align:start position:0% wrap and sort of sanitize that 00:27:09.159 --> 00:27:10.549 align:start position:0% wrap and sort of sanitize that functionality<00:27:09.720> such<00:27:09.919> that<00:27:10.000> we<00:27:10.080> can<00:27:10.240> compose 00:27:10.549 --> 00:27:10.559 align:start position:0% functionality such that we can compose 00:27:10.559 --> 00:27:12.029 align:start position:0% functionality such that we can compose these<00:27:10.679> things 00:27:12.029 --> 00:27:12.039 align:start position:0% these things 00:27:12.039 --> 00:27:16.669 align:start position:0% these things together<00:27:13.039> finally<00:27:13.559> at<00:27:13.679> the<00:27:13.799> end<00:27:14.720> oops<00:27:15.720> we<00:27:16.000> have 00:27:16.669 --> 00:27:16.679 align:start position:0% together finally at the end oops we have 00:27:16.679 --> 00:27:19.110 align:start position:0% together finally at the end oops we have and<00:27:17.320> I<00:27:17.399> mean<00:27:17.600> at<00:27:17.720> the<00:27:17.799> end<00:27:17.960> of<00:27:18.159> this<00:27:18.640> task<00:27:18.919> so 00:27:19.110 --> 00:27:19.120 align:start position:0% and I mean at the end of this task so 00:27:19.120 --> 00:27:21.149 align:start position:0% and I mean at the end of this task so the<00:27:19.240> task<00:27:19.480> has<00:27:19.600> done<00:27:19.799> its<00:27:19.960> work<00:27:20.720> it<00:27:20.880> called 00:27:21.149 --> 00:27:21.159 align:start position:0% the task has done its work it called 00:27:21.159 --> 00:27:22.830 align:start position:0% the task has done its work it called upcase<00:27:21.559> files<00:27:21.760> on<00:27:21.880> this<00:27:22.039> directory<00:27:22.480> upas 00:27:22.830 --> 00:27:22.840 align:start position:0% upcase files on this directory upas 00:27:22.840 --> 00:27:24.470 align:start position:0% upcase files on this directory upas files<00:27:23.080> went<00:27:23.240> in<00:27:23.320> and<00:27:23.440> mutated<00:27:23.880> a<00:27:23.960> bunch<00:27:24.120> of 00:27:24.470 --> 00:27:24.480 align:start position:0% files went in and mutated a bunch of 00:27:24.480 --> 00:27:27.389 align:start position:0% files went in and mutated a bunch of files<00:27:24.760> in<00:27:24.880> our<00:27:25.000> working<00:27:25.320> directory<00:27:25.880> this<00:27:26.399> dur 00:27:27.389 --> 00:27:27.399 align:start position:0% files in our working directory this dur 00:27:27.399 --> 00:27:29.350 align:start position:0% files in our working directory this dur and<00:27:27.559> now<00:27:27.679> what<00:27:27.799> we<00:27:27.880> do<00:27:28.039> is<00:27:28.320> we<00:27:28.559> add<00:27:29.200> this 00:27:29.350 --> 00:27:29.360 align:start position:0% and now what we do is we add this 00:27:29.360 --> 00:27:31.029 align:start position:0% and now what we do is we add this directory<00:27:29.720> to<00:27:29.840> the<00:27:29.919> file<00:27:30.200> set<00:27:30.440> this<00:27:30.520> is<00:27:30.760> the 00:27:31.029 --> 00:27:31.039 align:start position:0% directory to the file set this is the 00:27:31.039 --> 00:27:32.950 align:start position:0% directory to the file set this is the sort<00:27:31.240> of<00:27:31.520> analogous<00:27:31.919> to<00:27:32.039> a<00:27:32.200> get<00:27:32.399> add<00:27:32.679> followed 00:27:32.950 --> 00:27:32.960 align:start position:0% sort of analogous to a get add followed 00:27:32.960 --> 00:27:35.630 align:start position:0% sort of analogous to a get add followed by<00:27:33.080> a<00:27:33.200> get<00:27:33.399> commit<00:27:34.279> we're<00:27:35.000> adding<00:27:35.320> things<00:27:35.480> to 00:27:35.630 --> 00:27:35.640 align:start position:0% by a get commit we're adding things to 00:27:35.640 --> 00:27:37.389 align:start position:0% by a get commit we're adding things to the<00:27:35.760> file<00:27:35.960> set<00:27:36.200> value<00:27:36.720> committing<00:27:37.120> it<00:27:37.279> and 00:27:37.389 --> 00:27:37.399 align:start position:0% the file set value committing it and 00:27:37.399 --> 00:27:39.190 align:start position:0% the file set value committing it and preparing<00:27:37.760> it<00:27:37.840> to<00:27:37.960> be<00:27:38.279> passed<00:27:38.640> to<00:27:38.799> the<00:27:38.960> next 00:27:39.190 --> 00:27:39.200 align:start position:0% preparing it to be passed to the next 00:27:39.200 --> 00:27:42.549 align:start position:0% preparing it to be passed to the next PATH<00:27:39.480> in<00:27:39.600> the<00:27:39.679> change<00:27:40.039> if<00:27:40.200> there<00:27:40.320> is<00:27:40.880> one<00:27:41.880> um 00:27:42.549 --> 00:27:42.559 align:start position:0% PATH in the change if there is one um 00:27:42.559 --> 00:27:43.630 align:start position:0% PATH in the change if there is one um which<00:27:42.640> is 00:27:43.630 --> 00:27:43.640 align:start position:0% which is 00:27:43.640 --> 00:27:46.269 align:start position:0% which is great<00:27:44.640> works<00:27:44.960> awesome<00:27:45.640> we<00:27:45.760> could<00:27:45.960> actually 00:27:46.269 --> 00:27:46.279 align:start position:0% great works awesome we could actually 00:27:46.279 --> 00:27:48.590 align:start position:0% great works awesome we could actually maybe<00:27:46.480> run<00:27:46.640> that<00:27:46.720> one<00:27:46.840> with<00:27:46.960> the<00:27:47.039> command<00:27:47.600> line 00:27:48.590 --> 00:27:48.600 align:start position:0% maybe run that one with the command line 00:27:48.600 --> 00:28:01.070 align:start position:0% maybe run that one with the command line yeah<00:27:48.760> let's<00:27:48.960> do<00:27:49.200> that 00:28:01.070 --> 00:28:01.080 align:start position:0% 00:28:01.080 --> 00:28:08.470 align:start position:0% there<00:28:01.240> it<00:28:01.440> is<00:28:02.120> that's 00:28:08.470 --> 00:28:08.480 align:start position:0% 00:28:08.480 --> 00:28:12.470 align:start position:0% Lor<00:28:09.640> cool<00:28:10.640> and<00:28:10.840> by<00:28:11.000> default<00:28:11.320> boot<00:28:11.600> will<00:28:12.159> dump 00:28:12.470 --> 00:28:12.480 align:start position:0% Lor cool and by default boot will dump 00:28:12.480 --> 00:28:14.830 align:start position:0% Lor cool and by default boot will dump the<00:28:12.640> final<00:28:13.159> file<00:28:13.519> set<00:28:13.880> value<00:28:14.360> or<00:28:14.559> rather 00:28:14.830 --> 00:28:14.840 align:start position:0% the final file set value or rather 00:28:14.840 --> 00:28:16.190 align:start position:0% the final file set value or rather synchronizes<00:28:15.360> that<00:28:15.519> final<00:28:15.799> value<00:28:16.000> to 00:28:16.190 --> 00:28:16.200 align:start position:0% synchronizes that final value to 00:28:16.200 --> 00:28:19.230 align:start position:0% synchronizes that final value to directory<00:28:16.720> Target<00:28:17.440> directory<00:28:18.440> and<00:28:18.960> there<00:28:19.120> we 00:28:19.230 --> 00:28:19.240 align:start position:0% directory Target directory and there we 00:28:19.240 --> 00:28:22.070 align:start position:0% directory Target directory and there we have<00:28:19.360> it<00:28:19.760> for 00:28:22.070 --> 00:28:22.080 align:start position:0% 00:28:22.080 --> 00:28:25.470 align:start position:0% train<00:28:23.080> there's<00:28:23.240> a<00:28:23.640> problem<00:28:24.640> hold 00:28:25.470 --> 00:28:25.480 align:start position:0% train there's a problem hold 00:28:25.480 --> 00:28:34.149 align:start position:0% train there's a problem hold the<00:28:26.480> please<00:28:26.720> be<00:28:27.000> boot<00:28:27.240> show<00:28:27.519> Dash<00:28:27.799> me 00:28:34.149 --> 00:28:34.159 align:start position:0% 00:28:34.159 --> 00:28:36.389 align:start position:0% execute<00:28:35.159> look<00:28:35.279> at<00:28:35.399> these 00:28:36.389 --> 00:28:36.399 align:start position:0% execute look at these 00:28:36.399 --> 00:28:38.430 align:start position:0% execute look at these dependencies<00:28:37.399> let's<00:28:37.679> let's<00:28:37.840> celebrate<00:28:38.279> these 00:28:38.430 --> 00:28:38.440 align:start position:0% dependencies let's let's celebrate these 00:28:38.440 --> 00:28:39.710 align:start position:0% dependencies let's let's celebrate these dependencies<00:28:38.840> for<00:28:38.919> a<00:28:39.000> minute<00:28:39.159> can<00:28:39.279> we<00:28:39.360> scroll 00:28:39.710 --> 00:28:39.720 align:start position:0% dependencies for a minute can we scroll 00:28:39.720 --> 00:28:42.990 align:start position:0% dependencies for a minute can we scroll up<00:28:40.559> I<00:28:40.640> like<00:28:40.799> that<00:28:40.960> x<00:28:41.200> Allen 00:28:42.990 --> 00:28:43.000 align:start position:0% up I like that x Allen 00:28:43.000 --> 00:28:46.509 align:start position:0% up I like that x Allen library<00:28:44.000> and<00:28:44.279> J<00:28:44.840> boss<00:28:45.840> so<00:28:46.000> in<00:28:46.080> the<00:28:46.200> course<00:28:46.360> of 00:28:46.509 --> 00:28:46.519 align:start position:0% library and J boss so in the course of 00:28:46.519 --> 00:28:50.669 align:start position:0% library and J boss so in the course of developing<00:28:46.919> the<00:28:47.039> updates 00:28:50.669 --> 00:28:50.679 align:start position:0% 00:28:50.679 --> 00:28:52.669 align:start position:0% Library<00:28:51.679> so<00:28:51.840> when<00:28:51.960> I<00:28:52.080> was<00:28:52.200> Raising<00:28:52.559> this 00:28:52.669 --> 00:28:52.679 align:start position:0% Library so when I was Raising this 00:28:52.679 --> 00:28:54.389 align:start position:0% Library so when I was Raising this function<00:28:53.000> to<00:28:53.159> uppercase<00:28:53.640> strings<00:28:54.039> I<00:28:54.159> thought 00:28:54.389 --> 00:28:54.399 align:start position:0% function to uppercase strings I thought 00:28:54.399 --> 00:28:55.590 align:start position:0% function to uppercase strings I thought man<00:28:54.600> you<00:28:54.679> know<00:28:54.799> this<00:28:54.880> surely<00:28:55.240> has<00:28:55.360> been<00:28:55.480> done 00:28:55.590 --> 00:28:55.600 align:start position:0% man you know this surely has been done 00:28:55.600 --> 00:28:57.190 align:start position:0% man you know this surely has been done in<00:28:55.720> some<00:28:55.840> other<00:28:56.039> Library<00:28:56.399> so<00:28:56.519> I<00:28:56.640> went<00:28:56.760> and<00:28:57.000> got 00:28:57.190 --> 00:28:57.200 align:start position:0% in some other Library so I went and got 00:28:57.200 --> 00:29:00.149 align:start position:0% in some other Library so I went and got every<00:28:57.600> Library<00:28:58.240> fromen<00:28:58.640> and<00:28:58.960> clars<00:28:59.960> and<00:29:00.039> I 00:29:00.149 --> 00:29:00.159 align:start position:0% every Library fromen and clars and I 00:29:00.159 --> 00:29:01.990 align:start position:0% every Library fromen and clars and I brought<00:29:00.360> them<00:29:00.519> in<00:29:00.799> cuz<00:29:01.440> I<00:29:01.519> don't<00:29:01.640> know<00:29:01.799> I<00:29:01.880> was 00:29:01.990 --> 00:29:02.000 align:start position:0% brought them in cuz I don't know I was 00:29:02.000 --> 00:29:03.149 align:start position:0% brought them in cuz I don't know I was feeling 00:29:03.149 --> 00:29:03.159 align:start position:0% feeling 00:29:03.159 --> 00:29:05.630 align:start position:0% feeling it<00:29:04.159> which 00:29:05.630 --> 00:29:05.640 align:start position:0% it which 00:29:05.640 --> 00:29:09.710 align:start position:0% it which US<00:29:06.640> yeah<00:29:06.760> a<00:29:06.880> lot<00:29:06.960> of<00:29:07.080> people<00:29:07.279> are<00:29:07.440> like 00:29:09.710 --> 00:29:09.720 align:start position:0% 00:29:09.720 --> 00:29:12.950 align:start position:0% me<00:29:10.720> brings<00:29:11.000> us<00:29:11.120> to<00:29:11.320> pods<00:29:11.919> anyway<00:29:12.679> so<00:29:12.840> we 00:29:12.950 --> 00:29:12.960 align:start position:0% me brings us to pods anyway so we 00:29:12.960 --> 00:29:16.029 align:start position:0% me brings us to pods anyway so we invented<00:29:13.360> this 00:29:16.029 --> 00:29:16.039 align:start position:0% 00:29:16.039 --> 00:29:18.590 align:start position:0% thing<00:29:17.039> first<00:29:17.399> Toby<00:29:17.679> Crawley<00:29:18.159> oh<00:29:18.320> yeah<00:29:18.440> that's 00:29:18.590 --> 00:29:18.600 align:start position:0% thing first Toby Crawley oh yeah that's 00:29:18.600 --> 00:29:20.990 align:start position:0% thing first Toby Crawley oh yeah that's right<00:29:18.760> we<00:29:19.440> that<00:29:19.840> Toby<00:29:20.120> Crawley<00:29:20.480> of<00:29:20.679> mutant 00:29:20.990 --> 00:29:21.000 align:start position:0% right we that Toby Crawley of mutant 00:29:21.000 --> 00:29:22.630 align:start position:0% right we that Toby Crawley of mutant thing<00:29:21.360> actually<00:29:21.799> sort<00:29:22.000> of<00:29:22.120> have<00:29:22.240> the<00:29:22.320> original 00:29:22.630 --> 00:29:22.640 align:start position:0% thing actually sort of have the original 00:29:22.640 --> 00:29:25.990 align:start position:0% thing actually sort of have the original idea<00:29:23.279> yes<00:29:23.840> there<00:29:23.919> he<00:29:24.080> is<00:29:24.840> thank<00:29:24.960> you<00:29:25.159> dude<00:29:25.679> yes 00:29:25.990 --> 00:29:26.000 align:start position:0% idea yes there he is thank you dude yes 00:29:26.000 --> 00:29:29.029 align:start position:0% idea yes there he is thank you dude yes you<00:29:26.159> saved<00:29:26.440> us<00:29:26.559> all<00:29:26.760> from<00:29:26.960> dependency<00:29:27.440> heal 00:29:29.029 --> 00:29:29.039 align:start position:0% you saved us all from dependency heal 00:29:29.039 --> 00:29:31.230 align:start position:0% you saved us all from dependency heal and<00:29:29.480> so<00:29:29.640> the<00:29:29.799> idea<00:29:30.080> here<00:29:30.240> is<00:29:30.440> that<00:29:30.840> we<00:29:30.960> have<00:29:31.080> a 00:29:31.230 --> 00:29:31.240 align:start position:0% and so the idea here is that we have a 00:29:31.240 --> 00:29:32.870 align:start position:0% and so the idea here is that we have a program<00:29:31.519> inclosure<00:29:32.279> and<00:29:32.440> we<00:29:32.559> have<00:29:32.720> other 00:29:32.870 --> 00:29:32.880 align:start position:0% program inclosure and we have other 00:29:32.880 --> 00:29:34.269 align:start position:0% program inclosure and we have other things<00:29:33.039> we<00:29:33.159> want<00:29:33.279> to<00:29:33.360> use<00:29:33.519> from<00:29:33.720> closure<00:29:34.159> but 00:29:34.269 --> 00:29:34.279 align:start position:0% things we want to use from closure but 00:29:34.279 --> 00:29:35.750 align:start position:0% things we want to use from closure but we<00:29:34.399> can't<00:29:34.640> use<00:29:34.840> them<00:29:35.080> because<00:29:35.320> they<00:29:35.480> have<00:29:35.640> all 00:29:35.750 --> 00:29:35.760 align:start position:0% we can't use them because they have all 00:29:35.760 --> 00:29:38.669 align:start position:0% we can't use them because they have all these<00:29:36.000> dependencies<00:29:36.640> that<00:29:37.080> interfere<00:29:38.080> with 00:29:38.669 --> 00:29:38.679 align:start position:0% these dependencies that interfere with 00:29:38.679 --> 00:29:40.509 align:start position:0% these dependencies that interfere with the<00:29:38.919> things<00:29:39.159> that<00:29:39.240> are<00:29:39.360> in<00:29:39.480> our<00:29:39.679> program<00:29:40.399> and 00:29:40.509 --> 00:29:40.519 align:start position:0% the things that are in our program and 00:29:40.519 --> 00:29:42.029 align:start position:0% the things that are in our program and the<00:29:40.600> way<00:29:40.720> they<00:29:40.880> interfere<00:29:41.279> is<00:29:41.480> basically<00:29:41.919> if 00:29:42.029 --> 00:29:42.039 align:start position:0% the way they interfere is basically if 00:29:42.039 --> 00:29:43.870 align:start position:0% the way they interfere is basically if you<00:29:42.159> have<00:29:42.279> a<00:29:42.360> jar<00:29:42.679> file<00:29:42.919> that<00:29:43.080> has<00:29:43.159> a<00:29:43.360> class<00:29:43.720> of 00:29:43.870 --> 00:29:43.880 align:start position:0% you have a jar file that has a class of 00:29:43.880 --> 00:29:45.310 align:start position:0% you have a jar file that has a class of the<00:29:44.000> same<00:29:44.320> name<00:29:44.679> as<00:29:44.840> something<00:29:45.120> that's 00:29:45.310 --> 00:29:45.320 align:start position:0% the same name as something that's 00:29:45.320 --> 00:29:47.110 align:start position:0% the same name as something that's already<00:29:45.559> in<00:29:45.640> the<00:29:45.760> jbm<00:29:46.360> already<00:29:46.559> in<00:29:46.679> the<00:29:46.799> class 00:29:47.110 --> 00:29:47.120 align:start position:0% already in the jbm already in the class 00:29:47.120 --> 00:29:52.149 align:start position:0% already in the jbm already in the class path<00:29:47.960> you<00:29:48.159> have<00:29:48.720> problem<00:29:50.039> so<00:29:51.039> uh<00:29:51.760> what<00:29:51.840> you<00:29:51.960> do 00:29:52.149 --> 00:29:52.159 align:start position:0% path you have problem so uh what you do 00:29:52.159 --> 00:29:54.590 align:start position:0% path you have problem so uh what you do is<00:29:52.279> he<00:29:52.440> creates<00:29:53.039> pods<00:29:53.640> which<00:29:53.760> are<00:29:54.120> isolated 00:29:54.590 --> 00:29:54.600 align:start position:0% is he creates pods which are isolated 00:29:54.600 --> 00:29:56.549 align:start position:0% is he creates pods which are isolated run<00:29:54.840> times<00:29:55.640> which<00:29:55.799> can<00:29:55.960> have<00:29:56.120> their<00:29:56.240> own<00:29:56.440> set 00:29:56.549 --> 00:29:56.559 align:start position:0% run times which can have their own set 00:29:56.559 --> 00:29:58.310 align:start position:0% run times which can have their own set of<00:29:56.720> dependencies<00:29:57.360> and<00:29:57.480> you<00:29:57.600> can<00:29:57.760> eval<00:29:58.039> valate 00:29:58.310 --> 00:29:58.320 align:start position:0% of dependencies and you can eval valate 00:29:58.320 --> 00:29:59.950 align:start position:0% of dependencies and you can eval valate expressions<00:29:58.799> in<00:29:58.960> there<00:29:59.440> which<00:29:59.519> is<00:29:59.760> really 00:29:59.950 --> 00:29:59.960 align:start position:0% expressions in there which is really 00:29:59.960 --> 00:30:02.389 align:start position:0% expressions in there which is really useful<00:30:00.440> you<00:30:00.559> can<00:30:00.720> even<00:30:01.039> like<00:30:01.799> you<00:30:01.880> know<00:30:02.120> expand 00:30:02.389 --> 00:30:02.399 align:start position:0% useful you can even like you know expand 00:30:02.399 --> 00:30:04.269 align:start position:0% useful you can even like you know expand a<00:30:02.559> macro<00:30:03.039> in<00:30:03.200> there<00:30:03.320> so<00:30:03.440> you<00:30:03.559> have<00:30:03.720> a<00:30:03.880> macro 00:30:04.269 --> 00:30:04.279 align:start position:0% a macro in there so you have a macro 00:30:04.279 --> 00:30:06.870 align:start position:0% a macro in there so you have a macro that<00:30:04.440> has<00:30:04.679> crazy<00:30:05.519> dependencies<00:30:06.120> you<00:30:06.240> could 00:30:06.870 --> 00:30:06.880 align:start position:0% that has crazy dependencies you could 00:30:06.880 --> 00:30:10.029 align:start position:0% that has crazy dependencies you could yeah<00:30:07.600> cool<00:30:08.080> things<00:30:09.080> uh<00:30:09.200> it's<00:30:09.360> easy<00:30:09.559> to<00:30:09.720> create 00:30:10.029 --> 00:30:10.039 align:start position:0% yeah cool things uh it's easy to create 00:30:10.039 --> 00:30:11.789 align:start position:0% yeah cool things uh it's easy to create run<00:30:10.320> code<00:30:10.600> inside<00:30:10.840> of<00:30:10.960> them<00:30:11.159> they're<00:30:11.480> first 00:30:11.789 --> 00:30:11.799 align:start position:0% run code inside of them they're first 00:30:11.799 --> 00:30:13.389 align:start position:0% run code inside of them they're first class<00:30:12.120> you<00:30:12.200> can<00:30:12.320> have<00:30:12.440> a<00:30:12.559> function<00:30:12.960> that 00:30:13.389 --> 00:30:13.399 align:start position:0% class you can have a function that 00:30:13.399 --> 00:30:15.190 align:start position:0% class you can have a function that produces<00:30:13.799> a<00:30:14.000> pod<00:30:14.360> you<00:30:14.440> can<00:30:14.679> have<00:30:14.799> a<00:30:14.919> function 00:30:15.190 --> 00:30:15.200 align:start position:0% produces a pod you can have a function 00:30:15.200 --> 00:30:17.389 align:start position:0% produces a pod you can have a function that<00:30:15.320> takes<00:30:15.640> pods<00:30:16.000> as<00:30:16.360> arguments<00:30:16.799> and<00:30:17.039> returns 00:30:17.389 --> 00:30:17.399 align:start position:0% that takes pods as arguments and returns 00:30:17.399 --> 00:30:19.389 align:start position:0% that takes pods as arguments and returns pods<00:30:18.080> all<00:30:18.279> things<00:30:18.440> you<00:30:18.519> can<00:30:18.640> do<00:30:18.799> with<00:30:18.960> regular 00:30:19.389 --> 00:30:19.399 align:start position:0% pods all things you can do with regular 00:30:19.399 --> 00:30:22.070 align:start position:0% pods all things you can do with regular first<00:30:19.679> class<00:30:19.919> things<00:30:20.080> en<00:30:20.320> closure<00:30:21.320> although 00:30:22.070 --> 00:30:22.080 align:start position:0% first class things en closure although 00:30:22.080 --> 00:30:23.590 align:start position:0% first class things en closure although unfortunately<00:30:22.679> some<00:30:22.880> things<00:30:23.200> can't<00:30:23.399> be 00:30:23.590 --> 00:30:23.600 align:start position:0% unfortunately some things can't be 00:30:23.600 --> 00:30:25.110 align:start position:0% unfortunately some things can't be passed<00:30:23.919> between<00:30:24.279> pods<00:30:24.679> because<00:30:24.840> of<00:30:25.000> the 00:30:25.110 --> 00:30:25.120 align:start position:0% passed between pods because of the 00:30:25.120 --> 00:30:27.990 align:start position:0% passed between pods because of the dynamic<00:30:25.600> nature<00:30:25.840> of<00:30:26.080> closure<00:30:27.080> um<00:30:27.480> each 00:30:27.990 --> 00:30:28.000 align:start position:0% dynamic nature of closure um each 00:30:28.000 --> 00:30:30.070 align:start position:0% dynamic nature of closure um each instance<00:30:28.320> of<00:30:28.480> closure<00:30:28.840> each<00:30:29.000> closure<00:30:29.360> runtime 00:30:30.070 --> 00:30:30.080 align:start position:0% instance of closure each closure runtime 00:30:30.080 --> 00:30:32.190 align:start position:0% instance of closure each closure runtime has<00:30:30.279> dynamically<00:30:30.919> created<00:30:31.440> protocols<00:30:32.000> and 00:30:32.190 --> 00:30:32.200 align:start position:0% has dynamically created protocols and 00:30:32.200 --> 00:30:33.710 align:start position:0% has dynamically created protocols and interfaces<00:30:32.799> and<00:30:32.919> all<00:30:33.120> these<00:30:33.279> things<00:30:33.519> that<00:30:33.640> you 00:30:33.710 --> 00:30:33.720 align:start position:0% interfaces and all these things that you 00:30:33.720 --> 00:30:36.590 align:start position:0% interfaces and all these things that you can<00:30:33.880> mutate<00:30:34.720> inside<00:30:35.080> this<00:30:35.240> runtime<00:30:36.120> so<00:30:36.440> it's 00:30:36.590 --> 00:30:36.600 align:start position:0% can mutate inside this runtime so it's 00:30:36.600 --> 00:30:39.350 align:start position:0% can mutate inside this runtime so it's really<00:30:36.840> not<00:30:37.120> possible<00:30:37.519> to<00:30:38.240> pass<00:30:39.039> things 00:30:39.350 --> 00:30:39.360 align:start position:0% really not possible to pass things 00:30:39.360 --> 00:30:42.509 align:start position:0% really not possible to pass things created<00:30:39.720> by<00:30:39.919> closure<00:30:40.640> to<00:30:40.840> each<00:30:41.159> other<00:30:42.159> but<00:30:42.399> on 00:30:42.509 --> 00:30:42.519 align:start position:0% created by closure to each other but on 00:30:42.519 --> 00:30:44.470 align:start position:0% created by closure to each other but on the<00:30:42.679> other<00:30:42.919> hand<00:30:43.240> closure<00:30:43.679> is<00:30:44.000> really<00:30:44.240> welld 00:30:44.470 --> 00:30:44.480 align:start position:0% the other hand closure is really welld 00:30:44.480 --> 00:30:46.509 align:start position:0% the other hand closure is really welld designed<00:30:44.840> I<00:30:44.919> mean<00:30:45.080> you<00:30:45.279> you<00:30:45.440> you<00:30:45.519> can<00:30:45.799> print 00:30:46.509 --> 00:30:46.519 align:start position:0% designed I mean you you you can print 00:30:46.519 --> 00:30:48.310 align:start position:0% designed I mean you you you can print just<00:30:46.679> about<00:30:47.000> everything<00:30:47.440> that's<00:30:47.679> useful<00:30:48.200> all 00:30:48.310 --> 00:30:48.320 align:start position:0% just about everything that's useful all 00:30:48.320 --> 00:30:49.630 align:start position:0% just about everything that's useful all the<00:30:48.519> data<00:30:48.840> that<00:30:49.000> you<00:30:49.240> that<00:30:49.320> you're<00:30:49.440> going<00:30:49.519> to 00:30:49.630 --> 00:30:49.640 align:start position:0% the data that you that you're going to 00:30:49.640 --> 00:30:52.190 align:start position:0% the data that you that you're going to need<00:30:49.880> you<00:30:50.000> can<00:30:50.600> read<00:30:50.799> it<00:30:50.919> and<00:30:51.080> print<00:30:51.320> it<00:30:52.039> or 00:30:52.190 --> 00:30:52.200 align:start position:0% need you can read it and print it or 00:30:52.200 --> 00:30:54.190 align:start position:0% need you can read it and print it or make<00:30:52.320> a<00:30:52.480> tag<00:30:52.720> literal<00:30:53.240> and<00:30:53.480> that's<00:30:53.799> just<00:30:54.000> fine 00:30:54.190 --> 00:30:54.200 align:start position:0% make a tag literal and that's just fine 00:30:54.200 --> 00:31:00.149 align:start position:0% make a tag literal and that's just fine you<00:30:54.279> can<00:30:54.440> pass<00:30:54.679> strings<00:30:55.279> no<00:30:55.559> problem 00:31:00.149 --> 00:31:00.159 align:start position:0% 00:31:00.159 --> 00:31:01.629 align:start position:0% so<00:31:00.440> like<00:31:00.600> anything<00:31:00.919> in<00:31:01.080> boot<00:31:01.360> you<00:31:01.440> can 00:31:01.629 --> 00:31:01.639 align:start position:0% so like anything in boot you can 00:31:01.639 --> 00:31:04.269 align:start position:0% so like anything in boot you can experiment<00:31:02.039> with<00:31:02.200> pods<00:31:02.519> or<00:31:02.679> any<00:31:02.799> of<00:31:02.919> the<00:31:03.159> boot 00:31:04.269 --> 00:31:04.279 align:start position:0% experiment with pods or any of the boot 00:31:04.279 --> 00:31:07.110 align:start position:0% experiment with pods or any of the boot API<00:31:05.279> and<00:31:05.679> Nisha<00:31:06.080> said<00:31:06.279> that<00:31:06.519> pods<00:31:06.760> are<00:31:06.880> first 00:31:07.110 --> 00:31:07.120 align:start position:0% API and Nisha said that pods are first 00:31:07.120 --> 00:31:08.549 align:start position:0% API and Nisha said that pods are first class<00:31:07.360> we<00:31:07.440> have<00:31:07.679> Constructors<00:31:08.120> for<00:31:08.279> them<00:31:08.440> and 00:31:08.549 --> 00:31:08.559 align:start position:0% class we have Constructors for them and 00:31:08.559 --> 00:31:12.149 align:start position:0% class we have Constructors for them and we<00:31:08.679> do<00:31:09.000> create<00:31:09.480> a<00:31:09.679> pod<00:31:10.679> value<00:31:11.679> and<00:31:11.880> it's<00:31:12.039> kind 00:31:12.149 --> 00:31:12.159 align:start position:0% we do create a pod value and it's kind 00:31:12.159 --> 00:31:13.389 align:start position:0% we do create a pod value and it's kind of<00:31:12.320> like<00:31:12.480> a<00:31:12.559> we'<00:31:12.720> come<00:31:12.840> to<00:31:12.919> think<00:31:13.039> of<00:31:13.159> them<00:31:13.279> as 00:31:13.389 --> 00:31:13.399 align:start position:0% of like a we' come to think of them as 00:31:13.399 --> 00:31:14.549 align:start position:0% of like a we' come to think of them as kind<00:31:13.480> of<00:31:13.600> like<00:31:13.720> little<00:31:13.960> containers<00:31:14.360> little 00:31:14.549 --> 00:31:14.559 align:start position:0% kind of like little containers little 00:31:14.559 --> 00:31:16.230 align:start position:0% kind of like little containers little Docker<00:31:14.840> containers<00:31:15.279> on<00:31:15.760> CU<00:31:15.919> they're<00:31:16.120> like 00:31:16.230 --> 00:31:16.240 align:start position:0% Docker containers on CU they're like 00:31:16.240 --> 00:31:17.830 align:start position:0% Docker containers on CU they're like little<00:31:16.440> VMS<00:31:16.840> that<00:31:16.960> you<00:31:17.000> can<00:31:17.159> run<00:31:17.399> arbitrary 00:31:17.830 --> 00:31:17.840 align:start position:0% little VMS that you can run arbitrary 00:31:17.840 --> 00:31:20.629 align:start position:0% little VMS that you can run arbitrary closure<00:31:18.159> inside<00:31:18.480> of<00:31:19.279> and<00:31:19.440> that<00:31:19.600> closure<00:31:20.480> will 00:31:20.629 --> 00:31:20.639 align:start position:0% closure inside of and that closure will 00:31:20.639 --> 00:31:23.950 align:start position:0% closure inside of and that closure will not<00:31:20.840> affect<00:31:21.279> the<00:31:22.240> the<00:31:23.240> the<00:31:23.519> program<00:31:23.799> as<00:31:23.880> the 00:31:23.950 --> 00:31:23.960 align:start position:0% not affect the the the program as the 00:31:23.960 --> 00:31:25.029 align:start position:0% not affect the the the program as the whole<00:31:24.080> it's 00:31:25.029 --> 00:31:25.039 align:start position:0% whole it's 00:31:25.039 --> 00:31:27.590 align:start position:0% whole it's isolated<00:31:26.039> um<00:31:26.399> I<00:31:26.480> think<00:31:26.720> actually<00:31:26.960> recently 00:31:27.590 --> 00:31:27.600 align:start position:0% isolated um I think actually recently 00:31:27.600 --> 00:31:29.830 align:start position:0% isolated um I think actually recently one<00:31:27.960> use<00:31:28.080> of<00:31:28.240> pods<00:31:28.600> in<00:31:28.679> a<00:31:28.880> in<00:31:28.960> a<00:31:29.080> work<00:31:29.320> project 00:31:29.830 --> 00:31:29.840 align:start position:0% one use of pods in a in a work project 00:31:29.840 --> 00:31:32.470 align:start position:0% one use of pods in a in a work project was<00:31:30.760> uh<00:31:30.880> I<00:31:30.960> was<00:31:31.120> calling<00:31:31.399> out<00:31:31.559> to<00:31:31.760> the<00:31:32.240> the 00:31:32.470 --> 00:31:32.480 align:start position:0% was uh I was calling out to the the 00:31:32.480 --> 00:31:35.710 align:start position:0% was uh I was calling out to the the Amazon<00:31:33.480> uh<00:31:33.639> sqs<00:31:34.240> API<00:31:35.240> which<00:31:35.399> required 00:31:35.710 --> 00:31:35.720 align:start position:0% Amazon uh sqs API which required 00:31:35.720 --> 00:31:37.990 align:start position:0% Amazon uh sqs API which required bringing<00:31:36.039> in<00:31:36.240> all<00:31:36.360> of<00:31:36.840> most<00:31:36.960> of<00:31:37.120> Amazon's<00:31:37.639> API 00:31:37.990 --> 00:31:38.000 align:start position:0% bringing in all of most of Amazon's API 00:31:38.000 --> 00:31:40.310 align:start position:0% bringing in all of most of Amazon's API or<00:31:38.120> all<00:31:38.200> kinds<00:31:38.360> of<00:31:38.440> other<00:31:38.840> services<00:31:39.840> unrelated 00:31:40.310 --> 00:31:40.320 align:start position:0% or all kinds of other services unrelated 00:31:40.320 --> 00:31:43.549 align:start position:0% or all kinds of other services unrelated to<00:31:41.039> sqf<00:31:42.039> and<00:31:42.279> also<00:31:42.639> in<00:31:42.720> that<00:31:42.919> pro<00:31:43.200> project<00:31:43.440> I 00:31:43.549 --> 00:31:43.559 align:start position:0% to sqf and also in that pro project I 00:31:43.559 --> 00:31:45.509 align:start position:0% to sqf and also in that pro project I was<00:31:43.679> using<00:31:44.120> different<00:31:44.760> versions<00:31:45.120> of<00:31:45.279> the 00:31:45.509 --> 00:31:45.519 align:start position:0% was using different versions of the 00:31:45.519 --> 00:31:47.629 align:start position:0% was using different versions of the Amazon<00:31:46.200> API<00:31:46.639> MBR<00:31:47.039> you<00:31:47.120> know<00:31:47.240> all<00:31:47.320> these<00:31:47.440> things 00:31:47.629 --> 00:31:47.639 align:start position:0% Amazon API MBR you know all these things 00:31:47.639 --> 00:31:49.310 align:start position:0% Amazon API MBR you know all these things bring<00:31:47.840> in<00:31:48.080> multiple<00:31:48.399> logging<00:31:48.760> libraries<00:31:49.200> and 00:31:49.310 --> 00:31:49.320 align:start position:0% bring in multiple logging libraries and 00:31:49.320 --> 00:31:50.629 align:start position:0% bring in multiple logging libraries and all<00:31:49.440> kinds<00:31:49.600> of<00:31:49.760> things<00:31:49.919> that<00:31:50.039> can<00:31:50.159> really<00:31:50.360> hose 00:31:50.629 --> 00:31:50.639 align:start position:0% all kinds of things that can really hose 00:31:50.639 --> 00:31:53.230 align:start position:0% all kinds of things that can really hose your<00:31:51.320> program<00:31:52.320> so<00:31:52.480> instead<00:31:52.720> of<00:31:52.840> doing<00:31:53.080> these 00:31:53.230 --> 00:31:53.240 align:start position:0% your program so instead of doing these 00:31:53.240 --> 00:31:54.629 align:start position:0% your program so instead of doing these different<00:31:53.440> things<00:31:53.600> in<00:31:53.720> different<00:31:53.919> jbms<00:31:54.480> which 00:31:54.629 --> 00:31:54.639 align:start position:0% different things in different jbms which 00:31:54.639 --> 00:31:57.990 align:start position:0% different things in different jbms which is<00:31:54.960> you<00:31:55.080> know<00:31:55.519> memory<00:31:56.200> uh<00:31:56.720> consumptive<00:31:57.480> and 00:31:57.990 --> 00:31:58.000 align:start position:0% is you know memory uh consumptive and 00:31:58.000 --> 00:31:59.590 align:start position:0% is you know memory uh consumptive and thrown<00:31:58.279> to<00:31:58.440> error<00:31:59.000> just<00:31:59.120> run<00:31:59.320> all<00:31:59.440> these 00:31:59.590 --> 00:31:59.600 align:start position:0% thrown to error just run all these 00:31:59.600 --> 00:32:00.830 align:start position:0% thrown to error just run all these different<00:31:59.760> things<00:31:59.880> in<00:32:00.039> different 00:32:00.830 --> 00:32:00.840 align:start position:0% different things in different 00:32:00.840 --> 00:32:03.269 align:start position:0% different things in different pods<00:32:01.840> so<00:32:02.080> what<00:32:02.200> Misha<00:32:02.440> is<00:32:02.519> doing<00:32:02.760> here<00:32:02.880> is<00:32:03.039> he 00:32:03.269 --> 00:32:03.279 align:start position:0% pods so what Misha is doing here is he 00:32:03.279 --> 00:32:06.509 align:start position:0% pods so what Misha is doing here is he defined<00:32:03.600> a<00:32:03.799> pod<00:32:04.200> called<00:32:05.080> pod<00:32:06.039> and<00:32:06.120> in<00:32:06.200> the<00:32:06.320> boot 00:32:06.509 --> 00:32:06.519 align:start position:0% defined a pod called pod and in the boot 00:32:06.519 --> 00:32:08.070 align:start position:0% defined a pod called pod and in the boot dop<00:32:06.880> name<00:32:07.080> space<00:32:07.279> there's<00:32:07.440> a<00:32:07.600> constructure 00:32:08.070 --> 00:32:08.080 align:start position:0% dop name space there's a constructure 00:32:08.080 --> 00:32:10.710 align:start position:0% dop name space there's a constructure made<00:32:08.399> pod<00:32:09.200> the<00:32:09.360> Pod<00:32:09.519> takes<00:32:09.720> an<00:32:09.880> environment 00:32:10.710 --> 00:32:10.720 align:start position:0% made pod the Pod takes an environment 00:32:10.720 --> 00:32:12.389 align:start position:0% made pod the Pod takes an environment which<00:32:11.000> is<00:32:11.240> a<00:32:11.440> map<00:32:11.760> describing<00:32:12.240> the 00:32:12.389 --> 00:32:12.399 align:start position:0% which is a map describing the 00:32:12.399 --> 00:32:14.750 align:start position:0% which is a map describing the environment<00:32:12.960> that<00:32:13.200> pod<00:32:13.440> should<00:32:14.240> start<00:32:14.519> up 00:32:14.750 --> 00:32:14.760 align:start position:0% environment that pod should start up 00:32:14.760 --> 00:32:16.629 align:start position:0% environment that pod should start up with<00:32:15.240> it's<00:32:15.399> kind<00:32:15.519> of<00:32:15.639> like<00:32:15.760> a<00:32:15.880> Docker<00:32:16.200> file<00:32:16.399> for 00:32:16.629 --> 00:32:16.639 align:start position:0% with it's kind of like a Docker file for 00:32:16.639 --> 00:32:19.710 align:start position:0% with it's kind of like a Docker file for pods<00:32:17.360> you're<00:32:17.840> familiar<00:32:18.840> now<00:32:18.960> what<00:32:19.080> he<00:32:19.360> did<00:32:19.559> is 00:32:19.710 --> 00:32:19.720 align:start position:0% pods you're familiar now what he did is 00:32:19.720 --> 00:32:22.310 align:start position:0% pods you're familiar now what he did is in<00:32:19.880> this<00:32:20.080> pod<00:32:20.480> there's<00:32:21.080> closure<00:32:21.880> 51<00:32:22.200> was 00:32:22.310 --> 00:32:22.320 align:start position:0% in this pod there's closure 51 was 00:32:22.320 --> 00:32:24.269 align:start position:0% in this pod there's closure 51 was brought<00:32:22.519> in<00:32:23.080> kind<00:32:23.200> of<00:32:23.440> you<00:32:23.559> know<00:32:23.760> retro 00:32:24.269 --> 00:32:24.279 align:start position:0% brought in kind of you know retro 00:32:24.279 --> 00:32:27.310 align:start position:0% brought in kind of you know retro closure<00:32:24.919> version<00:32:25.799> uh<00:32:26.760> a<00:32:26.880> lot<00:32:26.960> of<00:32:27.039> cool<00:32:27.159> things 00:32:27.310 --> 00:32:27.320 align:start position:0% closure version uh a lot of cool things 00:32:27.320 --> 00:32:29.470 align:start position:0% closure version uh a lot of cool things in<00:32:27.440> closure<00:32:27.679> one<00:32:28.000> 51<00:32:28.399> but<00:32:28.600> we<00:32:28.760> certainly<00:32:29.360> don't 00:32:29.470 --> 00:32:29.480 align:start position:0% in closure one 51 but we certainly don't 00:32:29.480 --> 00:32:31.230 align:start position:0% in closure one 51 but we certainly don't want<00:32:29.600> to<00:32:29.679> use<00:32:29.799> it<00:32:29.960> anymore<00:32:30.760> but<00:32:30.919> maybe<00:32:31.080> we're 00:32:31.230 --> 00:32:31.240 align:start position:0% want to use it anymore but maybe we're 00:32:31.240 --> 00:32:32.950 align:start position:0% want to use it anymore but maybe we're using<00:32:31.480> some<00:32:31.679> library<00:32:32.120> that<00:32:32.279> requires 00:32:32.950 --> 00:32:32.960 align:start position:0% using some library that requires 00:32:32.960 --> 00:32:34.789 align:start position:0% using some library that requires something<00:32:33.240> in<00:32:33.519> closure1<00:32:34.519> again<00:32:34.679> that 00:32:34.789 --> 00:32:34.799 align:start position:0% something in closure1 again that 00:32:34.799 --> 00:32:35.870 align:start position:0% something in closure1 again that probably<00:32:35.000> will<00:32:35.120> never<00:32:35.279> happen<00:32:35.440> in<00:32:35.559> closure 00:32:35.870 --> 00:32:35.880 align:start position:0% probably will never happen in closure 00:32:35.880 --> 00:32:38.950 align:start position:0% probably will never happen in closure but<00:32:36.000> who<00:32:36.279> knows<00:32:37.279> um<00:32:38.080> in<00:32:38.240> there<00:32:38.440> he<00:32:38.559> ran<00:32:38.840> the 00:32:38.950 --> 00:32:38.960 align:start position:0% but who knows um in there he ran the 00:32:38.960 --> 00:32:40.549 align:start position:0% but who knows um in there he ran the expression<00:32:39.320> closure<00:32:39.679> Dash<00:32:39.919> version<00:32:40.360> which<00:32:40.440> is 00:32:40.549 --> 00:32:40.559 align:start position:0% expression closure Dash version which is 00:32:40.559 --> 00:32:42.029 align:start position:0% expression closure Dash version which is a<00:32:40.760> a<00:32:40.840> function<00:32:41.159> call<00:32:41.440> that<00:32:41.559> prints<00:32:41.799> out<00:32:41.919> the 00:32:42.029 --> 00:32:42.039 align:start position:0% a a function call that prints out the 00:32:42.039 --> 00:32:44.750 align:start position:0% a a function call that prints out the version<00:32:42.960> then<00:32:43.200> he<00:32:43.519> back<00:32:43.760> in<00:32:43.960> the<00:32:44.120> parent 00:32:44.750 --> 00:32:44.760 align:start position:0% version then he back in the parent 00:32:44.760 --> 00:32:46.669 align:start position:0% version then he back in the parent environment<00:32:45.279> which<00:32:45.399> is<00:32:45.519> the<00:32:45.600> reppel<00:32:46.320> he<00:32:46.440> ran 00:32:46.669 --> 00:32:46.679 align:start position:0% environment which is the reppel he ran 00:32:46.679 --> 00:32:49.029 align:start position:0% environment which is the reppel he ran closure<00:32:47.039> version<00:32:47.840> uh<00:32:48.240> and<00:32:48.639> you<00:32:48.720> know<00:32:48.840> we<00:32:48.960> can 00:32:49.029 --> 00:32:49.039 align:start position:0% closure version uh and you know we can 00:32:49.039 --> 00:32:51.149 align:start position:0% closure version uh and you know we can see<00:32:49.240> that<00:32:49.440> we're<00:32:49.600> in<00:32:49.760> closure<00:32:50.039> one<00:32:50.440> so<00:32:50.760> at<00:32:50.880> the 00:32:51.149 --> 00:32:51.159 align:start position:0% see that we're in closure one so at the 00:32:51.159 --> 00:32:54.389 align:start position:0% see that we're in closure one so at the top 00:32:54.389 --> 00:32:54.399 align:start position:0% 00:32:54.399 --> 00:32:59.389 align:start position:0% level<00:32:55.399> pause<00:32:56.080> sweet 00:32:59.389 --> 00:32:59.399 align:start position:0% 00:32:59.399 --> 00:33:02.669 align:start position:0% you<00:32:59.880> some<00:33:00.760> sure<00:33:01.760> um<00:33:01.880> so<00:33:02.039> here<00:33:02.159> we<00:33:02.279> do<00:33:02.440> the<00:33:02.519> same 00:33:02.669 --> 00:33:02.679 align:start position:0% you some sure um so here we do the same 00:33:02.679 --> 00:33:06.029 align:start position:0% you some sure um so here we do the same thing<00:33:02.799> that<00:33:02.919> we<00:33:03.039> did<00:33:03.240> before<00:33:04.000> only<00:33:05.039> we're 00:33:06.029 --> 00:33:06.039 align:start position:0% thing that we did before only we're 00:33:06.039 --> 00:33:09.710 align:start position:0% thing that we did before only we're running<00:33:06.600> Allen's<00:33:07.120> awesome<00:33:07.559> code<00:33:08.000> in<00:33:08.159> a<00:33:08.559> pod<00:33:09.559> so 00:33:09.710 --> 00:33:09.720 align:start position:0% running Allen's awesome code in a pod so 00:33:09.720 --> 00:33:10.470 align:start position:0% running Allen's awesome code in a pod so we<00:33:09.799> don't<00:33:09.919> have<00:33:10.000> to<00:33:10.120> deal<00:33:10.279> with<00:33:10.360> the 00:33:10.470 --> 00:33:10.480 align:start position:0% we don't have to deal with the 00:33:10.480 --> 00:33:12.350 align:start position:0% we don't have to deal with the consequences<00:33:11.000> of<00:33:11.120> all<00:33:11.279> those<00:33:11.440> dependencies 00:33:12.350 --> 00:33:12.360 align:start position:0% consequences of all those dependencies 00:33:12.360 --> 00:33:13.509 align:start position:0% consequences of all those dependencies so<00:33:12.519> the<00:33:12.600> first<00:33:12.760> thing<00:33:12.840> we<00:33:12.960> do<00:33:13.080> is<00:33:13.159> we<00:33:13.279> Define 00:33:13.509 --> 00:33:13.519 align:start position:0% so the first thing we do is we Define 00:33:13.519 --> 00:33:14.990 align:start position:0% so the first thing we do is we Define the<00:33:13.679> environment<00:33:14.200> that<00:33:14.320> the<00:33:14.440> Pod<00:33:14.639> is<00:33:14.760> going<00:33:14.840> to 00:33:14.990 --> 00:33:15.000 align:start position:0% the environment that the Pod is going to 00:33:15.000 --> 00:33:17.990 align:start position:0% the environment that the Pod is going to have<00:33:15.240> and<00:33:15.320> so<00:33:15.480> this<00:33:15.639> pod<00:33:15.919> is<00:33:16.399> uh<00:33:16.559> podm<00:33:17.440> there<00:33:17.880> is 00:33:17.990 --> 00:33:18.000 align:start position:0% have and so this pod is uh podm there is 00:33:18.000 --> 00:33:19.909 align:start position:0% have and so this pod is uh podm there is the<00:33:18.159> environment<00:33:18.559> of<00:33:18.720> the<00:33:18.840> parent<00:33:19.240> so<00:33:19.440> this<00:33:19.559> is 00:33:19.909 --> 00:33:19.919 align:start position:0% the environment of the parent so this is 00:33:19.919 --> 00:33:21.350 align:start position:0% the environment of the parent so this is you<00:33:20.039> know<00:33:20.320> our<00:33:20.480> current<00:33:20.760> environment<00:33:21.240> and 00:33:21.350 --> 00:33:21.360 align:start position:0% you know our current environment and 00:33:21.360 --> 00:33:22.629 align:start position:0% you know our current environment and what<00:33:21.440> we<00:33:21.559> want<00:33:21.639> to<00:33:21.799> do<00:33:21.919> is<00:33:22.000> we<00:33:22.399> have<00:33:22.519> the 00:33:22.629 --> 00:33:22.639 align:start position:0% what we want to do is we have the 00:33:22.639 --> 00:33:24.669 align:start position:0% what we want to do is we have the current<00:33:22.919> environment<00:33:23.880> but<00:33:24.120> with<00:33:24.279> different 00:33:24.669 --> 00:33:24.679 align:start position:0% current environment but with different 00:33:24.679 --> 00:33:27.389 align:start position:0% current environment but with different dependencies<00:33:25.679> so<00:33:25.880> we're<00:33:26.039> setting<00:33:26.919> that<00:33:27.159> pod 00:33:27.389 --> 00:33:27.399 align:start position:0% dependencies so we're setting that pod 00:33:27.399 --> 00:33:29.430 align:start position:0% dependencies so we're setting that pod to<00:33:27.519> have<00:33:27.799> a<00:33:27.880> dependency<00:33:28.360> on<00:33:28.639> on<00:33:28.799> Allen's 00:33:29.430 --> 00:33:29.440 align:start position:0% to have a dependency on on Allen's 00:33:29.440 --> 00:33:32.789 align:start position:0% to have a dependency on on Allen's library<00:33:30.440> and<00:33:30.559> then<00:33:30.799> down<00:33:31.399> here<00:33:32.399> uh<00:33:32.559> this<00:33:32.639> is 00:33:32.789 --> 00:33:32.799 align:start position:0% library and then down here uh this is 00:33:32.799 --> 00:33:34.710 align:start position:0% library and then down here uh this is some<00:33:33.279> accumulated<00:33:33.840> state<00:33:34.120> that<00:33:34.200> our<00:33:34.360> task<00:33:34.600> is 00:33:34.710 --> 00:33:34.720 align:start position:0% some accumulated state that our task is 00:33:34.720 --> 00:33:36.149 align:start position:0% some accumulated state that our task is going<00:33:34.840> to<00:33:34.960> have<00:33:35.120> it's<00:33:35.240> going<00:33:35.320> to<00:33:35.519> own<00:33:35.760> its<00:33:35.919> own 00:33:36.149 --> 00:33:36.159 align:start position:0% going to have it's going to own its own 00:33:36.159 --> 00:33:38.430 align:start position:0% going to have it's going to own its own pod<00:33:36.399> and<00:33:36.559> this<00:33:36.720> pod<00:33:36.960> is<00:33:37.639> pretty<00:33:37.880> cool<00:33:38.120> it's<00:33:38.240> a 00:33:38.430 --> 00:33:38.440 align:start position:0% pod and this pod is pretty cool it's a 00:33:38.440 --> 00:33:40.389 align:start position:0% pod and this pod is pretty cool it's a we<00:33:38.519> make<00:33:38.639> an<00:33:38.799> anonymous<00:33:39.279> pod<00:33:39.559> bind<00:33:39.840> it<00:33:40.000> locally 00:33:40.389 --> 00:33:40.399 align:start position:0% we make an anonymous pod bind it locally 00:33:40.399 --> 00:33:42.389 align:start position:0% we make an anonymous pod bind it locally you<00:33:40.480> know<00:33:40.679> lexically<00:33:41.679> which<00:33:41.799> is<00:33:41.960> then<00:33:42.080> in<00:33:42.200> the 00:33:42.389 --> 00:33:42.399 align:start position:0% you know lexically which is then in the 00:33:42.399 --> 00:33:46.269 align:start position:0% you know lexically which is then in the closure<00:33:43.120> of<00:33:43.399> our<00:33:44.399> closure<00:33:44.720> with<00:33:44.799> an<00:33:44.960> S<00:33:45.159> of<00:33:45.320> our 00:33:46.269 --> 00:33:46.279 align:start position:0% closure of our closure with an S of our 00:33:46.279 --> 00:33:49.230 align:start position:0% closure of our closure with an S of our task<00:33:47.279> it's<00:33:47.559> pretty<00:33:48.039> pretty 00:33:49.230 --> 00:33:49.240 align:start position:0% task it's pretty pretty 00:33:49.240 --> 00:33:53.350 align:start position:0% task it's pretty pretty listy<00:33:50.240> um<00:33:51.080> so<00:33:51.360> here<00:33:51.600> we<00:33:52.200> we<00:33:52.360> added<00:33:52.720> a<00:33:53.039> uh<00:33:53.240> a 00:33:53.350 --> 00:33:53.360 align:start position:0% listy um so here we we added a uh a 00:33:53.360 --> 00:33:56.269 align:start position:0% listy um so here we we added a uh a parameter<00:33:54.120> to<00:33:54.279> the<00:33:54.399> upcase<00:33:54.880> files<00:33:55.320> function 00:33:56.269 --> 00:33:56.279 align:start position:0% parameter to the upcase files function 00:33:56.279 --> 00:33:58.909 align:start position:0% parameter to the upcase files function which<00:33:56.679> uses<00:33:57.000> the<00:33:57.240> pod 00:33:58.909 --> 00:33:58.919 align:start position:0% which uses the pod 00:33:58.919 --> 00:34:02.190 align:start position:0% which uses the pod and<00:33:59.039> you're<00:33:59.399> welcome<00:34:00.399> no<00:34:00.639> thank<00:34:00.760> you<00:34:01.559> sorry 00:34:02.190 --> 00:34:02.200 align:start position:0% and you're welcome no thank you sorry 00:34:02.200 --> 00:34:05.029 align:start position:0% and you're welcome no thank you sorry we're<00:34:02.360> not<00:34:02.519> we're<00:34:02.679> done<00:34:02.919> quite 00:34:05.029 --> 00:34:05.039 align:start position:0% we're not we're done quite 00:34:05.039 --> 00:34:08.069 align:start position:0% we're not we're done quite yet<00:34:06.039> uh<00:34:06.240> yeah<00:34:06.360> so<00:34:06.679> at<00:34:06.799> the<00:34:07.039> at<00:34:07.200> the<00:34:07.519> uh<00:34:07.919> at<00:34:08.000> the 00:34:08.069 --> 00:34:08.079 align:start position:0% yet uh yeah so at the at the uh at the 00:34:08.079 --> 00:34:12.750 align:start position:0% yet uh yeah so at the at the uh at the end<00:34:08.320> we<00:34:08.520> we<00:34:08.639> commit<00:34:08.919> it<00:34:09.399> and<00:34:10.399> what<00:34:10.480> did<00:34:10.639> I<00:34:11.240> miss 00:34:12.750 --> 00:34:12.760 align:start position:0% end we we commit it and what did I miss 00:34:12.760 --> 00:34:15.950 align:start position:0% end we we commit it and what did I miss uh<00:34:13.760> I<00:34:13.800> don't<00:34:13.960> know<00:34:14.119> we<00:34:14.200> should<00:34:14.399> run 00:34:15.950 --> 00:34:15.960 align:start position:0% uh I don't know we should run 00:34:15.960 --> 00:34:22.990 align:start position:0% uh I don't know we should run it<00:34:16.960> fair 00:34:22.990 --> 00:34:23.000 align:start position:0% 00:34:23.000 --> 00:34:28.790 align:start position:0% enough<00:34:24.000> uh<00:34:24.960> upcase<00:34:25.960> oh<00:34:26.280> right 00:34:28.790 --> 00:34:28.800 align:start position:0% enough uh upcase oh right 00:34:28.800 --> 00:34:32.230 align:start position:0% enough uh upcase oh right origal<00:34:29.800> I 00:34:32.230 --> 00:34:32.240 align:start position:0% origal I 00:34:32.240 --> 00:34:34.790 align:start position:0% origal I there<00:34:33.240> there<00:34:33.359> we 00:34:34.790 --> 00:34:34.800 align:start position:0% there there we 00:34:34.800 --> 00:34:37.470 align:start position:0% there there we go<00:34:35.800> feel<00:34:36.119> good<00:34:36.280> about<00:34:36.440> this<00:34:36.800> I<00:34:36.879> feel<00:34:37.159> super 00:34:37.470 --> 00:34:37.480 align:start position:0% go feel good about this I feel super 00:34:37.480 --> 00:34:38.389 align:start position:0% go feel good about this I feel super good 00:34:38.389 --> 00:34:38.399 align:start position:0% good 00:34:38.399 --> 00:34:40.589 align:start position:0% good too<00:34:39.399> no 00:34:40.589 --> 00:34:40.599 align:start position:0% too no 00:34:40.599 --> 00:34:42.829 align:start position:0% too no exceptions 00:34:42.829 --> 00:34:42.839 align:start position:0% exceptions 00:34:42.839 --> 00:34:47.430 align:start position:0% exceptions yes 00:34:47.430 --> 00:34:47.440 align:start position:0% 00:34:47.440 --> 00:34:50.669 align:start position:0% yes<00:34:48.440> is<00:34:48.599> not<00:34:48.720> an 00:34:50.669 --> 00:34:50.679 align:start position:0% yes is not an 00:34:50.679 --> 00:34:53.629 align:start position:0% yes is not an option<00:34:51.679> so<00:34:51.879> did<00:34:52.000> the<00:34:52.159> thing<00:34:52.480> but<00:34:52.679> now<00:34:53.320> did<00:34:53.480> the 00:34:53.629 --> 00:34:53.639 align:start position:0% option so did the thing but now did the 00:34:53.639 --> 00:34:55.950 align:start position:0% option so did the thing but now did the Pod<00:34:53.960> help<00:34:54.639> so<00:34:54.800> we<00:34:54.879> can<00:34:55.000> use<00:34:55.159> boot<00:34:55.359> show<00:34:55.639> now<00:34:55.800> to 00:34:55.950 --> 00:34:55.960 align:start position:0% Pod help so we can use boot show now to 00:34:55.960 --> 00:34:58.390 align:start position:0% Pod help so we can use boot show now to look<00:34:56.079> at<00:34:56.440> the<00:34:56.560> dependencies 00:34:58.390 --> 00:34:58.400 align:start position:0% look at the dependencies 00:34:58.400 --> 00:35:04.390 align:start position:0% look at the dependencies and<00:34:59.040> drum<00:34:59.400> roll<00:35:00.200> there's<00:35:00.440> no<00:35:01.040> dependencies 00:35:04.390 --> 00:35:04.400 align:start position:0% 00:35:04.400 --> 00:35:08.390 align:start position:0% [Applause] 00:35:08.390 --> 00:35:08.400 align:start position:0% 00:35:08.400 --> 00:35:11.230 align:start position:0% success<00:35:09.400> so<00:35:10.160> to<00:35:10.280> be<00:35:10.440> clear<00:35:10.680> it's<00:35:10.800> not<00:35:10.920> like<00:35:11.079> our 00:35:11.230 --> 00:35:11.240 align:start position:0% success so to be clear it's not like our 00:35:11.240 --> 00:35:13.190 align:start position:0% success so to be clear it's not like our project<00:35:11.640> has<00:35:11.880> no<00:35:12.119> dependencies<00:35:12.800> it's<00:35:13.000> just 00:35:13.190 --> 00:35:13.200 align:start position:0% project has no dependencies it's just 00:35:13.200 --> 00:35:15.069 align:start position:0% project has no dependencies it's just that<00:35:13.520> those<00:35:13.800> dependencies<00:35:14.320> are<00:35:14.520> isolated<00:35:14.960> to 00:35:15.069 --> 00:35:15.079 align:start position:0% that those dependencies are isolated to 00:35:15.079 --> 00:35:16.990 align:start position:0% that those dependencies are isolated to the<00:35:15.200> places<00:35:15.440> in<00:35:15.599> the<00:35:15.760> build<00:35:16.240> process<00:35:16.720> where<00:35:16.880> we 00:35:16.990 --> 00:35:17.000 align:start position:0% the places in the build process where we 00:35:17.000 --> 00:35:21.910 align:start position:0% the places in the build process where we need<00:35:17.280> them<00:35:18.520> um<00:35:19.520> yeah<00:35:19.640> we've<00:35:19.920> got<00:35:20.920> uh<00:35:21.440> another 00:35:21.910 --> 00:35:21.920 align:start position:0% need them um yeah we've got uh another 00:35:21.920 --> 00:35:23.270 align:start position:0% need them um yeah we've got uh another probably<00:35:22.280> 10<00:35:22.480> minutes<00:35:22.720> so<00:35:22.839> maybe<00:35:22.960> we<00:35:23.040> can<00:35:23.119> show 00:35:23.270 --> 00:35:23.280 align:start position:0% probably 10 minutes so maybe we can show 00:35:23.280 --> 00:35:26.270 align:start position:0% probably 10 minutes so maybe we can show some<00:35:23.480> hop<00:35:23.680> on<00:35:23.839> stuff<00:35:24.000> and<00:35:24.160> get<00:35:24.280> some<00:35:24.480> questions 00:35:26.270 --> 00:35:26.280 align:start position:0% some hop on stuff and get some questions 00:35:26.280 --> 00:35:28.790 align:start position:0% some hop on stuff and get some questions sure<00:35:27.280> yeah<00:35:27.440> you<00:35:27.760> I<00:35:27.880> have 00:35:28.790 --> 00:35:28.800 align:start position:0% sure yeah you I have 00:35:28.800 --> 00:35:31.069 align:start position:0% sure yeah you I have questions<00:35:29.800> definitely<00:35:30.119> ask<00:35:30.359> them<00:35:30.560> so<00:35:30.800> so<00:35:30.960> this 00:35:31.069 --> 00:35:31.079 align:start position:0% questions definitely ask them so so this 00:35:31.079 --> 00:35:32.750 align:start position:0% questions definitely ask them so so this is<00:35:31.200> something<00:35:31.400> that<00:35:31.480> I'm<00:35:31.640> actually<00:35:31.839> doing<00:35:32.160> for 00:35:32.750 --> 00:35:32.760 align:start position:0% is something that I'm actually doing for 00:35:32.760 --> 00:35:35.470 align:start position:0% is something that I'm actually doing for uh<00:35:33.359> hoplon<00:35:33.839> which<00:35:33.920> is<00:35:34.119> a<00:35:34.359> a<00:35:34.520> web<00:35:35.000> framework 00:35:35.470 --> 00:35:35.480 align:start position:0% uh hoplon which is a a web framework 00:35:35.480 --> 00:35:37.750 align:start position:0% uh hoplon which is a a web framework which<00:35:35.680> doesn't<00:35:35.920> use<00:35:36.160> react<00:35:37.119> so<00:35:37.440> I<00:35:37.520> know<00:35:37.640> you're 00:35:37.750 --> 00:35:37.760 align:start position:0% which doesn't use react so I know you're 00:35:37.760 --> 00:35:39.030 align:start position:0% which doesn't use react so I know you're love<00:35:38.000> the<00:35:38.119> sound<00:35:38.280> of<00:35:38.400> this<00:35:38.520> like<00:35:38.680> oh<00:35:38.839> they<00:35:38.920> have 00:35:39.030 --> 00:35:39.040 align:start position:0% love the sound of this like oh they have 00:35:39.040 --> 00:35:41.790 align:start position:0% love the sound of this like oh they have their<00:35:39.119> own<00:35:39.280> bill<00:35:39.480> tool<00:35:40.359> framework<00:35:40.960> oh<00:35:41.640> those 00:35:41.790 --> 00:35:41.800 align:start position:0% their own bill tool framework oh those 00:35:41.800 --> 00:35:43.310 align:start position:0% their own bill tool framework oh those people<00:35:42.160> getting<00:35:42.359> to<00:35:42.480> drink<00:35:42.680> a<00:35:42.760> lot<00:35:42.960> too<00:35:43.160> the 00:35:43.310 --> 00:35:43.320 align:start position:0% people getting to drink a lot too the 00:35:43.320 --> 00:35:46.750 align:start position:0% people getting to drink a lot too the react<00:35:43.960> the<00:35:44.160> react<00:35:44.560> drinking<00:35:45.040> game<00:35:45.760> people 00:35:46.750 --> 00:35:46.760 align:start position:0% react the react drinking game people 00:35:46.760 --> 00:35:49.750 align:start position:0% react the react drinking game people react<00:35:47.520> react 00:35:49.750 --> 00:35:49.760 align:start position:0% react react 00:35:49.760 --> 00:35:52.550 align:start position:0% react react uh<00:35:50.760> so<00:35:50.960> what<00:35:51.079> we<00:35:51.240> have<00:35:51.480> here<00:35:51.880> is<00:35:52.200> uh<00:35:52.359> this<00:35:52.480> is 00:35:52.550 --> 00:35:52.560 align:start position:0% uh so what we have here is uh this is 00:35:52.560 --> 00:35:55.750 align:start position:0% uh so what we have here is uh this is the<00:35:52.680> bill.<00:35:53.119> boot<00:35:53.400> for<00:35:53.680> hoplon<00:35:54.160> doio<00:35:55.160> which<00:35:55.400> I'm 00:35:55.750 --> 00:35:55.760 align:start position:0% the bill. boot for hoplon doio which I'm 00:35:55.760 --> 00:35:58.069 align:start position:0% the bill. boot for hoplon doio which I'm I'm<00:35:56.000> uh<00:35:56.119> doing<00:35:56.359> some<00:35:56.520> work<00:35:56.720> on<00:35:57.359> and<00:35:57.760> uh<00:35:57.880> because 00:35:58.069 --> 00:35:58.079 align:start position:0% I'm uh doing some work on and uh because 00:35:58.079 --> 00:36:01.390 align:start position:0% I'm uh doing some work on and uh because hopl<00:35:58.319> on.<00:35:58.839> it's<00:35:59.000> a<00:35:59.240> um<00:35:59.800> it's<00:35:59.960> a<00:36:00.760> a<00:36:00.960> website<00:36:01.319> with 00:36:01.390 --> 00:36:01.400 align:start position:0% hopl on. it's a um it's a a website with 00:36:01.400 --> 00:36:04.390 align:start position:0% hopl on. it's a um it's a a website with a<00:36:01.480> lot<00:36:01.599> of<00:36:01.800> content<00:36:02.280> in<00:36:02.400> it<00:36:03.280> um<00:36:03.640> and<00:36:04.040> uh<00:36:04.160> so 00:36:04.390 --> 00:36:04.400 align:start position:0% a lot of content in it um and uh so 00:36:04.400 --> 00:36:06.790 align:start position:0% a lot of content in it um and uh so doing<00:36:04.760> content<00:36:05.160> and<00:36:06.079> with<00:36:06.240> hopl<00:36:06.480> on<00:36:06.560> you<00:36:06.680> do 00:36:06.790 --> 00:36:06.800 align:start position:0% doing content and with hopl on you do 00:36:06.800 --> 00:36:10.109 align:start position:0% doing content and with hopl on you do everything<00:36:07.000> in<00:36:07.200> list<00:36:08.400> uh<00:36:09.400> in<00:36:09.560> actual<00:36:09.839> X 00:36:10.109 --> 00:36:10.119 align:start position:0% everything in list uh in actual X 00:36:10.119 --> 00:36:11.790 align:start position:0% everything in list uh in actual X Expressions<00:36:10.520> it's<00:36:10.680> a<00:36:10.920> a<00:36:11.000> list<00:36:11.359> program<00:36:11.640> the 00:36:11.790 --> 00:36:11.800 align:start position:0% Expressions it's a a list program the 00:36:11.800 --> 00:36:13.790 align:start position:0% Expressions it's a a list program the actual<00:36:12.000> markup<00:36:12.359> is<00:36:12.480> a<00:36:12.560> list<00:36:12.880> program<00:36:13.680> and 00:36:13.790 --> 00:36:13.800 align:start position:0% actual markup is a list program and 00:36:13.800 --> 00:36:15.950 align:start position:0% actual markup is a list program and doing<00:36:14.119> content<00:36:14.440> in<00:36:14.680> list<00:36:15.040> in<00:36:15.280> s<00:36:15.520> Expressions 00:36:15.950 --> 00:36:15.960 align:start position:0% doing content in list in s Expressions 00:36:15.960 --> 00:36:16.630 align:start position:0% doing content in list in s Expressions is 00:36:16.630 --> 00:36:16.640 align:start position:0% is 00:36:16.640 --> 00:36:18.470 align:start position:0% is surprisingly 00:36:18.470 --> 00:36:18.480 align:start position:0% surprisingly 00:36:18.480 --> 00:36:22.109 align:start position:0% surprisingly unfun<00:36:19.480> but<00:36:20.160> there's<00:36:20.440> stuff<00:36:20.680> like<00:36:20.880> ham<00:36:21.440> which 00:36:22.109 --> 00:36:22.119 align:start position:0% unfun but there's stuff like ham which 00:36:22.119 --> 00:36:24.349 align:start position:0% unfun but there's stuff like ham which are<00:36:22.359> basically<00:36:22.800> emitting<00:36:23.160> s<00:36:23.440> Expressions<00:36:24.240> but 00:36:24.349 --> 00:36:24.359 align:start position:0% are basically emitting s Expressions but 00:36:24.359 --> 00:36:25.670 align:start position:0% are basically emitting s Expressions but they<00:36:24.480> do<00:36:24.599> it<00:36:24.720> without<00:36:24.920> the<00:36:25.040> punctuation<00:36:25.560> so 00:36:25.670 --> 00:36:25.680 align:start position:0% they do it without the punctuation so 00:36:25.680 --> 00:36:26.829 align:start position:0% they do it without the punctuation so that<00:36:25.760> means<00:36:25.920> you<00:36:26.000> don't<00:36:26.160> need<00:36:26.280> to<00:36:26.480> escape 00:36:26.829 --> 00:36:26.839 align:start position:0% that means you don't need to escape 00:36:26.839 --> 00:36:28.990 align:start position:0% that means you don't need to escape anything<00:36:27.359> but<00:36:27.599> you<00:36:27.680> do<00:36:27.760> have<00:36:27.880> to<00:36:27.960> endb<00:36:28.400> things 00:36:28.990 --> 00:36:29.000 align:start position:0% anything but you do have to endb things 00:36:29.000 --> 00:36:31.150 align:start position:0% anything but you do have to endb things right<00:36:29.520> and<00:36:29.680> so<00:36:29.960> I<00:36:30.079> wanted<00:36:30.319> to<00:36:30.720> incorporate 00:36:31.150 --> 00:36:31.160 align:start position:0% right and so I wanted to incorporate 00:36:31.160 --> 00:36:33.190 align:start position:0% right and so I wanted to incorporate haml<00:36:31.560> into<00:36:31.800> my<00:36:32.000> so<00:36:32.119> I<00:36:32.200> wrote<00:36:32.359> a<00:36:32.480> little<00:36:32.640> haml 00:36:33.190 --> 00:36:33.200 align:start position:0% haml into my so I wrote a little haml 00:36:33.200 --> 00:36:36.829 align:start position:0% haml into my so I wrote a little haml task<00:36:34.160> which<00:36:34.480> takes<00:36:34.960> my<00:36:35.160> version<00:36:35.440> of<00:36:35.720> haml<00:36:36.520> and 00:36:36.829 --> 00:36:36.839 align:start position:0% task which takes my version of haml and 00:36:36.839 --> 00:36:39.710 align:start position:0% task which takes my version of haml and emits<00:36:37.400> s<00:36:37.720> expressions<00:36:38.280> from<00:36:38.480> it<00:36:39.440> which 00:36:39.710 --> 00:36:39.720 align:start position:0% emits s expressions from it which 00:36:39.720 --> 00:36:41.510 align:start position:0% emits s expressions from it which becomes<00:36:40.040> a<00:36:40.200> hoplon<00:36:40.599> source<00:36:40.880> file<00:36:41.280> you<00:36:41.359> should 00:36:41.510 --> 00:36:41.520 align:start position:0% becomes a hoplon source file you should 00:36:41.520 --> 00:36:43.750 align:start position:0% becomes a hoplon source file you should show<00:36:41.760> some<00:36:41.880> of<00:36:42.040> the<00:36:42.240> some<00:36:42.359> of<00:36:42.480> the<00:36:42.599> source<00:36:43.400> okay 00:36:43.750 --> 00:36:43.760 align:start position:0% show some of the some of the source okay 00:36:43.760 --> 00:36:46.829 align:start position:0% show some of the some of the source okay sufficiently<00:36:44.200> mindblowing<00:36:44.760> I<00:36:44.839> think<00:36:44.960> it 00:36:46.829 --> 00:36:46.839 align:start position:0% sufficiently mindblowing I think it 00:36:46.839 --> 00:36:52.829 align:start position:0% sufficiently mindblowing I think it like<00:36:47.839> I<00:36:47.880> mean<00:36:48.040> not<00:36:48.200> to<00:36:48.839> overstate<00:36:49.359> it<00:36:50.040> yeah 00:36:52.829 --> 00:36:52.839 align:start position:0% like I mean not to overstate it yeah 00:36:52.839 --> 00:36:58.030 align:start position:0% like I mean not to overstate it yeah I<00:36:53.839> I<00:36:54.839> yeah 00:36:58.030 --> 00:36:58.040 align:start position:0% 00:36:58.040 --> 00:37:01.790 align:start position:0% content<00:36:59.040> start<00:37:00.040> yeah<00:37:00.920> that's<00:37:01.119> the<00:37:01.359> one<00:37:01.640> so 00:37:01.790 --> 00:37:01.800 align:start position:0% content start yeah that's the one so 00:37:01.800 --> 00:37:03.670 align:start position:0% content start yeah that's the one so this<00:37:02.040> this<00:37:02.119> is<00:37:02.200> a<00:37:02.359> pretty<00:37:02.520> sweet<00:37:02.839> file<00:37:03.599> make 00:37:03.670 --> 00:37:03.680 align:start position:0% this this is a pretty sweet file make 00:37:03.680 --> 00:37:06.870 align:start position:0% this this is a pretty sweet file make you<00:37:03.839> take<00:37:03.960> it<00:37:04.240> away<00:37:05.240> yeah<00:37:05.400> so<00:37:05.599> here's<00:37:05.880> a 00:37:06.870 --> 00:37:06.880 align:start position:0% you take it away yeah so here's a 00:37:06.880 --> 00:37:10.870 align:start position:0% you take it away yeah so here's a Hames<00:37:07.880> thing<00:37:08.280> where<00:37:08.720> you<00:37:08.880> know<00:37:09.560> these<00:37:10.040> uh<00:37:10.720> the 00:37:10.870 --> 00:37:10.880 align:start position:0% Hames thing where you know these uh the 00:37:10.880 --> 00:37:12.630 align:start position:0% Hames thing where you know these uh the percent<00:37:11.200> means<00:37:11.480> make<00:37:11.640> an<00:37:11.800> S<00:37:12.040> expression<00:37:12.440> with 00:37:12.630 --> 00:37:12.640 align:start position:0% percent means make an S expression with 00:37:12.640 --> 00:37:15.550 align:start position:0% percent means make an S expression with this<00:37:12.800> thing<00:37:13.040> as<00:37:13.319> the<00:37:13.839> car<00:37:14.359> the<00:37:14.560> head<00:37:14.880> the 00:37:15.550 --> 00:37:15.560 align:start position:0% this thing as the car the head the 00:37:15.560 --> 00:37:18.030 align:start position:0% this thing as the car the head the operation<00:37:16.560> and<00:37:16.680> so<00:37:16.839> there's<00:37:16.960> a<00:37:17.079> clj<00:37:17.599> macro 00:37:18.030 --> 00:37:18.040 align:start position:0% operation and so there's a clj macro 00:37:18.040 --> 00:37:19.230 align:start position:0% operation and so there's a clj macro this<00:37:18.160> is<00:37:18.319> actually<00:37:18.480> a<00:37:18.599> macro<00:37:18.880> that's<00:37:19.040> getting 00:37:19.230 --> 00:37:19.240 align:start position:0% this is actually a macro that's getting 00:37:19.240 --> 00:37:21.790 align:start position:0% this is actually a macro that's getting called<00:37:20.200> which<00:37:20.440> incorporates<00:37:21.079> all<00:37:21.280> this<00:37:21.440> stuff 00:37:21.790 --> 00:37:21.800 align:start position:0% called which incorporates all this stuff 00:37:21.800 --> 00:37:26.910 align:start position:0% called which incorporates all this stuff which<00:37:21.920> is<00:37:22.119> text<00:37:22.560> to<00:37:22.760> the<00:37:22.920> haml<00:37:24.200> editor<00:37:25.640> as<00:37:26.640> uh 00:37:26.910 --> 00:37:26.920 align:start position:0% which is text to the haml editor as uh 00:37:26.920 --> 00:37:29.069 align:start position:0% which is text to the haml editor as uh it<00:37:27.079> splies<00:37:27.760> these<00:37:28.040> Expressions<00:37:28.560> into<00:37:28.920> the 00:37:29.069 --> 00:37:29.079 align:start position:0% it splies these Expressions into the 00:37:29.079 --> 00:37:30.550 align:start position:0% it splies these Expressions into the final<00:37:29.440> product<00:37:29.960> Oh<00:37:30.040> and<00:37:30.160> actually<00:37:30.359> we're<00:37:30.480> out 00:37:30.550 --> 00:37:30.560 align:start position:0% final product Oh and actually we're out 00:37:30.560 --> 00:37:32.349 align:start position:0% final product Oh and actually we're out of<00:37:30.720> time 00:37:32.349 --> 00:37:32.359 align:start position:0% of time 00:37:32.359 --> 00:37:35.309 align:start position:0% of time so<00:37:33.359> go<00:37:33.440> down<00:37:33.560> to<00:37:33.720> the<00:37:34.079> part<00:37:34.680> the<00:37:34.760> point<00:37:35.000> here<00:37:35.160> is 00:37:35.309 --> 00:37:35.319 align:start position:0% so go down to the part the point here is 00:37:35.319 --> 00:37:37.470 align:start position:0% so go down to the part the point here is that<00:37:35.800> we<00:37:35.880> were<00:37:36.079> able<00:37:36.359> to<00:37:36.720> take<00:37:36.880> our<00:37:37.119> existing 00:37:37.470 --> 00:37:37.480 align:start position:0% that we were able to take our existing 00:37:37.480 --> 00:37:39.950 align:start position:0% that we were able to take our existing workflow<00:37:38.079> and<00:37:38.200> shim<00:37:38.560> in<00:37:38.839> a<00:37:39.000> thing<00:37:39.280> that<00:37:39.640> takes 00:37:39.950 --> 00:37:39.960 align:start position:0% workflow and shim in a thing that takes 00:37:39.960 --> 00:37:41.990 align:start position:0% workflow and shim in a thing that takes haml<00:37:40.359> and<00:37:41.040> you<00:37:41.160> know<00:37:41.359> basically<00:37:41.720> we're<00:37:41.880> we're 00:37:41.990 --> 00:37:42.000 align:start position:0% haml and you know basically we're we're 00:37:42.000 --> 00:37:44.750 align:start position:0% haml and you know basically we're we're doing<00:37:42.200> a<00:37:42.319> multipass<00:37:43.119> build<00:37:43.839> where<00:37:44.040> each<00:37:44.359> pass 00:37:44.750 --> 00:37:44.760 align:start position:0% doing a multipass build where each pass 00:37:44.760 --> 00:37:46.270 align:start position:0% doing a multipass build where each pass is<00:37:44.920> totally<00:37:45.280> independent<00:37:45.720> from<00:37:45.880> the<00:37:45.960> others 00:37:46.270 --> 00:37:46.280 align:start position:0% is totally independent from the others 00:37:46.280 --> 00:37:48.630 align:start position:0% is totally independent from the others so<00:37:46.480> I<00:37:46.520> can<00:37:47.040> haml<00:37:47.480> use<00:37:47.720> haml<00:37:48.079> and<00:37:48.280> I<00:37:48.359> can<00:37:48.480> take 00:37:48.630 --> 00:37:48.640 align:start position:0% so I can haml use haml and I can take 00:37:48.640 --> 00:37:50.710 align:start position:0% so I can haml use haml and I can take haml<00:37:49.000> out<00:37:49.280> and<00:37:49.640> the<00:37:49.760> rest<00:37:49.880> of<00:37:50.000> my<00:37:50.160> build<00:37:50.440> won't 00:37:50.710 --> 00:37:50.720 align:start position:0% haml out and the rest of my build won't 00:37:50.720 --> 00:37:52.829 align:start position:0% haml out and the rest of my build won't won't<00:37:50.960> change<00:37:51.480> and<00:37:51.640> actually<00:37:52.119> we're<00:37:52.319> using 00:37:52.829 --> 00:37:52.839 align:start position:0% won't change and actually we're using 00:37:52.839 --> 00:37:55.510 align:start position:0% won't change and actually we're using you<00:37:52.920> can<00:37:53.040> see<00:37:53.200> it<00:37:53.319> on<00:37:53.520> l947<00:37:54.520> it's<00:37:54.720> marked<00:37:55.040> down 00:37:55.510 --> 00:37:55.520 align:start position:0% you can see it on l947 it's marked down 00:37:55.520 --> 00:37:58.190 align:start position:0% you can see it on l947 it's marked down inside<00:37:55.800> of<00:37:56.040> haml<00:37:56.800> inside<00:37:57.040> of<00:37:57.920> that<00:37:58.040> gets 00:37:58.190 --> 00:37:58.200 align:start position:0% inside of haml inside of that gets 00:37:58.200 --> 00:37:59.589 align:start position:0% inside of haml inside of that gets converted<00:37:58.520> to<00:37:58.640> closure<00:37:58.960> script<00:37:59.280> which<00:37:59.400> gets 00:37:59.589 --> 00:37:59.599 align:start position:0% converted to closure script which gets 00:37:59.599 --> 00:38:01.510 align:start position:0% converted to closure script which gets converted<00:37:59.920> to<00:38:00.200> JavaScript<00:38:01.200> which<00:38:01.319> you<00:38:01.400> know 00:38:01.510 --> 00:38:01.520 align:start position:0% converted to JavaScript which you know 00:38:01.520 --> 00:38:03.670 align:start position:0% converted to JavaScript which you know runs<00:38:01.720> in<00:38:01.800> your<00:38:01.920> browser<00:38:02.520> yeah<00:38:02.640> MD<00:38:03.000> is<00:38:03.240> actually 00:38:03.670 --> 00:38:03.680 align:start position:0% runs in your browser yeah MD is actually 00:38:03.680 --> 00:38:04.589 align:start position:0% runs in your browser yeah MD is actually a 00:38:04.589 --> 00:38:04.599 align:start position:0% a 00:38:04.599 --> 00:38:08.069 align:start position:0% a macro<00:38:05.599> MD<00:38:05.920> is<00:38:06.040> a<00:38:06.160> macro<00:38:06.680> which<00:38:06.880> compiles<00:38:07.599> down 00:38:08.069 --> 00:38:08.079 align:start position:0% macro MD is a macro which compiles down 00:38:08.079 --> 00:38:10.550 align:start position:0% macro MD is a macro which compiles down to<00:38:08.520> an<00:38:08.720> a<00:38:09.400> which<00:38:09.520> is<00:38:09.760> basically<00:38:10.119> closure 00:38:10.550 --> 00:38:10.560 align:start position:0% to an a which is basically closure 00:38:10.560 --> 00:38:13.950 align:start position:0% to an a which is basically closure script<00:38:10.960> s<00:38:11.520> expressions<00:38:12.520> and<00:38:13.160> it's<00:38:13.319> a<00:38:13.560> syntax 00:38:13.950 --> 00:38:13.960 align:start position:0% script s expressions and it's a syntax 00:38:13.960 --> 00:38:17.750 align:start position:0% script s expressions and it's a syntax highlighting<00:38:14.440> using<00:38:15.400> um<00:38:16.119> using<00:38:16.760> uh<00:38:17.079> pigments 00:38:17.750 --> 00:38:17.760 align:start position:0% highlighting using um using uh pigments 00:38:17.760 --> 00:38:20.109 align:start position:0% highlighting using um using uh pigments in<00:38:17.960> J<00:38:18.359> python<00:38:18.920> in<00:38:19.040> a 00:38:20.109 --> 00:38:20.119 align:start position:0% in J python in a 00:38:20.119 --> 00:38:26.090 align:start position:0% in J python in a pod<00:38:21.119> in<00:38:21.200> a<00:38:21.319> pod 00:38:26.090 --> 00:38:26.100 align:start position:0% 00:38:26.100 --> 00:38:28.520 align:start position:0% [Applause]