WEBVTT Kind: captions Language: en 00:00:00.160 --> 00:00:03.510 align:start position:0% hi<00:00:00.560> and<00:00:00.719> welcome<00:00:01.120> everyone<00:00:01.920> such<00:00:02.240> a<00:00:02.320> fantastic 00:00:03.510 --> 00:00:03.520 align:start position:0% hi and welcome everyone such a fantastic 00:00:03.520 --> 00:00:07.030 align:start position:0% hi and welcome everyone such a fantastic uh<00:00:03.919> way<00:00:04.080> to<00:00:04.240> start<00:00:04.640> our<00:00:05.120> work<00:00:06.000> um 00:00:07.030 --> 00:00:07.040 align:start position:0% uh way to start our work um 00:00:07.040 --> 00:00:10.070 align:start position:0% uh way to start our work um we<00:00:08.240> we're<00:00:08.400> gonna<00:00:09.120> we<00:00:09.280> are<00:00:09.440> we<00:00:09.519> have<00:00:09.679> the 00:00:10.070 --> 00:00:10.080 align:start position:0% we we're gonna we are we have the 00:00:10.080 --> 00:00:12.310 align:start position:0% we we're gonna we are we have the the<00:00:10.240> honor<00:00:10.559> and<00:00:10.639> the<00:00:10.719> pleasure<00:00:11.120> to<00:00:11.280> host<00:00:11.759> uh 00:00:12.310 --> 00:00:12.320 align:start position:0% the honor and the pleasure to host uh 00:00:12.320 --> 00:00:13.509 align:start position:0% the honor and the pleasure to host uh alan<00:00:12.719> deeper 00:00:13.509 --> 00:00:13.519 align:start position:0% alan deeper 00:00:13.519 --> 00:00:16.870 align:start position:0% alan deeper diapered<00:00:14.559> excuse<00:00:14.960> me<00:00:15.360> alan<00:00:15.759> diaper<00:00:16.400> and 00:00:16.870 --> 00:00:16.880 align:start position:0% diapered excuse me alan diaper and 00:00:16.880 --> 00:00:19.910 align:start position:0% diapered excuse me alan diaper and um<00:00:18.800> everyone<00:00:19.279> asked 00:00:19.910 --> 00:00:19.920 align:start position:0% um everyone asked 00:00:19.920 --> 00:00:23.269 align:start position:0% um everyone asked we<00:00:20.160> i<00:00:20.320> mean<00:00:20.720> the<00:00:20.960> psychology<00:00:21.920> community 00:00:23.269 --> 00:00:23.279 align:start position:0% we i mean the psychology community 00:00:23.279 --> 00:00:27.029 align:start position:0% we i mean the psychology community and<00:00:23.840> um 00:00:27.029 --> 00:00:27.039 align:start position:0% 00:00:27.039 --> 00:00:30.310 align:start position:0% my<00:00:27.199> name<00:00:27.439> is<00:00:27.680> danielle<00:00:28.480> uh<00:00:29.679> and 00:00:30.310 --> 00:00:30.320 align:start position:0% my name is danielle uh and 00:00:30.320 --> 00:00:33.110 align:start position:0% my name is danielle uh and and<00:00:30.800> i'm<00:00:31.199> i<00:00:31.359> was<00:00:32.079> asked<00:00:32.320> to<00:00:32.399> moderate<00:00:32.880> this 00:00:33.110 --> 00:00:33.120 align:start position:0% and i'm i was asked to moderate this 00:00:33.120 --> 00:00:34.069 align:start position:0% and i'm i was asked to moderate this talk<00:00:33.440> so 00:00:34.069 --> 00:00:34.079 align:start position:0% talk so 00:00:34.079 --> 00:00:37.270 align:start position:0% talk so i'm<00:00:34.480> so<00:00:34.640> happy<00:00:34.960> to<00:00:35.840> that<00:00:36.079> danielle<00:00:36.480> switzky 00:00:37.270 --> 00:00:37.280 align:start position:0% i'm so happy to that danielle switzky 00:00:37.280 --> 00:00:39.430 align:start position:0% i'm so happy to that danielle switzky reached<00:00:37.600> out<00:00:37.680> to<00:00:37.840> me<00:00:38.160> and<00:00:38.480> that<00:00:38.719> i<00:00:38.800> get<00:00:39.120> to<00:00:39.280> do 00:00:39.430 --> 00:00:39.440 align:start position:0% reached out to me and that i get to do 00:00:39.440 --> 00:00:41.110 align:start position:0% reached out to me and that i get to do that<00:00:39.680> because<00:00:40.079> i<00:00:40.239> know 00:00:41.110 --> 00:00:41.120 align:start position:0% that because i know 00:00:41.120 --> 00:00:44.470 align:start position:0% that because i know alan<00:00:42.480> from<00:00:42.640> way<00:00:42.879> back<00:00:43.040> if<00:00:43.200> i<00:00:43.360> can<00:00:43.440> say<00:00:43.600> that 00:00:44.470 --> 00:00:44.480 align:start position:0% alan from way back if i can say that 00:00:44.480 --> 00:00:48.310 align:start position:0% alan from way back if i can say that uh<00:00:44.879> i<00:00:45.360> remember<00:00:45.680> allen's<00:00:46.079> work<00:00:46.399> uh<00:00:47.200> when 00:00:48.310 --> 00:00:48.320 align:start position:0% uh i remember allen's work uh when 00:00:48.320 --> 00:00:51.750 align:start position:0% uh i remember allen's work uh when uh<00:00:48.960> we<00:00:49.120> were<00:00:49.600> i<00:00:49.760> was<00:00:50.000> doubling<00:00:50.320> in<00:00:50.480> closure<00:00:51.199> and 00:00:51.750 --> 00:00:51.760 align:start position:0% uh we were i was doubling in closure and 00:00:51.760 --> 00:00:55.029 align:start position:0% uh we were i was doubling in closure and he<00:00:51.920> came<00:00:52.160> up<00:00:52.320> with<00:00:52.719> a<00:00:53.039> uh<00:00:53.520> very<00:00:53.760> ambitious 00:00:55.029 --> 00:00:55.039 align:start position:0% he came up with a uh very ambitious 00:00:55.039 --> 00:00:58.950 align:start position:0% he came up with a uh very ambitious front-end<00:00:55.920> framework<00:00:56.480> called<00:00:56.840> hotline 00:00:58.950 --> 00:00:58.960 align:start position:0% front-end framework called hotline 00:00:58.960 --> 00:01:02.470 align:start position:0% front-end framework called hotline and<00:00:59.600> we<00:00:59.760> will<00:00:59.920> see<00:01:01.039> what<00:01:01.280> was<00:01:01.520> impressive 00:01:02.470 --> 00:01:02.480 align:start position:0% and we will see what was impressive 00:01:02.480 --> 00:01:05.830 align:start position:0% and we will see what was impressive about<00:01:02.800> it<00:01:02.960> was<00:01:03.199> that<00:01:03.440> it<00:01:03.840> was<00:01:04.080> based<00:01:04.400> on 00:01:05.830 --> 00:01:05.840 align:start position:0% about it was that it was based on 00:01:05.840 --> 00:01:09.350 align:start position:0% about it was that it was based on a<00:01:06.000> completely<00:01:06.479> different<00:01:08.560> architectural 00:01:09.350 --> 00:01:09.360 align:start position:0% a completely different architectural 00:01:09.360 --> 00:01:12.469 align:start position:0% a completely different architectural principle<00:01:09.840> that<00:01:10.080> we<00:01:10.240> were<00:01:10.479> used<00:01:10.840> to<00:01:11.600> uh 00:01:12.469 --> 00:01:12.479 align:start position:0% principle that we were used to uh 00:01:12.479 --> 00:01:15.590 align:start position:0% principle that we were used to uh so<00:01:13.360> i<00:01:13.840> i<00:01:14.000> don't<00:01:14.159> remember<00:01:14.640> i<00:01:14.720> think<00:01:14.880> it<00:01:15.040> was 00:01:15.590 --> 00:01:15.600 align:start position:0% so i i don't remember i think it was 00:01:15.600 --> 00:01:17.830 align:start position:0% so i i don't remember i think it was the<00:01:15.759> react<00:01:16.159> frameworks<00:01:16.640> were<00:01:17.200> was<00:01:17.439> strong<00:01:17.759> at 00:01:17.830 --> 00:01:17.840 align:start position:0% the react frameworks were was strong at 00:01:17.840 --> 00:01:19.350 align:start position:0% the react frameworks were was strong at the<00:01:18.000> time<00:01:18.159> although<00:01:18.479> maybe<00:01:18.799> it<00:01:18.880> was<00:01:19.119> even 00:01:19.350 --> 00:01:19.360 align:start position:0% the time although maybe it was even 00:01:19.360 --> 00:01:20.710 align:start position:0% the time although maybe it was even before<00:01:19.759> that<00:01:20.080> when 00:01:20.710 --> 00:01:20.720 align:start position:0% before that when 00:01:20.720 --> 00:01:23.270 align:start position:0% before that when when<00:01:20.880> there<00:01:21.040> were<00:01:21.280> other<00:01:21.600> other<00:01:22.000> frameworks 00:01:23.270 --> 00:01:23.280 align:start position:0% when there were other other frameworks 00:01:23.280 --> 00:01:24.630 align:start position:0% when there were other other frameworks javascript<00:01:23.840> frameworks 00:01:24.630 --> 00:01:24.640 align:start position:0% javascript frameworks 00:01:24.640 --> 00:01:28.070 align:start position:0% javascript frameworks um<00:01:25.600> strong<00:01:26.560> but<00:01:26.960> at<00:01:27.360> any<00:01:27.600> case 00:01:28.070 --> 00:01:28.080 align:start position:0% um strong but at any case 00:01:28.080 --> 00:01:31.350 align:start position:0% um strong but at any case the<00:01:28.240> idea<00:01:28.640> of<00:01:28.880> using<00:01:29.600> the<00:01:30.479> the<00:01:30.640> paradigm 00:01:31.350 --> 00:01:31.360 align:start position:0% the idea of using the the paradigm 00:01:31.360 --> 00:01:34.870 align:start position:0% the idea of using the the paradigm of<00:01:32.079> of<00:01:32.240> a<00:01:32.400> spreadsheet<00:01:33.759> and<00:01:34.079> its<00:01:34.320> reactive 00:01:34.870 --> 00:01:34.880 align:start position:0% of of a spreadsheet and its reactive 00:01:34.880 --> 00:01:35.990 align:start position:0% of of a spreadsheet and its reactive functional<00:01:35.520> model 00:01:35.990 --> 00:01:36.000 align:start position:0% functional model 00:01:36.000 --> 00:01:39.270 align:start position:0% functional model to<00:01:36.400> to<00:01:36.640> render<00:01:37.040> a<00:01:37.759> front-end<00:01:38.799> was 00:01:39.270 --> 00:01:39.280 align:start position:0% to to render a front-end was 00:01:39.280 --> 00:01:43.990 align:start position:0% to to render a front-end was really<00:01:39.520> novel<00:01:40.000> at<00:01:40.079> the<00:01:40.240> time<00:01:41.040> uh<00:01:41.280> even<00:01:42.240> and<00:01:42.479> and 00:01:43.990 --> 00:01:44.000 align:start position:0% really novel at the time uh even and and 00:01:44.000 --> 00:01:47.109 align:start position:0% really novel at the time uh even and and testament<00:01:44.479> to<00:01:44.640> the<00:01:44.799> fact<00:01:45.280> that<00:01:45.680> today<00:01:46.560> you 00:01:47.109 --> 00:01:47.119 align:start position:0% testament to the fact that today you 00:01:47.119 --> 00:01:50.149 align:start position:0% testament to the fact that today you we<00:01:47.360> we<00:01:47.600> see<00:01:47.759> this<00:01:48.079> a<00:01:48.159> little<00:01:48.399> bit<00:01:48.799> more<00:01:49.600> uh 00:01:50.149 --> 00:01:50.159 align:start position:0% we we see this a little bit more uh 00:01:50.159 --> 00:01:54.230 align:start position:0% we we see this a little bit more uh but<00:01:50.399> it<00:01:50.880> was<00:01:51.280> uh<00:01:51.840> the<00:01:52.000> first<00:01:52.240> time<00:01:52.560> i<00:01:52.880> i<00:01:53.280> heard 00:01:54.230 --> 00:01:54.240 align:start position:0% but it was uh the first time i i heard 00:01:54.240 --> 00:01:57.590 align:start position:0% but it was uh the first time i i heard about<00:01:55.200> this<00:01:55.439> kind<00:01:55.600> of<00:01:56.560> mapping<00:01:57.119> of 00:01:57.590 --> 00:01:57.600 align:start position:0% about this kind of mapping of 00:01:57.600 --> 00:02:01.510 align:start position:0% about this kind of mapping of of<00:01:57.759> a<00:01:57.840> concept<00:01:58.479> onto<00:02:00.079> web<00:02:00.320> frameworks 00:02:01.510 --> 00:02:01.520 align:start position:0% of a concept onto web frameworks 00:02:01.520 --> 00:02:06.310 align:start position:0% of a concept onto web frameworks so<00:02:03.280> i<00:02:04.079> at<00:02:04.240> the<00:02:04.399> time<00:02:04.719> i<00:02:04.960> already 00:02:06.310 --> 00:02:06.320 align:start position:0% so i at the time i already 00:02:06.320 --> 00:02:09.109 align:start position:0% so i at the time i already was<00:02:06.880> was<00:02:07.200> uh<00:02:07.439> convinced<00:02:07.920> that<00:02:08.239> uh<00:02:08.479> alan<00:02:08.800> was<00:02:09.039> a 00:02:09.109 --> 00:02:09.119 align:start position:0% was was uh convinced that uh alan was a 00:02:09.119 --> 00:02:10.790 align:start position:0% was was uh convinced that uh alan was a man<00:02:09.360> of<00:02:09.520> ideas 00:02:10.790 --> 00:02:10.800 align:start position:0% man of ideas 00:02:10.800 --> 00:02:13.589 align:start position:0% man of ideas and<00:02:11.200> he<00:02:11.440> confirmed<00:02:11.840> this<00:02:12.160> all<00:02:12.560> the<00:02:12.720> time 00:02:13.589 --> 00:02:13.599 align:start position:0% and he confirmed this all the time 00:02:13.599 --> 00:02:14.390 align:start position:0% and he confirmed this all the time because<00:02:14.000> he 00:02:14.390 --> 00:02:14.400 align:start position:0% because he 00:02:14.400 --> 00:02:17.510 align:start position:0% because he he<00:02:14.640> managed<00:02:15.360> to<00:02:15.760> to<00:02:15.920> do<00:02:16.239> to<00:02:16.400> come<00:02:16.800> to<00:02:16.959> come<00:02:17.200> up 00:02:17.510 --> 00:02:17.520 align:start position:0% he managed to to do to come to come up 00:02:17.520 --> 00:02:20.630 align:start position:0% he managed to to do to come to come up with<00:02:17.840> novel<00:02:18.239> ideas<00:02:19.200> again<00:02:19.520> and<00:02:19.680> again 00:02:20.630 --> 00:02:20.640 align:start position:0% with novel ideas again and again 00:02:20.640 --> 00:02:24.150 align:start position:0% with novel ideas again and again if<00:02:20.800> i<00:02:20.879> may<00:02:21.120> say<00:02:21.280> so<00:02:22.000> um 00:02:24.150 --> 00:02:24.160 align:start position:0% if i may say so um 00:02:24.160 --> 00:02:27.270 align:start position:0% if i may say so um because<00:02:24.959> uh<00:02:25.599> the<00:02:25.760> next<00:02:26.160> next<00:02:26.480> thing 00:02:27.270 --> 00:02:27.280 align:start position:0% because uh the next next thing 00:02:27.280 --> 00:02:30.710 align:start position:0% because uh the next next thing alan<00:02:27.599> was<00:02:27.840> doing<00:02:29.280> was<00:02:29.840> the<00:02:30.000> boot 00:02:30.710 --> 00:02:30.720 align:start position:0% alan was doing was the boot 00:02:30.720 --> 00:02:34.309 align:start position:0% alan was doing was the boot uh<00:02:32.560> bit<00:02:32.800> framework<00:02:33.280> and<00:02:33.360> that<00:02:33.519> was<00:02:33.760> also<00:02:34.080> very 00:02:34.309 --> 00:02:34.319 align:start position:0% uh bit framework and that was also very 00:02:34.319 --> 00:02:35.750 align:start position:0% uh bit framework and that was also very interesting 00:02:35.750 --> 00:02:35.760 align:start position:0% interesting 00:02:35.760 --> 00:02:40.550 align:start position:0% interesting architecturally 00:02:40.550 --> 00:02:40.560 align:start position:0% 00:02:40.560 --> 00:02:43.509 align:start position:0% because<00:02:41.440> it<00:02:41.840> solved<00:02:42.239> a<00:02:42.319> couple<00:02:42.640> of<00:02:42.879> problems 00:02:43.509 --> 00:02:43.519 align:start position:0% because it solved a couple of problems 00:02:43.519 --> 00:02:43.910 align:start position:0% because it solved a couple of problems that 00:02:43.910 --> 00:02:43.920 align:start position:0% that 00:02:43.920 --> 00:02:46.550 align:start position:0% that we<00:02:44.319> we<00:02:44.480> had<00:02:44.720> with<00:02:44.879> the<00:02:45.040> traditional<00:02:45.680> tools<00:02:46.239> in 00:02:46.550 --> 00:02:46.560 align:start position:0% we we had with the traditional tools in 00:02:46.560 --> 00:02:47.990 align:start position:0% we we had with the traditional tools in aligning<00:02:47.040> them 00:02:47.990 --> 00:02:48.000 align:start position:0% aligning them 00:02:48.000 --> 00:02:51.270 align:start position:0% aligning them performance<00:02:48.720> wise<00:02:49.120> but<00:02:49.440> also<00:02:50.160> um 00:02:51.270 --> 00:02:51.280 align:start position:0% performance wise but also um 00:02:51.280 --> 00:02:54.869 align:start position:0% performance wise but also um it<00:02:51.519> was<00:02:51.920> based<00:02:52.160> on<00:02:52.239> the<00:02:52.400> idea<00:02:53.200> that 00:02:54.869 --> 00:02:54.879 align:start position:0% it was based on the idea that 00:02:54.879 --> 00:02:57.910 align:start position:0% it was based on the idea that a<00:02:55.120> build<00:02:55.360> tool<00:02:55.840> doesn't<00:02:56.239> necessarily<00:02:56.800> has<00:02:57.680> has 00:02:57.910 --> 00:02:57.920 align:start position:0% a build tool doesn't necessarily has has 00:02:57.920 --> 00:02:58.309 align:start position:0% a build tool doesn't necessarily has has to<00:02:58.000> be 00:02:58.309 --> 00:02:58.319 align:start position:0% to be 00:02:58.319 --> 00:03:01.509 align:start position:0% to be declarative<00:02:59.760> and<00:02:59.920> it<00:03:00.080> came<00:03:00.319> up<00:03:00.480> with<00:03:00.720> the<00:03:00.959> idea 00:03:01.509 --> 00:03:01.519 align:start position:0% declarative and it came up with the idea 00:03:01.519 --> 00:03:04.630 align:start position:0% declarative and it came up with the idea of<00:03:01.840> giving<00:03:02.239> the<00:03:02.400> full<00:03:02.640> power<00:03:03.040> of<00:03:03.200> closure 00:03:04.630 --> 00:03:04.640 align:start position:0% of giving the full power of closure 00:03:04.640 --> 00:03:07.830 align:start position:0% of giving the full power of closure while<00:03:05.120> while<00:03:05.360> writing<00:03:06.400> uh<00:03:07.120> the<00:03:07.599> build 00:03:07.830 --> 00:03:07.840 align:start position:0% while while writing uh the build 00:03:07.840 --> 00:03:09.509 align:start position:0% while while writing uh the build programs<00:03:08.319> the<00:03:08.400> extensions<00:03:08.959> for<00:03:09.120> the<00:03:09.280> build 00:03:09.509 --> 00:03:09.519 align:start position:0% programs the extensions for the build 00:03:09.519 --> 00:03:10.470 align:start position:0% programs the extensions for the build tool 00:03:10.470 --> 00:03:10.480 align:start position:0% tool 00:03:10.480 --> 00:03:12.550 align:start position:0% tool and<00:03:10.560> that<00:03:10.720> was<00:03:10.879> very<00:03:11.120> novel<00:03:11.760> also<00:03:12.239> and<00:03:12.400> very 00:03:12.550 --> 00:03:12.560 align:start position:0% and that was very novel also and very 00:03:12.560 --> 00:03:13.509 align:start position:0% and that was very novel also and very interesting 00:03:13.509 --> 00:03:13.519 align:start position:0% interesting 00:03:13.519 --> 00:03:16.149 align:start position:0% interesting because<00:03:14.159> normally<00:03:14.560> build<00:03:14.800> tools<00:03:15.120> are<00:03:15.280> either 00:03:16.149 --> 00:03:16.159 align:start position:0% because normally build tools are either 00:03:16.159 --> 00:03:18.390 align:start position:0% because normally build tools are either declarative<00:03:16.959> or<00:03:17.200> they<00:03:17.360> have<00:03:17.519> a<00:03:17.599> dsl 00:03:18.390 --> 00:03:18.400 align:start position:0% declarative or they have a dsl 00:03:18.400 --> 00:03:21.830 align:start position:0% declarative or they have a dsl that<00:03:18.560> you<00:03:18.720> use<00:03:19.040> to<00:03:19.360> extend<00:03:19.840> it 00:03:21.830 --> 00:03:21.840 align:start position:0% that you use to extend it 00:03:21.840 --> 00:03:25.509 align:start position:0% that you use to extend it uh<00:03:22.400> and<00:03:22.720> and<00:03:23.040> and<00:03:23.519> and<00:03:23.680> boot<00:03:24.400> was<00:03:24.640> very<00:03:24.959> elegant 00:03:25.509 --> 00:03:25.519 align:start position:0% uh and and and and boot was very elegant 00:03:25.519 --> 00:03:27.030 align:start position:0% uh and and and and boot was very elegant architectural<00:03:26.159> solution<00:03:26.480> which<00:03:26.720> gave<00:03:26.879> you 00:03:27.030 --> 00:03:27.040 align:start position:0% architectural solution which gave you 00:03:27.040 --> 00:03:29.910 align:start position:0% architectural solution which gave you the<00:03:27.120> full<00:03:27.360> power<00:03:27.680> of<00:03:27.840> closure 00:03:29.910 --> 00:03:29.920 align:start position:0% the full power of closure 00:03:29.920 --> 00:03:32.149 align:start position:0% the full power of closure so<00:03:30.239> you<00:03:30.400> might<00:03:30.560> think<00:03:30.799> that<00:03:31.040> uh<00:03:31.360> alan<00:03:31.680> diaper 00:03:32.149 --> 00:03:32.159 align:start position:0% so you might think that uh alan diaper 00:03:32.159 --> 00:03:37.509 align:start position:0% so you might think that uh alan diaper was<00:03:32.720> happy<00:03:33.040> in<00:03:33.200> claudia<00:03:33.680> land<00:03:34.000> but<00:03:34.159> next<00:03:34.400> time 00:03:37.509 --> 00:03:37.519 align:start position:0% 00:03:37.519 --> 00:03:39.670 align:start position:0% you<00:03:37.680> hear<00:03:37.920> about<00:03:38.159> him<00:03:38.480> and<00:03:38.799> it's<00:03:39.040> about<00:03:39.440> in<00:03:39.599> the 00:03:39.670 --> 00:03:39.680 align:start position:0% you hear about him and it's about in the 00:03:39.680 --> 00:03:41.750 align:start position:0% you hear about him and it's about in the context<00:03:40.159> of<00:03:40.400> ah 00:03:41.750 --> 00:03:41.760 align:start position:0% context of ah 00:03:41.760 --> 00:03:43.990 align:start position:0% context of ah and<00:03:41.920> that<00:03:42.159> is<00:03:42.480> that<00:03:42.720> is<00:03:42.879> that<00:03:43.120> is<00:03:43.200> what<00:03:43.440> i<00:03:43.760> like 00:03:43.990 --> 00:03:44.000 align:start position:0% and that is that is that is what i like 00:03:44.000 --> 00:03:45.509 align:start position:0% and that is that is that is what i like about<00:03:44.239> alan<00:03:44.640> it's<00:03:44.879> that 00:03:45.509 --> 00:03:45.519 align:start position:0% about alan it's that 00:03:45.519 --> 00:03:47.830 align:start position:0% about alan it's that it's<00:03:45.760> not<00:03:46.159> it's<00:03:46.319> not<00:03:46.560> it's<00:03:46.640> not<00:03:46.799> just<00:03:47.120> about 00:03:47.830 --> 00:03:47.840 align:start position:0% it's not it's not it's not just about 00:03:47.840 --> 00:03:48.949 align:start position:0% it's not it's not it's not just about one<00:03:48.239> community 00:03:48.949 --> 00:03:48.959 align:start position:0% one community 00:03:48.959 --> 00:03:52.070 align:start position:0% one community one<00:03:49.200> language<00:03:50.080> um<00:03:51.200> this<00:03:51.760> this 00:03:52.070 --> 00:03:52.080 align:start position:0% one language um this this 00:03:52.080 --> 00:03:56.789 align:start position:0% one language um this this this<00:03:52.480> uh<00:03:53.040> this<00:03:53.280> um<00:03:55.040> you<00:03:55.200> know 00:03:56.789 --> 00:03:56.799 align:start position:0% this uh this um you know 00:03:56.799 --> 00:03:58.710 align:start position:0% this uh this um you know polyglotism<00:03:57.599> if<00:03:57.760> i<00:03:57.920> may<00:03:58.080> say<00:03:58.400> you<00:03:58.480> know<00:03:58.640> the 00:03:58.710 --> 00:03:58.720 align:start position:0% polyglotism if i may say you know the 00:03:58.720 --> 00:04:00.309 align:start position:0% polyglotism if i may say you know the ability<00:03:59.200> to<00:03:59.200> to 00:04:00.309 --> 00:04:00.319 align:start position:0% ability to to 00:04:00.319 --> 00:04:02.869 align:start position:0% ability to to learn<00:04:00.720> multiple<00:04:01.120> languages<00:04:01.760> and<00:04:01.920> juggle<00:04:02.239> with 00:04:02.869 --> 00:04:02.879 align:start position:0% learn multiple languages and juggle with 00:04:02.879 --> 00:04:05.190 align:start position:0% learn multiple languages and juggle with the<00:04:02.959> languages 00:04:05.190 --> 00:04:05.200 align:start position:0% the languages 00:04:05.200 --> 00:04:07.910 align:start position:0% the languages polyamory<00:04:05.920> even<00:04:06.319> is<00:04:06.480> that<00:04:06.640> the<00:04:06.720> same<00:04:06.959> thing 00:04:07.910 --> 00:04:07.920 align:start position:0% polyamory even is that the same thing 00:04:07.920 --> 00:04:08.520 align:start position:0% polyamory even is that the same thing different<00:04:08.239> thing 00:04:08.520 --> 00:04:08.530 align:start position:0% different thing 00:04:08.530 --> 00:04:09.990 align:start position:0% different thing [Music] 00:04:09.990 --> 00:04:10.000 align:start position:0% [Music] 00:04:10.000 --> 00:04:13.030 align:start position:0% [Music] that's<00:04:10.319> awesome<00:04:10.640> yeah<00:04:11.840> um 00:04:13.030 --> 00:04:13.040 align:start position:0% that's awesome yeah um 00:04:13.040 --> 00:04:16.069 align:start position:0% that's awesome yeah um this<00:04:13.280> idea<00:04:14.000> of<00:04:14.239> uh<00:04:14.640> using<00:04:14.959> languages<00:04:15.599> for<00:04:16.000> in 00:04:16.069 --> 00:04:16.079 align:start position:0% this idea of uh using languages for in 00:04:16.079 --> 00:04:16.870 align:start position:0% this idea of uh using languages for in the<00:04:16.239> context 00:04:16.870 --> 00:04:16.880 align:start position:0% the context 00:04:16.880 --> 00:04:20.949 align:start position:0% the context uh<00:04:17.359> in<00:04:17.680> the<00:04:17.759> right<00:04:18.000> context<00:04:18.720> and<00:04:19.120> the<00:04:19.280> idea<00:04:19.759> to 00:04:20.949 --> 00:04:20.959 align:start position:0% uh in the right context and the idea to 00:04:20.959 --> 00:04:24.790 align:start position:0% uh in the right context and the idea to uh<00:04:21.519> to<00:04:21.680> be<00:04:21.759> able<00:04:21.919> to<00:04:22.079> move<00:04:22.240> along<00:04:22.800> and<00:04:22.960> not<00:04:23.199> to 00:04:24.790 --> 00:04:24.800 align:start position:0% uh to be able to move along and not to 00:04:24.800 --> 00:04:26.950 align:start position:0% uh to be able to move along and not to to<00:04:25.040> to<00:04:25.199> be<00:04:25.280> more<00:04:25.520> married<00:04:26.000> to<00:04:26.160> the<00:04:26.400> idea<00:04:26.800> and 00:04:26.950 --> 00:04:26.960 align:start position:0% to to be more married to the idea and 00:04:26.960 --> 00:04:28.950 align:start position:0% to to be more married to the idea and the<00:04:27.040> concepts 00:04:28.950 --> 00:04:28.960 align:start position:0% the concepts 00:04:28.960 --> 00:04:31.350 align:start position:0% the concepts behind<00:04:29.280> what<00:04:29.520> you're<00:04:29.680> doing<00:04:30.080> than<00:04:30.479> than<00:04:31.040> than 00:04:31.350 --> 00:04:31.360 align:start position:0% behind what you're doing than than than 00:04:31.360 --> 00:04:32.390 align:start position:0% behind what you're doing than than than the 00:04:32.390 --> 00:04:32.400 align:start position:0% the 00:04:32.400 --> 00:04:34.629 align:start position:0% the the<00:04:32.560> particular<00:04:33.360> uh<00:04:33.680> implementation<00:04:34.479> that 00:04:34.629 --> 00:04:34.639 align:start position:0% the particular uh implementation that 00:04:34.639 --> 00:04:36.870 align:start position:0% the particular uh implementation that you're<00:04:34.800> using 00:04:36.870 --> 00:04:36.880 align:start position:0% you're using 00:04:36.880 --> 00:04:39.909 align:start position:0% you're using this<00:04:37.360> this<00:04:37.680> this<00:04:38.240> this<00:04:38.560> is<00:04:38.800> uh<00:04:39.199> for<00:04:39.360> me 00:04:39.909 --> 00:04:39.919 align:start position:0% this this this this is uh for me 00:04:39.919 --> 00:04:42.550 align:start position:0% this this this this is uh for me a<00:04:40.160> sign<00:04:40.560> of<00:04:40.880> maturity<00:04:41.440> in<00:04:41.600> terms<00:04:41.919> of 00:04:42.550 --> 00:04:42.560 align:start position:0% a sign of maturity in terms of 00:04:42.560 --> 00:04:43.670 align:start position:0% a sign of maturity in terms of developers<00:04:43.120> so 00:04:43.670 --> 00:04:43.680 align:start position:0% developers so 00:04:43.680 --> 00:04:45.990 align:start position:0% developers so i<00:04:43.840> think<00:04:44.000> now<00:04:44.240> it's<00:04:44.400> the<00:04:44.560> time<00:04:44.880> to<00:04:45.280> to<00:04:45.440> see<00:04:45.840> what 00:04:45.990 --> 00:04:46.000 align:start position:0% i think now it's the time to to see what 00:04:46.000 --> 00:04:48.390 align:start position:0% i think now it's the time to to see what kind<00:04:46.160> of<00:04:46.320> audience<00:04:46.720> we<00:04:46.800> have<00:04:47.120> because 00:04:48.390 --> 00:04:48.400 align:start position:0% kind of audience we have because 00:04:48.400 --> 00:04:52.150 align:start position:0% kind of audience we have because this<00:04:48.639> is<00:04:48.960> this<00:04:49.199> is<00:04:49.440> uh<00:04:49.759> these<00:04:50.240> insights<00:04:50.880> are 00:04:52.150 --> 00:04:52.160 align:start position:0% this is this is uh these insights are 00:04:52.160 --> 00:04:55.430 align:start position:0% this is this is uh these insights are very<00:04:52.400> useful<00:04:52.880> to<00:04:53.520> to<00:04:53.840> uh<00:04:54.960> to 00:04:55.430 --> 00:04:55.440 align:start position:0% very useful to to uh to 00:04:55.440 --> 00:04:58.469 align:start position:0% very useful to to uh to to<00:04:55.600> people<00:04:55.919> who<00:04:56.160> begin<00:04:56.880> uh<00:04:57.440> in<00:04:57.520> their 00:04:58.469 --> 00:04:58.479 align:start position:0% to people who begin uh in their 00:04:58.479 --> 00:05:02.310 align:start position:0% to people who begin uh in their beginners<00:04:59.040> or<00:05:00.560> people<00:05:00.880> who<00:05:01.280> who<00:05:01.520> are 00:05:02.310 --> 00:05:02.320 align:start position:0% beginners or people who who are 00:05:02.320 --> 00:05:04.230 align:start position:0% beginners or people who who are uh<00:05:02.639> busy<00:05:03.039> learning<00:05:03.360> their<00:05:03.680> first<00:05:03.919> language 00:05:04.230 --> 00:05:04.240 align:start position:0% uh busy learning their first language 00:05:04.240 --> 00:05:05.430 align:start position:0% uh busy learning their first language because<00:05:04.400> there<00:05:04.560> is<00:05:04.720> also<00:05:04.960> always 00:05:05.430 --> 00:05:05.440 align:start position:0% because there is also always 00:05:05.440 --> 00:05:08.469 align:start position:0% because there is also always a<00:05:05.680> first<00:05:06.000> language<00:05:07.520> and<00:05:07.680> you<00:05:07.840> have<00:05:07.919> to<00:05:08.080> master 00:05:08.469 --> 00:05:08.479 align:start position:0% a first language and you have to master 00:05:08.479 --> 00:05:10.469 align:start position:0% a first language and you have to master it<00:05:08.639> before<00:05:08.960> you<00:05:09.120> can<00:05:09.680> start<00:05:10.000> jogging<00:05:10.320> with 00:05:10.469 --> 00:05:10.479 align:start position:0% it before you can start jogging with 00:05:10.479 --> 00:05:11.749 align:start position:0% it before you can start jogging with concepts<00:05:11.120> and 00:05:11.749 --> 00:05:11.759 align:start position:0% concepts and 00:05:11.759 --> 00:05:15.029 align:start position:0% concepts and and<00:05:12.240> ideas<00:05:13.039> so<00:05:14.080> uh 00:05:15.029 --> 00:05:15.039 align:start position:0% and ideas so uh 00:05:15.039 --> 00:05:16.550 align:start position:0% and ideas so uh that<00:05:15.280> is<00:05:15.440> one<00:05:15.600> thing<00:05:15.759> but<00:05:15.919> the<00:05:16.000> other<00:05:16.240> thing<00:05:16.479> is 00:05:16.550 --> 00:05:16.560 align:start position:0% that is one thing but the other thing is 00:05:16.560 --> 00:05:18.870 align:start position:0% that is one thing but the other thing is that<00:05:16.880> alan<00:05:17.440> also<00:05:18.000> uh 00:05:18.870 --> 00:05:18.880 align:start position:0% that alan also uh 00:05:18.880 --> 00:05:20.710 align:start position:0% that alan also uh is<00:05:19.039> going<00:05:19.199> to<00:05:19.360> talk<00:05:19.600> about<00:05:19.840> a<00:05:20.000> project<00:05:20.400> which 00:05:20.710 --> 00:05:20.720 align:start position:0% is going to talk about a project which 00:05:20.720 --> 00:05:22.790 align:start position:0% is going to talk about a project which is<00:05:20.960> uh 00:05:22.790 --> 00:05:22.800 align:start position:0% is uh 00:05:22.800 --> 00:05:26.230 align:start position:0% is uh in<00:05:23.039> a<00:05:23.199> yet<00:05:23.520> another<00:05:23.919> language<00:05:24.320> common<00:05:24.639> list<00:05:25.759> uh 00:05:26.230 --> 00:05:26.240 align:start position:0% in a yet another language common list uh 00:05:26.240 --> 00:05:27.670 align:start position:0% in a yet another language common list uh although<00:05:26.639> it's<00:05:26.800> the<00:05:26.960> same<00:05:27.280> family<00:05:27.600> of 00:05:27.670 --> 00:05:27.680 align:start position:0% although it's the same family of 00:05:27.680 --> 00:05:30.070 align:start position:0% although it's the same family of languages<00:05:28.400> but<00:05:28.960> uh<00:05:29.199> the<00:05:29.440> question<00:05:29.759> now 00:05:30.070 --> 00:05:30.080 align:start position:0% languages but uh the question now 00:05:30.080 --> 00:05:32.950 align:start position:0% languages but uh the question now is<00:05:30.479> uh<00:05:31.120> the<00:05:31.520> about<00:05:31.759> the<00:05:31.919> audience<00:05:32.639> we<00:05:32.800> would 00:05:32.950 --> 00:05:32.960 align:start position:0% is uh the about the audience we would 00:05:32.960 --> 00:05:34.870 align:start position:0% is uh the about the audience we would like<00:05:33.120> to<00:05:33.199> know<00:05:33.360> two<00:05:33.600> things 00:05:34.870 --> 00:05:34.880 align:start position:0% like to know two things 00:05:34.880 --> 00:05:38.310 align:start position:0% like to know two things and<00:05:35.360> uh<00:05:36.000> please<00:05:36.560> uh<00:05:36.960> use<00:05:37.199> the<00:05:37.360> chat<00:05:37.759> to 00:05:38.310 --> 00:05:38.320 align:start position:0% and uh please uh use the chat to 00:05:38.320 --> 00:05:41.830 align:start position:0% and uh please uh use the chat to to<00:05:38.560> answer<00:05:39.280> the<00:05:39.520> the<00:05:39.759> question<00:05:40.080> the<00:05:40.240> first<00:05:40.800> um 00:05:41.830 --> 00:05:41.840 align:start position:0% to answer the the question the first um 00:05:41.840 --> 00:05:44.950 align:start position:0% to answer the the question the first um the<00:05:42.000> first<00:05:42.240> question<00:05:42.639> is<00:05:42.960> uh<00:05:43.360> is<00:05:43.600> about<00:05:44.080> the 00:05:44.950 --> 00:05:44.960 align:start position:0% the first question is uh is about the 00:05:44.960 --> 00:05:48.629 align:start position:0% the first question is uh is about the experience<00:05:45.520> of<00:05:45.840> everybody<00:05:46.400> here<00:05:46.960> so<00:05:47.919> to<00:05:48.160> know 00:05:48.629 --> 00:05:48.639 align:start position:0% experience of everybody here so to know 00:05:48.639 --> 00:05:51.510 align:start position:0% experience of everybody here so to know uh<00:05:49.039> how<00:05:49.280> experienced<00:05:50.000> the<00:05:50.720> audience<00:05:51.199> is<00:05:51.360> in 00:05:51.510 --> 00:05:51.520 align:start position:0% uh how experienced the audience is in 00:05:51.520 --> 00:05:52.629 align:start position:0% uh how experienced the audience is in terms<00:05:51.919> of 00:05:52.629 --> 00:05:52.639 align:start position:0% terms of 00:05:52.639 --> 00:05:55.510 align:start position:0% terms of career<00:05:53.759> as<00:05:53.919> a<00:05:54.000> developer<00:05:54.800> so<00:05:54.960> maybe<00:05:55.280> you<00:05:55.360> can 00:05:55.510 --> 00:05:55.520 align:start position:0% career as a developer so maybe you can 00:05:55.520 --> 00:05:56.870 align:start position:0% career as a developer so maybe you can put<00:05:55.759> in<00:05:55.840> the<00:05:56.000> chat 00:05:56.870 --> 00:05:56.880 align:start position:0% put in the chat 00:05:56.880 --> 00:06:00.629 align:start position:0% put in the chat how<00:05:57.280> how<00:05:57.440> long<00:05:57.680> you've<00:05:57.840> been<00:05:58.240> programmed 00:06:00.629 --> 00:06:00.639 align:start position:0% how how long you've been programmed 00:06:00.639 --> 00:06:06.710 align:start position:0% how how long you've been programmed thank<00:06:04.840> you 00:06:06.710 --> 00:06:06.720 align:start position:0% thank you 00:06:06.720 --> 00:06:09.990 align:start position:0% thank you okay<00:06:07.199> 20<00:06:07.520> years<00:06:07.919> for<00:06:09.039> garyvalley 00:06:09.990 --> 00:06:10.000 align:start position:0% okay 20 years for garyvalley 00:06:10.000 --> 00:06:15.029 align:start position:0% okay 20 years for garyvalley capital<00:06:10.479> devices 00:06:15.029 --> 00:06:15.039 align:start position:0% 00:06:15.039 --> 00:06:19.510 align:start position:0% 10<00:06:15.360> years<00:06:15.840> professionally<00:06:16.880> seven<00:06:17.280> years 00:06:19.510 --> 00:06:19.520 align:start position:0% 10 years professionally seven years 00:06:19.520 --> 00:06:23.590 align:start position:0% 10 years professionally seven years six<00:06:19.840> years<00:06:22.080> six<00:06:22.400> years<00:06:22.880> 20 00:06:23.590 --> 00:06:23.600 align:start position:0% six years six years 20 00:06:23.600 --> 00:06:26.550 align:start position:0% six years six years 20 70.<00:06:24.240> so<00:06:24.479> we<00:06:24.639> have<00:06:24.960> uh<00:06:25.440> i<00:06:25.520> would<00:06:25.759> say<00:06:26.319> three 00:06:26.550 --> 00:06:26.560 align:start position:0% 70. so we have uh i would say three 00:06:26.560 --> 00:06:27.749 align:start position:0% 70. so we have uh i would say three years 00:06:27.749 --> 00:06:27.759 align:start position:0% years 00:06:27.759 --> 00:06:30.730 align:start position:0% years six<00:06:28.000> times<00:06:30.400> and 00:06:30.730 --> 00:06:30.740 align:start position:0% six times and 00:06:30.740 --> 00:06:33.350 align:start position:0% six times and [Music] 00:06:33.350 --> 00:06:33.360 align:start position:0% [Music] 00:06:33.360 --> 00:06:36.469 align:start position:0% [Music] everybody<00:06:33.919> is<00:06:34.080> kind<00:06:34.240> of<00:06:34.560> uh<00:06:35.280> okay<00:06:35.520> we<00:06:35.680> have<00:06:35.919> a 00:06:36.469 --> 00:06:36.479 align:start position:0% everybody is kind of uh okay we have a 00:06:36.479 --> 00:06:39.189 align:start position:0% everybody is kind of uh okay we have a okay<00:06:37.199> allen<00:06:37.520> your<00:06:37.680> audience<00:06:38.160> is<00:06:38.400> uh<00:06:38.720> made<00:06:38.960> of 00:06:39.189 --> 00:06:39.199 align:start position:0% okay allen your audience is uh made of 00:06:39.199 --> 00:06:39.670 align:start position:0% okay allen your audience is uh made of uh 00:06:39.670 --> 00:06:39.680 align:start position:0% uh 00:06:39.680 --> 00:06:41.990 align:start position:0% uh experienced<00:06:40.160> developers<00:06:41.440> which<00:06:41.680> maybe 00:06:41.990 --> 00:06:42.000 align:start position:0% experienced developers which maybe 00:06:42.000 --> 00:06:43.590 align:start position:0% experienced developers which maybe shouldn't<00:06:42.240> be<00:06:42.400> too<00:06:42.560> surprising<00:06:43.120> because<00:06:43.360> this 00:06:43.590 --> 00:06:43.600 align:start position:0% shouldn't be too surprising because this 00:06:43.600 --> 00:06:45.029 align:start position:0% shouldn't be too surprising because this is<00:06:43.680> not<00:06:43.919> the<00:06:44.000> kind<00:06:44.160> of<00:06:44.319> meetup 00:06:45.029 --> 00:06:45.039 align:start position:0% is not the kind of meetup 00:06:45.039 --> 00:06:48.550 align:start position:0% is not the kind of meetup you<00:06:45.120> stumble<00:06:45.520> upon<00:06:45.759> if<00:06:45.919> you<00:06:46.080> start<00:06:46.479> but<00:06:46.840> anyway 00:06:48.550 --> 00:06:48.560 align:start position:0% you stumble upon if you start but anyway 00:06:48.560 --> 00:06:51.430 align:start position:0% you stumble upon if you start but anyway now<00:06:48.720> we<00:06:48.880> know<00:06:49.759> and<00:06:49.840> then<00:06:50.400> the<00:06:50.560> second<00:06:50.960> question 00:06:51.430 --> 00:06:51.440 align:start position:0% now we know and then the second question 00:06:51.440 --> 00:06:52.710 align:start position:0% now we know and then the second question is 00:06:52.710 --> 00:06:52.720 align:start position:0% is 00:06:52.720 --> 00:06:55.589 align:start position:0% is what<00:06:52.960> is<00:06:53.039> your<00:06:53.280> daily<00:06:53.919> uh<00:06:54.319> driver<00:06:54.960> in<00:06:55.120> terms<00:06:55.360> of 00:06:55.589 --> 00:06:55.599 align:start position:0% what is your daily uh driver in terms of 00:06:55.599 --> 00:06:56.710 align:start position:0% what is your daily uh driver in terms of language<00:06:56.080> because 00:06:56.710 --> 00:06:56.720 align:start position:0% language because 00:06:56.720 --> 00:06:59.189 align:start position:0% language because we<00:06:56.880> have<00:06:57.599> maybe<00:06:58.160> we<00:06:58.319> have<00:06:58.479> certainly<00:06:58.880> closure 00:06:59.189 --> 00:06:59.199 align:start position:0% we have maybe we have certainly closure 00:06:59.199 --> 00:07:00.710 align:start position:0% we have maybe we have certainly closure people<00:06:59.520> which<00:06:59.759> are<00:06:59.840> recognized 00:07:00.710 --> 00:07:00.720 align:start position:0% people which are recognized 00:07:00.720 --> 00:07:02.710 align:start position:0% people which are recognized but<00:07:00.880> we<00:07:01.039> might<00:07:01.360> might<00:07:01.599> have<00:07:02.000> commonly<00:07:02.479> people 00:07:02.710 --> 00:07:02.720 align:start position:0% but we might might have commonly people 00:07:02.720 --> 00:07:04.550 align:start position:0% but we might might have commonly people and<00:07:02.800> we<00:07:02.880> might<00:07:03.120> have<00:07:03.280> people<00:07:03.520> who 00:07:04.550 --> 00:07:04.560 align:start position:0% and we might have people who 00:07:04.560 --> 00:07:06.309 align:start position:0% and we might have people who write<00:07:04.800> in<00:07:04.960> other<00:07:05.280> languages<00:07:05.840> as<00:07:05.919> well<00:07:06.160> so 00:07:06.309 --> 00:07:06.319 align:start position:0% write in other languages as well so 00:07:06.319 --> 00:07:08.469 align:start position:0% write in other languages as well so maybe<00:07:06.639> everybody<00:07:07.039> can<00:07:07.360> type<00:07:07.680> in 00:07:08.469 --> 00:07:08.479 align:start position:0% maybe everybody can type in 00:07:08.479 --> 00:07:10.070 align:start position:0% maybe everybody can type in what<00:07:08.720> kind<00:07:08.880> of<00:07:09.039> programming<00:07:09.520> language<00:07:09.840> they 00:07:10.070 --> 00:07:10.080 align:start position:0% what kind of programming language they 00:07:10.080 --> 00:07:11.589 align:start position:0% what kind of programming language they use<00:07:10.319> as<00:07:10.479> a<00:07:10.560> daily<00:07:10.800> driver 00:07:11.589 --> 00:07:11.599 align:start position:0% use as a daily driver 00:07:11.599 --> 00:07:13.110 align:start position:0% use as a daily driver and<00:07:11.759> the<00:07:11.919> question<00:07:12.240> is<00:07:12.400> just<00:07:12.639> the<00:07:12.800> daily 00:07:13.110 --> 00:07:13.120 align:start position:0% and the question is just the daily 00:07:13.120 --> 00:07:15.110 align:start position:0% and the question is just the daily driver<00:07:13.520> because<00:07:14.479> you<00:07:14.639> might 00:07:15.110 --> 00:07:15.120 align:start position:0% driver because you might 00:07:15.120 --> 00:07:17.189 align:start position:0% driver because you might know<00:07:15.440> multiple<00:07:15.919> languages<00:07:16.400> but<00:07:16.560> what<00:07:16.880> what<00:07:17.039> is 00:07:17.189 --> 00:07:17.199 align:start position:0% know multiple languages but what what is 00:07:17.199 --> 00:07:18.230 align:start position:0% know multiple languages but what what is the<00:07:17.360> the<00:07:17.520> main 00:07:18.230 --> 00:07:18.240 align:start position:0% the the main 00:07:18.240 --> 00:07:20.790 align:start position:0% the the main your<00:07:18.400> main<00:07:18.560> language<00:07:18.960> that<00:07:19.120> you<00:07:19.680> use<00:07:20.400> okay 00:07:20.790 --> 00:07:20.800 align:start position:0% your main language that you use okay 00:07:20.800 --> 00:07:21.350 align:start position:0% your main language that you use okay nice 00:07:21.350 --> 00:07:21.360 align:start position:0% nice 00:07:21.360 --> 00:07:24.550 align:start position:0% nice nice<00:07:22.240> uh<00:07:22.479> we<00:07:22.639> have<00:07:23.039> uh<00:07:23.280> ruby<00:07:23.680> we<00:07:23.840> have 00:07:24.550 --> 00:07:24.560 align:start position:0% nice uh we have uh ruby we have 00:07:24.560 --> 00:07:29.990 align:start position:0% nice uh we have uh ruby we have we<00:07:24.720> have<00:07:25.039> uh<00:07:25.440> c<00:07:25.680> plus<00:07:26.080> plus<00:07:26.560> we<00:07:26.720> have<00:07:28.840> kotlin 00:07:29.990 --> 00:07:30.000 align:start position:0% we have uh c plus plus we have kotlin 00:07:30.000 --> 00:07:34.870 align:start position:0% we have uh c plus plus we have kotlin um<00:07:30.639> we<00:07:30.800> have 00:07:34.870 --> 00:07:34.880 align:start position:0% 00:07:34.880 --> 00:07:40.070 align:start position:0% closure<00:07:36.240> and<00:07:37.280> python<00:07:37.840> also 00:07:40.070 --> 00:07:40.080 align:start position:0% closure and python also 00:07:40.080 --> 00:07:43.589 align:start position:0% closure and python also so<00:07:40.880> so<00:07:41.039> that's<00:07:41.360> nice 00:07:43.589 --> 00:07:43.599 align:start position:0% so so that's nice 00:07:43.599 --> 00:07:50.950 align:start position:0% so so that's nice commonly<00:07:44.479> also<00:07:44.879> your<00:07:45.120> script<00:07:45.919> that's<00:07:46.160> cool 00:07:50.950 --> 00:07:50.960 align:start position:0% 00:07:50.960 --> 00:07:53.029 align:start position:0% yeah<00:07:51.199> okay<00:07:51.520> so<00:07:51.840> so<00:07:52.240> great<00:07:52.479> thank<00:07:52.639> you<00:07:52.800> very 00:07:53.029 --> 00:07:53.039 align:start position:0% yeah okay so so great thank you very 00:07:53.039 --> 00:07:54.309 align:start position:0% yeah okay so so great thank you very much<00:07:53.680> and<00:07:53.919> i 00:07:54.309 --> 00:07:54.319 align:start position:0% much and i 00:07:54.319 --> 00:07:57.430 align:start position:0% much and i i<00:07:54.400> will<00:07:54.639> now<00:07:55.440> leave<00:07:55.919> the 00:07:57.430 --> 00:07:57.440 align:start position:0% i will now leave the 00:07:57.440 --> 00:08:01.110 align:start position:0% i will now leave the podium<00:07:58.319> if<00:07:58.479> i<00:07:58.560> may<00:07:58.800> say<00:07:58.960> so 00:08:01.110 --> 00:08:01.120 align:start position:0% podium if i may say so 00:08:01.120 --> 00:08:08.869 align:start position:0% podium if i may say so to<00:08:02.000> adam<00:08:03.360> thanks<00:08:04.080> let<00:08:04.240> me<00:08:04.319> simulate<00:08:04.800> coming<00:08:05.039> up 00:08:08.869 --> 00:08:08.879 align:start position:0% 00:08:08.879 --> 00:08:12.629 align:start position:0% oh<00:08:10.720> thank<00:08:10.960> you<00:08:11.039> daniel<00:08:11.919> uh<00:08:12.160> very 00:08:12.629 --> 00:08:12.639 align:start position:0% oh thank you daniel uh very 00:08:12.639 --> 00:08:14.629 align:start position:0% oh thank you daniel uh very humbling<00:08:13.039> and<00:08:13.120> flattering<00:08:13.599> introduction<00:08:14.400> uh 00:08:14.629 --> 00:08:14.639 align:start position:0% humbling and flattering introduction uh 00:08:14.639 --> 00:08:16.390 align:start position:0% humbling and flattering introduction uh i<00:08:14.720> cannot<00:08:15.039> take<00:08:15.280> full<00:08:15.520> credit<00:08:15.759> for<00:08:16.000> boot<00:08:16.240> or 00:08:16.390 --> 00:08:16.400 align:start position:0% i cannot take full credit for boot or 00:08:16.400 --> 00:08:17.189 align:start position:0% i cannot take full credit for boot or hoplon 00:08:17.189 --> 00:08:17.199 align:start position:0% hoplon 00:08:17.199 --> 00:08:20.550 align:start position:0% hoplon um<00:08:18.080> my<00:08:18.720> longtime<00:08:19.599> friend<00:08:19.919> and<00:08:20.000> collaborator 00:08:20.550 --> 00:08:20.560 align:start position:0% um my longtime friend and collaborator 00:08:20.560 --> 00:08:22.469 align:start position:0% um my longtime friend and collaborator misha<00:08:20.800> niskin<00:08:21.199> is<00:08:21.280> here<00:08:21.440> on<00:08:21.520> the<00:08:21.840> call 00:08:22.469 --> 00:08:22.479 align:start position:0% misha niskin is here on the call 00:08:22.479 --> 00:08:23.749 align:start position:0% misha niskin is here on the call so<00:08:22.639> that's<00:08:22.800> the<00:08:22.879> reason<00:08:23.120> i<00:08:23.199> have<00:08:23.280> to<00:08:23.360> be<00:08:23.440> honest 00:08:23.749 --> 00:08:23.759 align:start position:0% so that's the reason i have to be honest 00:08:23.759 --> 00:08:27.270 align:start position:0% so that's the reason i have to be honest about<00:08:24.000> it<00:08:24.639> uh<00:08:24.879> he<00:08:25.120> and<00:08:25.280> i 00:08:27.270 --> 00:08:27.280 align:start position:0% about it uh he and i 00:08:27.280 --> 00:08:30.469 align:start position:0% about it uh he and i designed<00:08:27.840> all<00:08:27.919> those<00:08:28.080> things<00:08:28.240> together<00:08:29.280> so 00:08:30.469 --> 00:08:30.479 align:start position:0% designed all those things together so 00:08:30.479 --> 00:08:34.070 align:start position:0% designed all those things together so um<00:08:32.320> but<00:08:32.719> yes<00:08:33.279> thank<00:08:33.440> you<00:08:33.599> so<00:08:33.760> much<00:08:33.919> for<00:08:34.000> the 00:08:34.070 --> 00:08:34.080 align:start position:0% um but yes thank you so much for the 00:08:34.080 --> 00:08:35.750 align:start position:0% um but yes thank you so much for the opportunity<00:08:34.560> to<00:08:34.640> come<00:08:34.800> here<00:08:34.959> and<00:08:35.120> speak 00:08:35.750 --> 00:08:35.760 align:start position:0% opportunity to come here and speak 00:08:35.760 --> 00:08:38.870 align:start position:0% opportunity to come here and speak and<00:08:37.519> i<00:08:37.680> was<00:08:38.320> telling 00:08:38.870 --> 00:08:38.880 align:start position:0% and i was telling 00:08:38.880 --> 00:08:42.870 align:start position:0% and i was telling the<00:08:39.039> daniels<00:08:39.680> before<00:08:40.000> the<00:08:40.159> call<00:08:41.200> uh 00:08:42.870 --> 00:08:42.880 align:start position:0% the daniels before the call uh 00:08:42.880 --> 00:08:45.590 align:start position:0% the daniels before the call uh preparing<00:08:43.839> for<00:08:44.000> things<00:08:44.240> like<00:08:44.399> this<00:08:45.040> is<00:08:45.279> always 00:08:45.590 --> 00:08:45.600 align:start position:0% preparing for things like this is always 00:08:45.600 --> 00:08:47.430 align:start position:0% preparing for things like this is always really<00:08:46.000> fun 00:08:47.430 --> 00:08:47.440 align:start position:0% really fun 00:08:47.440 --> 00:08:50.070 align:start position:0% really fun because<00:08:48.800> you<00:08:48.880> know<00:08:49.519> i'm<00:08:49.600> sure<00:08:49.760> you've<00:08:49.920> heard 00:08:50.070 --> 00:08:50.080 align:start position:0% because you know i'm sure you've heard 00:08:50.080 --> 00:08:51.829 align:start position:0% because you know i'm sure you've heard it<00:08:50.240> said<00:08:50.399> the<00:08:50.560> act<00:08:50.800> of<00:08:50.880> writing<00:08:51.279> is<00:08:51.440> kind<00:08:51.600> of<00:08:51.760> a 00:08:51.829 --> 00:08:51.839 align:start position:0% it said the act of writing is kind of a 00:08:51.839 --> 00:08:53.509 align:start position:0% it said the act of writing is kind of a vehicle<00:08:52.240> for<00:08:52.399> thought<00:08:52.720> and<00:08:52.800> for<00:08:53.040> honing<00:08:53.360> your 00:08:53.509 --> 00:08:53.519 align:start position:0% vehicle for thought and for honing your 00:08:53.519 --> 00:08:54.550 align:start position:0% vehicle for thought and for honing your thoughts 00:08:54.550 --> 00:08:54.560 align:start position:0% thoughts 00:08:54.560 --> 00:08:58.070 align:start position:0% thoughts and<00:08:55.519> every<00:08:55.680> time<00:08:55.920> i<00:08:56.000> have<00:08:56.160> an<00:08:56.320> opportunity<00:08:56.959> to 00:08:58.070 --> 00:08:58.080 align:start position:0% and every time i have an opportunity to 00:08:58.080 --> 00:09:01.030 align:start position:0% and every time i have an opportunity to introspect<00:08:59.040> and<00:08:59.440> crystallize<00:09:00.240> and<00:09:00.399> share<00:09:00.880> i 00:09:01.030 --> 00:09:01.040 align:start position:0% introspect and crystallize and share i 00:09:01.040 --> 00:09:01.910 align:start position:0% introspect and crystallize and share i feel<00:09:01.360> like<00:09:01.600> i 00:09:01.910 --> 00:09:01.920 align:start position:0% feel like i 00:09:01.920 --> 00:09:03.509 align:start position:0% feel like i gain<00:09:02.160> new<00:09:02.399> insights<00:09:02.720> for<00:09:02.880> myself<00:09:03.279> so<00:09:03.360> i'm 00:09:03.509 --> 00:09:03.519 align:start position:0% gain new insights for myself so i'm 00:09:03.519 --> 00:09:05.030 align:start position:0% gain new insights for myself so i'm grateful 00:09:05.030 --> 00:09:05.040 align:start position:0% grateful 00:09:05.040 --> 00:09:06.710 align:start position:0% grateful very<00:09:05.200> much<00:09:05.360> for<00:09:05.519> this<00:09:05.680> opportunity<00:09:06.399> and<00:09:06.640> i 00:09:06.710 --> 00:09:06.720 align:start position:0% very much for this opportunity and i 00:09:06.720 --> 00:09:08.550 align:start position:0% very much for this opportunity and i hope<00:09:06.959> i'm<00:09:07.120> able<00:09:07.360> to<00:09:07.440> share<00:09:07.760> something<00:09:08.160> of 00:09:08.550 --> 00:09:08.560 align:start position:0% hope i'm able to share something of 00:09:08.560 --> 00:09:12.230 align:start position:0% hope i'm able to share something of value<00:09:09.839> and<00:09:10.000> if<00:09:10.160> not<00:09:10.320> a<00:09:10.480> value<00:09:10.880> of<00:09:11.040> interest 00:09:12.230 --> 00:09:12.240 align:start position:0% value and if not a value of interest 00:09:12.240 --> 00:09:14.150 align:start position:0% value and if not a value of interest and<00:09:12.480> if<00:09:12.640> not<00:09:12.800> of<00:09:12.959> interest<00:09:13.440> at<00:09:13.519> least<00:09:13.920> you'll 00:09:14.150 --> 00:09:14.160 align:start position:0% and if not of interest at least you'll 00:09:14.160 --> 00:09:16.870 align:start position:0% and if not of interest at least you'll find<00:09:14.399> it<00:09:15.200> mildly<00:09:15.680> funny 00:09:16.870 --> 00:09:16.880 align:start position:0% find it mildly funny 00:09:16.880 --> 00:09:20.150 align:start position:0% find it mildly funny so<00:09:18.000> without<00:09:18.320> further<00:09:18.640> ado<00:09:18.880> let<00:09:19.040> me<00:09:19.279> uh 00:09:20.150 --> 00:09:20.160 align:start position:0% so without further ado let me uh 00:09:20.160 --> 00:09:23.350 align:start position:0% so without further ado let me uh get<00:09:20.399> my<00:09:21.519> slides<00:09:22.000> going<00:09:22.240> here<00:09:22.880> try<00:09:23.040> a<00:09:23.120> little 00:09:23.350 --> 00:09:23.360 align:start position:0% get my slides going here try a little 00:09:23.360 --> 00:09:30.550 align:start position:0% get my slides going here try a little screen<00:09:23.839> sharing 00:09:30.550 --> 00:09:30.560 align:start position:0% 00:09:30.560 --> 00:09:38.150 align:start position:0% share<00:09:34.839> screen 00:09:38.150 --> 00:09:38.160 align:start position:0% 00:09:38.160 --> 00:09:41.190 align:start position:0% okay<00:09:38.959> is<00:09:39.120> everybody<00:09:39.519> seeing<00:09:39.839> a<00:09:39.920> slide 00:09:41.190 --> 00:09:41.200 align:start position:0% okay is everybody seeing a slide 00:09:41.200 --> 00:09:45.350 align:start position:0% okay is everybody seeing a slide yeah<00:09:42.080> great 00:09:45.350 --> 00:09:45.360 align:start position:0% 00:09:45.360 --> 00:09:47.829 align:start position:0% so<00:09:45.760> yes<00:09:46.080> if<00:09:46.399> uh<00:09:46.800> you<00:09:46.959> have<00:09:47.120> any<00:09:47.360> questions 00:09:47.829 --> 00:09:47.839 align:start position:0% so yes if uh you have any questions 00:09:47.839 --> 00:09:48.389 align:start position:0% so yes if uh you have any questions later 00:09:48.389 --> 00:09:48.399 align:start position:0% later 00:09:48.399 --> 00:09:49.910 align:start position:0% later or<00:09:48.640> just<00:09:48.800> want<00:09:48.959> to<00:09:49.040> get<00:09:49.200> in<00:09:49.279> touch<00:09:49.600> you<00:09:49.760> can 00:09:49.910 --> 00:09:49.920 align:start position:0% or just want to get in touch you can 00:09:49.920 --> 00:09:51.269 align:start position:0% or just want to get in touch you can reach<00:09:50.160> me<00:09:50.320> at<00:09:50.399> these<00:09:50.560> coordinates<00:09:51.040> and<00:09:51.200> i'll 00:09:51.269 --> 00:09:51.279 align:start position:0% reach me at these coordinates and i'll 00:09:51.279 --> 00:09:52.790 align:start position:0% reach me at these coordinates and i'll share<00:09:51.519> these<00:09:51.680> slides 00:09:52.790 --> 00:09:52.800 align:start position:0% share these slides 00:09:52.800 --> 00:09:54.470 align:start position:0% share these slides as<00:09:52.959> well<00:09:53.279> and<00:09:53.440> get<00:09:53.680> distributed<00:09:54.240> and<00:09:54.320> they 00:09:54.470 --> 00:09:54.480 align:start position:0% as well and get distributed and they 00:09:54.480 --> 00:09:57.590 align:start position:0% as well and get distributed and they have<00:09:54.560> real<00:09:54.800> links<00:09:55.040> and<00:09:55.120> so<00:09:55.279> forth 00:09:57.590 --> 00:09:57.600 align:start position:0% 00:09:57.600 --> 00:10:01.030 align:start position:0% um<00:09:59.040> yeah<00:10:00.240> so 00:10:01.030 --> 00:10:01.040 align:start position:0% um yeah so 00:10:01.040 --> 00:10:03.269 align:start position:0% um yeah so daniel<00:10:01.519> has<00:10:01.680> done<00:10:01.839> a<00:10:01.920> fantastic<00:10:02.399> job<00:10:02.800> of 00:10:03.269 --> 00:10:03.279 align:start position:0% daniel has done a fantastic job of 00:10:03.279 --> 00:10:04.310 align:start position:0% daniel has done a fantastic job of biographying<00:10:04.000> me 00:10:04.310 --> 00:10:04.320 align:start position:0% biographying me 00:10:04.320 --> 00:10:07.430 align:start position:0% biographying me but<00:10:05.680> i<00:10:05.760> can<00:10:05.920> fill<00:10:06.160> in<00:10:06.320> some<00:10:06.560> gaps<00:10:06.959> and 00:10:07.430 --> 00:10:07.440 align:start position:0% but i can fill in some gaps and 00:10:07.440 --> 00:10:09.509 align:start position:0% but i can fill in some gaps and paint<00:10:07.680> the<00:10:07.839> picture<00:10:08.160> a<00:10:08.240> little<00:10:08.480> more<00:10:09.279> i<00:10:09.360> think 00:10:09.509 --> 00:10:09.519 align:start position:0% paint the picture a little more i think 00:10:09.519 --> 00:10:11.590 align:start position:0% paint the picture a little more i think this<00:10:09.760> is<00:10:09.920> important<00:10:10.399> because 00:10:11.590 --> 00:10:11.600 align:start position:0% this is important because 00:10:11.600 --> 00:10:13.030 align:start position:0% this is important because and<00:10:11.760> i'll<00:10:11.839> get<00:10:12.079> elaborate<00:10:12.480> more<00:10:12.640> on<00:10:12.800> this<00:10:12.880> but 00:10:13.030 --> 00:10:13.040 align:start position:0% and i'll get elaborate more on this but 00:10:13.040 --> 00:10:14.230 align:start position:0% and i'll get elaborate more on this but i<00:10:13.120> don't<00:10:13.279> think<00:10:13.360> you<00:10:13.440> can<00:10:13.680> understand<00:10:14.000> things 00:10:14.230 --> 00:10:14.240 align:start position:0% i don't think you can understand things 00:10:14.240 --> 00:10:16.310 align:start position:0% i don't think you can understand things in<00:10:14.320> the<00:10:14.399> world<00:10:14.640> without<00:10:14.959> understanding 00:10:16.310 --> 00:10:16.320 align:start position:0% in the world without understanding 00:10:16.320 --> 00:10:18.150 align:start position:0% in the world without understanding why<00:10:16.560> they<00:10:16.720> matter<00:10:17.040> to<00:10:17.200> other<00:10:17.440> people<00:10:17.839> and<00:10:18.079> to 00:10:18.150 --> 00:10:18.160 align:start position:0% why they matter to other people and to 00:10:18.160 --> 00:10:19.509 align:start position:0% why they matter to other people and to do<00:10:18.320> that<00:10:18.480> you<00:10:18.560> have<00:10:18.640> to<00:10:18.959> know<00:10:19.120> a<00:10:19.200> little<00:10:19.360> bit 00:10:19.509 --> 00:10:19.519 align:start position:0% do that you have to know a little bit 00:10:19.519 --> 00:10:20.550 align:start position:0% do that you have to know a little bit about<00:10:19.760> the<00:10:19.920> other<00:10:20.079> people 00:10:20.550 --> 00:10:20.560 align:start position:0% about the other people 00:10:20.560 --> 00:10:22.150 align:start position:0% about the other people um<00:10:20.880> and<00:10:21.040> you<00:10:21.200> know<00:10:21.360> it<00:10:21.760> understand<00:10:22.079> where 00:10:22.150 --> 00:10:22.160 align:start position:0% um and you know it understand where 00:10:22.160 --> 00:10:23.829 align:start position:0% um and you know it understand where they're<00:10:22.320> coming<00:10:22.560> from<00:10:22.720> a<00:10:22.800> little<00:10:22.880> bit<00:10:23.120> so 00:10:23.829 --> 00:10:23.839 align:start position:0% they're coming from a little bit so 00:10:23.839 --> 00:10:25.430 align:start position:0% they're coming from a little bit so that's<00:10:24.079> my<00:10:24.240> goal<00:10:24.480> here<00:10:24.800> so<00:10:24.959> i've<00:10:25.040> been<00:10:25.200> using 00:10:25.430 --> 00:10:25.440 align:start position:0% that's my goal here so i've been using 00:10:25.440 --> 00:10:27.430 align:start position:0% that's my goal here so i've been using closure<00:10:25.920> since<00:10:26.160> 2009 00:10:27.430 --> 00:10:27.440 align:start position:0% closure since 2009 00:10:27.440 --> 00:10:30.710 align:start position:0% closure since 2009 i<00:10:27.680> learned<00:10:28.000> it<00:10:28.079> when<00:10:28.320> i<00:10:28.399> was<00:10:28.640> a<00:10:28.800> student<00:10:30.000> and 00:10:30.710 --> 00:10:30.720 align:start position:0% i learned it when i was a student and 00:10:30.720 --> 00:10:35.030 align:start position:0% i learned it when i was a student and i<00:10:30.880> had<00:10:31.600> the<00:10:33.200> uh 00:10:35.030 --> 00:10:35.040 align:start position:0% i had the uh 00:10:35.040 --> 00:10:37.670 align:start position:0% i had the uh enthusiasm<00:10:35.760> of<00:10:35.839> the<00:10:36.000> new<00:10:36.240> convert<00:10:36.880> big<00:10:37.120> time 00:10:37.670 --> 00:10:37.680 align:start position:0% enthusiasm of the new convert big time 00:10:37.680 --> 00:10:38.870 align:start position:0% enthusiasm of the new convert big time because 00:10:38.870 --> 00:10:38.880 align:start position:0% because 00:10:38.880 --> 00:10:40.310 align:start position:0% because it<00:10:39.040> seemed<00:10:39.279> like<00:10:39.440> closure<00:10:39.760> was<00:10:39.920> the<00:10:40.000> end-all 00:10:40.310 --> 00:10:40.320 align:start position:0% it seemed like closure was the end-all 00:10:40.320 --> 00:10:41.670 align:start position:0% it seemed like closure was the end-all be-all<00:10:40.800> and<00:10:40.880> i<00:10:40.959> couldn't<00:10:41.200> believe<00:10:41.440> people 00:10:41.670 --> 00:10:41.680 align:start position:0% be-all and i couldn't believe people 00:10:41.680 --> 00:10:42.949 align:start position:0% be-all and i couldn't believe people were<00:10:41.839> using<00:10:42.160> java<00:10:42.480> that<00:10:42.640> was 00:10:42.949 --> 00:10:42.959 align:start position:0% were using java that was 00:10:42.959 --> 00:10:44.470 align:start position:0% were using java that was ridiculous<00:10:43.519> and<00:10:43.600> preposterous<00:10:44.240> and<00:10:44.320> there 00:10:44.470 --> 00:10:44.480 align:start position:0% ridiculous and preposterous and there 00:10:44.480 --> 00:10:45.430 align:start position:0% ridiculous and preposterous and there was<00:10:44.560> no<00:10:44.720> way<00:10:44.800> i<00:10:44.880> was<00:10:44.959> going<00:10:45.040> to<00:10:45.120> do<00:10:45.200> anything 00:10:45.430 --> 00:10:45.440 align:start position:0% was no way i was going to do anything 00:10:45.440 --> 00:10:46.790 align:start position:0% was no way i was going to do anything except<00:10:45.680> closure 00:10:46.790 --> 00:10:46.800 align:start position:0% except closure 00:10:46.800 --> 00:10:50.389 align:start position:0% except closure and<00:10:47.600> as<00:10:48.079> foolish<00:10:48.560> as<00:10:48.720> that<00:10:49.600> perspective<00:10:50.160> was 00:10:50.389 --> 00:10:50.399 align:start position:0% and as foolish as that perspective was 00:10:50.399 --> 00:10:51.590 align:start position:0% and as foolish as that perspective was it<00:10:50.480> turned<00:10:50.720> out<00:10:50.800> to<00:10:51.040> pay<00:10:51.200> pretty<00:10:51.440> huge 00:10:51.590 --> 00:10:51.600 align:start position:0% it turned out to pay pretty huge 00:10:51.600 --> 00:10:53.190 align:start position:0% it turned out to pay pretty huge dividends<00:10:52.079> for<00:10:52.240> my<00:10:52.399> career<00:10:52.720> and<00:10:52.880> for<00:10:53.040> my 00:10:53.190 --> 00:10:53.200 align:start position:0% dividends for my career and for my 00:10:53.200 --> 00:10:56.150 align:start position:0% dividends for my career and for my friend's<00:10:53.440> circles<00:10:53.839> and<00:10:54.000> everything<00:10:54.320> because 00:10:56.150 --> 00:10:56.160 align:start position:0% friend's circles and everything because 00:10:56.160 --> 00:10:59.110 align:start position:0% friend's circles and everything because going<00:10:56.560> all<00:10:56.800> in<00:10:56.959> on<00:10:57.200> something<00:10:58.399> is<00:10:58.560> valuable 00:10:59.110 --> 00:10:59.120 align:start position:0% going all in on something is valuable 00:10:59.120 --> 00:10:59.990 align:start position:0% going all in on something is valuable you<00:10:59.279> know<00:10:59.519> you<00:10:59.680> make 00:10:59.990 --> 00:11:00.000 align:start position:0% you know you make 00:11:00.000 --> 00:11:02.470 align:start position:0% you know you make these<00:11:00.160> lifelong<00:11:00.640> friends<00:11:00.959> and<00:11:01.040> connections 00:11:02.470 --> 00:11:02.480 align:start position:0% these lifelong friends and connections 00:11:02.480 --> 00:11:03.430 align:start position:0% these lifelong friends and connections you 00:11:03.430 --> 00:11:03.440 align:start position:0% you 00:11:03.440 --> 00:11:06.710 align:start position:0% you uh<00:11:04.720> are<00:11:04.880> exposed<00:11:05.360> to<00:11:05.920> ideas 00:11:06.710 --> 00:11:06.720 align:start position:0% uh are exposed to ideas 00:11:06.720 --> 00:11:09.030 align:start position:0% uh are exposed to ideas that<00:11:06.880> you<00:11:07.040> can<00:11:07.200> use<00:11:07.519> to<00:11:07.680> compare<00:11:08.480> other<00:11:08.720> ideas 00:11:09.030 --> 00:11:09.040 align:start position:0% that you can use to compare other ideas 00:11:09.040 --> 00:11:10.470 align:start position:0% that you can use to compare other ideas to<00:11:09.360> later 00:11:10.470 --> 00:11:10.480 align:start position:0% to later 00:11:10.480 --> 00:11:13.590 align:start position:0% to later and<00:11:10.720> i<00:11:10.880> know<00:11:11.279> anyone<00:11:11.519> who's<00:11:11.680> learned<00:11:12.000> closure 00:11:13.590 --> 00:11:13.600 align:start position:0% and i know anyone who's learned closure 00:11:13.600 --> 00:11:15.350 align:start position:0% and i know anyone who's learned closure pretty<00:11:13.920> much<00:11:14.240> compares<00:11:14.640> anything<00:11:14.959> anybody 00:11:15.350 --> 00:11:15.360 align:start position:0% pretty much compares anything anybody 00:11:15.360 --> 00:11:16.790 align:start position:0% pretty much compares anything anybody tells<00:11:15.600> them<00:11:16.240> about 00:11:16.790 --> 00:11:16.800 align:start position:0% tells them about 00:11:16.800 --> 00:11:19.509 align:start position:0% tells them about to<00:11:17.040> closure<00:11:17.600> right<00:11:17.839> i<00:11:17.920> mean<00:11:18.160> it's<00:11:18.320> like<00:11:18.560> okay 00:11:19.509 --> 00:11:19.519 align:start position:0% to closure right i mean it's like okay 00:11:19.519 --> 00:11:20.470 align:start position:0% to closure right i mean it's like okay what 00:11:20.470 --> 00:11:20.480 align:start position:0% what 00:11:20.480 --> 00:11:22.630 align:start position:0% what doesn't<00:11:20.800> this<00:11:21.040> do<00:11:21.279> that<00:11:21.440> closure<00:11:21.839> does<00:11:22.079> better 00:11:22.630 --> 00:11:22.640 align:start position:0% doesn't this do that closure does better 00:11:22.640 --> 00:11:24.150 align:start position:0% doesn't this do that closure does better is<00:11:22.800> kind<00:11:22.959> of<00:11:23.120> like<00:11:23.360> after<00:11:23.600> you<00:11:23.680> know<00:11:23.839> closure 00:11:24.150 --> 00:11:24.160 align:start position:0% is kind of like after you know closure 00:11:24.160 --> 00:11:27.590 align:start position:0% is kind of like after you know closure that's<00:11:24.320> kind<00:11:24.480> of<00:11:24.560> the<00:11:24.720> standard<00:11:25.120> you<00:11:25.279> hold 00:11:27.590 --> 00:11:27.600 align:start position:0% 00:11:27.600 --> 00:11:29.350 align:start position:0% at<00:11:27.680> least<00:11:27.920> i<00:11:28.000> did<00:11:28.160> for<00:11:28.320> a<00:11:28.399> while<00:11:28.720> and<00:11:28.880> tempered 00:11:29.350 --> 00:11:29.360 align:start position:0% at least i did for a while and tempered 00:11:29.360 --> 00:11:31.190 align:start position:0% at least i did for a while and tempered somewhat<00:11:29.760> there<00:11:30.399> um 00:11:31.190 --> 00:11:31.200 align:start position:0% somewhat there um 00:11:31.200 --> 00:11:33.670 align:start position:0% somewhat there um but<00:11:31.360> yeah<00:11:31.519> i<00:11:31.600> was<00:11:31.839> you<00:11:32.000> know<00:11:32.160> heavily<00:11:32.560> invested 00:11:33.670 --> 00:11:33.680 align:start position:0% but yeah i was you know heavily invested 00:11:33.680 --> 00:11:35.670 align:start position:0% but yeah i was you know heavily invested in<00:11:33.839> the<00:11:33.920> language<00:11:34.320> the<00:11:34.480> community<00:11:34.959> and<00:11:35.040> then 00:11:35.670 --> 00:11:35.680 align:start position:0% in the language the community and then 00:11:35.680 --> 00:11:38.550 align:start position:0% in the language the community and then uh<00:11:36.399> added<00:11:37.200> participated<00:11:37.920> in<00:11:38.000> the<00:11:38.079> creation<00:11:38.480> of 00:11:38.550 --> 00:11:38.560 align:start position:0% uh added participated in the creation of 00:11:38.560 --> 00:11:39.910 align:start position:0% uh added participated in the creation of new<00:11:38.720> tools<00:11:39.120> and<00:11:39.200> infrastructure<00:11:39.839> and 00:11:39.910 --> 00:11:39.920 align:start position:0% new tools and infrastructure and 00:11:39.920 --> 00:11:43.030 align:start position:0% new tools and infrastructure and libraries<00:11:40.399> and<00:11:40.839> stuff 00:11:43.030 --> 00:11:43.040 align:start position:0% libraries and stuff 00:11:43.040 --> 00:11:45.509 align:start position:0% libraries and stuff around<00:11:43.360> 2016<00:11:44.000> i<00:11:44.079> made<00:11:44.320> a<00:11:44.399> career<00:11:44.800> change<00:11:45.279> it 00:11:45.509 --> 00:11:45.519 align:start position:0% around 2016 i made a career change it 00:11:45.519 --> 00:11:47.030 align:start position:0% around 2016 i made a career change it seemed<00:11:45.680> like<00:11:45.839> there<00:11:46.000> was<00:11:46.079> an<00:11:46.240> opportunity<00:11:46.880> for 00:11:47.030 --> 00:11:47.040 align:start position:0% seemed like there was an opportunity for 00:11:47.040 --> 00:11:49.030 align:start position:0% seemed like there was an opportunity for me<00:11:47.360> to<00:11:47.680> apply 00:11:49.030 --> 00:11:49.040 align:start position:0% me to apply 00:11:49.040 --> 00:11:50.470 align:start position:0% me to apply the<00:11:49.200> skills<00:11:49.760> and<00:11:49.839> the<00:11:50.000> knowledge<00:11:50.320> i'd 00:11:50.470 --> 00:11:50.480 align:start position:0% the skills and the knowledge i'd 00:11:50.480 --> 00:11:52.150 align:start position:0% the skills and the knowledge i'd accumulated<00:11:51.120> in<00:11:51.200> the<00:11:51.279> closure<00:11:51.600> community<00:11:52.000> in 00:11:52.150 --> 00:11:52.160 align:start position:0% accumulated in the closure community in 00:11:52.160 --> 00:11:54.389 align:start position:0% accumulated in the closure community in a<00:11:52.240> new<00:11:52.560> context 00:11:54.389 --> 00:11:54.399 align:start position:0% a new context 00:11:54.399 --> 00:11:57.670 align:start position:0% a new context in<00:11:54.480> the<00:11:54.639> r<00:11:54.880> world<00:11:55.519> and<00:11:56.880> more<00:11:57.040> broadly<00:11:57.519> in 00:11:57.670 --> 00:11:57.680 align:start position:0% in the r world and more broadly in 00:11:57.680 --> 00:11:59.509 align:start position:0% in the r world and more broadly in scientific<00:11:58.160> computing 00:11:59.509 --> 00:11:59.519 align:start position:0% scientific computing 00:11:59.519 --> 00:12:02.949 align:start position:0% scientific computing and<00:12:00.720> i<00:12:00.959> think 00:12:02.949 --> 00:12:02.959 align:start position:0% and i think 00:12:02.959 --> 00:12:05.670 align:start position:0% and i think this<00:12:03.200> is<00:12:03.680> this<00:12:03.839> is<00:12:04.000> a<00:12:04.079> trend<00:12:04.639> uh<00:12:05.120> the<00:12:05.279> concept 00:12:05.670 --> 00:12:05.680 align:start position:0% this is this is a trend uh the concept 00:12:05.680 --> 00:12:07.110 align:start position:0% this is this is a trend uh the concept of<00:12:05.760> data<00:12:06.079> scientists<00:12:06.560> the<00:12:06.720> concept<00:12:07.040> of 00:12:07.110 --> 00:12:07.120 align:start position:0% of data scientists the concept of 00:12:07.120 --> 00:12:08.389 align:start position:0% of data scientists the concept of scientific<00:12:07.600> computing 00:12:08.389 --> 00:12:08.399 align:start position:0% scientific computing 00:12:08.399 --> 00:12:09.750 align:start position:0% scientific computing i<00:12:08.560> remember<00:12:08.800> when<00:12:09.040> i<00:12:09.120> was<00:12:09.279> in<00:12:09.360> college 00:12:09.750 --> 00:12:09.760 align:start position:0% i remember when i was in college 00:12:09.760 --> 00:12:12.069 align:start position:0% i remember when i was in college scientific<00:12:10.240> computing<00:12:11.040> meant 00:12:12.069 --> 00:12:12.079 align:start position:0% scientific computing meant 00:12:12.079 --> 00:12:15.110 align:start position:0% scientific computing meant like<00:12:12.240> grid<00:12:12.560> computing<00:12:13.040> with<00:12:13.279> c<00:12:14.000> and<00:12:14.240> mpi<00:12:14.959> and 00:12:15.110 --> 00:12:15.120 align:start position:0% like grid computing with c and mpi and 00:12:15.120 --> 00:12:16.150 align:start position:0% like grid computing with c and mpi and stuff<00:12:15.279> like<00:12:15.440> that<00:12:15.760> and<00:12:15.920> i 00:12:16.150 --> 00:12:16.160 align:start position:0% stuff like that and i 00:12:16.160 --> 00:12:17.990 align:start position:0% stuff like that and i vaguely<00:12:16.720> was<00:12:16.880> aware<00:12:17.200> that<00:12:17.360> this<00:12:17.519> was<00:12:17.680> going<00:12:17.839> on 00:12:17.990 --> 00:12:18.000 align:start position:0% vaguely was aware that this was going on 00:12:18.000 --> 00:12:20.069 align:start position:0% vaguely was aware that this was going on i<00:12:18.160> never<00:12:18.320> participated<00:12:19.120> in<00:12:19.279> it 00:12:20.069 --> 00:12:20.079 align:start position:0% i never participated in it 00:12:20.079 --> 00:12:21.910 align:start position:0% i never participated in it but<00:12:20.320> i<00:12:20.399> think<00:12:20.639> since<00:12:20.880> then<00:12:21.279> the<00:12:21.440> concept<00:12:21.839> of 00:12:21.910 --> 00:12:21.920 align:start position:0% but i think since then the concept of 00:12:21.920 --> 00:12:24.389 align:start position:0% but i think since then the concept of data<00:12:22.240> science<00:12:22.800> has<00:12:23.040> opened<00:12:23.360> up<00:12:23.519> significantly 00:12:24.389 --> 00:12:24.399 align:start position:0% data science has opened up significantly 00:12:24.399 --> 00:12:28.310 align:start position:0% data science has opened up significantly to<00:12:24.560> the<00:12:24.639> point<00:12:24.880> where<00:12:27.120> we<00:12:27.279> have<00:12:27.440> a<00:12:27.600> category<00:12:28.160> of 00:12:28.310 --> 00:12:28.320 align:start position:0% to the point where we have a category of 00:12:28.320 --> 00:12:30.389 align:start position:0% to the point where we have a category of person<00:12:28.720> who<00:12:28.880> is<00:12:29.040> a<00:12:29.200> new<00:12:29.440> programmer<00:12:30.000> who<00:12:30.160> needs 00:12:30.389 --> 00:12:30.399 align:start position:0% person who is a new programmer who needs 00:12:30.399 --> 00:12:32.150 align:start position:0% person who is a new programmer who needs to<00:12:30.560> explore<00:12:31.040> data 00:12:32.150 --> 00:12:32.160 align:start position:0% to explore data 00:12:32.160 --> 00:12:33.990 align:start position:0% to explore data and<00:12:32.560> that's<00:12:32.800> interesting<00:12:33.200> because<00:12:33.519> i<00:12:33.680> think 00:12:33.990 --> 00:12:34.000 align:start position:0% and that's interesting because i think 00:12:34.000 --> 00:12:35.829 align:start position:0% and that's interesting because i think that's<00:12:34.480> pretty<00:12:34.720> much<00:12:34.959> the<00:12:35.200> same<00:12:35.519> kind<00:12:35.680> of 00:12:35.829 --> 00:12:35.839 align:start position:0% that's pretty much the same kind of 00:12:35.839 --> 00:12:36.389 align:start position:0% that's pretty much the same kind of person 00:12:36.389 --> 00:12:36.399 align:start position:0% person 00:12:36.399 --> 00:12:38.470 align:start position:0% person as<00:12:36.720> someone<00:12:37.040> who's<00:12:37.360> using<00:12:37.760> a<00:12:38.160> dynamic 00:12:38.470 --> 00:12:38.480 align:start position:0% as someone who's using a dynamic 00:12:38.480 --> 00:12:39.509 align:start position:0% as someone who's using a dynamic language<00:12:38.800> for<00:12:38.880> the<00:12:38.959> first<00:12:39.200> time 00:12:39.509 --> 00:12:39.519 align:start position:0% language for the first time 00:12:39.519 --> 00:12:40.870 align:start position:0% language for the first time programmer<00:12:40.000> or<00:12:40.079> not<00:12:40.399> you<00:12:40.480> know<00:12:40.639> it's<00:12:40.720> all 00:12:40.870 --> 00:12:40.880 align:start position:0% programmer or not you know it's all 00:12:40.880 --> 00:12:43.269 align:start position:0% programmer or not you know it's all about<00:12:41.839> working<00:12:42.160> your<00:12:42.320> way<00:12:42.480> through<00:12:42.639> dad<00:12:42.959> data 00:12:43.269 --> 00:12:43.279 align:start position:0% about working your way through dad data 00:12:43.279 --> 00:12:45.910 align:start position:0% about working your way through dad data finding<00:12:43.680> patterns<00:12:44.160> defining<00:12:44.639> patterns 00:12:45.910 --> 00:12:45.920 align:start position:0% finding patterns defining patterns 00:12:45.920 --> 00:12:47.670 align:start position:0% finding patterns defining patterns uh<00:12:46.160> carrying<00:12:46.560> yourself<00:12:46.959> to<00:12:47.120> new<00:12:47.279> levels<00:12:47.519> of 00:12:47.670 --> 00:12:47.680 align:start position:0% uh carrying yourself to new levels of 00:12:47.680 --> 00:12:49.190 align:start position:0% uh carrying yourself to new levels of understanding<00:12:48.079> of<00:12:48.160> the<00:12:48.320> data<00:12:48.720> filling<00:12:49.040> in<00:12:49.120> the 00:12:49.190 --> 00:12:49.200 align:start position:0% understanding of the data filling in the 00:12:49.200 --> 00:12:51.190 align:start position:0% understanding of the data filling in the gaps<00:12:49.440> with<00:12:49.600> abstractions<00:12:50.160> and<00:12:50.320> so<00:12:50.480> on 00:12:51.190 --> 00:12:51.200 align:start position:0% gaps with abstractions and so on 00:12:51.200 --> 00:12:53.430 align:start position:0% gaps with abstractions and so on so<00:12:51.680> this<00:12:52.079> this<00:12:52.399> little<00:12:52.800> period<00:12:53.120> in<00:12:53.200> my<00:12:53.279> life 00:12:53.430 --> 00:12:53.440 align:start position:0% so this this little period in my life 00:12:53.440 --> 00:12:54.470 align:start position:0% so this this little period in my life when<00:12:53.600> i<00:12:53.680> was<00:12:53.760> doing<00:12:54.000> r 00:12:54.470 --> 00:12:54.480 align:start position:0% when i was doing r 00:12:54.480 --> 00:12:56.470 align:start position:0% when i was doing r and<00:12:54.639> javascript<00:12:55.279> and<00:12:55.760> immersed<00:12:56.079> in<00:12:56.160> the<00:12:56.240> data 00:12:56.470 --> 00:12:56.480 align:start position:0% and javascript and immersed in the data 00:12:56.480 --> 00:12:58.870 align:start position:0% and javascript and immersed in the data science<00:12:56.720> world<00:12:57.040> was<00:12:57.440> really<00:12:57.680> interesting 00:12:58.870 --> 00:12:58.880 align:start position:0% science world was really interesting 00:12:58.880 --> 00:13:00.790 align:start position:0% science world was really interesting and<00:12:59.279> my<00:12:59.440> experience<00:12:59.760> with<00:12:59.920> closure<00:13:00.240> paid<00:13:00.480> off 00:13:00.790 --> 00:13:00.800 align:start position:0% and my experience with closure paid off 00:13:00.800 --> 00:13:04.710 align:start position:0% and my experience with closure paid off there 00:13:04.710 --> 00:13:04.720 align:start position:0% 00:13:04.720 --> 00:13:08.550 align:start position:0% in<00:13:04.959> parallel<00:13:05.440> to<00:13:05.519> all<00:13:05.680> of<00:13:05.839> this<00:13:07.120> back<00:13:07.440> in<00:13:07.600> 2010 00:13:08.550 --> 00:13:08.560 align:start position:0% in parallel to all of this back in 2010 00:13:08.560 --> 00:13:11.829 align:start position:0% in parallel to all of this back in 2010 i<00:13:08.880> was<00:13:09.120> working<00:13:09.519> at<00:13:09.920> what<00:13:10.079> was<00:13:10.320> then<00:13:10.560> relevance 00:13:11.829 --> 00:13:11.839 align:start position:0% i was working at what was then relevance 00:13:11.839 --> 00:13:13.829 align:start position:0% i was working at what was then relevance and<00:13:12.240> we<00:13:12.399> had<00:13:12.560> a<00:13:12.639> concept<00:13:13.040> of<00:13:13.200> open<00:13:13.519> source 00:13:13.829 --> 00:13:13.839 align:start position:0% and we had a concept of open source 00:13:13.839 --> 00:13:15.590 align:start position:0% and we had a concept of open source fridays<00:13:14.639> where<00:13:14.959> we<00:13:15.200> would 00:13:15.590 --> 00:13:15.600 align:start position:0% fridays where we would 00:13:15.600 --> 00:13:18.550 align:start position:0% fridays where we would do<00:13:15.760> some<00:13:15.920> open<00:13:16.160> source<00:13:16.480> stuff<00:13:18.160> and<00:13:18.240> we<00:13:18.399> were 00:13:18.550 --> 00:13:18.560 align:start position:0% do some open source stuff and we were 00:13:18.560 --> 00:13:19.509 align:start position:0% do some open source stuff and we were paid<00:13:18.720> to<00:13:18.880> do<00:13:19.040> that 00:13:19.509 --> 00:13:19.519 align:start position:0% paid to do that 00:13:19.519 --> 00:13:22.069 align:start position:0% paid to do that and<00:13:20.240> i<00:13:20.399> was<00:13:20.959> helping<00:13:21.360> out<00:13:21.519> with<00:13:21.839> like 00:13:22.069 --> 00:13:22.079 align:start position:0% and i was helping out with like 00:13:22.079 --> 00:13:24.870 align:start position:0% and i was helping out with like low-hanging<00:13:22.639> fruit<00:13:23.040> and<00:13:23.120> closure<00:13:23.600> itself 00:13:24.870 --> 00:13:24.880 align:start position:0% low-hanging fruit and closure itself 00:13:24.880 --> 00:13:27.990 align:start position:0% low-hanging fruit and closure itself and<00:13:25.680> closures<00:13:26.320> plus 00:13:27.990 --> 00:13:28.000 align:start position:0% and closures plus 00:13:28.000 --> 00:13:31.350 align:start position:0% and closures plus function<00:13:29.600> uh 00:13:31.350 --> 00:13:31.360 align:start position:0% function uh 00:13:31.360 --> 00:13:33.509 align:start position:0% function uh and<00:13:32.160> functions<00:13:32.560> in<00:13:32.639> closure<00:13:33.040> generally 00:13:33.509 --> 00:13:33.519 align:start position:0% and functions in closure generally 00:13:33.519 --> 00:13:35.110 align:start position:0% and functions in closure generally support<00:13:34.000> something<00:13:34.399> called 00:13:35.110 --> 00:13:35.120 align:start position:0% support something called 00:13:35.120 --> 00:13:38.230 align:start position:0% support something called inlining<00:13:36.000> and<00:13:36.160> what<00:13:36.320> that<00:13:36.480> means<00:13:36.800> is 00:13:38.230 --> 00:13:38.240 align:start position:0% inlining and what that means is 00:13:38.240 --> 00:13:41.030 align:start position:0% inlining and what that means is in<00:13:39.199> like<00:13:39.440> syntactic<00:13:40.240> instances<00:13:40.800> of 00:13:41.030 --> 00:13:41.040 align:start position:0% in like syntactic instances of 00:13:41.040 --> 00:13:43.430 align:start position:0% in like syntactic instances of expressions<00:13:41.519> like<00:13:41.760> plus<00:13:42.160> one<00:13:42.399> two 00:13:43.430 --> 00:13:43.440 align:start position:0% expressions like plus one two 00:13:43.440 --> 00:13:46.710 align:start position:0% expressions like plus one two can<00:13:43.680> get<00:13:44.160> replaced<00:13:45.199> at<00:13:45.360> compile<00:13:45.920> time 00:13:46.710 --> 00:13:46.720 align:start position:0% can get replaced at compile time 00:13:46.720 --> 00:13:50.550 align:start position:0% can get replaced at compile time with<00:13:46.959> a<00:13:47.120> call<00:13:47.440> to<00:13:48.320> i<00:13:48.399> think<00:13:48.560> it's<00:13:48.800> closure 00:13:50.550 --> 00:13:50.560 align:start position:0% with a call to i think it's closure 00:13:50.560 --> 00:13:52.710 align:start position:0% with a call to i think it's closure math<00:13:51.440> ad<00:13:51.839> or<00:13:52.000> something<00:13:52.240> like<00:13:52.399> that<00:13:52.560> like 00:13:52.710 --> 00:13:52.720 align:start position:0% math ad or something like that like 00:13:52.720 --> 00:13:54.550 align:start position:0% math ad or something like that like there's<00:13:52.959> a<00:13:53.040> java<00:13:53.440> static<00:13:53.760> method<00:13:54.079> underneath 00:13:54.550 --> 00:13:54.560 align:start position:0% there's a java static method underneath 00:13:54.560 --> 00:13:56.150 align:start position:0% there's a java static method underneath closures<00:13:54.959> plus 00:13:56.150 --> 00:13:56.160 align:start position:0% closures plus 00:13:56.160 --> 00:13:58.389 align:start position:0% closures plus and<00:13:56.639> if<00:13:56.959> you<00:13:57.120> can<00:13:57.360> replace<00:13:57.760> the<00:13:57.920> function<00:13:58.240> call 00:13:58.389 --> 00:13:58.399 align:start position:0% and if you can replace the function call 00:13:58.399 --> 00:13:59.670 align:start position:0% and if you can replace the function call to<00:13:58.560> plus 00:13:59.670 --> 00:13:59.680 align:start position:0% to plus 00:13:59.680 --> 00:14:02.230 align:start position:0% to plus with<00:14:00.000> a<00:14:00.079> direct<00:14:00.560> call<00:14:00.880> to<00:14:01.040> the<00:14:01.360> java<00:14:01.760> static 00:14:02.230 --> 00:14:02.240 align:start position:0% with a direct call to the java static 00:14:02.240 --> 00:14:04.230 align:start position:0% with a direct call to the java static method<00:14:02.639> without<00:14:02.959> any<00:14:03.120> variatic<00:14:03.600> arguments 00:14:04.230 --> 00:14:04.240 align:start position:0% method without any variatic arguments 00:14:04.240 --> 00:14:05.509 align:start position:0% method without any variatic arguments then<00:14:04.480> you<00:14:04.560> get<00:14:04.639> a<00:14:04.800> slight<00:14:05.040> performance 00:14:05.509 --> 00:14:05.519 align:start position:0% then you get a slight performance 00:14:05.519 --> 00:14:07.910 align:start position:0% then you get a slight performance improvement<00:14:07.040> and 00:14:07.910 --> 00:14:07.920 align:start position:0% improvement and 00:14:07.920 --> 00:14:09.590 align:start position:0% improvement and when<00:14:08.160> i<00:14:08.240> was<00:14:08.639> studying<00:14:09.120> i've<00:14:09.199> never<00:14:09.360> seen 00:14:09.590 --> 00:14:09.600 align:start position:0% when i was studying i've never seen 00:14:09.600 --> 00:14:11.189 align:start position:0% when i was studying i've never seen anything<00:14:09.839> like<00:14:10.000> this<00:14:10.160> before<00:14:10.480> it's<00:14:10.639> like<00:14:10.800> a 00:14:11.189 --> 00:14:11.199 align:start position:0% anything like this before it's like a 00:14:11.199 --> 00:14:13.829 align:start position:0% anything like this before it's like a dual<00:14:12.000> headed<00:14:12.480> function<00:14:13.040> and<00:14:13.199> macro<00:14:13.680> because 00:14:13.829 --> 00:14:13.839 align:start position:0% dual headed function and macro because 00:14:13.839 --> 00:14:16.310 align:start position:0% dual headed function and macro because plus<00:14:14.079> is<00:14:14.240> a<00:14:14.320> function<00:14:14.639> not<00:14:14.800> a<00:14:14.959> macro<00:14:15.920> but<00:14:16.079> there 00:14:16.310 --> 00:14:16.320 align:start position:0% plus is a function not a macro but there 00:14:16.320 --> 00:14:16.790 align:start position:0% plus is a function not a macro but there is<00:14:16.480> a 00:14:16.790 --> 00:14:16.800 align:start position:0% is a 00:14:16.800 --> 00:14:18.550 align:start position:0% is a an<00:14:17.040> understanding<00:14:17.519> of<00:14:17.600> a<00:14:17.680> kind<00:14:17.920> of<00:14:18.000> macro<00:14:18.399> that 00:14:18.550 --> 00:14:18.560 align:start position:0% an understanding of a kind of macro that 00:14:18.560 --> 00:14:20.230 align:start position:0% an understanding of a kind of macro that is<00:14:18.720> applicable<00:14:19.279> to<00:14:19.440> even<00:14:19.680> functions<00:14:20.079> like 00:14:20.230 --> 00:14:20.240 align:start position:0% is applicable to even functions like 00:14:20.240 --> 00:14:23.269 align:start position:0% is applicable to even functions like plus<00:14:20.560> and<00:14:20.720> so<00:14:20.880> that<00:14:21.040> was<00:14:21.199> new<00:14:21.360> to<00:14:21.519> me 00:14:23.269 --> 00:14:23.279 align:start position:0% plus and so that was new to me 00:14:23.279 --> 00:14:25.509 align:start position:0% plus and so that was new to me and<00:14:23.519> it<00:14:23.600> turns<00:14:23.839> out<00:14:23.920> the<00:14:24.480> optimization<00:14:25.440> is 00:14:25.509 --> 00:14:25.519 align:start position:0% and it turns out the optimization is 00:14:25.519 --> 00:14:27.910 align:start position:0% and it turns out the optimization is called<00:14:25.839> broadly<00:14:26.320> compiler<00:14:26.800> macros 00:14:27.910 --> 00:14:27.920 align:start position:0% called broadly compiler macros 00:14:27.920 --> 00:14:30.069 align:start position:0% called broadly compiler macros and<00:14:28.079> this<00:14:28.240> is<00:14:28.399> a<00:14:28.480> feature<00:14:28.880> of<00:14:28.959> common<00:14:29.279> lisp<00:14:29.839> and 00:14:30.069 --> 00:14:30.079 align:start position:0% and this is a feature of common lisp and 00:14:30.079 --> 00:14:31.350 align:start position:0% and this is a feature of common lisp and that's<00:14:30.320> where<00:14:30.560> rich<00:14:30.800> got<00:14:30.959> the<00:14:31.120> idea 00:14:31.350 --> 00:14:31.360 align:start position:0% that's where rich got the idea 00:14:31.360 --> 00:14:32.550 align:start position:0% that's where rich got the idea presumably 00:14:32.550 --> 00:14:32.560 align:start position:0% presumably 00:14:32.560 --> 00:14:34.870 align:start position:0% presumably so<00:14:33.279> he<00:14:33.440> told<00:14:33.600> me<00:14:33.760> this<00:14:33.920> and<00:14:34.079> sent<00:14:34.240> me<00:14:34.399> over<00:14:34.639> to 00:14:34.870 --> 00:14:34.880 align:start position:0% so he told me this and sent me over to 00:14:34.880 --> 00:14:35.670 align:start position:0% so he told me this and sent me over to the<00:14:35.120> lisp 00:14:35.670 --> 00:14:35.680 align:start position:0% the lisp 00:14:35.680 --> 00:14:37.990 align:start position:0% the lisp documentation<00:14:37.040> and<00:14:37.199> i<00:14:37.360> landed<00:14:37.680> on<00:14:37.760> something 00:14:37.990 --> 00:14:38.000 align:start position:0% documentation and i landed on something 00:14:38.000 --> 00:14:39.430 align:start position:0% documentation and i landed on something called<00:14:38.160> the<00:14:38.240> hyperspec<00:14:38.880> which<00:14:39.040> i'll<00:14:39.120> show<00:14:39.279> you 00:14:39.430 --> 00:14:39.440 align:start position:0% called the hyperspec which i'll show you 00:14:39.440 --> 00:14:39.910 align:start position:0% called the hyperspec which i'll show you later 00:14:39.910 --> 00:14:39.920 align:start position:0% later 00:14:39.920 --> 00:14:43.430 align:start position:0% later but<00:14:41.440> i<00:14:41.519> was<00:14:41.680> really<00:14:42.000> impressed<00:14:42.560> with<00:14:42.800> the 00:14:43.430 --> 00:14:43.440 align:start position:0% but i was really impressed with the 00:14:43.440 --> 00:14:45.750 align:start position:0% but i was really impressed with the depth<00:14:43.920> and<00:14:44.079> breadth<00:14:44.639> of<00:14:44.880> the<00:14:45.040> common<00:14:45.360> lisp 00:14:45.750 --> 00:14:45.760 align:start position:0% depth and breadth of the common lisp 00:14:45.760 --> 00:14:47.189 align:start position:0% depth and breadth of the common lisp documentation<00:14:46.560> because<00:14:46.880> beyond<00:14:47.120> the 00:14:47.189 --> 00:14:47.199 align:start position:0% documentation because beyond the 00:14:47.199 --> 00:14:50.310 align:start position:0% documentation because beyond the hyperspec<00:14:47.920> you've<00:14:48.079> got<00:14:48.240> dozens<00:14:48.720> of<00:14:48.880> books<00:14:49.360> and 00:14:50.310 --> 00:14:50.320 align:start position:0% hyperspec you've got dozens of books and 00:14:50.320 --> 00:14:53.910 align:start position:0% hyperspec you've got dozens of books and technical<00:14:50.959> articles<00:14:51.600> and<00:14:51.920> academic<00:14:52.480> articles 00:14:53.910 --> 00:14:53.920 align:start position:0% technical articles and academic articles 00:14:53.920 --> 00:14:55.350 align:start position:0% technical articles and academic articles and<00:14:54.240> i<00:14:54.399> found<00:14:54.639> myself<00:14:54.880> getting<00:14:55.120> kind<00:14:55.279> of 00:14:55.350 --> 00:14:55.360 align:start position:0% and i found myself getting kind of 00:14:55.360 --> 00:14:58.150 align:start position:0% and i found myself getting kind of distracted<00:14:55.839> by<00:14:56.000> it<00:14:56.160> and<00:14:56.480> kind<00:14:56.839> of 00:14:58.150 --> 00:14:58.160 align:start position:0% distracted by it and kind of 00:14:58.160 --> 00:14:59.990 align:start position:0% distracted by it and kind of being<00:14:58.399> more<00:14:58.639> interested<00:14:59.120> in<00:14:59.519> learning<00:14:59.760> about 00:14:59.990 --> 00:15:00.000 align:start position:0% being more interested in learning about 00:15:00.000 --> 00:15:01.670 align:start position:0% being more interested in learning about common<00:15:00.240> lisp<00:15:00.560> and<00:15:00.639> then<00:15:00.880> making<00:15:01.199> closures 00:15:01.670 --> 00:15:01.680 align:start position:0% common lisp and then making closures 00:15:01.680 --> 00:15:03.030 align:start position:0% common lisp and then making closures plus 00:15:03.030 --> 00:15:03.040 align:start position:0% plus 00:15:03.040 --> 00:15:04.870 align:start position:0% plus as<00:15:03.199> fast<00:15:03.519> as<00:15:03.680> possible<00:15:04.000> and<00:15:04.079> i<00:15:04.160> had<00:15:04.240> to<00:15:04.320> kind<00:15:04.480> of 00:15:04.870 --> 00:15:04.880 align:start position:0% as fast as possible and i had to kind of 00:15:04.880 --> 00:15:06.790 align:start position:0% as fast as possible and i had to kind of consciously<00:15:05.839> step<00:15:06.079> back<00:15:06.240> from<00:15:06.399> the<00:15:06.480> common 00:15:06.790 --> 00:15:06.800 align:start position:0% consciously step back from the common 00:15:06.800 --> 00:15:09.110 align:start position:0% consciously step back from the common list<00:15:07.040> thing<00:15:07.199> to<00:15:07.279> get<00:15:07.360> back<00:15:07.519> to<00:15:07.600> my<00:15:07.760> work 00:15:09.110 --> 00:15:09.120 align:start position:0% list thing to get back to my work 00:15:09.120 --> 00:15:13.509 align:start position:0% list thing to get back to my work but<00:15:10.399> uh<00:15:10.639> that<00:15:10.800> was<00:15:10.959> my<00:15:11.040> first<00:15:11.279> glimpse 00:15:13.509 --> 00:15:13.519 align:start position:0% but uh that was my first glimpse 00:15:13.519 --> 00:15:16.310 align:start position:0% but uh that was my first glimpse um<00:15:13.839> since<00:15:14.160> then<00:15:14.639> i<00:15:14.880> have<00:15:15.120> not<00:15:15.360> used<00:15:15.839> lisp 00:15:16.310 --> 00:15:16.320 align:start position:0% um since then i have not used lisp 00:15:16.320 --> 00:15:18.230 align:start position:0% um since then i have not used lisp professionally<00:15:16.880> at<00:15:17.040> all<00:15:17.120> i'm<00:15:17.360> like<00:15:17.600> uh<00:15:17.839> i'm 00:15:18.230 --> 00:15:18.240 align:start position:0% professionally at all i'm like uh i'm 00:15:18.240 --> 00:15:21.030 align:start position:0% professionally at all i'm like uh i'm i'm<00:15:18.480> an<00:15:18.639> enthusiast<00:15:19.600> uh<00:15:19.920> it's<00:15:20.160> a<00:15:20.399> hobby<00:15:20.800> thing 00:15:21.030 --> 00:15:21.040 align:start position:0% i'm an enthusiast uh it's a hobby thing 00:15:21.040 --> 00:15:22.069 align:start position:0% i'm an enthusiast uh it's a hobby thing for<00:15:21.199> me 00:15:22.069 --> 00:15:22.079 align:start position:0% for me 00:15:22.079 --> 00:15:24.629 align:start position:0% for me um<00:15:22.720> and<00:15:22.880> i<00:15:23.040> should<00:15:23.199> say<00:15:23.440> further<00:15:23.839> that<00:15:24.399> not 00:15:24.629 --> 00:15:24.639 align:start position:0% um and i should say further that not 00:15:24.639 --> 00:15:26.470 align:start position:0% um and i should say further that not only<00:15:24.959> am<00:15:25.120> i<00:15:25.279> an<00:15:25.440> enthusiast<00:15:25.920> and<00:15:26.079> not<00:15:26.240> use<00:15:26.399> it 00:15:26.470 --> 00:15:26.480 align:start position:0% only am i an enthusiast and not use it 00:15:26.480 --> 00:15:27.910 align:start position:0% only am i an enthusiast and not use it professionally<00:15:27.040> i<00:15:27.120> don't<00:15:27.279> even<00:15:27.519> really<00:15:27.680> know 00:15:27.910 --> 00:15:27.920 align:start position:0% professionally i don't even really know 00:15:27.920 --> 00:15:28.310 align:start position:0% professionally i don't even really know how 00:15:28.310 --> 00:15:28.320 align:start position:0% how 00:15:28.320 --> 00:15:30.470 align:start position:0% how you<00:15:28.480> would<00:15:28.639> use<00:15:28.880> it<00:15:28.959> professionally<00:15:30.079> i<00:15:30.240> have 00:15:30.470 --> 00:15:30.480 align:start position:0% you would use it professionally i have 00:15:30.480 --> 00:15:32.629 align:start position:0% you would use it professionally i have vague<00:15:30.800> ideas<00:15:31.279> about<00:15:31.680> and<00:15:31.839> i<00:15:31.920> know 00:15:32.629 --> 00:15:32.639 align:start position:0% vague ideas about and i know 00:15:32.639 --> 00:15:34.069 align:start position:0% vague ideas about and i know more<00:15:32.880> or<00:15:32.959> less<00:15:33.199> the<00:15:33.360> affordances<00:15:33.920> of<00:15:34.000> the 00:15:34.069 --> 00:15:34.079 align:start position:0% more or less the affordances of the 00:15:34.079 --> 00:15:36.870 align:start position:0% more or less the affordances of the different<00:15:34.320> implementations<00:15:34.959> and<00:15:35.040> so<00:15:35.199> on 00:15:36.870 --> 00:15:36.880 align:start position:0% different implementations and so on 00:15:36.880 --> 00:15:39.430 align:start position:0% different implementations and so on but<00:15:38.240> one<00:15:38.399> of<00:15:38.480> the<00:15:38.560> things<00:15:38.880> i<00:15:38.959> would<00:15:39.120> hate<00:15:39.279> for 00:15:39.430 --> 00:15:39.440 align:start position:0% but one of the things i would hate for 00:15:39.440 --> 00:15:39.990 align:start position:0% but one of the things i would hate for anyone<00:15:39.680> to<00:15:39.759> take 00:15:39.990 --> 00:15:40.000 align:start position:0% anyone to take 00:15:40.000 --> 00:15:42.949 align:start position:0% anyone to take from<00:15:40.079> this<00:15:40.240> talk<00:15:40.639> is<00:15:42.480> i'm<00:15:42.639> going<00:15:42.720> to<00:15:42.800> use 00:15:42.949 --> 00:15:42.959 align:start position:0% from this talk is i'm going to use 00:15:42.959 --> 00:15:44.949 align:start position:0% from this talk is i'm going to use common<00:15:43.279> lisp<00:15:43.519> at<00:15:43.600> work<00:15:44.000> because<00:15:44.320> alan<00:15:44.560> diaper 00:15:44.949 --> 00:15:44.959 align:start position:0% common lisp at work because alan diaper 00:15:44.959 --> 00:15:45.749 align:start position:0% common lisp at work because alan diaper told<00:15:45.120> me<00:15:45.360> to 00:15:45.749 --> 00:15:45.759 align:start position:0% told me to 00:15:45.759 --> 00:15:47.030 align:start position:0% told me to and<00:15:46.240> i<00:15:46.320> don't<00:15:46.480> i<00:15:46.560> don't<00:15:46.639> want<00:15:46.720> to<00:15:46.800> be<00:15:46.880> on<00:15:46.959> the 00:15:47.030 --> 00:15:47.040 align:start position:0% and i don't i don't want to be on the 00:15:47.040 --> 00:15:48.629 align:start position:0% and i don't i don't want to be on the hook<00:15:47.199> for<00:15:47.360> that<00:15:47.600> okay<00:15:48.079> the<00:15:48.320> career 00:15:48.629 --> 00:15:48.639 align:start position:0% hook for that okay the career 00:15:48.639 --> 00:15:50.389 align:start position:0% hook for that okay the career consequences<00:15:49.279> for<00:15:49.440> you<00:15:49.600> are<00:15:49.680> undefined 00:15:50.389 --> 00:15:50.399 align:start position:0% consequences for you are undefined 00:15:50.399 --> 00:15:53.189 align:start position:0% consequences for you are undefined okay<00:15:51.120> so<00:15:51.279> for<00:15:51.440> me<00:15:51.600> this<00:15:51.839> is<00:15:51.920> a<00:15:52.000> hobby<00:15:52.560> and<00:15:53.040> by 00:15:53.189 --> 00:15:53.199 align:start position:0% okay so for me this is a hobby and by 00:15:53.199 --> 00:15:54.310 align:start position:0% okay so for me this is a hobby and by that<00:15:53.360> same<00:15:53.600> token 00:15:54.310 --> 00:15:54.320 align:start position:0% that same token 00:15:54.320 --> 00:15:57.189 align:start position:0% that same token i'm<00:15:54.480> not<00:15:54.639> an<00:15:54.800> expert<00:15:55.199> at<00:15:55.279> common<00:15:55.600> list<00:15:56.079> i'm<00:15:56.639> if 00:15:57.189 --> 00:15:57.199 align:start position:0% i'm not an expert at common list i'm if 00:15:57.199 --> 00:15:58.790 align:start position:0% i'm not an expert at common list i'm if i'm<00:15:57.440> closest<00:15:57.920> to<00:15:58.000> being<00:15:58.320> something<00:15:58.560> like<00:15:58.720> an 00:15:58.790 --> 00:15:58.800 align:start position:0% i'm closest to being something like an 00:15:58.800 --> 00:16:00.230 align:start position:0% i'm closest to being something like an expert<00:15:59.199> in<00:15:59.279> closure 00:16:00.230 --> 00:16:00.240 align:start position:0% expert in closure 00:16:00.240 --> 00:16:01.749 align:start position:0% expert in closure but<00:16:00.399> i<00:16:00.480> cannot<00:16:00.800> claim<00:16:01.040> to<00:16:01.120> be<00:16:01.199> an<00:16:01.360> expert<00:16:01.680> in 00:16:01.749 --> 00:16:01.759 align:start position:0% but i cannot claim to be an expert in 00:16:01.759 --> 00:16:03.749 align:start position:0% but i cannot claim to be an expert in common<00:16:02.079> lists<00:16:02.240> but<00:16:02.480> i<00:16:02.560> think<00:16:03.120> lack<00:16:03.360> of<00:16:03.600> real 00:16:03.749 --> 00:16:03.759 align:start position:0% common lists but i think lack of real 00:16:03.759 --> 00:16:05.269 align:start position:0% common lists but i think lack of real production<00:16:04.160> experience<00:16:04.639> is<00:16:04.800> probably<00:16:05.040> what 00:16:05.269 --> 00:16:05.279 align:start position:0% production experience is probably what 00:16:05.279 --> 00:16:07.110 align:start position:0% production experience is probably what keeps<00:16:05.519> me<00:16:05.680> from<00:16:05.839> that 00:16:07.110 --> 00:16:07.120 align:start position:0% keeps me from that 00:16:07.120 --> 00:16:08.550 align:start position:0% keeps me from that but<00:16:07.440> maybe<00:16:07.759> in<00:16:07.839> the<00:16:07.920> future<00:16:08.240> it'll<00:16:08.399> be 00:16:08.550 --> 00:16:08.560 align:start position:0% but maybe in the future it'll be 00:16:08.560 --> 00:16:09.590 align:start position:0% but maybe in the future it'll be something<00:16:08.800> i'll<00:16:08.880> be<00:16:08.959> able<00:16:09.120> to<00:16:09.199> pursue<00:16:09.519> it's 00:16:09.590 --> 00:16:09.600 align:start position:0% something i'll be able to pursue it's 00:16:09.600 --> 00:16:11.910 align:start position:0% something i'll be able to pursue it's certainly<00:16:10.000> an<00:16:10.160> aspiration 00:16:11.910 --> 00:16:11.920 align:start position:0% certainly an aspiration 00:16:11.920 --> 00:16:14.150 align:start position:0% certainly an aspiration um<00:16:12.160> for<00:16:12.320> the<00:16:12.480> moment<00:16:12.880> i<00:16:13.199> am<00:16:13.440> still<00:16:13.680> a<00:16:13.759> closure 00:16:14.150 --> 00:16:14.160 align:start position:0% um for the moment i am still a closure 00:16:14.160 --> 00:16:15.749 align:start position:0% um for the moment i am still a closure programmer 00:16:15.749 --> 00:16:15.759 align:start position:0% programmer 00:16:15.759 --> 00:16:17.829 align:start position:0% programmer i<00:16:15.920> came<00:16:16.079> back<00:16:16.240> from<00:16:16.399> the<00:16:16.560> r<00:16:16.720> world<00:16:17.440> about<00:16:17.680> a 00:16:17.829 --> 00:16:17.839 align:start position:0% i came back from the r world about a 00:16:17.839 --> 00:16:20.629 align:start position:0% i came back from the r world about a year<00:16:18.000> ago<00:16:18.320> i<00:16:18.399> switched<00:16:18.720> jobs<00:16:19.199> and<00:16:19.440> now 00:16:20.629 --> 00:16:20.639 align:start position:0% year ago i switched jobs and now 00:16:20.639 --> 00:16:22.230 align:start position:0% year ago i switched jobs and now like<00:16:20.880> well<00:16:21.040> i<00:16:21.199> technically<00:16:21.519> work<00:16:21.680> for<00:16:21.839> myself 00:16:22.230 --> 00:16:22.240 align:start position:0% like well i technically work for myself 00:16:22.240 --> 00:16:24.470 align:start position:0% like well i technically work for myself but<00:16:22.399> i<00:16:22.480> have<00:16:22.880> customers<00:16:23.600> who<00:16:23.839> have<00:16:24.079> me<00:16:24.160> doing 00:16:24.470 --> 00:16:24.480 align:start position:0% but i have customers who have me doing 00:16:24.480 --> 00:16:25.189 align:start position:0% but i have customers who have me doing closure<00:16:24.959> and 00:16:25.189 --> 00:16:25.199 align:start position:0% closure and 00:16:25.199 --> 00:16:28.389 align:start position:0% closure and javascript<00:16:26.160> which<00:16:26.399> i<00:16:26.480> enjoy<00:16:26.959> and<00:16:27.120> it's<00:16:27.279> great 00:16:28.389 --> 00:16:28.399 align:start position:0% javascript which i enjoy and it's great 00:16:28.399 --> 00:16:31.350 align:start position:0% javascript which i enjoy and it's great and<00:16:28.800> um<00:16:29.759> yeah<00:16:30.000> closure<00:16:30.320> is<00:16:30.959> closure<00:16:31.279> is 00:16:31.350 --> 00:16:31.360 align:start position:0% and um yeah closure is closure is 00:16:31.360 --> 00:16:34.870 align:start position:0% and um yeah closure is closure is awesome 00:16:34.870 --> 00:16:34.880 align:start position:0% 00:16:34.880 --> 00:16:38.470 align:start position:0% so<00:16:35.440> broad<00:16:35.920> stroke<00:16:36.399> agenda<00:16:36.880> here<00:16:37.839> uh 00:16:38.470 --> 00:16:38.480 align:start position:0% so broad stroke agenda here uh 00:16:38.480 --> 00:16:40.629 align:start position:0% so broad stroke agenda here uh yeah<00:16:38.720> i<00:16:38.880> i<00:16:39.360> it's<00:16:39.600> been<00:16:39.839> many<00:16:40.079> years<00:16:40.320> since<00:16:40.560> i 00:16:40.629 --> 00:16:40.639 align:start position:0% yeah i i it's been many years since i 00:16:40.639 --> 00:16:42.389 align:start position:0% yeah i i it's been many years since i first<00:16:40.880> saw<00:16:41.040> common<00:16:41.360> lisp<00:16:41.680> and<00:16:41.839> i'm<00:16:42.000> still 00:16:42.389 --> 00:16:42.399 align:start position:0% first saw common lisp and i'm still 00:16:42.399 --> 00:16:45.509 align:start position:0% first saw common lisp and i'm still interested<00:16:42.880> and<00:16:43.040> excited<00:16:43.360> about<00:16:43.680> it<00:16:44.480> and<00:16:45.279> i 00:16:45.509 --> 00:16:45.519 align:start position:0% interested and excited about it and i 00:16:45.519 --> 00:16:46.790 align:start position:0% interested and excited about it and i don't 00:16:46.790 --> 00:16:46.800 align:start position:0% don't 00:16:46.800 --> 00:16:48.550 align:start position:0% don't really<00:16:47.040> know<00:16:47.199> why<00:16:47.440> that<00:16:47.680> is<00:16:48.079> like<00:16:48.240> i<00:16:48.399> don't 00:16:48.550 --> 00:16:48.560 align:start position:0% really know why that is like i don't 00:16:48.560 --> 00:16:50.150 align:start position:0% really know why that is like i don't really<00:16:48.800> know<00:16:49.040> why 00:16:50.150 --> 00:16:50.160 align:start position:0% really know why 00:16:50.160 --> 00:16:52.069 align:start position:0% really know why uh<00:16:50.560> i<00:16:50.639> think<00:16:50.800> it's<00:16:50.959> good<00:16:51.279> and<00:16:51.360> i<00:16:51.519> like<00:16:51.759> it<00:16:51.920> and 00:16:52.069 --> 00:16:52.079 align:start position:0% uh i think it's good and i like it and 00:16:52.079 --> 00:16:54.150 align:start position:0% uh i think it's good and i like it and i'm<00:16:52.560> marginally<00:16:53.120> obsessed<00:16:53.440> with<00:16:53.600> it 00:16:54.150 --> 00:16:54.160 align:start position:0% i'm marginally obsessed with it 00:16:54.160 --> 00:16:56.069 align:start position:0% i'm marginally obsessed with it it's<00:16:54.399> funny<00:16:54.639> because<00:16:55.199> my<00:16:55.360> interest<00:16:55.759> in<00:16:55.839> this 00:16:56.069 --> 00:16:56.079 align:start position:0% it's funny because my interest in this 00:16:56.079 --> 00:16:57.829 align:start position:0% it's funny because my interest in this has<00:16:56.320> really<00:16:56.560> confused<00:16:57.120> and<00:16:57.199> surprised<00:16:57.680> a<00:16:57.759> lot 00:16:57.829 --> 00:16:57.839 align:start position:0% has really confused and surprised a lot 00:16:57.839 --> 00:16:59.189 align:start position:0% has really confused and surprised a lot of<00:16:57.920> my<00:16:58.079> friends<00:16:58.320> in<00:16:58.399> the<00:16:58.480> closure<00:16:58.800> community 00:16:59.189 --> 00:16:59.199 align:start position:0% of my friends in the closure community 00:16:59.199 --> 00:17:00.629 align:start position:0% of my friends in the closure community and<00:16:59.279> even<00:16:59.440> in<00:16:59.519> the<00:16:59.600> art<00:16:59.839> community 00:17:00.629 --> 00:17:00.639 align:start position:0% and even in the art community 00:17:00.639 --> 00:17:03.670 align:start position:0% and even in the art community like<00:17:00.880> what<00:17:01.199> what<00:17:01.360> do<00:17:01.440> you<00:17:01.600> see<00:17:01.839> in<00:17:01.920> this<00:17:02.399> um 00:17:03.670 --> 00:17:03.680 align:start position:0% like what what do you see in this um 00:17:03.680 --> 00:17:06.630 align:start position:0% like what what do you see in this um so<00:17:05.360> some<00:17:05.600> of<00:17:05.679> the<00:17:05.760> time<00:17:06.000> i'm<00:17:06.079> looking<00:17:06.319> at<00:17:06.400> this 00:17:06.630 --> 00:17:06.640 align:start position:0% so some of the time i'm looking at this 00:17:06.640 --> 00:17:07.429 align:start position:0% so some of the time i'm looking at this stuff<00:17:06.959> i<00:17:07.039> think 00:17:07.429 --> 00:17:07.439 align:start position:0% stuff i think 00:17:07.439 --> 00:17:09.110 align:start position:0% stuff i think maybe<00:17:07.760> maybe<00:17:08.079> i'm<00:17:08.240> just<00:17:08.400> going<00:17:08.640> crazy<00:17:08.959> like 00:17:09.110 --> 00:17:09.120 align:start position:0% maybe maybe i'm just going crazy like 00:17:09.120 --> 00:17:10.230 align:start position:0% maybe maybe i'm just going crazy like maybe<00:17:09.360> i<00:17:09.360> have<00:17:09.439> a<00:17:09.520> brain<00:17:09.679> tumor<00:17:09.919> or<00:17:10.079> something 00:17:10.230 --> 00:17:10.240 align:start position:0% maybe i have a brain tumor or something 00:17:10.240 --> 00:17:10.870 align:start position:0% maybe i have a brain tumor or something like<00:17:10.400> that 00:17:10.870 --> 00:17:10.880 align:start position:0% like that 00:17:10.880 --> 00:17:14.230 align:start position:0% like that but<00:17:11.919> um<00:17:13.199> you<00:17:13.280> know<00:17:13.520> i<00:17:13.600> don't<00:17:13.760> have<00:17:13.839> any<00:17:14.000> other 00:17:14.230 --> 00:17:14.240 align:start position:0% but um you know i don't have any other 00:17:14.240 --> 00:17:15.189 align:start position:0% but um you know i don't have any other symptoms 00:17:15.189 --> 00:17:15.199 align:start position:0% symptoms 00:17:15.199 --> 00:17:17.350 align:start position:0% symptoms so<00:17:15.760> i<00:17:15.919> think<00:17:16.160> it<00:17:16.240> really<00:17:16.559> is<00:17:16.720> just<00:17:16.959> it's 00:17:17.350 --> 00:17:17.360 align:start position:0% so i think it really is just it's 00:17:17.360 --> 00:17:18.789 align:start position:0% so i think it really is just it's interesting 00:17:18.789 --> 00:17:18.799 align:start position:0% interesting 00:17:18.799 --> 00:17:22.230 align:start position:0% interesting um<00:17:20.000> so<00:17:20.799> i<00:17:20.880> hope<00:17:21.120> to<00:17:21.199> convey<00:17:21.760> why 00:17:22.230 --> 00:17:22.240 align:start position:0% um so i hope to convey why 00:17:22.240 --> 00:17:23.510 align:start position:0% um so i hope to convey why why<00:17:22.400> i<00:17:22.480> think<00:17:22.559> it's<00:17:22.720> history<00:17:22.959> and<00:17:23.120> interesting 00:17:23.510 --> 00:17:23.520 align:start position:0% why i think it's history and interesting 00:17:23.520 --> 00:17:25.029 align:start position:0% why i think it's history and interesting and<00:17:23.760> this<00:17:23.919> is<00:17:24.000> the<00:17:24.079> introspection<00:17:24.799> that<00:17:24.880> i 00:17:25.029 --> 00:17:25.039 align:start position:0% and this is the introspection that i 00:17:25.039 --> 00:17:26.470 align:start position:0% and this is the introspection that i mentioned<00:17:25.280> earlier<00:17:25.600> that<00:17:25.760> i<00:17:25.919> that<00:17:26.079> i<00:17:26.160> did<00:17:26.400> that 00:17:26.470 --> 00:17:26.480 align:start position:0% mentioned earlier that i that i did that 00:17:26.480 --> 00:17:27.669 align:start position:0% mentioned earlier that i that i did that i<00:17:26.640> haven't<00:17:26.959> done 00:17:27.669 --> 00:17:27.679 align:start position:0% i haven't done 00:17:27.679 --> 00:17:29.270 align:start position:0% i haven't done is<00:17:27.839> i've<00:17:28.079> known<00:17:28.319> i've<00:17:28.480> been<00:17:28.640> afflicted<00:17:29.120> with 00:17:29.270 --> 00:17:29.280 align:start position:0% is i've known i've been afflicted with 00:17:29.280 --> 00:17:30.870 align:start position:0% is i've known i've been afflicted with this<00:17:29.520> like<00:17:29.919> obsession 00:17:30.870 --> 00:17:30.880 align:start position:0% this like obsession 00:17:30.880 --> 00:17:32.549 align:start position:0% this like obsession but<00:17:31.039> i<00:17:31.120> haven't<00:17:31.360> really<00:17:31.600> thought<00:17:31.840> about<00:17:32.160> why 00:17:32.549 --> 00:17:32.559 align:start position:0% but i haven't really thought about why 00:17:32.559 --> 00:17:34.470 align:start position:0% but i haven't really thought about why i'm<00:17:32.640> so<00:17:32.880> interested<00:17:33.520> and<00:17:33.679> so<00:17:33.840> i<00:17:33.919> hope<00:17:34.080> to<00:17:34.240> share 00:17:34.470 --> 00:17:34.480 align:start position:0% i'm so interested and so i hope to share 00:17:34.480 --> 00:17:35.350 align:start position:0% i'm so interested and so i hope to share that 00:17:35.350 --> 00:17:35.360 align:start position:0% that 00:17:35.360 --> 00:17:37.750 align:start position:0% that um<00:17:36.400> the<00:17:36.480> other<00:17:36.640> thing<00:17:36.799> is<00:17:36.960> context<00:17:37.440> i<00:17:37.520> think<00:17:37.679> i 00:17:37.750 --> 00:17:37.760 align:start position:0% um the other thing is context i think i 00:17:37.760 --> 00:17:38.549 align:start position:0% um the other thing is context i think i mentioned 00:17:38.549 --> 00:17:38.559 align:start position:0% mentioned 00:17:38.559 --> 00:17:39.909 align:start position:0% mentioned you<00:17:38.640> know<00:17:38.880> if<00:17:38.960> you<00:17:39.120> want<00:17:39.200> to<00:17:39.360> understand<00:17:39.760> an 00:17:39.909 --> 00:17:39.919 align:start position:0% you know if you want to understand an 00:17:39.919 --> 00:17:42.070 align:start position:0% you know if you want to understand an idea<00:17:40.400> it<00:17:40.559> helps<00:17:41.039> a<00:17:41.200> lot<00:17:41.440> to<00:17:41.600> understand<00:17:41.919> the 00:17:42.070 --> 00:17:42.080 align:start position:0% idea it helps a lot to understand the 00:17:42.080 --> 00:17:43.990 align:start position:0% idea it helps a lot to understand the people<00:17:42.320> behind<00:17:42.640> it<00:17:42.720> and<00:17:42.880> what<00:17:43.039> motivated<00:17:43.600> them 00:17:43.990 --> 00:17:44.000 align:start position:0% people behind it and what motivated them 00:17:44.000 --> 00:17:47.270 align:start position:0% people behind it and what motivated them to<00:17:44.160> do<00:17:44.400> stuff<00:17:45.440> um<00:17:46.160> and<00:17:46.400> i<00:17:46.559> don't<00:17:46.880> think 00:17:47.270 --> 00:17:47.280 align:start position:0% to do stuff um and i don't think 00:17:47.280 --> 00:17:50.470 align:start position:0% to do stuff um and i don't think common<00:17:47.760> lisp<00:17:49.440> common<00:17:49.760> lisp 00:17:50.470 --> 00:17:50.480 align:start position:0% common lisp common lisp 00:17:50.480 --> 00:17:52.230 align:start position:0% common lisp common lisp was<00:17:50.640> not<00:17:50.880> designed<00:17:51.120> by<00:17:51.280> one<00:17:51.520> person<00:17:51.840> first<00:17:52.080> of 00:17:52.230 --> 00:17:52.240 align:start position:0% was not designed by one person first of 00:17:52.240 --> 00:17:53.990 align:start position:0% was not designed by one person first of all<00:17:53.120> and 00:17:53.990 --> 00:17:54.000 align:start position:0% all and 00:17:54.000 --> 00:17:57.190 align:start position:0% all and none<00:17:54.240> of<00:17:54.320> the<00:17:54.480> people<00:17:54.960> who<00:17:55.440> promote<00:17:55.840> it<00:17:56.160> now 00:17:57.190 --> 00:17:57.200 align:start position:0% none of the people who promote it now 00:17:57.200 --> 00:17:59.590 align:start position:0% none of the people who promote it now lay<00:17:57.600> claim<00:17:58.000> to<00:17:58.160> it<00:17:58.320> or<00:17:58.640> particularly<00:17:59.200> invested 00:17:59.590 --> 00:17:59.600 align:start position:0% lay claim to it or particularly invested 00:17:59.600 --> 00:18:01.430 align:start position:0% lay claim to it or particularly invested in<00:17:59.760> its<00:17:59.840> future<00:18:00.160> directly 00:18:01.430 --> 00:18:01.440 align:start position:0% in its future directly 00:18:01.440 --> 00:18:02.789 align:start position:0% in its future directly uh<00:18:01.760> i<00:18:01.840> mean<00:18:02.000> everybody's<00:18:02.480> part<00:18:02.640> of<00:18:02.720> the 00:18:02.789 --> 00:18:02.799 align:start position:0% uh i mean everybody's part of the 00:18:02.799 --> 00:18:04.630 align:start position:0% uh i mean everybody's part of the community<00:18:03.360> but<00:18:03.520> that<00:18:03.679> nobody<00:18:04.080> has<00:18:04.320> special 00:18:04.630 --> 00:18:04.640 align:start position:0% community but that nobody has special 00:18:04.640 --> 00:18:06.390 align:start position:0% community but that nobody has special standing<00:18:05.200> the<00:18:05.280> way<00:18:05.440> that<00:18:05.679> rich<00:18:05.840> hickey<00:18:06.160> has 00:18:06.390 --> 00:18:06.400 align:start position:0% standing the way that rich hickey has 00:18:06.400 --> 00:18:07.510 align:start position:0% standing the way that rich hickey has special<00:18:06.720> standing<00:18:07.039> in<00:18:07.120> the<00:18:07.200> closure 00:18:07.510 --> 00:18:07.520 align:start position:0% special standing in the closure 00:18:07.520 --> 00:18:08.630 align:start position:0% special standing in the closure community 00:18:08.630 --> 00:18:08.640 align:start position:0% community 00:18:08.640 --> 00:18:11.430 align:start position:0% community so<00:18:08.799> you<00:18:08.960> hear<00:18:09.120> a<00:18:09.200> lot<00:18:09.360> of<00:18:09.520> different<00:18:11.039> versions 00:18:11.430 --> 00:18:11.440 align:start position:0% so you hear a lot of different versions 00:18:11.440 --> 00:18:13.190 align:start position:0% so you hear a lot of different versions of<00:18:11.600> why<00:18:11.840> common<00:18:12.080> lisp<00:18:12.400> is<00:18:12.480> good<00:18:12.720> and<00:18:12.880> you<00:18:12.960> hear 00:18:13.190 --> 00:18:13.200 align:start position:0% of why common lisp is good and you hear 00:18:13.200 --> 00:18:14.630 align:start position:0% of why common lisp is good and you hear common<00:18:13.520> lisp<00:18:13.840> explained<00:18:14.240> in<00:18:14.400> a<00:18:14.400> lot<00:18:14.559> of 00:18:14.630 --> 00:18:14.640 align:start position:0% common lisp explained in a lot of 00:18:14.640 --> 00:18:16.630 align:start position:0% common lisp explained in a lot of different<00:18:14.960> ways 00:18:16.630 --> 00:18:16.640 align:start position:0% different ways 00:18:16.640 --> 00:18:18.470 align:start position:0% different ways but<00:18:16.880> the<00:18:17.039> people<00:18:17.360> who<00:18:17.679> originally<00:18:18.080> designed 00:18:18.470 --> 00:18:18.480 align:start position:0% but the people who originally designed 00:18:18.480 --> 00:18:19.830 align:start position:0% but the people who originally designed it<00:18:18.640> are<00:18:18.720> more<00:18:18.880> or<00:18:19.039> less<00:18:19.280> out<00:18:19.360> of<00:18:19.440> the<00:18:19.520> public 00:18:19.830 --> 00:18:19.840 align:start position:0% it are more or less out of the public 00:18:19.840 --> 00:18:21.350 align:start position:0% it are more or less out of the public sphere<00:18:20.240> they're<00:18:20.400> retired 00:18:21.350 --> 00:18:21.360 align:start position:0% sphere they're retired 00:18:21.360 --> 00:18:24.549 align:start position:0% sphere they're retired you<00:18:21.440> know<00:18:21.600> playing<00:18:21.840> it<00:18:22.559> playing<00:18:22.880> it's<00:18:23.039> low 00:18:24.549 --> 00:18:24.559 align:start position:0% you know playing it playing it's low 00:18:24.559 --> 00:18:26.310 align:start position:0% you know playing it playing it's low so<00:18:24.720> you<00:18:24.799> don't<00:18:25.039> hear<00:18:25.280> much<00:18:25.600> about<00:18:26.000> what 00:18:26.310 --> 00:18:26.320 align:start position:0% so you don't hear much about what 00:18:26.320 --> 00:18:28.950 align:start position:0% so you don't hear much about what motivated<00:18:27.120> the<00:18:27.360> people<00:18:27.919> originally 00:18:28.950 --> 00:18:28.960 align:start position:0% motivated the people originally 00:18:28.960 --> 00:18:32.070 align:start position:0% motivated the people originally to<00:18:29.120> make<00:18:29.360> it<00:18:30.640> so<00:18:31.360> i'm 00:18:32.070 --> 00:18:32.080 align:start position:0% to make it so i'm 00:18:32.080 --> 00:18:34.390 align:start position:0% to make it so i'm not<00:18:32.400> that<00:18:32.640> person<00:18:33.120> obviously<00:18:33.679> this<00:18:33.919> was<00:18:34.320> i 00:18:34.390 --> 00:18:34.400 align:start position:0% not that person obviously this was i 00:18:34.400 --> 00:18:35.909 align:start position:0% not that person obviously this was i mean<00:18:34.559> come<00:18:34.799> the<00:18:34.960> design<00:18:35.280> on<00:18:35.360> common<00:18:35.679> list 00:18:35.909 --> 00:18:35.919 align:start position:0% mean come the design on common list 00:18:35.919 --> 00:18:37.750 align:start position:0% mean come the design on common list started<00:18:36.320> before<00:18:36.640> i<00:18:36.720> was<00:18:36.880> born 00:18:37.750 --> 00:18:37.760 align:start position:0% started before i was born 00:18:37.760 --> 00:18:39.909 align:start position:0% started before i was born and<00:18:38.320> the<00:18:38.480> stuff<00:18:38.720> that<00:18:39.200> the<00:18:39.360> other<00:18:39.520> lists<00:18:39.840> the 00:18:39.909 --> 00:18:39.919 align:start position:0% and the stuff that the other lists the 00:18:39.919 --> 00:18:41.590 align:start position:0% and the stuff that the other lists the common<00:18:40.160> lists<00:18:40.480> are<00:18:40.559> based<00:18:40.880> on 00:18:41.590 --> 00:18:41.600 align:start position:0% common lists are based on 00:18:41.600 --> 00:18:44.549 align:start position:0% common lists are based on existed<00:18:42.320> decades<00:18:42.720> before<00:18:42.960> i<00:18:43.039> was<00:18:43.200> born<00:18:44.080> so<00:18:44.400> i 00:18:44.549 --> 00:18:44.559 align:start position:0% existed decades before i was born so i 00:18:44.559 --> 00:18:46.549 align:start position:0% existed decades before i was born so i can't<00:18:45.039> i'm<00:18:45.520> not<00:18:45.679> going<00:18:45.760> to<00:18:45.840> be<00:18:46.000> that<00:18:46.160> person 00:18:46.549 --> 00:18:46.559 align:start position:0% can't i'm not going to be that person 00:18:46.559 --> 00:18:48.230 align:start position:0% can't i'm not going to be that person but<00:18:46.799> i<00:18:46.880> have<00:18:47.039> read<00:18:47.280> a<00:18:47.280> lot<00:18:47.440> of<00:18:47.520> that<00:18:47.679> stuff<00:18:48.080> and 00:18:48.230 --> 00:18:48.240 align:start position:0% but i have read a lot of that stuff and 00:18:48.240 --> 00:18:49.990 align:start position:0% but i have read a lot of that stuff and so<00:18:48.400> i<00:18:48.480> hope<00:18:48.640> to 00:18:49.990 --> 00:18:50.000 align:start position:0% so i hope to 00:18:50.000 --> 00:18:51.909 align:start position:0% so i hope to share<00:18:50.320> some<00:18:50.480> of<00:18:50.880> some<00:18:51.120> of<00:18:51.200> what<00:18:51.360> i<00:18:51.440> run<00:18:51.679> into 00:18:51.909 --> 00:18:51.919 align:start position:0% share some of some of what i run into 00:18:51.919 --> 00:18:54.390 align:start position:0% share some of some of what i run into that<00:18:52.000> i<00:18:52.080> thought<00:18:52.240> was<00:18:52.480> informative 00:18:54.390 --> 00:18:54.400 align:start position:0% that i thought was informative 00:18:54.400 --> 00:18:56.070 align:start position:0% that i thought was informative and<00:18:54.480> then<00:18:54.720> finally<00:18:55.200> there's<00:18:55.679> a<00:18:55.760> lot<00:18:55.919> of 00:18:56.070 --> 00:18:56.080 align:start position:0% and then finally there's a lot of 00:18:56.080 --> 00:18:58.150 align:start position:0% and then finally there's a lot of activity<00:18:56.480> in<00:18:56.559> common<00:18:56.799> list<00:18:57.039> right<00:18:57.200> now 00:18:58.150 --> 00:18:58.160 align:start position:0% activity in common list right now 00:18:58.160 --> 00:19:00.230 align:start position:0% activity in common list right now not<00:18:58.400> as<00:18:58.480> much<00:18:58.640> as<00:18:58.799> enclosure<00:18:59.520> not<00:18:59.679> as<00:18:59.840> much<00:19:00.000> as 00:19:00.230 --> 00:19:00.240 align:start position:0% not as much as enclosure not as much as 00:19:00.240 --> 00:19:01.669 align:start position:0% not as much as enclosure not as much as in<00:19:00.400> probably 00:19:01.669 --> 00:19:01.679 align:start position:0% in probably 00:19:01.679 --> 00:19:04.150 align:start position:0% in probably any<00:19:01.919> other<00:19:02.080> language<00:19:02.400> you've<00:19:02.559> heard<00:19:02.799> of<00:19:03.840> but 00:19:04.150 --> 00:19:04.160 align:start position:0% any other language you've heard of but 00:19:04.160 --> 00:19:05.350 align:start position:0% any other language you've heard of but it's<00:19:04.480> there 00:19:05.350 --> 00:19:05.360 align:start position:0% it's there 00:19:05.360 --> 00:19:09.190 align:start position:0% it's there and<00:19:05.760> it's<00:19:06.000> really<00:19:06.240> exciting<00:19:06.799> i<00:19:06.960> think<00:19:07.840> um 00:19:09.190 --> 00:19:09.200 align:start position:0% and it's really exciting i think um 00:19:09.200 --> 00:19:12.950 align:start position:0% and it's really exciting i think um because<00:19:09.600> the<00:19:09.760> foundation<00:19:10.240> is<00:19:10.320> so<00:19:10.559> solid<00:19:11.520> and 00:19:12.950 --> 00:19:12.960 align:start position:0% because the foundation is so solid and 00:19:12.960 --> 00:19:14.230 align:start position:0% because the foundation is so solid and well<00:19:13.120> there's<00:19:13.280> a<00:19:13.280> lot<00:19:13.440> of<00:19:13.520> reasons<00:19:13.760> for<00:19:13.919> causes 00:19:14.230 --> 00:19:14.240 align:start position:0% well there's a lot of reasons for causes 00:19:14.240 --> 00:19:16.870 align:start position:0% well there's a lot of reasons for causes for<00:19:14.400> excitement<00:19:14.799> that<00:19:14.960> i'll<00:19:15.039> get<00:19:15.200> into 00:19:16.870 --> 00:19:16.880 align:start position:0% for excitement that i'll get into 00:19:16.880 --> 00:19:18.870 align:start position:0% for excitement that i'll get into uh<00:19:17.120> what<00:19:17.280> this<00:19:17.440> definitely<00:19:17.919> isn't<00:19:18.559> is<00:19:18.799> the 00:19:18.870 --> 00:19:18.880 align:start position:0% uh what this definitely isn't is the 00:19:18.880 --> 00:19:20.230 align:start position:0% uh what this definitely isn't is the kind<00:19:19.039> of<00:19:19.200> talk<00:19:19.520> where<00:19:19.679> i'm<00:19:19.919> trying<00:19:20.160> to 00:19:20.230 --> 00:19:20.240 align:start position:0% kind of talk where i'm trying to 00:19:20.240 --> 00:19:21.110 align:start position:0% kind of talk where i'm trying to shoehorn 00:19:21.110 --> 00:19:21.120 align:start position:0% shoehorn 00:19:21.120 --> 00:19:24.230 align:start position:0% shoehorn these<00:19:21.440> into<00:19:21.600> some<00:19:21.760> kind<00:19:21.919> of<00:19:22.080> dichotomy<00:19:23.280> um 00:19:24.230 --> 00:19:24.240 align:start position:0% these into some kind of dichotomy um 00:19:24.240 --> 00:19:25.990 align:start position:0% these into some kind of dichotomy um daniel<00:19:24.880> mentioned<00:19:25.280> earlier<00:19:25.600> that<00:19:25.760> you<00:19:25.840> know 00:19:25.990 --> 00:19:26.000 align:start position:0% daniel mentioned earlier that you know 00:19:26.000 --> 00:19:27.430 align:start position:0% daniel mentioned earlier that you know i'm<00:19:26.160> polyamorous 00:19:27.430 --> 00:19:27.440 align:start position:0% i'm polyamorous 00:19:27.440 --> 00:19:30.630 align:start position:0% i'm polyamorous or<00:19:27.679> poly<00:19:28.480> poly<00:19:29.440> polytheistic 00:19:30.630 --> 00:19:30.640 align:start position:0% or poly poly polytheistic 00:19:30.640 --> 00:19:34.789 align:start position:0% or poly poly polytheistic polylingual<00:19:32.640> i'm<00:19:32.799> down<00:19:33.120> for<00:19:33.360> all<00:19:33.679> these<00:19:33.919> ideas 00:19:34.789 --> 00:19:34.799 align:start position:0% polylingual i'm down for all these ideas 00:19:34.799 --> 00:19:37.110 align:start position:0% polylingual i'm down for all these ideas i<00:19:34.960> have<00:19:35.280> recognized<00:19:35.919> great<00:19:36.160> personal<00:19:36.640> benefit 00:19:37.110 --> 00:19:37.120 align:start position:0% i have recognized great personal benefit 00:19:37.120 --> 00:19:38.950 align:start position:0% i have recognized great personal benefit from<00:19:37.360> investing<00:19:37.760> heavily<00:19:38.160> in<00:19:38.320> one<00:19:38.640> thing 00:19:38.950 --> 00:19:38.960 align:start position:0% from investing heavily in one thing 00:19:38.960 --> 00:19:40.470 align:start position:0% from investing heavily in one thing which<00:19:39.200> i<00:19:39.280> did<00:19:39.440> with<00:19:39.600> closure<00:19:39.919> for<00:19:40.080> like<00:19:40.240> 10 00:19:40.470 --> 00:19:40.480 align:start position:0% which i did with closure for like 10 00:19:40.480 --> 00:19:41.590 align:start position:0% which i did with closure for like 10 years 00:19:41.590 --> 00:19:41.600 align:start position:0% years 00:19:41.600 --> 00:19:43.190 align:start position:0% years but<00:19:42.080> i<00:19:42.160> think<00:19:42.320> there's<00:19:42.559> also<00:19:42.799> tremendous 00:19:43.190 --> 00:19:43.200 align:start position:0% but i think there's also tremendous 00:19:43.200 --> 00:19:44.710 align:start position:0% but i think there's also tremendous benefit<00:19:43.919> in 00:19:44.710 --> 00:19:44.720 align:start position:0% benefit in 00:19:44.720 --> 00:19:46.710 align:start position:0% benefit in recognizing<00:19:45.360> that<00:19:45.760> it's<00:19:45.919> possible<00:19:46.320> to<00:19:46.480> like 00:19:46.710 --> 00:19:46.720 align:start position:0% recognizing that it's possible to like 00:19:46.720 --> 00:19:48.150 align:start position:0% recognizing that it's possible to like multiple<00:19:47.039> things<00:19:47.280> at<00:19:47.360> the<00:19:47.520> same<00:19:47.760> time 00:19:48.150 --> 00:19:48.160 align:start position:0% multiple things at the same time 00:19:48.160 --> 00:19:49.990 align:start position:0% multiple things at the same time and<00:19:48.799> you<00:19:48.880> know<00:19:49.039> we<00:19:49.200> don't<00:19:49.360> have<00:19:49.520> to<00:19:49.600> be<00:19:49.679> fully 00:19:49.990 --> 00:19:50.000 align:start position:0% and you know we don't have to be fully 00:19:50.000 --> 00:19:51.510 align:start position:0% and you know we don't have to be fully invested<00:19:50.480> and<00:19:50.640> i<00:19:50.720> think<00:19:50.799> this<00:19:50.960> is<00:19:51.120> a<00:19:51.200> message 00:19:51.510 --> 00:19:51.520 align:start position:0% invested and i think this is a message 00:19:51.520 --> 00:19:52.870 align:start position:0% invested and i think this is a message more<00:19:51.760> for 00:19:52.870 --> 00:19:52.880 align:start position:0% more for 00:19:52.880 --> 00:19:54.950 align:start position:0% more for junior<00:19:53.200> people<00:19:53.679> and<00:19:53.760> my<00:19:53.919> former<00:19:54.320> self<00:19:54.720> i<00:19:54.799> don't 00:19:54.950 --> 00:19:54.960 align:start position:0% junior people and my former self i don't 00:19:54.960 --> 00:19:56.470 align:start position:0% junior people and my former self i don't think<00:19:55.120> anyone<00:19:55.440> here<00:19:55.760> probably 00:19:56.470 --> 00:19:56.480 align:start position:0% think anyone here probably 00:19:56.480 --> 00:19:59.750 align:start position:0% think anyone here probably is<00:19:58.240> would<00:19:58.400> disagree<00:19:58.880> with<00:19:59.039> this 00:19:59.750 --> 00:19:59.760 align:start position:0% is would disagree with this 00:19:59.760 --> 00:20:01.669 align:start position:0% is would disagree with this um<00:20:00.080> so<00:20:00.320> yeah<00:20:00.559> both<00:20:00.880> closure<00:20:01.200> and<00:20:01.280> common<00:20:01.520> list 00:20:01.669 --> 00:20:01.679 align:start position:0% um so yeah both closure and common list 00:20:01.679 --> 00:20:03.190 align:start position:0% um so yeah both closure and common list can<00:20:01.840> exist<00:20:02.080> at<00:20:02.159> the<00:20:02.240> same<00:20:02.480> time<00:20:02.720> and<00:20:02.880> both<00:20:03.039> be 00:20:03.190 --> 00:20:03.200 align:start position:0% can exist at the same time and both be 00:20:03.200 --> 00:20:04.950 align:start position:0% can exist at the same time and both be amazing<00:20:03.600> at<00:20:03.679> the<00:20:03.760> same<00:20:04.000> time<00:20:04.320> and<00:20:04.480> we<00:20:04.559> can 00:20:04.950 --> 00:20:04.960 align:start position:0% amazing at the same time and we can 00:20:04.960 --> 00:20:08.549 align:start position:0% amazing at the same time and we can uh<00:20:05.520> we<00:20:05.679> can<00:20:06.960> have<00:20:07.919> you<00:20:08.080> know 00:20:08.549 --> 00:20:08.559 align:start position:0% uh we can have you know 00:20:08.559 --> 00:20:10.230 align:start position:0% uh we can have you know recognize<00:20:09.039> and<00:20:09.120> realize<00:20:09.520> great<00:20:09.760> benefits 00:20:10.230 --> 00:20:10.240 align:start position:0% recognize and realize great benefits 00:20:10.240 --> 00:20:11.750 align:start position:0% recognize and realize great benefits from<00:20:10.640> holding<00:20:10.960> both<00:20:11.200> in<00:20:11.280> our<00:20:11.360> heads<00:20:11.600> at<00:20:11.679> the 00:20:11.750 --> 00:20:11.760 align:start position:0% from holding both in our heads at the 00:20:11.760 --> 00:20:12.310 align:start position:0% from holding both in our heads at the same<00:20:11.919> time 00:20:12.310 --> 00:20:12.320 align:start position:0% same time 00:20:12.320 --> 00:20:13.590 align:start position:0% same time and<00:20:12.480> maybe<00:20:12.720> even<00:20:12.880> switching<00:20:13.200> between<00:20:13.440> them 00:20:13.590 --> 00:20:13.600 align:start position:0% and maybe even switching between them 00:20:13.600 --> 00:20:16.470 align:start position:0% and maybe even switching between them when<00:20:13.679> it's<00:20:13.840> convenient 00:20:16.470 --> 00:20:16.480 align:start position:0% 00:20:16.480 --> 00:20:19.750 align:start position:0% okay<00:20:17.520> so<00:20:18.159> why<00:20:18.400> are<00:20:18.480> we<00:20:18.640> here<00:20:18.880> why<00:20:19.120> am<00:20:19.280> i 00:20:19.750 --> 00:20:19.760 align:start position:0% okay so why are we here why am i 00:20:19.760 --> 00:20:22.390 align:start position:0% okay so why are we here why am i why<00:20:20.240> why<00:20:20.480> is<00:20:20.559> this<00:20:20.799> meeting<00:20:21.039> worth<00:20:21.280> your<00:20:21.440> time 00:20:22.390 --> 00:20:22.400 align:start position:0% why why is this meeting worth your time 00:20:22.400 --> 00:20:23.510 align:start position:0% why why is this meeting worth your time and 00:20:23.510 --> 00:20:23.520 align:start position:0% and 00:20:23.520 --> 00:20:25.110 align:start position:0% and i<00:20:23.600> think<00:20:23.760> it's<00:20:23.919> because<00:20:24.240> common<00:20:24.480> lisp<00:20:24.880> is<00:20:24.960> not 00:20:25.110 --> 00:20:25.120 align:start position:0% i think it's because common lisp is not 00:20:25.120 --> 00:20:26.630 align:start position:0% i think it's because common lisp is not going<00:20:25.360> anywhere<00:20:25.840> it<00:20:26.000> is<00:20:26.159> going<00:20:26.240> to<00:20:26.320> wait<00:20:26.559> for 00:20:26.630 --> 00:20:26.640 align:start position:0% going anywhere it is going to wait for 00:20:26.640 --> 00:20:27.830 align:start position:0% going anywhere it is going to wait for you<00:20:26.799> for<00:20:26.960> the<00:20:27.039> rest<00:20:27.200> of<00:20:27.280> your<00:20:27.440> life 00:20:27.830 --> 00:20:27.840 align:start position:0% you for the rest of your life 00:20:27.840 --> 00:20:31.029 align:start position:0% you for the rest of your life to<00:20:28.000> learn<00:20:28.559> without<00:20:28.880> changing<00:20:30.159> um<00:20:30.720> and<00:20:30.799> that's 00:20:31.029 --> 00:20:31.039 align:start position:0% to learn without changing um and that's 00:20:31.039 --> 00:20:31.669 align:start position:0% to learn without changing um and that's because 00:20:31.669 --> 00:20:31.679 align:start position:0% because 00:20:31.679 --> 00:20:33.590 align:start position:0% because it's<00:20:31.840> a<00:20:32.000> standard<00:20:32.400> it's<00:20:32.720> already<00:20:32.960> agreed<00:20:33.280> upon 00:20:33.590 --> 00:20:33.600 align:start position:0% it's a standard it's already agreed upon 00:20:33.600 --> 00:20:35.350 align:start position:0% it's a standard it's already agreed upon it's<00:20:33.760> in<00:20:33.840> the<00:20:34.000> books<00:20:34.480> you<00:20:34.640> know<00:20:34.799> they<00:20:35.120> there's 00:20:35.350 --> 00:20:35.360 align:start position:0% it's in the books you know they there's 00:20:35.360 --> 00:20:36.070 align:start position:0% it's in the books you know they there's a<00:20:35.600> thing 00:20:36.070 --> 00:20:36.080 align:start position:0% a thing 00:20:36.080 --> 00:20:37.510 align:start position:0% a thing there's<00:20:36.240> a<00:20:36.400> plate<00:20:36.640> the<00:20:37.120> standards 00:20:37.510 --> 00:20:37.520 align:start position:0% there's a plate the standards 00:20:37.520 --> 00:20:40.390 align:start position:0% there's a plate the standards organization<00:20:38.159> keeps<00:20:38.400> it<00:20:38.480> on<00:20:38.640> file 00:20:40.390 --> 00:20:40.400 align:start position:0% organization keeps it on file 00:20:40.400 --> 00:20:42.870 align:start position:0% organization keeps it on file so<00:20:40.559> whether<00:20:40.880> you<00:20:40.960> learn<00:20:41.200> it<00:20:41.679> today<00:20:42.240> tomorrow 00:20:42.870 --> 00:20:42.880 align:start position:0% so whether you learn it today tomorrow 00:20:42.880 --> 00:20:43.669 align:start position:0% so whether you learn it today tomorrow next<00:20:43.200> year 00:20:43.669 --> 00:20:43.679 align:start position:0% next year 00:20:43.679 --> 00:20:45.430 align:start position:0% next year or<00:20:43.919> on<00:20:44.000> your<00:20:44.159> deathbed<00:20:44.799> it's<00:20:45.039> going<00:20:45.120> to<00:20:45.200> be<00:20:45.280> the 00:20:45.430 --> 00:20:45.440 align:start position:0% or on your deathbed it's going to be the 00:20:45.440 --> 00:20:47.350 align:start position:0% or on your deathbed it's going to be the same<00:20:46.640> and 00:20:47.350 --> 00:20:47.360 align:start position:0% same and 00:20:47.360 --> 00:20:49.750 align:start position:0% same and to<00:20:47.520> me<00:20:48.080> as<00:20:48.240> someone<00:20:48.640> who<00:20:48.880> spent<00:20:49.120> a<00:20:49.200> lot<00:20:49.360> of<00:20:49.440> time 00:20:49.750 --> 00:20:49.760 align:start position:0% to me as someone who spent a lot of time 00:20:49.760 --> 00:20:51.270 align:start position:0% to me as someone who spent a lot of time in<00:20:49.840> the<00:20:50.000> web<00:20:50.159> development<00:20:50.640> world 00:20:51.270 --> 00:20:51.280 align:start position:0% in the web development world 00:20:51.280 --> 00:20:54.549 align:start position:0% in the web development world and<00:20:52.080> at<00:20:52.240> the<00:20:52.400> mercy<00:20:52.880> of<00:20:53.360> people<00:20:53.679> who 00:20:54.549 --> 00:20:54.559 align:start position:0% and at the mercy of people who 00:20:54.559 --> 00:20:56.230 align:start position:0% and at the mercy of people who changed<00:20:54.960> libraries<00:20:55.600> for<00:20:55.760> reasons<00:20:56.159> that 00:20:56.230 --> 00:20:56.240 align:start position:0% changed libraries for reasons that 00:20:56.240 --> 00:20:57.750 align:start position:0% changed libraries for reasons that aren't<00:20:56.480> in<00:20:56.559> alignment<00:20:57.200> with 00:20:57.750 --> 00:20:57.760 align:start position:0% aren't in alignment with 00:20:57.760 --> 00:21:01.190 align:start position:0% aren't in alignment with my<00:20:57.919> own<00:20:58.159> interests<00:20:58.559> or<00:20:59.679> business<00:21:00.000> repurposes 00:21:01.190 --> 00:21:01.200 align:start position:0% my own interests or business repurposes 00:21:01.200 --> 00:21:04.390 align:start position:0% my own interests or business repurposes that's<00:21:01.520> very<00:21:01.760> refreshing<00:21:02.640> because 00:21:04.390 --> 00:21:04.400 align:start position:0% that's very refreshing because 00:21:04.400 --> 00:21:08.549 align:start position:0% that's very refreshing because um<00:21:06.080> it's<00:21:06.400> kind<00:21:06.640> of<00:21:07.360> part<00:21:07.600> of<00:21:07.760> nature<00:21:08.159> now 00:21:08.549 --> 00:21:08.559 align:start position:0% um it's kind of part of nature now 00:21:08.559 --> 00:21:11.190 align:start position:0% um it's kind of part of nature now it's<00:21:08.720> not<00:21:08.880> a<00:21:09.039> product<00:21:09.679> it's<00:21:09.919> not<00:21:10.720> even<00:21:11.039> an 00:21:11.190 --> 00:21:11.200 align:start position:0% it's not a product it's not even an 00:21:11.200 --> 00:21:12.870 align:start position:0% it's not a product it's not even an instance<00:21:11.520> of<00:21:11.679> a<00:21:11.760> thing<00:21:12.080> that<00:21:12.320> exists<00:21:12.720> on<00:21:12.799> a 00:21:12.870 --> 00:21:12.880 align:start position:0% instance of a thing that exists on a 00:21:12.880 --> 00:21:13.750 align:start position:0% instance of a thing that exists on a disk<00:21:13.280> it's 00:21:13.750 --> 00:21:13.760 align:start position:0% disk it's 00:21:13.760 --> 00:21:17.669 align:start position:0% disk it's literally<00:21:14.159> a<00:21:14.320> standard 00:21:17.669 --> 00:21:17.679 align:start position:0% 00:21:17.679 --> 00:21:20.149 align:start position:0% and<00:21:17.840> still<00:21:18.159> it<00:21:18.240> has<00:21:18.400> value<00:21:19.679> and<00:21:19.840> i<00:21:20.000> think 00:21:20.149 --> 00:21:20.159 align:start position:0% and still it has value and i think 00:21:20.159 --> 00:21:21.750 align:start position:0% and still it has value and i think that's<00:21:20.400> because<00:21:20.720> the<00:21:20.799> fundamental<00:21:21.360> problems 00:21:21.750 --> 00:21:21.760 align:start position:0% that's because the fundamental problems 00:21:21.760 --> 00:21:23.350 align:start position:0% that's because the fundamental problems of<00:21:21.840> programming<00:21:22.320> have<00:21:22.480> not<00:21:22.720> changed 00:21:23.350 --> 00:21:23.360 align:start position:0% of programming have not changed 00:21:23.360 --> 00:21:25.350 align:start position:0% of programming have not changed since<00:21:23.760> people<00:21:24.080> started<00:21:24.320> programming<00:21:25.200> the 00:21:25.350 --> 00:21:25.360 align:start position:0% since people started programming the 00:21:25.360 --> 00:21:27.110 align:start position:0% since people started programming the human<00:21:25.600> brain<00:21:25.919> hasn't<00:21:26.240> changed 00:21:27.110 --> 00:21:27.120 align:start position:0% human brain hasn't changed 00:21:27.120 --> 00:21:28.870 align:start position:0% human brain hasn't changed the<00:21:27.280> user<00:21:27.600> interface<00:21:28.080> the<00:21:28.320> you<00:21:28.400> know<00:21:28.480> the 00:21:28.870 --> 00:21:28.880 align:start position:0% the user interface the you know the 00:21:28.880 --> 00:21:30.310 align:start position:0% the user interface the you know the human<00:21:29.120> computer<00:21:29.440> interface<00:21:29.840> hasn't<00:21:30.080> changed 00:21:30.310 --> 00:21:30.320 align:start position:0% human computer interface hasn't changed 00:21:30.320 --> 00:21:32.310 align:start position:0% human computer interface hasn't changed we<00:21:30.480> still<00:21:30.640> have<00:21:30.720> keyboards<00:21:31.120> symbols<00:21:31.679> letters 00:21:32.310 --> 00:21:32.320 align:start position:0% we still have keyboards symbols letters 00:21:32.320 --> 00:21:35.990 align:start position:0% we still have keyboards symbols letters we<00:21:32.640> use<00:21:33.039> natural<00:21:33.440> language<00:21:34.320> in<00:21:34.480> identifiers 00:21:35.990 --> 00:21:36.000 align:start position:0% we use natural language in identifiers 00:21:36.000 --> 00:21:39.270 align:start position:0% we use natural language in identifiers um<00:21:37.280> we<00:21:37.360> can<00:21:37.520> more<00:21:37.840> you<00:21:37.919> know 00:21:39.270 --> 00:21:39.280 align:start position:0% um we can more you know 00:21:39.280 --> 00:21:41.110 align:start position:0% um we can more you know it's<00:21:39.440> not<00:21:39.600> like<00:21:39.919> people<00:21:40.240> now<00:21:40.480> can<00:21:40.640> hold<00:21:40.880> more 00:21:41.110 --> 00:21:41.120 align:start position:0% it's not like people now can hold more 00:21:41.120 --> 00:21:42.470 align:start position:0% it's not like people now can hold more ideas<00:21:41.440> in<00:21:41.520> their<00:21:41.600> head<00:21:41.840> at<00:21:41.919> the<00:21:42.000> same<00:21:42.159> time<00:21:42.400> as 00:21:42.470 --> 00:21:42.480 align:start position:0% ideas in their head at the same time as 00:21:42.480 --> 00:21:45.750 align:start position:0% ideas in their head at the same time as people<00:21:42.720> in<00:21:42.840> 1981. 00:21:45.750 --> 00:21:45.760 align:start position:0% people in 1981. 00:21:45.760 --> 00:21:47.190 align:start position:0% people in 1981. and<00:21:45.840> the<00:21:46.000> same<00:21:46.159> kinds<00:21:46.400> of<00:21:46.480> things<00:21:46.720> that<00:21:46.799> humans 00:21:47.190 --> 00:21:47.200 align:start position:0% and the same kinds of things that humans 00:21:47.200 --> 00:21:49.190 align:start position:0% and the same kinds of things that humans find<00:21:47.520> intuitive<00:21:48.080> and<00:21:48.240> natural<00:21:48.720> in<00:21:48.799> the<00:21:48.960> same 00:21:49.190 --> 00:21:49.200 align:start position:0% find intuitive and natural in the same 00:21:49.200 --> 00:21:50.950 align:start position:0% find intuitive and natural in the same ways<00:21:49.520> that<00:21:49.679> people<00:21:50.000> think<00:21:50.240> generally<00:21:50.640> are<00:21:50.799> all 00:21:50.950 --> 00:21:50.960 align:start position:0% ways that people think generally are all 00:21:50.960 --> 00:21:51.990 align:start position:0% ways that people think generally are all the<00:21:51.039> same 00:21:51.990 --> 00:21:52.000 align:start position:0% the same 00:21:52.000 --> 00:21:55.270 align:start position:0% the same and<00:21:52.240> so<00:21:52.960> these<00:21:53.200> are<00:21:53.280> the<00:21:53.440> affordances<00:21:54.880> of<00:21:55.120> a 00:21:55.270 --> 00:21:55.280 align:start position:0% and so these are the affordances of a 00:21:55.280 --> 00:21:55.990 align:start position:0% and so these are the affordances of a language 00:21:55.990 --> 00:21:56.000 align:start position:0% language 00:21:56.000 --> 00:21:59.510 align:start position:0% language and<00:21:57.200> common<00:21:57.520> lisp<00:21:58.559> offers<00:21:58.880> these<00:21:59.039> affordances 00:21:59.510 --> 00:21:59.520 align:start position:0% and common lisp offers these affordances 00:21:59.520 --> 00:22:05.909 align:start position:0% and common lisp offers these affordances and<00:21:59.679> it<00:21:59.760> tackles<00:22:00.080> these<00:22:00.320> problems<00:22:00.720> still 00:22:05.909 --> 00:22:05.919 align:start position:0% 00:22:05.919 --> 00:22:09.350 align:start position:0% so<00:22:06.880> there's<00:22:07.120> value<00:22:07.440> there<00:22:07.679> clearly 00:22:09.350 --> 00:22:09.360 align:start position:0% so there's value there clearly 00:22:09.360 --> 00:22:10.789 align:start position:0% so there's value there clearly the<00:22:09.520> other<00:22:09.679> interesting<00:22:10.080> thing<00:22:10.240> about<00:22:10.559> it 00:22:10.789 --> 00:22:10.799 align:start position:0% the other interesting thing about it 00:22:10.799 --> 00:22:12.710 align:start position:0% the other interesting thing about it compared<00:22:11.280> to<00:22:11.840> most<00:22:12.240> other 00:22:12.710 --> 00:22:12.720 align:start position:0% compared to most other 00:22:12.720 --> 00:22:14.390 align:start position:0% compared to most other language<00:22:13.120> implementations<00:22:13.760> and<00:22:13.919> design 00:22:14.390 --> 00:22:14.400 align:start position:0% language implementations and design 00:22:14.400 --> 00:22:16.390 align:start position:0% language implementations and design initiatives<00:22:15.200> is<00:22:15.440> the<00:22:15.600> amount<00:22:15.919> the<00:22:16.080> sheer 00:22:16.390 --> 00:22:16.400 align:start position:0% initiatives is the amount the sheer 00:22:16.400 --> 00:22:18.230 align:start position:0% initiatives is the amount the sheer amount<00:22:16.640> of<00:22:16.799> experience 00:22:18.230 --> 00:22:18.240 align:start position:0% amount of experience 00:22:18.240 --> 00:22:22.470 align:start position:0% amount of experience that<00:22:18.400> went<00:22:18.640> into<00:22:19.039> this<00:22:19.360> thing<00:22:20.720> usually 00:22:22.470 --> 00:22:22.480 align:start position:0% that went into this thing usually 00:22:22.480 --> 00:22:25.510 align:start position:0% that went into this thing usually people<00:22:22.799> when<00:22:23.039> people<00:22:23.679> from<00:22:24.240> closure<00:22:24.799> or<00:22:25.280> even 00:22:25.510 --> 00:22:25.520 align:start position:0% people when people from closure or even 00:22:25.520 --> 00:22:26.950 align:start position:0% people when people from closure or even the<00:22:25.600> scheme<00:22:25.919> community<00:22:26.320> talk<00:22:26.480> about<00:22:26.720> common 00:22:26.950 --> 00:22:26.960 align:start position:0% the scheme community talk about common 00:22:26.960 --> 00:22:27.430 align:start position:0% the scheme community talk about common lisp 00:22:27.430 --> 00:22:27.440 align:start position:0% lisp 00:22:27.440 --> 00:22:30.470 align:start position:0% lisp they<00:22:27.919> sneer<00:22:28.400> at<00:22:28.640> the<00:22:28.720> legacy<00:22:29.840> you<00:22:29.919> know<00:22:30.080> the 00:22:30.470 --> 00:22:30.480 align:start position:0% they sneer at the legacy you know the 00:22:30.480 --> 00:22:33.590 align:start position:0% they sneer at the legacy you know the the<00:22:30.880> problem<00:22:31.280> of<00:22:31.360> backward<00:22:31.679> compatibility 00:22:33.590 --> 00:22:33.600 align:start position:0% the problem of backward compatibility 00:22:33.600 --> 00:22:36.710 align:start position:0% the problem of backward compatibility um<00:22:34.559> but<00:22:34.799> the<00:22:34.880> flip<00:22:35.200> side<00:22:35.440> of<00:22:35.520> that<00:22:36.000> the<00:22:36.159> benefit 00:22:36.710 --> 00:22:36.720 align:start position:0% um but the flip side of that the benefit 00:22:36.720 --> 00:22:40.470 align:start position:0% um but the flip side of that the benefit of<00:22:37.200> a<00:22:37.360> legacy<00:22:38.559> is<00:22:38.720> that<00:22:39.679> everything<00:22:40.080> there<00:22:40.320> was 00:22:40.470 --> 00:22:40.480 align:start position:0% of a legacy is that everything there was 00:22:40.480 --> 00:22:42.870 align:start position:0% of a legacy is that everything there was put<00:22:40.640> in<00:22:40.720> for<00:22:40.880> a<00:22:40.960> reason<00:22:41.360> at<00:22:41.440> some<00:22:41.679> point 00:22:42.870 --> 00:22:42.880 align:start position:0% put in for a reason at some point 00:22:42.880 --> 00:22:46.070 align:start position:0% put in for a reason at some point so<00:22:44.240> it<00:22:44.400> might<00:22:44.799> bother<00:22:45.120> you<00:22:45.360> now<00:22:45.760> that<00:22:45.919> the 00:22:46.070 --> 00:22:46.080 align:start position:0% so it might bother you now that the 00:22:46.080 --> 00:22:48.549 align:start position:0% so it might bother you now that the interfaces<00:22:46.640> aren't<00:22:46.799> perfectly<00:22:47.280> uniform 00:22:48.549 --> 00:22:48.559 align:start position:0% interfaces aren't perfectly uniform 00:22:48.559 --> 00:22:50.789 align:start position:0% interfaces aren't perfectly uniform but<00:22:49.120> who's<00:22:49.440> to<00:22:49.600> say<00:22:49.840> that<00:22:50.000> your<00:22:50.159> perfectly 00:22:50.789 --> 00:22:50.799 align:start position:0% but who's to say that your perfectly 00:22:50.799 --> 00:22:52.390 align:start position:0% but who's to say that your perfectly uniform<00:22:51.280> interface<00:22:51.760> won't<00:22:52.000> be 00:22:52.390 --> 00:22:52.400 align:start position:0% uniform interface won't be 00:22:52.400 --> 00:22:54.070 align:start position:0% uniform interface won't be corrupted<00:22:52.880> in<00:22:52.960> the<00:22:53.039> future<00:22:53.440> when<00:22:53.600> you<00:22:53.760> decide 00:22:54.070 --> 00:22:54.080 align:start position:0% corrupted in the future when you decide 00:22:54.080 --> 00:22:56.149 align:start position:0% corrupted in the future when you decide to<00:22:54.240> use<00:22:54.400> it<00:22:55.120> and<00:22:55.280> considering<00:22:55.760> that 00:22:56.149 --> 00:22:56.159 align:start position:0% to use it and considering that 00:22:56.159 --> 00:22:58.230 align:start position:0% to use it and considering that all<00:22:56.320> of<00:22:56.480> the<00:22:56.559> problems<00:22:57.039> are<00:22:57.120> the<00:22:57.280> same<00:22:58.159> it 00:22:58.230 --> 00:22:58.240 align:start position:0% all of the problems are the same it 00:22:58.240 --> 00:22:59.990 align:start position:0% all of the problems are the same it seems<00:22:58.559> to<00:22:58.640> me<00:22:58.880> unlikely<00:22:59.360> that<00:22:59.520> you're<00:22:59.760> never 00:22:59.990 --> 00:23:00.000 align:start position:0% seems to me unlikely that you're never 00:23:00.000 --> 00:23:01.590 align:start position:0% seems to me unlikely that you're never going<00:23:00.159> to<00:23:00.240> have<00:23:00.480> to 00:23:01.590 --> 00:23:01.600 align:start position:0% going to have to 00:23:01.600 --> 00:23:03.909 align:start position:0% going to have to corrupt<00:23:02.559> whatever<00:23:02.960> idea<00:23:03.440> you<00:23:03.520> have<00:23:03.760> for 00:23:03.909 --> 00:23:03.919 align:start position:0% corrupt whatever idea you have for 00:23:03.919 --> 00:23:05.909 align:start position:0% corrupt whatever idea you have for abstraction<00:23:04.480> now<00:23:04.720> in<00:23:04.799> the<00:23:04.880> future 00:23:05.909 --> 00:23:05.919 align:start position:0% abstraction now in the future 00:23:05.919 --> 00:23:07.510 align:start position:0% abstraction now in the future so<00:23:06.320> why<00:23:06.480> not<00:23:06.640> just<00:23:06.799> start<00:23:07.039> with<00:23:07.120> the<00:23:07.280> set<00:23:07.440> of 00:23:07.510 --> 00:23:07.520 align:start position:0% so why not just start with the set of 00:23:07.520 --> 00:23:09.510 align:start position:0% so why not just start with the set of corruptions<00:23:08.159> from 00:23:09.510 --> 00:23:09.520 align:start position:0% corruptions from 00:23:09.520 --> 00:23:13.270 align:start position:0% corruptions from prehistory<00:23:11.200> and<00:23:11.360> build<00:23:11.679> up<00:23:11.760> from<00:23:11.919> there 00:23:13.270 --> 00:23:13.280 align:start position:0% prehistory and build up from there 00:23:13.280 --> 00:23:14.870 align:start position:0% prehistory and build up from there knowing<00:23:13.600> full<00:23:13.760> well<00:23:14.000> with<00:23:14.159> your<00:23:14.240> eyes<00:23:14.480> open 00:23:14.870 --> 00:23:14.880 align:start position:0% knowing full well with your eyes open 00:23:14.880 --> 00:23:16.950 align:start position:0% knowing full well with your eyes open that<00:23:15.200> these<00:23:15.440> are<00:23:15.520> compromises 00:23:16.950 --> 00:23:16.960 align:start position:0% that these are compromises 00:23:16.960 --> 00:23:19.669 align:start position:0% that these are compromises and<00:23:17.200> that<00:23:18.000> just<00:23:18.480> hindsight<00:23:19.039> doesn't<00:23:19.360> free<00:23:19.520> you 00:23:19.669 --> 00:23:19.679 align:start position:0% and that just hindsight doesn't free you 00:23:19.679 --> 00:23:21.190 align:start position:0% and that just hindsight doesn't free you from<00:23:19.840> having<00:23:20.080> to<00:23:20.240> make 00:23:21.190 --> 00:23:21.200 align:start position:0% from having to make 00:23:21.200 --> 00:23:24.710 align:start position:0% from having to make compromises<00:23:23.360> so<00:23:24.080> um 00:23:24.710 --> 00:23:24.720 align:start position:0% compromises so um 00:23:24.720 --> 00:23:26.070 align:start position:0% compromises so um and<00:23:24.880> yeah<00:23:25.360> i<00:23:25.440> think<00:23:25.520> it's<00:23:25.679> interesting<00:23:26.000> i 00:23:26.070 --> 00:23:26.080 align:start position:0% and yeah i think it's interesting i 00:23:26.080 --> 00:23:28.549 align:start position:0% and yeah i think it's interesting i don't<00:23:26.240> i'm<00:23:26.400> not<00:23:26.640> sure<00:23:27.120> people<00:23:27.440> come<00:23:27.679> together 00:23:28.549 --> 00:23:28.559 align:start position:0% don't i'm not sure people come together 00:23:28.559 --> 00:23:30.070 align:start position:0% don't i'm not sure people come together i'm<00:23:28.720> not<00:23:28.880> aware<00:23:29.200> of<00:23:29.360> any<00:23:29.520> more<00:23:29.760> recent 00:23:30.070 --> 00:23:30.080 align:start position:0% i'm not aware of any more recent 00:23:30.080 --> 00:23:31.750 align:start position:0% i'm not aware of any more recent examples<00:23:30.720> of 00:23:31.750 --> 00:23:31.760 align:start position:0% examples of 00:23:31.760 --> 00:23:33.669 align:start position:0% examples of people<00:23:32.080> with<00:23:32.480> this<00:23:32.720> depth<00:23:33.039> of<00:23:33.200> programming 00:23:33.669 --> 00:23:33.679 align:start position:0% people with this depth of programming 00:23:33.679 --> 00:23:35.510 align:start position:0% people with this depth of programming experience<00:23:34.320> coming<00:23:34.640> together<00:23:35.039> from<00:23:35.200> such 00:23:35.510 --> 00:23:35.520 align:start position:0% experience coming together from such 00:23:35.520 --> 00:23:37.190 align:start position:0% experience coming together from such wide<00:23:35.840> parts<00:23:36.159> of<00:23:36.240> the<00:23:36.320> programming<00:23:36.799> world<00:23:37.039> to 00:23:37.190 --> 00:23:37.200 align:start position:0% wide parts of the programming world to 00:23:37.200 --> 00:23:38.230 align:start position:0% wide parts of the programming world to make<00:23:37.440> something 00:23:38.230 --> 00:23:38.240 align:start position:0% make something 00:23:38.240 --> 00:23:39.750 align:start position:0% make something and<00:23:38.400> to<00:23:38.559> pour<00:23:38.799> their<00:23:38.960> experience<00:23:39.520> and<00:23:39.600> their 00:23:39.750 --> 00:23:39.760 align:start position:0% and to pour their experience and their 00:23:39.760 --> 00:23:41.990 align:start position:0% and to pour their experience and their interests<00:23:40.159> into<00:23:40.400> something 00:23:41.990 --> 00:23:42.000 align:start position:0% interests into something 00:23:42.000 --> 00:23:44.230 align:start position:0% interests into something so<00:23:42.159> i<00:23:42.320> think<00:23:42.880> commonlist<00:23:43.279> was<00:23:43.440> singular<00:23:43.840> as<00:23:44.080> an 00:23:44.230 --> 00:23:44.240 align:start position:0% so i think commonlist was singular as an 00:23:44.240 --> 00:23:46.390 align:start position:0% so i think commonlist was singular as an artifact 00:23:46.390 --> 00:23:46.400 align:start position:0% artifact 00:23:46.400 --> 00:23:49.990 align:start position:0% artifact um<00:23:46.880> yeah<00:23:47.279> so<00:23:47.760> dldr<00:23:49.200> commonlist<00:23:49.600> is<00:23:49.679> a<00:23:49.760> great 00:23:49.990 --> 00:23:50.000 align:start position:0% um yeah so dldr commonlist is a great 00:23:50.000 --> 00:23:51.029 align:start position:0% um yeah so dldr commonlist is a great thing<00:23:50.080> to<00:23:50.240> learn<00:23:50.400> because<00:23:50.559> it's<00:23:50.720> not<00:23:50.880> going 00:23:51.029 --> 00:23:51.039 align:start position:0% thing to learn because it's not going 00:23:51.039 --> 00:23:52.230 align:start position:0% thing to learn because it's not going anywhere<00:23:51.440> it's<00:23:51.520> not<00:23:51.679> going<00:23:51.760> to<00:23:51.919> change 00:23:52.230 --> 00:23:52.240 align:start position:0% anywhere it's not going to change 00:23:52.240 --> 00:23:53.669 align:start position:0% anywhere it's not going to change whatever<00:23:52.559> you<00:23:52.720> learn<00:23:52.880> about<00:23:53.120> commonlist 00:23:53.669 --> 00:23:53.679 align:start position:0% whatever you learn about commonlist 00:23:53.679 --> 00:23:54.789 align:start position:0% whatever you learn about commonlist today<00:23:53.919> and<00:23:54.000> this<00:23:54.159> meeting<00:23:54.400> is<00:23:54.559> going<00:23:54.640> to<00:23:54.640> be 00:23:54.789 --> 00:23:54.799 align:start position:0% today and this meeting is going to be 00:23:54.799 --> 00:23:55.430 align:start position:0% today and this meeting is going to be applicable 00:23:55.430 --> 00:23:55.440 align:start position:0% applicable 00:23:55.440 --> 00:23:57.990 align:start position:0% applicable in<00:23:55.520> 10<00:23:55.760> years<00:23:56.640> whatever<00:23:56.960> code<00:23:57.200> you<00:23:57.360> write<00:23:57.760> is 00:23:57.990 --> 00:23:58.000 align:start position:0% in 10 years whatever code you write is 00:23:58.000 --> 00:24:00.070 align:start position:0% in 10 years whatever code you write is probably<00:23:58.320> going<00:23:58.400> to<00:23:58.480> work 00:24:00.070 --> 00:24:00.080 align:start position:0% probably going to work 00:24:00.080 --> 00:24:03.669 align:start position:0% probably going to work and<00:24:00.240> that's<00:24:00.640> what<00:24:02.640> circling<00:24:03.039> back<00:24:03.200> to<00:24:03.360> me<00:24:03.520> and 00:24:03.669 --> 00:24:03.679 align:start position:0% and that's what circling back to me and 00:24:03.679 --> 00:24:04.470 align:start position:0% and that's what circling back to me and my<00:24:03.919> interest 00:24:04.470 --> 00:24:04.480 align:start position:0% my interest 00:24:04.480 --> 00:24:07.510 align:start position:0% my interest my<00:24:04.720> obsession<00:24:05.919> like<00:24:06.320> when<00:24:06.480> i<00:24:06.720> first<00:24:07.039> got 00:24:07.510 --> 00:24:07.520 align:start position:0% my obsession like when i first got 00:24:07.520 --> 00:24:09.590 align:start position:0% my obsession like when i first got back<00:24:07.679> into<00:24:07.919> common<00:24:08.159> list<00:24:08.400> in<00:24:08.480> 2016<00:24:09.200> i<00:24:09.279> was 00:24:09.590 --> 00:24:09.600 align:start position:0% back into common list in 2016 i was 00:24:09.600 --> 00:24:11.029 align:start position:0% back into common list in 2016 i was programming<00:24:10.240> and<00:24:10.400> reading<00:24:10.640> about<00:24:10.960> it 00:24:11.029 --> 00:24:11.039 align:start position:0% programming and reading about it 00:24:11.039 --> 00:24:12.789 align:start position:0% programming and reading about it probably<00:24:11.440> two<00:24:11.600> or<00:24:11.760> three<00:24:12.000> nights<00:24:12.320> a<00:24:12.400> week 00:24:12.789 --> 00:24:12.799 align:start position:0% probably two or three nights a week 00:24:12.799 --> 00:24:15.430 align:start position:0% probably two or three nights a week before<00:24:13.200> bed<00:24:14.240> like<00:24:14.640> three<00:24:14.880> hours<00:24:15.120> a<00:24:15.200> week<00:24:15.360> or 00:24:15.430 --> 00:24:15.440 align:start position:0% before bed like three hours a week or 00:24:15.440 --> 00:24:16.630 align:start position:0% before bed like three hours a week or something<00:24:15.679> like<00:24:15.840> that 00:24:16.630 --> 00:24:16.640 align:start position:0% something like that 00:24:16.640 --> 00:24:18.310 align:start position:0% something like that and<00:24:16.799> that's<00:24:17.039> been<00:24:17.200> an<00:24:17.360> ebb<00:24:17.520> and<00:24:17.679> a<00:24:17.760> flow<00:24:18.159> like 00:24:18.310 --> 00:24:18.320 align:start position:0% and that's been an ebb and a flow like 00:24:18.320 --> 00:24:19.750 align:start position:0% and that's been an ebb and a flow like i'll<00:24:18.480> pick<00:24:18.720> those<00:24:18.880> projects<00:24:19.360> up 00:24:19.750 --> 00:24:19.760 align:start position:0% i'll pick those projects up 00:24:19.760 --> 00:24:21.510 align:start position:0% i'll pick those projects up three<00:24:19.919> months<00:24:20.159> later<00:24:20.480> six<00:24:20.720> months<00:24:20.960> later<00:24:21.360> a 00:24:21.510 --> 00:24:21.520 align:start position:0% three months later six months later a 00:24:21.520 --> 00:24:22.870 align:start position:0% three months later six months later a year<00:24:21.840> later 00:24:22.870 --> 00:24:22.880 align:start position:0% year later 00:24:22.880 --> 00:24:25.909 align:start position:0% year later um<00:24:24.320> and<00:24:24.640> i<00:24:24.799> don't<00:24:25.039> perceive 00:24:25.909 --> 00:24:25.919 align:start position:0% um and i don't perceive 00:24:25.919 --> 00:24:28.470 align:start position:0% um and i don't perceive like<00:24:26.159> i'm<00:24:26.320> in<00:24:26.400> no<00:24:26.640> rush<00:24:27.360> and<00:24:27.520> it's<00:24:27.679> been<00:24:27.919> really 00:24:28.470 --> 00:24:28.480 align:start position:0% like i'm in no rush and it's been really 00:24:28.480 --> 00:24:29.510 align:start position:0% like i'm in no rush and it's been really honestly<00:24:28.880> delightful 00:24:29.510 --> 00:24:29.520 align:start position:0% honestly delightful 00:24:29.520 --> 00:24:31.029 align:start position:0% honestly delightful and<00:24:29.679> that's<00:24:30.000> partly<00:24:30.320> that's<00:24:30.559> the<00:24:30.640> delight<00:24:30.960> of 00:24:31.029 --> 00:24:31.039 align:start position:0% and that's partly that's the delight of 00:24:31.039 --> 00:24:32.149 align:start position:0% and that's partly that's the delight of a<00:24:31.120> hobby<00:24:31.440> project<00:24:31.760> because<00:24:31.919> there's<00:24:32.080> no 00:24:32.149 --> 00:24:32.159 align:start position:0% a hobby project because there's no 00:24:32.159 --> 00:24:33.510 align:start position:0% a hobby project because there's no business<00:24:32.559> pressure 00:24:33.510 --> 00:24:33.520 align:start position:0% business pressure 00:24:33.520 --> 00:24:37.190 align:start position:0% business pressure you<00:24:33.600> know<00:24:34.320> um<00:24:34.799> but<00:24:35.039> it's<00:24:35.200> also<00:24:35.520> partly<00:24:35.919> because 00:24:37.190 --> 00:24:37.200 align:start position:0% you know um but it's also partly because 00:24:37.200 --> 00:24:39.029 align:start position:0% you know um but it's also partly because uh<00:24:37.919> i'm<00:24:38.080> confident<00:24:38.480> these<00:24:38.640> things<00:24:38.880> aren't 00:24:39.029 --> 00:24:39.039 align:start position:0% uh i'm confident these things aren't 00:24:39.039 --> 00:24:40.470 align:start position:0% uh i'm confident these things aren't going<00:24:39.120> to<00:24:39.200> change<00:24:39.600> and<00:24:39.760> i<00:24:39.840> can<00:24:40.080> really<00:24:40.240> learn 00:24:40.470 --> 00:24:40.480 align:start position:0% going to change and i can really learn 00:24:40.480 --> 00:24:42.230 align:start position:0% going to change and i can really learn at<00:24:40.559> my<00:24:40.720> own<00:24:40.880> pace<00:24:41.200> in<00:24:41.279> a<00:24:41.360> way<00:24:41.520> that 00:24:42.230 --> 00:24:42.240 align:start position:0% at my own pace in a way that 00:24:42.240 --> 00:24:43.590 align:start position:0% at my own pace in a way that is<00:24:42.400> difficult<00:24:42.720> to<00:24:42.880> do<00:24:43.039> with<00:24:43.200> other<00:24:43.360> things 00:24:43.590 --> 00:24:43.600 align:start position:0% is difficult to do with other things 00:24:43.600 --> 00:24:47.430 align:start position:0% is difficult to do with other things that<00:24:43.679> change<00:24:43.919> more<00:24:44.840> frequently 00:24:47.430 --> 00:24:47.440 align:start position:0% that change more frequently 00:24:47.440 --> 00:24:50.310 align:start position:0% that change more frequently so<00:24:48.080> when<00:24:48.240> i<00:24:48.320> talk<00:24:48.559> about<00:24:49.200> the<00:24:49.520> trade-offs<00:24:50.240> and 00:24:50.310 --> 00:24:50.320 align:start position:0% so when i talk about the trade-offs and 00:24:50.320 --> 00:24:51.909 align:start position:0% so when i talk about the trade-offs and the<00:24:50.480> history<00:24:50.960> and<00:24:51.039> stuff 00:24:51.909 --> 00:24:51.919 align:start position:0% the history and stuff 00:24:51.919 --> 00:24:54.549 align:start position:0% the history and stuff not<00:24:52.159> only<00:24:52.480> was<00:24:52.880> lisp<00:24:53.360> designed<00:24:53.919> by<00:24:54.159> people 00:24:54.549 --> 00:24:54.559 align:start position:0% not only was lisp designed by people 00:24:54.559 --> 00:24:55.590 align:start position:0% not only was lisp designed by people with<00:24:54.880> a<00:24:55.039> really 00:24:55.590 --> 00:24:55.600 align:start position:0% with a really 00:24:55.600 --> 00:24:58.789 align:start position:0% with a really depth<00:24:56.159> d<00:24:56.400> really<00:24:56.640> deep<00:24:56.960> and<00:24:57.279> wide<00:24:57.679> experience 00:24:58.789 --> 00:24:58.799 align:start position:0% depth d really deep and wide experience 00:24:58.799 --> 00:25:00.149 align:start position:0% depth d really deep and wide experience but<00:24:58.960> we<00:24:59.120> have<00:24:59.279> some<00:24:59.440> visibility<00:25:00.000> in<00:25:00.080> the 00:25:00.149 --> 00:25:00.159 align:start position:0% but we have some visibility in the 00:25:00.159 --> 00:25:02.789 align:start position:0% but we have some visibility in the modern<00:25:00.480> era<00:25:01.120> into<00:25:01.760> those<00:25:02.000> experiences<00:25:02.720> and 00:25:02.789 --> 00:25:02.799 align:start position:0% modern era into those experiences and 00:25:02.799 --> 00:25:03.990 align:start position:0% modern era into those experiences and there's<00:25:03.039> a<00:25:03.120> few<00:25:03.279> different<00:25:03.520> sources<00:25:03.919> of 00:25:03.990 --> 00:25:04.000 align:start position:0% there's a few different sources of 00:25:04.000 --> 00:25:05.669 align:start position:0% there's a few different sources of information 00:25:05.669 --> 00:25:05.679 align:start position:0% information 00:25:05.679 --> 00:25:08.789 align:start position:0% information this<00:25:06.320> is<00:25:06.480> an<00:25:06.640> email<00:25:07.360> from 00:25:08.789 --> 00:25:08.799 align:start position:0% this is an email from 00:25:08.799 --> 00:25:11.380 align:start position:0% this is an email from the<00:25:09.039> original<00:25:09.600> i<00:25:09.679> believe<00:25:10.000> it's<00:25:10.240> the<00:25:10.400> original 00:25:11.380 --> 00:25:11.390 align:start position:0% the original i believe it's the original 00:25:11.390 --> 00:25:12.830 align:start position:0% the original i believe it's the original [Music] 00:25:12.830 --> 00:25:12.840 align:start position:0% [Music] 00:25:12.840 --> 00:25:14.070 align:start position:0% [Music] multi-institution 00:25:14.070 --> 00:25:14.080 align:start position:0% multi-institution 00:25:14.080 --> 00:25:16.630 align:start position:0% multi-institution design<00:25:14.720> mailing<00:25:15.039> list<00:25:15.919> so<00:25:16.080> there<00:25:16.240> were<00:25:16.400> people 00:25:16.630 --> 00:25:16.640 align:start position:0% design mailing list so there were people 00:25:16.640 --> 00:25:17.510 align:start position:0% design mailing list so there were people from<00:25:16.880> mit 00:25:17.510 --> 00:25:17.520 align:start position:0% from mit 00:25:17.520 --> 00:25:21.190 align:start position:0% from mit stanford<00:25:18.720> symbolics<00:25:20.080> all<00:25:20.240> the<00:25:20.480> major<00:25:20.799> players 00:25:21.190 --> 00:25:21.200 align:start position:0% stanford symbolics all the major players 00:25:21.200 --> 00:25:23.029 align:start position:0% stanford symbolics all the major players of<00:25:21.279> the<00:25:21.440> early<00:25:21.679> 80s 00:25:23.029 --> 00:25:23.039 align:start position:0% of the early 80s 00:25:23.039 --> 00:25:25.669 align:start position:0% of the early 80s and<00:25:23.200> they<00:25:23.360> were<00:25:23.440> on<00:25:23.520> an<00:25:23.679> email<00:25:24.000> list<00:25:25.039> and<00:25:25.440> they 00:25:25.669 --> 00:25:25.679 align:start position:0% and they were on an email list and they 00:25:25.679 --> 00:25:26.870 align:start position:0% and they were on an email list and they discussed 00:25:26.870 --> 00:25:26.880 align:start position:0% discussed 00:25:26.880 --> 00:25:30.630 align:start position:0% discussed fundamental<00:25:27.360> design<00:25:27.760> problems<00:25:28.559> and 00:25:30.630 --> 00:25:30.640 align:start position:0% fundamental design problems and 00:25:30.640 --> 00:25:31.909 align:start position:0% fundamental design problems and we<00:25:30.799> have<00:25:30.960> visibility<00:25:31.520> into<00:25:31.760> those 00:25:31.909 --> 00:25:31.919 align:start position:0% we have visibility into those 00:25:31.919 --> 00:25:33.909 align:start position:0% we have visibility into those discussions<00:25:32.720> some<00:25:32.880> of<00:25:32.960> the<00:25:33.039> discussions<00:25:33.600> are 00:25:33.909 --> 00:25:33.919 align:start position:0% discussions some of the discussions are 00:25:33.919 --> 00:25:36.549 align:start position:0% discussions some of the discussions are kind<00:25:34.080> of<00:25:34.159> contentious 00:25:36.549 --> 00:25:36.559 align:start position:0% kind of contentious 00:25:36.559 --> 00:25:38.230 align:start position:0% kind of contentious some<00:25:36.960> some<00:25:37.200> of<00:25:37.360> a<00:25:37.440> lot<00:25:37.600> of<00:25:37.679> the<00:25:37.760> times<00:25:38.080> they're 00:25:38.230 --> 00:25:38.240 align:start position:0% some some of a lot of the times they're 00:25:38.240 --> 00:25:39.669 align:start position:0% some some of a lot of the times they're referring<00:25:38.799> to 00:25:39.669 --> 00:25:39.679 align:start position:0% referring to 00:25:39.679 --> 00:25:41.510 align:start position:0% referring to meetings<00:25:40.000> they<00:25:40.159> had<00:25:40.400> in<00:25:40.480> person<00:25:41.200> and<00:25:41.279> so<00:25:41.440> you 00:25:41.510 --> 00:25:41.520 align:start position:0% meetings they had in person and so you 00:25:41.520 --> 00:25:43.350 align:start position:0% meetings they had in person and so you don't<00:25:41.679> get<00:25:41.840> the<00:25:42.000> full<00:25:42.240> picture 00:25:43.350 --> 00:25:43.360 align:start position:0% don't get the full picture 00:25:43.360 --> 00:25:45.430 align:start position:0% don't get the full picture but<00:25:43.679> it's<00:25:43.919> nevertheless<00:25:44.480> it's<00:25:44.640> a<00:25:44.720> window<00:25:45.279> like 00:25:45.430 --> 00:25:45.440 align:start position:0% but it's nevertheless it's a window like 00:25:45.440 --> 00:25:46.789 align:start position:0% but it's nevertheless it's a window like here's<00:25:45.679> an<00:25:45.840> example<00:25:46.159> that<00:25:46.240> i<00:25:46.320> pulled<00:25:46.559> up<00:25:46.640> this 00:25:46.789 --> 00:25:46.799 align:start position:0% here's an example that i pulled up this 00:25:46.799 --> 00:25:49.190 align:start position:0% here's an example that i pulled up this is<00:25:46.960> an<00:25:47.120> email<00:25:47.360> from<00:25:47.440> somebody<00:25:47.760> at<00:25:47.840> mit<00:25:48.320> about 00:25:49.190 --> 00:25:49.200 align:start position:0% is an email from somebody at mit about 00:25:49.200 --> 00:25:50.310 align:start position:0% is an email from somebody at mit about they're<00:25:49.360> talking<00:25:49.679> about<00:25:49.840> commonless 00:25:50.310 --> 00:25:50.320 align:start position:0% they're talking about commonless 00:25:50.320 --> 00:25:52.789 align:start position:0% they're talking about commonless language<00:25:50.720> probably<00:25:51.279> the<00:25:51.360> first<00:25:51.679> edition 00:25:52.789 --> 00:25:52.799 align:start position:0% language probably the first edition 00:25:52.799 --> 00:25:55.909 align:start position:0% language probably the first edition which<00:25:53.120> was<00:25:53.520> um<00:25:54.240> it's<00:25:54.400> like<00:25:54.559> a<00:25:54.640> 1200<00:25:55.120> page<00:25:55.520> book 00:25:55.909 --> 00:25:55.919 align:start position:0% which was um it's like a 1200 page book 00:25:55.919 --> 00:25:57.590 align:start position:0% which was um it's like a 1200 page book that<00:25:56.080> was<00:25:56.320> a 00:25:57.590 --> 00:25:57.600 align:start position:0% that was a 00:25:57.600 --> 00:25:59.510 align:start position:0% that was a draft<00:25:58.000> of<00:25:58.080> the<00:25:58.240> specification<00:25:59.120> that<00:25:59.279> guy 00:25:59.510 --> 00:25:59.520 align:start position:0% draft of the specification that guy 00:25:59.520 --> 00:26:03.750 align:start position:0% draft of the specification that guy still<00:25:59.679> put<00:25:59.840> together<00:26:00.240> in<00:26:00.400> i<00:26:00.480> think<00:26:00.640> 1981<00:26:01.440> or<00:26:01.600> 82 00:26:03.750 --> 00:26:03.760 align:start position:0% still put together in i think 1981 or 82 00:26:03.760 --> 00:26:05.590 align:start position:0% still put together in i think 1981 or 82 and<00:26:03.919> that<00:26:04.159> book<00:26:04.400> circulated<00:26:05.039> around<00:26:05.360> at<00:26:05.440> these 00:26:05.590 --> 00:26:05.600 align:start position:0% and that book circulated around at these 00:26:05.600 --> 00:26:07.110 align:start position:0% and that book circulated around at these different<00:26:05.840> institutions<00:26:06.720> and<00:26:06.799> they<00:26:06.960> would 00:26:07.110 --> 00:26:07.120 align:start position:0% different institutions and they would 00:26:07.120 --> 00:26:08.149 align:start position:0% different institutions and they would read<00:26:07.440> it<00:26:07.600> and 00:26:08.149 --> 00:26:08.159 align:start position:0% read it and 00:26:08.159 --> 00:26:10.710 align:start position:0% read it and think<00:26:08.400> about<00:26:08.720> it<00:26:08.880> and<00:26:08.960> prototype<00:26:09.600> things<00:26:10.559> and 00:26:10.710 --> 00:26:10.720 align:start position:0% think about it and prototype things and 00:26:10.720 --> 00:26:11.669 align:start position:0% think about it and prototype things and then<00:26:10.960> they<00:26:11.120> would 00:26:11.669 --> 00:26:11.679 align:start position:0% then they would 00:26:11.679 --> 00:26:12.710 align:start position:0% then they would communicate<00:26:12.159> to<00:26:12.240> each<00:26:12.400> other<00:26:12.559> on<00:26:12.640> this 00:26:12.710 --> 00:26:12.720 align:start position:0% communicate to each other on this 00:26:12.720 --> 00:26:15.110 align:start position:0% communicate to each other on this mailing<00:26:13.039> list<00:26:13.200> so<00:26:13.360> this<00:26:13.520> guy's<00:26:13.840> asking<00:26:14.240> about 00:26:15.110 --> 00:26:15.120 align:start position:0% mailing list so this guy's asking about 00:26:15.120 --> 00:26:18.230 align:start position:0% mailing list so this guy's asking about the<00:26:15.279> thing<00:26:15.520> for<00:26:15.679> making<00:26:16.000> a<00:26:16.640> hash<00:26:16.960> table 00:26:18.230 --> 00:26:18.240 align:start position:0% the thing for making a hash table 00:26:18.240 --> 00:26:21.909 align:start position:0% the thing for making a hash table uh<00:26:18.480> takes<00:26:18.799> a<00:26:18.960> test<00:26:20.240> keyword<00:26:20.640> argument 00:26:21.909 --> 00:26:21.919 align:start position:0% uh takes a test keyword argument 00:26:21.919 --> 00:26:25.190 align:start position:0% uh takes a test keyword argument and<00:26:22.320> one<00:26:22.480> of<00:26:22.640> the<00:26:22.840> equality<00:26:24.080> comparators<00:26:24.880> is 00:26:25.190 --> 00:26:25.200 align:start position:0% and one of the equality comparators is 00:26:25.200 --> 00:26:25.909 align:start position:0% and one of the equality comparators is is<00:26:25.440> missing 00:26:25.909 --> 00:26:25.919 align:start position:0% is missing 00:26:25.919 --> 00:26:27.510 align:start position:0% is missing you<00:26:26.000> know<00:26:26.159> why<00:26:26.400> is<00:26:26.480> that<00:26:26.880> it<00:26:27.039> seems<00:26:27.279> like<00:26:27.440> it 00:26:27.510 --> 00:26:27.520 align:start position:0% you know why is that it seems like it 00:26:27.520 --> 00:26:29.750 align:start position:0% you know why is that it seems like it should<00:26:27.840> be<00:26:28.080> in<00:26:28.159> there<00:26:28.799> and<00:26:28.960> so<00:26:29.120> people<00:26:29.440> respond 00:26:29.750 --> 00:26:29.760 align:start position:0% should be in there and so people respond 00:26:29.760 --> 00:26:31.669 align:start position:0% should be in there and so people respond to<00:26:29.919> him 00:26:31.669 --> 00:26:31.679 align:start position:0% to him 00:26:31.679 --> 00:26:34.230 align:start position:0% to him um<00:26:32.960> separately<00:26:33.440> there<00:26:33.679> is<00:26:33.760> this<00:26:33.919> thing<00:26:34.080> called 00:26:34.230 --> 00:26:34.240 align:start position:0% um separately there is this thing called 00:26:34.240 --> 00:26:35.750 align:start position:0% um separately there is this thing called the<00:26:34.320> hyperspec<00:26:34.880> which<00:26:35.039> i<00:26:35.120> mentioned<00:26:35.440> which<00:26:35.600> is 00:26:35.750 --> 00:26:35.760 align:start position:0% the hyperspec which i mentioned which is 00:26:35.760 --> 00:26:37.029 align:start position:0% the hyperspec which i mentioned which is a<00:26:35.840> hyperlinked 00:26:37.029 --> 00:26:37.039 align:start position:0% a hyperlinked 00:26:37.039 --> 00:26:40.710 align:start position:0% a hyperlinked documentation<00:26:38.080> of<00:26:39.760> everything<00:26:40.240> more<00:26:40.400> or<00:26:40.480> less 00:26:40.710 --> 00:26:40.720 align:start position:0% documentation of everything more or less 00:26:40.720 --> 00:26:41.909 align:start position:0% documentation of everything more or less everything<00:26:40.960> in<00:26:41.039> common<00:26:41.279> list<00:26:41.440> so<00:26:41.600> anything 00:26:41.909 --> 00:26:41.919 align:start position:0% everything in common list so anything 00:26:41.919 --> 00:26:43.430 align:start position:0% everything in common list so anything that's<00:26:42.159> named<00:26:42.480> in<00:26:42.559> common<00:26:42.880> lisp<00:26:43.200> has 00:26:43.430 --> 00:26:43.440 align:start position:0% that's named in common lisp has 00:26:43.440 --> 00:26:45.190 align:start position:0% that's named in common lisp has represented<00:26:43.919> somewhere<00:26:44.320> in<00:26:44.400> the 00:26:45.190 --> 00:26:45.200 align:start position:0% represented somewhere in the 00:26:45.200 --> 00:26:48.710 align:start position:0% represented somewhere in the hyperspec<00:26:46.960> this<00:26:47.200> is<00:26:47.279> not<00:26:47.440> the<00:26:47.600> specification 00:26:48.710 --> 00:26:48.720 align:start position:0% hyperspec this is not the specification 00:26:48.720 --> 00:26:52.149 align:start position:0% hyperspec this is not the specification this<00:26:48.960> is<00:26:49.440> a<00:26:49.679> proprietary<00:26:51.600> view 00:26:52.149 --> 00:26:52.159 align:start position:0% this is a proprietary view 00:26:52.159 --> 00:26:53.909 align:start position:0% this is a proprietary view of<00:26:52.320> the<00:26:52.400> specification<00:26:53.120> with<00:26:53.360> examples<00:26:53.840> that 00:26:53.909 --> 00:26:53.919 align:start position:0% of the specification with examples that 00:26:53.919 --> 00:26:55.830 align:start position:0% of the specification with examples that was<00:26:54.080> put<00:26:54.240> together<00:26:54.640> by<00:26:54.960> ken<00:26:55.200> pittman<00:26:55.600> who's 00:26:55.830 --> 00:26:55.840 align:start position:0% was put together by ken pittman who's 00:26:55.840 --> 00:26:57.110 align:start position:0% was put together by ken pittman who's one<00:26:56.000> of<00:26:56.080> the 00:26:57.110 --> 00:26:57.120 align:start position:0% one of the 00:26:57.120 --> 00:27:04.149 align:start position:0% one of the original<00:26:58.159> lisp<00:26:59.039> luminary<00:26:59.440> people<00:26:59.679> from<00:26:59.919> mit 00:27:04.149 --> 00:27:04.159 align:start position:0% 00:27:04.159 --> 00:27:06.710 align:start position:0% so<00:27:04.640> this<00:27:05.039> this<00:27:05.200> basically<00:27:05.600> is<00:27:05.760> like<00:27:05.919> a<00:27:06.000> javadoc 00:27:06.710 --> 00:27:06.720 align:start position:0% so this this basically is like a javadoc 00:27:06.720 --> 00:27:07.750 align:start position:0% so this this basically is like a javadoc for<00:27:06.880> lisp 00:27:07.750 --> 00:27:07.760 align:start position:0% for lisp 00:27:07.760 --> 00:27:10.630 align:start position:0% for lisp and<00:27:08.080> you<00:27:08.159> can<00:27:08.320> see<00:27:09.679> why<00:27:09.840> that<00:27:10.080> is<00:27:10.240> you<00:27:10.320> get<00:27:10.400> your 00:27:10.630 --> 00:27:10.640 align:start position:0% and you can see why that is you get your 00:27:10.640 --> 00:27:11.909 align:start position:0% and you can see why that is you get your arguments<00:27:11.039> your<00:27:11.120> return<00:27:11.440> value<00:27:11.760> your 00:27:11.909 --> 00:27:11.919 align:start position:0% arguments your return value your 00:27:11.919 --> 00:27:13.269 align:start position:0% arguments your return value your description<00:27:12.559> and<00:27:12.640> then<00:27:12.799> a<00:27:12.880> little<00:27:13.039> bit<00:27:13.200> of 00:27:13.269 --> 00:27:13.279 align:start position:0% description and then a little bit of 00:27:13.279 --> 00:27:14.630 align:start position:0% description and then a little bit of high<00:27:13.440> level<00:27:13.679> overview 00:27:14.630 --> 00:27:14.640 align:start position:0% high level overview 00:27:14.640 --> 00:27:16.390 align:start position:0% high level overview but<00:27:14.799> the<00:27:14.960> interesting<00:27:15.360> thing<00:27:15.600> is<00:27:15.679> that<00:27:16.080> these 00:27:16.390 --> 00:27:16.400 align:start position:0% but the interesting thing is that these 00:27:16.400 --> 00:27:18.789 align:start position:0% but the interesting thing is that these javadoc<00:27:16.960> things<00:27:17.360> link<00:27:17.679> to 00:27:18.789 --> 00:27:18.799 align:start position:0% javadoc things link to 00:27:18.799 --> 00:27:21.430 align:start position:0% javadoc things link to design<00:27:19.200> issues<00:27:19.919> and<00:27:20.480> represented<00:27:21.039> in<00:27:21.120> the<00:27:21.279> set 00:27:21.430 --> 00:27:21.440 align:start position:0% design issues and represented in the set 00:27:21.440 --> 00:27:23.029 align:start position:0% design issues and represented in the set of<00:27:21.520> design<00:27:21.919> issues<00:27:22.320> is 00:27:23.029 --> 00:27:23.039 align:start position:0% of design issues is 00:27:23.039 --> 00:27:24.630 align:start position:0% of design issues is a<00:27:23.120> reference<00:27:23.520> to<00:27:23.600> the<00:27:23.760> problem<00:27:24.000> we<00:27:24.159> saw<00:27:24.480> from 00:27:24.630 --> 00:27:24.640 align:start position:0% a reference to the problem we saw from 00:27:24.640 --> 00:27:27.990 align:start position:0% a reference to the problem we saw from the<00:27:24.799> design<00:27:25.120> mailing<00:27:25.440> list<00:27:25.679> which<00:27:25.919> is 00:27:27.990 --> 00:27:28.000 align:start position:0% the design mailing list which is 00:27:28.000 --> 00:27:29.430 align:start position:0% the design mailing list which is they<00:27:28.159> had<00:27:28.320> like<00:27:28.559> a<00:27:28.640> committee<00:27:29.039> discussion 00:27:29.430 --> 00:27:29.440 align:start position:0% they had like a committee discussion 00:27:29.440 --> 00:27:31.430 align:start position:0% they had like a committee discussion about<00:27:29.760> which<00:27:30.000> equality<00:27:30.640> constructs 00:27:31.430 --> 00:27:31.440 align:start position:0% about which equality constructs 00:27:31.440 --> 00:27:35.190 align:start position:0% about which equality constructs hash<00:27:31.760> tables<00:27:32.559> should<00:27:32.840> support 00:27:35.190 --> 00:27:35.200 align:start position:0% hash tables should support 00:27:35.200 --> 00:27:37.430 align:start position:0% hash tables should support um<00:27:36.000> so<00:27:36.240> you<00:27:36.320> can<00:27:36.559> if<00:27:36.799> you<00:27:36.880> know<00:27:37.039> if<00:27:37.120> you<00:27:37.200> have<00:27:37.279> a 00:27:37.430 --> 00:27:37.440 align:start position:0% um so you can if you know if you have a 00:27:37.440 --> 00:27:39.029 align:start position:0% um so you can if you know if you have a problem<00:27:37.679> with<00:27:37.919> why<00:27:38.080> common<00:27:38.480> lisp<00:27:38.720> does<00:27:38.960> it 00:27:39.029 --> 00:27:39.039 align:start position:0% problem with why common lisp does it 00:27:39.039 --> 00:27:41.190 align:start position:0% problem with why common lisp does it this<00:27:39.200> way<00:27:39.520> you<00:27:39.679> can<00:27:39.840> find<00:27:40.080> the<00:27:40.240> source 00:27:41.190 --> 00:27:41.200 align:start position:0% this way you can find the source 00:27:41.200 --> 00:27:45.510 align:start position:0% this way you can find the source and<00:27:42.000> uh<00:27:43.760> i<00:27:43.919> think 00:27:45.510 --> 00:27:45.520 align:start position:0% and uh i think 00:27:45.520 --> 00:27:47.430 align:start position:0% and uh i think i<00:27:45.600> think<00:27:45.760> that's<00:27:46.000> really<00:27:46.240> cool<00:27:46.880> i<00:27:46.960> think<00:27:47.120> very 00:27:47.430 --> 00:27:47.440 align:start position:0% i think that's really cool i think very 00:27:47.440 --> 00:27:48.710 align:start position:0% i think that's really cool i think very few<00:27:47.600> things<00:27:47.919> that<00:27:48.159> we 00:27:48.710 --> 00:27:48.720 align:start position:0% few things that we 00:27:48.720 --> 00:27:50.389 align:start position:0% few things that we use<00:27:49.039> that<00:27:49.200> are<00:27:49.360> designed<00:27:49.840> to<00:27:49.919> give<00:27:50.159> you<00:27:50.240> this 00:27:50.389 --> 00:27:50.399 align:start position:0% use that are designed to give you this 00:27:50.399 --> 00:27:52.389 align:start position:0% use that are designed to give you this kind<00:27:50.559> of<00:27:50.640> visibility<00:27:51.279> into<00:27:51.440> the<00:27:51.600> why<00:27:51.840> and<00:27:52.000> how 00:27:52.389 --> 00:27:52.399 align:start position:0% kind of visibility into the why and how 00:27:52.399 --> 00:27:56.950 align:start position:0% kind of visibility into the why and how and<00:27:52.559> the<00:27:52.640> context 00:27:56.950 --> 00:27:56.960 align:start position:0% 00:27:56.960 --> 00:27:58.789 align:start position:0% and<00:27:57.200> that's<00:27:57.440> actually<00:27:57.679> not<00:27:57.840> fair<00:27:58.080> to<00:27:58.320> python 00:27:58.789 --> 00:27:58.799 align:start position:0% and that's actually not fair to python 00:27:58.799 --> 00:28:00.630 align:start position:0% and that's actually not fair to python with<00:27:58.880> the<00:27:59.039> peps<00:27:59.760> and<00:27:59.919> stuff<00:28:00.080> like<00:28:00.240> that 00:28:00.630 --> 00:28:00.640 align:start position:0% with the peps and stuff like that 00:28:00.640 --> 00:28:03.990 align:start position:0% with the peps and stuff like that like<00:28:00.799> this<00:28:01.120> this<00:28:01.360> tradition<00:28:01.760> is<00:28:01.919> alive<00:28:02.799> um<00:28:03.600> but 00:28:03.990 --> 00:28:04.000 align:start position:0% like this this tradition is alive um but 00:28:04.000 --> 00:28:06.950 align:start position:0% like this this tradition is alive um but i<00:28:04.159> think<00:28:04.480> uh<00:28:05.919> common<00:28:06.159> list<00:28:06.399> was<00:28:06.559> an<00:28:06.640> instance 00:28:06.950 --> 00:28:06.960 align:start position:0% i think uh common list was an instance 00:28:06.960 --> 00:28:07.669 align:start position:0% i think uh common list was an instance of<00:28:07.120> it 00:28:07.669 --> 00:28:07.679 align:start position:0% of it 00:28:07.679 --> 00:28:11.590 align:start position:0% of it which<00:28:07.919> is<00:28:08.799> for<00:28:08.960> it's<00:28:09.120> for<00:28:09.279> its<00:28:09.440> benefit 00:28:11.590 --> 00:28:11.600 align:start position:0% which is for it's for its benefit 00:28:11.600 --> 00:28:14.230 align:start position:0% which is for it's for its benefit um<00:28:11.840> so<00:28:12.000> circling<00:28:12.399> back<00:28:12.559> to<00:28:12.640> closure<00:28:13.840> what<00:28:14.080> is 00:28:14.230 --> 00:28:14.240 align:start position:0% um so circling back to closure what is 00:28:14.240 --> 00:28:18.470 align:start position:0% um so circling back to closure what is the<00:28:14.399> killer<00:28:14.640> feature<00:28:14.960> of<00:28:15.039> closure<00:28:15.520> this<00:28:15.760> is<00:28:15.919> a 00:28:18.470 --> 00:28:18.480 align:start position:0% 00:28:18.480 --> 00:28:20.710 align:start position:0% this<00:28:18.640> is<00:28:18.799> a<00:28:19.039> subjective<00:28:19.679> question<00:28:20.240> you<00:28:20.399> know<00:28:20.640> i 00:28:20.710 --> 00:28:20.720 align:start position:0% this is a subjective question you know i 00:28:20.720 --> 00:28:21.669 align:start position:0% this is a subjective question you know i mean<00:28:20.880> some<00:28:21.039> people 00:28:21.669 --> 00:28:21.679 align:start position:0% mean some people 00:28:21.679 --> 00:28:24.870 align:start position:0% mean some people really<00:28:22.000> like<00:28:22.159> the<00:28:22.320> lisp<00:28:22.559> syntax<00:28:23.039> aspect<00:28:23.440> of<00:28:23.679> it 00:28:24.870 --> 00:28:24.880 align:start position:0% really like the lisp syntax aspect of it 00:28:24.880 --> 00:28:28.149 align:start position:0% really like the lisp syntax aspect of it uh<00:28:25.760> certainly<00:28:27.200> the<00:28:27.360> immutable<00:28:27.760> connect 00:28:28.149 --> 00:28:28.159 align:start position:0% uh certainly the immutable connect 00:28:28.159 --> 00:28:33.430 align:start position:0% uh certainly the immutable connect collections<00:28:28.799> we're<00:28:28.960> getting<00:28:29.279> a 00:28:33.430 --> 00:28:33.440 align:start position:0% 00:28:33.440 --> 00:28:44.389 align:start position:0% few<00:28:42.840> questions 00:28:44.389 --> 00:28:44.399 align:start position:0% few questions 00:28:44.399 --> 00:28:47.510 align:start position:0% few questions oh<00:28:44.720> so<00:28:45.200> uh<00:28:45.679> proprietary<00:28:46.399> view<00:28:46.880> the 00:28:47.510 --> 00:28:47.520 align:start position:0% oh so uh proprietary view the 00:28:47.520 --> 00:28:51.269 align:start position:0% oh so uh proprietary view the the<00:28:48.799> the<00:28:48.960> hyperspec<00:28:50.000> is<00:28:50.480> a 00:28:51.269 --> 00:28:51.279 align:start position:0% the the hyperspec is a 00:28:51.279 --> 00:28:54.389 align:start position:0% the the hyperspec is a document<00:28:51.840> with<00:28:52.080> a<00:28:52.240> copyright<00:28:53.760> and<00:28:54.240> that 00:28:54.389 --> 00:28:54.399 align:start position:0% document with a copyright and that 00:28:54.399 --> 00:28:57.430 align:start position:0% document with a copyright and that copyright<00:28:54.960> belongs<00:28:55.360> to<00:28:55.600> a<00:28:55.760> company 00:28:57.430 --> 00:28:57.440 align:start position:0% copyright belongs to a company 00:28:57.440 --> 00:29:00.549 align:start position:0% copyright belongs to a company and<00:28:58.320> the<00:28:59.360> copyright<00:28:59.919> does<00:29:00.159> not 00:29:00.549 --> 00:29:00.559 align:start position:0% and the copyright does not 00:29:00.559 --> 00:29:03.029 align:start position:0% and the copyright does not allow<00:29:01.279> arbitrarily<00:29:02.000> copying<00:29:02.480> and<00:29:02.559> pasting 00:29:03.029 --> 00:29:03.039 align:start position:0% allow arbitrarily copying and pasting 00:29:03.039 --> 00:29:03.750 align:start position:0% allow arbitrarily copying and pasting hyperspec 00:29:03.750 --> 00:29:03.760 align:start position:0% hyperspec 00:29:03.760 --> 00:29:06.310 align:start position:0% hyperspec so<00:29:03.919> while<00:29:05.440> the<00:29:05.679> constructs<00:29:06.159> that<00:29:06.240> the 00:29:06.310 --> 00:29:06.320 align:start position:0% so while the constructs that the 00:29:06.320 --> 00:29:08.310 align:start position:0% so while the constructs that the hyperspec<00:29:06.880> mentions<00:29:07.200> are<00:29:07.600> free<00:29:07.840> and<00:29:08.000> open<00:29:08.240> and 00:29:08.310 --> 00:29:08.320 align:start position:0% hyperspec mentions are free and open and 00:29:08.320 --> 00:29:10.070 align:start position:0% hyperspec mentions are free and open and you<00:29:08.480> can<00:29:08.640> talk<00:29:08.880> about<00:29:09.120> them 00:29:10.070 --> 00:29:10.080 align:start position:0% you can talk about them 00:29:10.080 --> 00:29:14.149 align:start position:0% you can talk about them in<00:29:10.240> any<00:29:10.399> normal<00:29:10.720> way<00:29:11.760> you<00:29:11.919> can't<00:29:12.559> for<00:29:12.720> example 00:29:14.149 --> 00:29:14.159 align:start position:0% in any normal way you can't for example 00:29:14.159 --> 00:29:16.870 align:start position:0% in any normal way you can't for example take<00:29:14.399> the<00:29:14.480> text<00:29:14.799> of<00:29:14.960> the<00:29:15.039> hypertext<00:29:15.919> or<00:29:16.320> of<00:29:16.480> the 00:29:16.870 --> 00:29:16.880 align:start position:0% take the text of the hypertext or of the 00:29:16.880 --> 00:29:18.789 align:start position:0% take the text of the hypertext or of the hyperspec<00:29:17.520> and<00:29:17.600> copy<00:29:17.919> it<00:29:18.000> into<00:29:18.159> your<00:29:18.320> program 00:29:18.789 --> 00:29:18.799 align:start position:0% hyperspec and copy it into your program 00:29:18.799 --> 00:29:19.510 align:start position:0% hyperspec and copy it into your program or 00:29:19.510 --> 00:29:19.520 align:start position:0% or 00:29:19.520 --> 00:29:20.789 align:start position:0% or you<00:29:19.679> know<00:29:19.760> make<00:29:19.919> a<00:29:20.000> new<00:29:20.159> website<00:29:20.559> called 00:29:20.789 --> 00:29:20.799 align:start position:0% you know make a new website called 00:29:20.799 --> 00:29:22.950 align:start position:0% you know make a new website called allen's<00:29:21.120> hyperspec 00:29:22.950 --> 00:29:22.960 align:start position:0% allen's hyperspec 00:29:22.960 --> 00:29:24.870 align:start position:0% allen's hyperspec uh<00:29:23.840> where<00:29:24.080> i've<00:29:24.159> just<00:29:24.320> replaced<00:29:24.720> all 00:29:24.870 --> 00:29:24.880 align:start position:0% uh where i've just replaced all 00:29:24.880 --> 00:29:26.630 align:start position:0% uh where i've just replaced all instances<00:29:25.279> of<00:29:25.679> ken<00:29:25.919> pitman<00:29:26.240> with<00:29:26.399> alan 00:29:26.630 --> 00:29:26.640 align:start position:0% instances of ken pitman with alan 00:29:26.640 --> 00:29:28.310 align:start position:0% instances of ken pitman with alan deibert<00:29:27.039> or<00:29:27.120> all<00:29:27.279> instances<00:29:27.679> of<00:29:27.760> common<00:29:28.000> lisp 00:29:28.310 --> 00:29:28.320 align:start position:0% deibert or all instances of common lisp 00:29:28.320 --> 00:29:30.070 align:start position:0% deibert or all instances of common lisp with<00:29:28.559> you<00:29:28.640> know 00:29:30.070 --> 00:29:30.080 align:start position:0% with you know 00:29:30.080 --> 00:29:33.350 align:start position:0% with you know rainbow<00:29:30.399> unicorn<00:29:30.799> or<00:29:30.960> whatever<00:29:33.039> does<00:29:33.200> that 00:29:33.350 --> 00:29:33.360 align:start position:0% rainbow unicorn or whatever does that 00:29:33.360 --> 00:29:39.430 align:start position:0% rainbow unicorn or whatever does that answer<00:29:33.600> a<00:29:33.679> question<00:29:34.000> tori 00:29:39.430 --> 00:29:39.440 align:start position:0% 00:29:39.440 --> 00:29:43.190 align:start position:0% no<00:29:39.679> problem<00:29:42.159> so<00:29:42.320> yeah<00:29:42.559> killer<00:29:42.880> feature<00:29:43.120> of 00:29:43.190 --> 00:29:43.200 align:start position:0% no problem so yeah killer feature of 00:29:43.200 --> 00:29:45.510 align:start position:0% no problem so yeah killer feature of closure 00:29:45.510 --> 00:29:45.520 align:start position:0% closure 00:29:45.520 --> 00:29:48.549 align:start position:0% closure java<00:29:45.840> interval<00:29:46.399> java<00:29:46.640> interrupt<00:29:46.960> that's<00:29:47.120> huge 00:29:48.549 --> 00:29:48.559 align:start position:0% java interval java interrupt that's huge 00:29:48.559 --> 00:29:49.750 align:start position:0% java interval java interrupt that's huge but<00:29:48.720> i<00:29:48.799> think<00:29:48.960> the<00:29:49.039> killer<00:29:49.279> feature<00:29:49.520> is<00:29:49.600> rich 00:29:49.750 --> 00:29:49.760 align:start position:0% but i think the killer feature is rich 00:29:49.760 --> 00:29:51.830 align:start position:0% but i think the killer feature is rich hickey 00:29:51.830 --> 00:29:51.840 align:start position:0% hickey 00:29:51.840 --> 00:29:53.510 align:start position:0% hickey and<00:29:52.080> the<00:29:52.159> reason<00:29:52.399> i<00:29:52.559> say<00:29:52.720> that<00:29:52.960> is<00:29:53.039> because 00:29:53.510 --> 00:29:53.520 align:start position:0% and the reason i say that is because 00:29:53.520 --> 00:29:55.269 align:start position:0% and the reason i say that is because rich<00:29:53.760> hickey 00:29:55.269 --> 00:29:55.279 align:start position:0% rich hickey 00:29:55.279 --> 00:29:56.950 align:start position:0% rich hickey yes<00:29:55.520> he<00:29:55.600> made<00:29:55.840> a<00:29:55.919> language<00:29:56.399> yes<00:29:56.640> he<00:29:56.720> put<00:29:56.880> all 00:29:56.950 --> 00:29:56.960 align:start position:0% yes he made a language yes he put all 00:29:56.960 --> 00:29:58.630 align:start position:0% yes he made a language yes he put all these<00:29:57.120> features<00:29:57.440> together<00:29:57.840> but<00:29:57.919> there's<00:29:58.240> a 00:29:58.630 --> 00:29:58.640 align:start position:0% these features together but there's a 00:29:58.640 --> 00:30:00.710 align:start position:0% these features together but there's a consistent<00:29:59.200> philosophy<00:30:00.320> behind<00:30:00.640> the 00:30:00.710 --> 00:30:00.720 align:start position:0% consistent philosophy behind the 00:30:00.720 --> 00:30:01.830 align:start position:0% consistent philosophy behind the language 00:30:01.830 --> 00:30:01.840 align:start position:0% language 00:30:01.840 --> 00:30:04.310 align:start position:0% language and<00:30:02.640> most<00:30:02.960> importantly<00:30:03.520> rich<00:30:03.760> makes<00:30:04.000> it<00:30:04.080> very 00:30:04.310 --> 00:30:04.320 align:start position:0% and most importantly rich makes it very 00:30:04.320 --> 00:30:05.269 align:start position:0% and most importantly rich makes it very clear<00:30:04.640> up<00:30:04.799> front 00:30:05.269 --> 00:30:05.279 align:start position:0% clear up front 00:30:05.279 --> 00:30:08.470 align:start position:0% clear up front why<00:30:05.600> he's<00:30:05.840> doing<00:30:06.080> what<00:30:06.240> he's<00:30:06.480> doing<00:30:07.600> so 00:30:08.470 --> 00:30:08.480 align:start position:0% why he's doing what he's doing so 00:30:08.480 --> 00:30:11.029 align:start position:0% why he's doing what he's doing so when<00:30:08.799> anyone<00:30:09.200> comes<00:30:09.440> to<00:30:09.520> closure<00:30:10.640> they're<00:30:10.799> not 00:30:11.029 --> 00:30:11.039 align:start position:0% when anyone comes to closure they're not 00:30:11.039 --> 00:30:13.430 align:start position:0% when anyone comes to closure they're not looking<00:30:11.360> at<00:30:11.520> individual<00:30:12.080> features 00:30:13.430 --> 00:30:13.440 align:start position:0% looking at individual features 00:30:13.440 --> 00:30:15.830 align:start position:0% looking at individual features they're<00:30:14.240> connecting<00:30:14.799> with<00:30:14.960> this<00:30:15.200> person<00:30:15.679> and 00:30:15.830 --> 00:30:15.840 align:start position:0% they're connecting with this person and 00:30:15.840 --> 00:30:16.630 align:start position:0% they're connecting with this person and his<00:30:16.080> story 00:30:16.630 --> 00:30:16.640 align:start position:0% his story 00:30:16.640 --> 00:30:19.350 align:start position:0% his story and<00:30:16.799> his<00:30:17.039> needs<00:30:17.520> and<00:30:17.600> his<00:30:17.840> philosophy<00:30:19.200> and 00:30:19.350 --> 00:30:19.360 align:start position:0% and his needs and his philosophy and 00:30:19.360 --> 00:30:21.269 align:start position:0% and his needs and his philosophy and once<00:30:19.600> you're 00:30:21.269 --> 00:30:21.279 align:start position:0% once you're 00:30:21.279 --> 00:30:23.110 align:start position:0% once you're holding<00:30:21.679> that<00:30:22.000> in<00:30:22.080> your<00:30:22.240> head<00:30:22.559> then<00:30:22.880> all<00:30:23.039> the 00:30:23.110 --> 00:30:23.120 align:start position:0% holding that in your head then all the 00:30:23.120 --> 00:30:24.710 align:start position:0% holding that in your head then all the features<00:30:23.520> and<00:30:23.600> stuff<00:30:23.840> in<00:30:23.919> closure<00:30:24.320> fall<00:30:24.559> out 00:30:24.710 --> 00:30:24.720 align:start position:0% features and stuff in closure fall out 00:30:24.720 --> 00:30:26.549 align:start position:0% features and stuff in closure fall out naturally<00:30:25.200> like<00:30:25.360> you<00:30:25.520> can<00:30:25.760> understand<00:30:26.320> his 00:30:26.549 --> 00:30:26.559 align:start position:0% naturally like you can understand his 00:30:26.559 --> 00:30:27.750 align:start position:0% naturally like you can understand his perspective<00:30:27.120> and<00:30:27.200> why<00:30:27.360> he<00:30:27.520> made<00:30:27.679> the 00:30:27.750 --> 00:30:27.760 align:start position:0% perspective and why he made the 00:30:27.760 --> 00:30:29.190 align:start position:0% perspective and why he made the decisions<00:30:28.159> he<00:30:28.320> did 00:30:29.190 --> 00:30:29.200 align:start position:0% decisions he did 00:30:29.200 --> 00:30:31.750 align:start position:0% decisions he did and<00:30:29.279> that<00:30:29.600> empowers<00:30:30.159> you<00:30:30.559> to<00:30:31.039> really<00:30:31.360> design 00:30:31.750 --> 00:30:31.760 align:start position:0% and that empowers you to really design 00:30:31.760 --> 00:30:33.830 align:start position:0% and that empowers you to really design closure<00:30:32.159> for<00:30:32.320> yourself 00:30:33.830 --> 00:30:33.840 align:start position:0% closure for yourself 00:30:33.840 --> 00:30:36.630 align:start position:0% closure for yourself in<00:30:33.919> a<00:30:34.000> way<00:30:34.159> that<00:30:34.480> also<00:30:34.720> is<00:30:34.960> i<00:30:35.039> think<00:30:35.279> rare<00:30:35.840> uh 00:30:36.630 --> 00:30:36.640 align:start position:0% in a way that also is i think rare uh 00:30:36.640 --> 00:30:38.149 align:start position:0% in a way that also is i think rare uh generally<00:30:37.039> when<00:30:37.200> people 00:30:38.149 --> 00:30:38.159 align:start position:0% generally when people 00:30:38.159 --> 00:30:39.909 align:start position:0% generally when people are<00:30:38.480> promoting<00:30:38.880> technology<00:30:39.440> they<00:30:39.600> talk<00:30:39.760> about 00:30:39.909 --> 00:30:39.919 align:start position:0% are promoting technology they talk about 00:30:39.919 --> 00:30:41.510 align:start position:0% are promoting technology they talk about specific<00:30:40.399> features<00:30:41.120> or 00:30:41.510 --> 00:30:41.520 align:start position:0% specific features or 00:30:41.520 --> 00:30:43.669 align:start position:0% specific features or if<00:30:41.600> you're<00:30:41.760> lucky<00:30:42.080> they'll<00:30:42.320> talk<00:30:42.480> about<00:30:43.600> you 00:30:43.669 --> 00:30:43.679 align:start position:0% if you're lucky they'll talk about you 00:30:43.679 --> 00:30:44.950 align:start position:0% if you're lucky they'll talk about you know<00:30:44.000> stories 00:30:44.950 --> 00:30:44.960 align:start position:0% know stories 00:30:44.960 --> 00:30:48.630 align:start position:0% know stories um<00:30:45.520> like<00:30:45.679> user<00:30:46.080> stories<00:30:46.559> or<00:30:46.880> case<00:30:47.120> analysis 00:30:48.630 --> 00:30:48.640 align:start position:0% um like user stories or case analysis 00:30:48.640 --> 00:30:51.029 align:start position:0% um like user stories or case analysis what<00:30:48.799> do<00:30:48.880> they<00:30:48.960> call<00:30:49.120> that<00:30:49.279> case<00:30:49.520> studies<00:30:50.640> um 00:30:51.029 --> 00:30:51.039 align:start position:0% what do they call that case studies um 00:30:51.039 --> 00:30:53.350 align:start position:0% what do they call that case studies um but<00:30:51.200> you<00:30:51.360> don't<00:30:51.440> really<00:30:51.679> get<00:30:51.840> a<00:30:51.919> holistic 00:30:53.350 --> 00:30:53.360 align:start position:0% but you don't really get a holistic 00:30:53.360 --> 00:30:56.389 align:start position:0% but you don't really get a holistic fundamental<00:30:53.919> view<00:30:54.640> part<00:30:54.880> of<00:30:54.960> that<00:30:55.200> is<00:30:55.279> because 00:30:56.389 --> 00:30:56.399 align:start position:0% fundamental view part of that is because 00:30:56.399 --> 00:30:59.750 align:start position:0% fundamental view part of that is because uh<00:30:56.640> it's<00:30:56.799> really<00:30:57.120> rare<00:30:57.440> for<00:30:58.399> for<00:30:59.200> large 00:30:59.750 --> 00:30:59.760 align:start position:0% uh it's really rare for for large 00:30:59.760 --> 00:31:01.509 align:start position:0% uh it's really rare for for large intellectual<00:31:00.320> artifacts<00:31:00.960> in<00:31:01.039> computing<00:31:01.440> to 00:31:01.509 --> 00:31:01.519 align:start position:0% intellectual artifacts in computing to 00:31:01.519 --> 00:31:03.590 align:start position:0% intellectual artifacts in computing to be<00:31:02.080> really<00:31:02.320> designed<00:31:02.720> by<00:31:02.880> one<00:31:03.120> person 00:31:03.590 --> 00:31:03.600 align:start position:0% be really designed by one person 00:31:03.600 --> 00:31:06.389 align:start position:0% be really designed by one person that's<00:31:04.000> pretty<00:31:04.240> rare<00:31:04.960> even<00:31:05.279> you<00:31:05.360> know<00:31:05.519> most 00:31:06.389 --> 00:31:06.399 align:start position:0% that's pretty rare even you know most 00:31:06.399 --> 00:31:08.630 align:start position:0% that's pretty rare even you know most most<00:31:06.640> things<00:31:06.880> are<00:31:06.960> designed<00:31:07.360> by 00:31:08.630 --> 00:31:08.640 align:start position:0% most things are designed by 00:31:08.640 --> 00:31:11.269 align:start position:0% most things are designed by small<00:31:08.960> groups<00:31:09.200> of<00:31:09.279> people<00:31:10.559> but<00:31:10.720> this<00:31:10.960> really 00:31:11.269 --> 00:31:11.279 align:start position:0% small groups of people but this really 00:31:11.279 --> 00:31:11.750 align:start position:0% small groups of people but this really is 00:31:11.750 --> 00:31:11.760 align:start position:0% is 00:31:11.760 --> 00:31:14.230 align:start position:0% is a<00:31:11.840> one<00:31:12.080> person<00:31:12.720> thing<00:31:13.120> and<00:31:13.279> so<00:31:13.760> because<00:31:14.000> it's<00:31:14.159> a 00:31:14.230 --> 00:31:14.240 align:start position:0% a one person thing and so because it's a 00:31:14.240 --> 00:31:15.750 align:start position:0% a one person thing and so because it's a one<00:31:14.399> person<00:31:14.640> thing<00:31:14.799> you<00:31:14.960> have<00:31:15.120> unprecedented 00:31:15.750 --> 00:31:15.760 align:start position:0% one person thing you have unprecedented 00:31:15.760 --> 00:31:17.509 align:start position:0% one person thing you have unprecedented visibility<00:31:16.240> into<00:31:16.480> why 00:31:17.509 --> 00:31:17.519 align:start position:0% visibility into why 00:31:17.519 --> 00:31:20.070 align:start position:0% visibility into why and<00:31:18.240> i<00:31:18.320> think<00:31:18.480> it's<00:31:18.640> great<00:31:18.880> i<00:31:19.039> i'm<00:31:19.679> this<00:31:19.919> this 00:31:20.070 --> 00:31:20.080 align:start position:0% and i think it's great i i'm this this 00:31:20.080 --> 00:31:21.509 align:start position:0% and i think it's great i i'm this this was<00:31:20.240> new<00:31:20.399> to<00:31:20.480> me<00:31:20.720> like<00:31:20.880> i 00:31:21.509 --> 00:31:21.519 align:start position:0% was new to me like i 00:31:21.519 --> 00:31:22.789 align:start position:0% was new to me like i when<00:31:21.679> i<00:31:21.840> when<00:31:22.000> i<00:31:22.080> learned<00:31:22.240> closure<00:31:22.559> this<00:31:22.720> was 00:31:22.789 --> 00:31:22.799 align:start position:0% when i when i learned closure this was 00:31:22.799 --> 00:31:25.269 align:start position:0% when i when i learned closure this was very<00:31:22.960> compelling<00:31:23.440> to<00:31:23.519> me<00:31:23.679> because 00:31:25.269 --> 00:31:25.279 align:start position:0% very compelling to me because 00:31:25.279 --> 00:31:27.350 align:start position:0% very compelling to me because it<00:31:25.519> seemed<00:31:25.760> like<00:31:26.240> i<00:31:26.320> had<00:31:26.480> to<00:31:26.559> learn<00:31:26.799> java<00:31:27.200> just 00:31:27.350 --> 00:31:27.360 align:start position:0% it seemed like i had to learn java just 00:31:27.360 --> 00:31:29.350 align:start position:0% it seemed like i had to learn java just because<00:31:27.600> that's<00:31:27.760> what<00:31:27.919> everybody<00:31:28.320> learned 00:31:29.350 --> 00:31:29.360 align:start position:0% because that's what everybody learned 00:31:29.360 --> 00:31:31.909 align:start position:0% because that's what everybody learned and<00:31:30.000> if<00:31:30.240> i<00:31:30.320> wanted<00:31:30.559> to<00:31:30.720> do<00:31:30.880> stuff<00:31:31.120> on<00:31:31.440> linux<00:31:31.760> i 00:31:31.909 --> 00:31:31.919 align:start position:0% and if i wanted to do stuff on linux i 00:31:31.919 --> 00:31:33.190 align:start position:0% and if i wanted to do stuff on linux i had<00:31:32.000> to<00:31:32.240> learn<00:31:32.480> c<00:31:32.720> because<00:31:32.880> that's<00:31:33.039> what 00:31:33.190 --> 00:31:33.200 align:start position:0% had to learn c because that's what 00:31:33.200 --> 00:31:34.630 align:start position:0% had to learn c because that's what everybody<00:31:33.600> does 00:31:34.630 --> 00:31:34.640 align:start position:0% everybody does 00:31:34.640 --> 00:31:38.230 align:start position:0% everybody does but<00:31:36.080> neither<00:31:36.480> of<00:31:36.559> those<00:31:36.720> things 00:31:38.230 --> 00:31:38.240 align:start position:0% but neither of those things 00:31:38.240 --> 00:31:40.630 align:start position:0% but neither of those things came<00:31:38.559> with<00:31:39.440> this<00:31:39.679> deep<00:31:39.919> philosophical 00:31:40.630 --> 00:31:40.640 align:start position:0% came with this deep philosophical 00:31:40.640 --> 00:31:41.750 align:start position:0% came with this deep philosophical historical 00:31:41.750 --> 00:31:41.760 align:start position:0% historical 00:31:41.760 --> 00:31:43.350 align:start position:0% historical background<00:31:42.399> and<00:31:42.480> so<00:31:42.640> that<00:31:42.880> i<00:31:42.960> was<00:31:43.120> i<00:31:43.200> was 00:31:43.350 --> 00:31:43.360 align:start position:0% background and so that i was i was 00:31:43.360 --> 00:31:44.789 align:start position:0% background and so that i was i was almost<00:31:43.600> shocked<00:31:43.919> by<00:31:44.080> this 00:31:44.789 --> 00:31:44.799 align:start position:0% almost shocked by this 00:31:44.799 --> 00:31:47.750 align:start position:0% almost shocked by this i'm<00:31:45.120> giddy<00:31:45.760> and<00:31:45.919> i<00:31:46.000> think<00:31:47.279> all<00:31:47.440> these<00:31:47.600> things 00:31:47.750 --> 00:31:47.760 align:start position:0% i'm giddy and i think all these things 00:31:47.760 --> 00:31:49.110 align:start position:0% i'm giddy and i think all these things are<00:31:47.919> still<00:31:48.159> on<00:31:48.240> youtube 00:31:49.110 --> 00:31:49.120 align:start position:0% are still on youtube 00:31:49.120 --> 00:31:51.029 align:start position:0% are still on youtube and<00:31:49.279> this<00:31:49.440> is<00:31:49.519> a<00:31:49.600> great<00:31:49.760> reason<00:31:50.080> to<00:31:50.720> to<00:31:50.880> use 00:31:51.029 --> 00:31:51.039 align:start position:0% and this is a great reason to to use 00:31:51.039 --> 00:31:52.230 align:start position:0% and this is a great reason to to use closure<00:31:51.279> today<00:31:51.679> still<00:31:51.919> and 00:31:52.230 --> 00:31:52.240 align:start position:0% closure today still and 00:31:52.240 --> 00:31:55.509 align:start position:0% closure today still and it's<00:31:52.399> awesome 00:31:55.509 --> 00:31:55.519 align:start position:0% 00:31:55.519 --> 00:31:59.029 align:start position:0% so<00:31:55.679> yeah<00:31:56.080> you<00:31:56.240> know<00:31:58.080> rich<00:31:58.320> is<00:31:58.480> big<00:31:58.640> on<00:31:58.880> on 00:31:59.029 --> 00:31:59.039 align:start position:0% so yeah you know rich is big on on 00:31:59.039 --> 00:32:00.389 align:start position:0% so yeah you know rich is big on on rationale<00:31:59.840> and 00:32:00.389 --> 00:32:00.399 align:start position:0% rationale and 00:32:00.399 --> 00:32:03.509 align:start position:0% rationale and and<00:32:00.880> doing<00:32:01.200> things<00:32:01.440> with<00:32:01.679> intent<00:32:02.799> and<00:32:03.200> in<00:32:03.360> an 00:32:03.509 --> 00:32:03.519 align:start position:0% and doing things with intent and in an 00:32:03.519 --> 00:32:05.029 align:start position:0% and doing things with intent and in an open<00:32:03.679> source<00:32:04.000> project<00:32:04.320> this<00:32:04.480> is<00:32:04.640> critical 00:32:05.029 --> 00:32:05.039 align:start position:0% open source project this is critical 00:32:05.039 --> 00:32:06.149 align:start position:0% open source project this is critical because 00:32:06.149 --> 00:32:06.159 align:start position:0% because 00:32:06.159 --> 00:32:08.710 align:start position:0% because uh<00:32:06.399> the<00:32:06.559> intent<00:32:07.679> messages<00:32:08.080> to<00:32:08.240> people<00:32:08.480> whether 00:32:08.710 --> 00:32:08.720 align:start position:0% uh the intent messages to people whether 00:32:08.720 --> 00:32:09.909 align:start position:0% uh the intent messages to people whether or<00:32:08.799> not<00:32:08.960> they<00:32:09.120> want<00:32:09.200> to<00:32:09.279> have<00:32:09.440> anything<00:32:09.760> to<00:32:09.840> do 00:32:09.909 --> 00:32:09.919 align:start position:0% or not they want to have anything to do 00:32:09.919 --> 00:32:10.549 align:start position:0% or not they want to have anything to do with<00:32:10.000> your<00:32:10.159> thing 00:32:10.549 --> 00:32:10.559 align:start position:0% with your thing 00:32:10.559 --> 00:32:11.909 align:start position:0% with your thing whether<00:32:10.799> they<00:32:10.960> want<00:32:11.120> to<00:32:11.200> help<00:32:11.440> you<00:32:11.679> you<00:32:11.760> know 00:32:11.909 --> 00:32:11.919 align:start position:0% whether they want to help you you know 00:32:11.919 --> 00:32:15.110 align:start position:0% whether they want to help you you know are<00:32:12.080> you<00:32:12.240> in<00:32:12.399> alignment<00:32:12.799> with<00:32:12.960> what<00:32:13.120> they<00:32:13.279> want 00:32:15.110 --> 00:32:15.120 align:start position:0% are you in alignment with what they want 00:32:15.120 --> 00:32:16.789 align:start position:0% are you in alignment with what they want if<00:32:15.279> you<00:32:15.440> don't<00:32:15.679> have<00:32:15.840> this<00:32:16.080> rationale<00:32:16.640> then 00:32:16.789 --> 00:32:16.799 align:start position:0% if you don't have this rationale then 00:32:16.799 --> 00:32:17.909 align:start position:0% if you don't have this rationale then you<00:32:16.880> get<00:32:16.960> pull<00:32:17.200> requests<00:32:17.519> that<00:32:17.679> you<00:32:17.760> have<00:32:17.840> to 00:32:17.909 --> 00:32:17.919 align:start position:0% you get pull requests that you have to 00:32:17.919 --> 00:32:19.430 align:start position:0% you get pull requests that you have to shut<00:32:18.159> down 00:32:19.430 --> 00:32:19.440 align:start position:0% shut down 00:32:19.440 --> 00:32:21.190 align:start position:0% shut down which<00:32:19.679> makes<00:32:19.919> everybody<00:32:20.240> feel<00:32:20.480> bad<00:32:20.799> so<00:32:21.039> it's 00:32:21.190 --> 00:32:21.200 align:start position:0% which makes everybody feel bad so it's 00:32:21.200 --> 00:32:22.950 align:start position:0% which makes everybody feel bad so it's better<00:32:21.440> to<00:32:21.600> say<00:32:21.840> what<00:32:22.000> you're<00:32:22.159> going<00:32:22.480> for<00:32:22.799> and 00:32:22.950 --> 00:32:22.960 align:start position:0% better to say what you're going for and 00:32:22.960 --> 00:32:24.789 align:start position:0% better to say what you're going for and let<00:32:23.200> people<00:32:23.440> come<00:32:23.600> to<00:32:23.760> you<00:32:24.000> rather<00:32:24.320> than<00:32:24.640> not 00:32:24.789 --> 00:32:24.799 align:start position:0% let people come to you rather than not 00:32:24.799 --> 00:32:26.310 align:start position:0% let people come to you rather than not say<00:32:24.960> what<00:32:25.120> you're<00:32:25.200> going<00:32:25.440> for 00:32:26.310 --> 00:32:26.320 align:start position:0% say what you're going for 00:32:26.320 --> 00:32:27.669 align:start position:0% say what you're going for and<00:32:26.480> people<00:32:26.720> come<00:32:26.880> to<00:32:26.960> you<00:32:27.039> with<00:32:27.200> ideas<00:32:27.519> that 00:32:27.669 --> 00:32:27.679 align:start position:0% and people come to you with ideas that 00:32:27.679 --> 00:32:29.509 align:start position:0% and people come to you with ideas that aren't<00:32:27.840> in<00:32:28.000> alignment<00:32:28.399> with<00:32:28.480> your<00:32:28.720> own<00:32:29.200> and 00:32:29.509 --> 00:32:29.519 align:start position:0% aren't in alignment with your own and 00:32:29.519 --> 00:32:31.590 align:start position:0% aren't in alignment with your own and you<00:32:29.679> know<00:32:29.840> for<00:32:30.000> himself 00:32:31.590 --> 00:32:31.600 align:start position:0% you know for himself 00:32:31.600 --> 00:32:33.669 align:start position:0% you know for himself i<00:32:31.679> know<00:32:32.080> richard<00:32:32.399> this<00:32:32.559> for<00:32:32.720> himself<00:32:33.120> this<00:32:33.360> is 00:32:33.669 --> 00:32:33.679 align:start position:0% i know richard this for himself this is 00:32:33.679 --> 00:32:35.590 align:start position:0% i know richard this for himself this is this<00:32:33.840> is<00:32:34.000> the<00:32:34.159> outcome<00:32:34.480> of<00:32:34.640> years<00:32:34.960> of<00:32:35.120> his<00:32:35.360> own 00:32:35.590 --> 00:32:35.600 align:start position:0% this is the outcome of years of his own 00:32:35.600 --> 00:32:37.509 align:start position:0% this is the outcome of years of his own thinking<00:32:36.000> and<00:32:36.080> research 00:32:37.509 --> 00:32:37.519 align:start position:0% thinking and research 00:32:37.519 --> 00:32:42.710 align:start position:0% thinking and research um<00:32:38.480> and<00:32:38.640> it's<00:32:38.880> great<00:32:39.519> uh<00:32:39.919> and<00:32:40.840> um 00:32:42.710 --> 00:32:42.720 align:start position:0% um and it's great uh and um 00:32:42.720 --> 00:32:44.950 align:start position:0% um and it's great uh and um lisp<00:32:43.279> doesn't<00:32:43.760> their<00:32:43.919> common<00:32:44.240> lisp<00:32:44.640> doesn't 00:32:44.950 --> 00:32:44.960 align:start position:0% lisp doesn't their common lisp doesn't 00:32:44.960 --> 00:32:46.710 align:start position:0% lisp doesn't their common lisp doesn't have<00:32:45.200> a<00:32:45.279> document<00:32:45.679> like<00:32:46.080> this<00:32:46.320> like<00:32:46.559> there 00:32:46.710 --> 00:32:46.720 align:start position:0% have a document like this like there 00:32:46.720 --> 00:32:49.190 align:start position:0% have a document like this like there isn't<00:32:46.960> a<00:32:47.039> common<00:32:47.360> lisp<00:32:47.679> rationale<00:32:48.240> document 00:32:49.190 --> 00:32:49.200 align:start position:0% isn't a common lisp rationale document 00:32:49.200 --> 00:32:51.269 align:start position:0% isn't a common lisp rationale document part<00:32:49.440> of<00:32:49.519> that<00:32:49.679> is<00:32:49.840> because<00:32:50.159> there<00:32:50.320> is<00:32:50.559> no 00:32:51.269 --> 00:32:51.279 align:start position:0% part of that is because there is no 00:32:51.279 --> 00:32:52.310 align:start position:0% part of that is because there is no single<00:32:51.600> person 00:32:52.310 --> 00:32:52.320 align:start position:0% single person 00:32:52.320 --> 00:32:54.789 align:start position:0% single person who<00:32:52.480> could<00:32:52.640> have<00:32:52.720> written<00:32:53.039> it<00:32:54.320> the<00:32:54.480> other<00:32:54.640> part 00:32:54.789 --> 00:32:54.799 align:start position:0% who could have written it the other part 00:32:54.799 --> 00:32:56.389 align:start position:0% who could have written it the other part of<00:32:54.880> it<00:32:55.039> is<00:32:55.200> a<00:32:55.279> lot<00:32:55.440> of<00:32:55.519> their<00:32:55.679> rationale<00:32:56.240> was 00:32:56.389 --> 00:32:56.399 align:start position:0% of it is a lot of their rationale was 00:32:56.399 --> 00:32:57.509 align:start position:0% of it is a lot of their rationale was implied 00:32:57.509 --> 00:32:57.519 align:start position:0% implied 00:32:57.519 --> 00:32:59.990 align:start position:0% implied to<00:32:57.760> themselves<00:32:58.240> at<00:32:58.320> the<00:32:58.480> time<00:32:59.200> so<00:32:59.360> you<00:32:59.519> can 00:32:59.990 --> 00:33:00.000 align:start position:0% to themselves at the time so you can 00:33:00.000 --> 00:33:01.590 align:start position:0% to themselves at the time so you can piece<00:33:00.480> something<00:33:00.799> like<00:33:00.960> this<00:33:01.120> together<00:33:01.440> for 00:33:01.590 --> 00:33:01.600 align:start position:0% piece something like this together for 00:33:01.600 --> 00:33:03.110 align:start position:0% piece something like this together for yourself<00:33:02.000> if<00:33:02.159> you<00:33:02.240> do<00:33:02.399> the<00:33:02.480> research<00:33:02.880> and<00:33:02.960> you 00:33:03.110 --> 00:33:03.120 align:start position:0% yourself if you do the research and you 00:33:03.120 --> 00:33:04.230 align:start position:0% yourself if you do the research and you can<00:33:03.200> find<00:33:03.360> it<00:33:03.519> in<00:33:03.600> the<00:33:03.679> emails<00:33:04.080> and<00:33:04.159> the 00:33:04.230 --> 00:33:04.240 align:start position:0% can find it in the emails and the 00:33:04.240 --> 00:33:07.750 align:start position:0% can find it in the emails and the hyperspec<00:33:04.880> and<00:33:04.960> the<00:33:05.120> issues<00:33:05.519> list 00:33:07.750 --> 00:33:07.760 align:start position:0% 00:33:07.760 --> 00:33:08.950 align:start position:0% but<00:33:07.919> it's<00:33:08.000> not<00:33:08.159> all<00:33:08.240> in<00:33:08.320> one<00:33:08.480> place<00:33:08.720> like<00:33:08.880> this 00:33:08.950 --> 00:33:08.960 align:start position:0% but it's not all in one place like this 00:33:08.960 --> 00:33:18.789 align:start position:0% but it's not all in one place like this but<00:33:09.120> i<00:33:09.200> think<00:33:09.279> this<00:33:09.440> is<00:33:09.519> very<00:33:09.760> powerful 00:33:18.789 --> 00:33:18.799 align:start position:0% 00:33:18.799 --> 00:33:20.230 align:start position:0% all<00:33:18.960> right<00:33:19.200> the<00:33:19.279> champion<00:33:19.679> so<00:33:19.840> that's<00:33:20.000> where<00:33:20.159> i 00:33:20.230 --> 00:33:20.240 align:start position:0% all right the champion so that's where i 00:33:20.240 --> 00:33:22.470 align:start position:0% all right the champion so that's where i introduce<00:33:20.640> myself<00:33:21.200> i'm<00:33:21.360> the<00:33:21.519> champion 00:33:22.470 --> 00:33:22.480 align:start position:0% introduce myself i'm the champion 00:33:22.480 --> 00:33:25.269 align:start position:0% introduce myself i'm the champion i'm<00:33:22.640> the<00:33:22.799> hero<00:33:23.360> of<00:33:23.519> this<00:33:23.679> talk<00:33:24.640> i'm<00:33:24.799> the<00:33:24.960> person 00:33:25.269 --> 00:33:25.279 align:start position:0% i'm the hero of this talk i'm the person 00:33:25.279 --> 00:33:25.590 align:start position:0% i'm the hero of this talk i'm the person who's 00:33:25.590 --> 00:33:25.600 align:start position:0% who's 00:33:25.600 --> 00:33:28.149 align:start position:0% who's who's<00:33:25.919> uh<00:33:26.080> distilling<00:33:26.640> all<00:33:26.720> the<00:33:26.880> context<00:33:28.000> uh 00:33:28.149 --> 00:33:28.159 align:start position:0% who's uh distilling all the context uh 00:33:28.159 --> 00:33:28.950 align:start position:0% who's uh distilling all the context uh for<00:33:28.320> you<00:33:28.559> all 00:33:28.950 --> 00:33:28.960 align:start position:0% for you all 00:33:28.960 --> 00:33:31.590 align:start position:0% for you all and<00:33:29.120> i'm<00:33:29.760> certainly<00:33:30.159> joking<00:33:30.960> uh<00:33:31.200> there<00:33:31.360> is<00:33:31.440> no 00:33:31.590 --> 00:33:31.600 align:start position:0% and i'm certainly joking uh there is no 00:33:31.600 --> 00:33:32.710 align:start position:0% and i'm certainly joking uh there is no such<00:33:31.840> person 00:33:32.710 --> 00:33:32.720 align:start position:0% such person 00:33:32.720 --> 00:33:34.389 align:start position:0% such person but<00:33:32.960> there<00:33:33.120> is<00:33:33.279> room<00:33:33.440> for<00:33:33.600> such<00:33:33.840> a<00:33:33.919> person<00:33:34.240> to 00:33:34.389 --> 00:33:34.399 align:start position:0% but there is room for such a person to 00:33:34.399 --> 00:33:36.389 align:start position:0% but there is room for such a person to pretend<00:33:34.799> to<00:33:34.880> be<00:33:35.600> such<00:33:35.840> a<00:33:35.919> person<00:33:36.159> which<00:33:36.320> is 00:33:36.389 --> 00:33:36.399 align:start position:0% pretend to be such a person which is 00:33:36.399 --> 00:33:39.830 align:start position:0% pretend to be such a person which is what<00:33:36.559> i'm<00:33:36.640> doing<00:33:36.880> now 00:33:39.830 --> 00:33:39.840 align:start position:0% what i'm doing now 00:33:39.840 --> 00:33:42.950 align:start position:0% what i'm doing now um<00:33:41.120> well<00:33:41.279> this<00:33:41.440> slide<00:33:41.760> is<00:33:41.840> mangled 00:33:42.950 --> 00:33:42.960 align:start position:0% um well this slide is mangled 00:33:42.960 --> 00:33:44.950 align:start position:0% um well this slide is mangled so<00:33:43.279> a<00:33:43.360> little<00:33:43.600> light<00:33:43.840> criticism<00:33:44.399> of<00:33:44.559> closure 00:33:44.950 --> 00:33:44.960 align:start position:0% so a little light criticism of closure 00:33:44.960 --> 00:33:46.149 align:start position:0% so a little light criticism of closure is<00:33:45.039> in<00:33:45.200> order 00:33:46.149 --> 00:33:46.159 align:start position:0% is in order 00:33:46.159 --> 00:33:49.430 align:start position:0% is in order uh<00:33:46.399> i<00:33:46.640> still<00:33:46.799> use<00:33:47.039> in<00:33:47.200> love<00:33:47.360> closure<00:33:49.039> but<00:33:49.279> one 00:33:49.430 --> 00:33:49.440 align:start position:0% uh i still use in love closure but one 00:33:49.440 --> 00:33:50.789 align:start position:0% uh i still use in love closure but one of<00:33:49.519> the<00:33:49.600> things<00:33:49.840> in<00:33:49.919> the<00:33:50.000> rationale 00:33:50.789 --> 00:33:50.799 align:start position:0% of the things in the rationale 00:33:50.799 --> 00:33:53.509 align:start position:0% of the things in the rationale is<00:33:51.440> emphasis<00:33:51.919> on<00:33:52.000> functional<00:33:52.399> programming 00:33:53.509 --> 00:33:53.519 align:start position:0% is emphasis on functional programming 00:33:53.519 --> 00:33:54.630 align:start position:0% is emphasis on functional programming which 00:33:54.630 --> 00:33:54.640 align:start position:0% which 00:33:54.640 --> 00:33:56.789 align:start position:0% which i<00:33:54.799> think<00:33:55.440> anyone<00:33:55.760> here<00:33:55.919> would<00:33:56.159> agree<00:33:56.480> is<00:33:56.640> a 00:33:56.789 --> 00:33:56.799 align:start position:0% i think anyone here would agree is a 00:33:56.799 --> 00:33:58.149 align:start position:0% i think anyone here would agree is a good<00:33:57.039> thing 00:33:58.149 --> 00:33:58.159 align:start position:0% good thing 00:33:58.159 --> 00:34:00.710 align:start position:0% good thing but<00:33:59.200> there<00:33:59.440> is<00:33:59.519> no<00:33:59.679> free<00:33:59.840> lunch<00:34:00.399> you<00:34:00.559> know 00:34:00.710 --> 00:34:00.720 align:start position:0% but there is no free lunch you know 00:34:00.720 --> 00:34:02.470 align:start position:0% but there is no free lunch you know every<00:34:01.039> every<00:34:01.360> design<00:34:01.679> decision<00:34:02.080> comes<00:34:02.320> with<00:34:02.399> a 00:34:02.470 --> 00:34:02.480 align:start position:0% every every design decision comes with a 00:34:02.480 --> 00:34:03.990 align:start position:0% every every design decision comes with a set<00:34:02.640> of<00:34:02.799> trade-offs 00:34:03.990 --> 00:34:04.000 align:start position:0% set of trade-offs 00:34:04.000 --> 00:34:07.830 align:start position:0% set of trade-offs and<00:34:04.960> um<00:34:05.919> in<00:34:06.000> one<00:34:06.240> interview<00:34:06.559> rich<00:34:06.960> described 00:34:07.830 --> 00:34:07.840 align:start position:0% and um in one interview rich described 00:34:07.840 --> 00:34:10.950 align:start position:0% and um in one interview rich described closure<00:34:08.320> as<00:34:09.599> uh<00:34:10.079> a<00:34:10.159> programming<00:34:10.560> language 00:34:10.950 --> 00:34:10.960 align:start position:0% closure as uh a programming language 00:34:10.960 --> 00:34:12.230 align:start position:0% closure as uh a programming language that<00:34:11.119> inhabits<00:34:11.599> a<00:34:11.679> place 00:34:12.230 --> 00:34:12.240 align:start position:0% that inhabits a place 00:34:12.240 --> 00:34:14.069 align:start position:0% that inhabits a place in<00:34:12.320> the<00:34:12.480> set<00:34:12.720> of<00:34:12.800> possible<00:34:13.280> designs<00:34:13.760> that<00:34:13.919> he 00:34:14.069 --> 00:34:14.079 align:start position:0% in the set of possible designs that he 00:34:14.079 --> 00:34:16.230 align:start position:0% in the set of possible designs that he really<00:34:14.320> likes<00:34:14.560> and<00:34:14.720> wants<00:34:14.960> to<00:34:15.040> be<00:34:15.200> in 00:34:16.230 --> 00:34:16.240 align:start position:0% really likes and wants to be in 00:34:16.240 --> 00:34:18.950 align:start position:0% really likes and wants to be in so<00:34:16.720> it's<00:34:16.879> a<00:34:16.960> multi-dimensional<00:34:17.760> space<00:34:18.800> he 00:34:18.950 --> 00:34:18.960 align:start position:0% so it's a multi-dimensional space he 00:34:18.960 --> 00:34:19.750 align:start position:0% so it's a multi-dimensional space he made<00:34:19.119> a<00:34:19.200> few<00:34:19.359> design 00:34:19.750 --> 00:34:19.760 align:start position:0% made a few design 00:34:19.760 --> 00:34:21.270 align:start position:0% made a few design decisions<00:34:20.159> that<00:34:20.320> took<00:34:20.560> him<00:34:20.639> to<00:34:20.800> a<00:34:20.960> particular 00:34:21.270 --> 00:34:21.280 align:start position:0% decisions that took him to a particular 00:34:21.280 --> 00:34:23.109 align:start position:0% decisions that took him to a particular place<00:34:21.520> that<00:34:21.679> he<00:34:21.760> likes<00:34:22.079> but 00:34:23.109 --> 00:34:23.119 align:start position:0% place that he likes but 00:34:23.119 --> 00:34:26.149 align:start position:0% place that he likes but um<00:34:24.560> maybe<00:34:25.119> it's<00:34:25.280> not<00:34:25.440> the<00:34:25.520> best<00:34:25.760> place<00:34:26.000> for 00:34:26.149 --> 00:34:26.159 align:start position:0% um maybe it's not the best place for 00:34:26.159 --> 00:34:28.149 align:start position:0% um maybe it's not the best place for other<00:34:26.320> people<00:34:26.560> to<00:34:26.639> be<00:34:26.800> in 00:34:28.149 --> 00:34:28.159 align:start position:0% other people to be in 00:34:28.159 --> 00:34:31.270 align:start position:0% other people to be in so<00:34:29.040> one<00:34:29.280> of<00:34:29.359> the<00:34:29.839> tenets<00:34:30.159> of<00:34:30.240> closure<00:34:30.560> is 00:34:31.270 --> 00:34:31.280 align:start position:0% so one of the tenets of closure is 00:34:31.280 --> 00:34:33.430 align:start position:0% so one of the tenets of closure is functional<00:34:31.679> programming<00:34:32.399> and<00:34:32.720> as<00:34:32.960> the<00:34:33.040> basis 00:34:33.430 --> 00:34:33.440 align:start position:0% functional programming and as the basis 00:34:33.440 --> 00:34:35.030 align:start position:0% functional programming and as the basis for<00:34:33.599> that<00:34:33.919> closure<00:34:34.320> has<00:34:34.480> a<00:34:34.639> really 00:34:35.030 --> 00:34:35.040 align:start position:0% for that closure has a really 00:34:35.040 --> 00:34:38.069 align:start position:0% for that closure has a really comprehensive<00:34:36.000> sense<00:34:36.320> of<00:34:36.879> equality 00:34:38.069 --> 00:34:38.079 align:start position:0% comprehensive sense of equality 00:34:38.079 --> 00:34:41.030 align:start position:0% comprehensive sense of equality general<00:34:38.480> generalized<00:34:39.040> equality<00:34:40.480> but<00:34:40.639> that<00:34:40.879> in 00:34:41.030 --> 00:34:41.040 align:start position:0% general generalized equality but that in 00:34:41.040 --> 00:34:42.149 align:start position:0% general generalized equality but that in itself<00:34:41.359> is<00:34:41.520> a<00:34:41.599> trade-off 00:34:42.149 --> 00:34:42.159 align:start position:0% itself is a trade-off 00:34:42.159 --> 00:34:44.869 align:start position:0% itself is a trade-off because<00:34:43.280> arbitrary<00:34:43.919> comparison<00:34:44.560> between 00:34:44.869 --> 00:34:44.879 align:start position:0% because arbitrary comparison between 00:34:44.879 --> 00:34:47.430 align:start position:0% because arbitrary comparison between arbitrary<00:34:45.599> pieces<00:34:46.000> of<00:34:46.079> memory 00:34:47.430 --> 00:34:47.440 align:start position:0% arbitrary pieces of memory 00:34:47.440 --> 00:34:50.710 align:start position:0% arbitrary pieces of memory requires<00:34:48.480> some<00:34:48.639> heuristics<00:34:49.200> to<00:34:49.280> be<00:34:49.440> applied 00:34:50.710 --> 00:34:50.720 align:start position:0% requires some heuristics to be applied 00:34:50.720 --> 00:34:53.750 align:start position:0% requires some heuristics to be applied because<00:34:51.040> there<00:34:51.280> is<00:34:51.440> no<00:34:52.800> universal 00:34:53.750 --> 00:34:53.760 align:start position:0% because there is no universal 00:34:53.760 --> 00:34:56.310 align:start position:0% because there is no universal mathematically<00:34:54.560> sound<00:34:54.879> definition<00:34:55.520> of<00:34:56.079> what 00:34:56.310 --> 00:34:56.320 align:start position:0% mathematically sound definition of what 00:34:56.320 --> 00:34:57.589 align:start position:0% mathematically sound definition of what something<00:34:56.720> is 00:34:57.589 --> 00:34:57.599 align:start position:0% something is 00:34:57.599 --> 00:35:00.230 align:start position:0% something is so<00:34:57.920> whoever's<00:34:58.400> designing<00:34:58.880> that<00:34:59.200> has<00:34:59.440> to<00:35:00.079> make 00:35:00.230 --> 00:35:00.240 align:start position:0% so whoever's designing that has to make 00:35:00.240 --> 00:35:02.390 align:start position:0% so whoever's designing that has to make some<00:35:00.839> cuts 00:35:02.390 --> 00:35:02.400 align:start position:0% some cuts 00:35:02.400 --> 00:35:06.870 align:start position:0% some cuts um<00:35:03.599> and<00:35:03.920> yeah<00:35:04.480> sorry<00:35:05.359> i<00:35:05.599> skipped<00:35:05.920> to<00:35:06.000> the 00:35:06.870 --> 00:35:06.880 align:start position:0% um and yeah sorry i skipped to the 00:35:06.880 --> 00:35:09.270 align:start position:0% um and yeah sorry i skipped to the fourth<00:35:07.200> bullet<00:35:07.920> but<00:35:08.079> with<00:35:08.480> regard<00:35:08.800> to<00:35:08.880> the 00:35:09.270 --> 00:35:09.280 align:start position:0% fourth bullet but with regard to the 00:35:09.280 --> 00:35:10.550 align:start position:0% fourth bullet but with regard to the first<00:35:09.680> bullet 00:35:10.550 --> 00:35:10.560 align:start position:0% first bullet 00:35:10.560 --> 00:35:13.750 align:start position:0% first bullet um<00:35:11.280> when<00:35:11.440> i<00:35:11.599> was<00:35:11.920> originally<00:35:12.480> in<00:35:13.200> use<00:35:13.440> closure 00:35:13.750 --> 00:35:13.760 align:start position:0% um when i was originally in use closure 00:35:13.760 --> 00:35:15.270 align:start position:0% um when i was originally in use closure the<00:35:13.920> concept<00:35:14.320> of<00:35:14.400> everything<00:35:14.720> as<00:35:14.880> data<00:35:15.119> was 00:35:15.270 --> 00:35:15.280 align:start position:0% the concept of everything as data was 00:35:15.280 --> 00:35:16.790 align:start position:0% the concept of everything as data was very<00:35:15.599> refreshing 00:35:16.790 --> 00:35:16.800 align:start position:0% very refreshing 00:35:16.800 --> 00:35:20.470 align:start position:0% very refreshing because<00:35:17.119> i<00:35:17.280> was<00:35:17.520> used<00:35:17.760> to<00:35:18.240> needing<00:35:18.560> to<00:35:19.119> write 00:35:20.470 --> 00:35:20.480 align:start position:0% because i was used to needing to write 00:35:20.480 --> 00:35:24.710 align:start position:0% because i was used to needing to write really<00:35:20.960> obtuse<00:35:21.520> java<00:35:21.920> programs 00:35:24.710 --> 00:35:24.720 align:start position:0% 00:35:24.720 --> 00:35:27.750 align:start position:0% and<00:35:26.560> the<00:35:26.720> other<00:35:26.960> end<00:35:27.119> of<00:35:27.280> it 00:35:27.750 --> 00:35:27.760 align:start position:0% and the other end of it 00:35:27.760 --> 00:35:28.950 align:start position:0% and the other end of it the<00:35:27.920> idea<00:35:28.160> that<00:35:28.240> you<00:35:28.320> could<00:35:28.480> describe<00:35:28.720> things 00:35:28.950 --> 00:35:28.960 align:start position:0% the idea that you could describe things 00:35:28.960 --> 00:35:30.790 align:start position:0% the idea that you could describe things as<00:35:29.040> data<00:35:29.280> was<00:35:29.440> really<00:35:29.680> empowering 00:35:30.790 --> 00:35:30.800 align:start position:0% as data was really empowering 00:35:30.800 --> 00:35:34.390 align:start position:0% as data was really empowering but<00:35:31.040> as<00:35:31.200> i<00:35:33.359> doubled<00:35:33.599> down<00:35:33.839> on<00:35:33.920> that<00:35:34.079> approach 00:35:34.390 --> 00:35:34.400 align:start position:0% but as i doubled down on that approach 00:35:34.400 --> 00:35:35.750 align:start position:0% but as i doubled down on that approach and<00:35:34.480> continued<00:35:34.880> in<00:35:34.960> my<00:35:35.119> career<00:35:35.359> i<00:35:35.440> realized 00:35:35.750 --> 00:35:35.760 align:start position:0% and continued in my career i realized 00:35:35.760 --> 00:35:37.270 align:start position:0% and continued in my career i realized well<00:35:35.920> if<00:35:36.079> even<00:35:36.320> if<00:35:36.400> you<00:35:36.480> put<00:35:36.640> data<00:35:36.960> together 00:35:37.270 --> 00:35:37.280 align:start position:0% well if even if you put data together 00:35:37.280 --> 00:35:37.829 align:start position:0% well if even if you put data together you<00:35:37.440> still 00:35:37.829 --> 00:35:37.839 align:start position:0% you still 00:35:37.839 --> 00:35:41.430 align:start position:0% you still have<00:35:38.000> to<00:35:38.160> interpret<00:35:38.560> it<00:35:38.640> somehow<00:35:39.839> and 00:35:41.430 --> 00:35:41.440 align:start position:0% have to interpret it somehow and 00:35:41.440 --> 00:35:44.950 align:start position:0% have to interpret it somehow and you're<00:35:41.599> going<00:35:41.680> to<00:35:41.760> need<00:35:42.000> code<00:35:42.560> to<00:35:42.720> do<00:35:42.880> that<00:35:43.839> and 00:35:44.950 --> 00:35:44.960 align:start position:0% you're going to need code to do that and 00:35:44.960 --> 00:35:46.710 align:start position:0% you're going to need code to do that and sometimes<00:35:45.440> the<00:35:45.760> kind<00:35:45.920> of<00:35:46.079> interpreter<00:35:46.560> you're 00:35:46.710 --> 00:35:46.720 align:start position:0% sometimes the kind of interpreter you're 00:35:46.720 --> 00:35:48.310 align:start position:0% sometimes the kind of interpreter you're going<00:35:46.800> to<00:35:46.880> write<00:35:47.119> looks<00:35:47.280> suspiciously<00:35:48.000> like<00:35:48.240> a 00:35:48.310 --> 00:35:48.320 align:start position:0% going to write looks suspiciously like a 00:35:48.320 --> 00:35:50.069 align:start position:0% going to write looks suspiciously like a lisp<00:35:48.560> interpreter<00:35:49.200> hiccup 00:35:50.069 --> 00:35:50.079 align:start position:0% lisp interpreter hiccup 00:35:50.079 --> 00:35:52.390 align:start position:0% lisp interpreter hiccup is<00:35:50.240> an<00:35:50.400> example<00:35:50.800> of<00:35:50.880> this<00:35:51.599> it's<00:35:51.760> like<00:35:51.920> huh<00:35:52.240> this 00:35:52.390 --> 00:35:52.400 align:start position:0% is an example of this it's like huh this 00:35:52.400 --> 00:35:54.870 align:start position:0% is an example of this it's like huh this is<00:35:52.560> kind<00:35:52.800> of<00:35:52.960> like<00:35:53.119> a<00:35:53.200> lisp<00:35:53.599> and<00:35:53.680> a<00:35:53.839> lisp 00:35:54.870 --> 00:35:54.880 align:start position:0% is kind of like a lisp and a lisp 00:35:54.880 --> 00:35:56.230 align:start position:0% is kind of like a lisp and a lisp at<00:35:55.040> first<00:35:55.280> i<00:35:55.359> thought<00:35:55.520> it<00:35:55.599> was<00:35:55.680> really<00:35:55.920> cool 00:35:56.230 --> 00:35:56.240 align:start position:0% at first i thought it was really cool 00:35:56.240 --> 00:35:58.069 align:start position:0% at first i thought it was really cool but<00:35:56.400> then<00:35:56.640> as<00:35:56.720> i<00:35:56.880> matured<00:35:57.280> i<00:35:57.359> thought<00:35:57.520> um 00:35:58.069 --> 00:35:58.079 align:start position:0% but then as i matured i thought um 00:35:58.079 --> 00:36:00.550 align:start position:0% but then as i matured i thought um i<00:35:58.160> wonder<00:35:58.480> if<00:35:59.359> this<00:35:59.599> might<00:35:59.760> be<00:35:59.920> going<00:36:00.079> backward 00:36:00.550 --> 00:36:00.560 align:start position:0% i wonder if this might be going backward 00:36:00.560 --> 00:36:01.190 align:start position:0% i wonder if this might be going backward a<00:36:00.640> little<00:36:00.800> bit 00:36:01.190 --> 00:36:01.200 align:start position:0% a little bit 00:36:01.200 --> 00:36:03.829 align:start position:0% a little bit because<00:36:02.079> i've<00:36:02.240> heard<00:36:02.400> it<00:36:02.560> said<00:36:02.800> that<00:36:03.599> you<00:36:03.680> know 00:36:03.829 --> 00:36:03.839 align:start position:0% because i've heard it said that you know 00:36:03.839 --> 00:36:06.870 align:start position:0% because i've heard it said that you know any<00:36:04.079> system<00:36:04.480> evolves<00:36:04.880> into<00:36:05.200> lisp 00:36:06.870 --> 00:36:06.880 align:start position:0% any system evolves into lisp 00:36:06.880 --> 00:36:08.710 align:start position:0% any system evolves into lisp that's<00:36:07.119> greenspun's<00:36:07.760> 10th<00:36:08.079> 10th<00:36:08.400> rule<00:36:08.640> you 00:36:08.710 --> 00:36:08.720 align:start position:0% that's greenspun's 10th 10th rule you 00:36:08.720 --> 00:36:10.230 align:start position:0% that's greenspun's 10th 10th rule you know<00:36:08.880> any<00:36:09.200> any 00:36:10.230 --> 00:36:10.240 align:start position:0% know any any 00:36:10.240 --> 00:36:13.910 align:start position:0% know any any large<00:36:10.560> system<00:36:10.960> is<00:36:11.119> a<00:36:11.920> ad<00:36:12.160> hoc 00:36:13.910 --> 00:36:13.920 align:start position:0% large system is a ad hoc 00:36:13.920 --> 00:36:15.750 align:start position:0% large system is a ad hoc incomplete<00:36:14.480> version<00:36:14.720> of<00:36:14.800> common<00:36:15.119> list<00:36:15.520> and<00:36:15.680> i 00:36:15.750 --> 00:36:15.760 align:start position:0% incomplete version of common list and i 00:36:15.760 --> 00:36:17.829 align:start position:0% incomplete version of common list and i thought<00:36:15.920> i<00:36:16.160> wonder<00:36:16.400> if<00:36:16.880> i'm<00:36:17.040> subject<00:36:17.520> to<00:36:17.680> that 00:36:17.829 --> 00:36:17.839 align:start position:0% thought i wonder if i'm subject to that 00:36:17.839 --> 00:36:19.990 align:start position:0% thought i wonder if i'm subject to that enclosure<00:36:18.320> world 00:36:19.990 --> 00:36:20.000 align:start position:0% enclosure world 00:36:20.000 --> 00:36:22.710 align:start position:0% enclosure world um<00:36:21.280> and<00:36:21.440> yeah<00:36:21.839> i<00:36:21.920> think<00:36:22.079> there's<00:36:22.240> an<00:36:22.320> emphasis 00:36:22.710 --> 00:36:22.720 align:start position:0% um and yeah i think there's an emphasis 00:36:22.720 --> 00:36:24.230 align:start position:0% um and yeah i think there's an emphasis on<00:36:22.880> keywords<00:36:23.280> enclosure<00:36:23.680> as<00:36:23.760> a<00:36:23.839> result<00:36:24.079> like 00:36:24.230 --> 00:36:24.240 align:start position:0% on keywords enclosure as a result like 00:36:24.240 --> 00:36:25.829 align:start position:0% on keywords enclosure as a result like keywords<00:36:24.560> are<00:36:24.640> a<00:36:24.720> really<00:36:24.960> dominant<00:36:25.359> part<00:36:25.680> of 00:36:25.829 --> 00:36:25.839 align:start position:0% keywords are a really dominant part of 00:36:25.839 --> 00:36:27.510 align:start position:0% keywords are a really dominant part of most<00:36:26.160> closure<00:36:26.480> programs 00:36:27.510 --> 00:36:27.520 align:start position:0% most closure programs 00:36:27.520 --> 00:36:29.349 align:start position:0% most closure programs and<00:36:27.839> arguably<00:36:28.320> they<00:36:28.400> form<00:36:28.640> a<00:36:28.720> namespace 00:36:29.349 --> 00:36:29.359 align:start position:0% and arguably they form a namespace 00:36:29.359 --> 00:36:30.630 align:start position:0% and arguably they form a namespace because<00:36:29.599> they're<00:36:29.760> global 00:36:30.630 --> 00:36:30.640 align:start position:0% because they're global 00:36:30.640 --> 00:36:32.390 align:start position:0% because they're global they<00:36:30.800> can<00:36:30.960> have<00:36:31.280> multiple<00:36:31.760> meanings<00:36:32.160> and<00:36:32.240> be 00:36:32.390 --> 00:36:32.400 align:start position:0% they can have multiple meanings and be 00:36:32.400 --> 00:36:34.069 align:start position:0% they can have multiple meanings and be used<00:36:32.800> for<00:36:32.960> multiple<00:36:33.280> different<00:36:33.520> purposes<00:36:34.000> in 00:36:34.069 --> 00:36:34.079 align:start position:0% used for multiple different purposes in 00:36:34.079 --> 00:36:35.510 align:start position:0% used for multiple different purposes in a<00:36:34.240> program 00:36:35.510 --> 00:36:35.520 align:start position:0% a program 00:36:35.520 --> 00:36:38.150 align:start position:0% a program and<00:36:35.680> that's<00:36:35.839> a<00:36:35.920> trade-off<00:36:37.839> same<00:36:38.079> with 00:36:38.150 --> 00:36:38.160 align:start position:0% and that's a trade-off same with 00:36:38.160 --> 00:36:39.270 align:start position:0% and that's a trade-off same with polymorphism 00:36:39.270 --> 00:36:39.280 align:start position:0% polymorphism 00:36:39.280 --> 00:36:41.030 align:start position:0% polymorphism you<00:36:39.440> know<00:36:39.520> closure<00:36:39.920> has<00:36:40.240> several<00:36:40.560> different 00:36:41.030 --> 00:36:41.040 align:start position:0% you know closure has several different 00:36:41.040 --> 00:36:43.190 align:start position:0% you know closure has several different mechanisms<00:36:41.599> for<00:36:41.680> polymorphism 00:36:43.190 --> 00:36:43.200 align:start position:0% mechanisms for polymorphism 00:36:43.200 --> 00:36:48.150 align:start position:0% mechanisms for polymorphism there's<00:36:43.599> protocols<00:36:45.280> multi<00:36:45.680> methods 00:36:48.150 --> 00:36:48.160 align:start position:0% there's protocols multi methods 00:36:48.160 --> 00:36:50.790 align:start position:0% there's protocols multi methods various<00:36:48.480> library<00:36:48.800> contributions<00:36:49.440> like<00:36:49.680> spec 00:36:50.790 --> 00:36:50.800 align:start position:0% various library contributions like spec 00:36:50.800 --> 00:36:51.430 align:start position:0% various library contributions like spec for 00:36:51.430 --> 00:36:51.440 align:start position:0% for 00:36:51.440 --> 00:36:53.109 align:start position:0% for pulling<00:36:51.760> apart<00:36:52.079> dispatching<00:36:52.560> on<00:36:52.720> pieces<00:36:52.960> of 00:36:53.109 --> 00:36:53.119 align:start position:0% pulling apart dispatching on pieces of 00:36:53.119 --> 00:36:55.510 align:start position:0% pulling apart dispatching on pieces of data<00:36:53.440> structurally 00:36:55.510 --> 00:36:55.520 align:start position:0% data structurally 00:36:55.520 --> 00:36:57.030 align:start position:0% data structurally you<00:36:55.599> know<00:36:55.760> each<00:36:55.920> of<00:36:56.000> those<00:36:56.240> is<00:36:56.320> that<00:36:56.640> is<00:36:56.800> code 00:36:57.030 --> 00:36:57.040 align:start position:0% you know each of those is that is code 00:36:57.040 --> 00:36:58.230 align:start position:0% you know each of those is that is code that's<00:36:57.200> going<00:36:57.280> to<00:36:57.359> be<00:36:57.520> on<00:36:57.599> disk<00:36:57.920> and<00:36:58.000> code 00:36:58.230 --> 00:36:58.240 align:start position:0% that's going to be on disk and code 00:36:58.240 --> 00:36:59.109 align:start position:0% that's going to be on disk and code that's<00:36:58.400> going<00:36:58.560> to<00:36:58.640> be 00:36:59.109 --> 00:36:59.119 align:start position:0% that's going to be 00:36:59.119 --> 00:37:02.390 align:start position:0% that's going to be in<00:36:59.280> memory<00:37:00.800> and<00:37:01.040> also<00:37:01.839> the<00:37:02.000> burden<00:37:02.320> of 00:37:02.390 --> 00:37:02.400 align:start position:0% in memory and also the burden of 00:37:02.400 --> 00:37:03.589 align:start position:0% in memory and also the burden of choosing<00:37:02.640> which<00:37:02.800> one<00:37:02.960> to<00:37:03.040> use<00:37:03.280> is<00:37:03.359> on<00:37:03.440> the 00:37:03.589 --> 00:37:03.599 align:start position:0% choosing which one to use is on the 00:37:03.599 --> 00:37:04.710 align:start position:0% choosing which one to use is on the programmer 00:37:04.710 --> 00:37:04.720 align:start position:0% programmer 00:37:04.720 --> 00:37:07.750 align:start position:0% programmer so<00:37:05.440> it's<00:37:05.599> all<00:37:05.760> a<00:37:05.839> set<00:37:06.000> of<00:37:06.079> trade-offs<00:37:07.359> overall 00:37:07.750 --> 00:37:07.760 align:start position:0% so it's all a set of trade-offs overall 00:37:07.760 --> 00:37:08.230 align:start position:0% so it's all a set of trade-offs overall though 00:37:08.230 --> 00:37:08.240 align:start position:0% though 00:37:08.240 --> 00:37:11.349 align:start position:0% though i<00:37:08.320> mean<00:37:08.480> i'm<00:37:08.720> still<00:37:09.040> really<00:37:09.680> grateful<00:37:11.040> for 00:37:11.349 --> 00:37:11.359 align:start position:0% i mean i'm still really grateful for 00:37:11.359 --> 00:37:12.950 align:start position:0% i mean i'm still really grateful for the<00:37:11.520> spot<00:37:11.920> on<00:37:12.000> the<00:37:12.079> design<00:37:12.400> space<00:37:12.800> that 00:37:12.950 --> 00:37:12.960 align:start position:0% the spot on the design space that 00:37:12.960 --> 00:37:14.470 align:start position:0% the spot on the design space that closure<00:37:13.359> inhabits<00:37:13.760> here<00:37:13.920> because<00:37:14.160> it<00:37:14.320> is 00:37:14.470 --> 00:37:14.480 align:start position:0% closure inhabits here because it is 00:37:14.480 --> 00:37:15.349 align:start position:0% closure inhabits here because it is unique 00:37:15.349 --> 00:37:15.359 align:start position:0% unique 00:37:15.359 --> 00:37:17.030 align:start position:0% unique and<00:37:15.440> it<00:37:15.599> is<00:37:15.760> very<00:37:16.000> very<00:37:16.160> powerful<00:37:16.560> like<00:37:16.800> it 00:37:17.030 --> 00:37:17.040 align:start position:0% and it is very very powerful like it 00:37:17.040 --> 00:37:19.030 align:start position:0% and it is very very powerful like it really<00:37:17.599> it's<00:37:17.760> very<00:37:18.000> easy<00:37:18.240> to<00:37:18.320> make 00:37:19.030 --> 00:37:19.040 align:start position:0% really it's very easy to make 00:37:19.040 --> 00:37:21.030 align:start position:0% really it's very easy to make things<00:37:19.359> that<00:37:19.520> are<00:37:19.599> likely<00:37:20.000> to<00:37:20.160> work<00:37:20.800> on<00:37:20.880> the 00:37:21.030 --> 00:37:21.040 align:start position:0% things that are likely to work on the 00:37:21.040 --> 00:37:22.470 align:start position:0% things that are likely to work on the first<00:37:21.280> try 00:37:22.470 --> 00:37:22.480 align:start position:0% first try 00:37:22.480 --> 00:37:25.670 align:start position:0% first try and<00:37:23.359> are<00:37:23.520> just<00:37:24.320> conceptually<00:37:25.200> nice 00:37:25.670 --> 00:37:25.680 align:start position:0% and are just conceptually nice 00:37:25.680 --> 00:37:28.790 align:start position:0% and are just conceptually nice it<00:37:25.839> feels<00:37:26.160> nice<00:37:26.800> so<00:37:27.680> um<00:37:28.240> that's<00:37:28.480> it<00:37:28.560> for<00:37:28.720> the 00:37:28.790 --> 00:37:28.800 align:start position:0% it feels nice so um that's it for the 00:37:28.800 --> 00:37:30.790 align:start position:0% it feels nice so um that's it for the light<00:37:28.960> criticism 00:37:30.790 --> 00:37:30.800 align:start position:0% light criticism 00:37:30.800 --> 00:37:33.190 align:start position:0% light criticism uh<00:37:31.520> i<00:37:31.680> can't<00:37:31.839> really<00:37:32.000> crit<00:37:32.480> and<00:37:32.800> the<00:37:32.880> other<00:37:33.119> the 00:37:33.190 --> 00:37:33.200 align:start position:0% uh i can't really crit and the other the 00:37:33.200 --> 00:37:35.030 align:start position:0% uh i can't really crit and the other the other<00:37:33.359> point<00:37:33.599> is<00:37:33.760> i<00:37:33.839> can't<00:37:34.000> really<00:37:34.240> criticize 00:37:35.030 --> 00:37:35.040 align:start position:0% other point is i can't really criticize 00:37:35.040 --> 00:37:36.150 align:start position:0% other point is i can't really criticize the<00:37:35.200> design<00:37:35.520> of<00:37:35.599> closure 00:37:36.150 --> 00:37:36.160 align:start position:0% the design of closure 00:37:36.160 --> 00:37:39.349 align:start position:0% the design of closure because<00:37:37.359> i<00:37:37.599> you<00:37:37.760> know<00:37:38.480> it<00:37:38.640> was<00:37:38.800> made<00:37:39.040> for<00:37:39.200> its 00:37:39.349 --> 00:37:39.359 align:start position:0% because i you know it was made for its 00:37:39.359 --> 00:37:40.150 align:start position:0% because i you know it was made for its time<00:37:39.599> and<00:37:39.760> place 00:37:40.150 --> 00:37:40.160 align:start position:0% time and place 00:37:40.160 --> 00:37:42.310 align:start position:0% time and place and<00:37:40.320> i'm<00:37:40.480> in<00:37:40.560> a<00:37:40.640> different<00:37:40.880> time<00:37:41.040> and<00:37:41.200> place<00:37:42.160> so 00:37:42.310 --> 00:37:42.320 align:start position:0% and i'm in a different time and place so 00:37:42.320 --> 00:37:45.270 align:start position:0% and i'm in a different time and place so it's<00:37:42.480> not<00:37:42.640> fair 00:37:45.270 --> 00:37:45.280 align:start position:0% 00:37:45.280 --> 00:37:48.470 align:start position:0% um<00:37:47.040> so<00:37:47.280> this<00:37:47.440> isn't<00:37:47.599> really<00:37:47.839> criticism's 00:37:48.470 --> 00:37:48.480 align:start position:0% um so this isn't really criticism's 00:37:48.480 --> 00:37:51.109 align:start position:0% um so this isn't really criticism's criticism<00:37:49.040> so<00:37:49.200> much<00:37:49.440> as<00:37:50.320> revisiting<00:37:50.880> some<00:37:51.040> of 00:37:51.109 --> 00:37:51.119 align:start position:0% criticism so much as revisiting some of 00:37:51.119 --> 00:37:52.710 align:start position:0% criticism so much as revisiting some of the<00:37:51.280> points<00:37:51.599> and<00:37:51.680> closures<00:37:52.079> rationale<00:37:52.560> in<00:37:52.640> the 00:37:52.710 --> 00:37:52.720 align:start position:0% the points and closures rationale in the 00:37:52.720 --> 00:37:54.470 align:start position:0% the points and closures rationale in the modern<00:37:53.119> era<00:37:53.440> so<00:37:53.680> pleasure 00:37:54.470 --> 00:37:54.480 align:start position:0% modern era so pleasure 00:37:54.480 --> 00:37:56.390 align:start position:0% modern era so pleasure this<00:37:54.720> the<00:37:55.280> most<00:37:55.440> of<00:37:55.520> the<00:37:55.599> closure<00:37:55.839> rationale 00:37:56.390 --> 00:37:56.400 align:start position:0% this the most of the closure rationale 00:37:56.400 --> 00:37:58.870 align:start position:0% this the most of the closure rationale is<00:37:56.480> i<00:37:56.560> think<00:37:56.720> written<00:37:56.960> 10<00:37:57.200> or<00:37:57.280> 15<00:37:57.599> years<00:37:57.839> ago 00:37:58.870 --> 00:37:58.880 align:start position:0% is i think written 10 or 15 years ago 00:37:58.880 --> 00:38:02.230 align:start position:0% is i think written 10 or 15 years ago and<00:37:59.359> certain<00:37:59.680> truths<00:38:00.160> about<00:38:00.720> the 00:38:02.230 --> 00:38:02.240 align:start position:0% and certain truths about the 00:38:02.240 --> 00:38:03.750 align:start position:0% and certain truths about the computing<00:38:02.640> landscape<00:38:03.119> have<00:38:03.280> changed<00:38:03.520> since 00:38:03.750 --> 00:38:03.760 align:start position:0% computing landscape have changed since 00:38:03.760 --> 00:38:06.630 align:start position:0% computing landscape have changed since then 00:38:06.630 --> 00:38:06.640 align:start position:0% 00:38:06.640 --> 00:38:09.670 align:start position:0% one<00:38:06.880> of<00:38:06.960> them<00:38:07.119> is<00:38:07.280> that 00:38:09.670 --> 00:38:09.680 align:start position:0% 00:38:09.680 --> 00:38:12.790 align:start position:0% docker<00:38:10.480> and<00:38:10.720> the<00:38:10.960> cloud<00:38:11.839> have 00:38:12.790 --> 00:38:12.800 align:start position:0% docker and the cloud have 00:38:12.800 --> 00:38:15.670 align:start position:0% docker and the cloud have put<00:38:14.079> renewed<00:38:14.640> emphasis<00:38:15.119> on<00:38:15.280> operating 00:38:15.670 --> 00:38:15.680 align:start position:0% put renewed emphasis on operating 00:38:15.680 --> 00:38:17.190 align:start position:0% put renewed emphasis on operating systems<00:38:16.160> and<00:38:16.240> i<00:38:16.320> think<00:38:16.560> you<00:38:16.640> see<00:38:16.800> things<00:38:17.040> like 00:38:17.190 --> 00:38:17.200 align:start position:0% systems and i think you see things like 00:38:17.200 --> 00:38:19.109 align:start position:0% systems and i think you see things like alpine<00:38:17.599> linux 00:38:19.109 --> 00:38:19.119 align:start position:0% alpine linux 00:38:19.119 --> 00:38:22.390 align:start position:0% alpine linux and<00:38:19.200> various<00:38:19.599> other<00:38:20.480> custom<00:38:21.440> os 00:38:22.390 --> 00:38:22.400 align:start position:0% and various other custom os 00:38:22.400 --> 00:38:25.270 align:start position:0% and various other custom os abstraction<00:38:22.960> layers<00:38:23.280> for<00:38:23.440> use<00:38:23.839> in<00:38:24.880> cloud 00:38:25.270 --> 00:38:25.280 align:start position:0% abstraction layers for use in cloud 00:38:25.280 --> 00:38:26.470 align:start position:0% abstraction layers for use in cloud environments 00:38:26.470 --> 00:38:26.480 align:start position:0% environments 00:38:26.480 --> 00:38:29.670 align:start position:0% environments um<00:38:28.240> i<00:38:28.320> don't<00:38:28.480> think<00:38:28.640> it's<00:38:28.800> the<00:38:28.960> case<00:38:29.359> that 00:38:29.670 --> 00:38:29.680 align:start position:0% um i don't think it's the case that 00:38:29.680 --> 00:38:32.870 align:start position:0% um i don't think it's the case that vms<00:38:30.640> are<00:38:31.280> the<00:38:31.440> future<00:38:32.000> i<00:38:32.160> but<00:38:32.400> i<00:38:32.480> think 00:38:32.870 --> 00:38:32.880 align:start position:0% vms are the future i but i think 00:38:32.880 --> 00:38:34.790 align:start position:0% vms are the future i but i think technology<00:38:33.839> and<00:38:34.000> approaches<00:38:34.400> that<00:38:34.560> are<00:38:34.640> in 00:38:34.790 --> 00:38:34.800 align:start position:0% technology and approaches that are in 00:38:34.800 --> 00:38:36.550 align:start position:0% technology and approaches that are in vms<00:38:35.200> are<00:38:35.280> proliferating 00:38:36.550 --> 00:38:36.560 align:start position:0% vms are proliferating 00:38:36.560 --> 00:38:41.190 align:start position:0% vms are proliferating into<00:38:36.800> os's<00:38:37.440> and<00:38:37.599> into<00:38:38.000> infrastructure 00:38:41.190 --> 00:38:41.200 align:start position:0% 00:38:41.200 --> 00:38:43.349 align:start position:0% jit<00:38:41.520> is<00:38:41.680> an<00:38:41.839> example<00:38:42.160> of<00:38:42.240> this<00:38:42.480> so<00:38:42.720> you<00:38:42.800> know<00:38:42.960> 15 00:38:43.349 --> 00:38:43.359 align:start position:0% jit is an example of this so you know 15 00:38:43.359 --> 00:38:45.190 align:start position:0% jit is an example of this so you know 15 years<00:38:43.520> ago 00:38:45.190 --> 00:38:45.200 align:start position:0% years ago 00:38:45.200 --> 00:38:48.069 align:start position:0% years ago hot<00:38:45.440> spot<00:38:45.760> was<00:38:46.480> and<00:38:46.640> maybe<00:38:46.960> lua<00:38:47.520> luagit<00:38:47.920> we 00:38:48.069 --> 00:38:48.079 align:start position:0% hot spot was and maybe lua luagit we 00:38:48.079 --> 00:38:49.349 align:start position:0% hot spot was and maybe lua luagit we came<00:38:48.320> a<00:38:48.400> little<00:38:48.560> later<00:38:48.880> but 00:38:49.349 --> 00:38:49.359 align:start position:0% came a little later but 00:38:49.359 --> 00:38:52.470 align:start position:0% came a little later but it<00:38:49.520> was<00:38:49.599> a<00:38:49.680> pretty<00:38:49.920> new<00:38:50.240> idea 00:38:52.470 --> 00:38:52.480 align:start position:0% it was a pretty new idea 00:38:52.480 --> 00:38:56.390 align:start position:0% it was a pretty new idea but<00:38:53.760> the<00:38:54.240> idea<00:38:54.640> of<00:38:54.800> a<00:38:54.960> jit 00:38:56.390 --> 00:38:56.400 align:start position:0% but the idea of a jit 00:38:56.400 --> 00:39:01.109 align:start position:0% but the idea of a jit was<00:38:56.640> more<00:38:56.800> or<00:38:56.960> less<00:38:58.079> proven<00:38:58.640> in<00:38:58.839> 1999<00:38:59.839> at<00:39:00.079> hp 00:39:01.109 --> 00:39:01.119 align:start position:0% was more or less proven in 1999 at hp 00:39:01.119 --> 00:39:04.470 align:start position:0% was more or less proven in 1999 at hp and<00:39:01.280> what<00:39:01.440> they<00:39:01.599> did<00:39:01.760> there<00:39:02.240> is<00:39:02.480> they 00:39:04.470 --> 00:39:04.480 align:start position:0% and what they did there is they 00:39:04.480 --> 00:39:07.750 align:start position:0% and what they did there is they uh<00:39:05.280> made<00:39:05.520> a<00:39:05.599> jit<00:39:05.839> compiler<00:39:07.359> for 00:39:07.750 --> 00:39:07.760 align:start position:0% uh made a jit compiler for 00:39:07.760 --> 00:39:09.349 align:start position:0% uh made a jit compiler for an<00:39:07.920> architecture<00:39:08.560> i<00:39:08.640> figured<00:39:08.880> what<00:39:08.960> it<00:39:09.040> was<00:39:09.200> it 00:39:09.349 --> 00:39:09.359 align:start position:0% an architecture i figured what it was it 00:39:09.359 --> 00:39:11.190 align:start position:0% an architecture i figured what it was it was<00:39:09.440> like<00:39:09.680> a 00:39:11.190 --> 00:39:11.200 align:start position:0% was like a 00:39:11.200 --> 00:39:15.510 align:start position:0% was like a alpha<00:39:12.160> processor<00:39:12.640> i<00:39:12.839> believe<00:39:14.079> and 00:39:15.510 --> 00:39:15.520 align:start position:0% alpha processor i believe and 00:39:15.520 --> 00:39:17.430 align:start position:0% alpha processor i believe and they<00:39:15.680> wrote<00:39:15.839> a<00:39:15.920> jet<00:39:16.160> for<00:39:16.240> the<00:39:16.320> alpha<00:39:16.640> processor 00:39:17.430 --> 00:39:17.440 align:start position:0% they wrote a jet for the alpha processor 00:39:17.440 --> 00:39:18.870 align:start position:0% they wrote a jet for the alpha processor that<00:39:17.599> compiled<00:39:18.079> into<00:39:18.320> code<00:39:18.640> for 00:39:18.870 --> 00:39:18.880 align:start position:0% that compiled into code for 00:39:18.880 --> 00:39:21.430 align:start position:0% that compiled into code for for<00:39:19.040> a<00:39:19.200> real<00:39:19.440> alpha<00:39:19.760> processor<00:39:20.960> and<00:39:21.119> so<00:39:21.280> they 00:39:21.430 --> 00:39:21.440 align:start position:0% for a real alpha processor and so they 00:39:21.440 --> 00:39:23.270 align:start position:0% for a real alpha processor and so they had<00:39:21.839> a<00:39:22.000> program 00:39:23.270 --> 00:39:23.280 align:start position:0% had a program 00:39:23.280 --> 00:39:25.670 align:start position:0% had a program that<00:39:23.520> emitted<00:39:24.160> alpha<00:39:24.560> processor<00:39:25.280> machine 00:39:25.670 --> 00:39:25.680 align:start position:0% that emitted alpha processor machine 00:39:25.680 --> 00:39:26.310 align:start position:0% that emitted alpha processor machine code 00:39:26.310 --> 00:39:26.320 align:start position:0% code 00:39:26.320 --> 00:39:27.829 align:start position:0% code and<00:39:26.400> then<00:39:26.560> they<00:39:26.720> fed<00:39:26.960> that<00:39:27.119> into<00:39:27.359> their<00:39:27.520> alpha 00:39:27.829 --> 00:39:27.839 align:start position:0% and then they fed that into their alpha 00:39:27.839 --> 00:39:29.670 align:start position:0% and then they fed that into their alpha processor<00:39:28.560> jit 00:39:29.670 --> 00:39:29.680 align:start position:0% processor jit 00:39:29.680 --> 00:39:31.349 align:start position:0% processor jit which<00:39:30.240> emitted<00:39:30.640> code<00:39:30.880> for<00:39:30.960> an<00:39:31.119> alpha 00:39:31.349 --> 00:39:31.359 align:start position:0% which emitted code for an alpha 00:39:31.359 --> 00:39:33.109 align:start position:0% which emitted code for an alpha processor<00:39:32.160> and<00:39:32.320> the<00:39:32.400> code<00:39:32.720> running<00:39:32.960> on<00:39:33.040> the 00:39:33.109 --> 00:39:33.119 align:start position:0% processor and the code running on the 00:39:33.119 --> 00:39:35.190 align:start position:0% processor and the code running on the jit<00:39:33.359> was<00:39:33.520> faster<00:39:33.839> than<00:39:34.000> the<00:39:34.079> machine<00:39:34.400> code 00:39:35.190 --> 00:39:35.200 align:start position:0% jit was faster than the machine code 00:39:35.200 --> 00:39:37.589 align:start position:0% jit was faster than the machine code if<00:39:35.359> you<00:39:35.520> ran<00:39:35.760> it<00:39:35.839> just<00:39:36.000> by<00:39:36.160> itself<00:39:37.119> which<00:39:37.359> made 00:39:37.589 --> 00:39:37.599 align:start position:0% if you ran it just by itself which made 00:39:37.599 --> 00:39:38.230 align:start position:0% if you ran it just by itself which made it<00:39:37.680> clear 00:39:38.230 --> 00:39:38.240 align:start position:0% it clear 00:39:38.240 --> 00:39:41.349 align:start position:0% it clear that<00:39:39.440> jits<00:39:39.760> could<00:39:40.000> be<00:39:40.880> could<00:39:41.040> do 00:39:41.349 --> 00:39:41.359 align:start position:0% that jits could be could do 00:39:41.359 --> 00:39:44.310 align:start position:0% that jits could be could do could<00:39:41.680> add<00:39:42.000> value<00:39:43.200> regardless<00:39:43.839> like<00:39:44.000> even<00:39:44.240> at 00:39:44.310 --> 00:39:44.320 align:start position:0% could add value regardless like even at 00:39:44.320 --> 00:39:45.750 align:start position:0% could add value regardless like even at the<00:39:44.400> machine<00:39:44.640> code<00:39:44.800> level<00:39:45.119> like<00:39:45.280> the<00:39:45.359> concept 00:39:45.750 --> 00:39:45.760 align:start position:0% the machine code level like the concept 00:39:45.760 --> 00:39:47.030 align:start position:0% the machine code level like the concept of<00:39:45.839> tracing 00:39:47.030 --> 00:39:47.040 align:start position:0% of tracing 00:39:47.040 --> 00:39:49.990 align:start position:0% of tracing and<00:39:47.520> hot<00:39:47.839> reloading<00:39:48.400> and<00:39:48.560> stuff<00:39:48.960> or<00:39:49.280> you<00:39:49.359> know 00:39:49.990 --> 00:39:50.000 align:start position:0% and hot reloading and stuff or you know 00:39:50.000 --> 00:39:51.910 align:start position:0% and hot reloading and stuff or you know moving<00:39:50.320> code<00:39:50.640> motion<00:39:51.040> and<00:39:51.119> all<00:39:51.280> that<00:39:51.440> stuff 00:39:51.910 --> 00:39:51.920 align:start position:0% moving code motion and all that stuff 00:39:51.920 --> 00:39:53.030 align:start position:0% moving code motion and all that stuff like<00:39:52.079> there<00:39:52.240> was<00:39:52.320> value<00:39:52.560> there<00:39:52.720> even<00:39:52.960> the 00:39:53.030 --> 00:39:53.040 align:start position:0% like there was value there even the 00:39:53.040 --> 00:39:55.109 align:start position:0% like there was value there even the machine<00:39:53.359> level<00:39:53.680> and 00:39:55.109 --> 00:39:55.119 align:start position:0% machine level and 00:39:55.119 --> 00:39:56.950 align:start position:0% machine level and that<00:39:55.440> kind<00:39:55.599> of<00:39:55.760> smarts<00:39:56.240> is<00:39:56.320> moving<00:39:56.640> further 00:39:56.950 --> 00:39:56.960 align:start position:0% that kind of smarts is moving further 00:39:56.960 --> 00:39:58.950 align:start position:0% that kind of smarts is moving further into<00:39:57.119> the<00:39:57.200> computer<00:39:57.520> as<00:39:57.680> we<00:39:57.839> see<00:39:58.000> with<00:39:58.240> apple's 00:39:58.950 --> 00:39:58.960 align:start position:0% into the computer as we see with apple's 00:39:58.960 --> 00:40:01.510 align:start position:0% into the computer as we see with apple's m1<00:39:59.520> chip<00:40:00.240> that<00:40:00.400> thing<00:40:00.720> is<00:40:00.800> basically<00:40:01.280> like<00:40:01.440> a 00:40:01.510 --> 00:40:01.520 align:start position:0% m1 chip that thing is basically like a 00:40:01.520 --> 00:40:03.910 align:start position:0% m1 chip that thing is basically like a little<00:40:01.680> hotspot<00:40:02.320> on<00:40:02.560> it 00:40:03.910 --> 00:40:03.920 align:start position:0% little hotspot on it 00:40:03.920 --> 00:40:07.109 align:start position:0% little hotspot on it but<00:40:04.079> it<00:40:04.240> has<00:40:04.400> a<00:40:04.480> full<00:40:04.720> view<00:40:04.880> of<00:40:05.040> memory<00:40:05.599> and<00:40:06.480> and 00:40:07.109 --> 00:40:07.119 align:start position:0% but it has a full view of memory and and 00:40:07.119 --> 00:40:10.309 align:start position:0% but it has a full view of memory and and stuff<00:40:07.359> going<00:40:07.520> on<00:40:07.599> in<00:40:07.680> the<00:40:07.760> computer<00:40:10.000> the<00:40:10.160> other 00:40:10.309 --> 00:40:10.319 align:start position:0% stuff going on in the computer the other 00:40:10.319 --> 00:40:11.430 align:start position:0% stuff going on in the computer the other trade-off<00:40:10.640> with<00:40:10.800> jits 00:40:11.430 --> 00:40:11.440 align:start position:0% trade-off with jits 00:40:11.440 --> 00:40:15.109 align:start position:0% trade-off with jits which<00:40:11.680> was<00:40:11.839> true<00:40:12.160> even<00:40:12.480> 15<00:40:12.800> years<00:40:13.040> ago<00:40:14.000> is 00:40:15.109 --> 00:40:15.119 align:start position:0% which was true even 15 years ago is 00:40:15.119 --> 00:40:17.750 align:start position:0% which was true even 15 years ago is they<00:40:15.839> make<00:40:16.000> it<00:40:16.079> harder<00:40:16.400> to<00:40:16.560> reason<00:40:16.960> about<00:40:17.280> the 00:40:17.750 --> 00:40:17.760 align:start position:0% they make it harder to reason about the 00:40:17.760 --> 00:40:18.950 align:start position:0% they make it harder to reason about the performance<00:40:18.319> envelope 00:40:18.950 --> 00:40:18.960 align:start position:0% performance envelope 00:40:18.960 --> 00:40:21.190 align:start position:0% performance envelope of<00:40:19.119> a<00:40:19.200> particular<00:40:19.680> function<00:40:20.079> because 00:40:21.190 --> 00:40:21.200 align:start position:0% of a particular function because 00:40:21.200 --> 00:40:22.470 align:start position:0% of a particular function because something<00:40:21.520> that<00:40:21.680> to<00:40:21.839> you<00:40:22.000> might<00:40:22.240> seem 00:40:22.470 --> 00:40:22.480 align:start position:0% something that to you might seem 00:40:22.480 --> 00:40:23.510 align:start position:0% something that to you might seem intuitively 00:40:23.510 --> 00:40:23.520 align:start position:0% intuitively 00:40:23.520 --> 00:40:27.030 align:start position:0% intuitively fast<00:40:24.800> might<00:40:25.119> actually<00:40:25.599> have<00:40:25.760> a<00:40:25.920> non<00:40:26.400> like<00:40:26.640> a 00:40:27.030 --> 00:40:27.040 align:start position:0% fast might actually have a non like a 00:40:27.040 --> 00:40:28.630 align:start position:0% fast might actually have a non like a non-local<00:40:27.680> effect<00:40:28.000> of<00:40:28.079> making<00:40:28.319> something 00:40:28.630 --> 00:40:28.640 align:start position:0% non-local effect of making something 00:40:28.640 --> 00:40:30.150 align:start position:0% non-local effect of making something else<00:40:28.800> that<00:40:28.960> you<00:40:29.040> thought<00:40:29.200> would<00:40:29.280> be<00:40:29.440> fast<00:40:29.680> slow 00:40:30.150 --> 00:40:30.160 align:start position:0% else that you thought would be fast slow 00:40:30.160 --> 00:40:31.670 align:start position:0% else that you thought would be fast slow because<00:40:30.480> it<00:40:30.560> gets<00:40:30.800> kicked<00:40:31.040> out<00:40:31.119> of<00:40:31.200> cash<00:40:31.520> for 00:40:31.670 --> 00:40:31.680 align:start position:0% because it gets kicked out of cash for 00:40:31.680 --> 00:40:33.910 align:start position:0% because it gets kicked out of cash for example<00:40:32.720> the<00:40:32.880> code<00:40:33.119> trace<00:40:33.359> gets<00:40:33.599> kicked<00:40:33.839> out 00:40:33.910 --> 00:40:33.920 align:start position:0% example the code trace gets kicked out 00:40:33.920 --> 00:40:35.589 align:start position:0% example the code trace gets kicked out of<00:40:34.000> cash<00:40:34.319> because<00:40:34.640> your<00:40:34.880> thing 00:40:35.589 --> 00:40:35.599 align:start position:0% of cash because your thing 00:40:35.599 --> 00:40:38.150 align:start position:0% of cash because your thing now<00:40:35.760> dominates<00:40:36.319> in<00:40:36.400> some<00:40:36.640> way<00:40:36.960> that<00:40:37.680> intrigues 00:40:38.150 --> 00:40:38.160 align:start position:0% now dominates in some way that intrigues 00:40:38.160 --> 00:40:39.670 align:start position:0% now dominates in some way that intrigues the<00:40:38.319> jit 00:40:39.670 --> 00:40:39.680 align:start position:0% the jit 00:40:39.680 --> 00:40:42.790 align:start position:0% the jit so<00:40:40.480> again<00:40:40.800> i<00:40:40.880> think<00:40:41.040> this<00:40:41.200> is<00:40:41.280> something<00:40:41.599> that 00:40:42.790 --> 00:40:42.800 align:start position:0% so again i think this is something that 00:40:42.800 --> 00:40:45.349 align:start position:0% so again i think this is something that is<00:40:43.040> a<00:40:43.200> trade-off<00:40:44.560> for<00:40:44.720> most<00:40:44.880> people<00:40:45.119> using 00:40:45.349 --> 00:40:45.359 align:start position:0% is a trade-off for most people using 00:40:45.359 --> 00:40:47.270 align:start position:0% is a trade-off for most people using java<00:40:45.760> it<00:40:46.000> provides<00:40:46.400> more<00:40:46.640> benefits<00:40:47.040> than 00:40:47.270 --> 00:40:47.280 align:start position:0% java it provides more benefits than 00:40:47.280 --> 00:40:48.309 align:start position:0% java it provides more benefits than problems 00:40:48.309 --> 00:40:48.319 align:start position:0% problems 00:40:48.319 --> 00:40:50.470 align:start position:0% problems but<00:40:48.640> if<00:40:48.720> you're<00:40:48.960> really<00:40:49.200> interested<00:40:49.680> in 00:40:50.470 --> 00:40:50.480 align:start position:0% but if you're really interested in 00:40:50.480 --> 00:40:52.710 align:start position:0% but if you're really interested in reliable<00:40:51.200> performance<00:40:51.760> envelope<00:40:52.319> like<00:40:52.560> you 00:40:52.710 --> 00:40:52.720 align:start position:0% reliable performance envelope like you 00:40:52.720 --> 00:40:53.910 align:start position:0% reliable performance envelope like you really<00:40:52.960> need<00:40:53.119> to<00:40:53.200> make<00:40:53.359> sure<00:40:53.599> that<00:40:53.760> this 00:40:53.910 --> 00:40:53.920 align:start position:0% really need to make sure that this 00:40:53.920 --> 00:40:56.390 align:start position:0% really need to make sure that this function<00:40:54.240> runs<00:40:54.560> the<00:40:54.640> same<00:40:54.880> speed<00:40:55.200> every<00:40:55.440> time 00:40:56.390 --> 00:40:56.400 align:start position:0% function runs the same speed every time 00:40:56.400 --> 00:40:57.750 align:start position:0% function runs the same speed every time and<00:40:56.480> there's<00:40:56.720> various<00:40:57.040> applications<00:40:57.599> that 00:40:57.750 --> 00:40:57.760 align:start position:0% and there's various applications that 00:40:57.760 --> 00:41:00.390 align:start position:0% and there's various applications that need<00:40:58.000> that<00:40:58.319> then 00:41:00.390 --> 00:41:00.400 align:start position:0% need that then 00:41:00.400 --> 00:41:03.510 align:start position:0% need that then java<00:41:00.800> and<00:41:00.880> jits<00:41:02.079> are<00:41:02.240> not<00:41:02.480> necessarily<00:41:03.359> the 00:41:03.510 --> 00:41:03.520 align:start position:0% java and jits are not necessarily the 00:41:03.520 --> 00:41:05.510 align:start position:0% java and jits are not necessarily the right<00:41:03.680> thing<00:41:03.839> for<00:41:03.920> you 00:41:05.510 --> 00:41:05.520 align:start position:0% right thing for you 00:41:05.520 --> 00:41:09.430 align:start position:0% right thing for you um<00:41:06.960> platform<00:41:07.440> on<00:41:07.520> platform<00:41:07.920> issues<00:41:08.319> i<00:41:08.400> think 00:41:09.430 --> 00:41:09.440 align:start position:0% um platform on platform issues i think 00:41:09.440 --> 00:41:11.349 align:start position:0% um platform on platform issues i think this<00:41:09.599> is<00:41:09.760> this<00:41:10.000> is<00:41:10.079> still<00:41:10.319> true<00:41:10.880> which<00:41:11.119> is<00:41:11.280> if 00:41:11.349 --> 00:41:11.359 align:start position:0% this is this is still true which is if 00:41:11.359 --> 00:41:13.030 align:start position:0% this is this is still true which is if you<00:41:11.520> have<00:41:11.839> different<00:41:12.160> platforms<00:41:12.880> with 00:41:13.030 --> 00:41:13.040 align:start position:0% you have different platforms with 00:41:13.040 --> 00:41:14.790 align:start position:0% you have different platforms with different<00:41:13.280> memory<00:41:13.680> models 00:41:14.790 --> 00:41:14.800 align:start position:0% different memory models 00:41:14.800 --> 00:41:16.630 align:start position:0% different memory models uh<00:41:15.040> like<00:41:15.200> for<00:41:15.359> example<00:41:15.760> if<00:41:16.000> on<00:41:16.160> what<00:41:16.400> one 00:41:16.630 --> 00:41:16.640 align:start position:0% uh like for example if on what one 00:41:16.640 --> 00:41:18.470 align:start position:0% uh like for example if on what one platform<00:41:17.040> you<00:41:17.280> have<00:41:17.440> strings<00:41:17.760> are<00:41:17.839> immutable 00:41:18.470 --> 00:41:18.480 align:start position:0% platform you have strings are immutable 00:41:18.480 --> 00:41:19.750 align:start position:0% platform you have strings are immutable and<00:41:18.720> another<00:41:19.040> platform<00:41:19.359> strings<00:41:19.599> are 00:41:19.750 --> 00:41:19.760 align:start position:0% and another platform strings are 00:41:19.760 --> 00:41:22.390 align:start position:0% and another platform strings are immutable<00:41:20.880> or<00:41:21.200> you<00:41:21.280> know<00:41:21.440> there's<00:41:21.680> 32<00:41:22.160> bits 00:41:22.390 --> 00:41:22.400 align:start position:0% immutable or you know there's 32 bits 00:41:22.400 --> 00:41:23.109 align:start position:0% immutable or you know there's 32 bits and<00:41:22.560> a<00:41:22.640> float 00:41:23.109 --> 00:41:23.119 align:start position:0% and a float 00:41:23.119 --> 00:41:26.390 align:start position:0% and a float or<00:41:23.280> there's<00:41:23.920> 32<00:41:24.319> bits<00:41:24.560> in<00:41:24.720> a<00:41:25.200> integer<00:41:25.680> here 00:41:26.390 --> 00:41:26.400 align:start position:0% or there's 32 bits in a integer here 00:41:26.400 --> 00:41:29.750 align:start position:0% or there's 32 bits in a integer here 64<00:41:26.880> bits<00:41:27.119> and<00:41:27.200> an<00:41:27.359> integer<00:41:27.760> here<00:41:28.640> um 00:41:29.750 --> 00:41:29.760 align:start position:0% 64 bits and an integer here um 00:41:29.760 --> 00:41:31.270 align:start position:0% 64 bits and an integer here um you<00:41:29.920> know<00:41:30.240> you<00:41:30.400> can<00:41:30.720> see<00:41:30.960> how<00:41:31.119> that 00:41:31.270 --> 00:41:31.280 align:start position:0% you know you can see how that 00:41:31.280 --> 00:41:33.270 align:start position:0% you know you can see how that complicates 00:41:33.270 --> 00:41:33.280 align:start position:0% complicates 00:41:33.280 --> 00:41:35.349 align:start position:0% complicates fitting<00:41:33.680> one<00:41:33.920> thing<00:41:34.319> to<00:41:34.480> the<00:41:34.640> other<00:41:34.800> thing<00:41:35.040> or 00:41:35.349 --> 00:41:35.359 align:start position:0% fitting one thing to the other thing or 00:41:35.359 --> 00:41:36.790 align:start position:0% fitting one thing to the other thing or setting<00:41:35.760> one<00:41:35.920> thing<00:41:36.160> on<00:41:36.240> top<00:41:36.480> of<00:41:36.560> the<00:41:36.640> other 00:41:36.790 --> 00:41:36.800 align:start position:0% setting one thing on top of the other 00:41:36.800 --> 00:41:37.109 align:start position:0% setting one thing on top of the other thing 00:41:37.109 --> 00:41:37.119 align:start position:0% thing 00:41:37.119 --> 00:41:38.150 align:start position:0% thing you<00:41:37.200> can<00:41:37.440> imagine<00:41:37.839> how<00:41:38.000> there's 00:41:38.150 --> 00:41:38.160 align:start position:0% you can imagine how there's 00:41:38.160 --> 00:41:39.430 align:start position:0% you can imagine how there's inefficiencies<00:41:38.800> that<00:41:38.960> creep<00:41:39.200> in<00:41:39.280> there 00:41:39.430 --> 00:41:39.440 align:start position:0% inefficiencies that creep in there 00:41:39.440 --> 00:41:41.910 align:start position:0% inefficiencies that creep in there because<00:41:39.599> you<00:41:39.760> have<00:41:39.839> to<00:41:39.920> coerce<00:41:40.560> and<00:41:40.720> copy<00:41:41.200> and 00:41:41.910 --> 00:41:41.920 align:start position:0% because you have to coerce and copy and 00:41:41.920 --> 00:41:46.710 align:start position:0% because you have to coerce and copy and do<00:41:42.160> stuff<00:41:42.319> to<00:41:42.400> make<00:41:42.560> it<00:41:42.640> all<00:41:42.800> match<00:41:43.040> up<00:41:43.200> right 00:41:46.710 --> 00:41:46.720 align:start position:0% 00:41:46.720 --> 00:41:49.109 align:start position:0% um<00:41:47.359> which<00:41:47.599> leads<00:41:47.839> me<00:41:48.000> to<00:41:48.079> this<00:41:48.319> key<00:41:48.800> another 00:41:49.109 --> 00:41:49.119 align:start position:0% um which leads me to this key another 00:41:49.119 --> 00:41:51.109 align:start position:0% um which leads me to this key another key<00:41:49.359> contextual<00:41:49.920> difference 00:41:51.109 --> 00:41:51.119 align:start position:0% key contextual difference 00:41:51.119 --> 00:41:53.910 align:start position:0% key contextual difference uh<00:41:51.839> and<00:41:52.079> i<00:41:52.400> i<00:41:52.480> think<00:41:52.720> maybe<00:41:53.119> a<00:41:53.200> better<00:41:53.440> term 00:41:53.910 --> 00:41:53.920 align:start position:0% uh and i i think maybe a better term 00:41:53.920 --> 00:41:55.589 align:start position:0% uh and i i think maybe a better term than<00:41:54.079> context<00:41:54.560> is<00:41:54.640> situation 00:41:55.589 --> 00:41:55.599 align:start position:0% than context is situation 00:41:55.599 --> 00:41:57.750 align:start position:0% than context is situation you<00:41:55.680> know<00:41:55.839> rich<00:41:56.480> talks<00:41:56.800> about<00:41:57.520> the 00:41:57.750 --> 00:41:57.760 align:start position:0% you know rich talks about the 00:41:57.760 --> 00:41:59.349 align:start position:0% you know rich talks about the situational<00:41:58.400> aspect<00:41:58.720> of<00:41:58.880> programming<00:41:59.280> and 00:41:59.349 --> 00:41:59.359 align:start position:0% situational aspect of programming and 00:41:59.359 --> 00:42:00.950 align:start position:0% situational aspect of programming and how<00:41:59.520> nothing<00:41:59.760> really<00:42:00.000> makes<00:42:00.240> sense<00:42:00.560> unless 00:42:00.950 --> 00:42:00.960 align:start position:0% how nothing really makes sense unless 00:42:00.960 --> 00:42:10.790 align:start position:0% how nothing really makes sense unless it's<00:42:01.920> embodied<00:42:02.400> or<00:42:02.560> situated<00:42:03.040> somewhere 00:42:10.790 --> 00:42:10.800 align:start position:0% 00:42:10.800 --> 00:42:13.270 align:start position:0% oh<00:42:11.119> yeah<00:42:11.839> i'm<00:42:12.480> i'm<00:42:12.640> not<00:42:12.800> sure<00:42:12.960> if<00:42:13.040> there's<00:42:13.200> a 00:42:13.270 --> 00:42:13.280 align:start position:0% oh yeah i'm i'm not sure if there's a 00:42:13.280 --> 00:42:14.550 align:start position:0% oh yeah i'm i'm not sure if there's a closure<00:42:13.599> script<00:42:13.839> rationale 00:42:14.550 --> 00:42:14.560 align:start position:0% closure script rationale 00:42:14.560 --> 00:42:16.870 align:start position:0% closure script rationale i<00:42:14.800> actually<00:42:15.119> if<00:42:15.280> you<00:42:15.440> go<00:42:15.680> to<00:42:16.079> the<00:42:16.240> first<00:42:16.480> commit 00:42:16.870 --> 00:42:16.880 align:start position:0% i actually if you go to the first commit 00:42:16.880 --> 00:42:18.230 align:start position:0% i actually if you go to the first commit enclosure<00:42:17.359> script 00:42:18.230 --> 00:42:18.240 align:start position:0% enclosure script 00:42:18.240 --> 00:42:21.030 align:start position:0% enclosure script there's<00:42:18.560> a<00:42:18.960> uh<00:42:19.520> an<00:42:19.680> org<00:42:20.000> file<00:42:20.480> the<00:42:20.640> original 00:42:21.030 --> 00:42:21.040 align:start position:0% there's a uh an org file the original 00:42:21.040 --> 00:42:22.309 align:start position:0% there's a uh an org file the original closure<00:42:21.359> script<00:42:21.680> read<00:42:21.839> me<00:42:22.079> there's<00:42:22.240> a 00:42:22.309 --> 00:42:22.319 align:start position:0% closure script read me there's a 00:42:22.319 --> 00:42:23.910 align:start position:0% closure script read me there's a bulleted<00:42:22.720> list<00:42:23.040> foreclosure<00:42:23.520> script<00:42:23.760> that's 00:42:23.910 --> 00:42:23.920 align:start position:0% bulleted list foreclosure script that's 00:42:23.920 --> 00:42:25.349 align:start position:0% bulleted list foreclosure script that's similar<00:42:24.240> to<00:42:24.319> the<00:42:24.400> one<00:42:24.560> for<00:42:24.720> closure<00:42:25.119> but<00:42:25.280> i 00:42:25.349 --> 00:42:25.359 align:start position:0% similar to the one for closure but i 00:42:25.359 --> 00:42:26.309 align:start position:0% similar to the one for closure but i don't<00:42:25.599> know<00:42:25.760> if<00:42:26.000> it's 00:42:26.309 --> 00:42:26.319 align:start position:0% don't know if it's 00:42:26.319 --> 00:42:27.829 align:start position:0% don't know if it's um<00:42:26.880> i<00:42:27.040> don't<00:42:27.119> know<00:42:27.200> if<00:42:27.280> that's<00:42:27.440> on<00:42:27.520> the<00:42:27.599> closure 00:42:27.829 --> 00:42:27.839 align:start position:0% um i don't know if that's on the closure 00:42:27.839 --> 00:42:32.150 align:start position:0% um i don't know if that's on the closure script<00:42:28.839> website 00:42:32.150 --> 00:42:32.160 align:start position:0% 00:42:32.160 --> 00:42:35.910 align:start position:0% whoops 00:42:35.910 --> 00:42:35.920 align:start position:0% 00:42:35.920 --> 00:42:39.430 align:start position:0% so<00:42:36.560> um<00:42:38.400> right<00:42:38.640> this<00:42:38.880> is<00:42:38.960> this<00:42:39.119> is<00:42:39.200> the<00:42:39.280> big 00:42:39.430 --> 00:42:39.440 align:start position:0% so um right this is this is the big 00:42:39.440 --> 00:42:39.990 align:start position:0% so um right this is this is the big difference 00:42:39.990 --> 00:42:40.000 align:start position:0% difference 00:42:40.000 --> 00:42:42.470 align:start position:0% difference really<00:42:41.040> closure<00:42:41.760> is<00:42:42.000> two<00:42:42.160> things<00:42:42.400> the 00:42:42.470 --> 00:42:42.480 align:start position:0% really closure is two things the 00:42:42.480 --> 00:42:43.670 align:start position:0% really closure is two things the compiler<00:42:42.960> and<00:42:43.040> the<00:42:43.119> runtime 00:42:43.670 --> 00:42:43.680 align:start position:0% compiler and the runtime 00:42:43.680 --> 00:42:46.630 align:start position:0% compiler and the runtime built<00:42:44.000> on<00:42:44.720> a<00:42:44.880> really<00:42:45.359> pretty<00:42:45.599> deep<00:42:45.920> stack<00:42:46.480> of 00:42:46.630 --> 00:42:46.640 align:start position:0% built on a really pretty deep stack of 00:42:46.640 --> 00:42:47.990 align:start position:0% built on a really pretty deep stack of other<00:42:46.880> stuff 00:42:47.990 --> 00:42:48.000 align:start position:0% other stuff 00:42:48.000 --> 00:42:52.309 align:start position:0% other stuff and<00:42:48.880> this<00:42:49.200> was<00:42:49.599> a 00:42:52.309 --> 00:42:52.319 align:start position:0% 00:42:52.319 --> 00:42:54.390 align:start position:0% this<00:42:52.560> is<00:42:52.720> a<00:42:52.880> tactical<00:42:53.359> decision<00:42:53.920> now<00:42:54.160> you<00:42:54.240> can 00:42:54.390 --> 00:42:54.400 align:start position:0% this is a tactical decision now you can 00:42:54.400 --> 00:42:55.910 align:start position:0% this is a tactical decision now you can imagine<00:42:54.720> you're<00:42:54.880> a<00:42:54.960> person<00:42:55.359> you're<00:42:55.520> a<00:42:55.599> single 00:42:55.910 --> 00:42:55.920 align:start position:0% imagine you're a person you're a single 00:42:55.920 --> 00:42:57.510 align:start position:0% imagine you're a person you're a single person<00:42:56.240> you<00:42:56.400> can<00:42:56.480> only<00:42:56.640> be<00:42:56.800> awake<00:42:57.119> for<00:42:57.200> so<00:42:57.359> many 00:42:57.510 --> 00:42:57.520 align:start position:0% person you can only be awake for so many 00:42:57.520 --> 00:42:58.950 align:start position:0% person you can only be awake for so many hours<00:42:57.760> in<00:42:57.839> the<00:42:57.920> day<00:42:58.160> you<00:42:58.240> can<00:42:58.319> only<00:42:58.560> type<00:42:58.800> so 00:42:58.950 --> 00:42:58.960 align:start position:0% hours in the day you can only type so 00:42:58.960 --> 00:43:00.230 align:start position:0% hours in the day you can only type so fast 00:43:00.230 --> 00:43:00.240 align:start position:0% fast 00:43:00.240 --> 00:43:01.430 align:start position:0% fast uh<00:43:00.640> but<00:43:00.800> you<00:43:00.880> want<00:43:01.040> to<00:43:01.119> make<00:43:01.200> a<00:43:01.280> new 00:43:01.430 --> 00:43:01.440 align:start position:0% uh but you want to make a new 00:43:01.440 --> 00:43:02.950 align:start position:0% uh but you want to make a new programming<00:43:01.839> language<00:43:02.480> are<00:43:02.640> you<00:43:02.720> going<00:43:02.880> to 00:43:02.950 --> 00:43:02.960 align:start position:0% programming language are you going to 00:43:02.960 --> 00:43:04.150 align:start position:0% programming language are you going to define 00:43:04.150 --> 00:43:04.160 align:start position:0% define 00:43:04.160 --> 00:43:06.390 align:start position:0% define a<00:43:04.240> new<00:43:04.400> kind<00:43:04.640> of<00:43:04.720> computer<00:43:05.839> and<00:43:06.000> operating 00:43:06.390 --> 00:43:06.400 align:start position:0% a new kind of computer and operating 00:43:06.400 --> 00:43:07.829 align:start position:0% a new kind of computer and operating system<00:43:06.960> to<00:43:07.119> make<00:43:07.280> that<00:43:07.440> happen 00:43:07.829 --> 00:43:07.839 align:start position:0% system to make that happen 00:43:07.839 --> 00:43:09.589 align:start position:0% system to make that happen no<00:43:08.160> you're<00:43:08.319> going<00:43:08.400> to<00:43:08.480> make<00:43:08.640> a<00:43:08.720> dsl<00:43:09.359> you're 00:43:09.589 --> 00:43:09.599 align:start position:0% no you're going to make a dsl you're 00:43:09.599 --> 00:43:12.150 align:start position:0% no you're going to make a dsl you're going<00:43:09.680> to<00:43:09.839> do<00:43:10.000> some<00:43:10.160> prototyping 00:43:12.150 --> 00:43:12.160 align:start position:0% going to do some prototyping 00:43:12.160 --> 00:43:13.750 align:start position:0% going to do some prototyping and<00:43:12.319> rich<00:43:12.560> when<00:43:12.720> he<00:43:12.800> made<00:43:12.960> closure<00:43:13.359> it<00:43:13.440> was<00:43:13.599> all 00:43:13.750 --> 00:43:13.760 align:start position:0% and rich when he made closure it was all 00:43:13.760 --> 00:43:15.349 align:start position:0% and rich when he made closure it was all him<00:43:14.000> you<00:43:14.079> know<00:43:14.240> he<00:43:14.319> had<00:43:14.560> some<00:43:14.720> ideas 00:43:15.349 --> 00:43:15.359 align:start position:0% him you know he had some ideas 00:43:15.359 --> 00:43:17.030 align:start position:0% him you know he had some ideas and<00:43:15.599> he<00:43:15.839> wanted<00:43:16.079> to<00:43:16.160> move<00:43:16.400> as<00:43:16.560> quickly<00:43:16.880> as 00:43:17.030 --> 00:43:17.040 align:start position:0% and he wanted to move as quickly as 00:43:17.040 --> 00:43:19.430 align:start position:0% and he wanted to move as quickly as possible<00:43:17.440> from<00:43:18.240> those<00:43:18.560> ideas<00:43:18.880> to<00:43:19.040> being<00:43:19.280> able 00:43:19.430 --> 00:43:19.440 align:start position:0% possible from those ideas to being able 00:43:19.440 --> 00:43:20.630 align:start position:0% possible from those ideas to being able to<00:43:19.520> use<00:43:19.680> them<00:43:19.839> professionally<00:43:20.480> and 00:43:20.630 --> 00:43:20.640 align:start position:0% to use them professionally and 00:43:20.640 --> 00:43:21.829 align:start position:0% to use them professionally and industrially 00:43:21.829 --> 00:43:21.839 align:start position:0% industrially 00:43:21.839 --> 00:43:23.750 align:start position:0% industrially you<00:43:21.920> know<00:43:22.079> he<00:43:22.160> had<00:43:22.319> the<00:43:22.480> experience<00:43:23.040> with<00:43:23.599> c 00:43:23.750 --> 00:43:23.760 align:start position:0% you know he had the experience with c 00:43:23.760 --> 00:43:26.309 align:start position:0% you know he had the experience with c plus<00:43:24.000> plus<00:43:24.240> and<00:43:24.400> common<00:43:24.720> lisp<00:43:24.960> industrially 00:43:26.309 --> 00:43:26.319 align:start position:0% plus plus and common lisp industrially 00:43:26.319 --> 00:43:27.829 align:start position:0% plus plus and common lisp industrially he<00:43:26.480> wanted<00:43:26.720> to<00:43:26.800> make<00:43:26.960> those<00:43:27.119> things<00:43:27.359> go<00:43:27.680> in<00:43:27.760> a 00:43:27.829 --> 00:43:27.839 align:start position:0% he wanted to make those things go in a 00:43:27.839 --> 00:43:29.349 align:start position:0% he wanted to make those things go in a way<00:43:28.000> that<00:43:28.079> he<00:43:28.160> could<00:43:28.400> sell 00:43:29.349 --> 00:43:29.359 align:start position:0% way that he could sell 00:43:29.359 --> 00:43:30.950 align:start position:0% way that he could sell in<00:43:29.599> a<00:43:29.680> way<00:43:29.839> that<00:43:29.920> he<00:43:30.079> could<00:43:30.240> start<00:43:30.400> using<00:43:30.800> like 00:43:30.950 --> 00:43:30.960 align:start position:0% in a way that he could start using like 00:43:30.960 --> 00:43:32.710 align:start position:0% in a way that he could start using like within<00:43:31.200> his<00:43:31.359> lifetime 00:43:32.710 --> 00:43:32.720 align:start position:0% within his lifetime 00:43:32.720 --> 00:43:35.829 align:start position:0% within his lifetime so<00:43:34.400> the<00:43:34.640> platform<00:43:35.280> aspect 00:43:35.829 --> 00:43:35.839 align:start position:0% so the platform aspect 00:43:35.839 --> 00:43:39.030 align:start position:0% so the platform aspect for<00:43:36.000> him<00:43:37.359> just<00:43:37.599> in<00:43:37.680> terms<00:43:37.920> of<00:43:38.079> his 00:43:39.030 --> 00:43:39.040 align:start position:0% for him just in terms of his 00:43:39.040 --> 00:43:41.670 align:start position:0% for him just in terms of his time<00:43:39.280> available<00:43:39.920> to<00:43:40.079> engineer<00:43:40.560> stuff 00:43:41.670 --> 00:43:41.680 align:start position:0% time available to engineer stuff 00:43:41.680 --> 00:43:43.109 align:start position:0% time available to engineer stuff certainly<00:43:42.079> was<00:43:42.240> really 00:43:43.109 --> 00:43:43.119 align:start position:0% certainly was really 00:43:43.119 --> 00:43:46.550 align:start position:0% certainly was really really<00:43:43.440> uh<00:43:44.160> key<00:43:44.960> um<00:43:45.680> i<00:43:45.839> should<00:43:46.000> say<00:43:46.160> also 00:43:46.550 --> 00:43:46.560 align:start position:0% really uh key um i should say also 00:43:46.560 --> 00:43:48.390 align:start position:0% really uh key um i should say also i<00:43:46.880> i<00:43:47.040> do<00:43:47.200> you<00:43:47.359> know<00:43:47.440> i<00:43:47.680> have<00:43:47.839> worked<00:43:48.079> with<00:43:48.160> rich 00:43:48.390 --> 00:43:48.400 align:start position:0% i i do you know i have worked with rich 00:43:48.400 --> 00:43:49.750 align:start position:0% i i do you know i have worked with rich and<00:43:48.480> i<00:43:48.560> have<00:43:48.640> a<00:43:48.720> personal<00:43:49.040> connection<00:43:49.440> to<00:43:49.599> him 00:43:49.750 --> 00:43:49.760 align:start position:0% and i have a personal connection to him 00:43:49.760 --> 00:43:51.270 align:start position:0% and i have a personal connection to him but<00:43:49.839> i<00:43:49.920> don't<00:43:50.160> speak<00:43:50.400> for<00:43:50.640> him<00:43:50.880> on<00:43:51.040> any<00:43:51.200> of 00:43:51.270 --> 00:43:51.280 align:start position:0% but i don't speak for him on any of 00:43:51.280 --> 00:43:52.150 align:start position:0% but i don't speak for him on any of these<00:43:51.440> things 00:43:52.150 --> 00:43:52.160 align:start position:0% these things 00:43:52.160 --> 00:43:55.190 align:start position:0% these things and<00:43:52.319> i'm<00:43:52.400> going<00:43:52.640> based<00:43:53.359> really<00:43:53.599> only<00:43:53.920> on 00:43:55.190 --> 00:43:55.200 align:start position:0% and i'm going based really only on 00:43:55.200 --> 00:43:57.030 align:start position:0% and i'm going based really only on information<00:43:55.760> that<00:43:56.240> he's<00:43:56.480> made<00:43:56.640> public<00:43:56.960> or 00:43:57.030 --> 00:43:57.040 align:start position:0% information that he's made public or 00:43:57.040 --> 00:43:58.390 align:start position:0% information that he's made public or written<00:43:57.280> about<00:43:57.440> or<00:43:57.599> spoken<00:43:57.920> about 00:43:58.390 --> 00:43:58.400 align:start position:0% written about or spoken about 00:43:58.400 --> 00:44:01.270 align:start position:0% written about or spoken about um<00:43:59.040> but<00:43:59.200> which<00:44:00.240> with<00:44:00.480> which<00:44:00.720> he<00:44:00.880> may<00:44:01.040> now 00:44:01.270 --> 00:44:01.280 align:start position:0% um but which with which he may now 00:44:01.280 --> 00:44:01.910 align:start position:0% um but which with which he may now disagree 00:44:01.910 --> 00:44:01.920 align:start position:0% disagree 00:44:01.920 --> 00:44:05.030 align:start position:0% disagree so<00:44:02.319> again<00:44:02.720> i<00:44:02.800> don't<00:44:03.760> i<00:44:04.000> am<00:44:04.079> not<00:44:04.240> rich<00:44:04.480> hickey 00:44:05.030 --> 00:44:05.040 align:start position:0% so again i don't i am not rich hickey 00:44:05.040 --> 00:44:07.109 align:start position:0% so again i don't i am not rich hickey i<00:44:05.280> don't<00:44:05.520> speak<00:44:05.760> for<00:44:06.000> him<00:44:06.319> but<00:44:06.640> this<00:44:06.880> is<00:44:06.960> my 00:44:07.109 --> 00:44:07.119 align:start position:0% i don't speak for him but this is my 00:44:07.119 --> 00:44:08.309 align:start position:0% i don't speak for him but this is my assessment<00:44:07.920> of 00:44:08.309 --> 00:44:08.319 align:start position:0% assessment of 00:44:08.319 --> 00:44:10.870 align:start position:0% assessment of maybe<00:44:08.720> why<00:44:08.960> he<00:44:09.599> made<00:44:09.760> these<00:44:09.920> decisions 00:44:10.870 --> 00:44:10.880 align:start position:0% maybe why he made these decisions 00:44:10.880 --> 00:44:11.990 align:start position:0% maybe why he made these decisions reading<00:44:11.119> reading<00:44:11.359> between<00:44:11.599> the<00:44:11.680> lines<00:44:11.920> a 00:44:11.990 --> 00:44:12.000 align:start position:0% reading reading between the lines a 00:44:12.000 --> 00:44:13.190 align:start position:0% reading reading between the lines a little<00:44:12.079> bit 00:44:13.190 --> 00:44:13.200 align:start position:0% little bit 00:44:13.200 --> 00:44:16.710 align:start position:0% little bit common<00:44:13.440> list<00:44:13.680> on<00:44:13.760> the<00:44:13.839> other<00:44:14.000> hand<00:44:16.079> much<00:44:16.400> much 00:44:16.710 --> 00:44:16.720 align:start position:0% common list on the other hand much much 00:44:16.720 --> 00:44:18.790 align:start position:0% common list on the other hand much much much<00:44:17.040> broader<00:44:17.680> set 00:44:18.790 --> 00:44:18.800 align:start position:0% much broader set 00:44:18.800 --> 00:44:21.910 align:start position:0% much broader set of<00:44:19.520> desired<00:44:20.000> capabilities 00:44:21.910 --> 00:44:21.920 align:start position:0% of desired capabilities 00:44:21.920 --> 00:44:24.470 align:start position:0% of desired capabilities i<00:44:22.160> have<00:44:22.400> operating<00:44:22.960> system<00:44:23.839> at<00:44:24.000> the<00:44:24.079> bottom<00:44:24.400> of 00:44:24.470 --> 00:44:24.480 align:start position:0% i have operating system at the bottom of 00:44:24.480 --> 00:44:25.910 align:start position:0% i have operating system at the bottom of the<00:44:24.560> stack<00:44:24.960> there 00:44:25.910 --> 00:44:25.920 align:start position:0% the stack there 00:44:25.920 --> 00:44:28.790 align:start position:0% the stack there but<00:44:26.560> even<00:44:26.800> the<00:44:26.960> earliest<00:44:27.520> lisps<00:44:27.920> were<00:44:28.560> really 00:44:28.790 --> 00:44:28.800 align:start position:0% but even the earliest lisps were really 00:44:28.800 --> 00:44:30.150 align:start position:0% but even the earliest lisps were really tightly<00:44:29.200> integrated<00:44:29.520> with<00:44:29.680> the<00:44:29.760> operating 00:44:30.150 --> 00:44:30.160 align:start position:0% tightly integrated with the operating 00:44:30.160 --> 00:44:34.069 align:start position:0% tightly integrated with the operating system 00:44:34.069 --> 00:44:34.079 align:start position:0% 00:44:34.079 --> 00:44:35.750 align:start position:0% and<00:44:34.480> the<00:44:34.640> operating<00:44:35.040> system<00:44:35.280> was<00:44:35.440> in<00:44:35.520> some 00:44:35.750 --> 00:44:35.760 align:start position:0% and the operating system was in some 00:44:35.760 --> 00:44:38.230 align:start position:0% and the operating system was in some cases<00:44:36.560> written<00:44:36.960> almost<00:44:37.280> entirely 00:44:38.230 --> 00:44:38.240 align:start position:0% cases written almost entirely 00:44:38.240 --> 00:44:40.870 align:start position:0% cases written almost entirely in<00:44:38.800> lisp<00:44:39.359> so<00:44:39.599> even<00:44:39.839> that<00:44:40.000> boundary<00:44:40.560> is<00:44:40.640> not 00:44:40.870 --> 00:44:40.880 align:start position:0% in lisp so even that boundary is not 00:44:40.880 --> 00:44:42.550 align:start position:0% in lisp so even that boundary is not really 00:44:42.550 --> 00:44:42.560 align:start position:0% really 00:44:42.560 --> 00:44:45.750 align:start position:0% really very<00:44:43.119> uh 00:44:45.750 --> 00:44:45.760 align:start position:0% 00:44:45.760 --> 00:44:49.670 align:start position:0% easy<00:44:46.160> you<00:44:46.319> know<00:44:46.720> or<00:44:47.119> obvious<00:44:48.000> uh 00:44:49.670 --> 00:44:49.680 align:start position:0% easy you know or obvious uh 00:44:49.680 --> 00:44:54.069 align:start position:0% easy you know or obvious uh lisp<00:44:50.160> the<00:44:50.319> idea<00:44:51.280> you<00:44:51.359> can<00:44:51.520> use<00:44:51.760> to<00:44:51.920> describe 00:44:54.069 --> 00:44:54.079 align:start position:0% lisp the idea you can use to describe 00:44:54.079 --> 00:44:57.910 align:start position:0% lisp the idea you can use to describe a<00:44:54.160> whole<00:44:54.400> computer<00:44:55.359> um<00:44:56.000> and<00:44:56.240> where<00:44:56.480> you<00:44:56.720> want 00:44:57.910 --> 00:44:57.920 align:start position:0% a whole computer um and where you want 00:44:57.920 --> 00:44:59.589 align:start position:0% a whole computer um and where you want the<00:44:58.079> fun<00:44:58.560> the<00:44:58.720> foundational<00:44:59.200> stuff<00:44:59.440> of<00:44:59.520> the 00:44:59.589 --> 00:44:59.599 align:start position:0% the fun the foundational stuff of the 00:44:59.599 --> 00:45:00.950 align:start position:0% the fun the foundational stuff of the computer<00:44:59.920> to<00:45:00.160> end<00:45:00.480> and<00:45:00.640> list 00:45:00.950 --> 00:45:00.960 align:start position:0% computer to end and list 00:45:00.960 --> 00:45:03.270 align:start position:0% computer to end and list to<00:45:01.119> begin<00:45:01.520> is<00:45:01.680> kind<00:45:01.839> of<00:45:02.000> a<00:45:02.240> design<00:45:02.880> design 00:45:03.270 --> 00:45:03.280 align:start position:0% to begin is kind of a design design 00:45:03.280 --> 00:45:04.870 align:start position:0% to begin is kind of a design design decision 00:45:04.870 --> 00:45:04.880 align:start position:0% decision 00:45:04.880 --> 00:45:07.109 align:start position:0% decision but<00:45:05.040> commonlist<00:45:05.680> was<00:45:05.920> not<00:45:06.160> architected<00:45:06.960> to 00:45:07.109 --> 00:45:07.119 align:start position:0% but commonlist was not architected to 00:45:07.119 --> 00:45:08.390 align:start position:0% but commonlist was not architected to take<00:45:07.359> on<00:45:07.440> the<00:45:07.599> problems<00:45:07.839> of<00:45:08.000> the<00:45:08.079> operating 00:45:08.390 --> 00:45:08.400 align:start position:0% take on the problems of the operating 00:45:08.400 --> 00:45:10.390 align:start position:0% take on the problems of the operating system<00:45:08.880> so 00:45:10.390 --> 00:45:10.400 align:start position:0% system so 00:45:10.400 --> 00:45:12.230 align:start position:0% system so some<00:45:10.560> things<00:45:10.800> are<00:45:10.960> absent<00:45:11.280> from<00:45:11.440> the<00:45:11.599> spec<00:45:12.079> and 00:45:12.230 --> 00:45:12.240 align:start position:0% some things are absent from the spec and 00:45:12.240 --> 00:45:13.589 align:start position:0% some things are absent from the spec and are<00:45:12.400> provided<00:45:12.800> by<00:45:12.960> third<00:45:13.200> parties<00:45:13.520> or 00:45:13.589 --> 00:45:13.599 align:start position:0% are provided by third parties or 00:45:13.599 --> 00:45:14.630 align:start position:0% are provided by third parties or implementations<00:45:14.240> now 00:45:14.630 --> 00:45:14.640 align:start position:0% implementations now 00:45:14.640 --> 00:45:18.550 align:start position:0% implementations now threads<00:45:15.040> is<00:45:15.119> one<00:45:15.280> of<00:45:15.440> those<00:45:17.200> c<00:45:17.520> interop 00:45:18.550 --> 00:45:18.560 align:start position:0% threads is one of those c interop 00:45:18.560 --> 00:45:22.470 align:start position:0% threads is one of those c interop cffi<00:45:19.359> is<00:45:19.520> another<00:45:19.760> one<00:45:19.920> that's<00:45:20.400> uh<00:45:20.640> platform 00:45:22.470 --> 00:45:22.480 align:start position:0% cffi is another one that's uh platform 00:45:22.480 --> 00:45:25.430 align:start position:0% cffi is another one that's uh platform uh<00:45:22.800> dependent<00:45:23.839> but<00:45:24.480> you<00:45:24.640> know<00:45:24.720> it's<00:45:24.880> been<00:45:25.200> 20 00:45:25.430 --> 00:45:25.440 align:start position:0% uh dependent but you know it's been 20 00:45:25.440 --> 00:45:26.230 align:start position:0% uh dependent but you know it's been 20 years 00:45:26.230 --> 00:45:26.240 align:start position:0% years 00:45:26.240 --> 00:45:28.550 align:start position:0% years so<00:45:26.560> i'll<00:45:27.119> even<00:45:27.520> a<00:45:27.599> lot<00:45:27.760> of<00:45:27.839> these<00:45:28.079> platform 00:45:28.550 --> 00:45:28.560 align:start position:0% so i'll even a lot of these platform 00:45:28.560 --> 00:45:29.589 align:start position:0% so i'll even a lot of these platform dependent<00:45:29.040> things 00:45:29.589 --> 00:45:29.599 align:start position:0% dependent things 00:45:29.599 --> 00:45:31.349 align:start position:0% dependent things have<00:45:29.920> converged<00:45:30.480> on<00:45:30.720> something<00:45:31.040> like<00:45:31.200> a 00:45:31.349 --> 00:45:31.359 align:start position:0% have converged on something like a 00:45:31.359 --> 00:45:33.910 align:start position:0% have converged on something like a standard<00:45:32.000> that<00:45:32.160> works<00:45:32.480> across<00:45:32.800> platforms 00:45:33.910 --> 00:45:33.920 align:start position:0% standard that works across platforms 00:45:33.920 --> 00:45:35.589 align:start position:0% standard that works across platforms like<00:45:34.079> the<00:45:34.240> thread<00:45:34.560> standard<00:45:34.960> board<00:45:35.359> there's<00:45:35.520> a 00:45:35.589 --> 00:45:35.599 align:start position:0% like the thread standard board there's a 00:45:35.599 --> 00:45:37.589 align:start position:0% like the thread standard board there's a library<00:45:36.000> called<00:45:36.160> bordeaux<00:45:36.560> threads 00:45:37.589 --> 00:45:37.599 align:start position:0% library called bordeaux threads 00:45:37.599 --> 00:45:39.510 align:start position:0% library called bordeaux threads but<00:45:38.160> nowadays<00:45:38.640> most<00:45:38.880> implementations 00:45:39.510 --> 00:45:39.520 align:start position:0% but nowadays most implementations 00:45:39.520 --> 00:45:40.870 align:start position:0% but nowadays most implementations provide<00:45:39.839> their<00:45:40.000> own<00:45:40.079> native<00:45:40.400> version<00:45:40.800> and 00:45:40.870 --> 00:45:40.880 align:start position:0% provide their own native version and 00:45:40.880 --> 00:45:41.430 align:start position:0% provide their own native version and they<00:45:41.040> all 00:45:41.430 --> 00:45:41.440 align:start position:0% they all 00:45:41.440 --> 00:45:43.829 align:start position:0% they all interoperate<00:45:42.400> and<00:45:42.640> people<00:45:43.200> in<00:45:43.280> the<00:45:43.440> community 00:45:43.829 --> 00:45:43.839 align:start position:0% interoperate and people in the community 00:45:43.839 --> 00:45:45.430 align:start position:0% interoperate and people in the community take<00:45:44.079> interoperation<00:45:44.800> between 00:45:45.430 --> 00:45:45.440 align:start position:0% take interoperation between 00:45:45.440 --> 00:45:46.630 align:start position:0% take interoperation between different<00:45:45.760> implementations<00:45:46.480> pretty 00:45:46.630 --> 00:45:46.640 align:start position:0% different implementations pretty 00:45:46.640 --> 00:45:50.470 align:start position:0% different implementations pretty seriously<00:45:48.079> um 00:45:50.470 --> 00:45:50.480 align:start position:0% 00:45:50.480 --> 00:45:52.630 align:start position:0% so<00:45:51.440> yeah<00:45:51.680> it's<00:45:51.839> a<00:45:51.920> different<00:45:52.160> thing<00:45:52.480> it's 00:45:52.630 --> 00:45:52.640 align:start position:0% so yeah it's a different thing it's 00:45:52.640 --> 00:45:53.829 align:start position:0% so yeah it's a different thing it's apples<00:45:52.880> and<00:45:53.040> oranges<00:45:53.359> really 00:45:53.829 --> 00:45:53.839 align:start position:0% apples and oranges really 00:45:53.839 --> 00:45:56.150 align:start position:0% apples and oranges really uh<00:45:54.640> going<00:45:54.880> back<00:45:55.040> to<00:45:55.119> my<00:45:55.280> second<00:45:55.520> slide<00:45:55.839> about 00:45:56.150 --> 00:45:56.160 align:start position:0% uh going back to my second slide about 00:45:56.160 --> 00:45:57.510 align:start position:0% uh going back to my second slide about you<00:45:56.319> know<00:45:56.720> is<00:45:56.880> it 00:45:57.510 --> 00:45:57.520 align:start position:0% you know is it 00:45:57.520 --> 00:45:58.950 align:start position:0% you know is it is<00:45:57.680> which<00:45:57.839> one<00:45:58.079> is<00:45:58.160> better<00:45:58.480> and<00:45:58.560> it's<00:45:58.720> like 00:45:58.950 --> 00:45:58.960 align:start position:0% is which one is better and it's like 00:45:58.960 --> 00:46:05.109 align:start position:0% is which one is better and it's like they<00:45:59.119> really<00:45:59.359> are<00:45:59.520> different<00:46:00.160> significantly 00:46:05.109 --> 00:46:05.119 align:start position:0% 00:46:05.119 --> 00:46:07.589 align:start position:0% um<00:46:05.760> so<00:46:06.000> we<00:46:06.160> have<00:46:06.400> all<00:46:06.560> these<00:46:06.720> abstractions<00:46:07.440> in 00:46:07.589 --> 00:46:07.599 align:start position:0% um so we have all these abstractions in 00:46:07.599 --> 00:46:08.550 align:start position:0% um so we have all these abstractions in play 00:46:08.550 --> 00:46:08.560 align:start position:0% play 00:46:08.560 --> 00:46:11.829 align:start position:0% play and<00:46:09.680> they<00:46:09.839> exist<00:46:10.240> at<00:46:10.319> different<00:46:10.800> levels 00:46:11.829 --> 00:46:11.839 align:start position:0% and they exist at different levels 00:46:11.839 --> 00:46:15.829 align:start position:0% and they exist at different levels in<00:46:12.000> our<00:46:12.839> tower 00:46:15.829 --> 00:46:15.839 align:start position:0% in our tower 00:46:15.839 --> 00:46:17.109 align:start position:0% in our tower and<00:46:16.000> we<00:46:16.160> have<00:46:16.240> to<00:46:16.400> choose<00:46:16.560> which<00:46:16.800> ones<00:46:17.040> to 00:46:17.109 --> 00:46:17.119 align:start position:0% and we have to choose which ones to 00:46:17.119 --> 00:46:18.870 align:start position:0% and we have to choose which ones to build<00:46:17.440> on<00:46:17.680> and<00:46:17.760> how<00:46:17.920> to<00:46:18.079> integrate<00:46:18.480> them<00:46:18.800> and 00:46:18.870 --> 00:46:18.880 align:start position:0% build on and how to integrate them and 00:46:18.880 --> 00:46:20.309 align:start position:0% build on and how to integrate them and then<00:46:19.040> this<00:46:19.280> is<00:46:19.359> the<00:46:19.599> this<00:46:19.760> is<00:46:19.839> the<00:46:20.000> work<00:46:20.240> of 00:46:20.309 --> 00:46:20.319 align:start position:0% then this is the this is the work of 00:46:20.319 --> 00:46:20.790 align:start position:0% then this is the this is the work of design 00:46:20.790 --> 00:46:20.800 align:start position:0% design 00:46:20.800 --> 00:46:21.910 align:start position:0% design this<00:46:20.960> is<00:46:21.040> what<00:46:21.200> anybody<00:46:21.520> who<00:46:21.680> makes<00:46:21.839> a 00:46:21.910 --> 00:46:21.920 align:start position:0% this is what anybody who makes a 00:46:21.920 --> 00:46:24.309 align:start position:0% this is what anybody who makes a language<00:46:22.240> has<00:46:22.400> to<00:46:22.560> do 00:46:24.309 --> 00:46:24.319 align:start position:0% language has to do 00:46:24.319 --> 00:46:26.309 align:start position:0% language has to do closure<00:46:24.720> has<00:46:24.960> a<00:46:25.040> set<00:46:25.520> embodies<00:46:25.920> a<00:46:26.000> set<00:46:26.240> of 00:46:26.309 --> 00:46:26.319 align:start position:0% closure has a set embodies a set of 00:46:26.319 --> 00:46:28.550 align:start position:0% closure has a set embodies a set of perspectives<00:46:26.880> on<00:46:27.040> how<00:46:27.200> to<00:46:27.280> do<00:46:27.440> this 00:46:28.550 --> 00:46:28.560 align:start position:0% perspectives on how to do this 00:46:28.560 --> 00:46:32.069 align:start position:0% perspectives on how to do this that<00:46:29.359> it<00:46:29.520> delivers<00:46:30.960> as<00:46:31.200> a<00:46:31.280> set<00:46:31.440> of<00:46:31.520> features 00:46:32.069 --> 00:46:32.079 align:start position:0% that it delivers as a set of features 00:46:32.079 --> 00:46:34.390 align:start position:0% that it delivers as a set of features or<00:46:32.319> you<00:46:32.480> know<00:46:32.640> forms<00:46:33.119> and<00:46:33.599> runtime<00:46:34.079> objects 00:46:34.390 --> 00:46:34.400 align:start position:0% or you know forms and runtime objects 00:46:34.400 --> 00:46:39.910 align:start position:0% or you know forms and runtime objects that<00:46:34.480> we<00:46:34.640> have<00:46:34.800> access<00:46:35.119> to 00:46:39.910 --> 00:46:39.920 align:start position:0% 00:46:39.920 --> 00:46:42.870 align:start position:0% oh<00:46:40.880> and<00:46:41.119> you<00:46:41.200> could<00:46:41.359> say<00:46:41.599> and<00:46:42.000> this<00:46:42.160> is<00:46:42.319> on<00:46:42.560> this 00:46:42.870 --> 00:46:42.880 align:start position:0% oh and you could say and this is on this 00:46:42.880 --> 00:46:44.470 align:start position:0% oh and you could say and this is on this fourth<00:46:43.119> bullet<00:46:43.520> i<00:46:43.599> kind<00:46:43.760> of<00:46:43.839> roll<00:46:44.079> this<00:46:44.240> up<00:46:44.400> and 00:46:44.470 --> 00:46:44.480 align:start position:0% fourth bullet i kind of roll this up and 00:46:44.480 --> 00:46:45.670 align:start position:0% fourth bullet i kind of roll this up and say 00:46:45.670 --> 00:46:45.680 align:start position:0% say 00:46:45.680 --> 00:46:47.349 align:start position:0% say my<00:46:45.920> own<00:46:46.079> definition<00:46:46.480> of<00:46:46.640> abstraction<00:46:47.200> is 00:46:47.349 --> 00:46:47.359 align:start position:0% my own definition of abstraction is 00:46:47.359 --> 00:46:49.349 align:start position:0% my own definition of abstraction is maybe<00:46:47.680> hiding<00:46:48.079> unnecessary<00:46:48.720> details<00:46:49.200> and 00:46:49.349 --> 00:46:49.359 align:start position:0% maybe hiding unnecessary details and 00:46:49.359 --> 00:46:51.990 align:start position:0% maybe hiding unnecessary details and emphasizing<00:46:49.920> necessary<00:46:50.560> concepts 00:46:51.990 --> 00:46:52.000 align:start position:0% emphasizing necessary concepts 00:46:52.000 --> 00:46:55.670 align:start position:0% emphasizing necessary concepts so<00:46:52.160> this<00:46:52.400> is<00:46:52.560> what<00:46:52.960> makes<00:46:53.280> things<00:46:54.000> simple 00:46:55.670 --> 00:46:55.680 align:start position:0% so this is what makes things simple 00:46:55.680 --> 00:46:57.349 align:start position:0% so this is what makes things simple and<00:46:55.760> then<00:46:56.000> things<00:46:56.160> that<00:46:56.319> are<00:46:56.480> simple<00:46:56.960> can<00:46:57.200> be 00:46:57.349 --> 00:46:57.359 align:start position:0% and then things that are simple can be 00:46:57.359 --> 00:46:58.710 align:start position:0% and then things that are simple can be made<00:46:58.160> easy 00:46:58.710 --> 00:46:58.720 align:start position:0% made easy 00:46:58.720 --> 00:47:02.309 align:start position:0% made easy right<00:47:01.200> but<00:47:01.359> this<00:47:01.599> raises<00:47:01.920> the<00:47:02.000> question<00:47:02.240> like 00:47:02.309 --> 00:47:02.319 align:start position:0% right but this raises the question like 00:47:02.319 --> 00:47:04.069 align:start position:0% right but this raises the question like what<00:47:02.560> is<00:47:02.720> unnecessary<00:47:03.440> how<00:47:03.599> does<00:47:03.760> somebody 00:47:04.069 --> 00:47:04.079 align:start position:0% what is unnecessary how does somebody 00:47:04.079 --> 00:47:07.750 align:start position:0% what is unnecessary how does somebody else<00:47:04.240> know<00:47:04.480> what's<00:47:04.640> necessary<00:47:05.119> to<00:47:05.200> me<00:47:05.359> or<00:47:05.520> not 00:47:07.750 --> 00:47:07.760 align:start position:0% else know what's necessary to me or not 00:47:07.760 --> 00:47:09.430 align:start position:0% else know what's necessary to me or not and<00:47:07.920> that's<00:47:08.079> a<00:47:08.160> good<00:47:08.319> question<00:47:08.720> i<00:47:08.800> think<00:47:09.200> this 00:47:09.430 --> 00:47:09.440 align:start position:0% and that's a good question i think this 00:47:09.440 --> 00:47:11.349 align:start position:0% and that's a good question i think this is<00:47:09.599> back<00:47:09.760> to<00:47:10.079> comes<00:47:10.319> back<00:47:10.480> to<00:47:10.640> alignment 00:47:11.349 --> 00:47:11.359 align:start position:0% is back to comes back to alignment 00:47:11.359 --> 00:47:13.589 align:start position:0% is back to comes back to alignment like<00:47:11.599> are<00:47:11.760> you<00:47:11.920> trying<00:47:12.160> to<00:47:12.240> do<00:47:12.400> the<00:47:12.480> same<00:47:12.800> thing 00:47:13.589 --> 00:47:13.599 align:start position:0% like are you trying to do the same thing 00:47:13.599 --> 00:47:15.109 align:start position:0% like are you trying to do the same thing that<00:47:13.760> the<00:47:13.920> person<00:47:14.160> who<00:47:14.319> made 00:47:15.109 --> 00:47:15.119 align:start position:0% that the person who made 00:47:15.119 --> 00:47:16.870 align:start position:0% that the person who made your<00:47:15.280> language<00:47:15.599> is<00:47:15.680> trying<00:47:15.920> to<00:47:16.079> do<00:47:16.319> if<00:47:16.480> you<00:47:16.640> are 00:47:16.870 --> 00:47:16.880 align:start position:0% your language is trying to do if you are 00:47:16.880 --> 00:47:18.470 align:start position:0% your language is trying to do if you are then<00:47:17.200> you're<00:47:17.359> probably<00:47:17.599> going<00:47:17.760> to 00:47:18.470 --> 00:47:18.480 align:start position:0% then you're probably going to 00:47:18.480 --> 00:47:19.990 align:start position:0% then you're probably going to come<00:47:18.640> to<00:47:18.720> the<00:47:18.800> same<00:47:19.040> conclusions<00:47:19.599> as<00:47:19.680> they<00:47:19.839> did 00:47:19.990 --> 00:47:20.000 align:start position:0% come to the same conclusions as they did 00:47:20.000 --> 00:47:21.430 align:start position:0% come to the same conclusions as they did about<00:47:20.160> what's<00:47:20.319> necessary<00:47:20.720> and<00:47:20.880> unnecessary 00:47:21.430 --> 00:47:21.440 align:start position:0% about what's necessary and unnecessary 00:47:21.440 --> 00:47:22.549 align:start position:0% about what's necessary and unnecessary if<00:47:21.599> you're<00:47:21.760> not<00:47:21.920> then<00:47:22.079> you're<00:47:22.240> going<00:47:22.319> to<00:47:22.400> feel 00:47:22.549 --> 00:47:22.559 align:start position:0% if you're not then you're going to feel 00:47:22.559 --> 00:47:25.430 align:start position:0% if you're not then you're going to feel like<00:47:22.720> this<00:47:22.880> thing<00:47:23.040> is<00:47:23.119> in<00:47:23.200> your<00:47:23.359> way 00:47:25.430 --> 00:47:25.440 align:start position:0% like this thing is in your way 00:47:25.440 --> 00:47:27.910 align:start position:0% like this thing is in your way certainly<00:47:26.559> when<00:47:26.800> rich<00:47:27.040> designed<00:47:27.359> closure<00:47:27.760> he 00:47:27.910 --> 00:47:27.920 align:start position:0% certainly when rich designed closure he 00:47:27.920 --> 00:47:29.670 align:start position:0% certainly when rich designed closure he felt<00:47:28.240> this<00:47:28.400> way<00:47:28.640> about<00:47:28.880> java<00:47:29.200> he<00:47:29.359> thought<00:47:29.599> you 00:47:29.670 --> 00:47:29.680 align:start position:0% felt this way about java he thought you 00:47:29.680 --> 00:47:31.589 align:start position:0% felt this way about java he thought you know<00:47:29.920> this<00:47:30.160> is 00:47:31.589 --> 00:47:31.599 align:start position:0% know this is 00:47:31.599 --> 00:47:34.230 align:start position:0% know this is these<00:47:32.480> the<00:47:32.720> the<00:47:32.880> people<00:47:33.119> who<00:47:33.280> design<00:47:33.520> java 00:47:34.230 --> 00:47:34.240 align:start position:0% these the the people who design java 00:47:34.240 --> 00:47:35.589 align:start position:0% these the the people who design java their<00:47:34.400> priorities<00:47:34.880> are<00:47:34.960> all<00:47:35.119> wrong<00:47:35.359> i<00:47:35.520> don't 00:47:35.589 --> 00:47:35.599 align:start position:0% their priorities are all wrong i don't 00:47:35.599 --> 00:47:37.030 align:start position:0% their priorities are all wrong i don't want<00:47:35.760> to<00:47:35.839> program<00:47:36.160> in<00:47:36.240> this<00:47:36.400> way<00:47:36.640> and<00:47:36.720> i'm<00:47:36.880> at 00:47:37.030 --> 00:47:37.040 align:start position:0% want to program in this way and i'm at 00:47:37.040 --> 00:47:38.470 align:start position:0% want to program in this way and i'm at odds<00:47:37.280> with<00:47:37.440> this<00:47:37.520> way<00:47:37.680> of<00:47:37.760> programming<00:47:38.160> so<00:47:38.319> i'm 00:47:38.470 --> 00:47:38.480 align:start position:0% odds with this way of programming so i'm 00:47:38.480 --> 00:47:40.790 align:start position:0% odds with this way of programming so i'm going<00:47:38.559> to<00:47:38.640> find<00:47:38.800> my<00:47:38.960> own<00:47:39.040> way 00:47:40.790 --> 00:47:40.800 align:start position:0% going to find my own way 00:47:40.800 --> 00:47:42.630 align:start position:0% going to find my own way well<00:47:41.040> enclosure<00:47:41.520> because<00:47:41.760> it<00:47:41.920> inhabits<00:47:42.400> that 00:47:42.630 --> 00:47:42.640 align:start position:0% well enclosure because it inhabits that 00:47:42.640 --> 00:47:44.630 align:start position:0% well enclosure because it inhabits that top<00:47:42.880> part<00:47:43.119> of<00:47:43.200> the<00:47:43.520> platform 00:47:44.630 --> 00:47:44.640 align:start position:0% top part of the platform 00:47:44.640 --> 00:47:47.910 align:start position:0% top part of the platform abstract<00:47:45.359> that<00:47:45.760> the<00:47:45.920> abstraction<00:47:46.880> stack 00:47:47.910 --> 00:47:47.920 align:start position:0% abstract that the abstraction stack 00:47:47.920 --> 00:47:50.549 align:start position:0% abstract that the abstraction stack it's<00:47:48.079> at<00:47:48.160> the<00:47:48.240> very<00:47:48.559> top<00:47:50.079> so<00:47:50.240> a<00:47:50.319> lot<00:47:50.480> of 00:47:50.549 --> 00:47:50.559 align:start position:0% it's at the very top so a lot of 00:47:50.559 --> 00:47:51.990 align:start position:0% it's at the very top so a lot of decisions<00:47:51.119> from<00:47:51.359> top<00:47:51.599> to<00:47:51.680> bottom 00:47:51.990 --> 00:47:52.000 align:start position:0% decisions from top to bottom 00:47:52.000 --> 00:47:54.870 align:start position:0% decisions from top to bottom are<00:47:52.160> already<00:47:52.400> are<00:47:52.480> made<00:47:52.720> for<00:47:52.880> you<00:47:53.040> already<00:47:54.640> but 00:47:54.870 --> 00:47:54.880 align:start position:0% are already are made for you already but 00:47:54.880 --> 00:47:55.750 align:start position:0% are already are made for you already but in<00:47:55.040> common<00:47:55.359> list 00:47:55.750 --> 00:47:55.760 align:start position:0% in common list 00:47:55.760 --> 00:47:58.150 align:start position:0% in common list you<00:47:55.920> have<00:47:56.079> more<00:47:56.319> room<00:47:56.720> to<00:47:56.880> make<00:47:57.839> your<00:47:58.000> own 00:47:58.150 --> 00:47:58.160 align:start position:0% you have more room to make your own 00:47:58.160 --> 00:47:59.670 align:start position:0% you have more room to make your own decisions<00:47:58.720> you<00:47:58.800> have<00:47:58.880> more<00:47:59.119> leverage 00:47:59.670 --> 00:47:59.680 align:start position:0% decisions you have more leverage 00:47:59.680 --> 00:48:02.549 align:start position:0% decisions you have more leverage more<00:47:59.839> rope<00:48:00.160> to<00:48:00.319> hang<00:48:00.480> yourself<00:48:02.079> a<00:48:02.160> lot<00:48:02.319> more 00:48:02.549 --> 00:48:02.559 align:start position:0% more rope to hang yourself a lot more 00:48:02.559 --> 00:48:04.950 align:start position:0% more rope to hang yourself a lot more rope 00:48:04.950 --> 00:48:04.960 align:start position:0% 00:48:04.960 --> 00:48:08.549 align:start position:0% as<00:48:05.200> an<00:48:05.359> example<00:48:05.680> of<00:48:05.760> that<00:48:07.839> commonlist<00:48:08.319> does 00:48:08.549 --> 00:48:08.559 align:start position:0% as an example of that commonlist does 00:48:08.559 --> 00:48:09.589 align:start position:0% as an example of that commonlist does not 00:48:09.589 --> 00:48:09.599 align:start position:0% not 00:48:09.599 --> 00:48:12.710 align:start position:0% not explicitly<00:48:10.160> does<00:48:10.319> not<00:48:10.559> have<00:48:11.119> offer 00:48:12.710 --> 00:48:12.720 align:start position:0% explicitly does not have offer 00:48:12.720 --> 00:48:15.990 align:start position:0% explicitly does not have offer a<00:48:12.880> concept<00:48:13.440> of 00:48:15.990 --> 00:48:16.000 align:start position:0% 00:48:16.000 --> 00:48:20.470 align:start position:0% general<00:48:16.920> equality<00:48:18.839> um 00:48:20.470 --> 00:48:20.480 align:start position:0% general equality um 00:48:20.480 --> 00:48:23.109 align:start position:0% general equality um and<00:48:20.800> that's<00:48:21.119> intentional<00:48:22.000> uh<00:48:22.400> the<00:48:22.720> downside 00:48:23.109 --> 00:48:23.119 align:start position:0% and that's intentional uh the downside 00:48:23.119 --> 00:48:24.390 align:start position:0% and that's intentional uh the downside of<00:48:23.280> it<00:48:23.440> is<00:48:23.520> that<00:48:23.760> there's<00:48:24.000> like 00:48:24.390 --> 00:48:24.400 align:start position:0% of it is that there's like 00:48:24.400 --> 00:48:27.910 align:start position:0% of it is that there's like half<00:48:24.640> a<00:48:24.720> dozen<00:48:25.040> or<00:48:25.119> more<00:48:25.599> equality<00:48:26.480> operators 00:48:27.910 --> 00:48:27.920 align:start position:0% half a dozen or more equality operators 00:48:27.920 --> 00:48:29.910 align:start position:0% half a dozen or more equality operators and<00:48:28.319> they<00:48:28.480> work<00:48:28.720> on<00:48:28.800> all<00:48:28.960> different<00:48:29.119> types<00:48:29.760> so 00:48:29.910 --> 00:48:29.920 align:start position:0% and they work on all different types so 00:48:29.920 --> 00:48:33.190 align:start position:0% and they work on all different types so this<00:48:30.160> is<00:48:30.319> exactly<00:48:30.720> the<00:48:30.880> kind<00:48:31.200> of 00:48:33.190 --> 00:48:33.200 align:start position:0% this is exactly the kind of 00:48:33.200 --> 00:48:36.630 align:start position:0% this is exactly the kind of legacy<00:48:34.720> uh<00:48:35.680> corruption 00:48:36.630 --> 00:48:36.640 align:start position:0% legacy uh corruption 00:48:36.640 --> 00:48:38.710 align:start position:0% legacy uh corruption that<00:48:37.119> people<00:48:37.440> point<00:48:37.680> out<00:48:37.839> when<00:48:38.000> they<00:48:38.160> say 00:48:38.710 --> 00:48:38.720 align:start position:0% that people point out when they say 00:48:38.720 --> 00:48:40.150 align:start position:0% that people point out when they say common<00:48:39.040> list<00:48:39.280> doesn't<00:48:39.520> have<00:48:39.760> unified 00:48:40.150 --> 00:48:40.160 align:start position:0% common list doesn't have unified 00:48:40.160 --> 00:48:41.750 align:start position:0% common list doesn't have unified abstractions<00:48:40.800> like<00:48:41.040> it<00:48:41.119> doesn't<00:48:41.359> even<00:48:41.599> have<00:48:41.680> a 00:48:41.750 --> 00:48:41.760 align:start position:0% abstractions like it doesn't even have a 00:48:41.760 --> 00:48:42.630 align:start position:0% abstractions like it doesn't even have a single<00:48:42.079> equal 00:48:42.630 --> 00:48:42.640 align:start position:0% single equal 00:48:42.640 --> 00:48:46.069 align:start position:0% single equal what's<00:48:42.880> up<00:48:42.960> with<00:48:43.119> that<00:48:43.440> that's<00:48:43.680> crazy<00:48:45.119> um 00:48:46.069 --> 00:48:46.079 align:start position:0% what's up with that that's crazy um 00:48:46.079 --> 00:48:49.750 align:start position:0% what's up with that that's crazy um but<00:48:46.240> there's<00:48:46.400> a<00:48:46.480> reason<00:48:46.720> for<00:48:46.880> it 00:48:49.750 --> 00:48:49.760 align:start position:0% but there's a reason for it 00:48:49.760 --> 00:48:52.950 align:start position:0% but there's a reason for it and<00:48:50.079> that<00:48:50.240> reason<00:48:50.559> is<00:48:50.720> in<00:48:51.680> the 00:48:52.950 --> 00:48:52.960 align:start position:0% and that reason is in the 00:48:52.960 --> 00:48:54.870 align:start position:0% and that reason is in the hyperspec<00:48:54.000> and<00:48:54.240> i<00:48:54.319> think<00:48:54.480> it's<00:48:54.559> one<00:48:54.720> of<00:48:54.800> the 00:48:54.870 --> 00:48:54.880 align:start position:0% hyperspec and i think it's one of the 00:48:54.880 --> 00:48:56.549 align:start position:0% hyperspec and i think it's one of the issues<00:48:55.359> attached<00:48:55.680> to<00:48:55.839> the<00:48:56.000> equal<00:48:56.240> p 00:48:56.549 --> 00:48:56.559 align:start position:0% issues attached to the equal p 00:48:56.559 --> 00:49:00.470 align:start position:0% issues attached to the equal p or<00:48:56.880> equal<00:48:58.640> um 00:49:00.470 --> 00:49:00.480 align:start position:0% or equal um 00:49:00.480 --> 00:49:02.710 align:start position:0% or equal um and<00:49:00.880> this<00:49:01.119> is<00:49:01.359> just<00:49:01.599> philosophically<00:49:02.319> true 00:49:02.710 --> 00:49:02.720 align:start position:0% and this is just philosophically true 00:49:02.720 --> 00:49:04.790 align:start position:0% and this is just philosophically true there<00:49:02.960> isn't<00:49:03.280> a<00:49:03.359> general<00:49:03.760> way<00:49:04.079> of<00:49:04.240> comparing 00:49:04.790 --> 00:49:04.800 align:start position:0% there isn't a general way of comparing 00:49:04.800 --> 00:49:05.510 align:start position:0% there isn't a general way of comparing to 00:49:05.510 --> 00:49:05.520 align:start position:0% to 00:49:05.520 --> 00:49:08.630 align:start position:0% to places<00:49:05.920> in<00:49:06.000> memory<00:49:06.319> for<00:49:06.480> equality<00:49:07.599> um<00:49:08.400> any 00:49:08.630 --> 00:49:08.640 align:start position:0% places in memory for equality um any 00:49:08.640 --> 00:49:10.230 align:start position:0% places in memory for equality um any choice<00:49:08.880> you<00:49:09.040> make<00:49:09.200> about<00:49:09.440> how<00:49:09.599> to<00:49:09.680> do<00:49:09.839> that<00:49:10.079> is 00:49:10.230 --> 00:49:10.240 align:start position:0% choice you make about how to do that is 00:49:10.240 --> 00:49:11.990 align:start position:0% choice you make about how to do that is going<00:49:10.400> to<00:49:10.559> suggest 00:49:11.990 --> 00:49:12.000 align:start position:0% going to suggest 00:49:12.000 --> 00:49:14.390 align:start position:0% going to suggest or<00:49:12.240> imply<00:49:12.640> other<00:49:12.880> constraints<00:49:13.520> on<00:49:13.599> the<00:49:13.760> system 00:49:14.390 --> 00:49:14.400 align:start position:0% or imply other constraints on the system 00:49:14.400 --> 00:49:16.309 align:start position:0% or imply other constraints on the system and<00:49:14.640> so<00:49:14.960> in<00:49:15.040> the<00:49:15.200> interest<00:49:15.520> of<00:49:15.599> making<00:49:15.920> as<00:49:16.079> many 00:49:16.309 --> 00:49:16.319 align:start position:0% and so in the interest of making as many 00:49:16.319 --> 00:49:18.150 align:start position:0% and so in the interest of making as many things<00:49:16.640> possible<00:49:17.119> in<00:49:17.200> common<00:49:17.520> lisp 00:49:18.150 --> 00:49:18.160 align:start position:0% things possible in common lisp 00:49:18.160 --> 00:49:20.710 align:start position:0% things possible in common lisp as<00:49:18.480> they<00:49:18.720> can<00:49:19.520> they<00:49:19.680> decided<00:49:20.000> not<00:49:20.160> to<00:49:20.480> make<00:49:20.640> a 00:49:20.710 --> 00:49:20.720 align:start position:0% as they can they decided not to make a 00:49:20.720 --> 00:49:21.990 align:start position:0% as they can they decided not to make a decision<00:49:21.119> about<00:49:21.359> this 00:49:21.990 --> 00:49:22.000 align:start position:0% decision about this 00:49:22.000 --> 00:49:23.430 align:start position:0% decision about this and<00:49:22.160> what<00:49:22.319> this<00:49:22.480> means<00:49:22.720> is<00:49:22.800> that<00:49:22.960> if<00:49:23.119> you<00:49:23.200> want 00:49:23.430 --> 00:49:23.440 align:start position:0% and what this means is that if you want 00:49:23.440 --> 00:49:25.030 align:start position:0% and what this means is that if you want something<00:49:23.680> like<00:49:23.839> closure<00:49:24.240> style 00:49:25.030 --> 00:49:25.040 align:start position:0% something like closure style 00:49:25.040 --> 00:49:26.870 align:start position:0% something like closure style immutable<00:49:25.760> structures<00:49:26.319> with<00:49:26.559> general 00:49:26.870 --> 00:49:26.880 align:start position:0% immutable structures with general 00:49:26.880 --> 00:49:28.069 align:start position:0% immutable structures with general equality<00:49:27.280> you're<00:49:27.440> going<00:49:27.520> to<00:49:27.599> have<00:49:27.680> to<00:49:27.760> make<00:49:27.920> it 00:49:28.069 --> 00:49:28.079 align:start position:0% equality you're going to have to make it 00:49:28.079 --> 00:49:28.790 align:start position:0% equality you're going to have to make it yourself<00:49:28.480> or 00:49:28.790 --> 00:49:28.800 align:start position:0% yourself or 00:49:28.800 --> 00:49:32.069 align:start position:0% yourself or use<00:49:29.040> library 00:49:32.069 --> 00:49:32.079 align:start position:0% 00:49:32.079 --> 00:49:33.430 align:start position:0% and<00:49:32.160> this<00:49:32.400> goes<00:49:32.559> back<00:49:32.720> to<00:49:32.800> the<00:49:32.960> tension<00:49:33.280> of 00:49:33.430 --> 00:49:33.440 align:start position:0% and this goes back to the tension of 00:49:33.440 --> 00:49:35.109 align:start position:0% and this goes back to the tension of platform<00:49:33.920> versus<00:49:34.240> language<00:49:34.559> on<00:49:34.640> top<00:49:34.880> of<00:49:35.040> a 00:49:35.109 --> 00:49:35.119 align:start position:0% platform versus language on top of a 00:49:35.119 --> 00:49:36.150 align:start position:0% platform versus language on top of a platform<00:49:35.520> this<00:49:35.680> is 00:49:36.150 --> 00:49:36.160 align:start position:0% platform this is 00:49:36.160 --> 00:49:37.990 align:start position:0% platform this is commonlist<00:49:36.720> taking<00:49:36.960> a<00:49:37.040> stand<00:49:37.280> as<00:49:37.359> a<00:49:37.520> platform 00:49:37.990 --> 00:49:38.000 align:start position:0% commonlist taking a stand as a platform 00:49:38.000 --> 00:49:39.750 align:start position:0% commonlist taking a stand as a platform and<00:49:38.079> saying<00:49:38.880> we're<00:49:39.040> not<00:49:39.200> going<00:49:39.280> to<00:49:39.440> approach 00:49:39.750 --> 00:49:39.760 align:start position:0% and saying we're not going to approach 00:49:39.760 --> 00:49:40.630 align:start position:0% and saying we're not going to approach this 00:49:40.630 --> 00:49:40.640 align:start position:0% this 00:49:40.640 --> 00:49:43.589 align:start position:0% this we're<00:49:40.800> going<00:49:40.880> to<00:49:40.960> leave<00:49:41.119> this<00:49:41.280> to<00:49:41.760> the<00:49:41.839> users 00:49:43.589 --> 00:49:43.599 align:start position:0% we're going to leave this to the users 00:49:43.599 --> 00:49:45.190 align:start position:0% we're going to leave this to the users and<00:49:43.839> contrast<00:49:44.240> with<00:49:44.400> closures 00:49:45.190 --> 00:49:45.200 align:start position:0% and contrast with closures 00:49:45.200 --> 00:49:48.309 align:start position:0% and contrast with closures generally<00:49:45.599> quality<00:49:46.079> operator<00:49:46.559> equal 00:49:48.309 --> 00:49:48.319 align:start position:0% generally quality operator equal 00:49:48.319 --> 00:49:49.510 align:start position:0% generally quality operator equal which<00:49:48.480> you<00:49:48.640> can<00:49:48.800> pretty<00:49:49.040> much<00:49:49.280> use 00:49:49.510 --> 00:49:49.520 align:start position:0% which you can pretty much use 00:49:49.520 --> 00:49:52.470 align:start position:0% which you can pretty much use intuitively<00:49:50.079> in<00:49:50.240> any<00:49:50.400> context<00:49:50.960> where<00:49:51.200> you 00:49:52.470 --> 00:49:52.480 align:start position:0% intuitively in any context where you 00:49:52.480 --> 00:49:55.670 align:start position:0% intuitively in any context where you situation<00:49:52.960> demands<00:49:53.280> equality 00:49:55.670 --> 00:49:55.680 align:start position:0% situation demands equality 00:49:55.680 --> 00:49:58.549 align:start position:0% situation demands equality but<00:49:56.880> there<00:49:57.280> are<00:49:57.440> a<00:49:57.440> few<00:49:57.599> costs<00:49:57.920> associated 00:49:58.549 --> 00:49:58.559 align:start position:0% but there are a few costs associated 00:49:58.559 --> 00:50:00.470 align:start position:0% but there are a few costs associated with<00:49:58.800> this<00:49:59.040> convenience 00:50:00.470 --> 00:50:00.480 align:start position:0% with this convenience 00:50:00.480 --> 00:50:03.589 align:start position:0% with this convenience um<00:50:02.960> you<00:50:03.119> need 00:50:03.589 --> 00:50:03.599 align:start position:0% um you need 00:50:03.599 --> 00:50:07.030 align:start position:0% um you need uh<00:50:04.640> the<00:50:04.800> fourth<00:50:05.119> one<00:50:05.280> is<00:50:05.440> maybe<00:50:05.680> the 00:50:07.030 --> 00:50:07.040 align:start position:0% uh the fourth one is maybe the 00:50:07.040 --> 00:50:10.150 align:start position:0% uh the fourth one is maybe the the<00:50:07.200> meatiest<00:50:07.680> one<00:50:08.000> which<00:50:08.240> is<00:50:09.200> um<00:50:09.839> you<00:50:10.000> know 00:50:10.150 --> 00:50:10.160 align:start position:0% the meatiest one which is um you know 00:50:10.160 --> 00:50:12.309 align:start position:0% the meatiest one which is um you know you<00:50:10.319> can<00:50:10.559> extend<00:50:10.960> quality<00:50:11.520> quality<00:50:11.920> to<00:50:12.079> your 00:50:12.309 --> 00:50:12.319 align:start position:0% you can extend quality quality to your 00:50:12.319 --> 00:50:12.710 align:start position:0% you can extend quality quality to your own 00:50:12.710 --> 00:50:12.720 align:start position:0% own 00:50:12.720 --> 00:50:14.309 align:start position:0% own new<00:50:12.960> objects<00:50:13.359> but<00:50:13.520> when<00:50:13.680> you<00:50:13.760> do<00:50:13.920> that<00:50:14.160> you 00:50:14.309 --> 00:50:14.319 align:start position:0% new objects but when you do that you 00:50:14.319 --> 00:50:17.750 align:start position:0% new objects but when you do that you need<00:50:14.480> to<00:50:15.680> mutate<00:50:16.240> the<00:50:16.400> list<00:50:16.800> of 00:50:17.750 --> 00:50:17.760 align:start position:0% need to mutate the list of 00:50:17.760 --> 00:50:20.150 align:start position:0% need to mutate the list of uh<00:50:18.160> equality<00:50:18.880> comparator<00:50:19.440> functions<00:50:19.839> inside 00:50:20.150 --> 00:50:20.160 align:start position:0% uh equality comparator functions inside 00:50:20.160 --> 00:50:21.589 align:start position:0% uh equality comparator functions inside closure<00:50:20.480> itself<00:50:20.960> and<00:50:21.119> that's<00:50:21.280> what<00:50:21.440> you're 00:50:21.589 --> 00:50:21.599 align:start position:0% closure itself and that's what you're 00:50:21.599 --> 00:50:22.710 align:start position:0% closure itself and that's what you're doing<00:50:21.839> that's<00:50:22.000> effectively<00:50:22.480> what<00:50:22.559> you're 00:50:22.710 --> 00:50:22.720 align:start position:0% doing that's effectively what you're 00:50:22.720 --> 00:50:24.069 align:start position:0% doing that's effectively what you're doing<00:50:22.960> when<00:50:23.119> you're 00:50:24.069 --> 00:50:24.079 align:start position:0% doing when you're 00:50:24.079 --> 00:50:26.150 align:start position:0% doing when you're extending<00:50:24.480> an<00:50:24.640> interface<00:50:25.440> in<00:50:25.599> java<00:50:25.920> or<00:50:26.000> if 00:50:26.150 --> 00:50:26.160 align:start position:0% extending an interface in java or if 00:50:26.160 --> 00:50:33.270 align:start position:0% extending an interface in java or if you're<00:50:26.240> extending<00:50:26.559> a<00:50:26.640> protocol<00:50:27.040> enclosure 00:50:33.270 --> 00:50:33.280 align:start position:0% 00:50:33.280 --> 00:50:38.309 align:start position:0% oh<00:50:33.520> yeah<00:50:33.839> uh<00:50:34.000> yeah<00:50:34.240> henry<00:50:34.559> baker<00:50:36.000> yeah 00:50:38.309 --> 00:50:38.319 align:start position:0% oh yeah uh yeah henry baker yeah 00:50:38.319 --> 00:50:41.750 align:start position:0% oh yeah uh yeah henry baker yeah yep<00:50:39.520> um<00:50:41.200> yeah<00:50:41.440> so 00:50:41.750 --> 00:50:41.760 align:start position:0% yep um yeah so 00:50:41.760 --> 00:50:44.790 align:start position:0% yep um yeah so uh<00:50:42.079> in<00:50:42.400> some<00:50:42.559> of<00:50:42.640> his<00:50:42.800> early<00:50:43.040> talks<00:50:43.440> uh 00:50:44.790 --> 00:50:44.800 align:start position:0% uh in some of his early talks uh 00:50:44.800 --> 00:50:47.670 align:start position:0% uh in some of his early talks uh rich<00:50:45.359> references<00:50:45.920> egal<00:50:46.720> and<00:50:46.960> this<00:50:47.200> is<00:50:47.280> henry 00:50:47.670 --> 00:50:47.680 align:start position:0% rich references egal and this is henry 00:50:47.680 --> 00:50:48.630 align:start position:0% rich references egal and this is henry baker's<00:50:48.079> attempt 00:50:48.630 --> 00:50:48.640 align:start position:0% baker's attempt 00:50:48.640 --> 00:50:51.589 align:start position:0% baker's attempt to<00:50:49.520> who's<00:50:50.160> another<00:50:50.400> original<00:50:50.800> mit<00:50:51.200> list 00:50:51.589 --> 00:50:51.599 align:start position:0% to who's another original mit list 00:50:51.599 --> 00:50:52.630 align:start position:0% to who's another original mit list person 00:50:52.630 --> 00:50:52.640 align:start position:0% person 00:50:52.640 --> 00:50:55.910 align:start position:0% person to<00:50:53.359> bring<00:50:53.599> some<00:50:53.760> sanity<00:50:54.240> to<00:50:55.200> common<00:50:55.520> lisps 00:50:55.910 --> 00:50:55.920 align:start position:0% to bring some sanity to common lisps 00:50:55.920 --> 00:50:57.109 align:start position:0% to bring some sanity to common lisps equality 00:50:57.109 --> 00:50:57.119 align:start position:0% equality 00:50:57.119 --> 00:50:59.829 align:start position:0% equality operations<00:50:57.839> because<00:50:58.160> he<00:50:58.400> he<00:50:58.640> also<00:50:59.040> was 00:50:59.829 --> 00:50:59.839 align:start position:0% operations because he he also was 00:50:59.839 --> 00:51:00.870 align:start position:0% operations because he he also was disgusted<00:51:00.400> by<00:51:00.559> the 00:51:00.870 --> 00:51:00.880 align:start position:0% disgusted by the 00:51:00.880 --> 00:51:03.910 align:start position:0% disgusted by the proliferation<00:51:01.599> of<00:51:02.000> equality<00:51:02.559> functions<00:51:03.680> and 00:51:03.910 --> 00:51:03.920 align:start position:0% proliferation of equality functions and 00:51:03.920 --> 00:51:05.349 align:start position:0% proliferation of equality functions and he<00:51:04.079> had<00:51:04.160> an<00:51:04.319> idea<00:51:04.640> about<00:51:04.800> how<00:51:04.960> to<00:51:05.040> make<00:51:05.280> a 00:51:05.349 --> 00:51:05.359 align:start position:0% he had an idea about how to make a 00:51:05.359 --> 00:51:06.470 align:start position:0% he had an idea about how to make a better<00:51:05.599> one<00:51:05.839> or<00:51:06.000> at<00:51:06.000> least<00:51:06.240> a<00:51:06.319> more 00:51:06.470 --> 00:51:06.480 align:start position:0% better one or at least a more 00:51:06.480 --> 00:51:07.589 align:start position:0% better one or at least a more comprehensive<00:51:07.040> one 00:51:07.589 --> 00:51:07.599 align:start position:0% comprehensive one 00:51:07.599 --> 00:51:09.190 align:start position:0% comprehensive one but<00:51:07.760> there<00:51:07.839> are<00:51:07.920> trade-offs<00:51:08.400> associated<00:51:08.880> with 00:51:09.190 --> 00:51:09.200 align:start position:0% but there are trade-offs associated with 00:51:09.200 --> 00:51:13.349 align:start position:0% but there are trade-offs associated with his<00:51:09.359> approach 00:51:13.349 --> 00:51:13.359 align:start position:0% 00:51:13.359 --> 00:51:16.549 align:start position:0% so<00:51:13.520> yeah<00:51:14.000> you<00:51:14.160> know<00:51:15.680> the<00:51:15.839> nice<00:51:16.079> thing<00:51:16.240> about 00:51:16.549 --> 00:51:16.559 align:start position:0% so yeah you know the nice thing about 00:51:16.559 --> 00:51:18.390 align:start position:0% so yeah you know the nice thing about these<00:51:16.720> abstractions<00:51:17.359> is<00:51:17.520> they 00:51:18.390 --> 00:51:18.400 align:start position:0% these abstractions is they 00:51:18.400 --> 00:51:24.630 align:start position:0% these abstractions is they change<00:51:18.800> the<00:51:19.359> economy<00:51:20.559> of<00:51:21.359> using<00:51:21.680> them 00:51:24.630 --> 00:51:24.640 align:start position:0% 00:51:24.640 --> 00:51:26.069 align:start position:0% and<00:51:24.800> it's<00:51:25.040> either<00:51:25.280> to<00:51:25.440> your<00:51:25.520> advantage<00:51:26.000> or 00:51:26.069 --> 00:51:26.079 align:start position:0% and it's either to your advantage or 00:51:26.079 --> 00:51:27.670 align:start position:0% and it's either to your advantage or your<00:51:26.240> detriment<00:51:26.800> depending<00:51:27.200> on 00:51:27.670 --> 00:51:27.680 align:start position:0% your detriment depending on 00:51:27.680 --> 00:51:29.109 align:start position:0% your detriment depending on what<00:51:27.839> you're<00:51:28.000> trying<00:51:28.240> to<00:51:28.319> do<00:51:28.720> and<00:51:28.880> if<00:51:28.960> you're 00:51:29.109 --> 00:51:29.119 align:start position:0% what you're trying to do and if you're 00:51:29.119 --> 00:51:30.790 align:start position:0% what you're trying to do and if you're trying<00:51:29.359> to<00:51:29.520> write 00:51:30.790 --> 00:51:30.800 align:start position:0% trying to write 00:51:30.800 --> 00:51:32.870 align:start position:0% trying to write a<00:51:30.960> hot<00:51:31.280> you<00:51:31.359> know<00:51:31.520> new<00:51:31.760> parrot<00:51:32.000> numeric<00:51:32.640> type 00:51:32.870 --> 00:51:32.880 align:start position:0% a hot you know new parrot numeric type 00:51:32.880 --> 00:51:35.109 align:start position:0% a hot you know new parrot numeric type loop<00:51:33.119> or<00:51:33.280> doing<00:51:33.440> scientific<00:51:33.920> computing 00:51:35.109 --> 00:51:35.119 align:start position:0% loop or doing scientific computing 00:51:35.119 --> 00:51:36.710 align:start position:0% loop or doing scientific computing then<00:51:35.760> and<00:51:35.839> you<00:51:36.000> know<00:51:36.160> you're<00:51:36.319> always<00:51:36.559> going<00:51:36.640> to 00:51:36.710 --> 00:51:36.720 align:start position:0% then and you know you're always going to 00:51:36.720 --> 00:51:38.230 align:start position:0% then and you know you're always going to be<00:51:36.800> working<00:51:37.119> with<00:51:37.280> a<00:51:37.359> particular 00:51:38.230 --> 00:51:38.240 align:start position:0% be working with a particular 00:51:38.240 --> 00:51:41.990 align:start position:0% be working with a particular you<00:51:38.400> know<00:51:38.559> signed<00:51:38.880> integer<00:51:39.359> or<00:51:39.520> whatever<00:51:40.640> then 00:51:41.990 --> 00:51:42.000 align:start position:0% you know signed integer or whatever then 00:51:42.000 --> 00:51:43.910 align:start position:0% you know signed integer or whatever then this<00:51:42.240> may<00:51:42.400> get<00:51:42.559> in<00:51:42.720> your<00:51:42.880> way<00:51:43.359> more<00:51:43.599> than<00:51:43.760> it 00:51:43.910 --> 00:51:43.920 align:start position:0% this may get in your way more than it 00:51:43.920 --> 00:51:45.030 align:start position:0% this may get in your way more than it helps<00:51:44.160> you 00:51:45.030 --> 00:51:45.040 align:start position:0% helps you 00:51:45.040 --> 00:51:48.829 align:start position:0% helps you um<00:51:46.640> maybe<00:51:47.040> i<00:51:47.200> mean<00:51:47.359> again<00:51:47.520> it's<00:51:47.760> it's 00:51:48.829 --> 00:51:48.839 align:start position:0% um maybe i mean again it's it's 00:51:48.839 --> 00:51:50.630 align:start position:0% um maybe i mean again it's it's contextual 00:51:50.630 --> 00:51:50.640 align:start position:0% contextual 00:51:50.640 --> 00:51:53.510 align:start position:0% contextual so<00:51:50.960> if<00:51:51.119> i<00:51:51.200> were<00:51:51.359> to<00:51:51.440> like<00:51:51.680> sum<00:51:51.920> up<00:51:52.800> the 00:51:53.510 --> 00:51:53.520 align:start position:0% so if i were to like sum up the 00:51:53.520 --> 00:51:54.390 align:start position:0% so if i were to like sum up the conceptual 00:51:54.390 --> 00:51:54.400 align:start position:0% conceptual 00:51:54.400 --> 00:51:55.990 align:start position:0% conceptual abstraction<00:51:54.880> differences<00:51:55.280> between<00:51:55.599> closure 00:51:55.990 --> 00:51:56.000 align:start position:0% abstraction differences between closure 00:51:56.000 --> 00:51:57.430 align:start position:0% abstraction differences between closure i<00:51:56.079> would<00:51:56.160> say<00:51:56.559> in<00:51:56.720> common<00:51:56.960> list<00:51:57.119> i<00:51:57.200> think<00:51:57.359> you 00:51:57.430 --> 00:51:57.440 align:start position:0% i would say in common list i think you 00:51:57.440 --> 00:51:58.710 align:start position:0% i would say in common list i think you know<00:51:57.599> closure<00:51:57.920> is<00:51:58.000> like<00:51:58.160> this<00:51:58.319> tightly 00:51:58.710 --> 00:51:58.720 align:start position:0% know closure is like this tightly 00:51:58.720 --> 00:51:59.829 align:start position:0% know closure is like this tightly integrated 00:51:59.829 --> 00:51:59.839 align:start position:0% integrated 00:51:59.839 --> 00:52:01.510 align:start position:0% integrated beautifully<00:52:00.400> designed<00:52:01.040> internally 00:52:01.510 --> 00:52:01.520 align:start position:0% beautifully designed internally 00:52:01.520 --> 00:52:03.030 align:start position:0% beautifully designed internally consistent 00:52:03.030 --> 00:52:03.040 align:start position:0% consistent 00:52:03.040 --> 00:52:05.910 align:start position:0% consistent view<00:52:04.079> of<00:52:04.240> how<00:52:04.400> to<00:52:04.559> program<00:52:05.200> and<00:52:05.359> in<00:52:05.520> particular 00:52:05.910 --> 00:52:05.920 align:start position:0% view of how to program and in particular 00:52:05.920 --> 00:52:07.750 align:start position:0% view of how to program and in particular how<00:52:06.079> to<00:52:06.240> program<00:52:06.559> on<00:52:06.720> a<00:52:06.880> platform<00:52:07.359> like 00:52:07.750 --> 00:52:07.760 align:start position:0% how to program on a platform like 00:52:07.760 --> 00:52:11.990 align:start position:0% how to program on a platform like java<00:52:08.160> or<00:52:08.400> javascript<00:52:10.240> common<00:52:10.559> lisp 00:52:11.990 --> 00:52:12.000 align:start position:0% java or javascript common lisp 00:52:12.000 --> 00:52:14.150 align:start position:0% java or javascript common lisp it<00:52:12.240> evolved<00:52:12.720> over<00:52:12.960> a<00:52:13.040> long<00:52:13.200> period<00:52:13.440> of<00:52:13.599> time<00:52:14.000> it 00:52:14.150 --> 00:52:14.160 align:start position:0% it evolved over a long period of time it 00:52:14.160 --> 00:52:16.630 align:start position:0% it evolved over a long period of time it has<00:52:14.640> amazing<00:52:15.040> ideas<00:52:15.440> in<00:52:15.599> it<00:52:15.760> those<00:52:16.079> ideas<00:52:16.480> are 00:52:16.630 --> 00:52:16.640 align:start position:0% has amazing ideas in it those ideas are 00:52:16.640 --> 00:52:18.390 align:start position:0% has amazing ideas in it those ideas are not<00:52:16.960> especially<00:52:17.680> artfully 00:52:18.390 --> 00:52:18.400 align:start position:0% not especially artfully 00:52:18.400 --> 00:52:22.390 align:start position:0% not especially artfully connected<00:52:20.160> but<00:52:21.040> where<00:52:21.280> their<00:52:21.520> connections 00:52:22.390 --> 00:52:22.400 align:start position:0% connected but where their connections 00:52:22.400 --> 00:52:25.430 align:start position:0% connected but where their connections dissatisfy<00:52:24.079> you<00:52:24.240> can<00:52:24.400> at<00:52:24.480> least<00:52:24.800> go<00:52:24.960> find<00:52:25.200> out 00:52:25.430 --> 00:52:25.440 align:start position:0% dissatisfy you can at least go find out 00:52:25.440 --> 00:52:26.069 align:start position:0% dissatisfy you can at least go find out why 00:52:26.069 --> 00:52:26.079 align:start position:0% why 00:52:26.079 --> 00:52:28.069 align:start position:0% why there's<00:52:26.400> always<00:52:26.640> a<00:52:26.720> place<00:52:27.040> to<00:52:27.119> figure<00:52:27.440> out<00:52:27.680> why 00:52:28.069 --> 00:52:28.079 align:start position:0% there's always a place to figure out why 00:52:28.079 --> 00:52:29.270 align:start position:0% there's always a place to figure out why like<00:52:28.240> what<00:52:28.480> experience 00:52:29.270 --> 00:52:29.280 align:start position:0% like what experience 00:52:29.280 --> 00:52:30.950 align:start position:0% like what experience led<00:52:29.440> to<00:52:29.599> this<00:52:30.079> what<00:52:30.240> was<00:52:30.400> the<00:52:30.480> discussion 00:52:30.950 --> 00:52:30.960 align:start position:0% led to this what was the discussion 00:52:30.960 --> 00:52:33.030 align:start position:0% led to this what was the discussion behind<00:52:31.200> this<00:52:31.440> why<00:52:31.680> is<00:52:31.839> it<00:52:32.000> that<00:52:32.160> way 00:52:33.030 --> 00:52:33.040 align:start position:0% behind this why is it that way 00:52:33.040 --> 00:52:34.470 align:start position:0% behind this why is it that way and<00:52:33.119> so<00:52:33.280> it's<00:52:33.440> a<00:52:33.520> patchwork<00:52:34.079> it's<00:52:34.240> a<00:52:34.319> very 00:52:34.470 --> 00:52:34.480 align:start position:0% and so it's a patchwork it's a very 00:52:34.480 --> 00:52:36.069 align:start position:0% and so it's a patchwork it's a very broad<00:52:34.960> patchwork 00:52:36.069 --> 00:52:36.079 align:start position:0% broad patchwork 00:52:36.079 --> 00:52:39.190 align:start position:0% broad patchwork and<00:52:36.240> so<00:52:37.119> um<00:52:38.319> that<00:52:38.480> makes<00:52:38.720> it<00:52:38.800> feel<00:52:38.960> kind<00:52:39.119> of 00:52:39.190 --> 00:52:39.200 align:start position:0% and so um that makes it feel kind of 00:52:39.200 --> 00:52:39.589 align:start position:0% and so um that makes it feel kind of weird 00:52:39.589 --> 00:52:39.599 align:start position:0% weird 00:52:39.599 --> 00:52:41.190 align:start position:0% weird coming<00:52:39.839> from<00:52:40.000> closure<00:52:40.400> honestly<00:52:40.880> and<00:52:40.960> i<00:52:41.040> think 00:52:41.190 --> 00:52:41.200 align:start position:0% coming from closure honestly and i think 00:52:41.200 --> 00:52:43.750 align:start position:0% coming from closure honestly and i think that's<00:52:41.440> why<00:52:41.680> when<00:52:41.839> i<00:52:42.240> would<00:52:42.400> tell<00:52:42.640> people 00:52:43.750 --> 00:52:43.760 align:start position:0% that's why when i would tell people 00:52:43.760 --> 00:52:45.030 align:start position:0% that's why when i would tell people that<00:52:43.920> i<00:52:44.079> came<00:52:44.240> up<00:52:44.400> with<00:52:44.559> in<00:52:44.640> the<00:52:44.720> closure 00:52:45.030 --> 00:52:45.040 align:start position:0% that i came up with in the closure 00:52:45.040 --> 00:52:46.069 align:start position:0% that i came up with in the closure community<00:52:45.280> i<00:52:45.359> told<00:52:45.520> them<00:52:45.599> about<00:52:45.680> common<00:52:45.920> list 00:52:46.069 --> 00:52:46.079 align:start position:0% community i told them about common list 00:52:46.079 --> 00:52:47.349 align:start position:0% community i told them about common list but<00:52:46.240> i<00:52:46.319> sent<00:52:46.400> them<00:52:46.559> to<00:52:46.640> the<00:52:46.720> hyperspec<00:52:47.280> and 00:52:47.349 --> 00:52:47.359 align:start position:0% but i sent them to the hyperspec and 00:52:47.359 --> 00:52:48.549 align:start position:0% but i sent them to the hyperspec and they<00:52:47.520> see<00:52:47.680> that<00:52:47.920> it<00:52:48.000> looks<00:52:48.160> like<00:52:48.319> you<00:52:48.480> know 00:52:48.549 --> 00:52:48.559 align:start position:0% they see that it looks like you know 00:52:48.559 --> 00:52:50.630 align:start position:0% they see that it looks like you know copyright<00:52:49.040> 1994. 00:52:50.630 --> 00:52:50.640 align:start position:0% copyright 1994. 00:52:50.640 --> 00:52:54.150 align:start position:0% copyright 1994. what<00:52:50.880> is<00:52:51.040> this<00:52:51.839> like<00:52:52.640> why<00:52:52.880> are<00:52:53.040> you 00:52:54.150 --> 00:52:54.160 align:start position:0% what is this like why are you 00:52:54.160 --> 00:52:56.630 align:start position:0% what is this like why are you looking<00:52:54.480> at<00:52:54.640> this<00:52:55.040> and<00:52:55.359> um<00:52:55.760> yeah<00:52:56.000> so<00:52:56.160> it<00:52:56.400> has<00:52:56.559> a 00:52:56.630 --> 00:52:56.640 align:start position:0% looking at this and um yeah so it has a 00:52:56.640 --> 00:52:57.750 align:start position:0% looking at this and um yeah so it has a weird 00:52:57.750 --> 00:52:57.760 align:start position:0% weird 00:52:57.760 --> 00:53:00.790 align:start position:0% weird weird<00:52:58.079> vibe<00:52:58.319> it's<00:52:58.839> old-timey<00:53:00.400> but<00:53:00.640> it's 00:53:00.790 --> 00:53:00.800 align:start position:0% weird vibe it's old-timey but it's 00:53:00.800 --> 00:53:02.150 align:start position:0% weird vibe it's old-timey but it's lovable 00:53:02.150 --> 00:53:02.160 align:start position:0% lovable 00:53:02.160 --> 00:53:06.150 align:start position:0% lovable endearing<00:53:03.119> and<00:53:03.839> again<00:53:04.160> will<00:53:04.319> never<00:53:04.559> change<00:53:05.040> so 00:53:06.150 --> 00:53:06.160 align:start position:0% endearing and again will never change so 00:53:06.160 --> 00:53:08.950 align:start position:0% endearing and again will never change so whatever<00:53:06.480> time<00:53:06.720> you<00:53:06.800> spend<00:53:07.200> learning<00:53:07.520> it<00:53:08.720> it's 00:53:08.950 --> 00:53:08.960 align:start position:0% whatever time you spend learning it it's 00:53:08.960 --> 00:53:10.309 align:start position:0% whatever time you spend learning it it's going<00:53:09.040> to<00:53:09.119> pay<00:53:09.200> a<00:53:09.280> dividend<00:53:09.680> on<00:53:09.839> the<00:53:09.920> long 00:53:10.309 --> 00:53:10.319 align:start position:0% going to pay a dividend on the long 00:53:10.319 --> 00:53:14.549 align:start position:0% going to pay a dividend on the long the<00:53:10.480> long<00:53:12.839> tail 00:53:14.549 --> 00:53:14.559 align:start position:0% the long tail 00:53:14.559 --> 00:53:17.910 align:start position:0% the long tail so<00:53:15.119> i've<00:53:15.359> got<00:53:16.480> a<00:53:16.640> list<00:53:17.040> of<00:53:17.200> things 00:53:17.910 --> 00:53:17.920 align:start position:0% so i've got a list of things 00:53:17.920 --> 00:53:21.430 align:start position:0% so i've got a list of things that<00:53:18.079> i<00:53:18.240> am<00:53:18.400> interested<00:53:18.880> in<00:53:19.280> of<00:53:19.599> late<00:53:20.559> um 00:53:21.430 --> 00:53:21.440 align:start position:0% that i am interested in of late um 00:53:21.440 --> 00:53:23.750 align:start position:0% that i am interested in of late um i<00:53:21.520> think<00:53:22.160> by<00:53:22.400> far<00:53:22.640> the<00:53:22.800> one<00:53:22.960> i'm<00:53:23.119> most<00:53:23.359> excited 00:53:23.750 --> 00:53:23.760 align:start position:0% i think by far the one i'm most excited 00:53:23.760 --> 00:53:25.829 align:start position:0% i think by far the one i'm most excited about<00:53:24.160> is<00:53:24.319> this<00:53:24.559> project<00:53:24.960> which<00:53:25.200> i'll 00:53:25.829 --> 00:53:25.839 align:start position:0% about is this project which i'll 00:53:25.839 --> 00:53:38.950 align:start position:0% about is this project which i'll see<00:53:25.920> if<00:53:26.079> i<00:53:26.160> can<00:53:26.319> open<00:53:26.559> it<00:53:26.839> up 00:53:38.950 --> 00:53:38.960 align:start position:0% 00:53:38.960 --> 00:53:42.069 align:start position:0% oh<00:53:39.200> cool<00:53:39.520> it's<00:53:39.599> not<00:53:39.839> loading<00:53:40.640> anyway<00:53:41.119> um 00:53:42.069 --> 00:53:42.079 align:start position:0% oh cool it's not loading anyway um 00:53:42.079 --> 00:53:44.470 align:start position:0% oh cool it's not loading anyway um there<00:53:42.400> is<00:53:42.640> a<00:53:43.200> professor<00:53:43.680> in<00:53:43.760> france<00:53:44.160> his<00:53:44.240> name 00:53:44.470 --> 00:53:44.480 align:start position:0% there is a professor in france his name 00:53:44.480 --> 00:53:45.750 align:start position:0% there is a professor in france his name is<00:53:44.559> robert<00:53:44.880> strand 00:53:45.750 --> 00:53:45.760 align:start position:0% is robert strand 00:53:45.760 --> 00:53:49.750 align:start position:0% is robert strand he<00:53:47.200> is<00:53:48.160> a<00:53:48.319> longtime<00:53:48.800> lisper 00:53:49.750 --> 00:53:49.760 align:start position:0% he is a longtime lisper 00:53:49.760 --> 00:53:52.790 align:start position:0% he is a longtime lisper and<00:53:50.079> he's<00:53:50.400> known<00:53:50.640> for<00:53:50.800> many<00:53:51.280> uh<00:53:52.000> libraries<00:53:52.640> and 00:53:52.790 --> 00:53:52.800 align:start position:0% and he's known for many uh libraries and 00:53:52.800 --> 00:53:55.270 align:start position:0% and he's known for many uh libraries and initiatives<00:53:53.359> in<00:53:53.440> the<00:53:53.520> common<00:53:53.760> list<00:53:54.000> community 00:53:55.270 --> 00:53:55.280 align:start position:0% initiatives in the common list community 00:53:55.280 --> 00:53:59.589 align:start position:0% initiatives in the common list community and<00:53:56.800> like<00:53:57.280> rich<00:53:57.760> he<00:53:57.920> has<00:53:58.160> dedicated 00:53:59.589 --> 00:53:59.599 align:start position:0% and like rich he has dedicated 00:53:59.599 --> 00:54:01.510 align:start position:0% and like rich he has dedicated a<00:53:59.760> large<00:54:00.079> part<00:54:00.240> of<00:54:00.319> his<00:54:00.480> life<00:54:00.720> to<00:54:00.880> the<00:54:00.960> pursuit 00:54:01.510 --> 00:54:01.520 align:start position:0% a large part of his life to the pursuit 00:54:01.520 --> 00:54:02.870 align:start position:0% a large part of his life to the pursuit of<00:54:01.599> the<00:54:01.680> kind<00:54:01.839> of<00:54:01.920> programming<00:54:02.400> that<00:54:02.480> he<00:54:02.640> wants 00:54:02.870 --> 00:54:02.880 align:start position:0% of the kind of programming that he wants 00:54:02.880 --> 00:54:04.150 align:start position:0% of the kind of programming that he wants to<00:54:03.040> do 00:54:04.150 --> 00:54:04.160 align:start position:0% to do 00:54:04.160 --> 00:54:05.990 align:start position:0% to do and<00:54:04.400> so<00:54:05.040> there's<00:54:05.280> always<00:54:05.520> a<00:54:05.520> lot<00:54:05.680> to<00:54:05.839> learn 00:54:05.990 --> 00:54:06.000 align:start position:0% and so there's always a lot to learn 00:54:06.000 --> 00:54:07.510 align:start position:0% and so there's always a lot to learn from<00:54:06.160> such<00:54:06.400> people 00:54:07.510 --> 00:54:07.520 align:start position:0% from such people 00:54:07.520 --> 00:54:10.069 align:start position:0% from such people and<00:54:08.720> there's<00:54:08.960> a<00:54:08.960> lot<00:54:09.119> to<00:54:09.440> learn<00:54:09.599> from<00:54:09.760> him<00:54:10.000> in 00:54:10.069 --> 00:54:10.079 align:start position:0% and there's a lot to learn from him in 00:54:10.079 --> 00:54:11.430 align:start position:0% and there's a lot to learn from him in particular<00:54:10.480> he's<00:54:10.720> given<00:54:10.880> a<00:54:10.960> lot<00:54:11.119> of<00:54:11.200> talks 00:54:11.430 --> 00:54:11.440 align:start position:0% particular he's given a lot of talks 00:54:11.440 --> 00:54:12.549 align:start position:0% particular he's given a lot of talks that<00:54:11.520> are<00:54:11.599> on<00:54:11.760> youtube<00:54:12.000> he's<00:54:12.160> written<00:54:12.400> a<00:54:12.400> lot 00:54:12.549 --> 00:54:12.559 align:start position:0% that are on youtube he's written a lot 00:54:12.559 --> 00:54:14.230 align:start position:0% that are on youtube he's written a lot of<00:54:12.640> papers<00:54:13.040> and<00:54:13.200> all<00:54:13.359> of<00:54:13.440> his<00:54:13.599> papers 00:54:14.230 --> 00:54:14.240 align:start position:0% of papers and all of his papers 00:54:14.240 --> 00:54:17.349 align:start position:0% of papers and all of his papers are<00:54:15.520> really<00:54:15.839> short<00:54:16.160> and<00:54:16.319> clear<00:54:16.880> relative<00:54:17.280> to 00:54:17.349 --> 00:54:17.359 align:start position:0% are really short and clear relative to 00:54:17.359 --> 00:54:17.750 align:start position:0% are really short and clear relative to other 00:54:17.750 --> 00:54:17.760 align:start position:0% other 00:54:17.760 --> 00:54:21.030 align:start position:0% other papers<00:54:18.240> even<00:54:18.640> even<00:54:18.880> list<00:54:19.119> papers<00:54:20.240> so 00:54:21.030 --> 00:54:21.040 align:start position:0% papers even even list papers so 00:54:21.040 --> 00:54:22.150 align:start position:0% papers even even list papers so everything<00:54:21.359> about<00:54:21.599> this<00:54:21.760> guy<00:54:21.920> and<00:54:22.000> his 00:54:22.150 --> 00:54:22.160 align:start position:0% everything about this guy and his 00:54:22.160 --> 00:54:24.390 align:start position:0% everything about this guy and his projects<00:54:22.480> i'm<00:54:22.559> super<00:54:22.800> into<00:54:23.119> usually<00:54:24.000> um 00:54:24.390 --> 00:54:24.400 align:start position:0% projects i'm super into usually um 00:54:24.400 --> 00:54:26.549 align:start position:0% projects i'm super into usually um there's<00:54:24.640> an<00:54:24.800> irc<00:54:25.280> channel<00:54:25.520> on<00:54:25.680> free<00:54:25.839> node<00:54:26.400> it's 00:54:26.549 --> 00:54:26.559 align:start position:0% there's an irc channel on free node it's 00:54:26.559 --> 00:54:28.630 align:start position:0% there's an irc channel on free node it's the<00:54:26.720> sickle<00:54:27.359> channel<00:54:27.599> where<00:54:27.839> you<00:54:27.920> can 00:54:28.630 --> 00:54:28.640 align:start position:0% the sickle channel where you can 00:54:28.640 --> 00:54:30.309 align:start position:0% the sickle channel where you can follow<00:54:29.040> what<00:54:29.200> he's<00:54:29.440> doing<00:54:29.680> he<00:54:29.839> checks<00:54:30.160> in 00:54:30.309 --> 00:54:30.319 align:start position:0% follow what he's doing he checks in 00:54:30.319 --> 00:54:31.589 align:start position:0% follow what he's doing he checks in every<00:54:30.559> morning<00:54:30.880> and<00:54:30.960> he<00:54:31.040> says<00:54:31.200> good<00:54:31.359> morning 00:54:31.589 --> 00:54:31.599 align:start position:0% every morning and he says good morning 00:54:31.599 --> 00:54:32.710 align:start position:0% every morning and he says good morning everyone<00:54:31.920> this<00:54:32.079> is<00:54:32.160> what<00:54:32.240> i'm<00:54:32.319> working<00:54:32.559> on 00:54:32.710 --> 00:54:32.720 align:start position:0% everyone this is what i'm working on 00:54:32.720 --> 00:54:33.349 align:start position:0% everyone this is what i'm working on today 00:54:33.349 --> 00:54:33.359 align:start position:0% today 00:54:33.359 --> 00:54:35.030 align:start position:0% today so<00:54:33.520> you<00:54:33.680> have<00:54:33.920> like<00:54:34.400> it's<00:54:34.559> it's<00:54:34.720> kind<00:54:34.880> of 00:54:35.030 --> 00:54:35.040 align:start position:0% so you have like it's it's kind of 00:54:35.040 --> 00:54:36.630 align:start position:0% so you have like it's it's kind of exciting<00:54:35.359> i<00:54:35.839> i'm<00:54:36.160> never 00:54:36.630 --> 00:54:36.640 align:start position:0% exciting i i'm never 00:54:36.640 --> 00:54:38.390 align:start position:0% exciting i i'm never i'm<00:54:36.880> rarely<00:54:37.280> able<00:54:37.440> to<00:54:37.520> offer<00:54:37.839> him<00:54:38.000> any<00:54:38.160> kind<00:54:38.319> of 00:54:38.390 --> 00:54:38.400 align:start position:0% i'm rarely able to offer him any kind of 00:54:38.400 --> 00:54:40.150 align:start position:0% i'm rarely able to offer him any kind of feedback<00:54:39.040> but<00:54:39.200> i<00:54:39.280> always<00:54:39.440> try<00:54:39.599> to<00:54:39.680> register<00:54:40.000> my 00:54:40.150 --> 00:54:40.160 align:start position:0% feedback but i always try to register my 00:54:40.160 --> 00:54:40.630 align:start position:0% feedback but i always try to register my interest 00:54:40.630 --> 00:54:40.640 align:start position:0% interest 00:54:40.640 --> 00:54:44.309 align:start position:0% interest and<00:54:40.799> support<00:54:42.079> um<00:54:43.520> but 00:54:44.309 --> 00:54:44.319 align:start position:0% and support um but 00:54:44.319 --> 00:54:47.109 align:start position:0% and support um but he<00:54:44.640> has<00:54:45.040> a<00:54:45.280> really<00:54:45.599> comprehensive<00:54:46.400> and 00:54:47.109 --> 00:54:47.119 align:start position:0% he has a really comprehensive and 00:54:47.119 --> 00:54:48.950 align:start position:0% he has a really comprehensive and well-designed<00:54:47.920> plan 00:54:48.950 --> 00:54:48.960 align:start position:0% well-designed plan 00:54:48.960 --> 00:54:50.630 align:start position:0% well-designed plan to<00:54:49.119> write<00:54:49.359> a<00:54:49.440> new<00:54:49.680> implementation<00:54:50.240> of<00:54:50.319> common 00:54:50.630 --> 00:54:50.640 align:start position:0% to write a new implementation of common 00:54:50.640 --> 00:54:52.150 align:start position:0% to write a new implementation of common lisp<00:54:51.119> and 00:54:52.150 --> 00:54:52.160 align:start position:0% lisp and 00:54:52.160 --> 00:54:53.430 align:start position:0% lisp and for<00:54:52.319> his<00:54:52.559> implementation<00:54:53.119> to<00:54:53.280> have 00:54:53.430 --> 00:54:53.440 align:start position:0% for his implementation to have 00:54:53.440 --> 00:54:55.270 align:start position:0% for his implementation to have properties<00:54:54.000> that<00:54:54.240> no<00:54:54.480> other<00:54:54.720> implementation 00:54:55.270 --> 00:54:55.280 align:start position:0% properties that no other implementation 00:54:55.280 --> 00:54:56.230 align:start position:0% properties that no other implementation does 00:54:56.230 --> 00:54:56.240 align:start position:0% does 00:54:56.240 --> 00:55:00.150 align:start position:0% does principally 00:55:00.150 --> 00:55:00.160 align:start position:0% 00:55:00.160 --> 00:55:02.390 align:start position:0% well<00:55:00.720> two<00:55:00.880> things<00:55:01.119> the<00:55:01.280> benefit<00:55:01.599> of<00:55:01.680> hindsight 00:55:02.390 --> 00:55:02.400 align:start position:0% well two things the benefit of hindsight 00:55:02.400 --> 00:55:03.589 align:start position:0% well two things the benefit of hindsight like<00:55:02.559> the<00:55:02.640> hindsight<00:55:03.119> of<00:55:03.200> multiple 00:55:03.589 --> 00:55:03.599 align:start position:0% like the hindsight of multiple 00:55:03.599 --> 00:55:04.470 align:start position:0% like the hindsight of multiple implementations 00:55:04.470 --> 00:55:04.480 align:start position:0% implementations 00:55:04.480 --> 00:55:06.789 align:start position:0% implementations most<00:55:04.720> of<00:55:04.799> the<00:55:05.359> implementations<00:55:06.079> today<00:55:06.480> are 00:55:06.789 --> 00:55:06.799 align:start position:0% most of the implementations today are 00:55:06.799 --> 00:55:08.789 align:start position:0% most of the implementations today are are 00:55:08.789 --> 00:55:08.799 align:start position:0% are 00:55:08.799 --> 00:55:11.190 align:start position:0% are descended<00:55:09.599> from<00:55:10.240> implementations<00:55:11.040> of<00:55:11.119> the 00:55:11.190 --> 00:55:11.200 align:start position:0% descended from implementations of the 00:55:11.200 --> 00:55:11.910 align:start position:0% descended from implementations of the 80s 00:55:11.910 --> 00:55:11.920 align:start position:0% 80s 00:55:11.920 --> 00:55:15.430 align:start position:0% 80s and<00:55:12.240> early<00:55:12.480> 90s<00:55:13.760> that<00:55:13.920> have<00:55:14.160> built<00:55:14.400> into<00:55:14.640> them 00:55:15.430 --> 00:55:15.440 align:start position:0% and early 90s that have built into them 00:55:15.440 --> 00:55:17.670 align:start position:0% and early 90s that have built into them certain<00:55:15.920> assumptions<00:55:16.400> about<00:55:17.440> you<00:55:17.520> know 00:55:17.670 --> 00:55:17.680 align:start position:0% certain assumptions about you know 00:55:17.680 --> 00:55:19.910 align:start position:0% certain assumptions about you know what's<00:55:18.079> efficient 00:55:19.910 --> 00:55:19.920 align:start position:0% what's efficient 00:55:19.920 --> 00:55:23.670 align:start position:0% what's efficient most<00:55:20.160> of<00:55:20.240> them<00:55:21.040> do<00:55:21.200> not<00:55:21.599> use<00:55:22.720> common<00:55:23.119> lisps 00:55:23.670 --> 00:55:23.680 align:start position:0% most of them do not use common lisps 00:55:23.680 --> 00:55:25.109 align:start position:0% most of them do not use common lisps highest<00:55:24.000> level<00:55:24.240> abstractions<00:55:24.880> in<00:55:24.960> their 00:55:25.109 --> 00:55:25.119 align:start position:0% highest level abstractions in their 00:55:25.119 --> 00:55:27.349 align:start position:0% highest level abstractions in their implementation<00:55:26.079> so<00:55:26.240> they're<00:55:26.400> not 00:55:27.349 --> 00:55:27.359 align:start position:0% implementation so they're not 00:55:27.359 --> 00:55:29.109 align:start position:0% implementation so they're not strictly<00:55:27.839> speaking<00:55:28.160> they're<00:55:28.319> meta<00:55:28.559> circular 00:55:29.109 --> 00:55:29.119 align:start position:0% strictly speaking they're meta circular 00:55:29.119 --> 00:55:30.789 align:start position:0% strictly speaking they're meta circular because<00:55:29.280> they<00:55:29.440> are<00:55:29.520> written<00:55:29.760> in<00:55:29.920> lisp 00:55:30.789 --> 00:55:30.799 align:start position:0% because they are written in lisp 00:55:30.799 --> 00:55:32.950 align:start position:0% because they are written in lisp but<00:55:30.960> they're<00:55:31.200> not<00:55:31.520> fully<00:55:32.079> object<00:55:32.480> oriented 00:55:32.950 --> 00:55:32.960 align:start position:0% but they're not fully object oriented 00:55:32.960 --> 00:55:34.549 align:start position:0% but they're not fully object oriented using<00:55:33.359> lisp's 00:55:34.549 --> 00:55:34.559 align:start position:0% using lisp's 00:55:34.559 --> 00:55:37.670 align:start position:0% using lisp's best<00:55:36.000> object-oriented<00:55:36.720> constructs 00:55:37.670 --> 00:55:37.680 align:start position:0% best object-oriented constructs 00:55:37.680 --> 00:55:39.589 align:start position:0% best object-oriented constructs and<00:55:38.000> i'm<00:55:38.160> sorry<00:55:38.400> to<00:55:38.480> use<00:55:38.640> that<00:55:38.799> word<00:55:39.040> but<00:55:39.440> in 00:55:39.589 --> 00:55:39.599 align:start position:0% and i'm sorry to use that word but in 00:55:39.599 --> 00:55:40.789 align:start position:0% and i'm sorry to use that word but in lisp<00:55:40.000> it's<00:55:40.079> a<00:55:40.160> good<00:55:40.319> word 00:55:40.789 --> 00:55:40.799 align:start position:0% lisp it's a good word 00:55:40.799 --> 00:55:44.309 align:start position:0% lisp it's a good word trust<00:55:41.040> me<00:55:42.240> um 00:55:44.309 --> 00:55:44.319 align:start position:0% trust me um 00:55:44.319 --> 00:55:47.750 align:start position:0% trust me um so<00:55:44.480> his<00:55:44.799> idea<00:55:45.200> is<00:55:45.920> make<00:55:46.079> a<00:55:46.160> new<00:55:46.400> implementation 00:55:47.750 --> 00:55:47.760 align:start position:0% so his idea is make a new implementation 00:55:47.760 --> 00:55:49.910 align:start position:0% so his idea is make a new implementation written<00:55:48.079> in<00:55:48.160> the<00:55:48.240> highest<00:55:48.720> possible<00:55:49.520> level 00:55:49.910 --> 00:55:49.920 align:start position:0% written in the highest possible level 00:55:49.920 --> 00:55:51.990 align:start position:0% written in the highest possible level common<00:55:50.240> lisp<00:55:50.559> that<00:55:50.720> he<00:55:50.799> can 00:55:51.990 --> 00:55:52.000 align:start position:0% common lisp that he can 00:55:52.000 --> 00:55:54.309 align:start position:0% common lisp that he can and<00:55:52.160> then<00:55:52.880> bootstrap<00:55:53.520> from<00:55:53.760> the<00:55:53.920> existing 00:55:54.309 --> 00:55:54.319 align:start position:0% and then bootstrap from the existing 00:55:54.319 --> 00:55:55.990 align:start position:0% and then bootstrap from the existing implementations 00:55:55.990 --> 00:55:56.000 align:start position:0% implementations 00:55:56.000 --> 00:55:58.390 align:start position:0% implementations so<00:55:56.640> what<00:55:56.799> you<00:55:57.040> end<00:55:57.200> up<00:55:57.280> with<00:55:57.520> and<00:55:57.680> what<00:55:57.839> he<00:55:58.000> has 00:55:58.390 --> 00:55:58.400 align:start position:0% so what you end up with and what he has 00:55:58.400 --> 00:56:00.829 align:start position:0% so what you end up with and what he has is<00:55:58.640> a<00:55:58.799> set<00:55:58.960> of<00:55:59.200> libraries 00:56:00.829 --> 00:56:00.839 align:start position:0% is a set of libraries 00:56:00.839 --> 00:56:03.430 align:start position:0% is a set of libraries that<00:56:02.079> sum<00:56:02.319> up<00:56:02.480> to<00:56:02.640> an<00:56:02.720> implementation<00:56:03.280> they're 00:56:03.430 --> 00:56:03.440 align:start position:0% that sum up to an implementation they're 00:56:03.440 --> 00:56:03.990 align:start position:0% that sum up to an implementation they're just<00:56:03.599> all 00:56:03.990 --> 00:56:04.000 align:start position:0% just all 00:56:04.000 --> 00:56:07.270 align:start position:0% just all beautifully<00:56:04.480> written<00:56:05.440> um<00:56:06.319> and<00:56:06.559> his 00:56:07.270 --> 00:56:07.280 align:start position:0% beautifully written um and his 00:56:07.280 --> 00:56:08.789 align:start position:0% beautifully written um and his implementation<00:56:07.920> of<00:56:08.000> one<00:56:08.160> of<00:56:08.240> commonless 00:56:08.789 --> 00:56:08.799 align:start position:0% implementation of one of commonless 00:56:08.799 --> 00:56:10.470 align:start position:0% implementation of one of commonless standard<00:56:09.119> macros<00:56:09.599> the<00:56:09.680> loop<00:56:09.920> macro<00:56:10.240> is<00:56:10.319> what 00:56:10.470 --> 00:56:10.480 align:start position:0% standard macros the loop macro is what 00:56:10.480 --> 00:56:12.390 align:start position:0% standard macros the loop macro is what got<00:56:10.640> me<00:56:10.720> into<00:56:10.960> sickle<00:56:11.280> originally<00:56:11.760> so 00:56:12.390 --> 00:56:12.400 align:start position:0% got me into sickle originally so 00:56:12.400 --> 00:56:14.710 align:start position:0% got me into sickle originally so i<00:56:12.559> can't<00:56:12.799> i<00:56:12.880> can't<00:56:13.119> recommend<00:56:13.839> his<00:56:14.079> stuff<00:56:14.400> or 00:56:14.710 --> 00:56:14.720 align:start position:0% i can't i can't recommend his stuff or 00:56:14.720 --> 00:56:16.069 align:start position:0% i can't i can't recommend his stuff or things<00:56:14.960> related<00:56:15.280> to<00:56:15.359> this<00:56:15.440> project<00:56:15.760> enough 00:56:16.069 --> 00:56:16.079 align:start position:0% things related to this project enough 00:56:16.079 --> 00:56:17.910 align:start position:0% things related to this project enough it's<00:56:16.240> like<00:56:16.400> a<00:56:16.480> great<00:56:16.720> source<00:56:17.119> of 00:56:17.910 --> 00:56:17.920 align:start position:0% it's like a great source of 00:56:17.920 --> 00:56:21.430 align:start position:0% it's like a great source of really<00:56:18.160> high<00:56:18.400> quality<00:56:20.720> information 00:56:21.430 --> 00:56:21.440 align:start position:0% really high quality information 00:56:21.440 --> 00:56:24.069 align:start position:0% really high quality information and<00:56:21.599> it's<00:56:21.760> exciting<00:56:22.319> because<00:56:23.520> uh<00:56:23.760> i<00:56:23.839> think<00:56:24.000> it 00:56:24.069 --> 00:56:24.079 align:start position:0% and it's exciting because uh i think it 00:56:24.079 --> 00:56:26.230 align:start position:0% and it's exciting because uh i think it was<00:56:24.160> last<00:56:24.400> week<00:56:24.559> or<00:56:24.720> the<00:56:24.799> week<00:56:24.960> before 00:56:26.230 --> 00:56:26.240 align:start position:0% was last week or the week before 00:56:26.240 --> 00:56:28.390 align:start position:0% was last week or the week before he<00:56:26.400> was<00:56:26.640> able<00:56:26.799> to<00:56:26.880> use<00:56:27.119> sickle<00:56:27.520> to<00:56:27.760> either<00:56:28.240> to 00:56:28.390 --> 00:56:28.400 align:start position:0% he was able to use sickle to either to 00:56:28.400 --> 00:56:30.630 align:start position:0% he was able to use sickle to either to load<00:56:28.720> and<00:56:28.839> compile 00:56:30.630 --> 00:56:30.640 align:start position:0% load and compile 00:56:30.640 --> 00:56:32.309 align:start position:0% load and compile a<00:56:30.799> large<00:56:31.200> part<00:56:31.440> of<00:56:31.599> a<00:56:31.760> package<00:56:32.079> called 00:56:32.309 --> 00:56:32.319 align:start position:0% a large part of a package called 00:56:32.319 --> 00:56:34.549 align:start position:0% a large part of a package called alexandria<00:56:33.119> which<00:56:33.359> is<00:56:33.440> like<00:56:33.680> commonly 00:56:34.549 --> 00:56:34.559 align:start position:0% alexandria which is like commonly 00:56:34.559 --> 00:56:36.549 align:start position:0% alexandria which is like commonly standard<00:56:35.040> third-party<00:56:35.599> utility<00:56:36.079> package<00:56:36.480> and 00:56:36.549 --> 00:56:36.559 align:start position:0% standard third-party utility package and 00:56:36.559 --> 00:56:38.230 align:start position:0% standard third-party utility package and this<00:56:36.799> is<00:56:36.880> like<00:56:37.119> many<00:56:37.359> thousands<00:56:37.760> of<00:56:37.839> lines<00:56:38.160> of 00:56:38.230 --> 00:56:38.240 align:start position:0% this is like many thousands of lines of 00:56:38.240 --> 00:56:38.950 align:start position:0% this is like many thousands of lines of common<00:56:38.559> lisp 00:56:38.950 --> 00:56:38.960 align:start position:0% common lisp 00:56:38.960 --> 00:56:41.990 align:start position:0% common lisp using<00:56:39.200> a<00:56:39.280> lot<00:56:39.440> of<00:56:39.599> esoteric<00:56:40.079> features 00:56:41.990 --> 00:56:42.000 align:start position:0% using a lot of esoteric features 00:56:42.000 --> 00:56:43.510 align:start position:0% using a lot of esoteric features and<00:56:42.160> so<00:56:42.319> when<00:56:42.559> he<00:56:42.640> was<00:56:42.720> able<00:56:42.880> to<00:56:42.960> load<00:56:43.200> that<00:56:43.359> up 00:56:43.510 --> 00:56:43.520 align:start position:0% and so when he was able to load that up 00:56:43.520 --> 00:56:45.030 align:start position:0% and so when he was able to load that up he<00:56:43.599> announced<00:56:43.920> it<00:56:44.000> in<00:56:44.160> irc<00:56:44.559> and<00:56:44.640> i<00:56:44.720> got<00:56:44.880> really 00:56:45.030 --> 00:56:45.040 align:start position:0% he announced it in irc and i got really 00:56:45.040 --> 00:56:46.309 align:start position:0% he announced it in irc and i got really excited<00:56:45.359> because<00:56:45.520> i<00:56:45.680> thought<00:56:45.839> oh 00:56:46.309 --> 00:56:46.319 align:start position:0% excited because i thought oh 00:56:46.319 --> 00:56:47.510 align:start position:0% excited because i thought oh i<00:56:46.480> might<00:56:46.640> be<00:56:46.720> able<00:56:46.799> to<00:56:46.880> use<00:56:47.040> sickle<00:56:47.280> in<00:56:47.440> my 00:56:47.510 --> 00:56:47.520 align:start position:0% i might be able to use sickle in my 00:56:47.520 --> 00:56:49.190 align:start position:0% i might be able to use sickle in my lifetime<00:56:47.920> for<00:56:48.079> sure<00:56:48.400> like<00:56:48.559> maybe<00:56:48.880> even<00:56:49.119> the 00:56:49.190 --> 00:56:49.200 align:start position:0% lifetime for sure like maybe even the 00:56:49.200 --> 00:56:50.870 align:start position:0% lifetime for sure like maybe even the next<00:56:49.359> couple<00:56:49.680> years 00:56:50.870 --> 00:56:50.880 align:start position:0% next couple years 00:56:50.880 --> 00:56:54.870 align:start position:0% next couple years so<00:56:52.319> that's<00:56:52.640> fun<00:56:53.280> um<00:56:53.599> jackal 00:56:54.870 --> 00:56:54.880 align:start position:0% so that's fun um jackal 00:56:54.880 --> 00:56:59.109 align:start position:0% so that's fun um jackal is<00:56:56.839> my<00:56:57.920> i<00:56:58.000> mean<00:56:58.160> certainly<00:56:58.480> in<00:56:58.559> comparison<00:56:58.960> to 00:56:59.109 --> 00:56:59.119 align:start position:0% is my i mean certainly in comparison to 00:56:59.119 --> 00:56:59.589 align:start position:0% is my i mean certainly in comparison to sickle 00:56:59.589 --> 00:56:59.599 align:start position:0% sickle 00:56:59.599 --> 00:57:01.750 align:start position:0% sickle hobby<00:57:00.160> pet<00:57:00.640> thing<00:57:01.040> i<00:57:01.119> don't<00:57:01.280> work<00:57:01.520> on<00:57:01.599> this 00:57:01.750 --> 00:57:01.760 align:start position:0% hobby pet thing i don't work on this 00:57:01.760 --> 00:57:03.190 align:start position:0% hobby pet thing i don't work on this every<00:57:01.920> day<00:57:02.160> i<00:57:02.240> don't<00:57:02.400> even<00:57:02.559> work<00:57:02.720> on<00:57:02.880> it<00:57:02.960> every 00:57:03.190 --> 00:57:03.200 align:start position:0% every day i don't even work on it every 00:57:03.200 --> 00:57:03.589 align:start position:0% every day i don't even work on it every week 00:57:03.589 --> 00:57:03.599 align:start position:0% week 00:57:03.599 --> 00:57:06.390 align:start position:0% week it's<00:57:03.760> a<00:57:03.920> long<00:57:04.160> term<00:57:04.559> bet<00:57:05.119> and<00:57:05.680> a<00:57:05.760> lot<00:57:05.920> of<00:57:06.000> it<00:57:06.160> is 00:57:06.390 --> 00:57:06.400 align:start position:0% it's a long term bet and a lot of it is 00:57:06.400 --> 00:57:08.870 align:start position:0% it's a long term bet and a lot of it is educational<00:57:06.960> for<00:57:07.119> me<00:57:07.280> but<00:57:07.440> this<00:57:07.680> is 00:57:08.870 --> 00:57:08.880 align:start position:0% educational for me but this is 00:57:08.880 --> 00:57:11.430 align:start position:0% educational for me but this is uh<00:57:09.280> an<00:57:09.520> attempt<00:57:10.000> to<00:57:10.160> bring<00:57:10.400> the<00:57:10.480> common<00:57:10.799> lisp 00:57:11.430 --> 00:57:11.440 align:start position:0% uh an attempt to bring the common lisp 00:57:11.440 --> 00:57:12.150 align:start position:0% uh an attempt to bring the common lisp platform 00:57:12.150 --> 00:57:12.160 align:start position:0% platform 00:57:12.160 --> 00:57:14.390 align:start position:0% platform at<00:57:12.240> least<00:57:12.480> parts<00:57:12.720> of<00:57:12.880> it<00:57:13.119> to<00:57:13.440> javascript<00:57:14.319> and 00:57:14.390 --> 00:57:14.400 align:start position:0% at least parts of it to javascript and 00:57:14.400 --> 00:57:16.470 align:start position:0% at least parts of it to javascript and to<00:57:14.559> think<00:57:14.799> about 00:57:16.470 --> 00:57:16.480 align:start position:0% to think about 00:57:16.480 --> 00:57:19.030 align:start position:0% to think about those<00:57:16.799> platform<00:57:17.440> impedance<00:57:17.920> issues<00:57:18.799> that<00:57:18.960> i 00:57:19.030 --> 00:57:19.040 align:start position:0% those platform impedance issues that i 00:57:19.040 --> 00:57:20.309 align:start position:0% those platform impedance issues that i mentioned<00:57:19.359> having<00:57:19.599> to<00:57:19.680> do<00:57:19.839> with<00:57:19.920> lining<00:57:20.240> up 00:57:20.309 --> 00:57:20.319 align:start position:0% mentioned having to do with lining up 00:57:20.319 --> 00:57:22.230 align:start position:0% mentioned having to do with lining up the<00:57:20.400> data<00:57:20.720> types<00:57:21.040> and<00:57:21.200> lining<00:57:21.520> up<00:57:21.599> the 00:57:22.230 --> 00:57:22.240 align:start position:0% the data types and lining up the 00:57:22.240 --> 00:57:24.710 align:start position:0% the data types and lining up the abstractions<00:57:22.960> and<00:57:23.040> use<00:57:23.280> cases<00:57:23.680> and<00:57:23.760> so<00:57:23.920> on<00:57:24.640> and 00:57:24.710 --> 00:57:24.720 align:start position:0% abstractions and use cases and so on and 00:57:24.720 --> 00:57:26.069 align:start position:0% abstractions and use cases and so on and so<00:57:24.880> there's<00:57:25.119> a<00:57:25.200> paper<00:57:25.440> that<00:57:25.520> i<00:57:25.599> wrote<00:57:25.839> about 00:57:26.069 --> 00:57:26.079 align:start position:0% so there's a paper that i wrote about 00:57:26.079 --> 00:57:26.710 align:start position:0% so there's a paper that i wrote about that<00:57:26.319> that 00:57:26.710 --> 00:57:26.720 align:start position:0% that that 00:57:26.720 --> 00:57:31.109 align:start position:0% that that uh<00:57:28.319> that<00:57:29.359> illuminates<00:57:30.000> that 00:57:31.109 --> 00:57:31.119 align:start position:0% uh that illuminates that 00:57:31.119 --> 00:57:33.670 align:start position:0% uh that illuminates that and<00:57:31.760> uh<00:57:32.079> i<00:57:32.480> still<00:57:32.720> i<00:57:32.880> still<00:57:33.040> poke<00:57:33.280> at<00:57:33.359> that<00:57:33.520> most 00:57:33.670 --> 00:57:33.680 align:start position:0% and uh i still i still poke at that most 00:57:33.680 --> 00:57:35.109 align:start position:0% and uh i still i still poke at that most recently<00:57:34.079> i've<00:57:34.160> been<00:57:34.240> working<00:57:34.480> on<00:57:34.640> multiple 00:57:35.109 --> 00:57:35.119 align:start position:0% recently i've been working on multiple 00:57:35.119 --> 00:57:36.390 align:start position:0% recently i've been working on multiple value<00:57:35.520> return 00:57:36.390 --> 00:57:36.400 align:start position:0% value return 00:57:36.400 --> 00:57:38.710 align:start position:0% value return support<00:57:37.440> to<00:57:37.599> be<00:57:37.760> efficient<00:57:38.160> in<00:57:38.240> there<00:57:38.559> which 00:57:38.710 --> 00:57:38.720 align:start position:0% support to be efficient in there which 00:57:38.720 --> 00:57:41.030 align:start position:0% support to be efficient in there which is<00:57:38.880> the<00:57:38.960> thing<00:57:39.200> i'll<00:57:39.359> talk<00:57:39.520> about 00:57:41.030 --> 00:57:41.040 align:start position:0% is the thing i'll talk about 00:57:41.040 --> 00:57:44.789 align:start position:0% is the thing i'll talk about um<00:57:43.440> and<00:57:43.760> yeah<00:57:44.000> i<00:57:44.079> think<00:57:44.240> i'll<00:57:44.319> leave<00:57:44.559> these 00:57:44.789 --> 00:57:44.799 align:start position:0% um and yeah i think i'll leave these 00:57:44.799 --> 00:57:47.109 align:start position:0% um and yeah i think i'll leave these other<00:57:44.960> things<00:57:45.280> for<00:57:45.440> you<00:57:45.599> to<00:57:45.839> explore 00:57:47.109 --> 00:57:47.119 align:start position:0% other things for you to explore 00:57:47.119 --> 00:57:50.309 align:start position:0% other things for you to explore uh<00:57:48.720> one<00:57:48.960> thing<00:57:49.359> i<00:57:49.599> will 00:57:50.309 --> 00:57:50.319 align:start position:0% uh one thing i will 00:57:50.319 --> 00:57:52.230 align:start position:0% uh one thing i will emphasize<00:57:50.880> or<00:57:51.119> one<00:57:51.280> thing<00:57:51.440> i'll<00:57:51.680> highlight<00:57:52.079> is 00:57:52.230 --> 00:57:52.240 align:start position:0% emphasize or one thing i'll highlight is 00:57:52.240 --> 00:57:54.470 align:start position:0% emphasize or one thing i'll highlight is peter<00:57:52.559> norvig<00:57:52.960> so<00:57:53.119> peter<00:57:53.440> norvig 00:57:54.470 --> 00:57:54.480 align:start position:0% peter norvig so peter norvig 00:57:54.480 --> 00:57:57.910 align:start position:0% peter norvig so peter norvig long<00:57:54.799> time<00:57:56.160> whisper<00:57:56.880> and<00:57:57.119> also 00:57:57.910 --> 00:57:57.920 align:start position:0% long time whisper and also 00:57:57.920 --> 00:58:01.030 align:start position:0% long time whisper and also lisp's<00:57:58.640> most<00:57:58.880> famous<00:57:59.280> defector<00:58:00.000> probably 00:58:01.030 --> 00:58:01.040 align:start position:0% lisp's most famous defector probably 00:58:01.040 --> 00:58:03.190 align:start position:0% lisp's most famous defector probably because<00:58:01.440> he<00:58:01.599> famously<00:58:02.160> switched<00:58:02.480> from<00:58:02.960> after 00:58:03.190 --> 00:58:03.200 align:start position:0% because he famously switched from after 00:58:03.200 --> 00:58:05.270 align:start position:0% because he famously switched from after doing<00:58:03.359> decades<00:58:03.760> of<00:58:03.920> common<00:58:04.160> lisp<00:58:04.480> and<00:58:04.640> ai 00:58:05.270 --> 00:58:05.280 align:start position:0% doing decades of common lisp and ai 00:58:05.280 --> 00:58:09.829 align:start position:0% doing decades of common lisp and ai for<00:58:05.440> ai<00:58:05.760> research<00:58:06.160> to<00:58:06.319> using<00:58:06.839> python<00:58:08.000> and 00:58:09.829 --> 00:58:09.839 align:start position:0% for ai research to using python and 00:58:09.839 --> 00:58:13.589 align:start position:0% for ai research to using python and i<00:58:10.000> think<00:58:11.440> that<00:58:11.680> confused<00:58:12.400> and<00:58:12.799> saddened 00:58:13.589 --> 00:58:13.599 align:start position:0% i think that confused and saddened 00:58:13.599 --> 00:58:16.630 align:start position:0% i think that confused and saddened many<00:58:13.839> people<00:58:14.000> in<00:58:14.079> this<00:58:14.400> community<00:58:16.160> but 00:58:16.630 --> 00:58:16.640 align:start position:0% many people in this community but 00:58:16.640 --> 00:58:19.510 align:start position:0% many people in this community but if<00:58:16.799> you<00:58:16.960> click<00:58:17.359> on<00:58:18.400> this<00:58:18.799> video<00:58:19.200> he's 00:58:19.510 --> 00:58:19.520 align:start position:0% if you click on this video he's 00:58:19.520 --> 00:58:21.109 align:start position:0% if you click on this video he's interviewed<00:58:20.079> on<00:58:20.160> a<00:58:20.240> podcast<00:58:20.720> i<00:58:20.799> think<00:58:20.960> two 00:58:21.109 --> 00:58:21.119 align:start position:0% interviewed on a podcast i think two 00:58:21.119 --> 00:58:22.470 align:start position:0% interviewed on a podcast i think two years<00:58:21.359> ago<00:58:21.680> and<00:58:21.760> he<00:58:21.920> gets<00:58:22.079> into 00:58:22.470 --> 00:58:22.480 align:start position:0% years ago and he gets into 00:58:22.480 --> 00:58:26.309 align:start position:0% years ago and he gets into why<00:58:23.040> he<00:58:23.200> did<00:58:23.359> that<00:58:24.480> uh<00:58:25.119> and<00:58:25.359> he<00:58:25.520> has 00:58:26.309 --> 00:58:26.319 align:start position:0% why he did that uh and he has 00:58:26.319 --> 00:58:29.670 align:start position:0% why he did that uh and he has a<00:58:26.480> very<00:58:27.760> nuanced<00:58:28.880> perspective<00:58:29.359> and<00:58:29.520> he's<00:58:29.599> a 00:58:29.670 --> 00:58:29.680 align:start position:0% a very nuanced perspective and he's a 00:58:29.680 --> 00:58:31.030 align:start position:0% a very nuanced perspective and he's a really<00:58:29.839> smart<00:58:30.160> guy<00:58:30.400> so 00:58:31.030 --> 00:58:31.040 align:start position:0% really smart guy so 00:58:31.040 --> 00:58:32.549 align:start position:0% really smart guy so any<00:58:31.280> opportunity<00:58:31.680> to<00:58:31.760> watch<00:58:31.920> him<00:58:32.079> speak<00:58:32.400> about 00:58:32.549 --> 00:58:32.559 align:start position:0% any opportunity to watch him speak about 00:58:32.559 --> 00:58:34.150 align:start position:0% any opportunity to watch him speak about lisp<00:58:32.880> or<00:58:32.960> anything<00:58:33.200> else<00:58:33.440> is<00:58:33.760> you<00:58:33.920> know<00:58:34.000> i 00:58:34.150 --> 00:58:34.160 align:start position:0% lisp or anything else is you know i 00:58:34.160 --> 00:58:35.589 align:start position:0% lisp or anything else is you know i recommend 00:58:35.589 --> 00:58:35.599 align:start position:0% recommend 00:58:35.599 --> 00:58:40.630 align:start position:0% recommend um<00:58:37.119> i<00:58:37.280> think<00:58:37.440> i'm<00:58:37.599> at<00:58:37.680> a<00:58:37.760> good<00:58:38.000> place<00:58:38.319> to 00:58:40.630 --> 00:58:40.640 align:start position:0% 00:58:40.640 --> 00:58:43.670 align:start position:0% stop<00:58:41.760> uh<00:58:42.160> this<00:58:42.319> is<00:58:42.400> the<00:58:42.559> end<00:58:42.720> of<00:58:42.799> my<00:58:42.960> slides 00:58:43.670 --> 00:58:43.680 align:start position:0% stop uh this is the end of my slides 00:58:43.680 --> 00:58:45.670 align:start position:0% stop uh this is the end of my slides my<00:58:43.920> plan<00:58:44.319> was<00:58:44.559> to<00:58:44.799> give<00:58:44.960> you<00:58:45.040> these<00:58:45.200> slides<00:58:45.599> to 00:58:45.670 --> 00:58:45.680 align:start position:0% my plan was to give you these slides to 00:58:45.680 --> 00:58:47.750 align:start position:0% my plan was to give you these slides to give<00:58:45.760> you<00:58:45.839> some<00:58:46.079> background<00:58:46.559> and<00:58:46.720> then<00:58:46.880> we<00:58:47.040> can 00:58:47.750 --> 00:58:47.760 align:start position:0% give you some background and then we can 00:58:47.760 --> 00:58:49.109 align:start position:0% give you some background and then we can whatever<00:58:48.160> time<00:58:48.319> we<00:58:48.400> have<00:58:48.559> we<00:58:48.720> can<00:58:48.799> use<00:58:48.960> for 00:58:49.109 --> 00:58:49.119 align:start position:0% whatever time we have we can use for 00:58:49.119 --> 00:58:50.950 align:start position:0% whatever time we have we can use for discussion<00:58:49.599> or<00:58:49.839> questions 00:58:50.950 --> 00:58:50.960 align:start position:0% discussion or questions 00:58:50.960 --> 00:58:56.870 align:start position:0% discussion or questions or<00:58:51.200> i<00:58:51.280> can<00:58:51.440> do<00:58:51.599> little<00:58:51.760> demos<00:58:52.960> of<00:58:53.119> things 00:58:56.870 --> 00:58:56.880 align:start position:0% 00:58:56.880 --> 00:59:00.870 align:start position:0% sure<00:58:58.960> that<00:58:59.119> was<00:58:59.440> a<00:58:59.520> delightful 00:59:00.870 --> 00:59:00.880 align:start position:0% sure that was a delightful 00:59:00.880 --> 00:59:04.309 align:start position:0% sure that was a delightful talk<00:59:01.359> i<00:59:01.520> could<00:59:01.760> hear<00:59:02.000> you<00:59:02.240> talk<00:59:03.280> so<00:59:03.440> much 00:59:04.309 --> 00:59:04.319 align:start position:0% talk i could hear you talk so much 00:59:04.319 --> 00:59:08.549 align:start position:0% talk i could hear you talk so much longer<00:59:05.119> you<00:59:05.280> could<00:59:05.440> go<00:59:05.599> forever 00:59:08.549 --> 00:59:08.559 align:start position:0% 00:59:08.559 --> 00:59:11.750 align:start position:0% um<00:59:10.160> what<00:59:10.319> a<00:59:10.400> joy<00:59:10.799> what<00:59:10.960> a<00:59:11.040> pleasure<00:59:11.440> really 00:59:11.750 --> 00:59:11.760 align:start position:0% um what a joy what a pleasure really 00:59:11.760 --> 00:59:12.549 align:start position:0% um what a joy what a pleasure really thank<00:59:11.920> you<00:59:12.160> and 00:59:12.549 --> 00:59:12.559 align:start position:0% thank you and 00:59:12.559 --> 00:59:15.829 align:start position:0% thank you and i<00:59:12.640> want<00:59:12.720> to<00:59:12.799> say<00:59:13.040> hi<00:59:13.280> to<00:59:13.760> mikhail<00:59:14.400> who<00:59:14.720> came 00:59:15.829 --> 00:59:15.839 align:start position:0% i want to say hi to mikhail who came 00:59:15.839 --> 00:59:17.990 align:start position:0% i want to say hi to mikhail who came because<00:59:16.079> i<00:59:16.160> didn't<00:59:16.319> have<00:59:16.960> the<00:59:17.119> opportunity 00:59:17.990 --> 00:59:18.000 align:start position:0% because i didn't have the opportunity 00:59:18.000 --> 00:59:20.390 align:start position:0% because i didn't have the opportunity and<00:59:18.400> uh<00:59:18.640> it's<00:59:18.799> good<00:59:19.040> to<00:59:19.119> see<00:59:19.359> you<00:59:19.599> also 00:59:20.390 --> 00:59:20.400 align:start position:0% and uh it's good to see you also 00:59:20.400 --> 00:59:23.270 align:start position:0% and uh it's good to see you also i<00:59:20.559> just<00:59:20.720> want<00:59:20.880> to<00:59:21.040> mention<00:59:21.440> that<00:59:21.760> uh<00:59:22.960> at<00:59:23.119> a 00:59:23.270 --> 00:59:23.280 align:start position:0% i just want to mention that uh at a 00:59:23.280 --> 00:59:24.630 align:start position:0% i just want to mention that uh at a certain<00:59:23.680> time 00:59:24.630 --> 00:59:24.640 align:start position:0% certain time 00:59:24.640 --> 00:59:27.670 align:start position:0% certain time when<00:59:25.119> uh<00:59:25.920> alan<00:59:26.319> and<00:59:26.400> michael<00:59:26.799> were<00:59:27.200> doing<00:59:27.520> the 00:59:27.670 --> 00:59:27.680 align:start position:0% when uh alan and michael were doing the 00:59:27.680 --> 00:59:28.549 align:start position:0% when uh alan and michael were doing the boot<00:59:28.000> project 00:59:28.549 --> 00:59:28.559 align:start position:0% boot project 00:59:28.559 --> 00:59:31.670 align:start position:0% boot project um<00:59:29.520> that's<00:59:29.839> when<00:59:30.000> i<00:59:30.319> i<00:59:30.480> got<00:59:30.720> to<00:59:31.040> contribute<00:59:31.599> a 00:59:31.670 --> 00:59:31.680 align:start position:0% um that's when i i got to contribute a 00:59:31.680 --> 00:59:33.510 align:start position:0% um that's when i i got to contribute a little<00:59:31.839> bit<00:59:32.160> of<00:59:32.319> my<00:59:32.559> own<00:59:32.799> and<00:59:32.960> i<00:59:33.040> want<00:59:33.200> to<00:59:33.280> say 00:59:33.510 --> 00:59:33.520 align:start position:0% little bit of my own and i want to say 00:59:33.520 --> 00:59:35.030 align:start position:0% little bit of my own and i want to say that<00:59:33.680> it<00:59:33.839> was<00:59:34.079> always<00:59:34.400> such 00:59:35.030 --> 00:59:35.040 align:start position:0% that it was always such 00:59:35.040 --> 00:59:38.309 align:start position:0% that it was always such a<00:59:35.680> um<00:59:36.240> nice<00:59:36.480> interaction<00:59:37.119> with<00:59:37.680> the<00:59:37.839> host 00:59:38.309 --> 00:59:38.319 align:start position:0% a um nice interaction with the host 00:59:38.319 --> 00:59:41.030 align:start position:0% a um nice interaction with the host and<00:59:38.640> anybody<00:59:39.040> who<00:59:39.200> is<00:59:39.280> doing<00:59:39.599> open<00:59:39.920> source<00:59:40.720> uh 00:59:41.030 --> 00:59:41.040 align:start position:0% and anybody who is doing open source uh 00:59:41.040 --> 00:59:42.710 align:start position:0% and anybody who is doing open source uh know<00:59:41.359> how<00:59:41.680> difficult<00:59:42.079> it<00:59:42.240> can<00:59:42.400> be 00:59:42.710 --> 00:59:42.720 align:start position:0% know how difficult it can be 00:59:42.720 --> 00:59:45.430 align:start position:0% know how difficult it can be to<00:59:43.280> you<00:59:43.440> know<00:59:44.160> interact<00:59:44.720> with<00:59:44.960> people<00:59:45.280> the 00:59:45.430 --> 00:59:45.440 align:start position:0% to you know interact with people the 00:59:45.440 --> 00:59:46.150 align:start position:0% to you know interact with people the community 00:59:46.150 --> 00:59:46.160 align:start position:0% community 00:59:46.160 --> 00:59:49.190 align:start position:0% community and<00:59:46.400> and<00:59:46.960> and<00:59:47.200> and<00:59:47.520> and<00:59:47.760> make<00:59:47.920> sure<00:59:48.319> that<00:59:48.640> uh 00:59:49.190 --> 00:59:49.200 align:start position:0% and and and and and make sure that uh 00:59:49.200 --> 00:59:52.470 align:start position:0% and and and and and make sure that uh interactions<00:59:49.839> happen<00:59:50.160> on<00:59:50.400> a<00:59:50.880> on<00:59:51.520> on<00:59:51.920> a<00:59:52.079> human 00:59:52.470 --> 00:59:52.480 align:start position:0% interactions happen on a on on a human 00:59:52.480 --> 00:59:53.430 align:start position:0% interactions happen on a on on a human level 00:59:53.430 --> 00:59:53.440 align:start position:0% level 00:59:53.440 --> 00:59:56.470 align:start position:0% level um<00:59:54.240> that<00:59:54.480> is<00:59:54.640> agreeable<00:59:55.119> to<00:59:55.280> everyone<00:59:55.839> and 00:59:56.470 --> 00:59:56.480 align:start position:0% um that is agreeable to everyone and 00:59:56.480 --> 00:59:59.589 align:start position:0% um that is agreeable to everyone and you<00:59:56.720> really<00:59:56.960> did<00:59:57.200> a<00:59:57.359> spectacular<00:59:58.160> job<00:59:59.359> not 00:59:59.589 --> 00:59:59.599 align:start position:0% you really did a spectacular job not 00:59:59.599 --> 00:59:59.990 align:start position:0% you really did a spectacular job not only 00:59:59.990 --> 01:00:00.000 align:start position:0% only 01:00:00.000 --> 01:00:02.309 align:start position:0% only for<01:00:00.160> myself<01:00:00.559> i<01:00:00.880> i<01:00:01.040> was<01:00:01.200> just<01:00:01.520> also<01:00:01.839> observing 01:00:02.309 --> 01:00:02.319 align:start position:0% for myself i i was just also observing 01:00:02.319 --> 01:00:04.470 align:start position:0% for myself i i was just also observing you<01:00:02.640> how<01:00:02.799> you<01:00:02.960> were<01:00:03.200> interacting<01:00:03.680> with<01:00:03.839> the 01:00:04.470 --> 01:00:04.480 align:start position:0% you how you were interacting with the 01:00:04.480 --> 01:00:08.390 align:start position:0% you how you were interacting with the community<01:00:05.440> and<01:00:05.680> it<01:00:05.760> was<01:00:05.920> really<01:00:06.160> a<01:00:06.319> joy<01:00:07.119> so<01:00:07.440> um 01:00:08.390 --> 01:00:08.400 align:start position:0% community and it was really a joy so um 01:00:08.400 --> 01:00:11.990 align:start position:0% community and it was really a joy so um kudos<01:00:08.960> to<01:00:09.119> you<01:00:09.359> and<01:00:10.160> thank<01:00:10.400> you<01:00:11.280> uh 01:00:11.990 --> 01:00:12.000 align:start position:0% kudos to you and thank you uh 01:00:12.000 --> 01:00:14.630 align:start position:0% kudos to you and thank you uh so<01:00:12.240> yeah<01:00:12.480> so<01:00:12.799> i<01:00:12.880> think<01:00:13.119> uh<01:00:13.280> we<01:00:13.280> we<01:00:13.920> could<01:00:14.160> uh<01:00:14.400> go 01:00:14.630 --> 01:00:14.640 align:start position:0% so yeah so i think uh we we could uh go 01:00:14.640 --> 01:00:15.109 align:start position:0% so yeah so i think uh we we could uh go on<01:00:14.799> and 01:00:15.109 --> 01:00:15.119 align:start position:0% on and 01:00:15.119 --> 01:00:19.829 align:start position:0% on and and<01:00:15.440> um<01:00:16.480> uh<01:00:17.040> go<01:00:17.359> go<01:00:17.680> uh<01:00:18.079> see<01:00:18.319> what<01:00:18.559> uh<01:00:18.799> what<01:00:19.040> the 01:00:19.829 --> 01:00:19.839 align:start position:0% and um uh go go uh see what uh what the 01:00:19.839 --> 01:00:21.430 align:start position:0% and um uh go go uh see what uh what the what<01:00:20.079> kind<01:00:20.240> of<01:00:20.400> questions<01:00:20.720> we<01:00:20.880> have<01:00:21.119> from<01:00:21.280> the 01:00:21.430 --> 01:00:21.440 align:start position:0% what kind of questions we have from the 01:00:21.440 --> 01:00:24.630 align:start position:0% what kind of questions we have from the audience 01:00:24.630 --> 01:00:24.640 align:start position:0% 01:00:24.640 --> 01:00:35.030 align:start position:0% so<01:00:25.440> yeah<01:00:25.920> go<01:00:26.079> ahead<01:00:26.319> shoot<01:00:26.880> sammy<01:00:27.200> hi 01:00:35.030 --> 01:00:35.040 align:start position:0% 01:00:35.040 --> 01:00:37.910 align:start position:0% somebody<01:00:35.440> wanted<01:00:35.760> to<01:00:36.240> to<01:00:36.640> i<01:00:36.960> heard<01:00:37.200> that<01:00:37.280> look 01:00:37.910 --> 01:00:37.920 align:start position:0% somebody wanted to to i heard that look 01:00:37.920 --> 01:00:38.870 align:start position:0% somebody wanted to to i heard that look said<01:00:38.240> leave<01:00:38.480> his 01:00:38.870 --> 01:00:38.880 align:start position:0% said leave his 01:00:38.880 --> 01:00:42.390 align:start position:0% said leave his son<01:00:39.119> who<01:00:39.200> was<01:00:40.839> that 01:00:42.390 --> 01:00:42.400 align:start position:0% son who was that 01:00:42.400 --> 01:00:45.430 align:start position:0% son who was that slanted<01:00:42.960> no<01:00:43.520> no<01:00:43.920> sorry<01:00:44.240> um<01:00:44.480> i<01:00:44.640> i<01:00:44.720> was<01:00:44.960> just 01:00:45.430 --> 01:00:45.440 align:start position:0% slanted no no sorry um i i was just 01:00:45.440 --> 01:00:48.630 align:start position:0% slanted no no sorry um i i was just trying<01:00:45.680> to<01:00:45.920> type<01:00:46.160> until<01:00:46.640> uh<01:00:47.920> so 01:00:48.630 --> 01:00:48.640 align:start position:0% trying to type until uh so 01:00:48.640 --> 01:00:51.670 align:start position:0% trying to type until uh so i<01:00:48.720> can<01:00:48.960> i<01:00:49.119> can<01:00:49.280> just<01:00:49.520> ask<01:00:49.760> it<01:00:50.720> live<01:00:51.040> if<01:00:51.200> you<01:00:51.280> want 01:00:51.670 --> 01:00:51.680 align:start position:0% i can i can just ask it live if you want 01:00:51.680 --> 01:00:54.950 align:start position:0% i can i can just ask it live if you want yeah<01:00:51.920> sure<01:00:52.079> yes<01:00:52.319> yeah<01:00:53.280> yeah<01:00:53.520> um<01:00:53.760> i<01:00:54.000> i<01:00:54.559> actually 01:00:54.950 --> 01:00:54.960 align:start position:0% yeah sure yes yeah yeah um i i actually 01:00:54.960 --> 01:00:56.470 align:start position:0% yeah sure yes yeah yeah um i i actually i<01:00:55.200> i<01:00:55.599> um 01:00:56.470 --> 01:00:56.480 align:start position:0% i i um 01:00:56.480 --> 01:00:58.789 align:start position:0% i i um i<01:00:56.559> think<01:00:56.720> it's<01:00:57.520> you<01:00:57.680> made<01:00:58.000> a<01:00:58.559> great 01:00:58.789 --> 01:00:58.799 align:start position:0% i think it's you made a great 01:00:58.799 --> 01:00:59.510 align:start position:0% i think it's you made a great introduction 01:00:59.510 --> 01:00:59.520 align:start position:0% introduction 01:00:59.520 --> 01:01:02.390 align:start position:0% introduction um<01:01:00.079> because<01:01:00.480> uh<01:01:00.640> one<01:01:00.799> thing<01:01:01.040> uh<01:01:01.200> where<01:01:01.440> i<01:01:01.760> also 01:01:02.390 --> 01:01:02.400 align:start position:0% um because uh one thing uh where i also 01:01:02.400 --> 01:01:02.950 align:start position:0% um because uh one thing uh where i also wrote 01:01:02.950 --> 01:01:02.960 align:start position:0% wrote 01:01:02.960 --> 01:01:04.870 align:start position:0% wrote it's<01:01:03.119> a<01:01:03.200> great<01:01:03.440> slide<01:01:03.839> um<01:01:04.400> where<01:01:04.559> you<01:01:04.720> could 01:01:04.870 --> 01:01:04.880 align:start position:0% it's a great slide um where you could 01:01:04.880 --> 01:01:06.150 align:start position:0% it's a great slide um where you could see<01:01:05.200> um 01:01:06.150 --> 01:01:06.160 align:start position:0% see um 01:01:06.160 --> 01:01:08.390 align:start position:0% see um a<01:01:06.559> calmness<01:01:07.119> which<01:01:07.440> more<01:01:07.599> or<01:01:07.680> less<01:01:08.000> takes<01:01:08.240> the 01:01:08.390 --> 01:01:08.400 align:start position:0% a calmness which more or less takes the 01:01:08.400 --> 01:01:10.150 align:start position:0% a calmness which more or less takes the whole<01:01:09.119> stack<01:01:09.599> from 01:01:10.150 --> 01:01:10.160 align:start position:0% whole stack from 01:01:10.160 --> 01:01:13.270 align:start position:0% whole stack from bare<01:01:10.400> metal<01:01:10.720> to<01:01:10.880> space<01:01:11.359> or 01:01:13.270 --> 01:01:13.280 align:start position:0% bare metal to space or 01:01:13.280 --> 01:01:16.390 align:start position:0% bare metal to space or um<01:01:14.079> you<01:01:14.240> can<01:01:14.480> you<01:01:14.559> can<01:01:14.720> work<01:01:14.960> on<01:01:15.200> on<01:01:15.359> the<01:01:16.160> in 01:01:16.390 --> 01:01:16.400 align:start position:0% um you can you can work on on the in 01:01:16.400 --> 01:01:17.270 align:start position:0% um you can you can work on on the in lisp<01:01:16.880> yeah 01:01:17.270 --> 01:01:17.280 align:start position:0% lisp yeah 01:01:17.280 --> 01:01:19.109 align:start position:0% lisp yeah you're<01:01:17.520> still<01:01:17.839> in<01:01:18.000> this<01:01:18.240> but<01:01:18.400> you<01:01:18.480> can<01:01:18.640> work<01:01:18.880> on 01:01:19.109 --> 01:01:19.119 align:start position:0% you're still in this but you can work on 01:01:19.119 --> 01:01:20.309 align:start position:0% you're still in this but you can work on the<01:01:19.280> nitty-gritty 01:01:20.309 --> 01:01:20.319 align:start position:0% the nitty-gritty 01:01:20.319 --> 01:01:23.109 align:start position:0% the nitty-gritty compiler<01:01:20.880> details<01:01:21.359> where<01:01:21.599> you<01:01:21.760> get<01:01:22.160> uh<01:01:22.960> i 01:01:23.109 --> 01:01:23.119 align:start position:0% compiler details where you get uh i 01:01:23.119 --> 01:01:23.670 align:start position:0% compiler details where you get uh i don't<01:01:23.280> know 01:01:23.670 --> 01:01:23.680 align:start position:0% don't know 01:01:23.680 --> 01:01:25.109 align:start position:0% don't know your<01:01:23.920> virtual<01:01:24.240> operations<01:01:24.799> into<01:01:25.040> the 01:01:25.109 --> 01:01:25.119 align:start position:0% your virtual operations into the 01:01:25.119 --> 01:01:27.270 align:start position:0% your virtual operations into the registers<01:01:25.680> of<01:01:25.760> your<01:01:26.079> of<01:01:26.160> your<01:01:26.400> processor 01:01:27.270 --> 01:01:27.280 align:start position:0% registers of your of your processor 01:01:27.280 --> 01:01:29.750 align:start position:0% registers of your of your processor uh<01:01:27.680> up<01:01:27.839> to<01:01:28.319> highest<01:01:28.720> abstractions<01:01:29.440> uh 01:01:29.750 --> 01:01:29.760 align:start position:0% uh up to highest abstractions uh 01:01:29.760 --> 01:01:30.950 align:start position:0% uh up to highest abstractions uh whatever 01:01:30.950 --> 01:01:30.960 align:start position:0% whatever 01:01:30.960 --> 01:01:32.789 align:start position:0% whatever and<01:01:31.119> it's<01:01:31.280> all<01:01:31.599> inside<01:01:31.920> of<01:01:32.000> list<01:01:32.400> and<01:01:32.480> there's 01:01:32.789 --> 01:01:32.799 align:start position:0% and it's all inside of list and there's 01:01:32.799 --> 01:01:34.069 align:start position:0% and it's all inside of list and there's also<01:01:33.119> um 01:01:34.069 --> 01:01:34.079 align:start position:0% also um 01:01:34.079 --> 01:01:37.510 align:start position:0% also um several<01:01:34.480> attempts<01:01:34.880> to<01:01:35.440> to<01:01:35.760> start<01:01:36.160> new 01:01:37.510 --> 01:01:37.520 align:start position:0% several attempts to to start new 01:01:37.520 --> 01:01:38.630 align:start position:0% several attempts to to start new common<01:01:37.839> lisp 01:01:38.630 --> 01:01:38.640 align:start position:0% common lisp 01:01:38.640 --> 01:01:42.069 align:start position:0% common lisp [Music] 01:01:42.069 --> 01:01:42.079 align:start position:0% [Music] 01:01:42.079 --> 01:01:44.710 align:start position:0% [Music] operating<01:01:42.559> systems<01:01:43.520> so<01:01:43.680> that<01:01:43.920> you<01:01:44.079> really<01:01:44.480> get 01:01:44.710 --> 01:01:44.720 align:start position:0% operating systems so that you really get 01:01:44.720 --> 01:01:45.430 align:start position:0% operating systems so that you really get from 01:01:45.430 --> 01:01:45.440 align:start position:0% from 01:01:45.440 --> 01:01:48.180 align:start position:0% from bare<01:01:45.680> metal<01:01:46.240> to<01:01:46.880> whatever 01:01:48.180 --> 01:01:48.190 align:start position:0% bare metal to whatever 01:01:48.190 --> 01:01:49.670 align:start position:0% bare metal to whatever [Music] 01:01:49.670 --> 01:01:49.680 align:start position:0% [Music] 01:01:49.680 --> 01:01:51.990 align:start position:0% [Music] the<01:01:50.079> most<01:01:50.319> recent<01:01:50.640> that<01:01:50.799> i'm<01:01:50.960> aware<01:01:51.200> of<01:01:51.440> is 01:01:51.990 --> 01:01:52.000 align:start position:0% the most recent that i'm aware of is 01:01:52.000 --> 01:01:52.789 align:start position:0% the most recent that i'm aware of is mezzano 01:01:52.789 --> 01:01:52.799 align:start position:0% mezzano 01:01:52.799 --> 01:01:55.349 align:start position:0% mezzano which<01:01:53.119> uh<01:01:53.680> seems<01:01:53.920> to<01:01:54.079> make<01:01:54.400> uh<01:01:54.799> some<01:01:54.960> progress 01:01:55.349 --> 01:01:55.359 align:start position:0% which uh seems to make uh some progress 01:01:55.359 --> 01:01:56.390 align:start position:0% which uh seems to make uh some progress recently 01:01:56.390 --> 01:01:56.400 align:start position:0% recently 01:01:56.400 --> 01:01:59.990 align:start position:0% recently um<01:01:57.839> what<01:01:58.400> uh<01:01:58.720> what<01:01:58.960> i<01:01:59.039> wanted<01:01:59.280> to<01:01:59.440> ask<01:01:59.680> actually 01:01:59.990 --> 01:02:00.000 align:start position:0% um what uh what i wanted to ask actually 01:02:00.000 --> 01:02:00.950 align:start position:0% um what uh what i wanted to ask actually was<01:02:00.240> um 01:02:00.950 --> 01:02:00.960 align:start position:0% was um 01:02:00.960 --> 01:02:04.069 align:start position:0% was um what<01:02:01.200> other<01:02:01.520> details<01:02:02.000> are<01:02:02.319> so<01:02:02.880> some<01:02:03.440> some 01:02:04.069 --> 01:02:04.079 align:start position:0% what other details are so some some 01:02:04.079 --> 01:02:06.789 align:start position:0% what other details are so some some features<01:02:04.640> something<01:02:05.039> like<01:02:05.359> uh<01:02:06.400> of<01:02:06.480> course<01:02:06.720> i 01:02:06.789 --> 01:02:06.799 align:start position:0% features something like uh of course i 01:02:06.799 --> 01:02:07.190 align:start position:0% features something like uh of course i have 01:02:07.190 --> 01:02:07.200 align:start position:0% have 01:02:07.200 --> 01:02:10.309 align:start position:0% have some<01:02:07.359> ideas<01:02:07.760> about<01:02:08.000> that<01:02:08.160> but<01:02:08.400> um<01:02:09.119> um<01:02:09.680> what<01:02:09.920> you 01:02:10.309 --> 01:02:10.319 align:start position:0% some ideas about that but um um what you 01:02:10.319 --> 01:02:11.029 align:start position:0% some ideas about that but um um what you think<01:02:10.640> um 01:02:11.029 --> 01:02:11.039 align:start position:0% think um 01:02:11.039 --> 01:02:13.829 align:start position:0% think um makes<01:02:11.520> common<01:02:11.920> list<01:02:12.319> um<01:02:13.200> what<01:02:13.359> do<01:02:13.440> you<01:02:13.599> miss 01:02:13.829 --> 01:02:13.839 align:start position:0% makes common list um what do you miss 01:02:13.839 --> 01:02:17.109 align:start position:0% makes common list um what do you miss and<01:02:13.920> closure<01:02:14.400> what<01:02:14.559> commonness<01:02:15.119> pass 01:02:17.109 --> 01:02:17.119 align:start position:0% and closure what commonness pass 01:02:17.119 --> 01:02:20.470 align:start position:0% and closure what commonness pass well<01:02:18.000> i'm<01:02:18.160> not<01:02:18.400> sure<01:02:18.559> i'm<01:02:19.599> i<01:02:19.760> don't<01:02:19.920> know<01:02:20.079> if<01:02:20.240> i 01:02:20.470 --> 01:02:20.480 align:start position:0% well i'm not sure i'm i don't know if i 01:02:20.480 --> 01:02:21.029 align:start position:0% well i'm not sure i'm i don't know if i miss<01:02:20.720> it 01:02:21.029 --> 01:02:21.039 align:start position:0% miss it 01:02:21.039 --> 01:02:25.109 align:start position:0% miss it but<01:02:21.280> i'm<01:02:21.440> certainly<01:02:22.160> aware<01:02:22.559> of<01:02:22.720> it<01:02:23.440> is 01:02:25.109 --> 01:02:25.119 align:start position:0% but i'm certainly aware of it is 01:02:25.119 --> 01:02:28.470 align:start position:0% but i'm certainly aware of it is the<01:02:25.359> rebel<01:02:26.480> situation<01:02:27.760> in<01:02:27.839> these<01:02:28.079> two 01:02:28.470 --> 01:02:28.480 align:start position:0% the rebel situation in these two 01:02:28.480 --> 01:02:31.829 align:start position:0% the rebel situation in these two things<01:02:29.520> um<01:02:30.640> i<01:02:30.880> i<01:02:31.039> should<01:02:31.280> have<01:02:31.359> had<01:02:31.440> a<01:02:31.520> slide 01:02:31.829 --> 01:02:31.839 align:start position:0% things um i i should have had a slide 01:02:31.839 --> 01:02:32.390 align:start position:0% things um i i should have had a slide for<01:02:32.000> this 01:02:32.390 --> 01:02:32.400 align:start position:0% for this 01:02:32.400 --> 01:02:34.470 align:start position:0% for this it's<01:02:32.640> an<01:02:32.799> important<01:02:33.119> point<01:02:33.520> which<01:02:33.760> is<01:02:33.920> both<01:02:34.319> of 01:02:34.470 --> 01:02:34.480 align:start position:0% it's an important point which is both of 01:02:34.480 --> 01:02:37.190 align:start position:0% it's an important point which is both of these<01:02:34.799> languages<01:02:35.359> are<01:02:35.440> very<01:02:35.680> rebel<01:02:36.079> focused 01:02:37.190 --> 01:02:37.200 align:start position:0% these languages are very rebel focused 01:02:37.200 --> 01:02:39.750 align:start position:0% these languages are very rebel focused and<01:02:37.359> what<01:02:37.520> i<01:02:37.680> mean<01:02:37.839> by<01:02:38.000> that<01:02:38.240> is<01:02:39.440> everything 01:02:39.750 --> 01:02:39.760 align:start position:0% and what i mean by that is everything 01:02:39.760 --> 01:02:41.109 align:start position:0% and what i mean by that is everything about<01:02:40.000> the<01:02:40.160> language<01:02:40.559> supports 01:02:41.109 --> 01:02:41.119 align:start position:0% about the language supports 01:02:41.119 --> 01:02:43.910 align:start position:0% about the language supports interactive<01:02:41.599> development<01:02:42.960> and<01:02:43.359> everything 01:02:43.910 --> 01:02:43.920 align:start position:0% interactive development and everything 01:02:43.920 --> 01:02:44.309 align:start position:0% interactive development and everything about 01:02:44.309 --> 01:02:44.319 align:start position:0% about 01:02:44.319 --> 01:02:47.349 align:start position:0% about compilation<01:02:45.039> and<01:02:45.200> delivery<01:02:46.400> it<01:02:46.640> accounts<01:02:47.119> for 01:02:47.349 --> 01:02:47.359 align:start position:0% compilation and delivery it accounts for 01:02:47.359 --> 01:02:49.190 align:start position:0% compilation and delivery it accounts for and<01:02:47.599> admits 01:02:49.190 --> 01:02:49.200 align:start position:0% and admits 01:02:49.200 --> 01:02:52.470 align:start position:0% and admits it<01:02:49.359> allows<01:02:49.839> for<01:02:50.400> interactive<01:02:50.880> development<01:02:52.079> so 01:02:52.470 --> 01:02:52.480 align:start position:0% it allows for interactive development so 01:02:52.480 --> 01:02:54.390 align:start position:0% it allows for interactive development so there's<01:02:52.799> a<01:02:52.880> strict<01:02:53.200> concept<01:02:53.599> of<01:02:53.760> a<01:02:53.839> top<01:02:54.079> level 01:02:54.390 --> 01:02:54.400 align:start position:0% there's a strict concept of a top level 01:02:54.400 --> 01:02:56.069 align:start position:0% there's a strict concept of a top level form<01:02:54.799> in<01:02:54.880> both<01:02:55.119> of<01:02:55.200> these<01:02:55.359> languages 01:02:56.069 --> 01:02:56.079 align:start position:0% form in both of these languages 01:02:56.079 --> 01:02:58.069 align:start position:0% form in both of these languages and<01:02:56.400> the<01:02:56.559> semantics<01:02:57.119> of<01:02:57.200> the<01:02:57.280> top<01:02:57.520> level<01:02:57.760> form 01:02:58.069 --> 01:02:58.079 align:start position:0% and the semantics of the top level form 01:02:58.079 --> 01:02:59.190 align:start position:0% and the semantics of the top level form are<01:02:58.160> the<01:02:58.319> same<01:02:58.640> whether<01:02:58.880> you're 01:02:59.190 --> 01:02:59.200 align:start position:0% are the same whether you're 01:02:59.200 --> 01:03:00.309 align:start position:0% are the same whether you're pre-compiling 01:03:00.309 --> 01:03:00.319 align:start position:0% pre-compiling 01:03:00.319 --> 01:03:02.789 align:start position:0% pre-compiling or<01:03:00.640> whether<01:03:00.880> you're<01:03:01.359> interpreting<01:03:02.640> or 01:03:02.789 --> 01:03:02.799 align:start position:0% or whether you're interpreting or 01:03:02.799 --> 01:03:03.430 align:start position:0% or whether you're interpreting or whatever 01:03:03.430 --> 01:03:03.440 align:start position:0% whatever 01:03:03.440 --> 01:03:06.549 align:start position:0% whatever and<01:03:03.520> this<01:03:03.760> is<01:03:03.839> kind<01:03:04.000> of<01:03:04.160> subtle<01:03:05.359> um 01:03:06.549 --> 01:03:06.559 align:start position:0% and this is kind of subtle um 01:03:06.559 --> 01:03:08.549 align:start position:0% and this is kind of subtle um but<01:03:07.359> i<01:03:07.440> think<01:03:07.599> it's<01:03:07.760> a<01:03:07.920> property<01:03:08.400> of<01:03:08.480> the 01:03:08.549 --> 01:03:08.559 align:start position:0% but i think it's a property of the 01:03:08.559 --> 01:03:09.670 align:start position:0% but i think it's a property of the language<01:03:09.119> that 01:03:09.670 --> 01:03:09.680 align:start position:0% language that 01:03:09.680 --> 01:03:11.670 align:start position:0% language that we<01:03:09.920> take<01:03:10.160> for<01:03:10.400> granted<01:03:10.960> that<01:03:11.200> actually<01:03:11.520> very 01:03:11.670 --> 01:03:11.680 align:start position:0% we take for granted that actually very 01:03:11.680 --> 01:03:13.190 align:start position:0% we take for granted that actually very few<01:03:11.839> languages<01:03:12.240> have<01:03:12.480> which<01:03:12.720> is<01:03:12.880> such<01:03:13.119> a 01:03:13.190 --> 01:03:13.200 align:start position:0% few languages have which is such a 01:03:13.200 --> 01:03:19.750 align:start position:0% few languages have which is such a low-level<01:03:13.599> compilation<01:03:14.240> unit 01:03:19.750 --> 01:03:19.760 align:start position:0% 01:03:19.760 --> 01:03:22.870 align:start position:0% the<01:03:20.400> trade-off<01:03:20.880> here<01:03:21.359> is 01:03:22.870 --> 01:03:22.880 align:start position:0% the trade-off here is 01:03:22.880 --> 01:03:25.349 align:start position:0% the trade-off here is rich<01:03:23.119> has<01:03:23.280> spoken<01:03:23.520> to<01:03:23.680> this<01:03:24.240> point<01:03:24.720> in<01:03:25.039> hacker 01:03:25.349 --> 01:03:25.359 align:start position:0% rich has spoken to this point in hacker 01:03:25.359 --> 01:03:26.309 align:start position:0% rich has spoken to this point in hacker news<01:03:25.599> threats 01:03:26.309 --> 01:03:26.319 align:start position:0% news threats 01:03:26.319 --> 01:03:28.789 align:start position:0% news threats about<01:03:26.720> single<01:03:27.039> pass<01:03:27.280> versus<01:03:27.680> multi-pass<01:03:28.640> and 01:03:28.789 --> 01:03:28.799 align:start position:0% about single pass versus multi-pass and 01:03:28.799 --> 01:03:29.589 align:start position:0% about single pass versus multi-pass and so 01:03:29.589 --> 01:03:29.599 align:start position:0% so 01:03:29.599 --> 01:03:31.510 align:start position:0% so lisp<01:03:29.920> compilers<01:03:30.720> have<01:03:30.880> always<01:03:31.039> been<01:03:31.200> single 01:03:31.510 --> 01:03:31.520 align:start position:0% lisp compilers have always been single 01:03:31.520 --> 01:03:33.190 align:start position:0% lisp compilers have always been single pass<01:03:31.839> in<01:03:31.920> the<01:03:32.079> sense<01:03:32.319> that<01:03:32.400> you<01:03:32.559> feed<01:03:32.799> the 01:03:33.190 --> 01:03:33.200 align:start position:0% pass in the sense that you feed the 01:03:33.200 --> 01:03:36.789 align:start position:0% pass in the sense that you feed the top<01:03:33.440> level<01:03:33.680> forms<01:03:34.079> in<01:03:34.799> and<01:03:35.359> you<01:03:36.000> accumulate 01:03:36.789 --> 01:03:36.799 align:start position:0% top level forms in and you accumulate 01:03:36.799 --> 01:03:39.109 align:start position:0% top level forms in and you accumulate a<01:03:36.960> lisp<01:03:37.280> image<01:03:37.920> inside<01:03:38.240> the<01:03:38.319> computer<01:03:38.799> so<01:03:38.960> what 01:03:39.109 --> 01:03:39.119 align:start position:0% a lisp image inside the computer so what 01:03:39.119 --> 01:03:40.470 align:start position:0% a lisp image inside the computer so what you're<01:03:39.200> doing<01:03:39.520> is<01:03:39.599> you're 01:03:40.470 --> 01:03:40.480 align:start position:0% you're doing is you're 01:03:40.480 --> 01:03:43.990 align:start position:0% you're doing is you're contributing<01:03:41.440> code<01:03:42.079> to<01:03:43.200> a<01:03:43.280> stable 01:03:43.990 --> 01:03:44.000 align:start position:0% contributing code to a stable 01:03:44.000 --> 01:03:47.190 align:start position:0% contributing code to a stable identity<01:03:44.559> which<01:03:44.799> is<01:03:45.280> the<01:03:45.760> lisp<01:03:46.160> image<01:03:46.960> and<01:03:47.119> you 01:03:47.190 --> 01:03:47.200 align:start position:0% identity which is the lisp image and you 01:03:47.200 --> 01:03:49.190 align:start position:0% identity which is the lisp image and you have<01:03:47.280> certain<01:03:47.599> assurances<01:03:48.240> like 01:03:49.190 --> 01:03:49.200 align:start position:0% have certain assurances like 01:03:49.200 --> 01:03:52.309 align:start position:0% have certain assurances like if<01:03:50.160> loading<01:03:50.720> a<01:03:50.880> top-level<01:03:51.359> form<01:03:51.680> fails<01:03:52.079> your 01:03:52.309 --> 01:03:52.319 align:start position:0% if loading a top-level form fails your 01:03:52.319 --> 01:03:54.230 align:start position:0% if loading a top-level form fails your image<01:03:52.559> isn't<01:03:52.799> corrupt<01:03:53.200> for<01:03:53.359> example<01:03:53.839> so<01:03:54.000> it's 01:03:54.230 --> 01:03:54.240 align:start position:0% image isn't corrupt for example so it's 01:03:54.240 --> 01:03:58.630 align:start position:0% image isn't corrupt for example so it's like<01:03:54.400> a<01:03:54.920> transaction<01:03:56.839> um 01:03:58.630 --> 01:03:58.640 align:start position:0% like a transaction um 01:03:58.640 --> 01:04:00.150 align:start position:0% like a transaction um so<01:03:58.880> both<01:03:59.039> of<01:03:59.200> the<01:03:59.280> languages<01:03:59.680> have<01:03:59.920> that<01:04:00.079> in 01:04:00.150 --> 01:04:00.160 align:start position:0% so both of the languages have that in 01:04:00.160 --> 01:04:01.990 align:start position:0% so both of the languages have that in common<01:04:00.720> and<01:04:01.599> this 01:04:01.990 --> 01:04:02.000 align:start position:0% common and this 01:04:02.000 --> 01:04:05.270 align:start position:0% common and this is<01:04:02.240> different<01:04:02.799> from<01:04:04.480> languages<01:04:05.039> in<01:04:05.119> the 01:04:05.270 --> 01:04:05.280 align:start position:0% is different from languages in the 01:04:05.280 --> 01:04:05.750 align:start position:0% is different from languages in the scheme 01:04:05.750 --> 01:04:05.760 align:start position:0% scheme 01:04:05.760 --> 01:04:09.510 align:start position:0% scheme tradition<01:04:07.200> um<01:04:08.079> which 01:04:09.510 --> 01:04:09.520 align:start position:0% tradition um which 01:04:09.520 --> 01:04:11.750 align:start position:0% tradition um which have<01:04:10.480> broadly<01:04:10.960> speaking<01:04:11.359> and<01:04:11.440> this<01:04:11.599> is<01:04:11.680> a 01:04:11.750 --> 01:04:11.760 align:start position:0% have broadly speaking and this is a 01:04:11.760 --> 01:04:13.109 align:start position:0% have broadly speaking and this is a generalization<01:04:12.319> that<01:04:12.480> i'm<01:04:12.559> not<01:04:12.720> a<01:04:12.880> scheme 01:04:13.109 --> 01:04:13.119 align:start position:0% generalization that i'm not a scheme 01:04:13.119 --> 01:04:15.190 align:start position:0% generalization that i'm not a scheme expert<01:04:13.440> so<01:04:13.599> feel<01:04:13.760> free<01:04:13.920> to<01:04:14.079> correct<01:04:14.240> me<01:04:14.480> but 01:04:15.190 --> 01:04:15.200 align:start position:0% expert so feel free to correct me but 01:04:15.200 --> 01:04:16.230 align:start position:0% expert so feel free to correct me but one<01:04:15.359> of<01:04:15.440> the<01:04:15.520> things<01:04:15.760> that<01:04:15.839> you<01:04:15.920> have<01:04:16.160> in 01:04:16.230 --> 01:04:16.240 align:start position:0% one of the things that you have in 01:04:16.240 --> 01:04:18.230 align:start position:0% one of the things that you have in common<01:04:16.559> lisp<01:04:16.799> enclosure<01:04:17.359> are<01:04:17.680> first<01:04:17.920> class 01:04:18.230 --> 01:04:18.240 align:start position:0% common lisp enclosure are first class 01:04:18.240 --> 01:04:20.069 align:start position:0% common lisp enclosure are first class packages<01:04:18.640> or<01:04:18.720> name<01:04:18.960> spaces 01:04:20.069 --> 01:04:20.079 align:start position:0% packages or name spaces 01:04:20.079 --> 01:04:21.910 align:start position:0% packages or name spaces so<01:04:20.240> that<01:04:20.480> lisp<01:04:20.799> image<01:04:21.039> you're<01:04:21.200> building<01:04:21.599> up 01:04:21.910 --> 01:04:21.920 align:start position:0% so that lisp image you're building up 01:04:21.920 --> 01:04:23.109 align:start position:0% so that lisp image you're building up it's<01:04:22.079> introspectible 01:04:23.109 --> 01:04:23.119 align:start position:0% it's introspectible 01:04:23.119 --> 01:04:26.069 align:start position:0% it's introspectible and<01:04:23.359> there<01:04:23.520> are<01:04:24.000> well<01:04:24.240> there<01:04:24.400> are<01:04:24.720> you<01:04:24.839> know 01:04:26.069 --> 01:04:26.079 align:start position:0% and there are well there are you know 01:04:26.079 --> 01:04:26.630 align:start position:0% and there are well there are you know public 01:04:26.630 --> 01:04:26.640 align:start position:0% public 01:04:26.640 --> 01:04:28.470 align:start position:0% public entry<01:04:26.960> points<01:04:27.359> into<01:04:27.680> the<01:04:27.839> database<01:04:28.319> of 01:04:28.470 --> 01:04:28.480 align:start position:0% entry points into the database of 01:04:28.480 --> 01:04:31.029 align:start position:0% entry points into the database of information<01:04:28.960> contained<01:04:29.440> in<01:04:29.520> the<01:04:29.599> lisp<01:04:29.920> image 01:04:31.029 --> 01:04:31.039 align:start position:0% information contained in the lisp image 01:04:31.039 --> 01:04:33.910 align:start position:0% information contained in the lisp image and<01:04:32.559> that's<01:04:32.799> accessible<01:04:33.200> from<01:04:33.359> the<01:04:33.440> reppl 01:04:33.910 --> 01:04:33.920 align:start position:0% and that's accessible from the reppl 01:04:33.920 --> 01:04:35.430 align:start position:0% and that's accessible from the reppl using<01:04:34.319> various<01:04:34.640> functions<01:04:35.039> for<01:04:35.200> looking<01:04:35.359> at 01:04:35.430 --> 01:04:35.440 align:start position:0% using various functions for looking at 01:04:35.440 --> 01:04:37.349 align:start position:0% using various functions for looking at documentation 01:04:37.349 --> 01:04:37.359 align:start position:0% documentation 01:04:37.359 --> 01:04:39.990 align:start position:0% documentation there<01:04:37.599> are<01:04:38.400> third<01:04:38.640> party<01:04:39.039> programs<01:04:39.520> like<01:04:39.680> list 01:04:39.990 --> 01:04:40.000 align:start position:0% there are third party programs like list 01:04:40.000 --> 01:04:42.710 align:start position:0% there are third party programs like list works<01:04:40.319> that<01:04:40.480> give<01:04:40.640> you<01:04:40.799> uis<01:04:41.280> on<01:04:41.359> top<01:04:41.599> of<01:04:41.680> that 01:04:42.710 --> 01:04:42.720 align:start position:0% works that give you uis on top of that 01:04:42.720 --> 01:04:45.829 align:start position:0% works that give you uis on top of that um<01:04:43.119> and<01:04:43.359> in<01:04:43.520> in<01:04:43.680> common<01:04:44.000> lists<01:04:44.480> the<01:04:45.520> probably 01:04:45.829 --> 01:04:45.839 align:start position:0% um and in in common lists the probably 01:04:45.839 --> 01:04:47.430 align:start position:0% um and in in common lists the probably the<01:04:46.000> most<01:04:46.160> popular<01:04:46.559> or<01:04:46.640> third<01:04:46.799> party<01:04:47.039> ui<01:04:47.280> is 01:04:47.430 --> 01:04:47.440 align:start position:0% the most popular or third party ui is 01:04:47.440 --> 01:04:48.230 align:start position:0% the most popular or third party ui is list<01:04:47.680> works 01:04:48.230 --> 01:04:48.240 align:start position:0% list works 01:04:48.240 --> 01:04:50.630 align:start position:0% list works but<01:04:48.400> there<01:04:48.559> are<01:04:48.640> other<01:04:48.799> ones<01:04:49.680> uh<01:04:50.000> and<01:04:50.160> then<01:04:50.400> in 01:04:50.630 --> 01:04:50.640 align:start position:0% but there are other ones uh and then in 01:04:50.640 --> 01:04:52.870 align:start position:0% but there are other ones uh and then in closure<01:04:51.119> maybe<01:04:51.520> rebel 01:04:52.870 --> 01:04:52.880 align:start position:0% closure maybe rebel 01:04:52.880 --> 01:04:58.950 align:start position:0% closure maybe rebel is<01:04:54.079> um<01:04:55.280> analogous 01:04:58.950 --> 01:04:58.960 align:start position:0% 01:04:58.960 --> 01:05:01.109 align:start position:0% so<01:04:59.200> those<01:04:59.359> are<01:04:59.440> the<01:04:59.520> ways<01:04:59.680> that<01:05:00.000> the<01:05:00.160> same<01:05:00.880> one 01:05:01.109 --> 01:05:01.119 align:start position:0% so those are the ways that the same one 01:05:01.119 --> 01:05:02.470 align:start position:0% so those are the ways that the same one way<01:05:01.359> that<01:05:01.520> they're<01:05:01.760> different 01:05:02.470 --> 01:05:02.480 align:start position:0% way that they're different 01:05:02.480 --> 01:05:05.910 align:start position:0% way that they're different is<01:05:02.640> in<01:05:02.799> terms<01:05:03.119> of<01:05:03.200> the<01:05:03.359> platform 01:05:05.910 --> 01:05:05.920 align:start position:0% is in terms of the platform 01:05:05.920 --> 01:05:08.789 align:start position:0% is in terms of the platform trade-off<01:05:07.039> so<01:05:07.359> in<01:05:07.440> common<01:05:07.760> lisp<01:05:08.480> when<01:05:08.640> you're 01:05:08.789 --> 01:05:08.799 align:start position:0% trade-off so in common lisp when you're 01:05:08.799 --> 01:05:10.069 align:start position:0% trade-off so in common lisp when you're at<01:05:08.880> the<01:05:08.960> reppel 01:05:10.069 --> 01:05:10.079 align:start position:0% at the reppel 01:05:10.079 --> 01:05:12.390 align:start position:0% at the reppel um<01:05:10.720> there's<01:05:10.960> a<01:05:11.039> can<01:05:11.200> there's<01:05:11.440> a<01:05:11.680> sophisticated 01:05:12.390 --> 01:05:12.400 align:start position:0% um there's a can there's a sophisticated 01:05:12.400 --> 01:05:14.230 align:start position:0% um there's a can there's a sophisticated error<01:05:12.640> handling<01:05:13.039> system<01:05:13.280> called<01:05:13.520> conditions 01:05:14.230 --> 01:05:14.240 align:start position:0% error handling system called conditions 01:05:14.240 --> 01:05:16.069 align:start position:0% error handling system called conditions and<01:05:14.400> there's<01:05:14.640> also<01:05:15.039> a<01:05:15.280> traditional<01:05:15.760> idea<01:05:16.000> of 01:05:16.069 --> 01:05:16.079 align:start position:0% and there's also a traditional idea of 01:05:16.079 --> 01:05:17.430 align:start position:0% and there's also a traditional idea of what<01:05:16.160> a<01:05:16.240> debugger<01:05:16.799> can<01:05:16.960> do 01:05:17.430 --> 01:05:17.440 align:start position:0% what a debugger can do 01:05:17.440 --> 01:05:19.670 align:start position:0% what a debugger can do and<01:05:17.520> one<01:05:17.680> of<01:05:17.760> the<01:05:17.839> things<01:05:18.079> that<01:05:18.559> the<01:05:18.720> average 01:05:19.670 --> 01:05:19.680 align:start position:0% and one of the things that the average 01:05:19.680 --> 01:05:21.190 align:start position:0% and one of the things that the average common<01:05:20.000> list<01:05:20.240> debugger<01:05:20.720> can<01:05:20.880> do 01:05:21.190 --> 01:05:21.200 align:start position:0% common list debugger can do 01:05:21.200 --> 01:05:24.470 align:start position:0% common list debugger can do is<01:05:22.160> give<01:05:22.319> you<01:05:22.559> a<01:05:22.720> lisp<01:05:23.119> rebel<01:05:23.680> at<01:05:23.920> a<01:05:24.079> place<01:05:24.400> in 01:05:24.470 --> 01:05:24.480 align:start position:0% is give you a lisp rebel at a place in 01:05:24.480 --> 01:05:26.230 align:start position:0% is give you a lisp rebel at a place in the<01:05:24.559> call<01:05:24.799> stack 01:05:26.230 --> 01:05:26.240 align:start position:0% the call stack 01:05:26.240 --> 01:05:28.150 align:start position:0% the call stack so<01:05:26.960> like<01:05:27.200> if<01:05:27.280> you<01:05:27.520> it<01:05:27.599> would<01:05:27.680> be<01:05:27.760> like<01:05:27.920> if<01:05:28.079> you 01:05:28.150 --> 01:05:28.160 align:start position:0% so like if you it would be like if you 01:05:28.160 --> 01:05:30.309 align:start position:0% so like if you it would be like if you throw<01:05:28.319> an<01:05:28.400> exception<01:05:28.799> in<01:05:28.960> java 01:05:30.309 --> 01:05:30.319 align:start position:0% throw an exception in java 01:05:30.319 --> 01:05:32.710 align:start position:0% throw an exception in java and<01:05:30.720> instead<01:05:31.039> of<01:05:31.599> the<01:05:31.680> stack<01:05:32.079> unwinding<01:05:32.559> and 01:05:32.710 --> 01:05:32.720 align:start position:0% and instead of the stack unwinding and 01:05:32.720 --> 01:05:34.710 align:start position:0% and instead of the stack unwinding and you're<01:05:32.799> seeing<01:05:33.039> a<01:05:33.119> stack<01:05:33.440> trace 01:05:34.710 --> 01:05:34.720 align:start position:0% you're seeing a stack trace 01:05:34.720 --> 01:05:36.630 align:start position:0% you're seeing a stack trace execution<01:05:35.280> can<01:05:35.440> actually<01:05:35.680> be<01:05:35.920> suspended<01:05:36.480> in 01:05:36.630 --> 01:05:36.640 align:start position:0% execution can actually be suspended in 01:05:36.640 --> 01:05:38.549 align:start position:0% execution can actually be suspended in common<01:05:36.960> lisp<01:05:37.280> and<01:05:37.440> you<01:05:37.520> can<01:05:37.680> have<01:05:37.839> a<01:05:38.000> reply<01:05:38.400> at 01:05:38.549 --> 01:05:38.559 align:start position:0% common lisp and you can have a reply at 01:05:38.559 --> 01:05:40.069 align:start position:0% common lisp and you can have a reply at the<01:05:38.720> place<01:05:38.960> where<01:05:39.119> the<01:05:39.200> exception<01:05:39.599> was<01:05:39.760> thrown 01:05:40.069 --> 01:05:40.079 align:start position:0% the place where the exception was thrown 01:05:40.079 --> 01:05:40.630 align:start position:0% the place where the exception was thrown so<01:05:40.240> you<01:05:40.319> can 01:05:40.630 --> 01:05:40.640 align:start position:0% so you can 01:05:40.640 --> 01:05:42.549 align:start position:0% so you can inspect<01:05:40.960> local<01:05:41.280> variables<01:05:41.920> you<01:05:42.079> can<01:05:42.319> write 01:05:42.549 --> 01:05:42.559 align:start position:0% inspect local variables you can write 01:05:42.559 --> 01:05:44.950 align:start position:0% inspect local variables you can write new<01:05:42.720> code<01:05:42.960> that<01:05:43.039> gets<01:05:43.280> run<01:05:43.520> in<01:05:43.599> that<01:05:43.839> same 01:05:44.950 --> 01:05:44.960 align:start position:0% new code that gets run in that same 01:05:44.960 --> 01:05:49.670 align:start position:0% new code that gets run in that same stack<01:05:45.520> context 01:05:49.670 --> 01:05:49.680 align:start position:0% 01:05:49.680 --> 01:05:52.549 align:start position:0% which<01:05:49.920> is<01:05:50.000> pretty<01:05:50.160> cool<01:05:51.280> it's<01:05:51.440> pretty<01:05:51.680> cool 01:05:52.549 --> 01:05:52.559 align:start position:0% which is pretty cool it's pretty cool 01:05:52.559 --> 01:05:54.710 align:start position:0% which is pretty cool it's pretty cool and<01:05:52.960> it's<01:05:53.280> i<01:05:53.440> think<01:05:53.680> it's<01:05:53.839> still<01:05:54.079> unique 01:05:54.710 --> 01:05:54.720 align:start position:0% and it's i think it's still unique 01:05:54.720 --> 01:05:57.190 align:start position:0% and it's i think it's still unique among<01:05:55.119> languages<01:05:56.160> closure<01:05:56.640> does<01:05:56.799> not<01:05:56.960> have 01:05:57.190 --> 01:05:57.200 align:start position:0% among languages closure does not have 01:05:57.200 --> 01:05:58.789 align:start position:0% among languages closure does not have that<01:05:57.440> you<01:05:57.520> know<01:05:57.680> we<01:05:57.760> have<01:05:57.920> java<01:05:58.319> stacked<01:05:58.720> we 01:05:58.789 --> 01:05:58.799 align:start position:0% that you know we have java stacked we 01:05:58.799 --> 01:06:00.470 align:start position:0% that you know we have java stacked we have<01:05:58.960> java<01:05:59.280> exception<01:05:59.680> semantics 01:06:00.470 --> 01:06:00.480 align:start position:0% have java exception semantics 01:06:00.480 --> 01:06:04.309 align:start position:0% have java exception semantics and<01:06:00.640> java<01:06:00.960> stack<01:06:01.200> traces<01:06:02.839> um<01:06:03.839> and 01:06:04.309 --> 01:06:04.319 align:start position:0% and java stack traces um and 01:06:04.319 --> 01:06:05.750 align:start position:0% and java stack traces um and at<01:06:04.480> one<01:06:04.640> point<01:06:04.880> when<01:06:05.039> i<01:06:05.119> was<01:06:05.200> learning<01:06:05.520> common 01:06:05.750 --> 01:06:05.760 align:start position:0% at one point when i was learning common 01:06:05.760 --> 01:06:08.230 align:start position:0% at one point when i was learning common list<01:06:06.000> i<01:06:06.160> reflected<01:06:06.640> on<01:06:06.880> why 01:06:08.230 --> 01:06:08.240 align:start position:0% list i reflected on why 01:06:08.240 --> 01:06:10.789 align:start position:0% list i reflected on why i<01:06:08.400> didn't<01:06:08.960> really<01:06:09.760> even<01:06:10.000> once<01:06:10.240> i<01:06:10.400> knew<01:06:10.640> about 01:06:10.789 --> 01:06:10.799 align:start position:0% i didn't really even once i knew about 01:06:10.799 --> 01:06:12.630 align:start position:0% i didn't really even once i knew about the<01:06:10.960> common<01:06:11.280> lisp<01:06:11.520> way<01:06:11.760> why<01:06:11.920> i<01:06:12.000> didn't<01:06:12.319> miss<01:06:12.480> it 01:06:12.630 --> 01:06:12.640 align:start position:0% the common lisp way why i didn't miss it 01:06:12.640 --> 01:06:13.670 align:start position:0% the common lisp way why i didn't miss it in<01:06:12.720> closure 01:06:13.670 --> 01:06:13.680 align:start position:0% in closure 01:06:13.680 --> 01:06:14.789 align:start position:0% in closure and<01:06:13.839> the<01:06:13.920> best<01:06:14.160> i<01:06:14.319> could<01:06:14.400> come<01:06:14.559> to<01:06:14.720> an 01:06:14.789 --> 01:06:14.799 align:start position:0% and the best i could come to an 01:06:14.799 --> 01:06:17.190 align:start position:0% and the best i could come to an explanation<01:06:15.440> was<01:06:16.319> the<01:06:16.480> most<01:06:16.720> of<01:06:16.799> the<01:06:16.880> closure 01:06:17.190 --> 01:06:17.200 align:start position:0% explanation was the most of the closure 01:06:17.200 --> 01:06:18.390 align:start position:0% explanation was the most of the closure programs<01:06:17.599> i<01:06:17.680> was<01:06:17.839> writing 01:06:18.390 --> 01:06:18.400 align:start position:0% programs i was writing 01:06:18.400 --> 01:06:19.829 align:start position:0% programs i was writing kept<01:06:18.640> their<01:06:18.880> important<01:06:19.280> state<01:06:19.599> in<01:06:19.680> the 01:06:19.829 --> 01:06:19.839 align:start position:0% kept their important state in the 01:06:19.839 --> 01:06:21.510 align:start position:0% kept their important state in the database<01:06:20.400> so<01:06:20.559> i<01:06:20.640> was<01:06:20.720> writing<01:06:20.960> mostly<01:06:21.280> web 01:06:21.510 --> 01:06:21.520 align:start position:0% database so i was writing mostly web 01:06:21.520 --> 01:06:22.309 align:start position:0% database so i was writing mostly web applications 01:06:22.309 --> 01:06:22.319 align:start position:0% applications 01:06:22.319 --> 01:06:24.309 align:start position:0% applications or<01:06:22.880> writing<01:06:23.200> applications<01:06:23.680> that<01:06:23.839> interacted 01:06:24.309 --> 01:06:24.319 align:start position:0% or writing applications that interacted 01:06:24.319 --> 01:06:26.470 align:start position:0% or writing applications that interacted with<01:06:24.960> services 01:06:26.470 --> 01:06:26.480 align:start position:0% with services 01:06:26.480 --> 01:06:29.109 align:start position:0% with services and<01:06:26.720> so<01:06:27.359> if<01:06:27.520> i<01:06:27.680> needed<01:06:27.920> to<01:06:28.000> restart<01:06:28.400> my<01:06:28.559> jvm<01:06:29.039> it 01:06:29.109 --> 01:06:29.119 align:start position:0% and so if i needed to restart my jvm it 01:06:29.119 --> 01:06:30.630 align:start position:0% and so if i needed to restart my jvm it was<01:06:29.200> a<01:06:29.280> bit<01:06:29.440> of<01:06:29.599> a<01:06:29.680> pain<01:06:30.079> but<01:06:30.240> it<01:06:30.319> wasn't<01:06:30.559> the 01:06:30.630 --> 01:06:30.640 align:start position:0% was a bit of a pain but it wasn't the 01:06:30.640 --> 01:06:32.150 align:start position:0% was a bit of a pain but it wasn't the end<01:06:30.720> of<01:06:30.880> the<01:06:30.960> world<01:06:31.280> it's<01:06:31.359> not<01:06:31.520> like<01:06:31.680> my<01:06:31.920> data 01:06:32.150 --> 01:06:32.160 align:start position:0% end of the world it's not like my data 01:06:32.160 --> 01:06:34.150 align:start position:0% end of the world it's not like my data of<01:06:32.319> record<01:06:32.720> was<01:06:32.960> in<01:06:33.039> the<01:06:33.200> heap 01:06:34.150 --> 01:06:34.160 align:start position:0% of record was in the heap 01:06:34.160 --> 01:06:36.390 align:start position:0% of record was in the heap and<01:06:34.720> turning<01:06:35.039> off<01:06:35.200> the<01:06:35.359> jbm<01:06:36.000> was<01:06:36.160> going<01:06:36.319> to 01:06:36.390 --> 01:06:36.400 align:start position:0% and turning off the jbm was going to 01:06:36.400 --> 01:06:38.950 align:start position:0% and turning off the jbm was going to ruin<01:06:36.640> my<01:06:36.799> day 01:06:38.950 --> 01:06:38.960 align:start position:0% ruin my day 01:06:38.960 --> 01:06:41.829 align:start position:0% ruin my day 20<01:06:39.280> or<01:06:39.359> 30<01:06:39.599> years<01:06:39.839> ago<01:06:40.640> when<01:06:41.200> lisp<01:06:41.520> machines 01:06:41.829 --> 01:06:41.839 align:start position:0% 20 or 30 years ago when lisp machines 01:06:41.839 --> 01:06:42.710 align:start position:0% 20 or 30 years ago when lisp machines were<01:06:42.000> running<01:06:42.240> 24 01:06:42.710 --> 01:06:42.720 align:start position:0% were running 24 01:06:42.720 --> 01:06:45.430 align:start position:0% were running 24 7<01:06:42.960> in<01:06:43.119> ai<01:06:43.520> labs<01:06:44.400> and<01:06:44.559> they<01:06:44.720> had<01:06:44.960> persistent 01:06:45.430 --> 01:06:45.440 align:start position:0% 7 in ai labs and they had persistent 01:06:45.440 --> 01:06:46.950 align:start position:0% 7 in ai labs and they had persistent object<01:06:45.839> systems 01:06:46.950 --> 01:06:46.960 align:start position:0% object systems 01:06:46.960 --> 01:06:50.390 align:start position:0% object systems and<01:06:47.920> the<01:06:48.319> the<01:06:48.480> os<01:06:49.280> the<01:06:49.440> database<01:06:50.079> and<01:06:50.160> your 01:06:50.390 --> 01:06:50.400 align:start position:0% and the the os the database and your 01:06:50.400 --> 01:06:51.589 align:start position:0% and the the os the database and your program<01:06:50.720> were<01:06:50.960> all 01:06:51.589 --> 01:06:51.599 align:start position:0% program were all 01:06:51.599 --> 01:06:53.829 align:start position:0% program were all in<01:06:51.760> the<01:06:51.839> same<01:06:52.079> computer<01:06:52.799> and<01:06:53.440> even<01:06:53.680> in<01:06:53.760> the 01:06:53.829 --> 01:06:53.839 align:start position:0% in the same computer and even in the 01:06:53.839 --> 01:06:55.510 align:start position:0% in the same computer and even in the same<01:06:54.000> memory<01:06:54.319> space 01:06:55.510 --> 01:06:55.520 align:start position:0% same memory space 01:06:55.520 --> 01:06:58.309 align:start position:0% same memory space um<01:06:56.559> it<01:06:56.640> was<01:06:56.799> much<01:06:57.119> more<01:06:57.359> important<01:06:58.000> that<01:06:58.160> you 01:06:58.309 --> 01:06:58.319 align:start position:0% um it was much more important that you 01:06:58.319 --> 01:06:59.270 align:start position:0% um it was much more important that you had<01:06:58.480> that 01:06:59.270 --> 01:06:59.280 align:start position:0% had that 01:06:59.280 --> 01:07:01.270 align:start position:0% had that depth<01:06:59.599> of<01:06:59.760> debugging<01:07:00.160> capability<01:07:00.799> i<01:07:00.880> think 01:07:01.270 --> 01:07:01.280 align:start position:0% depth of debugging capability i think 01:07:01.280 --> 01:07:02.789 align:start position:0% depth of debugging capability i think this<01:07:01.440> is<01:07:02.000> it's<01:07:02.160> not<01:07:02.319> like<01:07:02.400> i<01:07:02.480> have<01:07:02.640> that 01:07:02.789 --> 01:07:02.799 align:start position:0% this is it's not like i have that 01:07:02.799 --> 01:07:04.150 align:start position:0% this is it's not like i have that experience<01:07:03.119> again<01:07:03.359> i<01:07:03.440> wasn't<01:07:03.599> even<01:07:03.760> born<01:07:04.000> when 01:07:04.150 --> 01:07:04.160 align:start position:0% experience again i wasn't even born when 01:07:04.160 --> 01:07:04.630 align:start position:0% experience again i wasn't even born when people<01:07:04.400> are 01:07:04.630 --> 01:07:04.640 align:start position:0% people are 01:07:04.640 --> 01:07:06.390 align:start position:0% people are programming<01:07:05.119> this<01:07:05.280> way<01:07:05.520> but<01:07:05.680> my<01:07:05.839> perception 01:07:06.390 --> 01:07:06.400 align:start position:0% programming this way but my perception 01:07:06.400 --> 01:07:08.950 align:start position:0% programming this way but my perception is<01:07:06.480> that<01:07:07.599> uh<01:07:07.839> one<01:07:08.000> thing<01:07:08.160> that<01:07:08.319> has<01:07:08.559> changed 01:07:08.950 --> 01:07:08.960 align:start position:0% is that uh one thing that has changed 01:07:08.960 --> 01:07:10.150 align:start position:0% is that uh one thing that has changed about<01:07:09.200> the<01:07:09.280> kinds<01:07:09.440> of<01:07:09.520> programming<01:07:09.920> most 01:07:10.150 --> 01:07:10.160 align:start position:0% about the kinds of programming most 01:07:10.160 --> 01:07:11.270 align:start position:0% about the kinds of programming most people<01:07:10.319> do<01:07:10.480> is<01:07:10.640> that<01:07:10.720> we<01:07:10.799> generally<01:07:11.119> have 01:07:11.270 --> 01:07:11.280 align:start position:0% people do is that we generally have 01:07:11.280 --> 01:07:13.109 align:start position:0% people do is that we generally have databases<01:07:11.920> now<01:07:12.160> for<01:07:12.319> managing 01:07:13.109 --> 01:07:13.119 align:start position:0% databases now for managing 01:07:13.119 --> 01:07:16.069 align:start position:0% databases now for managing transactional<01:07:13.680> data<01:07:15.200> but<01:07:15.520> that<01:07:15.680> hasn't 01:07:16.069 --> 01:07:16.079 align:start position:0% transactional data but that hasn't 01:07:16.079 --> 01:07:17.589 align:start position:0% transactional data but that hasn't always<01:07:16.319> been<01:07:16.480> the<01:07:16.559> case<01:07:16.960> and<01:07:17.119> when<01:07:17.280> common 01:07:17.589 --> 01:07:17.599 align:start position:0% always been the case and when common 01:07:17.599 --> 01:07:18.710 align:start position:0% always been the case and when common lisp 01:07:18.710 --> 01:07:18.720 align:start position:0% lisp 01:07:18.720 --> 01:07:21.750 align:start position:0% lisp first<01:07:18.960> came<01:07:19.520> into<01:07:19.760> existence<01:07:21.200> it<01:07:21.280> was<01:07:21.520> really 01:07:21.750 --> 01:07:21.760 align:start position:0% first came into existence it was really 01:07:21.760 --> 01:07:22.390 align:start position:0% first came into existence it was really important 01:07:22.390 --> 01:07:22.400 align:start position:0% important 01:07:22.400 --> 01:07:24.789 align:start position:0% important to<01:07:22.559> be<01:07:22.720> able<01:07:22.880> to<01:07:22.960> do<01:07:23.119> that<01:07:23.280> kind<01:07:23.520> of<01:07:23.680> very<01:07:24.480> very 01:07:24.789 --> 01:07:24.799 align:start position:0% to be able to do that kind of very very 01:07:24.799 --> 01:07:25.990 align:start position:0% to be able to do that kind of very very surgical<01:07:25.280> debugging 01:07:25.990 --> 01:07:26.000 align:start position:0% surgical debugging 01:07:26.000 --> 01:07:27.589 align:start position:0% surgical debugging because<01:07:26.559> you<01:07:26.720> might<01:07:26.880> lose<01:07:27.119> data<01:07:27.359> if<01:07:27.520> you 01:07:27.589 --> 01:07:27.599 align:start position:0% because you might lose data if you 01:07:27.599 --> 01:07:29.670 align:start position:0% because you might lose data if you didn't<01:07:27.760> have<01:07:27.839> an<01:07:28.000> opportunity<01:07:28.960> to<01:07:29.119> do<01:07:29.280> it 01:07:29.670 --> 01:07:29.680 align:start position:0% didn't have an opportunity to do it 01:07:29.680 --> 01:07:33.029 align:start position:0% didn't have an opportunity to do it right<01:07:29.920> then<01:07:31.920> and<01:07:32.400> actually 01:07:33.029 --> 01:07:33.039 align:start position:0% right then and actually 01:07:33.039 --> 01:07:34.630 align:start position:0% right then and actually you<01:07:33.200> can<01:07:33.359> see<01:07:33.520> this<01:07:33.680> in<01:07:33.839> action<01:07:34.160> there's<01:07:34.400> a 01:07:34.630 --> 01:07:34.640 align:start position:0% you can see this in action there's a 01:07:34.640 --> 01:07:36.950 align:start position:0% you can see this in action there's a youtube<01:07:34.960> video<01:07:35.280> of<01:07:35.440> a<01:07:35.520> screencast 01:07:36.950 --> 01:07:36.960 align:start position:0% youtube video of a screencast 01:07:36.960 --> 01:07:40.230 align:start position:0% youtube video of a screencast of<01:07:38.480> i<01:07:38.640> believe<01:07:39.440> symbolics 01:07:40.230 --> 01:07:40.240 align:start position:0% of i believe symbolics 01:07:40.240 --> 01:07:43.670 align:start position:0% of i believe symbolics only<01:07:40.559> employee<01:07:41.520> right<01:07:41.680> now<01:07:42.640> so<01:07:43.200> there<01:07:43.440> is 01:07:43.670 --> 01:07:43.680 align:start position:0% only employee right now so there is 01:07:43.680 --> 01:07:45.109 align:start position:0% only employee right now so there is still<01:07:43.920> a<01:07:44.000> symbolic<01:07:44.480> company<01:07:44.799> and<01:07:44.880> they 01:07:45.109 --> 01:07:45.119 align:start position:0% still a symbolic company and they 01:07:45.119 --> 01:07:47.190 align:start position:0% still a symbolic company and they distribute<01:07:45.920> uh 01:07:47.190 --> 01:07:47.200 align:start position:0% distribute uh 01:07:47.200 --> 01:07:50.470 align:start position:0% distribute uh cds<01:07:47.760> of<01:07:48.160> opengenera<01:07:49.280> and<01:07:49.680> vlm<01:07:50.160> which<01:07:50.400> are 01:07:50.470 --> 01:07:50.480 align:start position:0% cds of opengenera and vlm which are 01:07:50.480 --> 01:07:51.589 align:start position:0% cds of opengenera and vlm which are their 01:07:51.589 --> 01:07:51.599 align:start position:0% their 01:07:51.599 --> 01:07:53.190 align:start position:0% their it's<01:07:51.839> a<01:07:52.000> it's<01:07:52.160> a<01:07:52.240> list<01:07:52.480> machine<01:07:52.880> virtual 01:07:53.190 --> 01:07:53.200 align:start position:0% it's a it's a list machine virtual 01:07:53.200 --> 01:07:54.789 align:start position:0% it's a it's a list machine virtual machine<01:07:53.599> and<01:07:53.760> the<01:07:53.920> os<01:07:54.240> on<01:07:54.319> top<01:07:54.559> and<01:07:54.640> they 01:07:54.789 --> 01:07:54.799 align:start position:0% machine and the os on top and they 01:07:54.799 --> 01:07:56.390 align:start position:0% machine and the os on top and they actually<01:07:55.039> employ<01:07:55.440> someone<01:07:55.680> who<01:07:55.839> used<01:07:56.079> to<01:07:56.160> work 01:07:56.390 --> 01:07:56.400 align:start position:0% actually employ someone who used to work 01:07:56.400 --> 01:07:57.990 align:start position:0% actually employ someone who used to work at<01:07:56.559> symbolics 01:07:57.990 --> 01:07:58.000 align:start position:0% at symbolics 01:07:58.000 --> 01:07:59.750 align:start position:0% at symbolics and<01:07:58.319> he<01:07:58.480> did<01:07:58.640> a<01:07:58.720> screencast<01:07:59.280> at<01:07:59.359> a<01:07:59.440> meetup 01:07:59.750 --> 01:07:59.760 align:start position:0% and he did a screencast at a meetup 01:07:59.760 --> 01:08:01.910 align:start position:0% and he did a screencast at a meetup where<01:08:00.000> he<01:08:00.160> showed<01:08:00.960> how<01:08:01.200> he<01:08:01.359> debugged<01:08:01.839> the 01:08:01.910 --> 01:08:01.920 align:start position:0% where he showed how he debugged the 01:08:01.920 --> 01:08:02.870 align:start position:0% where he showed how he debugged the network<01:08:02.319> driver 01:08:02.870 --> 01:08:02.880 align:start position:0% network driver 01:08:02.880 --> 01:08:05.349 align:start position:0% network driver or<01:08:02.960> something<01:08:03.280> like<01:08:03.440> that<01:08:04.559> and<01:08:04.960> it's<01:08:05.119> pretty 01:08:05.349 --> 01:08:05.359 align:start position:0% or something like that and it's pretty 01:08:05.359 --> 01:08:06.630 align:start position:0% or something like that and it's pretty incredible<01:08:05.839> because 01:08:06.630 --> 01:08:06.640 align:start position:0% incredible because 01:08:06.640 --> 01:08:08.549 align:start position:0% incredible because like<01:08:06.960> svante<01:08:07.440> is<01:08:07.520> saying<01:08:07.839> you<01:08:07.920> see<01:08:08.079> him<01:08:08.319> go 01:08:08.549 --> 01:08:08.559 align:start position:0% like svante is saying you see him go 01:08:08.559 --> 01:08:09.670 align:start position:0% like svante is saying you see him go from<01:08:08.720> like<01:08:08.880> the<01:08:08.960> highest<01:08:09.200> levels<01:08:09.520> of 01:08:09.670 --> 01:08:09.680 align:start position:0% from like the highest levels of 01:08:09.680 --> 01:08:10.390 align:start position:0% from like the highest levels of abstraction 01:08:10.390 --> 01:08:10.400 align:start position:0% abstraction 01:08:10.400 --> 01:08:11.430 align:start position:0% abstraction like<01:08:10.640> you<01:08:10.720> know<01:08:10.880> right<01:08:11.039> clicking<01:08:11.359> and 01:08:11.430 --> 01:08:11.440 align:start position:0% like you know right clicking and 01:08:11.440 --> 01:08:14.069 align:start position:0% like you know right clicking and navigating<01:08:11.920> hyperlinks<01:08:13.039> to<01:08:13.200> like 01:08:14.069 --> 01:08:14.079 align:start position:0% navigating hyperlinks to like 01:08:14.079 --> 01:08:16.630 align:start position:0% navigating hyperlinks to like pausing<01:08:14.480> in<01:08:14.559> the<01:08:14.720> stack<01:08:15.280> inside<01:08:16.000> the<01:08:16.159> ethernet 01:08:16.630 --> 01:08:16.640 align:start position:0% pausing in the stack inside the ethernet 01:08:16.640 --> 01:08:18.149 align:start position:0% pausing in the stack inside the ethernet or<01:08:16.799> the<01:08:16.880> network<01:08:17.199> drive<01:08:17.440> the<01:08:17.520> chaos<01:08:17.920> net 01:08:18.149 --> 01:08:18.159 align:start position:0% or the network drive the chaos net 01:08:18.159 --> 01:08:19.910 align:start position:0% or the network drive the chaos net driver<01:08:18.480> or<01:08:18.560> whatever<01:08:18.799> he<01:08:18.960> was<01:08:19.040> doing 01:08:19.910 --> 01:08:19.920 align:start position:0% driver or whatever he was doing 01:08:19.920 --> 01:08:22.789 align:start position:0% driver or whatever he was doing and<01:08:20.239> like<01:08:20.719> twiddling<01:08:21.199> bits<01:08:21.440> in<01:08:21.600> there<01:08:22.640> and 01:08:22.789 --> 01:08:22.799 align:start position:0% and like twiddling bits in there and 01:08:22.799 --> 01:08:23.430 align:start position:0% and like twiddling bits in there and then 01:08:23.430 --> 01:08:23.440 align:start position:0% then 01:08:23.440 --> 01:08:25.430 align:start position:0% then like<01:08:23.600> this<01:08:23.839> is<01:08:23.920> like<01:08:24.159> in<01:08:24.239> the<01:08:24.319> middle<01:08:24.719> of<01:08:25.279> like 01:08:25.430 --> 01:08:25.440 align:start position:0% like this is like in the middle of like 01:08:25.440 --> 01:08:27.749 align:start position:0% like this is like in the middle of like he's<01:08:25.679> actually<01:08:26.239> i<01:08:26.400> believe 01:08:27.749 --> 01:08:27.759 align:start position:0% he's actually i believe 01:08:27.759 --> 01:08:29.430 align:start position:0% he's actually i believe it<01:08:27.920> was<01:08:28.159> actually<01:08:28.480> like<01:08:28.640> in<01:08:28.799> the<01:08:28.880> middle<01:08:29.120> of<01:08:29.279> a 01:08:29.430 --> 01:08:29.440 align:start position:0% it was actually like in the middle of a 01:08:29.440 --> 01:08:30.789 align:start position:0% it was actually like in the middle of a network 01:08:30.789 --> 01:08:30.799 align:start position:0% network 01:08:30.799 --> 01:08:33.749 align:start position:0% network transaction<01:08:32.000> it<01:08:32.159> would<01:08:32.239> be<01:08:32.480> like<01:08:33.279> pausing 01:08:33.749 --> 01:08:33.759 align:start position:0% transaction it would be like pausing 01:08:33.759 --> 01:08:37.110 align:start position:0% transaction it would be like pausing linux<01:08:34.239> inside<01:08:34.640> a<01:08:34.719> packet<01:08:35.199> so<01:08:35.359> that<01:08:35.520> you<01:08:35.679> could 01:08:37.110 --> 01:08:37.120 align:start position:0% linux inside a packet so that you could 01:08:37.120 --> 01:08:38.789 align:start position:0% linux inside a packet so that you could you<01:08:37.279> know<01:08:37.440> look<01:08:37.600> at<01:08:37.679> the<01:08:37.759> packet<01:08:38.319> or<01:08:38.560> change 01:08:38.789 --> 01:08:38.799 align:start position:0% you know look at the packet or change 01:08:38.799 --> 01:08:40.149 align:start position:0% you know look at the packet or change what<01:08:39.120> was<01:08:39.279> going<01:08:39.359> to<01:08:39.440> happen<01:08:39.679> to<01:08:39.759> the<01:08:39.839> pack<01:08:40.080> or 01:08:40.149 --> 01:08:40.159 align:start position:0% what was going to happen to the pack or 01:08:40.159 --> 01:08:41.590 align:start position:0% what was going to happen to the pack or something<01:08:40.400> like<01:08:40.560> that 01:08:41.590 --> 01:08:41.600 align:start position:0% something like that 01:08:41.600 --> 01:08:44.950 align:start position:0% something like that um<01:08:42.560> so<01:08:42.960> i<01:08:43.040> think<01:08:43.759> yeah<01:08:43.920> i<01:08:44.000> think<01:08:44.400> in<01:08:44.560> our<01:08:44.640> modern 01:08:44.950 --> 01:08:44.960 align:start position:0% um so i think yeah i think in our modern 01:08:44.960 --> 01:08:46.950 align:start position:0% um so i think yeah i think in our modern usage<01:08:45.279> of<01:08:45.359> languages<01:08:45.839> that<01:08:46.080> capability<01:08:46.719> isn't 01:08:46.950 --> 01:08:46.960 align:start position:0% usage of languages that capability isn't 01:08:46.960 --> 01:08:47.590 align:start position:0% usage of languages that capability isn't as<01:08:47.040> important 01:08:47.590 --> 01:08:47.600 align:start position:0% as important 01:08:47.600 --> 01:08:50.309 align:start position:0% as important and<01:08:47.759> part<01:08:47.920> of<01:08:48.080> it<01:08:48.239> might<01:08:48.400> be<01:08:48.640> because<01:08:50.080> we've 01:08:50.309 --> 01:08:50.319 align:start position:0% and part of it might be because we've 01:08:50.319 --> 01:08:50.950 align:start position:0% and part of it might be because we've given<01:08:50.640> up 01:08:50.950 --> 01:08:50.960 align:start position:0% given up 01:08:50.960 --> 01:08:53.990 align:start position:0% given up the<01:08:51.199> need<01:08:51.759> for<01:08:52.080> that<01:08:52.480> because<01:08:53.120> we<01:08:53.199> have<01:08:53.359> we<01:08:53.759> we 01:08:53.990 --> 01:08:54.000 align:start position:0% the need for that because we have we we 01:08:54.000 --> 01:08:56.950 align:start position:0% the need for that because we have we we rely<01:08:54.319> on<01:08:54.480> the<01:08:54.560> platform<01:08:55.839> you<01:08:56.000> know<01:08:56.480> again<01:08:56.719> to 01:08:56.950 --> 01:08:56.960 align:start position:0% rely on the platform you know again to 01:08:56.960 --> 01:08:57.269 align:start position:0% rely on the platform you know again to our 01:08:57.269 --> 01:08:57.279 align:start position:0% our 01:08:57.279 --> 01:08:59.510 align:start position:0% our benefit<01:08:57.759> and<01:08:58.000> our<01:08:58.159> detriment<01:08:58.719> if<01:08:58.880> that's 01:08:59.510 --> 01:08:59.520 align:start position:0% benefit and our detriment if that's 01:08:59.520 --> 01:09:03.590 align:start position:0% benefit and our detriment if that's depending<01:08:59.839> on<01:08:59.920> your<01:09:00.080> perspective 01:09:03.590 --> 01:09:03.600 align:start position:0% 01:09:03.600 --> 01:09:05.749 align:start position:0% but<01:09:03.759> yeah<01:09:04.159> i'll<01:09:04.719> i'll<01:09:05.120> find<01:09:05.279> a<01:09:05.359> link<01:09:05.520> to<01:09:05.600> that 01:09:05.749 --> 01:09:05.759 align:start position:0% but yeah i'll i'll find a link to that 01:09:05.759 --> 01:09:06.709 align:start position:0% but yeah i'll i'll find a link to that video<01:09:06.000> it's<01:09:06.319> pretty 01:09:06.709 --> 01:09:06.719 align:start position:0% video it's pretty 01:09:06.719 --> 01:09:10.149 align:start position:0% video it's pretty pretty<01:09:06.880> amazing 01:09:10.149 --> 01:09:10.159 align:start position:0% 01:09:10.159 --> 01:09:12.870 align:start position:0% yeah<01:09:10.480> um<01:09:10.960> just<01:09:11.120> adding<01:09:11.440> to<01:09:11.520> that<01:09:11.759> um<01:09:12.719> you 01:09:12.870 --> 01:09:12.880 align:start position:0% yeah um just adding to that um you 01:09:12.880 --> 01:09:14.229 align:start position:0% yeah um just adding to that um you mentioned<01:09:13.040> the<01:09:13.199> condition<01:09:13.600> system<01:09:13.920> which<01:09:14.159> i 01:09:14.229 --> 01:09:14.239 align:start position:0% mentioned the condition system which i 01:09:14.239 --> 01:09:15.030 align:start position:0% mentioned the condition system which i think<01:09:14.480> is<01:09:14.640> also 01:09:15.030 --> 01:09:15.040 align:start position:0% think is also 01:09:15.040 --> 01:09:17.829 align:start position:0% think is also a<01:09:15.120> very<01:09:15.359> defining<01:09:15.839> thing<01:09:17.279> there's<01:09:17.600> a 01:09:17.829 --> 01:09:17.839 align:start position:0% a very defining thing there's a 01:09:17.839 --> 01:09:20.309 align:start position:0% a very defining thing there's a commonest<01:09:18.319> guy<01:09:18.839> who<01:09:18.960> um 01:09:20.309 --> 01:09:20.319 align:start position:0% commonest guy who um 01:09:20.319 --> 01:09:23.030 align:start position:0% commonest guy who um recently<01:09:21.600> i<01:09:21.759> think<01:09:22.000> two<01:09:22.159> or<01:09:22.319> three<01:09:22.480> months<01:09:22.719> ago 01:09:23.030 --> 01:09:23.040 align:start position:0% recently i think two or three months ago 01:09:23.040 --> 01:09:23.990 align:start position:0% recently i think two or three months ago um<01:09:23.359> just 01:09:23.990 --> 01:09:24.000 align:start position:0% um just 01:09:24.000 --> 01:09:27.110 align:start position:0% um just wrote<01:09:24.400> a<01:09:24.480> little<01:09:25.759> a<01:09:25.920> java<01:09:26.239> library<01:09:26.799> that 01:09:27.110 --> 01:09:27.120 align:start position:0% wrote a little a java library that 01:09:27.120 --> 01:09:28.950 align:start position:0% wrote a little a java library that implements<01:09:27.679> the<01:09:27.839> common<01:09:28.159> list<01:09:28.480> condition 01:09:28.950 --> 01:09:28.960 align:start position:0% implements the common list condition 01:09:28.960 --> 01:09:30.870 align:start position:0% implements the common list condition system<01:09:29.359> in<01:09:29.440> java 01:09:30.870 --> 01:09:30.880 align:start position:0% system in java 01:09:30.880 --> 01:09:32.950 align:start position:0% system in java so<01:09:31.120> if<01:09:31.199> you<01:09:31.600> if<01:09:31.759> you're<01:09:31.839> interested<01:09:32.239> in<01:09:32.400> that<01:09:32.640> i 01:09:32.950 --> 01:09:32.960 align:start position:0% so if you if you're interested in that i 01:09:32.960 --> 01:09:34.309 align:start position:0% so if you if you're interested in that i posted<01:09:33.279> the<01:09:33.440> link<01:09:33.600> to<01:09:33.759> that 01:09:34.309 --> 01:09:34.319 align:start position:0% posted the link to that 01:09:34.319 --> 01:09:37.430 align:start position:0% posted the link to that into<01:09:34.560> the 01:09:37.430 --> 01:09:37.440 align:start position:0% 01:09:37.440 --> 01:09:40.630 align:start position:0% definitely<01:09:37.759> check<01:09:38.000> that<01:09:38.159> out<01:09:39.440> oh<01:09:40.000> foe 01:09:40.630 --> 01:09:40.640 align:start position:0% definitely check that out oh foe 01:09:40.640 --> 01:09:42.550 align:start position:0% definitely check that out oh foe yes<01:09:41.120> he<01:09:41.359> wrote<01:09:41.600> a<01:09:41.679> book<01:09:41.920> too<01:09:42.159> didn't<01:09:42.400> he 01:09:42.550 --> 01:09:42.560 align:start position:0% yes he wrote a book too didn't he 01:09:42.560 --> 01:09:43.829 align:start position:0% yes he wrote a book too didn't he recently 01:09:43.829 --> 01:09:43.839 align:start position:0% recently 01:09:43.839 --> 01:09:48.950 align:start position:0% recently yes<01:09:44.080> excuse<01:09:44.400> me<01:09:44.960> right<01:09:46.839> right 01:09:48.950 --> 01:09:48.960 align:start position:0% yes excuse me right right 01:09:48.960 --> 01:09:53.030 align:start position:0% yes excuse me right right um<01:09:49.520> cool<01:09:50.000> very<01:09:50.239> cool 01:09:53.030 --> 01:09:53.040 align:start position:0% 01:09:53.040 --> 01:09:56.310 align:start position:0% kenneth<01:09:54.000> can<01:09:54.159> i<01:09:54.239> just<01:09:54.560> ask 01:09:56.310 --> 01:09:56.320 align:start position:0% kenneth can i just ask 01:09:56.320 --> 01:09:59.830 align:start position:0% kenneth can i just ask the<01:09:56.480> audience<01:09:57.120> if<01:09:57.600> um<01:09:59.199> we<01:09:59.360> have<01:09:59.600> common 01:09:59.830 --> 01:09:59.840 align:start position:0% the audience if um we have common 01:09:59.840 --> 01:10:00.870 align:start position:0% the audience if um we have common lispers<01:10:00.320> here 01:10:00.870 --> 01:10:00.880 align:start position:0% lispers here 01:10:00.880 --> 01:10:04.070 align:start position:0% lispers here who<01:10:01.120> would<01:10:01.360> like<01:10:01.679> to<01:10:03.600> add 01:10:04.070 --> 01:10:04.080 align:start position:0% who would like to add 01:10:04.080 --> 01:10:07.430 align:start position:0% who would like to add anything<01:10:04.560> from<01:10:04.719> their<01:10:04.880> own<01:10:05.120> experience<01:10:06.640> uh 01:10:07.430 --> 01:10:07.440 align:start position:0% anything from their own experience uh 01:10:07.440 --> 01:10:10.390 align:start position:0% anything from their own experience uh and<01:10:07.679> and<01:10:07.920> just<01:10:08.159> uh<01:10:08.640> you<01:10:08.800> know<01:10:09.120> if<01:10:09.760> if<01:10:09.920> you<01:10:10.000> feel 01:10:10.390 --> 01:10:10.400 align:start position:0% and and just uh you know if if you feel 01:10:10.400 --> 01:10:12.229 align:start position:0% and and just uh you know if if you feel if<01:10:10.560> you<01:10:10.640> want<01:10:10.800> to<01:10:10.880> say<01:10:11.120> something 01:10:12.229 --> 01:10:12.239 align:start position:0% if you want to say something 01:10:12.239 --> 01:10:15.669 align:start position:0% if you want to say something please<01:10:12.640> do<01:10:13.199> uh<01:10:14.000> i'm<01:10:14.480> i'm<01:10:14.640> very<01:10:14.880> interested<01:10:15.440> and 01:10:15.669 --> 01:10:15.679 align:start position:0% please do uh i'm i'm very interested and 01:10:15.679 --> 01:10:18.390 align:start position:0% please do uh i'm i'm very interested and probably<01:10:16.080> more<01:10:16.480> more<01:10:16.880> more<01:10:17.120> people<01:10:17.440> are 01:10:18.390 --> 01:10:18.400 align:start position:0% probably more more more people are 01:10:18.400 --> 01:10:24.229 align:start position:0% probably more more more people are absolutely 01:10:24.229 --> 01:10:24.239 align:start position:0% 01:10:24.239 --> 01:10:27.189 align:start position:0% maybe<01:10:24.560> i'll<01:10:24.719> just<01:10:25.679> uh<01:10:25.920> offer<01:10:26.239> a<01:10:26.320> comment<01:10:26.960> um 01:10:27.189 --> 01:10:27.199 align:start position:0% maybe i'll just uh offer a comment um 01:10:27.199 --> 01:10:27.990 align:start position:0% maybe i'll just uh offer a comment um adam 01:10:27.990 --> 01:10:28.000 align:start position:0% adam 01:10:28.000 --> 01:10:29.990 align:start position:0% adam i<01:10:28.080> think<01:10:28.320> on<01:10:28.400> your<01:10:28.560> last<01:10:28.880> slide<01:10:29.199> you<01:10:29.280> had<01:10:29.440> a 01:10:29.990 --> 01:10:30.000 align:start position:0% i think on your last slide you had a 01:10:30.000 --> 01:10:31.110 align:start position:0% i think on your last slide you had a list<01:10:30.239> of<01:10:30.400> things<01:10:30.640> that<01:10:30.719> you 01:10:31.110 --> 01:10:31.120 align:start position:0% list of things that you 01:10:31.120 --> 01:10:34.390 align:start position:0% list of things that you might<01:10:31.440> talk<01:10:31.679> about<01:10:31.920> one<01:10:32.080> was<01:10:32.320> the<01:10:32.560> um<01:10:33.920> symbols 01:10:34.390 --> 01:10:34.400 align:start position:0% might talk about one was the um symbols 01:10:34.400 --> 01:10:34.790 align:start position:0% might talk about one was the um symbols and<01:10:34.480> the 01:10:34.790 --> 01:10:34.800 align:start position:0% and the 01:10:34.800 --> 01:10:38.070 align:start position:0% and the and<01:10:34.880> the<01:10:35.120> package<01:10:35.520> system<01:10:37.199> um<01:10:37.520> when<01:10:37.760> i 01:10:38.070 --> 01:10:38.080 align:start position:0% and the package system um when i 01:10:38.080 --> 01:10:40.149 align:start position:0% and the package system um when i so<01:10:38.320> so<01:10:38.560> i<01:10:38.880> had<01:10:39.040> a<01:10:39.120> background<01:10:39.520> in<01:10:39.600> common<01:10:39.920> lisp 01:10:40.149 --> 01:10:40.159 align:start position:0% so so i had a background in common lisp 01:10:40.159 --> 01:10:41.830 align:start position:0% so so i had a background in common lisp when<01:10:40.320> i<01:10:40.320> was<01:10:40.480> learning<01:10:40.800> closure 01:10:41.830 --> 01:10:41.840 align:start position:0% when i was learning closure 01:10:41.840 --> 01:10:44.390 align:start position:0% when i was learning closure and<01:10:42.000> i<01:10:42.239> found<01:10:43.199> the<01:10:43.360> way<01:10:43.600> symbols<01:10:44.000> worked<01:10:44.320> in 01:10:44.390 --> 01:10:44.400 align:start position:0% and i found the way symbols worked in 01:10:44.400 --> 01:10:45.510 align:start position:0% and i found the way symbols worked in closure<01:10:44.800> to<01:10:44.960> be 01:10:45.510 --> 01:10:45.520 align:start position:0% closure to be 01:10:45.520 --> 01:10:47.350 align:start position:0% closure to be i<01:10:45.760> guess<01:10:46.000> i<01:10:46.080> came<01:10:46.400> in<01:10:46.480> with<01:10:46.640> a<01:10:46.719> bunch<01:10:46.880> of 01:10:47.350 --> 01:10:47.360 align:start position:0% i guess i came in with a bunch of 01:10:47.360 --> 01:10:49.669 align:start position:0% i guess i came in with a bunch of assumptions<01:10:48.320> that<01:10:48.560> just<01:10:48.800> went<01:10:49.120> weren't 01:10:49.669 --> 01:10:49.679 align:start position:0% assumptions that just went weren't 01:10:49.679 --> 01:10:52.149 align:start position:0% assumptions that just went weren't true<01:10:49.920> and<01:10:50.080> i<01:10:50.320> it<01:10:50.480> took<01:10:50.640> me<01:10:50.719> a<01:10:50.800> while<01:10:51.040> to<01:10:51.920> really 01:10:52.149 --> 01:10:52.159 align:start position:0% true and i it took me a while to really 01:10:52.159 --> 01:10:53.030 align:start position:0% true and i it took me a while to really understand<01:10:52.640> how 01:10:53.030 --> 01:10:53.040 align:start position:0% understand how 01:10:53.040 --> 01:10:55.590 align:start position:0% understand how how<01:10:53.360> common<01:10:53.679> this<01:10:54.080> sorry<01:10:54.320> how<01:10:54.480> closure 01:10:55.590 --> 01:10:55.600 align:start position:0% how common this sorry how closure 01:10:55.600 --> 01:10:56.950 align:start position:0% how common this sorry how closure symbols<01:10:56.080> worked 01:10:56.950 --> 01:10:56.960 align:start position:0% symbols worked 01:10:56.960 --> 01:10:59.590 align:start position:0% symbols worked um<01:10:57.840> i<01:10:58.000> think<01:10:58.159> that<01:10:58.400> they're<01:10:58.880> they're<01:10:59.280> quite<01:10:59.520> a 01:10:59.590 --> 01:10:59.600 align:start position:0% um i think that they're they're quite a 01:10:59.600 --> 01:11:00.470 align:start position:0% um i think that they're they're quite a lot<01:10:59.920> different 01:11:00.470 --> 01:11:00.480 align:start position:0% lot different 01:11:00.480 --> 01:11:03.910 align:start position:0% lot different to<01:11:01.120> common<01:11:01.440> lisp<01:11:01.760> symbols<01:11:02.719> i<01:11:02.880> just<01:11:03.280> wondered 01:11:03.910 --> 01:11:03.920 align:start position:0% to common lisp symbols i just wondered 01:11:03.920 --> 01:11:06.550 align:start position:0% to common lisp symbols i just wondered if<01:11:04.159> you<01:11:04.239> had<01:11:04.480> any<01:11:05.360> any<01:11:05.600> um<01:11:06.000> i<01:11:06.080> guess<01:11:06.239> you've<01:11:06.400> got 01:11:06.550 --> 01:11:06.560 align:start position:0% if you had any any um i guess you've got 01:11:06.560 --> 01:11:07.990 align:start position:0% if you had any any um i guess you've got some<01:11:06.719> thoughts<01:11:06.960> on<01:11:07.040> that<01:11:07.199> because<01:11:07.520> of 01:11:07.990 --> 01:11:08.000 align:start position:0% some thoughts on that because of 01:11:08.000 --> 01:11:10.870 align:start position:0% some thoughts on that because of what<01:11:08.159> was<01:11:08.320> on<01:11:08.400> your<01:11:08.560> slide<01:11:08.880> there<01:11:09.600> yes<01:11:10.640> two 01:11:10.870 --> 01:11:10.880 align:start position:0% what was on your slide there yes two 01:11:10.880 --> 01:11:12.070 align:start position:0% what was on your slide there yes two thoughts<01:11:11.199> so<01:11:11.440> first<01:11:11.600> of<01:11:11.760> all 01:11:12.070 --> 01:11:12.080 align:start position:0% thoughts so first of all 01:11:12.080 --> 01:11:14.709 align:start position:0% thoughts so first of all uh<01:11:12.400> i<01:11:12.480> don't<01:11:12.640> know<01:11:12.800> about<01:11:12.960> you<01:11:13.199> all<01:11:13.520> but<01:11:14.400> when<01:11:14.640> i 01:11:14.709 --> 01:11:14.719 align:start position:0% uh i don't know about you all but when i 01:11:14.719 --> 01:11:15.750 align:start position:0% uh i don't know about you all but when i was<01:11:14.880> learning<01:11:15.199> closure 01:11:15.750 --> 01:11:15.760 align:start position:0% was learning closure 01:11:15.760 --> 01:11:18.950 align:start position:0% was learning closure the<01:11:15.920> ns<01:11:16.320> macro<01:11:17.600> took<01:11:17.840> me<01:11:17.920> a<01:11:18.080> really<01:11:18.239> long<01:11:18.480> time 01:11:18.950 --> 01:11:18.960 align:start position:0% the ns macro took me a really long time 01:11:18.960 --> 01:11:21.830 align:start position:0% the ns macro took me a really long time to<01:11:19.120> become<01:11:19.440> comfortable<01:11:19.840> with<01:11:20.719> and<01:11:21.280> i<01:11:21.440> think<01:11:21.760> i 01:11:21.830 --> 01:11:21.840 align:start position:0% to become comfortable with and i think i 01:11:21.840 --> 01:11:23.030 align:start position:0% to become comfortable with and i think i was<01:11:22.000> thinking<01:11:22.320> of<01:11:22.480> it<01:11:22.719> like 01:11:23.030 --> 01:11:23.040 align:start position:0% was thinking of it like 01:11:23.040 --> 01:11:25.270 align:start position:0% was thinking of it like you<01:11:23.120> know<01:11:23.280> python's<01:11:23.840> import<01:11:24.159> syntax<01:11:24.800> i<01:11:24.960> took 01:11:25.270 --> 01:11:25.280 align:start position:0% you know python's import syntax i took 01:11:25.280 --> 01:11:26.070 align:start position:0% you know python's import syntax i took the<01:11:25.520> syntax 01:11:26.070 --> 01:11:26.080 align:start position:0% the syntax 01:11:26.080 --> 01:11:28.550 align:start position:0% the syntax for<01:11:26.239> the<01:11:26.480> thing<01:11:27.600> which<01:11:28.000> you<01:11:28.080> know<01:11:28.320> as<01:11:28.400> you 01:11:28.550 --> 01:11:28.560 align:start position:0% for the thing which you know as you 01:11:28.560 --> 01:11:29.510 align:start position:0% for the thing which you know as you learn<01:11:28.800> lisp<01:11:29.120> you 01:11:29.510 --> 01:11:29.520 align:start position:0% learn lisp you 01:11:29.520 --> 01:11:31.270 align:start position:0% learn lisp you realize<01:11:29.920> that<01:11:30.080> the<01:11:30.159> syntax<01:11:30.640> is<01:11:30.719> the<01:11:30.880> front<01:11:31.120> end 01:11:31.270 --> 01:11:31.280 align:start position:0% realize that the syntax is the front end 01:11:31.280 --> 01:11:32.790 align:start position:0% realize that the syntax is the front end for<01:11:31.440> the<01:11:31.600> thing<01:11:32.000> and<01:11:32.159> if<01:11:32.320> you<01:11:32.400> really<01:11:32.560> want<01:11:32.640> to 01:11:32.790 --> 01:11:32.800 align:start position:0% for the thing and if you really want to 01:11:32.800 --> 01:11:33.830 align:start position:0% for the thing and if you really want to understand<01:11:33.120> the<01:11:33.199> thing<01:11:33.440> you<01:11:33.520> have<01:11:33.600> to<01:11:33.679> go 01:11:33.830 --> 01:11:33.840 align:start position:0% understand the thing you have to go 01:11:33.840 --> 01:11:35.430 align:start position:0% understand the thing you have to go beneath<01:11:34.159> the<01:11:34.239> syntax<01:11:34.719> but 01:11:35.430 --> 01:11:35.440 align:start position:0% beneath the syntax but 01:11:35.440 --> 01:11:38.550 align:start position:0% beneath the syntax but um<01:11:36.480> yeah<01:11:36.719> so<01:11:36.880> i<01:11:37.040> was<01:11:37.199> pretty<01:11:37.600> befuddled<01:11:38.080> by<01:11:38.239> the 01:11:38.550 --> 01:11:38.560 align:start position:0% um yeah so i was pretty befuddled by the 01:11:38.560 --> 01:11:40.550 align:start position:0% um yeah so i was pretty befuddled by the ns<01:11:38.880> macro<01:11:39.600> and<01:11:39.840> i<01:11:39.920> didn't<01:11:40.159> have<01:11:40.239> my<01:11:40.400> head 01:11:40.550 --> 01:11:40.560 align:start position:0% ns macro and i didn't have my head 01:11:40.560 --> 01:11:42.070 align:start position:0% ns macro and i didn't have my head around<01:11:40.800> the<01:11:41.040> closure<01:11:41.360> package<01:11:41.679> system<01:11:42.000> and 01:11:42.070 --> 01:11:42.080 align:start position:0% around the closure package system and 01:11:42.080 --> 01:11:46.630 align:start position:0% around the closure package system and then<01:11:42.239> i<01:11:42.320> finally<01:11:42.640> did 01:11:46.630 --> 01:11:46.640 align:start position:0% 01:11:46.640 --> 01:11:49.830 align:start position:0% and<01:11:47.280> i<01:11:47.520> think<01:11:48.640> based<01:11:48.960> on<01:11:49.120> what<01:11:49.280> i've<01:11:49.520> read 01:11:49.830 --> 01:11:49.840 align:start position:0% and i think based on what i've read 01:11:49.840 --> 01:11:51.590 align:start position:0% and i think based on what i've read about<01:11:50.239> the<01:11:50.400> common<01:11:50.640> list<01:11:50.880> package<01:11:51.199> system<01:11:51.520> i 01:11:51.590 --> 01:11:51.600 align:start position:0% about the common list package system i 01:11:51.600 --> 01:11:55.510 align:start position:0% about the common list package system i think<01:11:51.760> there<01:11:51.920> are<01:11:52.000> a<01:11:52.000> lot<01:11:52.159> of<01:11:52.320> the<01:11:52.840> same<01:11:53.760> uh 01:11:55.510 --> 01:11:55.520 align:start position:0% think there are a lot of the same uh 01:11:55.520 --> 01:11:57.110 align:start position:0% think there are a lot of the same uh at<01:11:55.679> least<01:11:55.920> people<01:11:56.159> who<01:11:56.320> are<01:11:56.400> learning<01:11:56.800> seem<01:11:57.040> to 01:11:57.110 --> 01:11:57.120 align:start position:0% at least people who are learning seem to 01:11:57.120 --> 01:11:58.630 align:start position:0% at least people who are learning seem to have<01:11:57.280> some<01:11:57.440> of<01:11:57.520> the<01:11:57.600> same<01:11:57.840> problems 01:11:58.630 --> 01:11:58.640 align:start position:0% have some of the same problems 01:11:58.640 --> 01:12:00.390 align:start position:0% have some of the same problems but<01:11:58.800> anyway<01:11:59.120> that's<01:11:59.440> that's<01:11:59.600> sort<01:11:59.760> of<01:12:00.159> neither 01:12:00.390 --> 01:12:00.400 align:start position:0% but anyway that's that's sort of neither 01:12:00.400 --> 01:12:02.070 align:start position:0% but anyway that's that's sort of neither here<01:12:00.560> nor<01:12:00.800> there<01:12:00.960> that<01:12:01.120> doesn't<01:12:01.600> address<01:12:01.920> your 01:12:02.070 --> 01:12:02.080 align:start position:0% here nor there that doesn't address your 01:12:02.080 --> 01:12:03.270 align:start position:0% here nor there that doesn't address your question<01:12:02.400> exactly 01:12:03.270 --> 01:12:03.280 align:start position:0% question exactly 01:12:03.280 --> 01:12:05.830 align:start position:0% question exactly um<01:12:04.000> yeah<01:12:04.239> the<01:12:04.320> big<01:12:04.560> difference<01:12:05.120> the<01:12:05.360> specific 01:12:05.830 --> 01:12:05.840 align:start position:0% um yeah the big difference the specific 01:12:05.840 --> 01:12:07.750 align:start position:0% um yeah the big difference the specific technical<01:12:06.320> difference<01:12:06.800> between<01:12:07.120> the<01:12:07.280> reader 01:12:07.750 --> 01:12:07.760 align:start position:0% technical difference between the reader 01:12:07.760 --> 01:12:09.030 align:start position:0% technical difference between the reader the<01:12:07.920> symbol<01:12:08.159> reader<01:12:08.480> enclosure<01:12:08.880> and<01:12:08.960> the 01:12:09.030 --> 01:12:09.040 align:start position:0% the symbol reader enclosure and the 01:12:09.040 --> 01:12:10.709 align:start position:0% the symbol reader enclosure and the simple<01:12:09.280> reader<01:12:09.520> and<01:12:09.600> common<01:12:09.840> lisp 01:12:10.709 --> 01:12:10.719 align:start position:0% simple reader and common lisp 01:12:10.719 --> 01:12:14.470 align:start position:0% simple reader and common lisp is<01:12:10.880> that<01:12:11.600> the<01:12:13.120> common<01:12:13.600> lisp 01:12:14.470 --> 01:12:14.480 align:start position:0% is that the common lisp 01:12:14.480 --> 01:12:17.910 align:start position:0% is that the common lisp symbols<01:12:15.360> are<01:12:15.679> interned<01:12:16.880> in<01:12:17.280> the<01:12:17.520> current 01:12:17.910 --> 01:12:17.920 align:start position:0% symbols are interned in the current 01:12:17.920 --> 01:12:18.790 align:start position:0% symbols are interned in the current package 01:12:18.790 --> 01:12:18.800 align:start position:0% package 01:12:18.800 --> 01:12:21.830 align:start position:0% package when<01:12:18.960> they<01:12:19.120> are<01:12:19.360> read<01:12:20.400> so<01:12:20.560> there's<01:12:20.800> no<01:12:21.040> concept 01:12:21.830 --> 01:12:21.840 align:start position:0% when they are read so there's no concept 01:12:21.840 --> 01:12:22.709 align:start position:0% when they are read so there's no concept of<01:12:22.080> a 01:12:22.709 --> 01:12:22.719 align:start position:0% of a 01:12:22.719 --> 01:12:25.990 align:start position:0% of a pat<01:12:23.040> of<01:12:23.199> a<01:12:23.360> symbol<01:12:24.080> without<01:12:24.400> a<01:12:24.480> package 01:12:25.990 --> 01:12:26.000 align:start position:0% pat of a symbol without a package 01:12:26.000 --> 01:12:28.870 align:start position:0% pat of a symbol without a package and<01:12:26.159> what<01:12:26.320> this<01:12:26.560> means<01:12:26.960> is<01:12:27.120> that<01:12:28.400> you<01:12:28.560> can<01:12:28.719> be 01:12:28.870 --> 01:12:28.880 align:start position:0% and what this means is that you can be 01:12:28.880 --> 01:12:30.550 align:start position:0% and what this means is that you can be looking<01:12:29.199> at<01:12:29.280> a<01:12:29.440> fragment<01:12:29.760> of<01:12:29.920> code 01:12:30.550 --> 01:12:30.560 align:start position:0% looking at a fragment of code 01:12:30.560 --> 01:12:33.270 align:start position:0% looking at a fragment of code in<01:12:30.719> a<01:12:30.800> particular<01:12:31.440> global<01:12:31.840> environment<01:12:33.120> and 01:12:33.270 --> 01:12:33.280 align:start position:0% in a particular global environment and 01:12:33.280 --> 01:12:35.270 align:start position:0% in a particular global environment and you<01:12:33.440> can<01:12:33.679> see<01:12:33.920> with<01:12:34.159> your<01:12:34.320> eyes<01:12:34.719> things<01:12:34.960> that 01:12:35.270 --> 01:12:35.280 align:start position:0% you can see with your eyes things that 01:12:35.280 --> 01:12:37.430 align:start position:0% you can see with your eyes things that look<01:12:35.520> like<01:12:35.920> they're<01:12:36.159> the<01:12:36.239> same<01:12:36.560> symbol<01:12:37.120> or<01:12:37.360> you 01:12:37.430 --> 01:12:37.440 align:start position:0% look like they're the same symbol or you 01:12:37.440 --> 01:12:39.990 align:start position:0% look like they're the same symbol or you would<01:12:37.600> assume<01:12:37.840> them<01:12:38.000> to<01:12:38.080> be<01:12:38.239> the<01:12:38.320> same<01:12:38.560> symbol 01:12:39.990 --> 01:12:40.000 align:start position:0% would assume them to be the same symbol 01:12:40.000 --> 01:12:42.390 align:start position:0% would assume them to be the same symbol um<01:12:40.640> like<01:12:40.880> you<01:12:41.040> would<01:12:41.199> assume<01:12:41.440> them<01:12:41.600> to<01:12:41.679> be<01:12:41.840> eq 01:12:42.390 --> 01:12:42.400 align:start position:0% um like you would assume them to be eq 01:12:42.400 --> 01:12:43.110 align:start position:0% um like you would assume them to be eq like<01:12:42.640> they're 01:12:43.110 --> 01:12:43.120 align:start position:0% like they're 01:12:43.120 --> 01:12:46.229 align:start position:0% like they're the<01:12:43.360> same<01:12:43.679> object<01:12:44.960> um<01:12:45.600> but<01:12:46.000> they<01:12:46.080> were 01:12:46.229 --> 01:12:46.239 align:start position:0% the same object um but they were 01:12:46.239 --> 01:12:48.149 align:start position:0% the same object um but they were actually<01:12:46.560> interned<01:12:47.040> in<01:12:47.199> different<01:12:47.520> packages 01:12:48.149 --> 01:12:48.159 align:start position:0% actually interned in different packages 01:12:48.159 --> 01:12:50.870 align:start position:0% actually interned in different packages and<01:12:48.320> so<01:12:48.480> they're<01:12:48.640> not<01:12:48.880> eq<01:12:50.239> all<01:12:50.480> even<01:12:50.719> though 01:12:50.870 --> 01:12:50.880 align:start position:0% and so they're not eq all even though 01:12:50.880 --> 01:12:52.709 align:start position:0% and so they're not eq all even though textually<01:12:51.520> they<01:12:51.679> may<01:12:51.840> appear<01:12:52.080> to<01:12:52.239> be 01:12:52.709 --> 01:12:52.719 align:start position:0% textually they may appear to be 01:12:52.719 --> 01:12:55.110 align:start position:0% textually they may appear to be eq<01:12:53.280> and<01:12:53.440> that's<01:12:53.679> context<01:12:54.159> dependent<01:12:54.880> and<01:12:55.040> you 01:12:55.110 --> 01:12:55.120 align:start position:0% eq and that's context dependent and you 01:12:55.120 --> 01:12:56.709 align:start position:0% eq and that's context dependent and you can<01:12:55.280> do<01:12:55.520> you<01:12:55.600> can<01:12:55.679> set<01:12:55.920> up<01:12:56.000> situations<01:12:56.560> like 01:12:56.709 --> 01:12:56.719 align:start position:0% can do you can set up situations like 01:12:56.719 --> 01:12:57.030 align:start position:0% can do you can set up situations like that 01:12:57.030 --> 01:12:57.040 align:start position:0% that 01:12:57.040 --> 01:12:59.590 align:start position:0% that by<01:12:57.280> um<01:12:58.159> you<01:12:58.239> know<01:12:58.400> switching<01:12:58.800> the<01:12:58.880> package<01:12:59.440> in 01:12:59.590 --> 01:12:59.600 align:start position:0% by um you know switching the package in 01:12:59.600 --> 01:13:00.870 align:start position:0% by um you know switching the package in a<01:12:59.679> let<01:12:59.840> binding<01:13:00.239> for<01:13:00.320> example<01:13:00.640> because<01:13:00.800> you 01:13:00.870 --> 01:13:00.880 align:start position:0% a let binding for example because you 01:13:00.880 --> 01:13:02.709 align:start position:0% a let binding for example because you can<01:13:00.960> dynamically<01:13:01.440> bind<01:13:01.760> the<01:13:01.840> current<01:13:02.080> package 01:13:02.709 --> 01:13:02.719 align:start position:0% can dynamically bind the current package 01:13:02.719 --> 01:13:05.750 align:start position:0% can dynamically bind the current package which<01:13:03.040> changes<01:13:04.320> there's<01:13:05.040> there's<01:13:05.280> just 01:13:05.750 --> 01:13:05.760 align:start position:0% which changes there's there's just 01:13:05.760 --> 01:13:09.750 align:start position:0% which changes there's there's just actually<01:13:06.000> that's<01:13:06.159> not<01:13:06.560> that's<01:13:06.800> not<01:13:07.600> not<01:13:07.920> a 01:13:09.750 --> 01:13:09.760 align:start position:0% actually that's not that's not not a 01:13:09.760 --> 01:13:11.590 align:start position:0% actually that's not that's not not a that<01:13:09.920> may<01:13:10.080> or<01:13:10.159> may<01:13:10.320> not<01:13:10.480> be<01:13:10.640> true<01:13:11.280> maybe<01:13:11.520> i 01:13:11.590 --> 01:13:11.600 align:start position:0% that may or may not be true maybe i 01:13:11.600 --> 01:13:13.510 align:start position:0% that may or may not be true maybe i don't<01:13:11.760> have<01:13:11.920> my<01:13:12.000> head<01:13:12.159> around<01:13:12.400> it<01:13:12.480> completely 01:13:13.510 --> 01:13:13.520 align:start position:0% don't have my head around it completely 01:13:13.520 --> 01:13:15.990 align:start position:0% don't have my head around it completely but<01:13:14.400> the<01:13:14.560> big<01:13:14.800> the<01:13:14.880> big<01:13:15.040> part<01:13:15.280> is<01:13:15.440> the<01:13:15.520> mutation 01:13:15.990 --> 01:13:16.000 align:start position:0% but the big the big part is the mutation 01:13:16.000 --> 01:13:18.310 align:start position:0% but the big the big part is the mutation of<01:13:16.080> the<01:13:16.840> package 01:13:18.310 --> 01:13:18.320 align:start position:0% of the package 01:13:18.320 --> 01:13:21.350 align:start position:0% of the package is<01:13:18.480> what<01:13:18.640> happens<01:13:19.040> so<01:13:19.199> when<01:13:19.440> you<01:13:19.520> read<01:13:19.840> a<01:13:21.199> when 01:13:21.350 --> 01:13:21.360 align:start position:0% is what happens so when you read a when 01:13:21.360 --> 01:13:23.510 align:start position:0% is what happens so when you read a when you<01:13:21.520> read<01:13:21.760> a<01:13:21.840> closure<01:13:22.320> symbol 01:13:23.510 --> 01:13:23.520 align:start position:0% you read a closure symbol 01:13:23.520 --> 01:13:27.510 align:start position:0% you read a closure symbol um<01:13:24.800> a<01:13:25.520> if<01:13:25.840> a<01:13:26.080> symbol<01:13:26.480> is<01:13:26.640> associated<01:13:27.280> with<01:13:27.440> a 01:13:27.510 --> 01:13:27.520 align:start position:0% um a if a symbol is associated with a 01:13:27.520 --> 01:13:29.189 align:start position:0% um a if a symbol is associated with a package<01:13:27.840> that<01:13:28.080> information<01:13:28.560> is<01:13:28.719> attached<01:13:29.120> to 01:13:29.189 --> 01:13:29.199 align:start position:0% package that information is attached to 01:13:29.199 --> 01:13:30.630 align:start position:0% package that information is attached to the<01:13:29.280> symbol<01:13:29.600> in<01:13:29.679> its<01:13:29.760> symbol<01:13:30.080> syntax<01:13:30.480> and<01:13:30.560> we 01:13:30.630 --> 01:13:30.640 align:start position:0% the symbol in its symbol syntax and we 01:13:30.640 --> 01:13:33.990 align:start position:0% the symbol in its symbol syntax and we have<01:13:30.719> a<01:13:30.800> namespace<01:13:31.280> qualified<01:13:31.760> symbols 01:13:33.990 --> 01:13:34.000 align:start position:0% have a namespace qualified symbols 01:13:34.000 --> 01:13:37.830 align:start position:0% have a namespace qualified symbols there's<01:13:34.239> also<01:13:34.560> a<01:13:34.640> concept<01:13:35.120> enclosure<01:13:35.679> of 01:13:37.830 --> 01:13:37.840 align:start position:0% there's also a concept enclosure of 01:13:37.840 --> 01:13:41.110 align:start position:0% there's also a concept enclosure of referred<01:13:39.280> symbols<01:13:39.920> which 01:13:41.110 --> 01:13:41.120 align:start position:0% referred symbols which 01:13:41.120 --> 01:13:43.030 align:start position:0% referred symbols which means<01:13:41.360> that<01:13:41.600> closure<01:13:42.080> will<01:13:42.320> interpret 01:13:43.030 --> 01:13:43.040 align:start position:0% means that closure will interpret 01:13:43.040 --> 01:13:44.390 align:start position:0% means that closure will interpret symbols 01:13:44.390 --> 01:13:44.400 align:start position:0% symbols 01:13:44.400 --> 01:13:46.790 align:start position:0% symbols that<01:13:44.640> it<01:13:44.719> reads<01:13:45.040> without<01:13:45.360> a<01:13:45.440> package<01:13:45.760> to<01:13:45.920> be<01:13:46.159> in 01:13:46.790 --> 01:13:46.800 align:start position:0% that it reads without a package to be in 01:13:46.800 --> 01:13:48.149 align:start position:0% that it reads without a package to be in a<01:13:46.960> particular<01:13:47.360> package<01:13:47.679> so<01:13:47.920> you<01:13:48.080> can 01:13:48.149 --> 01:13:48.159 align:start position:0% a particular package so you can 01:13:48.159 --> 01:13:49.750 align:start position:0% a particular package so you can establish<01:13:48.640> a<01:13:48.800> mapping 01:13:49.750 --> 01:13:49.760 align:start position:0% establish a mapping 01:13:49.760 --> 01:13:52.870 align:start position:0% establish a mapping between<01:13:50.480> a<01:13:51.280> packet<01:13:51.840> between<01:13:52.239> a<01:13:52.320> symbol<01:13:52.719> that 01:13:52.870 --> 01:13:52.880 align:start position:0% between a packet between a symbol that 01:13:52.880 --> 01:13:53.910 align:start position:0% between a packet between a symbol that doesn't<01:13:53.280> have 01:13:53.910 --> 01:13:53.920 align:start position:0% doesn't have 01:13:53.920 --> 01:13:57.350 align:start position:0% doesn't have a<01:13:54.080> package<01:13:54.640> and<01:13:54.960> a<01:13:55.120> package<01:13:56.880> and<01:13:57.120> you<01:13:57.199> can 01:13:57.350 --> 01:13:57.360 align:start position:0% a package and a package and you can 01:13:57.360 --> 01:13:59.110 align:start position:0% a package and a package and you can install<01:13:57.679> that<01:13:58.000> in<01:13:58.080> your<01:13:58.239> package 01:13:59.110 --> 01:13:59.120 align:start position:0% install that in your package 01:13:59.120 --> 01:14:01.510 align:start position:0% install that in your package if<01:13:59.199> that<01:13:59.360> makes<01:13:59.600> sense<01:14:00.560> but<01:14:00.960> the<01:14:01.120> symbols 01:14:01.510 --> 01:14:01.520 align:start position:0% if that makes sense but the symbols 01:14:01.520 --> 01:14:02.310 align:start position:0% if that makes sense but the symbols themselves 01:14:02.310 --> 01:14:02.320 align:start position:0% themselves 01:14:02.320 --> 01:14:04.390 align:start position:0% themselves are<01:14:02.640> not<01:14:02.960> installed<01:14:03.440> in<01:14:03.520> particular<01:14:03.920> packages 01:14:04.390 --> 01:14:04.400 align:start position:0% are not installed in particular packages 01:14:04.400 --> 01:14:05.350 align:start position:0% are not installed in particular packages the<01:14:04.640> the 01:14:05.350 --> 01:14:05.360 align:start position:0% the the 01:14:05.360 --> 01:14:07.910 align:start position:0% the the package<01:14:06.400> environment<01:14:06.960> is<01:14:07.040> not<01:14:07.280> mutated<01:14:07.760> by 01:14:07.910 --> 01:14:07.920 align:start position:0% package environment is not mutated by 01:14:07.920 --> 01:14:08.550 align:start position:0% package environment is not mutated by the<01:14:08.000> reader 01:14:08.550 --> 01:14:08.560 align:start position:0% the reader 01:14:08.560 --> 01:14:10.229 align:start position:0% the reader and<01:14:08.640> that<01:14:08.880> if<01:14:09.280> in<01:14:09.360> the<01:14:09.520> closure<01:14:09.760> rationale<01:14:10.159> i 01:14:10.229 --> 01:14:10.239 align:start position:0% and that if in the closure rationale i 01:14:10.239 --> 01:14:11.510 align:start position:0% and that if in the closure rationale i think<01:14:10.400> this<01:14:10.480> is<01:14:10.640> actually<01:14:11.120> mentioned 01:14:11.510 --> 01:14:11.520 align:start position:0% think this is actually mentioned 01:14:11.520 --> 01:14:14.390 align:start position:0% think this is actually mentioned specifically<01:14:12.159> rich<01:14:12.840> says<01:14:13.920> something<01:14:14.239> to<01:14:14.320> be 01:14:14.390 --> 01:14:14.400 align:start position:0% specifically rich says something to be 01:14:14.400 --> 01:14:15.910 align:start position:0% specifically rich says something to be effective<01:14:14.800> i<01:14:14.880> don't<01:14:15.040> like<01:14:15.360> that 01:14:15.910 --> 01:14:15.920 align:start position:0% effective i don't like that 01:14:15.920 --> 01:14:18.550 align:start position:0% effective i don't like that the<01:14:16.080> reader<01:14:16.719> necessitates<01:14:17.520> mutation<01:14:18.239> because 01:14:18.550 --> 01:14:18.560 align:start position:0% the reader necessitates mutation because 01:14:18.560 --> 01:14:20.709 align:start position:0% the reader necessitates mutation because you<01:14:18.640> know<01:14:18.800> he<01:14:18.880> believes<01:14:19.120> strongly<01:14:19.520> in<01:14:19.600> data 01:14:20.709 --> 01:14:20.719 align:start position:0% you know he believes strongly in data 01:14:20.719 --> 01:14:24.310 align:start position:0% you know he believes strongly in data and<01:14:21.040> he<01:14:21.199> believes<01:14:21.600> strongly<01:14:22.159> in 01:14:24.310 --> 01:14:24.320 align:start position:0% and he believes strongly in 01:14:24.320 --> 01:14:27.590 align:start position:0% and he believes strongly in the<01:14:24.560> idea<01:14:24.800> that<01:14:25.040> data<01:14:25.440> should<01:14:25.600> be 01:14:27.590 --> 01:14:27.600 align:start position:0% the idea that data should be 01:14:27.600 --> 01:14:29.430 align:start position:0% the idea that data should be require<01:14:28.239> data<01:14:28.480> should<01:14:28.640> not<01:14:28.800> necessitate 01:14:29.430 --> 01:14:29.440 align:start position:0% require data should not necessitate 01:14:29.440 --> 01:14:33.110 align:start position:0% require data should not necessitate interpretation<01:14:30.320> in<01:14:30.480> any<01:14:30.640> way 01:14:33.110 --> 01:14:33.120 align:start position:0% 01:14:33.120 --> 01:14:34.229 align:start position:0% that's<01:14:33.360> my<01:14:33.520> understanding<01:14:33.920> of<01:14:34.000> the<01:14:34.080> key 01:14:34.229 --> 01:14:34.239 align:start position:0% that's my understanding of the key 01:14:34.239 --> 01:14:35.350 align:start position:0% that's my understanding of the key difference<01:14:34.560> is<01:14:34.719> the<01:14:34.800> mutation<01:14:35.199> of<01:14:35.280> the 01:14:35.350 --> 01:14:35.360 align:start position:0% difference is the mutation of the 01:14:35.360 --> 01:14:41.669 align:start position:0% difference is the mutation of the packages<01:14:35.760> when<01:14:35.840> you're<01:14:36.000> reading<01:14:36.239> symbols 01:14:41.669 --> 01:14:41.679 align:start position:0% 01:14:41.679 --> 01:14:44.870 align:start position:0% follow-on<01:14:42.239> thought<01:14:43.040> is<01:14:43.280> that 01:14:44.870 --> 01:14:44.880 align:start position:0% follow-on thought is that 01:14:44.880 --> 01:14:48.149 align:start position:0% follow-on thought is that mutation<01:14:46.560> uh 01:14:48.149 --> 01:14:48.159 align:start position:0% mutation uh 01:14:48.159 --> 01:14:51.110 align:start position:0% mutation uh is<01:14:48.320> contextual<01:14:49.840> because<01:14:50.640> if<01:14:50.800> you<01:14:50.880> have<01:14:50.960> a 01:14:51.110 --> 01:14:51.120 align:start position:0% is contextual because if you have a 01:14:51.120 --> 01:14:52.229 align:start position:0% is contextual because if you have a functional<01:14:51.440> programming<01:14:51.840> language<01:14:52.159> and 01:14:52.229 --> 01:14:52.239 align:start position:0% functional programming language and 01:14:52.239 --> 01:14:53.590 align:start position:0% functional programming language and you're<01:14:52.400> doing<01:14:52.560> a<01:14:52.640> bunch<01:14:52.880> of<01:14:52.960> mutation 01:14:53.590 --> 01:14:53.600 align:start position:0% you're doing a bunch of mutation 01:14:53.600 --> 01:14:56.630 align:start position:0% you're doing a bunch of mutation inside<01:14:54.159> a<01:14:54.320> function<01:14:55.040> and<01:14:55.199> nobody<01:14:56.320> outside<01:14:56.560> of 01:14:56.630 --> 01:14:56.640 align:start position:0% inside a function and nobody outside of 01:14:56.640 --> 01:14:58.229 align:start position:0% inside a function and nobody outside of the<01:14:56.719> function<01:14:57.120> knows 01:14:58.229 --> 01:14:58.239 align:start position:0% the function knows 01:14:58.239 --> 01:15:01.990 align:start position:0% the function knows then<01:14:58.480> do<01:14:58.640> we<01:14:58.800> really<01:14:59.040> care<01:15:00.159> and<01:15:01.120> closure<01:15:01.520> that 01:15:01.990 --> 01:15:02.000 align:start position:0% then do we really care and closure that 01:15:02.000 --> 01:15:05.669 align:start position:0% then do we really care and closure that idea<01:15:02.320> is<01:15:02.400> delivered<01:15:03.040> with<01:15:03.440> transients 01:15:05.669 --> 01:15:05.679 align:start position:0% idea is delivered with transients 01:15:05.679 --> 01:15:07.910 align:start position:0% idea is delivered with transients but<01:15:06.080> i<01:15:06.159> think<01:15:06.400> it<01:15:06.560> illustrates<01:15:07.120> a<01:15:07.360> more<01:15:07.600> broad 01:15:07.910 --> 01:15:07.920 align:start position:0% but i think it illustrates a more broad 01:15:07.920 --> 01:15:09.510 align:start position:0% but i think it illustrates a more broad point<01:15:08.159> which<01:15:08.400> is<01:15:08.560> you<01:15:08.640> know<01:15:08.880> mutation<01:15:09.280> is<01:15:09.360> just 01:15:09.510 --> 01:15:09.520 align:start position:0% point which is you know mutation is just 01:15:09.520 --> 01:15:10.870 align:start position:0% point which is you know mutation is just a<01:15:09.600> matter<01:15:09.840> of<01:15:09.920> perspective<01:15:10.480> because<01:15:10.640> when<01:15:10.800> you 01:15:10.870 --> 01:15:10.880 align:start position:0% a matter of perspective because when you 01:15:10.880 --> 01:15:12.310 align:start position:0% a matter of perspective because when you run<01:15:11.040> a<01:15:11.120> program<01:15:11.440> you're<01:15:11.600> mutating<01:15:12.000> the<01:15:12.080> call 01:15:12.310 --> 01:15:12.320 align:start position:0% run a program you're mutating the call 01:15:12.320 --> 01:15:13.910 align:start position:0% run a program you're mutating the call stack<01:15:12.719> you're<01:15:12.880> mutating<01:15:13.280> pixels<01:15:13.679> on<01:15:13.840> the 01:15:13.910 --> 01:15:13.920 align:start position:0% stack you're mutating pixels on the 01:15:13.920 --> 01:15:14.870 align:start position:0% stack you're mutating pixels on the screen 01:15:14.870 --> 01:15:14.880 align:start position:0% screen 01:15:14.880 --> 01:15:17.430 align:start position:0% screen you<01:15:15.040> know<01:15:16.239> regardless<01:15:16.800> of<01:15:17.040> what<01:15:17.199> kind<01:15:17.360> of 01:15:17.430 --> 01:15:17.440 align:start position:0% you know regardless of what kind of 01:15:17.440 --> 01:15:18.630 align:start position:0% you know regardless of what kind of programming<01:15:17.840> you<01:15:18.000> claim<01:15:18.159> to<01:15:18.320> be 01:15:18.630 --> 01:15:18.640 align:start position:0% programming you claim to be 01:15:18.640 --> 01:15:21.270 align:start position:0% programming you claim to be they<01:15:18.960> claim<01:15:19.120> to<01:15:19.280> be<01:15:19.360> doing<01:15:20.159> um<01:15:20.719> so<01:15:20.880> it's<01:15:21.040> just<01:15:21.199> a 01:15:21.270 --> 01:15:21.280 align:start position:0% they claim to be doing um so it's just a 01:15:21.280 --> 01:15:22.310 align:start position:0% they claim to be doing um so it's just a question<01:15:21.520> of<01:15:21.679> perspective 01:15:22.310 --> 01:15:22.320 align:start position:0% question of perspective 01:15:22.320 --> 01:15:26.149 align:start position:0% question of perspective and<01:15:23.600> in<01:15:23.840> sickle<01:15:24.960> robert<01:15:25.360> strand 01:15:26.149 --> 01:15:26.159 align:start position:0% and in sickle robert strand 01:15:26.159 --> 01:15:29.350 align:start position:0% and in sickle robert strand the<01:15:26.480> professor<01:15:28.080> he<01:15:28.239> has<01:15:28.480> a<01:15:28.640> concept 01:15:29.350 --> 01:15:29.360 align:start position:0% the professor he has a concept 01:15:29.360 --> 01:15:33.030 align:start position:0% the professor he has a concept of<01:15:31.199> first<01:15:31.520> class<01:15:31.840> global<01:15:32.239> environments 01:15:33.030 --> 01:15:33.040 align:start position:0% of first class global environments 01:15:33.040 --> 01:15:35.270 align:start position:0% of first class global environments that<01:15:33.199> he's<01:15:33.280> written<01:15:33.520> a<01:15:33.600> paper<01:15:33.920> about<01:15:34.560> but<01:15:34.960> this 01:15:35.270 --> 01:15:35.280 align:start position:0% that he's written a paper about but this 01:15:35.280 --> 01:15:37.110 align:start position:0% that he's written a paper about but this encapsulates<01:15:36.159> the<01:15:36.239> mutation<01:15:36.719> that<01:15:36.880> i<01:15:36.960> just 01:15:37.110 --> 01:15:37.120 align:start position:0% encapsulates the mutation that i just 01:15:37.120 --> 01:15:38.390 align:start position:0% encapsulates the mutation that i just described 01:15:38.390 --> 01:15:38.400 align:start position:0% described 01:15:38.400 --> 01:15:41.189 align:start position:0% described into<01:15:39.280> another<01:15:39.679> concept<01:15:40.480> another<01:15:40.800> abstraction 01:15:41.189 --> 01:15:41.199 align:start position:0% into another concept another abstraction 01:15:41.199 --> 01:15:42.390 align:start position:0% into another concept another abstraction a<01:15:41.280> higher<01:15:41.520> level<01:15:41.760> abstraction<01:15:42.159> called<01:15:42.320> the 01:15:42.390 --> 01:15:42.400 align:start position:0% a higher level abstraction called the 01:15:42.400 --> 01:15:44.310 align:start position:0% a higher level abstraction called the first<01:15:42.640> class<01:15:42.800> global<01:15:43.120> environment 01:15:44.310 --> 01:15:44.320 align:start position:0% first class global environment 01:15:44.320 --> 01:15:46.709 align:start position:0% first class global environment and<01:15:44.400> so<01:15:44.640> now<01:15:45.120> yes<01:15:45.440> the<01:15:45.600> reader<01:15:46.000> mutates<01:15:46.560> but 01:15:46.709 --> 01:15:46.719 align:start position:0% and so now yes the reader mutates but 01:15:46.719 --> 01:15:48.630 align:start position:0% and so now yes the reader mutates but that<01:15:46.960> mutation<01:15:47.520> is<01:15:47.600> limited<01:15:48.080> to<01:15:48.239> the<01:15:48.480> first 01:15:48.630 --> 01:15:48.640 align:start position:0% that mutation is limited to the first 01:15:48.640 --> 01:15:50.550 align:start position:0% that mutation is limited to the first class<01:15:48.880> global<01:15:49.199> environment 01:15:50.550 --> 01:15:50.560 align:start position:0% class global environment 01:15:50.560 --> 01:15:52.709 align:start position:0% class global environment so<01:15:50.719> now<01:15:50.960> is<01:15:51.120> it<01:15:51.280> really<01:15:51.520> bad<01:15:51.840> i<01:15:51.920> don't<01:15:52.080> know 01:15:52.709 --> 01:15:52.719 align:start position:0% so now is it really bad i don't know 01:15:52.719 --> 01:15:54.070 align:start position:0% so now is it really bad i don't know again<01:15:52.960> it's<01:15:53.120> a<01:15:53.199> matter<01:15:53.520> of 01:15:54.070 --> 01:15:54.080 align:start position:0% again it's a matter of 01:15:54.080 --> 01:15:56.390 align:start position:0% again it's a matter of perspective<01:15:54.640> and<01:15:54.800> trade-offs<01:15:55.280> and<01:15:55.440> so<01:15:55.600> on<01:15:56.159> but 01:15:56.390 --> 01:15:56.400 align:start position:0% perspective and trade-offs and so on but 01:15:56.400 --> 01:15:58.149 align:start position:0% perspective and trade-offs and so on but uh<01:15:56.560> that's<01:15:56.880> that<01:15:57.120> that<01:15:57.360> that<01:15:57.679> first<01:15:57.920> class 01:15:58.149 --> 01:15:58.159 align:start position:0% uh that's that that that first class 01:15:58.159 --> 01:15:58.709 align:start position:0% uh that's that that that first class global 01:15:58.709 --> 01:15:58.719 align:start position:0% global 01:15:58.719 --> 01:15:59.910 align:start position:0% global environment<01:15:59.120> thing<01:15:59.280> is<01:15:59.360> kind<01:15:59.520> of<01:15:59.600> a<01:15:59.679> recent 01:15:59.910 --> 01:15:59.920 align:start position:0% environment thing is kind of a recent 01:15:59.920 --> 01:16:01.910 align:start position:0% environment thing is kind of a recent development<01:16:00.400> i<01:16:00.480> think<01:16:00.640> he<01:16:00.880> uh 01:16:01.910 --> 01:16:01.920 align:start position:0% development i think he uh 01:16:01.920 --> 01:16:05.430 align:start position:0% development i think he uh is<01:16:03.120> still<01:16:03.360> working<01:16:03.600> on<01:16:03.679> that<01:16:03.840> paper 01:16:05.430 --> 01:16:05.440 align:start position:0% is still working on that paper 01:16:05.440 --> 01:16:09.110 align:start position:0% is still working on that paper just<01:16:05.760> for<01:16:06.000> the<01:16:06.800> the<01:16:07.120> youtube<01:16:07.520> recording<01:16:08.239> um 01:16:09.110 --> 01:16:09.120 align:start position:0% just for the the youtube recording um 01:16:09.120 --> 01:16:11.030 align:start position:0% just for the the youtube recording um people<01:16:09.360> who<01:16:09.520> will<01:16:09.679> not<01:16:09.920> be<01:16:10.080> able<01:16:10.320> to<01:16:10.719> read<01:16:10.960> the 01:16:11.030 --> 01:16:11.040 align:start position:0% people who will not be able to read the 01:16:11.040 --> 01:16:12.470 align:start position:0% people who will not be able to read the chat<01:16:11.840> uh<01:16:12.080> dave 01:16:12.470 --> 01:16:12.480 align:start position:0% chat uh dave 01:16:12.480 --> 01:16:14.550 align:start position:0% chat uh dave dave<01:16:12.800> yarwood<01:16:13.199> has<01:16:13.360> this<01:16:13.760> this<01:16:14.159> way<01:16:14.400> of 01:16:14.550 --> 01:16:14.560 align:start position:0% dave yarwood has this this way of 01:16:14.560 --> 01:16:16.790 align:start position:0% dave yarwood has this this way of summarizing<01:16:15.440> at<01:16:15.520> this<01:16:15.840> point 01:16:16.790 --> 01:16:16.800 align:start position:0% summarizing at this point 01:16:16.800 --> 01:16:19.110 align:start position:0% summarizing at this point he<01:16:17.040> writes<01:16:17.360> uh<01:16:17.600> if<01:16:17.760> a<01:16:17.920> var<01:16:18.159> is<01:16:18.320> mutated<01:16:18.880> in<01:16:19.040> a 01:16:19.110 --> 01:16:19.120 align:start position:0% he writes uh if a var is mutated in a 01:16:19.120 --> 01:16:21.110 align:start position:0% he writes uh if a var is mutated in a forest<01:16:19.520> and<01:16:19.600> nothing<01:16:19.920> references<01:16:20.560> it 01:16:21.110 --> 01:16:21.120 align:start position:0% forest and nothing references it 01:16:21.120 --> 01:16:25.669 align:start position:0% forest and nothing references it does<01:16:21.280> the<01:16:21.440> value<01:16:21.760> change<01:16:22.719> right 01:16:25.669 --> 01:16:25.679 align:start position:0% 01:16:25.679 --> 01:16:29.830 align:start position:0% okay<01:16:26.080> and<01:16:26.159> then<01:16:26.320> we<01:16:26.480> have<01:16:26.800> a<01:16:27.120> nice 01:16:29.830 --> 01:16:29.840 align:start position:0% 01:16:29.840 --> 01:16:33.030 align:start position:0% careful 01:16:33.030 --> 01:16:33.040 align:start position:0% 01:16:33.040 --> 01:16:36.470 align:start position:0% question<01:16:33.760> uh<01:16:35.360> yeah<01:16:35.760> so 01:16:36.470 --> 01:16:36.480 align:start position:0% question uh yeah so 01:16:36.480 --> 01:16:38.630 align:start position:0% question uh yeah so i<01:16:36.640> think<01:16:36.800> we<01:16:37.040> we<01:16:37.199> have<01:16:37.440> to<01:16:37.600> talk<01:16:37.840> about<01:16:38.159> it<01:16:38.320> even 01:16:38.630 --> 01:16:38.640 align:start position:0% i think we we have to talk about it even 01:16:38.640 --> 01:16:39.669 align:start position:0% i think we we have to talk about it even even<01:16:38.960> though 01:16:39.669 --> 01:16:39.679 align:start position:0% even though 01:16:39.679 --> 01:16:43.030 align:start position:0% even though uh<01:16:40.080> if<01:16:40.480> you<01:16:41.040> if<01:16:41.199> you<01:16:41.280> don't<01:16:42.239> i<01:16:42.400> mean<01:16:42.560> feel<01:16:42.800> free 01:16:43.030 --> 01:16:43.040 align:start position:0% uh if you if you don't i mean feel free 01:16:43.040 --> 01:16:43.430 align:start position:0% uh if you if you don't i mean feel free to 01:16:43.430 --> 01:16:43.440 align:start position:0% to 01:16:43.440 --> 01:16:46.550 align:start position:0% to to<01:16:43.760> uh<01:16:44.159> to<01:16:44.560> skip<01:16:44.960> it<01:16:45.199> but<01:16:45.520> uh<01:16:46.159> it<01:16:46.320> is 01:16:46.550 --> 01:16:46.560 align:start position:0% to uh to skip it but uh it is 01:16:46.560 --> 01:16:47.350 align:start position:0% to uh to skip it but uh it is interesting 01:16:47.350 --> 01:16:47.360 align:start position:0% interesting 01:16:47.360 --> 01:16:49.910 align:start position:0% interesting i<01:16:47.600> find<01:16:48.000> i<01:16:48.239> myself<01:16:48.800> also<01:16:49.120> a<01:16:49.199> bit<01:16:49.440> interested<01:16:49.760> in 01:16:49.910 --> 01:16:49.920 align:start position:0% i find i myself also a bit interested in 01:16:49.920 --> 01:16:51.110 align:start position:0% i find i myself also a bit interested in what<01:16:50.000> you<01:16:50.159> might<01:16:50.400> say 01:16:51.110 --> 01:16:51.120 align:start position:0% what you might say 01:16:51.120 --> 01:16:54.229 align:start position:0% what you might say uh<01:16:51.440> on<01:16:51.520> this<01:16:51.760> topic<01:16:52.320> and<01:16:52.560> that<01:16:52.800> is<01:16:52.960> the<01:16:53.360> uh 01:16:54.229 --> 01:16:54.239 align:start position:0% uh on this topic and that is the uh 01:16:54.239 --> 01:16:57.669 align:start position:0% uh on this topic and that is the uh uh<01:16:54.560> lisp<01:16:54.880> one<01:16:55.120> of<01:16:55.280> us<01:16:55.520> at<01:16:55.679> least<01:16:56.080> two<01:16:56.719> so<01:16:57.040> um 01:16:57.669 --> 01:16:57.679 align:start position:0% uh lisp one of us at least two so um 01:16:57.679 --> 01:17:00.709 align:start position:0% uh lisp one of us at least two so um right<01:16:58.719> well<01:16:59.840> i<01:17:00.000> think<01:17:00.159> you<01:17:00.239> have<01:17:00.320> to<01:17:00.400> address 01:17:00.709 --> 01:17:00.719 align:start position:0% right well i think you have to address 01:17:00.719 --> 01:17:01.990 align:start position:0% right well i think you have to address the<01:17:00.800> fact<01:17:00.960> that<01:17:01.199> closure 01:17:01.990 --> 01:17:02.000 align:start position:0% the fact that closure 01:17:02.000 --> 01:17:04.229 align:start position:0% the fact that closure that<01:17:02.239> uh<01:17:02.560> that<01:17:02.800> rich<01:17:03.040> hickey<01:17:03.679> coming<01:17:04.000> from 01:17:04.229 --> 01:17:04.239 align:start position:0% that uh that rich hickey coming from 01:17:04.239 --> 01:17:05.510 align:start position:0% that uh that rich hickey coming from commonly 01:17:05.510 --> 01:17:05.520 align:start position:0% commonly 01:17:05.520 --> 01:17:09.110 align:start position:0% commonly corrected<01:17:08.320> i<01:17:08.480> think<01:17:08.560> there's<01:17:08.719> an<01:17:08.800> argument 01:17:09.110 --> 01:17:09.120 align:start position:0% corrected i think there's an argument 01:17:09.120 --> 01:17:10.870 align:start position:0% corrected i think there's an argument that<01:17:09.280> he<01:17:09.360> made<01:17:09.520> it<01:17:09.600> worse 01:17:10.870 --> 01:17:10.880 align:start position:0% that he made it worse 01:17:10.880 --> 01:17:16.229 align:start position:0% that he made it worse so<01:17:11.040> let<01:17:11.199> me<01:17:12.640> know<01:17:13.280> this<01:17:13.440> is<01:17:13.520> a<01:17:13.600> fun<01:17:14.840> topic<01:17:15.920> no<01:17:16.080> so 01:17:16.229 --> 01:17:16.239 align:start position:0% so let me know this is a fun topic no so 01:17:16.239 --> 01:17:17.910 align:start position:0% so let me know this is a fun topic no so this<01:17:16.400> is<01:17:16.560> another<01:17:16.880> matter<01:17:17.199> of<01:17:17.280> perspective<01:17:17.840> i 01:17:17.910 --> 01:17:17.920 align:start position:0% this is another matter of perspective i 01:17:17.920 --> 01:17:18.630 align:start position:0% this is another matter of perspective i think<01:17:18.239> um 01:17:18.630 --> 01:17:18.640 align:start position:0% think um 01:17:18.640 --> 01:17:20.149 align:start position:0% think um you<01:17:18.719> know<01:17:18.880> there<01:17:19.040> is<01:17:19.199> a<01:17:19.360> traditional<01:17:19.920> there's 01:17:20.149 --> 01:17:20.159 align:start position:0% you know there is a traditional there's 01:17:20.159 --> 01:17:21.990 align:start position:0% you know there is a traditional there's a<01:17:20.239> classical 01:17:21.990 --> 01:17:22.000 align:start position:0% a classical 01:17:22.000 --> 01:17:23.830 align:start position:0% a classical understanding<01:17:22.640> of<01:17:22.719> what<01:17:22.960> lisp<01:17:23.199> one<01:17:23.440> versus 01:17:23.830 --> 01:17:23.840 align:start position:0% understanding of what lisp one versus 01:17:23.840 --> 01:17:25.750 align:start position:0% understanding of what lisp one versus lisp<01:17:24.159> two<01:17:24.400> is<01:17:24.560> and<01:17:24.719> it's<01:17:25.040> limited 01:17:25.750 --> 01:17:25.760 align:start position:0% lisp two is and it's limited 01:17:25.760 --> 01:17:31.189 align:start position:0% lisp two is and it's limited to<01:17:26.880> uh<01:17:27.280> the<01:17:27.360> interpretation<01:17:28.000> of<01:17:28.840> symbols 01:17:31.189 --> 01:17:31.199 align:start position:0% to uh the interpretation of symbols 01:17:31.199 --> 01:17:34.390 align:start position:0% to uh the interpretation of symbols but<01:17:33.040> you<01:17:33.199> know<01:17:33.280> there's<01:17:33.520> a<01:17:33.600> lot<01:17:33.760> of<01:17:33.840> dimensions 01:17:34.390 --> 01:17:34.400 align:start position:0% but you know there's a lot of dimensions 01:17:34.400 --> 01:17:35.669 align:start position:0% but you know there's a lot of dimensions of<01:17:34.480> interpretation<01:17:35.120> in<01:17:35.199> the<01:17:35.280> programming 01:17:35.669 --> 01:17:35.679 align:start position:0% of interpretation in the programming 01:17:35.679 --> 01:17:37.189 align:start position:0% of interpretation in the programming language<01:17:36.000> obviously 01:17:37.189 --> 01:17:37.199 align:start position:0% language obviously 01:17:37.199 --> 01:17:40.870 align:start position:0% language obviously and<01:17:38.080> if<01:17:38.320> you<01:17:39.199> add<01:17:39.600> other<01:17:39.920> types<01:17:40.159> of<01:17:40.320> atomic 01:17:40.870 --> 01:17:40.880 align:start position:0% and if you add other types of atomic 01:17:40.880 --> 01:17:41.910 align:start position:0% and if you add other types of atomic values 01:17:41.910 --> 01:17:41.920 align:start position:0% values 01:17:41.920 --> 01:17:47.189 align:start position:0% values you<01:17:42.000> know<01:17:42.239> atoms<01:17:42.880> to<01:17:43.040> this<01:17:43.280> discussion<01:17:44.880> then 01:17:47.189 --> 01:17:47.199 align:start position:0% you know atoms to this discussion then 01:17:47.199 --> 01:17:50.630 align:start position:0% you know atoms to this discussion then for<01:17:47.440> me<01:17:48.159> this<01:17:48.480> point<01:17:48.800> becomes<01:17:49.360> less<01:17:49.679> important 01:17:50.630 --> 01:17:50.640 align:start position:0% for me this point becomes less important 01:17:50.640 --> 01:17:53.590 align:start position:0% for me this point becomes less important so<01:17:50.800> for<01:17:51.040> example<01:17:52.400> is<01:17:52.560> closure<01:17:52.880> a<01:17:52.960> list<01:17:53.199> one 01:17:53.590 --> 01:17:53.600 align:start position:0% so for example is closure a list one 01:17:53.600 --> 01:17:55.430 align:start position:0% so for example is closure a list one let's<01:17:53.760> think<01:17:53.920> about<01:17:54.159> this 01:17:55.430 --> 01:17:55.440 align:start position:0% let's think about this 01:17:55.440 --> 01:17:57.510 align:start position:0% let's think about this what<01:17:55.600> does<01:17:55.760> a<01:17:55.840> symbol<01:17:56.159> mean<01:17:56.800> well<01:17:57.120> a<01:17:57.199> symbol 01:17:57.510 --> 01:17:57.520 align:start position:0% what does a symbol mean well a symbol 01:17:57.520 --> 01:17:59.990 align:start position:0% what does a symbol mean well a symbol can<01:17:57.679> stand<01:17:58.080> for<01:17:58.239> a<01:17:58.320> locally<01:17:58.719> bound<01:17:58.960> function 01:17:59.990 --> 01:18:00.000 align:start position:0% can stand for a locally bound function 01:18:00.000 --> 01:18:02.630 align:start position:0% can stand for a locally bound function but<01:18:00.159> it<01:18:00.239> can<01:18:00.400> also<01:18:00.719> stand<01:18:00.880> for<01:18:01.040> a<01:18:01.120> java<01:18:01.520> class 01:18:02.630 --> 01:18:02.640 align:start position:0% but it can also stand for a java class 01:18:02.640 --> 01:18:03.189 align:start position:0% but it can also stand for a java class right 01:18:03.189 --> 01:18:03.199 align:start position:0% right 01:18:03.199 --> 01:18:04.950 align:start position:0% right because<01:18:03.600> java<01:18:03.920> class<01:18:04.239> names<01:18:04.480> and<01:18:04.640> closure 01:18:04.950 --> 01:18:04.960 align:start position:0% because java class names and closure 01:18:04.960 --> 01:18:07.430 align:start position:0% because java class names and closure symbols<01:18:06.080> intersect 01:18:07.430 --> 01:18:07.440 align:start position:0% symbols intersect 01:18:07.440 --> 01:18:10.070 align:start position:0% symbols intersect and<01:18:07.679> so<01:18:08.400> there<01:18:08.719> is<01:18:08.880> an<01:18:09.040> if<01:18:09.199> statement<01:18:09.520> there<01:18:09.920> in 01:18:10.070 --> 01:18:10.080 align:start position:0% and so there is an if statement there in 01:18:10.080 --> 01:18:11.830 align:start position:0% and so there is an if statement there in the<01:18:10.159> reader 01:18:11.830 --> 01:18:11.840 align:start position:0% the reader 01:18:11.840 --> 01:18:15.350 align:start position:0% the reader which<01:18:12.080> is<01:18:12.159> a<01:18:12.239> source<01:18:12.480> of<01:18:12.560> complexity 01:18:15.350 --> 01:18:15.360 align:start position:0% 01:18:15.360 --> 01:18:18.390 align:start position:0% keywords 01:18:18.390 --> 01:18:18.400 align:start position:0% 01:18:18.400 --> 01:18:22.470 align:start position:0% in<01:18:18.640> practice<01:18:21.280> closure<01:18:21.760> libraries 01:18:22.470 --> 01:18:22.480 align:start position:0% in practice closure libraries 01:18:22.480 --> 01:18:24.950 align:start position:0% in practice closure libraries lean<01:18:22.800> pretty<01:18:23.040> heavily<01:18:23.440> on<01:18:23.600> keywords<01:18:24.159> and<01:18:24.400> even 01:18:24.950 --> 01:18:24.960 align:start position:0% lean pretty heavily on keywords and even 01:18:24.960 --> 01:18:27.189 align:start position:0% lean pretty heavily on keywords and even use<01:18:25.360> keywords<01:18:25.840> to<01:18:26.000> invent<01:18:26.480> new<01:18:26.800> naming 01:18:27.189 --> 01:18:27.199 align:start position:0% use keywords to invent new naming 01:18:27.199 --> 01:18:27.750 align:start position:0% use keywords to invent new naming schemes 01:18:27.750 --> 01:18:27.760 align:start position:0% schemes 01:18:27.760 --> 01:18:30.550 align:start position:0% schemes like<01:18:28.000> to<01:18:28.159> name<01:18:28.480> for<01:18:28.640> example<01:18:29.040> subscriptions 01:18:30.550 --> 01:18:30.560 align:start position:0% like to name for example subscriptions 01:18:30.560 --> 01:18:31.430 align:start position:0% like to name for example subscriptions or 01:18:31.430 --> 01:18:31.440 align:start position:0% or 01:18:31.440 --> 01:18:35.430 align:start position:0% or conditions<01:18:32.159> like<01:18:32.400> the<01:18:32.560> x<01:18:32.960> info<01:18:33.440> function 01:18:35.430 --> 01:18:35.440 align:start position:0% conditions like the x info function 01:18:35.440 --> 01:18:37.030 align:start position:0% conditions like the x info function a<01:18:35.520> lot<01:18:35.679> of<01:18:35.760> people<01:18:36.080> pass<01:18:36.320> that<01:18:36.480> a<01:18:36.560> keyword<01:18:36.960> to 01:18:37.030 --> 01:18:37.040 align:start position:0% a lot of people pass that a keyword to 01:18:37.040 --> 01:18:38.470 align:start position:0% a lot of people pass that a keyword to indicate 01:18:38.470 --> 01:18:38.480 align:start position:0% indicate 01:18:38.480 --> 01:18:40.149 align:start position:0% indicate you<01:18:38.640> know<01:18:38.800> to<01:18:38.960> identify<01:18:39.440> the<01:18:39.600> condition<01:18:40.000> or 01:18:40.149 --> 01:18:40.159 align:start position:0% you know to identify the condition or 01:18:40.159 --> 01:18:41.750 align:start position:0% you know to identify the condition or the<01:18:40.239> exception<01:18:40.640> they're<01:18:40.800> throwing 01:18:41.750 --> 01:18:41.760 align:start position:0% the exception they're throwing 01:18:41.760 --> 01:18:43.590 align:start position:0% the exception they're throwing so<01:18:41.920> anytime<01:18:42.320> people<01:18:42.640> use<01:18:42.800> those<01:18:43.040> identifiers 01:18:43.590 --> 01:18:43.600 align:start position:0% so anytime people use those identifiers 01:18:43.600 --> 01:18:45.189 align:start position:0% so anytime people use those identifiers they've<01:18:43.920> created<01:18:44.320> their<01:18:44.480> own<01:18:44.640> global 01:18:45.189 --> 01:18:45.199 align:start position:0% they've created their own global 01:18:45.199 --> 01:18:47.270 align:start position:0% they've created their own global naming<01:18:45.520> scheme<01:18:45.840> with<01:18:46.000> their<01:18:46.239> own<01:18:46.560> interpretat 01:18:47.270 --> 01:18:47.280 align:start position:0% naming scheme with their own interpretat 01:18:47.280 --> 01:18:50.630 align:start position:0% naming scheme with their own interpretat you<01:18:47.360> know<01:18:47.600> their<01:18:47.760> own<01:18:47.920> semantics<01:18:48.480> there 01:18:50.630 --> 01:18:50.640 align:start position:0% you know their own semantics there 01:18:50.640 --> 01:18:53.990 align:start position:0% you know their own semantics there so<01:18:50.800> that's<01:18:51.040> kind<01:18:51.199> of<01:18:51.360> a<01:18:51.440> dimension<01:18:51.920> of<01:18:52.080> naming 01:18:53.990 --> 01:18:54.000 align:start position:0% so that's kind of a dimension of naming 01:18:54.000 --> 01:18:57.110 align:start position:0% so that's kind of a dimension of naming there<01:18:54.159> is<01:18:54.320> the<01:18:55.120> there<01:18:55.360> is<01:18:55.600> the<01:18:56.239> namespace<01:18:56.960> of 01:18:57.110 --> 01:18:57.120 align:start position:0% there is the there is the namespace of 01:18:57.120 --> 01:18:58.149 align:start position:0% there is the there is the namespace of reader<01:18:57.440> macros 01:18:58.149 --> 01:18:58.159 align:start position:0% reader macros 01:18:58.159 --> 01:19:00.630 align:start position:0% reader macros enclosure<01:18:58.640> they're<01:18:58.800> data<01:18:59.040> literals<01:19:00.159> but<01:19:00.400> any 01:19:00.630 --> 01:19:00.640 align:start position:0% enclosure they're data literals but any 01:19:00.640 --> 01:19:01.350 align:start position:0% enclosure they're data literals but any package 01:19:01.350 --> 01:19:01.360 align:start position:0% package 01:19:01.360 --> 01:19:03.030 align:start position:0% package that<01:19:01.520> you<01:19:01.679> load<01:19:01.920> into<01:19:02.080> the<01:19:02.239> classpath 01:19:03.030 --> 01:19:03.040 align:start position:0% that you load into the classpath 01:19:03.040 --> 01:19:04.470 align:start position:0% that you load into the classpath enclosure<01:19:03.760> has<01:19:04.000> it<01:19:04.159> can 01:19:04.470 --> 01:19:04.480 align:start position:0% enclosure has it can 01:19:04.480 --> 01:19:06.390 align:start position:0% enclosure has it can provide<01:19:04.800> a<01:19:05.000> datareaders.clj<01:19:06.000> file<01:19:06.239> which 01:19:06.390 --> 01:19:06.400 align:start position:0% provide a datareaders.clj file which 01:19:06.400 --> 01:19:07.990 align:start position:0% provide a datareaders.clj file which will<01:19:06.560> automatically<01:19:07.040> get<01:19:07.280> executed<01:19:07.840> and 01:19:07.990 --> 01:19:08.000 align:start position:0% will automatically get executed and 01:19:08.000 --> 01:19:10.229 align:start position:0% will automatically get executed and contribute<01:19:08.560> a<01:19:08.640> data<01:19:08.880> literal<01:19:09.280> syntax<01:19:09.840> to 01:19:10.229 --> 01:19:10.239 align:start position:0% contribute a data literal syntax to 01:19:10.239 --> 01:19:13.270 align:start position:0% contribute a data literal syntax to closure<01:19:11.600> and<01:19:12.159> those<01:19:12.400> have<01:19:12.560> an<01:19:12.719> opportunity<01:19:13.120> to 01:19:13.270 --> 01:19:13.280 align:start position:0% closure and those have an opportunity to 01:19:13.280 --> 01:19:15.110 align:start position:0% closure and those have an opportunity to conflict<01:19:13.760> so<01:19:14.080> i<01:19:14.159> think<01:19:14.320> we're<01:19:14.400> at<01:19:14.480> a<01:19:14.560> lisp<01:19:14.880> four 01:19:15.110 --> 01:19:15.120 align:start position:0% conflict so i think we're at a lisp four 01:19:15.120 --> 01:19:17.910 align:start position:0% conflict so i think we're at a lisp four now 01:19:17.910 --> 01:19:17.920 align:start position:0% 01:19:17.920 --> 01:19:22.470 align:start position:0% so<01:19:18.719> my<01:19:18.880> point<01:19:19.120> with<01:19:19.199> this<01:19:19.440> is<01:19:19.640> that<01:19:20.840> uh 01:19:22.470 --> 01:19:22.480 align:start position:0% so my point with this is that uh 01:19:22.480 --> 01:19:25.910 align:start position:0% so my point with this is that uh in<01:19:23.199> my<01:19:23.520> view<01:19:23.840> now<01:19:24.560> this<01:19:24.800> is<01:19:24.960> actually<01:19:25.440> a<01:19:25.520> really 01:19:25.910 --> 01:19:25.920 align:start position:0% in my view now this is actually a really 01:19:25.920 --> 01:19:26.790 align:start position:0% in my view now this is actually a really small 01:19:26.790 --> 01:19:26.800 align:start position:0% small 01:19:26.800 --> 01:19:28.950 align:start position:0% small and<01:19:27.199> maybe<01:19:27.600> even<01:19:28.000> not<01:19:28.239> very<01:19:28.480> important 01:19:28.950 --> 01:19:28.960 align:start position:0% and maybe even not very important 01:19:28.960 --> 01:19:31.510 align:start position:0% and maybe even not very important distinction<01:19:29.440> between<01:19:29.760> these<01:19:30.000> two<01:19:30.239> things 01:19:31.510 --> 01:19:31.520 align:start position:0% distinction between these two things 01:19:31.520 --> 01:19:33.590 align:start position:0% distinction between these two things um<01:19:32.239> because<01:19:32.480> the<01:19:32.640> same<01:19:32.880> is<01:19:33.040> true<01:19:33.199> for<01:19:33.360> common 01:19:33.590 --> 01:19:33.600 align:start position:0% um because the same is true for common 01:19:33.600 --> 01:19:35.189 align:start position:0% um because the same is true for common lisp<01:19:33.920> if<01:19:34.000> you<01:19:34.080> go<01:19:34.320> and<01:19:34.400> catalog<01:19:34.960> all<01:19:35.040> the 01:19:35.189 --> 01:19:35.199 align:start position:0% lisp if you go and catalog all the 01:19:35.199 --> 01:19:37.430 align:start position:0% lisp if you go and catalog all the different 01:19:37.430 --> 01:19:37.440 align:start position:0% different 01:19:37.440 --> 01:19:39.030 align:start position:0% different things<01:19:37.679> that<01:19:37.840> can<01:19:38.000> be<01:19:38.159> named<01:19:38.480> globally<01:19:38.880> or 01:19:39.030 --> 01:19:39.040 align:start position:0% things that can be named globally or 01:19:39.040 --> 01:19:40.390 align:start position:0% things that can be named globally or interfere<01:19:39.440> with<01:19:39.600> each<01:19:39.760> other<01:19:39.920> at<01:19:40.000> a<01:19:40.080> global 01:19:40.390 --> 01:19:40.400 align:start position:0% interfere with each other at a global 01:19:40.400 --> 01:19:41.990 align:start position:0% interfere with each other at a global level 01:19:41.990 --> 01:19:42.000 align:start position:0% level 01:19:42.000 --> 01:19:45.350 align:start position:0% level it's<01:19:42.159> a<01:19:42.239> lot<01:19:42.400> of<01:19:42.480> stuff<01:19:43.280> and 01:19:45.350 --> 01:19:45.360 align:start position:0% it's a lot of stuff and 01:19:45.360 --> 01:19:47.030 align:start position:0% it's a lot of stuff and i'm<01:19:45.600> not<01:19:45.840> sure<01:19:46.080> you<01:19:46.239> can<01:19:46.320> get<01:19:46.480> away<01:19:46.800> from 01:19:47.030 --> 01:19:47.040 align:start position:0% i'm not sure you can get away from 01:19:47.040 --> 01:19:48.229 align:start position:0% i'm not sure you can get away from having<01:19:47.360> a<01:19:47.440> lot<01:19:47.520> of<01:19:47.679> stuff<01:19:47.920> i<01:19:48.000> think<01:19:48.080> you're 01:19:48.229 --> 01:19:48.239 align:start position:0% having a lot of stuff i think you're 01:19:48.239 --> 01:19:50.149 align:start position:0% having a lot of stuff i think you're just<01:19:48.400> going<01:19:48.480> to<01:19:48.560> have<01:19:48.640> a<01:19:48.719> lot<01:19:48.880> of<01:19:48.960> stuff 01:19:50.149 --> 01:19:50.159 align:start position:0% just going to have a lot of stuff 01:19:50.159 --> 01:19:54.310 align:start position:0% just going to have a lot of stuff um<01:19:51.679> for<01:19:51.840> my<01:19:52.000> part<01:19:52.400> i 01:19:54.310 --> 01:19:54.320 align:start position:0% um for my part i 01:19:54.320 --> 01:19:56.550 align:start position:0% um for my part i i<01:19:54.480> think<01:19:54.719> it<01:19:55.040> the<01:19:55.280> lisp2<01:19:55.840> thing<01:19:56.000> contributes 01:19:56.550 --> 01:19:56.560 align:start position:0% i think it the lisp2 thing contributes 01:19:56.560 --> 01:19:58.310 align:start position:0% i think it the lisp2 thing contributes to<01:19:56.640> the<01:19:56.800> old-timey<01:19:57.280> feel<01:19:57.679> which<01:19:57.920> i 01:19:58.310 --> 01:19:58.320 align:start position:0% to the old-timey feel which i 01:19:58.320 --> 01:20:00.229 align:start position:0% to the old-timey feel which i enjoy<01:19:58.800> i<01:19:58.960> haven't<01:19:59.199> written<01:19:59.440> enough<01:19:59.679> lisp<01:20:00.000> code 01:20:00.229 --> 01:20:00.239 align:start position:0% enjoy i haven't written enough lisp code 01:20:00.239 --> 01:20:01.590 align:start position:0% enjoy i haven't written enough lisp code to<01:20:00.400> leverage<01:20:00.880> any<01:20:01.040> of<01:20:01.120> the 01:20:01.590 --> 01:20:01.600 align:start position:0% to leverage any of the 01:20:01.600 --> 01:20:04.870 align:start position:0% to leverage any of the purported<01:20:02.080> benefits<01:20:02.480> i<01:20:02.560> don't<01:20:02.840> think<01:20:04.320> but<01:20:04.640> it 01:20:04.870 --> 01:20:04.880 align:start position:0% purported benefits i don't think but it 01:20:04.880 --> 01:20:05.830 align:start position:0% purported benefits i don't think but it certainly<01:20:05.280> i<01:20:05.360> don't 01:20:05.830 --> 01:20:05.840 align:start position:0% certainly i don't 01:20:05.840 --> 01:20:07.189 align:start position:0% certainly i don't in<01:20:06.000> the<01:20:06.080> little<01:20:06.239> list<01:20:06.480> code<01:20:06.719> i've<01:20:06.800> written<01:20:07.040> it 01:20:07.189 --> 01:20:07.199 align:start position:0% in the little list code i've written it 01:20:07.199 --> 01:20:11.030 align:start position:0% in the little list code i've written it i<01:20:07.600> don't<01:20:07.760> feel<01:20:07.920> like<01:20:08.080> it's<01:20:08.159> gotten<01:20:08.480> in<01:20:08.560> my<01:20:08.719> way 01:20:11.030 --> 01:20:11.040 align:start position:0% 01:20:11.040 --> 01:20:15.430 align:start position:0% but<01:20:11.199> that<01:20:11.440> that<01:20:11.679> is<01:20:11.760> just<01:20:11.920> my<01:20:12.159> opinion 01:20:15.430 --> 01:20:15.440 align:start position:0% 01:20:15.440 --> 01:20:18.629 align:start position:0% right<01:20:17.120> which<01:20:17.360> is<01:20:17.520> interesting<01:20:18.000> because<01:20:18.320> i<01:20:18.480> i 01:20:18.629 --> 01:20:18.639 align:start position:0% right which is interesting because i i 01:20:18.639 --> 01:20:18.950 align:start position:0% right which is interesting because i i can 01:20:18.950 --> 01:20:18.960 align:start position:0% can 01:20:18.960 --> 01:20:21.430 align:start position:0% can i<01:20:19.120> can<01:20:19.360> uh<01:20:19.600> testify<01:20:20.080> myself<01:20:20.639> that<01:20:20.880> uh<01:20:21.040> the<01:20:21.199> same 01:20:21.430 --> 01:20:21.440 align:start position:0% i can uh testify myself that uh the same 01:20:21.440 --> 01:20:23.350 align:start position:0% i can uh testify myself that uh the same way<01:20:21.679> that<01:20:22.000> uh<01:20:22.239> you<01:20:22.400> were 01:20:23.350 --> 01:20:23.360 align:start position:0% way that uh you were 01:20:23.360 --> 01:20:25.910 align:start position:0% way that uh you were uh<01:20:23.600> drawn<01:20:24.000> to<01:20:24.320> common<01:20:24.639> lisp<01:20:25.120> in<01:20:25.360> in<01:20:25.520> this<01:20:25.679> kind 01:20:25.910 --> 01:20:25.920 align:start position:0% uh drawn to common lisp in in this kind 01:20:25.920 --> 01:20:27.030 align:start position:0% uh drawn to common lisp in in this kind of<01:20:26.159> uh 01:20:27.030 --> 01:20:27.040 align:start position:0% of uh 01:20:27.040 --> 01:20:28.950 align:start position:0% of uh oh<01:20:27.440> this<01:20:27.679> looks<01:20:27.920> interesting<01:20:28.480> let's<01:20:28.719> have<01:20:28.800> a 01:20:28.950 --> 01:20:28.960 align:start position:0% oh this looks interesting let's have a 01:20:28.960 --> 01:20:30.229 align:start position:0% oh this looks interesting let's have a closer<01:20:29.280> look<01:20:29.440> at<01:20:29.600> it 01:20:30.229 --> 01:20:30.239 align:start position:0% closer look at it 01:20:30.239 --> 01:20:33.510 align:start position:0% closer look at it i<01:20:31.040> uh<01:20:31.679> i<01:20:31.920> have<01:20:32.080> this<01:20:32.320> kind<01:20:32.480> of<01:20:32.639> hobby<01:20:33.040> where<01:20:33.280> i 01:20:33.510 --> 01:20:33.520 align:start position:0% i uh i have this kind of hobby where i 01:20:33.520 --> 01:20:33.990 align:start position:0% i uh i have this kind of hobby where i uh 01:20:33.990 --> 01:20:34.000 align:start position:0% uh 01:20:34.000 --> 01:20:37.350 align:start position:0% uh study<01:20:34.639> scheme<01:20:35.120> implementations<01:20:36.000> or<01:20:36.480> at<01:20:36.719> least 01:20:37.350 --> 01:20:37.360 align:start position:0% study scheme implementations or at least 01:20:37.360 --> 01:20:39.510 align:start position:0% study scheme implementations or at least uh<01:20:37.760> try<01:20:38.000> to<01:20:38.159> follow<01:20:38.480> what's<01:20:39.040> happening<01:20:39.360> in<01:20:39.440> the 01:20:39.510 --> 01:20:39.520 align:start position:0% uh try to follow what's happening in the 01:20:39.520 --> 01:20:40.629 align:start position:0% uh try to follow what's happening in the skin<01:20:39.840> world 01:20:40.629 --> 01:20:40.639 align:start position:0% skin world 01:20:40.639 --> 01:20:43.189 align:start position:0% skin world and<01:20:41.600> trying<01:20:42.000> trying<01:20:42.320> some<01:20:42.480> implementations 01:20:43.189 --> 01:20:43.199 align:start position:0% and trying trying some implementations 01:20:43.199 --> 01:20:45.030 align:start position:0% and trying trying some implementations on<01:20:43.440> and<01:20:43.600> trying<01:20:43.840> to<01:20:43.920> understand<01:20:44.320> how<01:20:44.560> it<01:20:44.639> works 01:20:45.030 --> 01:20:45.040 align:start position:0% on and trying to understand how it works 01:20:45.040 --> 01:20:46.390 align:start position:0% on and trying to understand how it works and<01:20:45.280> understanding<01:20:45.920> the 01:20:46.390 --> 01:20:46.400 align:start position:0% and understanding the 01:20:46.400 --> 01:20:49.350 align:start position:0% and understanding the standard<01:20:46.880> systems<01:20:47.840> serif<01:20:48.320> is<01:20:48.719> and<01:20:48.880> stuff<01:20:49.199> like 01:20:49.350 --> 01:20:49.360 align:start position:0% standard systems serif is and stuff like 01:20:49.360 --> 01:20:50.310 align:start position:0% standard systems serif is and stuff like that 01:20:50.310 --> 01:20:50.320 align:start position:0% that 01:20:50.320 --> 01:20:53.990 align:start position:0% that um<01:20:51.199> and<01:20:51.440> in<01:20:51.520> that<01:20:51.679> respect 01:20:53.990 --> 01:20:54.000 align:start position:0% um and in that respect 01:20:54.000 --> 01:20:57.830 align:start position:0% um and in that respect the<01:20:54.719> the<01:20:55.440> the<01:20:55.679> major<01:20:56.080> maybe<01:20:56.400> difference 01:20:57.830 --> 01:20:57.840 align:start position:0% the the the major maybe difference 01:20:57.840 --> 01:20:59.750 align:start position:0% the the the major maybe difference except<01:20:58.159> of<01:20:58.239> course<01:20:58.480> the<01:20:58.560> least<01:20:59.040> is<01:20:59.280> two<01:20:59.440> thing 01:20:59.750 --> 01:20:59.760 align:start position:0% except of course the least is two thing 01:20:59.760 --> 01:21:01.830 align:start position:0% except of course the least is two thing is<01:20:59.920> that<01:21:00.239> scheme<01:21:00.639> is<01:21:00.800> evolving 01:21:01.830 --> 01:21:01.840 align:start position:0% is that scheme is evolving 01:21:01.840 --> 01:21:03.910 align:start position:0% is that scheme is evolving because<01:21:02.159> the<01:21:02.320> standard<01:21:02.800> itself<01:21:03.120> it<01:21:03.280> is<01:21:03.520> also<01:21:03.760> a 01:21:03.910 --> 01:21:03.920 align:start position:0% because the standard itself it is also a 01:21:03.920 --> 01:21:05.270 align:start position:0% because the standard itself it is also a standard<01:21:04.320> like<01:21:04.480> common<01:21:04.800> list 01:21:05.270 --> 01:21:05.280 align:start position:0% standard like common list 01:21:05.280 --> 01:21:08.629 align:start position:0% standard like common list but<01:21:05.520> it's<01:21:05.840> another<01:21:06.400> that<01:21:06.639> is<01:21:06.880> that<01:21:07.120> is<01:21:07.520> um 01:21:08.629 --> 01:21:08.639 align:start position:0% but it's another that is that is um 01:21:08.639 --> 01:21:11.189 align:start position:0% but it's another that is that is um that<01:21:08.800> has<01:21:09.040> revisions<01:21:09.840> and<01:21:10.239> which<01:21:10.480> is<01:21:10.719> ongoing 01:21:11.189 --> 01:21:11.199 align:start position:0% that has revisions and which is ongoing 01:21:11.199 --> 01:21:13.189 align:start position:0% that has revisions and which is ongoing with<01:21:11.440> the<01:21:11.520> committee<01:21:12.000> that<01:21:12.239> is<01:21:12.400> being 01:21:13.189 --> 01:21:13.199 align:start position:0% with the committee that is being 01:21:13.199 --> 01:21:16.229 align:start position:0% with the committee that is being um<01:21:14.400> so<01:21:14.639> maybe<01:21:15.040> maybe<01:21:15.280> you<01:21:15.440> want<01:21:15.679> to 01:21:16.229 --> 01:21:16.239 align:start position:0% um so maybe maybe you want to 01:21:16.239 --> 01:21:19.110 align:start position:0% um so maybe maybe you want to to<01:21:16.400> address<01:21:16.719> this<01:21:16.960> this<01:21:17.280> aspect<01:21:17.840> uh<01:21:18.400> just<01:21:18.719> just 01:21:19.110 --> 01:21:19.120 align:start position:0% to address this this aspect uh just just 01:21:19.120 --> 01:21:20.950 align:start position:0% to address this this aspect uh just just uh<01:21:19.440> just<01:21:19.679> a<01:21:19.760> thought<01:21:20.159> like 01:21:20.950 --> 01:21:20.960 align:start position:0% uh just a thought like 01:21:20.960 --> 01:21:24.470 align:start position:0% uh just a thought like um<01:21:21.520> scheme<01:21:21.840> is<01:21:22.000> going<01:21:22.239> to<01:21:22.400> change<01:21:23.120> uh 01:21:24.470 --> 01:21:24.480 align:start position:0% um scheme is going to change uh 01:21:24.480 --> 01:21:26.950 align:start position:0% um scheme is going to change uh commonly<01:21:24.960> is<01:21:25.199> not<01:21:25.920> so<01:21:26.239> that's<01:21:26.480> interesting 01:21:26.950 --> 01:21:26.960 align:start position:0% commonly is not so that's interesting 01:21:26.960 --> 01:21:28.229 align:start position:0% commonly is not so that's interesting right 01:21:28.229 --> 01:21:28.239 align:start position:0% right 01:21:28.239 --> 01:21:31.350 align:start position:0% right well<01:21:28.960> um<01:21:29.679> it's<01:21:29.920> interesting<01:21:30.639> and 01:21:31.350 --> 01:21:31.360 align:start position:0% well um it's interesting and 01:21:31.360 --> 01:21:34.950 align:start position:0% well um it's interesting and strictly<01:21:31.840> speaking<01:21:32.320> is<01:21:32.560> true<01:21:33.440> but<01:21:34.000> uh 01:21:34.950 --> 01:21:34.960 align:start position:0% strictly speaking is true but uh 01:21:34.960 --> 01:21:37.189 align:start position:0% strictly speaking is true but uh i<01:21:35.120> think<01:21:35.600> the<01:21:35.840> implementations<01:21:36.800> of<01:21:36.880> common 01:21:37.189 --> 01:21:37.199 align:start position:0% i think the implementations of common 01:21:37.199 --> 01:21:39.590 align:start position:0% i think the implementations of common lisp<01:21:37.600> have<01:21:37.840> continued<01:21:38.320> to<01:21:38.480> evolve 01:21:39.590 --> 01:21:39.600 align:start position:0% lisp have continued to evolve 01:21:39.600 --> 01:21:43.750 align:start position:0% lisp have continued to evolve and<01:21:40.239> because<01:21:40.639> of<01:21:40.719> the<01:21:41.040> culture<01:21:42.000> of<01:21:42.239> platform 01:21:43.750 --> 01:21:43.760 align:start position:0% and because of the culture of platform 01:21:43.760 --> 01:21:46.709 align:start position:0% and because of the culture of platform interop<01:21:45.840> the<01:21:45.920> culture<01:21:46.239> rather<01:21:46.560> of 01:21:46.709 --> 01:21:46.719 align:start position:0% interop the culture rather of 01:21:46.719 --> 01:21:47.830 align:start position:0% interop the culture rather of implementation 01:21:47.830 --> 01:21:47.840 align:start position:0% implementation 01:21:47.840 --> 01:21:51.189 align:start position:0% implementation interop<01:21:48.880> um 01:21:51.189 --> 01:21:51.199 align:start position:0% 01:21:51.199 --> 01:21:52.629 align:start position:0% like<01:21:51.440> for<01:21:51.600> example<01:21:51.920> there's<01:21:52.159> a<01:21:52.320> there's<01:21:52.480> a 01:21:52.629 --> 01:21:52.639 align:start position:0% like for example there's a there's a 01:21:52.639 --> 01:21:54.229 align:start position:0% like for example there's a there's a fairly<01:21:52.960> recent<01:21:53.520> feature<01:21:53.920> in 01:21:54.229 --> 01:21:54.239 align:start position:0% fairly recent feature in 01:21:54.239 --> 01:21:56.070 align:start position:0% fairly recent feature in a<01:21:54.800> common<01:21:55.120> list<01:21:55.280> called<01:21:55.440> package<01:21:55.760> local 01:21:56.070 --> 01:21:56.080 align:start position:0% a common list called package local 01:21:56.080 --> 01:21:58.070 align:start position:0% a common list called package local nicknames<01:21:57.199> and<01:21:57.280> that's 01:21:58.070 --> 01:21:58.080 align:start position:0% nicknames and that's 01:21:58.080 --> 01:21:59.189 align:start position:0% nicknames and that's enclosure<01:21:58.560> we've<01:21:58.719> had<01:21:58.880> that<01:21:58.960> from<01:21:59.120> the 01:21:59.189 --> 01:21:59.199 align:start position:0% enclosure we've had that from the 01:21:59.199 --> 01:22:00.709 align:start position:0% enclosure we've had that from the beginning<01:21:59.600> and<01:21:59.679> that's<01:21:59.840> the<01:22:00.000> ability<01:22:00.320> to<01:22:00.480> give 01:22:00.709 --> 01:22:00.719 align:start position:0% beginning and that's the ability to give 01:22:00.719 --> 01:22:02.550 align:start position:0% beginning and that's the ability to give pac<01:22:00.960> uh<01:22:01.120> namespaces<01:22:01.679> aliases 01:22:02.550 --> 01:22:02.560 align:start position:0% pac uh namespaces aliases 01:22:02.560 --> 01:22:05.750 align:start position:0% pac uh namespaces aliases so<01:22:02.800> you<01:22:02.960> can<01:22:03.120> use<01:22:04.080> um<01:22:04.960> some<01:22:05.199> abbreviated 01:22:05.750 --> 01:22:05.760 align:start position:0% so you can use um some abbreviated 01:22:05.760 --> 01:22:07.189 align:start position:0% so you can use um some abbreviated version<01:22:06.000> of<01:22:06.159> a<01:22:06.239> package<01:22:06.639> name 01:22:07.189 --> 01:22:07.199 align:start position:0% version of a package name 01:22:07.199 --> 01:22:08.550 align:start position:0% version of a package name forward<01:22:07.520> slash<01:22:07.840> and<01:22:07.920> then<01:22:08.320> you<01:22:08.400> know 01:22:08.550 --> 01:22:08.560 align:start position:0% forward slash and then you know 01:22:08.560 --> 01:22:10.629 align:start position:0% forward slash and then you know something<01:22:08.880> some<01:22:09.040> symbol<01:22:09.360> from<01:22:09.440> that<01:22:09.600> package 01:22:10.629 --> 01:22:10.639 align:start position:0% something some symbol from that package 01:22:10.639 --> 01:22:11.990 align:start position:0% something some symbol from that package um<01:22:10.880> but<01:22:11.040> that's<01:22:11.199> not<01:22:11.360> in<01:22:11.440> the<01:22:11.520> common<01:22:11.760> list 01:22:11.990 --> 01:22:12.000 align:start position:0% um but that's not in the common list 01:22:12.000 --> 01:22:14.390 align:start position:0% um but that's not in the common list standard<01:22:12.400> and<01:22:12.480> so<01:22:12.719> you<01:22:12.800> have<01:22:12.960> to<01:22:13.120> either 01:22:14.390 --> 01:22:14.400 align:start position:0% standard and so you have to either 01:22:14.400 --> 01:22:17.669 align:start position:0% standard and so you have to either deal<01:22:14.639> with<01:22:15.280> you<01:22:15.360> know<01:22:15.600> collisions<01:22:16.320> or<01:22:17.360> fully 01:22:17.669 --> 01:22:17.679 align:start position:0% deal with you know collisions or fully 01:22:17.679 --> 01:22:18.790 align:start position:0% deal with you know collisions or fully qualify 01:22:18.790 --> 01:22:18.800 align:start position:0% qualify 01:22:18.800 --> 01:22:21.990 align:start position:0% qualify you<01:22:18.880> know<01:22:20.960> and<01:22:21.120> so<01:22:21.280> this<01:22:21.440> is<01:22:21.600> a 01:22:21.990 --> 01:22:22.000 align:start position:0% you know and so this is a 01:22:22.000 --> 01:22:24.870 align:start position:0% you know and so this is a feature<01:22:22.400> that<01:22:22.719> all<01:22:23.040> major<01:22:23.360> common<01:22:23.679> lifts<01:22:24.560> have 01:22:24.870 --> 01:22:24.880 align:start position:0% feature that all major common lifts have 01:22:24.880 --> 01:22:25.910 align:start position:0% feature that all major common lifts have now 01:22:25.910 --> 01:22:25.920 align:start position:0% now 01:22:25.920 --> 01:22:29.830 align:start position:0% now and<01:22:26.159> it's<01:22:26.400> non-standard<01:22:28.000> but<01:22:28.560> in<01:22:28.800> practice 01:22:29.830 --> 01:22:29.840 align:start position:0% and it's non-standard but in practice 01:22:29.840 --> 01:22:31.430 align:start position:0% and it's non-standard but in practice like<01:22:30.000> you<01:22:30.159> can<01:22:30.320> pretty<01:22:30.480> much<01:22:30.719> count<01:22:31.040> on<01:22:31.199> an 01:22:31.430 --> 01:22:31.440 align:start position:0% like you can pretty much count on an 01:22:31.440 --> 01:22:34.310 align:start position:0% like you can pretty much count on an existing<01:22:32.639> and 01:22:34.310 --> 01:22:34.320 align:start position:0% existing and 01:22:34.320 --> 01:22:36.870 align:start position:0% existing and you<01:22:34.400> know<01:22:34.639> that's<01:22:34.880> at<01:22:35.040> odds<01:22:35.360> with<01:22:36.400> the<01:22:36.560> spirit 01:22:36.870 --> 01:22:36.880 align:start position:0% you know that's at odds with the spirit 01:22:36.880 --> 01:22:38.390 align:start position:0% you know that's at odds with the spirit of<01:22:36.960> the<01:22:37.120> standard 01:22:38.390 --> 01:22:38.400 align:start position:0% of the standard 01:22:38.400 --> 01:22:40.229 align:start position:0% of the standard because<01:22:38.880> that<01:22:39.120> is<01:22:39.280> strictly<01:22:39.679> speaking<01:22:40.000> that 01:22:40.229 --> 01:22:40.239 align:start position:0% because that is strictly speaking that 01:22:40.239 --> 01:22:41.510 align:start position:0% because that is strictly speaking that is<01:22:40.320> not<01:22:40.560> conformant 01:22:41.510 --> 01:22:41.520 align:start position:0% is not conformant 01:22:41.520 --> 01:22:47.990 align:start position:0% is not conformant you<01:22:41.600> know<01:22:42.480> uh<01:22:42.880> or<01:22:43.360> not<01:22:43.679> um<01:22:44.320> or<01:22:44.480> rather<01:22:44.800> not<01:22:45.120> uh 01:22:47.990 --> 01:22:48.000 align:start position:0% 01:22:48.000 --> 01:22:49.510 align:start position:0% there<01:22:48.239> there's<01:22:48.560> particular<01:22:49.040> terms<01:22:49.360> that 01:22:49.510 --> 01:22:49.520 align:start position:0% there there's particular terms that 01:22:49.520 --> 01:22:51.110 align:start position:0% there there's particular terms that people<01:22:49.760> in<01:22:49.920> commonlist<01:22:50.480> use<01:22:50.639> when<01:22:50.719> they<01:22:50.880> refer 01:22:51.110 --> 01:22:51.120 align:start position:0% people in commonlist use when they refer 01:22:51.120 --> 01:22:52.390 align:start position:0% people in commonlist use when they refer to<01:22:51.280> different<01:22:51.520> features<01:22:51.840> and<01:22:52.000> whether<01:22:52.159> or<01:22:52.239> not 01:22:52.390 --> 01:22:52.400 align:start position:0% to different features and whether or not 01:22:52.400 --> 01:22:54.149 align:start position:0% to different features and whether or not they're<01:22:52.560> implementation<01:22:53.120> dependent<01:22:53.600> or 01:22:54.149 --> 01:22:54.159 align:start position:0% they're implementation dependent or 01:22:54.159 --> 01:22:57.510 align:start position:0% they're implementation dependent or conformant<01:22:55.280> um<01:22:55.760> but<01:22:56.159> that<01:22:56.560> adds<01:22:56.800> gray<01:22:57.040> area<01:22:57.360> to 01:22:57.510 --> 01:22:57.520 align:start position:0% conformant um but that adds gray area to 01:22:57.520 --> 01:22:59.030 align:start position:0% conformant um but that adds gray area to say<01:22:57.679> the<01:22:57.760> least<01:22:58.000> you<01:22:58.080> know<01:22:58.239> it<01:22:58.480> complicates 01:22:59.030 --> 01:22:59.040 align:start position:0% say the least you know it complicates 01:22:59.040 --> 01:23:00.310 align:start position:0% say the least you know it complicates the<01:22:59.120> situation 01:23:00.310 --> 01:23:00.320 align:start position:0% the situation 01:23:00.320 --> 01:23:04.470 align:start position:0% the situation um<01:23:01.440> but<01:23:02.639> um 01:23:04.470 --> 01:23:04.480 align:start position:0% um but um 01:23:04.480 --> 01:23:06.149 align:start position:0% um but um another<01:23:05.040> other<01:23:05.199> thing<01:23:05.360> that<01:23:05.520> comes<01:23:05.679> to<01:23:05.920> mind 01:23:06.149 --> 01:23:06.159 align:start position:0% another other thing that comes to mind 01:23:06.159 --> 01:23:07.910 align:start position:0% another other thing that comes to mind is<01:23:06.320> there's<01:23:06.480> a<01:23:06.719> there<01:23:06.960> well<01:23:07.440> there<01:23:07.520> are<01:23:07.600> a<01:23:07.679> few 01:23:07.910 --> 01:23:07.920 align:start position:0% is there's a there well there are a few 01:23:07.920 --> 01:23:09.990 align:start position:0% is there's a there well there are a few things<01:23:08.159> there's<01:23:08.320> a<01:23:08.400> sequence<01:23:08.880> of<01:23:09.040> protocol 01:23:09.990 --> 01:23:10.000 align:start position:0% things there's a sequence of protocol 01:23:10.000 --> 01:23:13.030 align:start position:0% things there's a sequence of protocol in<01:23:10.239> uh<01:23:11.520> a<01:23:11.760> you<01:23:11.920> know<01:23:12.080> non-standard<01:23:12.800> but 01:23:13.030 --> 01:23:13.040 align:start position:0% in uh a you know non-standard but 01:23:13.040 --> 01:23:14.950 align:start position:0% in uh a you know non-standard but universally<01:23:13.520> supported<01:23:13.840> sequence<01:23:14.239> protocol 01:23:14.950 --> 01:23:14.960 align:start position:0% universally supported sequence protocol 01:23:14.960 --> 01:23:18.310 align:start position:0% universally supported sequence protocol in<01:23:15.199> common<01:23:15.520> lisp<01:23:17.040> um<01:23:17.520> so 01:23:18.310 --> 01:23:18.320 align:start position:0% in common lisp um so 01:23:18.320 --> 01:23:19.590 align:start position:0% in common lisp um so which<01:23:18.560> is<01:23:18.639> to<01:23:18.800> say<01:23:18.960> that<01:23:19.040> yeah<01:23:19.199> street 01:23:19.590 --> 01:23:19.600 align:start position:0% which is to say that yeah street 01:23:19.600 --> 01:23:20.870 align:start position:0% which is to say that yeah street strictly<01:23:20.000> speaking<01:23:20.320> common<01:23:20.560> list<01:23:20.719> for 01:23:20.870 --> 01:23:20.880 align:start position:0% strictly speaking common list for 01:23:20.880 --> 01:23:22.550 align:start position:0% strictly speaking common list for standard<01:23:21.280> is<01:23:21.360> unlikely<01:23:21.760> to<01:23:21.840> change<01:23:22.159> anytime 01:23:22.550 --> 01:23:22.560 align:start position:0% standard is unlikely to change anytime 01:23:22.560 --> 01:23:23.030 align:start position:0% standard is unlikely to change anytime soon 01:23:23.030 --> 01:23:23.040 align:start position:0% soon 01:23:23.040 --> 01:23:26.310 align:start position:0% soon but<01:23:23.600> there<01:23:23.920> is<01:23:24.480> movement<01:23:25.520> there<01:23:25.840> is 01:23:26.310 --> 01:23:26.320 align:start position:0% but there is movement there is 01:23:26.320 --> 01:23:29.750 align:start position:0% but there is movement there is activity<01:23:27.520> um<01:23:28.400> and<01:23:28.880> uh 01:23:29.750 --> 01:23:29.760 align:start position:0% activity um and uh 01:23:29.760 --> 01:23:34.070 align:start position:0% activity um and uh you<01:23:29.920> know<01:23:30.320> the<01:23:30.560> culture<01:23:31.280> is<01:23:31.520> what<01:23:32.159> makes<01:23:32.840> it 01:23:34.070 --> 01:23:34.080 align:start position:0% you know the culture is what makes it 01:23:34.080 --> 01:23:36.950 align:start position:0% you know the culture is what makes it tolerable<01:23:34.960> to<01:23:35.120> me<01:23:35.679> it's<01:23:35.920> not<01:23:36.239> like<01:23:36.719> other 01:23:36.950 --> 01:23:36.960 align:start position:0% tolerable to me it's not like other 01:23:36.960 --> 01:23:38.629 align:start position:0% tolerable to me it's not like other languages<01:23:37.520> where<01:23:37.760> they're<01:23:37.920> changing<01:23:38.239> or 01:23:38.629 --> 01:23:38.639 align:start position:0% languages where they're changing or 01:23:38.639 --> 01:23:40.070 align:start position:0% languages where they're changing or packages<01:23:39.280> or<01:23:39.440> libraries<01:23:39.840> where<01:23:39.920> they're 01:23:40.070 --> 01:23:40.080 align:start position:0% packages or libraries where they're 01:23:40.080 --> 01:23:42.870 align:start position:0% packages or libraries where they're changing<01:23:40.320> fundamental<01:23:40.800> things<01:23:41.040> on<01:23:41.600> on<01:23:41.679> a<01:23:41.840> whim 01:23:42.870 --> 01:23:42.880 align:start position:0% changing fundamental things on on a whim 01:23:42.880 --> 01:23:45.110 align:start position:0% changing fundamental things on on a whim um<01:23:43.920> there<01:23:44.159> is<01:23:44.239> a<01:23:44.320> culture<01:23:44.639> of<01:23:44.719> backward 01:23:45.110 --> 01:23:45.120 align:start position:0% um there is a culture of backward 01:23:45.120 --> 01:23:46.629 align:start position:0% um there is a culture of backward compatibility<01:23:45.840> which 01:23:46.629 --> 01:23:46.639 align:start position:0% compatibility which 01:23:46.639 --> 01:23:49.910 align:start position:0% compatibility which is<01:23:46.800> here<01:23:47.040> to<01:23:47.120> stay<01:23:47.679> i<01:23:47.840> think 01:23:49.910 --> 01:23:49.920 align:start position:0% is here to stay i think 01:23:49.920 --> 01:23:55.750 align:start position:0% is here to stay i think sure<01:23:52.159> anybody<01:23:52.560> else<01:23:52.719> want<01:23:52.880> to<01:23:53.040> chime<01:23:53.360> in 01:23:55.750 --> 01:23:55.760 align:start position:0% 01:23:55.760 --> 01:23:56.950 align:start position:0% simon<01:23:56.000> do<01:23:56.159> you<01:23:56.239> want<01:23:56.320> to<01:23:56.480> explain<01:23:56.719> a<01:23:56.800> little 01:23:56.950 --> 01:23:56.960 align:start position:0% simon do you want to explain a little 01:23:56.960 --> 01:23:58.790 align:start position:0% simon do you want to explain a little bit<01:23:57.199> maybe<01:23:57.520> why<01:23:58.080> um 01:23:58.790 --> 01:23:58.800 align:start position:0% bit maybe why um 01:23:58.800 --> 01:24:01.189 align:start position:0% bit maybe why um or<01:23:59.199> how<01:23:59.840> how<01:24:00.159> transitioning<01:24:00.719> from<01:24:00.960> common 01:24:01.189 --> 01:24:01.199 align:start position:0% or how how transitioning from common 01:24:01.199 --> 01:24:02.870 align:start position:0% or how how transitioning from common list<01:24:01.360> to<01:24:01.520> closure<01:24:01.920> is<01:24:02.080> if 01:24:02.870 --> 01:24:02.880 align:start position:0% list to closure is if 01:24:02.880 --> 01:24:09.510 align:start position:0% list to closure is if if<01:24:03.199> if<01:24:03.360> that's<01:24:03.600> what<01:24:03.760> you've<01:24:04.000> done 01:24:09.510 --> 01:24:09.520 align:start position:0% 01:24:09.520 --> 01:24:12.950 align:start position:0% hi<01:24:09.920> um<01:24:11.120> yeah<01:24:11.360> so<01:24:11.600> it's<01:24:12.239> tough<01:24:12.480> to<01:24:12.639> remember<01:24:12.880> a 01:24:12.950 --> 01:24:12.960 align:start position:0% hi um yeah so it's tough to remember a 01:24:12.960 --> 01:24:14.070 align:start position:0% hi um yeah so it's tough to remember a little<01:24:13.120> bit<01:24:13.199> because<01:24:13.360> it's<01:24:13.520> about 01:24:14.070 --> 01:24:14.080 align:start position:0% little bit because it's about 01:24:14.080 --> 01:24:15.430 align:start position:0% little bit because it's about it's<01:24:14.320> coming<01:24:14.639> up<01:24:14.719> for<01:24:14.800> 10<01:24:15.040> years<01:24:15.199> ago<01:24:15.360> i 01:24:15.430 --> 01:24:15.440 align:start position:0% it's coming up for 10 years ago i 01:24:15.440 --> 01:24:18.709 align:start position:0% it's coming up for 10 years ago i suppose<01:24:16.639> um 01:24:18.709 --> 01:24:18.719 align:start position:0% suppose um 01:24:18.719 --> 01:24:20.070 align:start position:0% suppose um i'm<01:24:18.960> trying<01:24:19.120> to<01:24:19.199> think<01:24:19.360> if<01:24:19.440> i<01:24:19.520> can<01:24:19.840> say<01:24:20.000> an 01:24:20.070 --> 01:24:20.080 align:start position:0% i'm trying to think if i can say an 01:24:20.080 --> 01:24:21.910 align:start position:0% i'm trying to think if i can say an interesting<01:24:20.400> intelligence<01:24:21.199> um 01:24:21.910 --> 01:24:21.920 align:start position:0% interesting intelligence um 01:24:21.920 --> 01:24:24.870 align:start position:0% interesting intelligence um uh<01:24:22.480> i<01:24:22.560> think<01:24:22.719> it<01:24:22.800> probably<01:24:23.040> took<01:24:23.280> me<01:24:24.320> a<01:24:24.639> good 01:24:24.870 --> 01:24:24.880 align:start position:0% uh i think it probably took me a good 01:24:24.880 --> 01:24:25.830 align:start position:0% uh i think it probably took me a good while 01:24:25.830 --> 01:24:25.840 align:start position:0% while 01:24:25.840 --> 01:24:29.189 align:start position:0% while maybe<01:24:27.120> it's<01:24:27.280> probably<01:24:27.520> a<01:24:27.600> gradual<01:24:28.000> thing<01:24:28.239> but 01:24:29.189 --> 01:24:29.199 align:start position:0% maybe it's probably a gradual thing but 01:24:29.199 --> 01:24:30.229 align:start position:0% maybe it's probably a gradual thing but um<01:24:29.360> there<01:24:29.520> were<01:24:29.600> definitely<01:24:29.920> things<01:24:30.080> i 01:24:30.229 --> 01:24:30.239 align:start position:0% um there were definitely things i 01:24:30.239 --> 01:24:34.390 align:start position:0% um there were definitely things i tripped<01:24:30.560> up<01:24:30.719> on<01:24:30.960> and<01:24:31.120> and<01:24:31.440> and<01:24:32.000> um 01:24:34.390 --> 01:24:34.400 align:start position:0% 01:24:34.400 --> 01:24:37.189 align:start position:0% i<01:24:34.560> mentioned<01:24:35.120> the<01:24:35.199> thing<01:24:35.360> with<01:24:35.600> with<01:24:35.840> um 01:24:37.189 --> 01:24:37.199 align:start position:0% i mentioned the thing with with um 01:24:37.199 --> 01:24:38.550 align:start position:0% i mentioned the thing with with um symbols<01:24:37.679> and<01:24:37.920> and 01:24:38.550 --> 01:24:38.560 align:start position:0% symbols and and 01:24:38.560 --> 01:24:41.990 align:start position:0% symbols and and packages<01:24:39.360> um<01:24:40.560> so<01:24:40.800> i<01:24:40.880> think 01:24:41.990 --> 01:24:42.000 align:start position:0% packages um so i think 01:24:42.000 --> 01:24:43.590 align:start position:0% packages um so i think this<01:24:42.239> might<01:24:42.400> not<01:24:42.560> be<01:24:42.800> quite<01:24:43.199> right<01:24:43.440> but<01:24:43.520> i 01:24:43.590 --> 01:24:43.600 align:start position:0% this might not be quite right but i 01:24:43.600 --> 01:24:45.590 align:start position:0% this might not be quite right but i think<01:24:43.840> one<01:24:44.080> of<01:24:44.159> the<01:24:44.320> reasons<01:24:44.719> why 01:24:45.590 --> 01:24:45.600 align:start position:0% think one of the reasons why 01:24:45.600 --> 01:24:48.709 align:start position:0% think one of the reasons why closure<01:24:46.000> symbols<01:24:46.400> are<01:24:46.960> as<01:24:47.199> they<01:24:47.440> are<01:24:48.400> is 01:24:48.709 --> 01:24:48.719 align:start position:0% closure symbols are as they are is 01:24:48.719 --> 01:24:51.030 align:start position:0% closure symbols are as they are is is<01:24:48.960> to<01:24:49.600> make<01:24:49.760> it<01:24:49.920> easier<01:24:50.239> to<01:24:50.320> write<01:24:50.560> hygienic 01:24:51.030 --> 01:24:51.040 align:start position:0% is to make it easier to write hygienic 01:24:51.040 --> 01:24:52.709 align:start position:0% is to make it easier to write hygienic macros 01:24:52.709 --> 01:24:52.719 align:start position:0% macros 01:24:52.719 --> 01:24:55.189 align:start position:0% macros um<01:24:53.360> now<01:24:53.600> i'd<01:24:53.679> have<01:24:53.840> to<01:24:53.920> think<01:24:54.159> to<01:24:54.320> kind<01:24:54.480> of<01:24:54.960> tie 01:24:55.189 --> 01:24:55.199 align:start position:0% um now i'd have to think to kind of tie 01:24:55.199 --> 01:24:56.950 align:start position:0% um now i'd have to think to kind of tie that<01:24:55.520> back<01:24:55.760> into<01:24:56.159> to<01:24:56.320> what<01:24:56.480> we<01:24:56.639> were<01:24:56.719> talking 01:24:56.950 --> 01:24:56.960 align:start position:0% that back into to what we were talking 01:24:56.960 --> 01:24:58.229 align:start position:0% that back into to what we were talking about<01:24:57.199> earlier 01:24:58.229 --> 01:24:58.239 align:start position:0% about earlier 01:24:58.239 --> 01:25:02.070 align:start position:0% about earlier um<01:24:59.760> but<01:25:00.719> i<01:25:00.880> think 01:25:02.070 --> 01:25:02.080 align:start position:0% um but i think 01:25:02.080 --> 01:25:06.149 align:start position:0% um but i think um<01:25:04.239> i<01:25:04.400> think<01:25:04.560> when<01:25:04.800> when<01:25:04.960> you<01:25:05.199> get<01:25:05.440> the<01:25:05.920> thing 01:25:06.149 --> 01:25:06.159 align:start position:0% um i think when when you get the thing 01:25:06.159 --> 01:25:07.510 align:start position:0% um i think when when you get the thing with<01:25:06.320> um 01:25:07.510 --> 01:25:07.520 align:start position:0% with um 01:25:07.520 --> 01:25:10.310 align:start position:0% with um uh<01:25:07.920> the<01:25:08.080> symbols<01:25:08.719> being<01:25:08.960> interned<01:25:09.760> at<01:25:10.000> read 01:25:10.310 --> 01:25:10.320 align:start position:0% uh the symbols being interned at read 01:25:10.320 --> 01:25:11.350 align:start position:0% uh the symbols being interned at read time 01:25:11.350 --> 01:25:11.360 align:start position:0% time 01:25:11.360 --> 01:25:14.870 align:start position:0% time um<01:25:13.520> i<01:25:13.600> think<01:25:14.159> i'd<01:25:14.320> really<01:25:14.480> have<01:25:14.639> to<01:25:14.719> think 01:25:14.870 --> 01:25:14.880 align:start position:0% um i think i'd really have to think 01:25:14.880 --> 01:25:16.390 align:start position:0% um i think i'd really have to think about<01:25:15.040> this<01:25:15.199> but<01:25:15.360> i<01:25:15.440> think<01:25:15.600> that<01:25:15.840> draws<01:25:16.159> you 01:25:16.390 --> 01:25:16.400 align:start position:0% about this but i think that draws you 01:25:16.400 --> 01:25:17.669 align:start position:0% about this but i think that draws you into 01:25:17.669 --> 01:25:17.679 align:start position:0% into 01:25:17.679 --> 01:25:20.709 align:start position:0% into getting<01:25:18.480> um 01:25:20.709 --> 01:25:20.719 align:start position:0% getting um 01:25:20.719 --> 01:25:22.390 align:start position:0% getting um that's<01:25:20.960> one<01:25:21.120> of<01:25:21.280> the<01:25:21.360> things<01:25:21.520> that<01:25:21.679> makes<01:25:22.000> it 01:25:22.390 --> 01:25:22.400 align:start position:0% that's one of the things that makes it 01:25:22.400 --> 01:25:24.390 align:start position:0% that's one of the things that makes it harder<01:25:22.800> to<01:25:22.960> write<01:25:23.360> hygienic<01:25:23.840> macros<01:25:24.320> in 01:25:24.390 --> 01:25:24.400 align:start position:0% harder to write hygienic macros in 01:25:24.400 --> 01:25:26.229 align:start position:0% harder to write hygienic macros in common<01:25:24.719> lips<01:25:24.960> i<01:25:25.040> think 01:25:26.229 --> 01:25:26.239 align:start position:0% common lips i think 01:25:26.239 --> 01:25:28.950 align:start position:0% common lips i think um<01:25:26.639> and<01:25:26.800> so<01:25:27.040> closure's<01:25:27.520> approach<01:25:28.639> i<01:25:28.800> think 01:25:28.950 --> 01:25:28.960 align:start position:0% um and so closure's approach i think 01:25:28.960 --> 01:25:30.870 align:start position:0% um and so closure's approach i think part<01:25:29.199> of<01:25:29.280> the<01:25:29.440> rationale<01:25:29.920> for<01:25:30.080> that 01:25:30.870 --> 01:25:30.880 align:start position:0% part of the rationale for that 01:25:30.880 --> 01:25:34.470 align:start position:0% part of the rationale for that was<01:25:31.120> maybe<01:25:32.639> um 01:25:34.470 --> 01:25:34.480 align:start position:0% was maybe um 01:25:34.480 --> 01:25:37.270 align:start position:0% was maybe um to<01:25:34.639> make<01:25:34.800> hygienic<01:25:35.280> macros<01:25:35.760> easier<01:25:36.880> yes 01:25:37.270 --> 01:25:37.280 align:start position:0% to make hygienic macros easier yes 01:25:37.280 --> 01:25:39.030 align:start position:0% to make hygienic macros easier yes second<01:25:37.600> speak<01:25:37.840> to<01:25:38.000> that<01:25:38.159> relationship 01:25:39.030 --> 01:25:39.040 align:start position:0% second speak to that relationship 01:25:39.040 --> 01:25:42.550 align:start position:0% second speak to that relationship um<01:25:39.440> cool<01:25:40.320> again<01:25:41.280> yeah<01:25:41.520> it's<01:25:41.920> it<01:25:42.159> is<01:25:42.239> a<01:25:42.320> really 01:25:42.550 --> 01:25:42.560 align:start position:0% um cool again yeah it's it is a really 01:25:42.560 --> 01:25:44.629 align:start position:0% um cool again yeah it's it is a really complicated<01:25:43.040> part<01:25:43.199> of<01:25:43.280> both<01:25:43.520> languages 01:25:44.629 --> 01:25:44.639 align:start position:0% complicated part of both languages 01:25:44.639 --> 01:25:47.110 align:start position:0% complicated part of both languages um<01:25:45.360> so<01:25:45.520> i<01:25:45.600> could<01:25:45.760> be<01:25:45.840> wrong<01:25:46.239> but<01:25:46.880> yeah<01:25:47.040> in 01:25:47.110 --> 01:25:47.120 align:start position:0% um so i could be wrong but yeah in 01:25:47.120 --> 01:25:48.870 align:start position:0% um so i could be wrong but yeah in common<01:25:47.440> list<01:25:47.679> there<01:25:47.840> is<01:25:48.000> a<01:25:48.159> function 01:25:48.870 --> 01:25:48.880 align:start position:0% common list there is a function 01:25:48.880 --> 01:25:50.470 align:start position:0% common list there is a function and<01:25:49.199> syntax<01:25:49.600> for<01:25:49.760> making<01:25:50.000> what<01:25:50.159> they<01:25:50.239> call 01:25:50.470 --> 01:25:50.480 align:start position:0% and syntax for making what they call 01:25:50.480 --> 01:25:52.790 align:start position:0% and syntax for making what they call uninterned<01:25:51.120> symbols 01:25:52.790 --> 01:25:52.800 align:start position:0% uninterned symbols 01:25:52.800 --> 01:25:55.189 align:start position:0% uninterned symbols and<01:25:53.199> so<01:25:53.360> like<01:25:53.520> the<01:25:53.679> gen<01:25:53.920> sim<01:25:54.159> function<01:25:55.040> in 01:25:55.189 --> 01:25:55.199 align:start position:0% and so like the gen sim function in 01:25:55.199 --> 01:25:57.270 align:start position:0% and so like the gen sim function in common<01:25:55.520> list<01:25:55.760> returns<01:25:56.080> one<01:25:56.239> of<01:25:56.320> these 01:25:57.270 --> 01:25:57.280 align:start position:0% common list returns one of these 01:25:57.280 --> 01:25:59.990 align:start position:0% common list returns one of these and<01:25:57.440> that's<01:25:58.800> a<01:25:59.199> that<01:25:59.360> gives<01:25:59.520> you<01:25:59.600> an<01:25:59.760> object 01:25:59.990 --> 01:26:00.000 align:start position:0% and that's a that gives you an object 01:26:00.000 --> 01:26:01.990 align:start position:0% and that's a that gives you an object that<01:26:00.239> is<01:26:00.320> a<01:26:00.480> symbol<01:26:00.800> type<01:26:01.120> with<01:26:01.360> a<01:26:01.440> distinct 01:26:01.990 --> 01:26:02.000 align:start position:0% that is a symbol type with a distinct 01:26:02.000 --> 01:26:02.470 align:start position:0% that is a symbol type with a distinct name 01:26:02.470 --> 01:26:02.480 align:start position:0% name 01:26:02.480 --> 01:26:05.910 align:start position:0% name and<01:26:02.639> a<01:26:02.719> distinct<01:26:03.199> identity<01:26:04.560> so<01:26:04.960> it's<01:26:05.120> not<01:26:05.360> eq 01:26:05.910 --> 01:26:05.920 align:start position:0% and a distinct identity so it's not eq 01:26:05.920 --> 01:26:07.830 align:start position:0% and a distinct identity so it's not eq or<01:26:06.080> identical<01:26:06.639> question<01:26:06.960> mark<01:26:07.199> to<01:26:07.280> any<01:26:07.679> any 01:26:07.830 --> 01:26:07.840 align:start position:0% or identical question mark to any any 01:26:07.840 --> 01:26:09.270 align:start position:0% or identical question mark to any any other<01:26:08.000> symbol<01:26:08.320> in<01:26:08.400> the<01:26:08.480> system<01:26:08.880> if<01:26:09.040> once<01:26:09.199> you 01:26:09.270 --> 01:26:09.280 align:start position:0% other symbol in the system if once you 01:26:09.280 --> 01:26:11.030 align:start position:0% other symbol in the system if once you get<01:26:09.440> it<01:26:09.520> back<01:26:09.679> from<01:26:09.840> gen<01:26:10.000> sim 01:26:11.030 --> 01:26:11.040 align:start position:0% get it back from gen sim 01:26:11.040 --> 01:26:15.189 align:start position:0% get it back from gen sim um<01:26:12.560> and<01:26:12.719> so<01:26:13.440> those<01:26:13.840> identifiers<01:26:14.480> can<01:26:14.639> be<01:26:14.800> used 01:26:15.189 --> 01:26:15.199 align:start position:0% um and so those identifiers can be used 01:26:15.199 --> 01:26:15.830 align:start position:0% um and so those identifiers can be used in<01:26:15.360> code 01:26:15.830 --> 01:26:15.840 align:start position:0% in code 01:26:15.840 --> 01:26:17.430 align:start position:0% in code that<01:26:16.000> you're<01:26:16.159> generating<01:26:16.560> in<01:26:16.639> a<01:26:16.719> macro<01:26:17.199> for 01:26:17.430 --> 01:26:17.440 align:start position:0% that you're generating in a macro for 01:26:17.440 --> 01:26:18.870 align:start position:0% that you're generating in a macro for things<01:26:17.679> like<01:26:17.840> the<01:26:18.000> name<01:26:18.239> of<01:26:18.320> something<01:26:18.639> in<01:26:18.800> a 01:26:18.870 --> 01:26:18.880 align:start position:0% things like the name of something in a 01:26:18.880 --> 01:26:20.149 align:start position:0% things like the name of something in a let<01:26:19.120> binding 01:26:20.149 --> 01:26:20.159 align:start position:0% let binding 01:26:20.159 --> 01:26:23.270 align:start position:0% let binding and<01:26:20.639> that's<01:26:21.040> the<01:26:21.360> um<01:26:22.400> i<01:26:22.480> think<01:26:22.639> maybe<01:26:22.880> that's 01:26:23.270 --> 01:26:23.280 align:start position:0% and that's the um i think maybe that's 01:26:23.280 --> 01:26:24.550 align:start position:0% and that's the um i think maybe that's what<01:26:23.440> you<01:26:23.520> might<01:26:23.679> be<01:26:23.760> getting<01:26:24.000> at<01:26:24.159> simon 01:26:24.550 --> 01:26:24.560 align:start position:0% what you might be getting at simon 01:26:24.560 --> 01:26:26.709 align:start position:0% what you might be getting at simon because<01:26:24.880> that's<01:26:25.679> because<01:26:26.080> that<01:26:26.239> thing<01:26:26.560> does 01:26:26.709 --> 01:26:26.719 align:start position:0% because that's because that thing does 01:26:26.719 --> 01:26:28.470 align:start position:0% because that's because that thing does not<01:26:26.960> inhabit<01:26:27.360> a<01:26:27.440> package 01:26:28.470 --> 01:26:28.480 align:start position:0% not inhabit a package 01:26:28.480 --> 01:26:31.510 align:start position:0% not inhabit a package uh<01:26:28.639> regardless<01:26:29.280> of<01:26:30.239> the<01:26:30.400> package<01:26:30.880> in<01:26:31.040> effect 01:26:31.510 --> 01:26:31.520 align:start position:0% uh regardless of the package in effect 01:26:31.520 --> 01:26:33.510 align:start position:0% uh regardless of the package in effect when<01:26:31.679> the<01:26:31.840> macro<01:26:32.320> is<01:26:32.480> called 01:26:33.510 --> 01:26:33.520 align:start position:0% when the macro is called 01:26:33.520 --> 01:26:34.950 align:start position:0% when the macro is called the<01:26:33.760> identity<01:26:34.239> of<01:26:34.320> that<01:26:34.560> symbol<01:26:34.880> is 01:26:34.950 --> 01:26:34.960 align:start position:0% the identity of that symbol is 01:26:34.960 --> 01:26:36.310 align:start position:0% the identity of that symbol is guaranteed<01:26:35.440> not<01:26:35.600> to<01:26:35.760> conflict<01:26:36.159> with<01:26:36.239> the 01:26:36.310 --> 01:26:36.320 align:start position:0% guaranteed not to conflict with the 01:26:36.320 --> 01:26:37.669 align:start position:0% guaranteed not to conflict with the identity<01:26:36.719> of<01:26:36.800> any<01:26:36.960> symbols<01:26:37.280> either<01:26:37.520> in<01:26:37.600> the 01:26:37.669 --> 01:26:37.679 align:start position:0% identity of any symbols either in the 01:26:37.679 --> 01:26:40.070 align:start position:0% identity of any symbols either in the caller's<01:26:38.000> package<01:26:38.320> or<01:26:38.480> anywhere<01:26:38.719> else<01:26:38.960> in<01:26:39.040> the 01:26:40.070 --> 01:26:40.080 align:start position:0% caller's package or anywhere else in the 01:26:40.080 --> 01:26:43.189 align:start position:0% caller's package or anywhere else in the in<01:26:40.239> the<01:26:40.320> system<01:26:41.199> and<01:26:41.520> um<01:26:42.400> we<01:26:42.560> don't<01:26:42.880> we<01:26:43.040> don't 01:26:43.189 --> 01:26:43.199 align:start position:0% in the system and um we don't we don't 01:26:43.199 --> 01:26:44.870 align:start position:0% in the system and um we don't we don't need<01:26:43.360> to<01:26:43.440> go<01:26:43.679> out<01:26:43.760> of<01:26:43.920> our<01:26:44.000> way<01:26:44.239> to<01:26:44.400> do<01:26:44.560> that 01:26:44.870 --> 01:26:44.880 align:start position:0% need to go out of our way to do that 01:26:44.880 --> 01:26:48.070 align:start position:0% need to go out of our way to do that in<01:26:44.960> closure<01:26:45.679> because<01:26:46.960> the<01:26:47.120> symbols<01:26:47.600> naturally 01:26:48.070 --> 01:26:48.080 align:start position:0% in closure because the symbols naturally 01:26:48.080 --> 01:26:49.590 align:start position:0% in closure because the symbols naturally are<01:26:48.239> uninterned 01:26:49.590 --> 01:26:49.600 align:start position:0% are uninterned 01:26:49.600 --> 01:26:55.590 align:start position:0% are uninterned right<01:26:51.440> yup 01:26:55.590 --> 01:26:55.600 align:start position:0% 01:26:55.600 --> 01:26:58.390 align:start position:0% santa<01:26:56.080> are<01:26:56.239> you<01:26:56.480> a<01:26:57.360> common<01:26:57.600> whisper<01:26:58.000> or<01:26:58.159> a<01:26:58.239> claw 01:26:58.390 --> 01:26:58.400 align:start position:0% santa are you a common whisper or a claw 01:26:58.400 --> 01:26:59.030 align:start position:0% santa are you a common whisper or a claw jeweler<01:26:58.719> yeah 01:26:59.030 --> 01:26:59.040 align:start position:0% jeweler yeah 01:26:59.040 --> 01:27:01.750 align:start position:0% jeweler yeah but<01:26:59.440> both<01:27:00.159> in<01:27:00.320> a<01:27:00.400> way<01:27:00.639> i<01:27:01.120> have<01:27:01.280> been<01:27:01.440> doing 01:27:01.750 --> 01:27:01.760 align:start position:0% but both in a way i have been doing 01:27:01.760 --> 01:27:03.350 align:start position:0% but both in a way i have been doing communists<01:27:02.159> for<01:27:02.320> longer<01:27:02.719> but 01:27:03.350 --> 01:27:03.360 align:start position:0% communists for longer but 01:27:03.360 --> 01:27:06.790 align:start position:0% communists for longer but but<01:27:03.679> at<01:27:03.840> work<01:27:04.560> i'm<01:27:04.880> not<01:27:05.120> for<01:27:05.920> five<01:27:06.159> years<01:27:06.400> or<01:27:06.560> so 01:27:06.790 --> 01:27:06.800 align:start position:0% but at work i'm not for five years or so 01:27:06.800 --> 01:27:08.470 align:start position:0% but at work i'm not for five years or so i'm<01:27:07.120> using<01:27:07.360> closure 01:27:08.470 --> 01:27:08.480 align:start position:0% i'm using closure 01:27:08.480 --> 01:27:12.070 align:start position:0% i'm using closure um<01:27:09.600> yeah<01:27:10.000> i<01:27:10.080> think<01:27:10.400> um 01:27:12.070 --> 01:27:12.080 align:start position:0% um yeah i think um 01:27:12.080 --> 01:27:15.590 align:start position:0% um yeah i think um that's<01:27:12.800> also<01:27:13.679> uh<01:27:14.239> this<01:27:14.800> like<01:27:14.960> dancing<01:27:15.360> thing 01:27:15.590 --> 01:27:15.600 align:start position:0% that's also uh this like dancing thing 01:27:15.600 --> 01:27:17.110 align:start position:0% that's also uh this like dancing thing is<01:27:16.000> also<01:27:16.400> a 01:27:17.110 --> 01:27:17.120 align:start position:0% is also a 01:27:17.120 --> 01:27:19.030 align:start position:0% is also a thing<01:27:17.360> which<01:27:17.760> uh<01:27:18.080> interacts<01:27:18.480> with<01:27:18.719> uh<01:27:18.880> this 01:27:19.030 --> 01:27:19.040 align:start position:0% thing which uh interacts with uh this 01:27:19.040 --> 01:27:20.390 align:start position:0% thing which uh interacts with uh this one<01:27:19.280> or<01:27:19.360> this<01:27:19.679> two 01:27:20.390 --> 01:27:20.400 align:start position:0% one or this two 01:27:20.400 --> 01:27:22.709 align:start position:0% one or this two because<01:27:20.719> um<01:27:21.199> if<01:27:21.280> you<01:27:21.440> have<01:27:21.679> this<01:27:21.840> one<01:27:22.400> then<01:27:22.560> you 01:27:22.709 --> 01:27:22.719 align:start position:0% because um if you have this one then you 01:27:22.719 --> 01:27:24.470 align:start position:0% because um if you have this one then you have<01:27:23.040> a<01:27:23.280> much<01:27:23.600> higher 01:27:24.470 --> 01:27:24.480 align:start position:0% have a much higher 01:27:24.480 --> 01:27:27.510 align:start position:0% have a much higher um<01:27:26.639> or 01:27:27.510 --> 01:27:27.520 align:start position:0% um or 01:27:27.520 --> 01:27:30.310 align:start position:0% um or the<01:27:27.679> the<01:27:27.840> hygiene<01:27:28.400> of<01:27:28.560> a<01:27:28.639> macro<01:27:29.040> is<01:27:29.120> a<01:27:29.199> much 01:27:30.310 --> 01:27:30.320 align:start position:0% the the hygiene of a macro is a much 01:27:30.320 --> 01:27:31.590 align:start position:0% the the hygiene of a macro is a much much<01:27:30.560> more<01:27:30.800> important 01:27:31.590 --> 01:27:31.600 align:start position:0% much more important 01:27:31.600 --> 01:27:34.870 align:start position:0% much more important because<01:27:32.400> um<01:27:33.040> if<01:27:33.199> you<01:27:33.600> uh<01:27:34.159> if<01:27:34.320> you<01:27:34.400> know<01:27:34.639> that 01:27:34.870 --> 01:27:34.880 align:start position:0% because um if you uh if you know that 01:27:34.880 --> 01:27:36.629 align:start position:0% because um if you uh if you know that only<01:27:35.280> operators 01:27:36.629 --> 01:27:36.639 align:start position:0% only operators 01:27:36.639 --> 01:27:40.550 align:start position:0% only operators can<01:27:37.520> be<01:27:38.080> uh<01:27:38.719> shadowed<01:27:39.360> accidentally 01:27:40.550 --> 01:27:40.560 align:start position:0% can be uh shadowed accidentally 01:27:40.560 --> 01:27:43.270 align:start position:0% can be uh shadowed accidentally then<01:27:40.800> you<01:27:40.960> can<01:27:41.199> be<01:27:41.440> a<01:27:41.520> bit<01:27:41.920> uh<01:27:42.159> you<01:27:42.480> have<01:27:42.639> a<01:27:42.960> lot 01:27:43.270 --> 01:27:43.280 align:start position:0% then you can be a bit uh you have a lot 01:27:43.280 --> 01:27:44.629 align:start position:0% then you can be a bit uh you have a lot more<01:27:43.440> leeway<01:27:44.080> in 01:27:44.629 --> 01:27:44.639 align:start position:0% more leeway in 01:27:44.639 --> 01:27:47.990 align:start position:0% more leeway in in<01:27:44.960> writing<01:27:45.280> your<01:27:45.440> micros<01:27:46.239> um<01:27:47.360> and 01:27:47.990 --> 01:27:48.000 align:start position:0% in writing your micros um and 01:27:48.000 --> 01:27:51.189 align:start position:0% in writing your micros um and you<01:27:48.159> only<01:27:48.400> need<01:27:48.560> to<01:27:49.280> use<01:27:49.520> jensen<01:27:50.000> for<01:27:50.239> your 01:27:51.189 --> 01:27:51.199 align:start position:0% you only need to use jensen for your 01:27:51.199 --> 01:27:53.189 align:start position:0% you only need to use jensen for your variables<01:27:51.920> that<01:27:52.080> you<01:27:52.320> introduce<01:27:52.880> in<01:27:52.960> your 01:27:53.189 --> 01:27:53.199 align:start position:0% variables that you introduce in your 01:27:53.199 --> 01:27:55.270 align:start position:0% variables that you introduce in your macro<01:27:53.520> body 01:27:55.270 --> 01:27:55.280 align:start position:0% macro body 01:27:55.280 --> 01:27:58.629 align:start position:0% macro body and<01:27:56.560> but<01:27:56.960> in 01:27:58.629 --> 01:27:58.639 align:start position:0% and but in 01:27:58.639 --> 01:28:01.030 align:start position:0% and but in if<01:27:58.800> you<01:27:58.880> have<01:27:59.120> this<01:27:59.360> one<01:27:59.920> then<01:28:00.159> it's<01:28:00.639> both<01:28:00.880> the 01:28:01.030 --> 01:28:01.040 align:start position:0% if you have this one then it's both the 01:28:01.040 --> 01:28:03.030 align:start position:0% if you have this one then it's both the operators<01:28:01.760> and<01:28:01.920> the<01:28:02.080> values<01:28:02.560> and<01:28:02.639> they're<01:28:02.880> all 01:28:03.030 --> 01:28:03.040 align:start position:0% operators and the values and they're all 01:28:03.040 --> 01:28:04.790 align:start position:0% operators and the values and they're all in<01:28:03.199> the<01:28:03.280> name<01:28:03.520> name<01:28:03.760> space 01:28:04.790 --> 01:28:04.800 align:start position:0% in the name name space 01:28:04.800 --> 01:28:07.350 align:start position:0% in the name name space the<01:28:04.960> variables<01:28:05.679> and<01:28:05.920> the<01:28:06.400> and<01:28:06.480> the<01:28:06.639> operators 01:28:07.350 --> 01:28:07.360 align:start position:0% the variables and the and the operators 01:28:07.360 --> 01:28:08.790 align:start position:0% the variables and the and the operators um<01:28:07.760> are<01:28:08.000> all<01:28:08.159> in<01:28:08.239> the<01:28:08.400> name 01:28:08.790 --> 01:28:08.800 align:start position:0% um are all in the name 01:28:08.800 --> 01:28:11.110 align:start position:0% um are all in the name same<01:28:09.120> name<01:28:09.360> space<01:28:09.679> so<01:28:10.239> uh<01:28:10.480> for<01:28:10.639> example<01:28:11.040> you 01:28:11.110 --> 01:28:11.120 align:start position:0% same name space so uh for example you 01:28:11.120 --> 01:28:12.550 align:start position:0% same name space so uh for example you can't<01:28:11.520> uh 01:28:12.550 --> 01:28:12.560 align:start position:0% can't uh 01:28:12.560 --> 01:28:15.590 align:start position:0% can't uh suppose<01:28:13.199> a<01:28:13.280> much<01:28:13.600> more<01:28:14.719> possibility<01:28:15.440> for 01:28:15.590 --> 01:28:15.600 align:start position:0% suppose a much more possibility for 01:28:15.600 --> 01:28:16.390 align:start position:0% suppose a much more possibility for conflict 01:28:16.390 --> 01:28:16.400 align:start position:0% conflict 01:28:16.400 --> 01:28:19.990 align:start position:0% conflict yeah<01:28:17.120> um<01:28:17.600> and<01:28:17.760> so<01:28:17.920> you<01:28:18.080> need<01:28:18.239> to<01:28:18.880> to<01:28:19.040> to<01:28:19.360> be<01:28:19.679> very 01:28:19.990 --> 01:28:20.000 align:start position:0% yeah um and so you need to to to be very 01:28:20.000 --> 01:28:22.470 align:start position:0% yeah um and so you need to to to be very careful<01:28:20.480> about<01:28:20.880> gendering<01:28:21.520> anything 01:28:22.470 --> 01:28:22.480 align:start position:0% careful about gendering anything 01:28:22.480 --> 01:28:26.629 align:start position:0% careful about gendering anything um<01:28:23.040> and<01:28:23.840> um<01:28:24.560> so<01:28:25.040> what<01:28:25.280> what<01:28:25.520> closure<01:28:25.840> does<01:28:26.159> is 01:28:26.629 --> 01:28:26.639 align:start position:0% um and um so what what closure does is 01:28:26.639 --> 01:28:30.149 align:start position:0% um and um so what what closure does is uh<01:28:26.880> that<01:28:27.120> it<01:28:27.360> includes<01:28:28.239> um<01:28:29.120> the 01:28:30.149 --> 01:28:30.159 align:start position:0% uh that it includes um the 01:28:30.159 --> 01:28:33.270 align:start position:0% uh that it includes um the uh<01:28:30.480> facility<01:28:31.120> that<01:28:31.520> for<01:28:31.760> one<01:28:32.320> every<01:28:32.880> symbol 01:28:33.270 --> 01:28:33.280 align:start position:0% uh facility that for one every symbol 01:28:33.280 --> 01:28:34.629 align:start position:0% uh facility that for one every symbol that<01:28:33.440> you<01:28:33.600> use<01:28:33.840> in<01:28:34.000> a 01:28:34.629 --> 01:28:34.639 align:start position:0% that you use in a 01:28:34.639 --> 01:28:38.070 align:start position:0% that you use in a in<01:28:34.880> a<01:28:34.960> macro<01:28:35.360> body<01:28:36.080> is<01:28:36.440> automatically 01:28:38.070 --> 01:28:38.080 align:start position:0% in a macro body is automatically 01:28:38.080 --> 01:28:41.669 align:start position:0% in a macro body is automatically fully<01:28:38.480> qualified<01:28:40.320> and<01:28:40.480> it's<01:28:40.639> not<01:28:40.880> the<01:28:41.120> same 01:28:41.669 --> 01:28:41.679 align:start position:0% fully qualified and it's not the same 01:28:41.679 --> 01:28:43.510 align:start position:0% fully qualified and it's not the same well<01:28:41.840> you<01:28:42.000> have<01:28:42.159> to<01:28:42.320> use<01:28:42.560> that<01:28:42.800> or<01:28:42.960> you<01:28:43.120> have<01:28:43.360> to 01:28:43.510 --> 01:28:43.520 align:start position:0% well you have to use that or you have to 01:28:43.520 --> 01:28:44.790 align:start position:0% well you have to use that or you have to fully<01:28:43.840> qualify<01:28:44.320> it<01:28:44.480> as 01:28:44.790 --> 01:28:44.800 align:start position:0% fully qualify it as 01:28:44.800 --> 01:28:47.030 align:start position:0% fully qualify it as so<01:28:44.960> it's<01:28:45.199> a<01:28:46.000> little<01:28:46.159> bit<01:28:46.560> the<01:28:46.639> other<01:28:46.880> way 01:28:47.030 --> 01:28:47.040 align:start position:0% so it's a little bit the other way 01:28:47.040 --> 01:28:48.310 align:start position:0% so it's a little bit the other way around<01:28:47.679> um 01:28:48.310 --> 01:28:48.320 align:start position:0% around um 01:28:48.320 --> 01:28:52.229 align:start position:0% around um and<01:28:48.719> um<01:28:49.600> so<01:28:50.159> um<01:28:51.120> when<01:28:51.360> you 01:28:52.229 --> 01:28:52.239 align:start position:0% and um so um when you 01:28:52.239 --> 01:28:55.990 align:start position:0% and um so um when you use<01:28:52.480> your<01:28:54.840> um 01:28:55.990 --> 01:28:56.000 align:start position:0% use your um 01:28:56.000 --> 01:28:59.270 align:start position:0% use your um wait<01:28:57.120> i'm<01:28:57.280> sorry<01:28:58.000> i<01:28:58.159> have<01:28:58.239> to<01:28:58.639> no 01:28:59.270 --> 01:28:59.280 align:start position:0% wait i'm sorry i have to no 01:28:59.280 --> 01:29:00.790 align:start position:0% wait i'm sorry i have to no really<01:28:59.600> you<01:28:59.760> have<01:28:59.920> to<01:29:00.159> you<01:29:00.320> have<01:29:00.480> to<01:29:00.560> fully 01:29:00.790 --> 01:29:00.800 align:start position:0% really you have to you have to fully 01:29:00.800 --> 01:29:03.350 align:start position:0% really you have to you have to fully qualify<01:29:01.360> it<01:29:01.600> but<01:29:01.840> the<01:29:02.080> backtech 01:29:03.350 --> 01:29:03.360 align:start position:0% qualify it but the backtech 01:29:03.360 --> 01:29:06.790 align:start position:0% qualify it but the backtech syntax<01:29:04.080> sugar<01:29:04.880> does<01:29:05.199> that<01:29:05.440> for<01:29:05.679> you<01:29:06.159> yeah<01:29:06.400> so 01:29:06.790 --> 01:29:06.800 align:start position:0% syntax sugar does that for you yeah so 01:29:06.800 --> 01:29:10.070 align:start position:0% syntax sugar does that for you yeah so so<01:29:06.960> it<01:29:07.280> automatically<01:29:08.480> fully<01:29:08.800> qualifies<01:29:09.679> also 01:29:10.070 --> 01:29:10.080 align:start position:0% so it automatically fully qualifies also 01:29:10.080 --> 01:29:12.229 align:start position:0% so it automatically fully qualifies also the<01:29:10.239> symbols<01:29:10.719> that<01:29:10.960> are<01:29:11.120> in<01:29:11.199> the<01:29:11.360> backtick 01:29:12.229 --> 01:29:12.239 align:start position:0% the symbols that are in the backtick 01:29:12.239 --> 01:29:16.149 align:start position:0% the symbols that are in the backtick body<01:29:13.520> and<01:29:14.320> um<01:29:15.199> you<01:29:15.440> also 01:29:16.149 --> 01:29:16.159 align:start position:0% body and um you also 01:29:16.159 --> 01:29:19.110 align:start position:0% body and um you also have<01:29:16.719> this<01:29:17.280> thing<01:29:17.600> where<01:29:17.760> you<01:29:17.920> can<01:29:18.480> extend<01:29:19.040> a 01:29:19.110 --> 01:29:19.120 align:start position:0% have this thing where you can extend a 01:29:19.120 --> 01:29:20.629 align:start position:0% have this thing where you can extend a variable<01:29:19.679> name 01:29:20.629 --> 01:29:20.639 align:start position:0% variable name 01:29:20.639 --> 01:29:23.270 align:start position:0% variable name used<01:29:20.960> in<01:29:21.040> the<01:29:21.199> macro<01:29:21.760> with<01:29:22.159> a<01:29:22.480> little<01:29:22.880> hash 01:29:23.270 --> 01:29:23.280 align:start position:0% used in the macro with a little hash 01:29:23.280 --> 01:29:24.470 align:start position:0% used in the macro with a little hash sign<01:29:23.920> then 01:29:24.470 --> 01:29:24.480 align:start position:0% sign then 01:29:24.480 --> 01:29:27.189 align:start position:0% sign then there<01:29:24.719> there's<01:29:24.960> the<01:29:25.199> autogensen<01:29:26.159> so<01:29:26.560> there's 01:29:27.189 --> 01:29:27.199 align:start position:0% there there's the autogensen so there's 01:29:27.199 --> 01:29:29.990 align:start position:0% there there's the autogensen so there's this<01:29:27.440> is<01:29:27.679> automatically<01:29:28.639> expanded 01:29:29.990 --> 01:29:30.000 align:start position:0% this is automatically expanded 01:29:30.000 --> 01:29:33.510 align:start position:0% this is automatically expanded uh<01:29:30.400> to<01:29:30.880> a<01:29:31.120> gent<01:29:31.600> name<01:29:31.760> so<01:29:32.400> in<01:29:32.719> effect<01:29:32.960> there's<01:29:33.280> a 01:29:33.510 --> 01:29:33.520 align:start position:0% uh to a gent name so in effect there's a 01:29:33.520 --> 01:29:34.790 align:start position:0% uh to a gent name so in effect there's a little<01:29:33.760> number<01:29:34.159> uh 01:29:34.790 --> 01:29:34.800 align:start position:0% little number uh 01:29:34.800 --> 01:29:37.030 align:start position:0% little number uh yeah<01:29:35.040> increasing<01:29:35.440> number<01:29:35.840> it<01:29:36.080> attached<01:29:36.480> to<01:29:36.639> it 01:29:37.030 --> 01:29:37.040 align:start position:0% yeah increasing number it attached to it 01:29:37.040 --> 01:29:38.870 align:start position:0% yeah increasing number it attached to it so<01:29:37.199> it's<01:29:37.440> always<01:29:37.760> a<01:29:37.840> different<01:29:38.239> symbol 01:29:38.870 --> 01:29:38.880 align:start position:0% so it's always a different symbol 01:29:38.880 --> 01:29:41.189 align:start position:0% so it's always a different symbol and<01:29:39.120> you<01:29:39.360> get<01:29:39.600> all<01:29:39.760> this<01:29:40.000> hygiene<01:29:40.719> from<01:29:40.960> that 01:29:41.189 --> 01:29:41.199 align:start position:0% and you get all this hygiene from that 01:29:41.199 --> 01:29:42.229 align:start position:0% and you get all this hygiene from that so<01:29:41.440> it's<01:29:41.600> it's 01:29:42.229 --> 01:29:42.239 align:start position:0% so it's it's 01:29:42.239 --> 01:29:45.270 align:start position:0% so it's it's um<01:29:43.040> much<01:29:43.360> easier<01:29:43.840> and<01:29:44.320> closer<01:29:44.800> to<01:29:44.960> write<01:29:45.199> a 01:29:45.270 --> 01:29:45.280 align:start position:0% um much easier and closer to write a 01:29:45.280 --> 01:29:45.990 align:start position:0% um much easier and closer to write a really 01:29:45.990 --> 01:29:46.000 align:start position:0% really 01:29:46.000 --> 01:29:49.030 align:start position:0% really hygienic<01:29:46.719> macro<01:29:47.600> yeah<01:29:47.920> so<01:29:48.080> so<01:29:48.239> you<01:29:48.639> get<01:29:48.880> all 01:29:49.030 --> 01:29:49.040 align:start position:0% hygienic macro yeah so so you get all 01:29:49.040 --> 01:29:51.189 align:start position:0% hygienic macro yeah so so you get all this 01:29:51.189 --> 01:29:51.199 align:start position:0% this 01:29:51.199 --> 01:29:54.149 align:start position:0% this accidental<01:29:52.400> shadowing<01:29:53.040> out<01:29:53.280> of<01:29:53.440> the<01:29:53.760> out<01:29:54.000> of 01:29:54.149 --> 01:29:54.159 align:start position:0% accidental shadowing out of the out of 01:29:54.159 --> 01:29:56.070 align:start position:0% accidental shadowing out of the out of the<01:29:54.239> way 01:29:56.070 --> 01:29:56.080 align:start position:0% the way 01:29:56.080 --> 01:29:58.790 align:start position:0% the way and<01:29:56.719> in<01:29:56.880> communism<01:29:57.600> you<01:29:57.760> have<01:29:57.920> to<01:29:58.080> be<01:29:58.480> a<01:29:58.560> bit 01:29:58.790 --> 01:29:58.800 align:start position:0% and in communism you have to be a bit 01:29:58.800 --> 01:30:00.709 align:start position:0% and in communism you have to be a bit more<01:29:58.960> explicit<01:29:59.440> about<01:29:59.760> it<01:29:59.920> yeah<01:30:00.080> so<01:30:00.480> you<01:30:00.639> have 01:30:00.709 --> 01:30:00.719 align:start position:0% more explicit about it yeah so you have 01:30:00.719 --> 01:30:02.709 align:start position:0% more explicit about it yeah so you have to 01:30:02.709 --> 01:30:02.719 align:start position:0% to 01:30:02.719 --> 01:30:05.189 align:start position:0% to many<01:30:03.920> macros<01:30:04.400> that<01:30:04.639> are<01:30:04.719> a<01:30:04.800> bit<01:30:05.040> more 01:30:05.189 --> 01:30:05.199 align:start position:0% many macros that are a bit more 01:30:05.199 --> 01:30:06.229 align:start position:0% many macros that are a bit more complicated 01:30:06.229 --> 01:30:06.239 align:start position:0% complicated 01:30:06.239 --> 01:30:09.189 align:start position:0% complicated start<01:30:06.639> with<01:30:06.960> uh<01:30:07.679> okay<01:30:08.000> make<01:30:08.239> these<01:30:08.560> gemstones 01:30:09.189 --> 01:30:09.199 align:start position:0% start with uh okay make these gemstones 01:30:09.199 --> 01:30:11.510 align:start position:0% start with uh okay make these gemstones there's<01:30:09.520> a<01:30:09.679> macro<01:30:10.159> for<01:30:10.320> making<01:30:10.639> jensens 01:30:11.510 --> 01:30:11.520 align:start position:0% there's a macro for making jensens 01:30:11.520 --> 01:30:15.189 align:start position:0% there's a macro for making jensens in<01:30:11.679> a<01:30:12.159> more<01:30:12.320> convenient<01:30:12.800> way<01:30:13.120> but 01:30:15.189 --> 01:30:15.199 align:start position:0% in a more convenient way but 01:30:15.199 --> 01:30:18.870 align:start position:0% in a more convenient way but you<01:30:15.840> always<01:30:16.159> use<01:30:16.400> that<01:30:17.040> and<01:30:17.520> um<01:30:18.159> but 01:30:18.870 --> 01:30:18.880 align:start position:0% you always use that and um but 01:30:18.880 --> 01:30:20.950 align:start position:0% you always use that and um but you<01:30:19.040> don't<01:30:19.280> have<01:30:19.440> to<01:30:19.520> be<01:30:19.679> so<01:30:19.920> careful<01:30:20.400> about 01:30:20.950 --> 01:30:20.960 align:start position:0% you don't have to be so careful about 01:30:20.960 --> 01:30:23.430 align:start position:0% you don't have to be so careful about not<01:30:21.600> accidentally<01:30:22.400> shadowing 01:30:23.430 --> 01:30:23.440 align:start position:0% not accidentally shadowing 01:30:23.440 --> 01:30:27.830 align:start position:0% not accidentally shadowing um<01:30:24.320> um<01:30:26.400> function<01:30:26.800> names 01:30:27.830 --> 01:30:27.840 align:start position:0% um um function names 01:30:27.840 --> 01:30:30.629 align:start position:0% um um function names with<01:30:28.080> your<01:30:28.239> variables<01:30:29.280> yeah<01:30:29.679> you<01:30:30.159> you<01:30:30.480> you 01:30:30.629 --> 01:30:30.639 align:start position:0% with your variables yeah you you you 01:30:30.639 --> 01:30:31.110 align:start position:0% with your variables yeah you you you can't 01:30:31.110 --> 01:30:31.120 align:start position:0% can't 01:30:31.120 --> 01:30:34.149 align:start position:0% can't have<01:30:31.360> a<01:30:31.600> led<01:30:32.320> keys<01:30:33.440> something 01:30:34.149 --> 01:30:34.159 align:start position:0% have a led keys something 01:30:34.159 --> 01:30:36.790 align:start position:0% have a led keys something and<01:30:34.480> uh<01:30:34.719> oh<01:30:34.960> oops<01:30:35.360> uh<01:30:35.600> my<01:30:35.920> keys<01:30:36.239> function<01:30:36.639> is 01:30:36.790 --> 01:30:36.800 align:start position:0% and uh oh oops uh my keys function is 01:30:36.800 --> 01:30:37.510 align:start position:0% and uh oh oops uh my keys function is gone 01:30:37.510 --> 01:30:37.520 align:start position:0% gone 01:30:37.520 --> 01:30:39.669 align:start position:0% gone and<01:30:37.760> that's<01:30:38.080> uh<01:30:38.560> something<01:30:38.880> that<01:30:39.040> uh<01:30:39.280> took<01:30:39.520> me 01:30:39.669 --> 01:30:39.679 align:start position:0% and that's uh something that uh took me 01:30:39.679 --> 01:30:41.270 align:start position:0% and that's uh something that uh took me up<01:30:39.840> and<01:30:40.000> when<01:30:40.239> i<01:30:40.320> came<01:30:40.480> to<01:30:40.639> closure 01:30:41.270 --> 01:30:41.280 align:start position:0% up and when i came to closure 01:30:41.280 --> 01:30:43.510 align:start position:0% up and when i came to closure it<01:30:41.360> was<01:30:41.840> always<01:30:42.080> oh<01:30:42.320> i<01:30:42.400> can't<01:30:42.639> use<01:30:42.880> keys<01:30:43.280> it's 01:30:43.510 --> 01:30:43.520 align:start position:0% it was always oh i can't use keys it's 01:30:43.520 --> 01:30:44.950 align:start position:0% it was always oh i can't use keys it's it's<01:30:43.760> a<01:30:43.840> function<01:30:44.239> in<01:30:44.320> the 01:30:44.950 --> 01:30:44.960 align:start position:0% it's a function in the 01:30:44.960 --> 01:30:47.510 align:start position:0% it's a function in the in<01:30:45.040> the<01:30:45.199> chord<01:30:45.600> yeah<01:30:45.840> i<01:30:45.920> can't<01:30:46.320> uh<01:30:46.880> i<01:30:46.960> can't<01:30:47.199> use 01:30:47.510 --> 01:30:47.520 align:start position:0% in the chord yeah i can't uh i can't use 01:30:47.520 --> 01:30:48.550 align:start position:0% in the chord yeah i can't uh i can't use ends<01:30:47.920> because<01:30:48.239> it's 01:30:48.550 --> 01:30:48.560 align:start position:0% ends because it's 01:30:48.560 --> 01:30:51.590 align:start position:0% ends because it's it's<01:30:48.800> a<01:30:49.120> operator<01:30:49.679> in<01:30:49.840> core<01:30:50.560> it's<01:30:50.880> uh 01:30:51.590 --> 01:30:51.600 align:start position:0% it's a operator in core it's uh 01:30:51.600 --> 01:30:54.390 align:start position:0% it's a operator in core it's uh i<01:30:51.679> want<01:30:51.840> to<01:30:52.000> destruction<01:30:52.480> numbers<01:30:53.199> n<01:30:53.600> and<01:30:53.840> ends 01:30:54.390 --> 01:30:54.400 align:start position:0% i want to destruction numbers n and ends 01:30:54.400 --> 01:30:54.870 align:start position:0% i want to destruction numbers n and ends oh 01:30:54.870 --> 01:30:54.880 align:start position:0% oh 01:30:54.880 --> 01:30:57.910 align:start position:0% oh damn<01:30:56.080> um<01:30:57.199> wells 01:30:57.910 --> 01:30:57.920 align:start position:0% damn um wells 01:30:57.920 --> 01:30:59.750 align:start position:0% damn um wells uh<01:30:58.159> no<01:30:58.480> you<01:30:58.639> can't<01:30:58.880> say<01:30:59.120> vowels<01:30:59.440> you<01:30:59.520> have<01:30:59.679> to 01:30:59.750 --> 01:30:59.760 align:start position:0% uh no you can't say vowels you have to 01:30:59.760 --> 01:31:00.950 align:start position:0% uh no you can't say vowels you have to say<01:31:00.080> values 01:31:00.950 --> 01:31:00.960 align:start position:0% say values 01:31:00.960 --> 01:31:04.229 align:start position:0% say values is<01:31:01.520> okay<01:31:02.080> uh<01:31:02.400> yeah<01:31:02.639> values<01:31:03.040> is<01:31:03.120> okay<01:31:03.760> uh<01:31:04.000> yeah 01:31:04.229 --> 01:31:04.239 align:start position:0% is okay uh yeah values is okay uh yeah 01:31:04.239 --> 01:31:04.709 align:start position:0% is okay uh yeah values is okay uh yeah so 01:31:04.709 --> 01:31:04.719 align:start position:0% so 01:31:04.719 --> 01:31:07.910 align:start position:0% so it's<01:31:04.960> uh<01:31:05.440> it's<01:31:06.000> i<01:31:06.159> i<01:31:06.320> feel<01:31:06.639> more<01:31:06.800> restricted<01:31:07.360> by 01:31:07.910 --> 01:31:07.920 align:start position:0% it's uh it's i i feel more restricted by 01:31:07.920 --> 01:31:10.950 align:start position:0% it's uh it's i i feel more restricted by it<01:31:08.080> being<01:31:08.400> a<01:31:08.480> lisp<01:31:08.719> one<01:31:10.080> um 01:31:10.950 --> 01:31:10.960 align:start position:0% it being a lisp one um 01:31:10.960 --> 01:31:12.790 align:start position:0% it being a lisp one um on<01:31:11.040> the<01:31:11.199> other<01:31:11.440> hand<01:31:11.760> it's<01:31:12.000> of<01:31:12.080> course<01:31:12.400> um 01:31:12.790 --> 01:31:12.800 align:start position:0% on the other hand it's of course um 01:31:12.800 --> 01:31:14.950 align:start position:0% on the other hand it's of course um always<01:31:13.120> this<01:31:13.360> thing<01:31:13.840> this<01:31:14.000> funny<01:31:14.320> thing<01:31:14.560> about 01:31:14.950 --> 01:31:14.960 align:start position:0% always this thing this funny thing about 01:31:14.960 --> 01:31:17.110 align:start position:0% always this thing this funny thing about um<01:31:15.199> okay<01:31:15.600> if<01:31:15.760> i<01:31:15.840> use<01:31:16.080> higher<01:31:16.400> order<01:31:16.639> functions 01:31:17.110 --> 01:31:17.120 align:start position:0% um okay if i use higher order functions 01:31:17.120 --> 01:31:18.470 align:start position:0% um okay if i use higher order functions and<01:31:17.199> i<01:31:17.280> want<01:31:17.440> to<01:31:17.520> pass<01:31:17.840> a<01:31:17.920> function<01:31:18.159> then<01:31:18.400> i 01:31:18.470 --> 01:31:18.480 align:start position:0% and i want to pass a function then i 01:31:18.480 --> 01:31:19.110 align:start position:0% and i want to pass a function then i have<01:31:18.719> to 01:31:19.110 --> 01:31:19.120 align:start position:0% have to 01:31:19.120 --> 01:31:21.110 align:start position:0% have to reference<01:31:19.760> it<01:31:19.920> from<01:31:20.080> the<01:31:20.239> function<01:31:20.639> here<01:31:20.880> so<01:31:21.040> i 01:31:21.110 --> 01:31:21.120 align:start position:0% reference it from the function here so i 01:31:21.120 --> 01:31:23.350 align:start position:0% reference it from the function here so i have<01:31:21.199> to<01:31:21.360> put<01:31:21.600> this<01:31:22.080> hash<01:31:22.400> science 01:31:23.350 --> 01:31:23.360 align:start position:0% have to put this hash science 01:31:23.360 --> 01:31:25.910 align:start position:0% have to put this hash science quote<01:31:23.920> before<01:31:24.320> it<01:31:24.560> to<01:31:25.120> pass<01:31:25.440> it<01:31:25.600> and<01:31:25.760> it's 01:31:25.910 --> 01:31:25.920 align:start position:0% quote before it to pass it and it's 01:31:25.920 --> 01:31:28.550 align:start position:0% quote before it to pass it and it's always<01:31:26.320> a<01:31:26.400> bit<01:31:26.639> more<01:31:26.880> hassle<01:31:27.280> a<01:31:27.360> bit<01:31:27.520> more 01:31:28.550 --> 01:31:28.560 align:start position:0% always a bit more hassle a bit more 01:31:28.560 --> 01:31:30.629 align:start position:0% always a bit more hassle a bit more why<01:31:28.719> doesn't<01:31:29.040> this<01:31:29.280> work<01:31:29.520> oh<01:31:29.679> i<01:31:29.760> forgot<01:31:30.239> this 01:31:30.629 --> 01:31:30.639 align:start position:0% why doesn't this work oh i forgot this 01:31:30.639 --> 01:31:32.070 align:start position:0% why doesn't this work oh i forgot this and<01:31:30.960> and<01:31:31.120> when<01:31:31.440> i'm 01:31:32.070 --> 01:31:32.080 align:start position:0% and and when i'm 01:31:32.080 --> 01:31:33.669 align:start position:0% and and when i'm writing<01:31:32.320> a<01:31:32.400> lot<01:31:32.560> yeah<01:31:33.120> and<01:31:33.280> i<01:31:33.360> come<01:31:33.520> to 01:31:33.669 --> 01:31:33.679 align:start position:0% writing a lot yeah and i come to 01:31:33.679 --> 01:31:35.590 align:start position:0% writing a lot yeah and i come to columbus<01:31:34.080> then<01:31:34.239> i<01:31:34.400> sometimes<01:31:34.880> mix<01:31:35.120> this<01:31:35.360> up 01:31:35.590 --> 01:31:35.600 align:start position:0% columbus then i sometimes mix this up 01:31:35.600 --> 01:31:35.910 align:start position:0% columbus then i sometimes mix this up but 01:31:35.910 --> 01:31:35.920 align:start position:0% but 01:31:35.920 --> 01:31:38.310 align:start position:0% but uh<01:31:36.080> i<01:31:36.239> didn't<01:31:36.400> know<01:31:37.199> the<01:31:37.360> point<01:31:37.679> that<01:31:37.920> uh<01:31:38.159> for 01:31:38.310 --> 01:31:38.320 align:start position:0% uh i didn't know the point that uh for 01:31:38.320 --> 01:31:39.030 align:start position:0% uh i didn't know the point that uh for me 01:31:39.030 --> 01:31:39.040 align:start position:0% me 01:31:39.040 --> 01:31:41.350 align:start position:0% me in<01:31:39.199> terms<01:31:39.600> aesthetically<01:31:40.800> high<01:31:41.040> order 01:31:41.350 --> 01:31:41.360 align:start position:0% in terms aesthetically high order 01:31:41.360 --> 01:31:43.189 align:start position:0% in terms aesthetically high order functions<01:31:41.840> and<01:31:42.000> at<01:31:42.080> least<01:31:42.320> one<01:31:42.639> is<01:31:42.719> just 01:31:43.189 --> 01:31:43.199 align:start position:0% functions and at least one is just 01:31:43.199 --> 01:31:46.070 align:start position:0% functions and at least one is just this<01:31:43.440> is<01:31:43.600> just<01:31:43.840> elegance<01:31:44.560> uh<01:31:44.960> embodied<01:31:45.600> for<01:31:45.760> me 01:31:46.070 --> 01:31:46.080 align:start position:0% this is just elegance uh embodied for me 01:31:46.080 --> 01:31:46.870 align:start position:0% this is just elegance uh embodied for me i<01:31:46.159> mean 01:31:46.870 --> 01:31:46.880 align:start position:0% i mean 01:31:46.880 --> 01:31:49.750 align:start position:0% i mean to<01:31:47.040> be<01:31:47.199> able<01:31:47.360> to<01:31:47.520> say<01:31:47.840> you<01:31:48.000> know<01:31:48.239> uh<01:31:48.639> map<01:31:49.679> and 01:31:49.750 --> 01:31:49.760 align:start position:0% to be able to say you know uh map and 01:31:49.760 --> 01:31:50.149 align:start position:0% to be able to say you know uh map and then 01:31:50.149 --> 01:31:50.159 align:start position:0% then 01:31:50.159 --> 01:31:51.350 align:start position:0% then the<01:31:50.320> name<01:31:50.480> of<01:31:50.560> the<01:31:50.719> function<01:31:51.120> and<01:31:51.199> your 01:31:51.350 --> 01:31:51.360 align:start position:0% the name of the function and your 01:31:51.360 --> 01:31:53.510 align:start position:0% the name of the function and your collection<01:31:51.840> that's<01:31:52.560> without 01:31:53.510 --> 01:31:53.520 align:start position:0% collection that's without 01:31:53.520 --> 01:31:56.950 align:start position:0% collection that's without going<01:31:53.840> through<01:31:54.080> the<01:31:54.560> to<01:31:54.719> this<01:31:55.040> uh<01:31:55.520> yeah<01:31:56.320> but<01:31:56.560> uh 01:31:56.950 --> 01:31:56.960 align:start position:0% going through the to this uh yeah but uh 01:31:56.960 --> 01:31:58.550 align:start position:0% going through the to this uh yeah but uh that's<01:31:57.280> that's<01:31:57.520> maybe<01:31:57.760> just<01:31:58.000> an<01:31:58.159> aesthetic 01:31:58.550 --> 01:31:58.560 align:start position:0% that's that's maybe just an aesthetic 01:31:58.560 --> 01:32:00.070 align:start position:0% that's that's maybe just an aesthetic point<01:31:58.800> and<01:31:59.040> really<01:31:59.360> not<01:31:59.679> not<01:31:59.840> really 01:32:00.070 --> 01:32:00.080 align:start position:0% point and really not not really 01:32:00.080 --> 01:32:01.270 align:start position:0% point and really not not really important 01:32:01.270 --> 01:32:01.280 align:start position:0% important 01:32:01.280 --> 01:32:02.629 align:start position:0% important well<01:32:01.520> the<01:32:01.600> aesthetics<01:32:02.080> are<01:32:02.159> important<01:32:02.560> i 01:32:02.629 --> 01:32:02.639 align:start position:0% well the aesthetics are important i 01:32:02.639 --> 01:32:04.550 align:start position:0% well the aesthetics are important i think<01:32:02.800> to<01:32:02.960> the<01:32:03.040> extent<01:32:03.440> that<01:32:03.920> you<01:32:04.080> know<01:32:04.239> your 01:32:04.550 --> 01:32:04.560 align:start position:0% think to the extent that you know your 01:32:04.560 --> 01:32:06.149 align:start position:0% think to the extent that you know your your<01:32:04.800> tastes<01:32:05.120> are<01:32:05.280> in<01:32:05.360> alignment<01:32:05.840> with<01:32:06.000> what 01:32:06.149 --> 01:32:06.159 align:start position:0% your tastes are in alignment with what 01:32:06.159 --> 01:32:07.910 align:start position:0% your tastes are in alignment with what you're<01:32:06.400> using<01:32:06.960> because<01:32:07.199> it's<01:32:07.360> only<01:32:07.600> it's<01:32:07.760> only 01:32:07.910 --> 01:32:07.920 align:start position:0% you're using because it's only it's only 01:32:07.920 --> 01:32:08.950 align:start position:0% you're using because it's only it's only a<01:32:08.000> pain<01:32:08.400> if<01:32:08.560> you 01:32:08.950 --> 01:32:08.960 align:start position:0% a pain if you 01:32:08.960 --> 01:32:14.550 align:start position:0% a pain if you are<01:32:09.120> forced<01:32:09.360> to<01:32:09.440> use<01:32:09.600> something<01:32:09.920> that<01:32:11.600> yeah 01:32:14.550 --> 01:32:14.560 align:start position:0% 01:32:14.560 --> 01:32:18.229 align:start position:0% um<01:32:16.400> a<01:32:16.560> suggestion<01:32:17.040> was<01:32:17.280> made<01:32:17.440> to<01:32:17.600> do<01:32:17.760> a<01:32:17.840> rebel 01:32:18.229 --> 01:32:18.239 align:start position:0% um a suggestion was made to do a rebel 01:32:18.239 --> 01:32:19.510 align:start position:0% um a suggestion was made to do a rebel which<01:32:18.480> i 01:32:19.510 --> 01:32:19.520 align:start position:0% which i 01:32:19.520 --> 01:32:22.629 align:start position:0% which i i'd<01:32:19.760> love<01:32:19.920> to<01:32:20.080> do<01:32:20.400> we<01:32:20.560> could<01:32:20.800> oh<01:32:21.040> great 01:32:22.629 --> 01:32:22.639 align:start position:0% i'd love to do we could oh great 01:32:22.639 --> 01:32:28.629 align:start position:0% i'd love to do we could oh great for<01:32:22.800> sure<01:32:23.440> yeah<01:32:25.360> let's<01:32:25.600> do<01:32:25.760> it 01:32:28.629 --> 01:32:28.639 align:start position:0% 01:32:28.639 --> 01:32:29.910 align:start position:0% i'm<01:32:28.880> glad<01:32:29.040> there<01:32:29.120> are<01:32:29.199> other<01:32:29.360> people<01:32:29.679> here 01:32:29.910 --> 01:32:29.920 align:start position:0% i'm glad there are other people here 01:32:29.920 --> 01:32:31.910 align:start position:0% i'm glad there are other people here with<01:32:30.159> actual<01:32:30.560> lisp<01:32:30.880> experience<01:32:31.360> because<01:32:31.679> i'm 01:32:31.910 --> 01:32:31.920 align:start position:0% with actual lisp experience because i'm 01:32:31.920 --> 01:32:32.310 align:start position:0% with actual lisp experience because i'm a 01:32:32.310 --> 01:32:32.320 align:start position:0% a 01:32:32.320 --> 01:32:35.430 align:start position:0% a bit<01:32:32.480> of<01:32:32.639> a<01:32:32.719> fraud<01:32:33.280> in<01:32:33.360> that<01:32:33.520> regard 01:32:35.430 --> 01:32:35.440 align:start position:0% bit of a fraud in that regard 01:32:35.440 --> 01:32:38.709 align:start position:0% bit of a fraud in that regard okay<01:32:37.679> so<01:32:37.920> um 01:32:38.709 --> 01:32:38.719 align:start position:0% okay so um 01:32:38.719 --> 01:32:41.750 align:start position:0% okay so um i<01:32:38.880> don't<01:32:39.840> use<01:32:40.480> list<01:32:40.719> books<01:32:41.120> myself<01:32:41.600> for 01:32:41.750 --> 01:32:41.760 align:start position:0% i don't use list books myself for 01:32:41.760 --> 01:32:43.590 align:start position:0% i don't use list books myself for anything<01:32:42.080> i'll<01:32:42.560> occasionally<01:32:43.040> open<01:32:43.199> it<01:32:43.440> up<01:32:43.520> to 01:32:43.590 --> 01:32:43.600 align:start position:0% anything i'll occasionally open it up to 01:32:43.600 --> 01:32:45.430 align:start position:0% anything i'll occasionally open it up to poke<01:32:43.920> around 01:32:45.430 --> 01:32:45.440 align:start position:0% poke around 01:32:45.440 --> 01:32:47.830 align:start position:0% poke around test<01:32:45.679> things<01:32:45.920> out<01:32:46.560> but<01:32:47.120> i'm<01:32:47.280> glad<01:32:47.520> that<01:32:47.679> it 01:32:47.830 --> 01:32:47.840 align:start position:0% test things out but i'm glad that it 01:32:47.840 --> 01:32:49.270 align:start position:0% test things out but i'm glad that it exists<01:32:48.400> and<01:32:48.560> what<01:32:48.719> it<01:32:48.880> is 01:32:49.270 --> 01:32:49.280 align:start position:0% exists and what it is 01:32:49.280 --> 01:32:50.790 align:start position:0% exists and what it is is<01:32:49.600> it<01:32:49.760> is<01:32:49.840> a<01:32:50.000> commercial<01:32:50.480> lisp 01:32:50.790 --> 01:32:50.800 align:start position:0% is it is a commercial lisp 01:32:50.800 --> 01:32:53.189 align:start position:0% is it is a commercial lisp implementation<01:32:51.520> and<01:32:51.679> ide 01:32:53.189 --> 01:32:53.199 align:start position:0% implementation and ide 01:32:53.199 --> 01:32:56.149 align:start position:0% implementation and ide and<01:32:53.920> someday<01:32:54.800> i<01:32:54.880> will<01:32:55.040> buy<01:32:55.280> a<01:32:55.360> license<01:32:55.760> to<01:32:55.920> it 01:32:56.149 --> 01:32:56.159 align:start position:0% and someday i will buy a license to it 01:32:56.159 --> 01:32:57.510 align:start position:0% and someday i will buy a license to it because 01:32:57.510 --> 01:32:57.520 align:start position:0% because 01:32:57.520 --> 01:32:59.750 align:start position:0% because i<01:32:57.600> think<01:32:57.840> it's<01:32:58.000> neat<01:32:58.639> and<01:32:59.040> i<01:32:59.199> want<01:32:59.360> to<01:32:59.440> support 01:32:59.750 --> 01:32:59.760 align:start position:0% i think it's neat and i want to support 01:32:59.760 --> 01:33:00.790 align:start position:0% i think it's neat and i want to support the<01:32:59.840> work 01:33:00.790 --> 01:33:00.800 align:start position:0% the work 01:33:00.800 --> 01:33:02.550 align:start position:0% the work but<01:33:01.120> the<01:33:01.280> license<01:33:01.760> costs<01:33:02.080> like<01:33:02.320> three 01:33:02.550 --> 01:33:02.560 align:start position:0% but the license costs like three 01:33:02.560 --> 01:33:04.070 align:start position:0% but the license costs like three thousand<01:33:02.800> dollars 01:33:04.070 --> 01:33:04.080 align:start position:0% thousand dollars 01:33:04.080 --> 01:33:07.510 align:start position:0% thousand dollars and<01:33:05.280> i<01:33:05.440> want<01:33:05.679> other<01:33:05.920> things<01:33:06.480> first<01:33:07.040> so 01:33:07.510 --> 01:33:07.520 align:start position:0% and i want other things first so 01:33:07.520 --> 01:33:09.030 align:start position:0% and i want other things first so it's<01:33:07.679> not<01:33:07.760> going<01:33:07.840> to<01:33:07.920> happen<01:33:08.159> anytime<01:33:08.480> soon 01:33:09.030 --> 01:33:09.040 align:start position:0% it's not going to happen anytime soon 01:33:09.040 --> 01:33:10.709 align:start position:0% it's not going to happen anytime soon but<01:33:09.280> you<01:33:09.440> can<01:33:09.520> download<01:33:09.920> this<01:33:10.080> thing<01:33:10.320> for<01:33:10.480> free 01:33:10.709 --> 01:33:10.719 align:start position:0% but you can download this thing for free 01:33:10.719 --> 01:33:12.709 align:start position:0% but you can download this thing for free and<01:33:10.880> run<01:33:11.120> it 01:33:12.709 --> 01:33:12.719 align:start position:0% and run it 01:33:12.719 --> 01:33:15.270 align:start position:0% and run it it<01:33:12.880> doesn't<01:33:13.280> have<01:33:13.679> any<01:33:13.920> kind<01:33:14.080> of<01:33:14.480> nagging 01:33:15.270 --> 01:33:15.280 align:start position:0% it doesn't have any kind of nagging 01:33:15.280 --> 01:33:15.910 align:start position:0% it doesn't have any kind of nagging features 01:33:15.910 --> 01:33:15.920 align:start position:0% features 01:33:15.920 --> 01:33:17.830 align:start position:0% features i<01:33:16.000> think<01:33:16.159> it<01:33:16.320> turns<01:33:16.639> off<01:33:16.880> after<01:33:17.199> two<01:33:17.440> hours<01:33:17.760> or 01:33:17.830 --> 01:33:17.840 align:start position:0% i think it turns off after two hours or 01:33:17.840 --> 01:33:21.590 align:start position:0% i think it turns off after two hours or something<01:33:18.080> like<01:33:18.239> that<01:33:18.639> but<01:33:18.800> it'll<01:33:18.960> warn<01:33:19.199> you 01:33:21.590 --> 01:33:21.600 align:start position:0% 01:33:21.600 --> 01:33:23.350 align:start position:0% but<01:33:21.840> what<01:33:22.000> it<01:33:22.159> is<01:33:22.400> is<01:33:22.560> it's<01:33:22.719> the<01:33:22.880> closest<01:33:23.199> thing 01:33:23.350 --> 01:33:23.360 align:start position:0% but what it is is it's the closest thing 01:33:23.360 --> 01:33:26.229 align:start position:0% but what it is is it's the closest thing we<01:33:23.520> have<01:33:23.760> today<01:33:24.480> to<01:33:24.639> the<01:33:24.800> kind<01:33:25.199> of 01:33:26.229 --> 01:33:26.239 align:start position:0% we have today to the kind of 01:33:26.239 --> 01:33:29.350 align:start position:0% we have today to the kind of environment<01:33:27.360> that<01:33:27.600> the<01:33:27.760> whispers<01:33:28.239> of<01:33:28.320> your 01:33:29.350 --> 01:33:29.360 align:start position:0% environment that the whispers of your 01:33:29.360 --> 01:33:32.390 align:start position:0% environment that the whispers of your had<01:33:30.480> where<01:33:31.199> there<01:33:31.360> were<01:33:31.520> first-class<01:33:32.080> package 01:33:32.390 --> 01:33:32.400 align:start position:0% had where there were first-class package 01:33:32.400 --> 01:33:33.189 align:start position:0% had where there were first-class package browsers 01:33:33.189 --> 01:33:33.199 align:start position:0% browsers 01:33:33.199 --> 01:33:37.030 align:start position:0% browsers first-class<01:33:35.120> uh<01:33:35.840> you<01:33:35.920> know<01:33:36.159> ui<01:33:36.560> support<01:33:36.880> for 01:33:37.030 --> 01:33:37.040 align:start position:0% first-class uh you know ui support for 01:33:37.040 --> 01:33:38.870 align:start position:0% first-class uh you know ui support for the<01:33:37.120> stuff<01:33:37.360> in<01:33:37.440> common<01:33:37.679> list 01:33:38.870 --> 01:33:38.880 align:start position:0% the stuff in common list 01:33:38.880 --> 01:33:42.070 align:start position:0% the stuff in common list um<01:33:39.280> so<01:33:40.480> we<01:33:40.639> can<01:33:40.800> do<01:33:41.520> you<01:33:41.679> know 01:33:42.070 --> 01:33:42.080 align:start position:0% um so we can do you know 01:33:42.080 --> 01:33:43.910 align:start position:0% um so we can do you know i've<01:33:42.239> got<01:33:42.400> a<01:33:42.800> what's<01:33:42.960> called<01:33:43.199> a<01:33:43.280> listener<01:33:43.760> over 01:33:43.910 --> 01:33:43.920 align:start position:0% i've got a what's called a listener over 01:33:43.920 --> 01:33:45.510 align:start position:0% i've got a what's called a listener over here<01:33:44.480> a<01:33:44.719> listener<01:33:45.199> is<01:33:45.280> a 01:33:45.510 --> 01:33:45.520 align:start position:0% here a listener is a 01:33:45.520 --> 01:33:48.709 align:start position:0% here a listener is a is<01:33:45.679> a<01:33:45.760> term<01:33:46.080> you'll<01:33:46.239> see<01:33:46.560> used<01:33:47.040> in<01:33:48.320> the<01:33:48.400> common 01:33:48.709 --> 01:33:48.719 align:start position:0% is a term you'll see used in the common 01:33:48.719 --> 01:33:51.270 align:start position:0% is a term you'll see used in the common list<01:33:48.960> world<01:33:49.199> to<01:33:49.360> refer<01:33:49.679> to<01:33:49.840> a<01:33:50.000> rebel 01:33:51.270 --> 01:33:51.280 align:start position:0% list world to refer to a rebel 01:33:51.280 --> 01:33:54.550 align:start position:0% list world to refer to a rebel um<01:33:52.320> but<01:33:52.639> usually<01:33:53.280> the<01:33:53.760> kinds<01:33:54.000> of<01:33:54.080> rebels<01:33:54.480> you 01:33:54.550 --> 01:33:54.560 align:start position:0% um but usually the kinds of rebels you 01:33:54.560 --> 01:33:55.910 align:start position:0% um but usually the kinds of rebels you can<01:33:54.719> expect<01:33:55.040> in<01:33:55.120> common<01:33:55.440> lists 01:33:55.910 --> 01:33:55.920 align:start position:0% can expect in common lists 01:33:55.920 --> 01:33:57.189 align:start position:0% can expect in common lists are<01:33:56.000> more<01:33:56.159> featureful<01:33:56.639> than<01:33:56.800> what<01:33:56.960> we're<01:33:57.120> used 01:33:57.189 --> 01:33:57.199 align:start position:0% are more featureful than what we're used 01:33:57.199 --> 01:34:00.149 align:start position:0% are more featureful than what we're used to<01:33:57.360> in<01:33:57.440> the<01:33:57.520> closure<01:33:57.920> world<01:33:58.239> and<01:33:58.400> i<01:33:58.480> think<01:33:58.719> uh 01:34:00.149 --> 01:34:00.159 align:start position:0% to in the closure world and i think uh 01:34:00.159 --> 01:34:01.990 align:start position:0% to in the closure world and i think uh that's<01:34:00.400> just<01:34:00.639> again<01:34:00.960> part<01:34:01.199> of<01:34:01.360> being<01:34:01.760> the 01:34:01.990 --> 01:34:02.000 align:start position:0% that's just again part of being the 01:34:02.000 --> 01:34:03.510 align:start position:0% that's just again part of being the platform<01:34:03.040> is 01:34:03.510 --> 01:34:03.520 align:start position:0% platform is 01:34:03.520 --> 01:34:06.950 align:start position:0% platform is they<01:34:03.760> have<01:34:05.199> special<01:34:05.520> affordances 01:34:06.950 --> 01:34:06.960 align:start position:0% they have special affordances 01:34:06.960 --> 01:34:11.110 align:start position:0% they have special affordances so<01:34:09.920> this<01:34:10.159> is<01:34:10.320> the<01:34:10.400> most<01:34:10.560> important<01:34:10.880> thing<01:34:11.040> to 01:34:11.110 --> 01:34:11.120 align:start position:0% so this is the most important thing to 01:34:11.120 --> 01:34:13.430 align:start position:0% so this is the most important thing to write<01:34:11.360> first 01:34:13.430 --> 01:34:13.440 align:start position:0% write first 01:34:13.440 --> 01:34:21.590 align:start position:0% write first excuse<01:34:13.840> me<01:34:14.000> my<01:34:14.480> phone<01:34:14.719> is<01:34:16.840> blocking 01:34:21.590 --> 01:34:21.600 align:start position:0% 01:34:21.600 --> 01:34:26.709 align:start position:0% um 01:34:26.709 --> 01:34:26.719 align:start position:0% 01:34:26.719 --> 01:34:29.030 align:start position:0% one<01:34:26.960> second<01:34:27.360> i<01:34:27.600> uh<01:34:28.080> just<01:34:28.239> need<01:34:28.400> to<01:34:28.560> turn<01:34:28.719> off<01:34:28.880> my 01:34:29.030 --> 01:34:29.040 align:start position:0% one second i uh just need to turn off my 01:34:29.040 --> 01:34:30.870 align:start position:0% one second i uh just need to turn off my video 01:34:30.870 --> 01:34:30.880 align:start position:0% video 01:34:30.880 --> 01:34:32.470 align:start position:0% video it's<01:34:31.120> a<01:34:31.199> family<01:34:31.520> member<01:34:31.760> who<01:34:32.000> doesn't<01:34:32.239> want<01:34:32.400> to 01:34:32.470 --> 01:34:32.480 align:start position:0% it's a family member who doesn't want to 01:34:32.480 --> 01:34:34.629 align:start position:0% it's a family member who doesn't want to be<01:34:33.360> seen 01:34:34.629 --> 01:34:34.639 align:start position:0% be seen 01:34:34.639 --> 01:34:55.030 align:start position:0% be seen will<01:34:34.880> access<01:34:35.280> the<01:34:35.360> pantry<01:34:35.760> behind<01:34:44.840> me 01:34:55.030 --> 01:34:55.040 align:start position:0% 01:34:55.040 --> 01:34:57.830 align:start position:0% all<01:34:55.119> right<01:34:55.440> everybody<01:34:55.760> still<01:34:55.920> there<01:34:56.960> yeah<01:34:57.760> all 01:34:57.830 --> 01:34:57.840 align:start position:0% all right everybody still there yeah all 01:34:57.840 --> 01:34:58.550 align:start position:0% all right everybody still there yeah all right<01:34:58.080> great 01:34:58.550 --> 01:34:58.560 align:start position:0% right great 01:34:58.560 --> 01:35:01.430 align:start position:0% right great so<01:34:58.960> um<01:35:00.400> right<01:35:00.560> so<01:35:00.719> we<01:35:00.800> have<01:35:00.880> the<01:35:00.960> listener<01:35:01.360> we 01:35:01.430 --> 01:35:01.440 align:start position:0% so um right so we have the listener we 01:35:01.440 --> 01:35:03.030 align:start position:0% so um right so we have the listener we can<01:35:01.520> type<01:35:01.760> stuff<01:35:02.000> in 01:35:03.030 --> 01:35:03.040 align:start position:0% can type stuff in 01:35:03.040 --> 01:35:05.109 align:start position:0% can type stuff in you<01:35:03.199> know<01:35:03.920> everything<01:35:04.239> that<01:35:04.320> we<01:35:04.480> would<01:35:04.719> expect 01:35:05.109 --> 01:35:05.119 align:start position:0% you know everything that we would expect 01:35:05.119 --> 01:35:06.550 align:start position:0% you know everything that we would expect i'm<01:35:05.280> actually<01:35:05.600> i've<01:35:05.840> been<01:35:06.000> writing<01:35:06.320> closure 01:35:06.550 --> 01:35:06.560 align:start position:0% i'm actually i've been writing closure 01:35:06.560 --> 01:35:07.910 align:start position:0% i'm actually i've been writing closure code<01:35:06.800> into<01:35:06.960> the<01:35:07.040> reply<01:35:07.360> and<01:35:07.520> it's<01:35:07.600> working 01:35:07.910 --> 01:35:07.920 align:start position:0% code into the reply and it's working 01:35:07.920 --> 01:35:11.030 align:start position:0% code into the reply and it's working magically 01:35:11.030 --> 01:35:11.040 align:start position:0% 01:35:11.040 --> 01:35:14.310 align:start position:0% um<01:35:13.280> but<01:35:14.000> we 01:35:14.310 --> 01:35:14.320 align:start position:0% um but we 01:35:14.320 --> 01:35:16.470 align:start position:0% um but we can<01:35:15.440> let's<01:35:15.600> look<01:35:15.840> at<01:35:15.920> some<01:35:16.080> of<01:35:16.159> the<01:35:16.239> things 01:35:16.470 --> 01:35:16.480 align:start position:0% can let's look at some of the things 01:35:16.480 --> 01:35:17.590 align:start position:0% can let's look at some of the things that<01:35:16.639> we<01:35:16.719> were<01:35:16.880> discussing 01:35:17.590 --> 01:35:17.600 align:start position:0% that we were discussing 01:35:17.600 --> 01:35:19.109 align:start position:0% that we were discussing uh<01:35:17.760> we<01:35:17.840> were<01:35:18.000> talking<01:35:18.159> about<01:35:18.320> list<01:35:18.560> one<01:35:18.800> versus 01:35:19.109 --> 01:35:19.119 align:start position:0% uh we were talking about list one versus 01:35:19.119 --> 01:35:30.550 align:start position:0% uh we were talking about list one versus lisp<01:35:26.840> two 01:35:30.550 --> 01:35:30.560 align:start position:0% 01:35:30.560 --> 01:35:34.629 align:start position:0% so<01:35:30.880> there<01:35:31.119> is<01:35:31.199> a<01:35:31.280> function<01:35:31.760> list 01:35:34.629 --> 01:35:34.639 align:start position:0% 01:35:34.639 --> 01:35:37.430 align:start position:0% in<01:35:34.800> common<01:35:35.119> lisp<01:35:35.840> and<01:35:36.239> it's<01:35:36.400> very<01:35:36.639> attic<01:35:37.119> takes 01:35:37.430 --> 01:35:37.440 align:start position:0% in common lisp and it's very attic takes 01:35:37.440 --> 01:35:41.270 align:start position:0% in common lisp and it's very attic takes things<01:35:37.760> puts<01:35:38.000> them<01:35:38.159> in<01:35:38.239> a<01:35:38.320> list 01:35:41.270 --> 01:35:41.280 align:start position:0% 01:35:41.280 --> 01:35:43.510 align:start position:0% here<01:35:42.000> i<01:35:42.239> wrote<01:35:42.639> a<01:35:42.719> function<01:35:43.040> called<01:35:43.280> my 01:35:43.510 --> 01:35:43.520 align:start position:0% here i wrote a function called my 01:35:43.520 --> 01:35:45.270 align:start position:0% here i wrote a function called my function<01:35:43.920> that<01:35:44.080> takes<01:35:44.320> an<01:35:44.560> argument<01:35:45.040> called 01:35:45.270 --> 01:35:45.280 align:start position:0% function that takes an argument called 01:35:45.280 --> 01:35:45.669 align:start position:0% function that takes an argument called list 01:35:45.669 --> 01:35:45.679 align:start position:0% list 01:35:45.679 --> 01:35:48.790 align:start position:0% list and<01:35:45.840> returns<01:35:46.320> it<01:35:47.360> um<01:35:48.000> now<01:35:48.400> in 01:35:48.790 --> 01:35:48.800 align:start position:0% and returns it um now in 01:35:48.800 --> 01:35:52.629 align:start position:0% and returns it um now in closure<01:35:50.639> this<01:35:51.119> would 01:35:52.629 --> 01:35:52.639 align:start position:0% closure this would 01:35:52.639 --> 01:35:56.950 align:start position:0% closure this would this<01:35:52.880> function<01:35:53.760> parameter<01:35:54.320> would<01:35:54.840> shadow 01:35:56.950 --> 01:35:56.960 align:start position:0% this function parameter would shadow 01:35:56.960 --> 01:36:01.189 align:start position:0% this function parameter would shadow the<01:35:57.920> list<01:35:58.400> function<01:35:59.199> and<01:35:59.440> so 01:36:01.189 --> 01:36:01.199 align:start position:0% the list function and so 01:36:01.199 --> 01:36:04.629 align:start position:0% the list function and so we 01:36:04.629 --> 01:36:04.639 align:start position:0% 01:36:04.639 --> 01:36:21.669 align:start position:0% let<01:36:04.800> me<01:36:04.960> do<01:36:08.840> this 01:36:21.669 --> 01:36:21.679 align:start position:0% 01:36:21.679 --> 01:36:23.590 align:start position:0% okay<01:36:22.239> so<01:36:22.400> this<01:36:22.560> is<01:36:22.719> kind<01:36:22.880> of<01:36:22.960> confusing<01:36:23.440> let's 01:36:23.590 --> 01:36:23.600 align:start position:0% okay so this is kind of confusing let's 01:36:23.600 --> 01:36:30.870 align:start position:0% okay so this is kind of confusing let's see<01:36:23.760> what<01:36:23.840> it<01:36:23.920> does 01:36:30.870 --> 01:36:30.880 align:start position:0% 01:36:30.880 --> 01:36:33.910 align:start position:0% weird<01:36:31.280> okay<01:36:31.679> so<01:36:32.719> um 01:36:33.910 --> 01:36:33.920 align:start position:0% weird okay so um 01:36:33.920 --> 01:36:35.990 align:start position:0% weird okay so um we<01:36:34.080> have<01:36:34.320> an<01:36:34.480> argument<01:36:35.040> list<01:36:35.360> so<01:36:35.520> this<01:36:35.679> is<01:36:35.760> a 01:36:35.990 --> 01:36:36.000 align:start position:0% we have an argument list so this is a 01:36:36.000 --> 01:36:37.270 align:start position:0% we have an argument list so this is a lexical<01:36:36.639> variable 01:36:37.270 --> 01:36:37.280 align:start position:0% lexical variable 01:36:37.280 --> 01:36:40.470 align:start position:0% lexical variable which<01:36:37.600> means<01:36:38.000> it<01:36:38.239> is<01:36:38.320> a<01:36:38.560> symbol<01:36:40.000> whose 01:36:40.470 --> 01:36:40.480 align:start position:0% which means it is a symbol whose 01:36:40.480 --> 01:36:43.750 align:start position:0% which means it is a symbol whose so<01:36:40.719> a<01:36:40.800> symbol<01:36:41.199> in<01:36:41.360> lisp<01:36:41.679> is<01:36:41.840> a<01:36:42.880> is<01:36:43.040> mutable 01:36:43.750 --> 01:36:43.760 align:start position:0% so a symbol in lisp is a is mutable 01:36:43.760 --> 01:36:46.870 align:start position:0% so a symbol in lisp is a is mutable in<01:36:43.840> the<01:36:44.000> sense<01:36:44.320> that<01:36:45.360> symbols<01:36:45.760> have<01:36:46.000> a 01:36:46.870 --> 01:36:46.880 align:start position:0% in the sense that symbols have a 01:36:46.880 --> 01:36:50.790 align:start position:0% in the sense that symbols have a metadata<01:36:47.440> protocol<01:36:49.119> this<01:36:49.360> is<01:36:49.760> back<01:36:50.000> to<01:36:50.239> a<01:36:50.560> big 01:36:50.790 --> 01:36:50.800 align:start position:0% metadata protocol this is back to a big 01:36:50.800 --> 01:36:52.390 align:start position:0% metadata protocol this is back to a big significant<01:36:51.360> difference<01:36:51.679> in<01:36:51.760> syntax<01:36:52.159> which 01:36:52.390 --> 01:36:52.400 align:start position:0% significant difference in syntax which 01:36:52.400 --> 01:36:52.709 align:start position:0% significant difference in syntax which is 01:36:52.709 --> 01:36:52.719 align:start position:0% is 01:36:52.719 --> 01:36:55.669 align:start position:0% is in<01:36:52.960> closure<01:36:53.440> you<01:36:53.520> can<01:36:53.679> attach<01:36:54.080> metadata<01:36:55.440> to 01:36:55.669 --> 01:36:55.679 align:start position:0% in closure you can attach metadata to 01:36:55.679 --> 01:36:56.390 align:start position:0% in closure you can attach metadata to almost<01:36:56.000> any 01:36:56.390 --> 01:36:56.400 align:start position:0% almost any 01:36:56.400 --> 01:36:59.990 align:start position:0% almost any cl<01:36:56.800> anything<01:36:57.199> that's<01:36:57.440> readable 01:36:59.990 --> 01:37:00.000 align:start position:0% 01:37:00.000 --> 01:37:02.229 align:start position:0% there's<01:37:00.320> some<01:37:01.040> subtlety<01:37:01.520> there<01:37:01.760> into<01:37:02.000> whether 01:37:02.229 --> 01:37:02.239 align:start position:0% there's some subtlety there into whether 01:37:02.239 --> 01:37:04.070 align:start position:0% there's some subtlety there into whether the<01:37:02.400> metadata<01:37:03.040> is<01:37:03.280> copied 01:37:04.070 --> 01:37:04.080 align:start position:0% the metadata is copied 01:37:04.080 --> 01:37:06.629 align:start position:0% the metadata is copied if<01:37:04.239> you<01:37:04.719> add<01:37:05.119> something<01:37:05.600> to<01:37:05.920> that<01:37:06.320> like 01:37:06.629 --> 01:37:06.639 align:start position:0% if you add something to that like 01:37:06.639 --> 01:37:08.310 align:start position:0% if you add something to that like there's<01:37:06.880> a<01:37:06.960> concept<01:37:07.360> of<01:37:07.520> losing<01:37:07.840> metadata 01:37:08.310 --> 01:37:08.320 align:start position:0% there's a concept of losing metadata 01:37:08.320 --> 01:37:09.910 align:start position:0% there's a concept of losing metadata enclosure<01:37:08.960> like<01:37:09.119> if<01:37:09.280> you 01:37:09.910 --> 01:37:09.920 align:start position:0% enclosure like if you 01:37:09.920 --> 01:37:11.510 align:start position:0% enclosure like if you have<01:37:10.080> a<01:37:10.239> vector<01:37:10.480> with<01:37:10.639> metadata<01:37:11.199> on<01:37:11.280> it<01:37:11.440> and 01:37:11.510 --> 01:37:11.520 align:start position:0% have a vector with metadata on it and 01:37:11.520 --> 01:37:12.709 align:start position:0% have a vector with metadata on it and then<01:37:11.600> you<01:37:11.760> conjure<01:37:12.080> something<01:37:12.320> onto<01:37:12.560> that 01:37:12.709 --> 01:37:12.719 align:start position:0% then you conjure something onto that 01:37:12.719 --> 01:37:13.510 align:start position:0% then you conjure something onto that vector 01:37:13.510 --> 01:37:13.520 align:start position:0% vector 01:37:13.520 --> 01:37:15.189 align:start position:0% vector is<01:37:13.679> the<01:37:13.760> vector<01:37:14.080> you<01:37:14.239> get<01:37:14.400> back<01:37:14.719> does<01:37:14.880> it<01:37:14.960> still 01:37:15.189 --> 01:37:15.199 align:start position:0% is the vector you get back does it still 01:37:15.199 --> 01:37:17.430 align:start position:0% is the vector you get back does it still have<01:37:15.280> the<01:37:15.360> metadata 01:37:17.430 --> 01:37:17.440 align:start position:0% have the metadata 01:37:17.440 --> 01:37:19.350 align:start position:0% have the metadata and<01:37:17.600> i<01:37:17.679> think<01:37:17.920> it<01:37:18.080> does<01:37:18.400> in<01:37:18.480> most<01:37:18.719> cases<01:37:19.280> but 01:37:19.350 --> 01:37:19.360 align:start position:0% and i think it does in most cases but 01:37:19.360 --> 01:37:20.790 align:start position:0% and i think it does in most cases but there<01:37:19.520> might<01:37:19.679> be<01:37:19.840> cases<01:37:20.080> when<01:37:20.320> it<01:37:20.400> doesn't<01:37:20.639> but 01:37:20.790 --> 01:37:20.800 align:start position:0% there might be cases when it doesn't but 01:37:20.800 --> 01:37:21.109 align:start position:0% there might be cases when it doesn't but an 01:37:21.109 --> 01:37:21.119 align:start position:0% an 01:37:21.119 --> 01:37:23.270 align:start position:0% an area<01:37:21.360> of<01:37:21.440> subtlety<01:37:21.840> and<01:37:21.920> closure<01:37:22.960> in<01:37:23.040> common 01:37:23.270 --> 01:37:23.280 align:start position:0% area of subtlety and closure in common 01:37:23.280 --> 01:37:25.109 align:start position:0% area of subtlety and closure in common list<01:37:23.520> there<01:37:23.679> is<01:37:23.840> no<01:37:24.000> general<01:37:24.320> metadata<01:37:24.880> thing 01:37:25.109 --> 01:37:25.119 align:start position:0% list there is no general metadata thing 01:37:25.119 --> 01:37:27.990 align:start position:0% list there is no general metadata thing there's<01:37:25.280> not<01:37:25.440> syntax<01:37:25.840> for<01:37:26.080> it 01:37:27.990 --> 01:37:28.000 align:start position:0% there's not syntax for it 01:37:28.000 --> 01:37:31.669 align:start position:0% there's not syntax for it but<01:37:29.119> symbols<01:37:29.840> are<01:37:30.639> mutable<01:37:31.119> in<01:37:31.280> the<01:37:31.360> sense 01:37:31.669 --> 01:37:31.679 align:start position:0% but symbols are mutable in the sense 01:37:31.679 --> 01:37:33.510 align:start position:0% but symbols are mutable in the sense that<01:37:31.920> they<01:37:32.159> carry<01:37:32.480> a<01:37:32.639> property<01:37:33.119> list 01:37:33.510 --> 01:37:33.520 align:start position:0% that they carry a property list 01:37:33.520 --> 01:37:36.870 align:start position:0% that they carry a property list which<01:37:33.760> is<01:37:34.800> a<01:37:35.199> set<01:37:35.440> of<01:37:35.679> associations<01:37:36.480> between 01:37:36.870 --> 01:37:36.880 align:start position:0% which is a set of associations between 01:37:36.880 --> 01:37:38.709 align:start position:0% which is a set of associations between other<01:37:37.040> symbols<01:37:37.440> and<01:37:37.520> values 01:37:38.709 --> 01:37:38.719 align:start position:0% other symbols and values 01:37:38.719 --> 01:37:40.870 align:start position:0% other symbols and values and<01:37:39.119> they<01:37:39.360> also<01:37:39.600> have<01:37:40.400> what<01:37:40.560> are 01:37:40.870 --> 01:37:40.880 align:start position:0% and they also have what are 01:37:40.880 --> 01:37:42.149 align:start position:0% and they also have what are traditionally<01:37:41.360> called<01:37:41.600> the<01:37:41.679> function<01:37:42.080> and 01:37:42.149 --> 01:37:42.159 align:start position:0% traditionally called the function and 01:37:42.159 --> 01:37:42.629 align:start position:0% traditionally called the function and value 01:37:42.629 --> 01:37:42.639 align:start position:0% value 01:37:42.639 --> 01:37:45.189 align:start position:0% value cells<01:37:43.199> and<01:37:43.360> these<01:37:43.520> are<01:37:43.679> basically<01:37:44.239> slots<01:37:44.880> or 01:37:45.189 --> 01:37:45.199 align:start position:0% cells and these are basically slots or 01:37:45.199 --> 01:37:47.189 align:start position:0% cells and these are basically slots or fields<01:37:45.679> on<01:37:45.840> the<01:37:46.000> symbol 01:37:47.189 --> 01:37:47.199 align:start position:0% fields on the symbol 01:37:47.199 --> 01:37:50.390 align:start position:0% fields on the symbol that<01:37:47.440> can<01:37:47.760> either<01:37:48.159> carry<01:37:48.880> a<01:37:49.119> value<01:37:49.760> at<01:37:50.000> some 01:37:50.390 --> 01:37:50.400 align:start position:0% that can either carry a value at some 01:37:50.400 --> 01:37:54.149 align:start position:0% that can either carry a value at some in<01:37:50.560> some<01:37:50.800> environment<01:37:51.679> or<01:37:52.480> a<01:37:52.560> function<01:37:52.960> value 01:37:54.149 --> 01:37:54.159 align:start position:0% in some environment or a function value 01:37:54.159 --> 01:37:57.270 align:start position:0% in some environment or a function value and<01:37:55.520> by<01:37:55.760> default<01:37:56.239> if<01:37:56.400> you<01:37:56.480> just<01:37:56.639> refer<01:37:57.040> to<01:37:57.199> a 01:37:57.270 --> 01:37:57.280 align:start position:0% and by default if you just refer to a 01:37:57.280 --> 01:37:57.750 align:start position:0% and by default if you just refer to a symbol 01:37:57.750 --> 01:37:57.760 align:start position:0% symbol 01:37:57.760 --> 01:38:00.629 align:start position:0% symbol without<01:37:58.080> any<01:37:58.400> qualification<01:37:59.760> it's<01:38:00.000> the<01:38:00.159> value 01:38:00.629 --> 01:38:00.639 align:start position:0% without any qualification it's the value 01:38:00.639 --> 01:38:01.189 align:start position:0% without any qualification it's the value cell 01:38:01.189 --> 01:38:01.199 align:start position:0% cell 01:38:01.199 --> 01:38:04.390 align:start position:0% cell that<01:38:01.440> is<01:38:01.520> going<01:38:01.679> to<01:38:01.920> be<01:38:02.560> accessed<01:38:04.080> and<01:38:04.239> so 01:38:04.390 --> 01:38:04.400 align:start position:0% that is going to be accessed and so 01:38:04.400 --> 01:38:04.950 align:start position:0% that is going to be accessed and so that's 01:38:04.950 --> 01:38:04.960 align:start position:0% that's 01:38:04.960 --> 01:38:08.229 align:start position:0% that's effectively<01:38:05.600> how<01:38:06.080> lisp<01:38:06.560> ii<01:38:06.800> is<01:38:06.960> implemented 01:38:08.229 --> 01:38:08.239 align:start position:0% effectively how lisp ii is implemented 01:38:08.239 --> 01:38:11.430 align:start position:0% effectively how lisp ii is implemented is<01:38:08.800> its<01:38:09.679> admission<01:38:10.400> of<01:38:11.040> the 01:38:11.430 --> 01:38:11.440 align:start position:0% is its admission of the 01:38:11.440 --> 01:38:14.470 align:start position:0% is its admission of the symbol<01:38:12.080> as<01:38:12.480> a<01:38:12.719> mutable<01:38:13.199> container 01:38:14.470 --> 01:38:14.480 align:start position:0% symbol as a mutable container 01:38:14.480 --> 01:38:16.310 align:start position:0% symbol as a mutable container and<01:38:14.639> then<01:38:14.800> it's<01:38:15.040> the<01:38:15.199> admission<01:38:15.840> of<01:38:16.159> a 01:38:16.310 --> 01:38:16.320 align:start position:0% and then it's the admission of a 01:38:16.320 --> 01:38:18.229 align:start position:0% and then it's the admission of a syntactic<01:38:16.960> default 01:38:18.229 --> 01:38:18.239 align:start position:0% syntactic default 01:38:18.239 --> 01:38:21.910 align:start position:0% syntactic default to<01:38:19.920> interpret<01:38:20.800> occurrences 01:38:21.910 --> 01:38:21.920 align:start position:0% to interpret occurrences 01:38:21.920 --> 01:38:25.189 align:start position:0% to interpret occurrences of<01:38:22.480> symbols<01:38:23.040> as<01:38:23.760> accesses<01:38:24.320> of<01:38:24.400> their<01:38:24.639> values 01:38:25.189 --> 01:38:25.199 align:start position:0% of symbols as accesses of their values 01:38:25.199 --> 01:38:26.950 align:start position:0% of symbols as accesses of their values and<01:38:25.360> not<01:38:25.600> necessarily<01:38:26.239> accesses<01:38:26.719> of<01:38:26.800> their 01:38:26.950 --> 01:38:26.960 align:start position:0% and not necessarily accesses of their 01:38:26.960 --> 01:38:28.830 align:start position:0% and not necessarily accesses of their function<01:38:27.360> values 01:38:28.830 --> 01:38:28.840 align:start position:0% function values 01:38:28.840 --> 01:38:31.990 align:start position:0% function values right<01:38:29.920> so<01:38:30.560> in<01:38:30.719> this<01:38:30.880> function<01:38:31.520> we<01:38:31.840> have<01:38:31.920> this 01:38:31.990 --> 01:38:32.000 align:start position:0% right so in this function we have this 01:38:32.000 --> 01:38:33.030 align:start position:0% right so in this function we have this parameter<01:38:32.480> list 01:38:33.030 --> 01:38:33.040 align:start position:0% parameter list 01:38:33.040 --> 01:38:36.310 align:start position:0% parameter list lexically<01:38:33.679> it<01:38:33.760> takes<01:38:34.159> the<01:38:34.480> value<01:38:35.840> of<01:38:36.159> the 01:38:36.310 --> 01:38:36.320 align:start position:0% lexically it takes the value of the 01:38:36.320 --> 01:38:37.189 align:start position:0% lexically it takes the value of the parameter 01:38:37.189 --> 01:38:37.199 align:start position:0% parameter 01:38:37.199 --> 01:38:39.910 align:start position:0% parameter that's<01:38:37.600> activated<01:38:38.159> on<01:38:38.239> the<01:38:38.320> stack<01:38:39.520> when<01:38:39.760> it's 01:38:39.910 --> 01:38:39.920 align:start position:0% that's activated on the stack when it's 01:38:39.920 --> 01:38:40.870 align:start position:0% that's activated on the stack when it's activated<01:38:40.320> on<01:38:40.400> the<01:38:40.480> stack 01:38:40.870 --> 01:38:40.880 align:start position:0% activated on the stack 01:38:40.880 --> 01:38:43.830 align:start position:0% activated on the stack and<01:38:41.119> then<01:38:41.440> so<01:38:41.600> now<01:38:41.920> list<01:38:42.639> is<01:38:42.800> a<01:38:42.960> variable<01:38:43.520> but 01:38:43.830 --> 01:38:43.840 align:start position:0% and then so now list is a variable but 01:38:43.840 --> 01:38:44.229 align:start position:0% and then so now list is a variable but look 01:38:44.229 --> 01:38:44.239 align:start position:0% look 01:38:44.239 --> 01:38:47.189 align:start position:0% look on<01:38:44.560> this<01:38:44.960> i<01:38:45.040> don't<01:38:45.199> have<01:38:45.280> line<01:38:45.520> numbers<01:38:45.840> here<01:38:47.040> i 01:38:47.189 --> 01:38:47.199 align:start position:0% on this i don't have line numbers here i 01:38:47.199 --> 01:38:51.030 align:start position:0% on this i don't have line numbers here i have<01:38:47.360> a<01:38:47.520> call<01:38:47.920> to<01:38:48.080> the<01:38:48.239> list<01:38:48.560> function 01:38:51.030 --> 01:38:51.040 align:start position:0% 01:38:51.040 --> 01:38:53.669 align:start position:0% well<01:38:51.440> because<01:38:52.320> that's<01:38:52.639> a<01:38:52.800> syntax<01:38:53.360> enlist 01:38:53.669 --> 01:38:53.679 align:start position:0% well because that's a syntax enlist 01:38:53.679 --> 01:38:55.189 align:start position:0% well because that's a syntax enlist called<01:38:54.000> an<01:38:54.159> operation<01:38:54.719> form 01:38:55.189 --> 01:38:55.199 align:start position:0% called an operation form 01:38:55.199 --> 01:38:57.350 align:start position:0% called an operation form we<01:38:55.360> have<01:38:55.520> a<01:38:55.679> symbol<01:38:56.239> a<01:38:56.400> list<01:38:56.719> with<01:38:56.880> a<01:38:56.960> symbol 01:38:57.350 --> 01:38:57.360 align:start position:0% we have a symbol a list with a symbol 01:38:57.360 --> 01:39:00.629 align:start position:0% we have a symbol a list with a symbol and<01:38:57.440> some<01:38:57.600> number<01:38:57.840> of<01:38:58.000> arguments 01:39:00.629 --> 01:39:00.639 align:start position:0% 01:39:00.639 --> 01:39:02.390 align:start position:0% that's<01:39:00.960> distinct<01:39:01.360> as<01:39:01.520> a<01:39:01.600> reference<01:39:01.920> to<01:39:02.080> the 01:39:02.390 --> 01:39:02.400 align:start position:0% that's distinct as a reference to the 01:39:02.400 --> 01:39:04.229 align:start position:0% that's distinct as a reference to the function<01:39:02.960> cell<01:39:03.360> of 01:39:04.229 --> 01:39:04.239 align:start position:0% function cell of 01:39:04.239 --> 01:39:09.430 align:start position:0% function cell of list<01:39:05.040> and<01:39:05.280> which<01:39:05.440> we<01:39:05.600> can<01:39:05.760> look<01:39:06.000> at 01:39:09.430 --> 01:39:09.440 align:start position:0% 01:39:09.440 --> 01:39:14.790 align:start position:0% oh<01:39:10.840> whoops 01:39:14.790 --> 01:39:14.800 align:start position:0% 01:39:14.800 --> 01:39:16.310 align:start position:0% so<01:39:14.960> there's<01:39:15.199> another<01:39:15.600> operator<01:39:16.000> called 01:39:16.310 --> 01:39:16.320 align:start position:0% so there's another operator called 01:39:16.320 --> 01:39:18.550 align:start position:0% so there's another operator called function<01:39:16.800> which<01:39:17.119> takes<01:39:17.440> a<01:39:17.600> symbol 01:39:18.550 --> 01:39:18.560 align:start position:0% function which takes a symbol 01:39:18.560 --> 01:39:21.830 align:start position:0% function which takes a symbol and<01:39:19.040> will<01:39:19.440> give<01:39:19.679> you<01:39:20.800> the<01:39:20.960> actual<01:39:21.360> function 01:39:21.830 --> 01:39:21.840 align:start position:0% and will give you the actual function 01:39:21.840 --> 01:39:22.629 align:start position:0% and will give you the actual function value 01:39:22.629 --> 01:39:22.639 align:start position:0% value 01:39:22.639 --> 01:39:25.430 align:start position:0% value so<01:39:22.800> that's<01:39:23.119> like<01:39:23.520> the<01:39:24.480> instance<01:39:25.040> of<01:39:25.199> the 01:39:25.430 --> 01:39:25.440 align:start position:0% so that's like the instance of the 01:39:25.440 --> 01:39:26.229 align:start position:0% so that's like the instance of the function 01:39:26.229 --> 01:39:26.239 align:start position:0% function 01:39:26.239 --> 01:39:29.189 align:start position:0% function as<01:39:26.480> opposed<01:39:26.880> to<01:39:27.760> the<01:39:28.000> instance<01:39:28.400> of<01:39:28.480> the<01:39:28.639> name 01:39:29.189 --> 01:39:29.199 align:start position:0% as opposed to the instance of the name 01:39:29.199 --> 01:39:29.910 align:start position:0% as opposed to the instance of the name that 01:39:29.910 --> 01:39:29.920 align:start position:0% that 01:39:29.920 --> 01:39:35.430 align:start position:0% that contains<01:39:30.400> the<01:39:30.480> function<01:39:30.960> inside<01:39:31.199> of<01:39:31.360> it<01:39:32.400> um 01:39:35.430 --> 01:39:35.440 align:start position:0% 01:39:35.440 --> 01:39:40.390 align:start position:0% yeah<01:39:35.679> so<01:39:35.920> it's<01:39:36.159> that<01:39:36.800> this<01:39:38.840> object 01:39:40.390 --> 01:39:40.400 align:start position:0% yeah so it's that this object 01:39:40.400 --> 01:39:42.870 align:start position:0% yeah so it's that this object is<01:39:40.480> what<01:39:40.639> we're<01:39:40.880> extracting<01:39:42.320> here<01:39:42.639> as<01:39:42.800> the 01:39:42.870 --> 01:39:42.880 align:start position:0% is what we're extracting here as the 01:39:42.880 --> 01:39:45.109 align:start position:0% is what we're extracting here as the first<01:39:43.119> argument<01:39:43.520> to<01:39:43.679> apply 01:39:45.109 --> 01:39:45.119 align:start position:0% first argument to apply 01:39:45.119 --> 01:39:48.390 align:start position:0% first argument to apply so<01:39:47.760> you<01:39:47.920> can<01:39:48.080> see 01:39:48.390 --> 01:39:48.400 align:start position:0% so you can see 01:39:48.400 --> 01:39:51.430 align:start position:0% so you can see these<01:39:48.719> two<01:39:50.000> return<01:39:50.480> the<01:39:50.560> same<01:39:50.880> object<01:39:51.360> and 01:39:51.430 --> 01:39:51.440 align:start position:0% these two return the same object and 01:39:51.440 --> 01:39:52.950 align:start position:0% these two return the same object and that's<01:39:51.760> because 01:39:52.950 --> 01:39:52.960 align:start position:0% that's because 01:39:52.960 --> 01:39:56.790 align:start position:0% that's because this<01:39:53.199> hash<01:39:53.679> quote<01:39:54.320> is<01:39:55.920> a 01:39:56.790 --> 01:39:56.800 align:start position:0% this hash quote is a 01:39:56.800 --> 01:40:00.229 align:start position:0% this hash quote is a reader<01:39:57.119> macro<01:39:58.239> that<01:39:58.719> basically<01:39:59.360> expands<01:40:00.080> to 01:40:00.229 --> 01:40:00.239 align:start position:0% reader macro that basically expands to 01:40:00.239 --> 01:40:01.510 align:start position:0% reader macro that basically expands to this 01:40:01.510 --> 01:40:01.520 align:start position:0% this 01:40:01.520 --> 01:40:05.669 align:start position:0% this you<01:40:01.679> can<01:40:01.760> think<01:40:01.840> of<01:40:02.000> it<01:40:02.080> as<01:40:02.239> expanding<01:40:02.560> to<01:40:02.719> that 01:40:05.669 --> 01:40:05.679 align:start position:0% 01:40:05.679 --> 01:40:09.990 align:start position:0% um<01:40:07.119> yep<01:40:07.520> so<01:40:08.560> this<01:40:08.800> occurrence<01:40:09.280> of<01:40:09.440> list 01:40:09.990 --> 01:40:10.000 align:start position:0% um yep so this occurrence of list 01:40:10.000 --> 01:40:11.669 align:start position:0% um yep so this occurrence of list is<01:40:10.239> not<01:40:10.400> a<01:40:10.560> function<01:40:10.960> call<01:40:11.199> we<01:40:11.360> could<01:40:11.520> say 01:40:11.669 --> 01:40:11.679 align:start position:0% is not a function call we could say 01:40:11.679 --> 01:40:14.310 align:start position:0% is not a function call we could say that's<01:40:12.239> uh<01:40:12.960> the<01:40:13.119> symbol<01:40:13.440> appears<01:40:13.840> in<01:40:13.920> value 01:40:14.310 --> 01:40:14.320 align:start position:0% that's uh the symbol appears in value 01:40:14.320 --> 01:40:15.510 align:start position:0% that's uh the symbol appears in value position<01:40:14.719> maybe 01:40:15.510 --> 01:40:15.520 align:start position:0% position maybe 01:40:15.520 --> 01:40:16.950 align:start position:0% position maybe but<01:40:15.679> you<01:40:15.760> could<01:40:15.920> say<01:40:16.159> whether<01:40:16.480> or<01:40:16.560> not<01:40:16.800> we're 01:40:16.950 --> 01:40:16.960 align:start position:0% but you could say whether or not we're 01:40:16.960 --> 01:40:19.030 align:start position:0% but you could say whether or not we're accessing<01:40:17.440> the<01:40:17.520> symbol<01:40:17.760> or<01:40:17.920> the<01:40:18.000> function<01:40:18.400> is 01:40:19.030 --> 01:40:19.040 align:start position:0% accessing the symbol or the function is 01:40:19.040 --> 01:40:20.629 align:start position:0% accessing the symbol or the function is you<01:40:19.119> know<01:40:19.280> syntactically<01:40:19.920> dependent<01:40:20.400> and 01:40:20.629 --> 01:40:20.639 align:start position:0% you know syntactically dependent and 01:40:20.639 --> 01:40:25.510 align:start position:0% you know syntactically dependent and lexically<01:40:21.119> dependent 01:40:25.510 --> 01:40:25.520 align:start position:0% 01:40:25.520 --> 01:40:32.310 align:start position:0% any<01:40:25.760> questions<01:40:26.080> about<01:40:26.320> that 01:40:32.310 --> 01:40:32.320 align:start position:0% 01:40:32.320 --> 01:40:35.669 align:start position:0% cool<01:40:33.520> maybe<01:40:34.400> maybe<01:40:34.639> you<01:40:34.800> want<01:40:34.960> to<01:40:35.040> show<01:40:35.280> funk 01:40:35.669 --> 01:40:35.679 align:start position:0% cool maybe maybe you want to show funk 01:40:35.679 --> 01:40:36.950 align:start position:0% cool maybe maybe you want to show funk all<01:40:35.920> because 01:40:36.950 --> 01:40:36.960 align:start position:0% all because 01:40:36.960 --> 01:40:40.470 align:start position:0% all because that's<01:40:37.280> the<01:40:38.080> entire<01:40:38.480> of<01:40:38.560> the<01:40:38.719> function 01:40:40.470 --> 01:40:40.480 align:start position:0% that's the entire of the function 01:40:40.480 --> 01:40:43.350 align:start position:0% that's the entire of the function [Music] 01:40:43.350 --> 01:40:43.360 align:start position:0% [Music] 01:40:43.360 --> 01:40:46.790 align:start position:0% [Music] oh<01:40:43.920> well<01:40:44.159> there's<01:40:44.400> uh 01:40:46.790 --> 01:40:46.800 align:start position:0% 01:40:46.800 --> 01:40:50.390 align:start position:0% uh<01:40:48.560> yeah<01:40:48.880> i<01:40:48.960> mean<01:40:49.520> map<01:40:49.840> car 01:40:50.390 --> 01:40:50.400 align:start position:0% uh yeah i mean map car 01:40:50.400 --> 01:40:59.510 align:start position:0% uh yeah i mean map car is<01:40:50.960> what<01:40:51.360> closure<01:40:51.760> we<01:40:51.920> know<01:40:52.080> enclosure<01:40:52.480> is<01:40:52.560> map 01:40:59.510 --> 01:40:59.520 align:start position:0% 01:40:59.520 --> 01:41:03.669 align:start position:0% so<01:41:00.159> um 01:41:03.669 --> 01:41:03.679 align:start position:0% 01:41:03.679 --> 01:41:06.709 align:start position:0% map<01:41:04.000> car<01:41:04.400> is<01:41:04.560> a<01:41:04.639> higher<01:41:04.880> order<01:41:05.199> function<01:41:06.480> and 01:41:06.709 --> 01:41:06.719 align:start position:0% map car is a higher order function and 01:41:06.719 --> 01:41:08.310 align:start position:0% map car is a higher order function and it<01:41:06.880> takes 01:41:08.310 --> 01:41:08.320 align:start position:0% it takes 01:41:08.320 --> 01:41:10.470 align:start position:0% it takes a<01:41:08.480> function<01:41:08.960> as<01:41:09.199> its<01:41:09.360> first<01:41:09.760> argument<01:41:10.320> and 01:41:10.470 --> 01:41:10.480 align:start position:0% a function as its first argument and 01:41:10.480 --> 01:41:11.590 align:start position:0% a function as its first argument and then 01:41:11.590 --> 01:41:11.600 align:start position:0% then 01:41:11.600 --> 01:41:13.510 align:start position:0% then a<01:41:11.760> list<01:41:12.080> as<01:41:12.239> its<01:41:12.560> second<01:41:12.880> argument<01:41:13.280> and<01:41:13.360> it 01:41:13.510 --> 01:41:13.520 align:start position:0% a list as its second argument and it 01:41:13.520 --> 01:41:14.790 align:start position:0% a list as its second argument and it iterates<01:41:13.920> through<01:41:14.080> the<01:41:14.159> list<01:41:14.400> and<01:41:14.480> applies 01:41:14.790 --> 01:41:14.800 align:start position:0% iterates through the list and applies 01:41:14.800 --> 01:41:16.950 align:start position:0% iterates through the list and applies the<01:41:14.880> function<01:41:15.360> to<01:41:15.520> each<01:41:15.679> element 01:41:16.950 --> 01:41:16.960 align:start position:0% the function to each element 01:41:16.960 --> 01:41:20.550 align:start position:0% the function to each element um<01:41:17.679> i<01:41:17.920> believe<01:41:19.679> so<01:41:19.920> in<01:41:20.000> lisp<01:41:20.320> there's<01:41:20.480> a 01:41:20.550 --> 01:41:20.560 align:start position:0% um i believe so in lisp there's a 01:41:20.560 --> 01:41:22.709 align:start position:0% um i believe so in lisp there's a concept<01:41:20.960> of<01:41:21.119> designator 01:41:22.709 --> 01:41:22.719 align:start position:0% concept of designator 01:41:22.719 --> 01:41:27.990 align:start position:0% concept of designator which<01:41:22.960> is<01:41:23.280> uh<01:41:25.679> basically 01:41:27.990 --> 01:41:28.000 align:start position:0% which is uh basically 01:41:28.000 --> 01:41:30.070 align:start position:0% which is uh basically it's<01:41:28.159> kind<01:41:28.400> of<01:41:28.480> like<01:41:28.719> a<01:41:28.880> polymorphism<01:41:29.760> system 01:41:30.070 --> 01:41:30.080 align:start position:0% it's kind of like a polymorphism system 01:41:30.080 --> 01:41:31.109 align:start position:0% it's kind of like a polymorphism system in<01:41:30.239> the<01:41:30.320> sense<01:41:30.639> that<01:41:30.880> it 01:41:31.109 --> 01:41:31.119 align:start position:0% in the sense that it 01:41:31.119 --> 01:41:35.270 align:start position:0% in the sense that it acknowledges<01:41:31.920> that<01:41:33.760> uh<01:41:34.080> intuitively 01:41:35.270 --> 01:41:35.280 align:start position:0% acknowledges that uh intuitively 01:41:35.280 --> 01:41:37.430 align:start position:0% acknowledges that uh intuitively we<01:41:35.440> want<01:41:35.679> to<01:41:35.760> use<01:41:36.400> a<01:41:36.560> set<01:41:36.800> of<01:41:36.960> objects<01:41:37.280> to 01:41:37.430 --> 01:41:37.440 align:start position:0% we want to use a set of objects to 01:41:37.440 --> 01:41:39.189 align:start position:0% we want to use a set of objects to represent<01:41:37.840> the<01:41:38.000> same<01:41:38.239> idea 01:41:39.189 --> 01:41:39.199 align:start position:0% represent the same idea 01:41:39.199 --> 01:41:44.229 align:start position:0% represent the same idea and<01:41:39.440> in<01:41:39.520> this<01:41:39.760> case<01:41:40.880> the<01:41:41.040> symbol<01:41:42.080> one<01:41:42.400> plus 01:41:44.229 --> 01:41:44.239 align:start position:0% and in this case the symbol one plus 01:41:44.239 --> 01:41:46.709 align:start position:0% and in this case the symbol one plus now<01:41:44.480> strictly<01:41:44.880> speaking<01:41:45.360> this<01:41:45.600> is<01:41:45.760> a<01:41:46.239> a<01:41:46.400> quoted 01:41:46.709 --> 01:41:46.719 align:start position:0% now strictly speaking this is a a quoted 01:41:46.719 --> 01:41:47.750 align:start position:0% now strictly speaking this is a a quoted symbol 01:41:47.750 --> 01:41:47.760 align:start position:0% symbol 01:41:47.760 --> 01:41:49.910 align:start position:0% symbol but<01:41:48.000> in<01:41:48.159> a<01:41:48.320> context<01:41:48.880> where<01:41:49.040> we<01:41:49.199> were<01:41:49.440> expecting 01:41:49.910 --> 01:41:49.920 align:start position:0% but in a context where we were expecting 01:41:49.920 --> 01:41:50.950 align:start position:0% but in a context where we were expecting for<01:41:50.080> the<01:41:50.239> cloaded 01:41:50.950 --> 01:41:50.960 align:start position:0% for the cloaded 01:41:50.960 --> 01:41:54.310 align:start position:0% for the cloaded symbol<01:41:51.280> to<01:41:51.360> represent<01:41:52.080> a<01:41:52.239> function<01:41:53.600> um 01:41:54.310 --> 01:41:54.320 align:start position:0% symbol to represent a function um 01:41:54.320 --> 01:41:56.870 align:start position:0% symbol to represent a function um we<01:41:54.480> would<01:41:54.639> want<01:41:54.880> it<01:41:54.960> to<01:41:55.119> designate<01:41:55.600> a<01:41:55.679> function 01:41:56.870 --> 01:41:56.880 align:start position:0% we would want it to designate a function 01:41:56.880 --> 01:41:57.590 align:start position:0% we would want it to designate a function and<01:41:57.040> so 01:41:57.590 --> 01:41:57.600 align:start position:0% and so 01:41:57.600 --> 01:42:03.350 align:start position:0% and so i<01:41:57.760> think<01:41:58.000> in<01:41:58.080> the<01:41:58.239> case<01:41:58.480> of<01:41:58.560> map<01:41:58.880> car 01:42:03.350 --> 01:42:03.360 align:start position:0% 01:42:03.360 --> 01:42:05.430 align:start position:0% we<01:42:03.520> could<01:42:03.679> also<01:42:04.080> pass<01:42:04.400> it<01:42:04.639> the<01:42:04.800> symbol<01:42:05.199> one 01:42:05.430 --> 01:42:05.440 align:start position:0% we could also pass it the symbol one 01:42:05.440 --> 01:42:07.910 align:start position:0% we could also pass it the symbol one plus<01:42:05.760> and<01:42:05.920> it<01:42:06.080> will<01:42:06.239> infer<01:42:06.719> for<01:42:07.040> us<01:42:07.280> that<01:42:07.520> hey 01:42:07.910 --> 01:42:07.920 align:start position:0% plus and it will infer for us that hey 01:42:07.920 --> 01:42:10.229 align:start position:0% plus and it will infer for us that hey i'm<01:42:08.239> passing<01:42:08.560> you<01:42:08.639> the<01:42:08.800> symbol<01:42:09.119> for<01:42:09.280> its<01:42:10.000> for 01:42:10.229 --> 01:42:10.239 align:start position:0% i'm passing you the symbol for its for 01:42:10.239 --> 01:42:11.430 align:start position:0% i'm passing you the symbol for its for its<01:42:10.480> use<01:42:10.719> as<01:42:10.880> a<01:42:10.960> function 01:42:11.430 --> 01:42:11.440 align:start position:0% its use as a function 01:42:11.440 --> 01:42:20.310 align:start position:0% its use as a function and<01:42:11.600> so<01:42:11.760> we<01:42:11.920> don't<01:42:12.159> need<01:42:13.280> to<01:42:13.440> wrap<01:42:13.760> it<01:42:14.000> in 01:42:20.310 --> 01:42:20.320 align:start position:0% 01:42:20.320 --> 01:42:21.990 align:start position:0% so<01:42:20.480> there's<01:42:20.639> a<01:42:20.639> lot<01:42:20.800> of<01:42:20.880> ways<01:42:21.119> to<01:42:21.199> do<01:42:21.360> this<01:42:21.760> and 01:42:21.990 --> 01:42:22.000 align:start position:0% so there's a lot of ways to do this and 01:42:22.000 --> 01:42:24.470 align:start position:0% so there's a lot of ways to do this and they're<01:42:22.239> all<01:42:22.480> different<01:42:22.880> variations<01:42:23.600> of 01:42:24.470 --> 01:42:24.480 align:start position:0% they're all different variations of 01:42:24.480 --> 01:42:27.990 align:start position:0% they're all different variations of you<01:42:24.639> know<01:42:25.199> this<01:42:25.440> general<01:42:25.840> idea<01:42:26.159> that<01:42:26.840> um 01:42:27.990 --> 01:42:28.000 align:start position:0% you know this general idea that um 01:42:28.000 --> 01:42:30.310 align:start position:0% you know this general idea that um we<01:42:28.960> have<01:42:29.119> a<01:42:29.199> symbol<01:42:29.520> that<01:42:29.679> can<01:42:29.840> have<01:42:29.920> multiple 01:42:30.310 --> 01:42:30.320 align:start position:0% we have a symbol that can have multiple 01:42:30.320 --> 01:42:31.030 align:start position:0% we have a symbol that can have multiple meanings 01:42:31.030 --> 01:42:31.040 align:start position:0% meanings 01:42:31.040 --> 01:42:32.870 align:start position:0% meanings and<01:42:31.600> there<01:42:31.840> are<01:42:32.000> different<01:42:32.239> contexts<01:42:32.800> in 01:42:32.870 --> 01:42:32.880 align:start position:0% and there are different contexts in 01:42:32.880 --> 01:42:35.189 align:start position:0% and there are different contexts in which<01:42:33.440> the<01:42:33.600> meanings<01:42:33.920> will<01:42:34.000> be 01:42:35.189 --> 01:42:35.199 align:start position:0% which the meanings will be 01:42:35.199 --> 01:42:37.830 align:start position:0% which the meanings will be inferred<01:42:35.840> automatically<01:42:37.119> and<01:42:37.280> but<01:42:37.440> we<01:42:37.600> also 01:42:37.830 --> 01:42:37.840 align:start position:0% inferred automatically and but we also 01:42:37.840 --> 01:42:39.350 align:start position:0% inferred automatically and but we also have<01:42:38.080> tools<01:42:38.480> to<01:42:38.639> make 01:42:39.350 --> 01:42:39.360 align:start position:0% have tools to make 01:42:39.360 --> 01:42:41.270 align:start position:0% have tools to make explicit<01:42:39.920> references<01:42:40.400> to<01:42:40.639> aspects<01:42:41.040> of<01:42:41.119> this 01:42:41.270 --> 01:42:41.280 align:start position:0% explicit references to aspects of this 01:42:41.280 --> 01:42:44.950 align:start position:0% explicit references to aspects of this symbol 01:42:44.950 --> 01:42:44.960 align:start position:0% 01:42:44.960 --> 01:42:47.270 align:start position:0% so<01:42:45.280> yeah<01:42:45.520> i<01:42:45.600> mean<01:42:45.920> not<01:42:46.080> very<01:42:46.320> savory<01:42:46.880> honestly 01:42:47.270 --> 01:42:47.280 align:start position:0% so yeah i mean not very savory honestly 01:42:47.280 --> 01:42:48.709 align:start position:0% so yeah i mean not very savory honestly from<01:42:47.440> a<01:42:47.520> closure<01:42:47.840> perspective<01:42:48.400> like<01:42:48.560> these 01:42:48.709 --> 01:42:48.719 align:start position:0% from a closure perspective like these 01:42:48.719 --> 01:42:51.830 align:start position:0% from a closure perspective like these are<01:42:48.880> all<01:42:48.960> the<01:42:49.040> details<01:42:49.600> that 01:42:51.830 --> 01:42:51.840 align:start position:0% 01:42:51.840 --> 01:42:53.750 align:start position:0% closure<01:42:52.239> helps<01:42:52.480> us<01:42:52.639> avoid<01:42:53.119> but<01:42:53.360> at<01:42:53.440> the<01:42:53.520> same 01:42:53.750 --> 01:42:53.760 align:start position:0% closure helps us avoid but at the same 01:42:53.760 --> 01:42:55.590 align:start position:0% closure helps us avoid but at the same time<01:42:54.400> there<01:42:54.560> is<01:42:54.719> some<01:42:54.880> value<01:42:55.360> in 01:42:55.590 --> 01:42:55.600 align:start position:0% time there is some value in 01:42:55.600 --> 01:42:58.629 align:start position:0% time there is some value in them<01:42:55.840> existing<01:42:56.560> because<01:42:57.119> you<01:42:57.360> have 01:42:58.629 --> 01:42:58.639 align:start position:0% them existing because you have 01:42:58.639 --> 01:43:02.870 align:start position:0% them existing because you have um<01:43:01.119> uh 01:43:02.870 --> 01:43:02.880 align:start position:0% um uh 01:43:02.880 --> 01:43:05.910 align:start position:0% um uh you<01:43:03.040> have<01:43:03.600> more<01:43:03.840> flexibility<01:43:04.560> along<01:43:05.440> certain 01:43:05.910 --> 01:43:05.920 align:start position:0% you have more flexibility along certain 01:43:05.920 --> 01:43:08.470 align:start position:0% you have more flexibility along certain certain<01:43:06.239> dimensions<01:43:06.960> um<01:43:07.760> foremost<01:43:08.159> among 01:43:08.470 --> 01:43:08.480 align:start position:0% certain dimensions um foremost among 01:43:08.480 --> 01:43:10.310 align:start position:0% certain dimensions um foremost among them<01:43:08.639> is<01:43:08.840> this 01:43:10.310 --> 01:43:10.320 align:start position:0% them is this 01:43:10.320 --> 01:43:13.669 align:start position:0% them is this lac<01:43:10.800> the<01:43:10.960> fact<01:43:11.199> that<01:43:11.360> this<01:43:12.560> function<01:43:13.280> variable 01:43:13.669 --> 01:43:13.679 align:start position:0% lac the fact that this function variable 01:43:13.679 --> 01:43:15.510 align:start position:0% lac the fact that this function variable does<01:43:13.840> not<01:43:14.000> shadow<01:43:14.320> the<01:43:14.480> list<01:43:14.719> function 01:43:15.510 --> 01:43:15.520 align:start position:0% does not shadow the list function 01:43:15.520 --> 01:43:17.750 align:start position:0% does not shadow the list function and<01:43:15.679> so<01:43:15.840> honestly<01:43:16.239> like<01:43:17.360> i'm<01:43:17.520> kind<01:43:17.679> of 01:43:17.750 --> 01:43:17.760 align:start position:0% and so honestly like i'm kind of 01:43:17.760 --> 01:43:19.030 align:start position:0% and so honestly like i'm kind of refreshed<01:43:18.400> because<01:43:18.719> like 01:43:19.030 --> 01:43:19.040 align:start position:0% refreshed because like 01:43:19.040 --> 01:43:22.070 align:start position:0% refreshed because like in<01:43:19.119> closure<01:43:19.679> you<01:43:19.760> know<01:43:19.840> you<01:43:20.000> do<01:43:20.159> things<01:43:20.400> like 01:43:22.070 --> 01:43:22.080 align:start position:0% in closure you know you do things like 01:43:22.080 --> 01:43:24.629 align:start position:0% in closure you know you do things like you<01:43:22.239> have<01:43:22.400> to<01:43:22.480> make<01:43:23.440> you<01:43:23.600> have<01:43:23.679> to<01:43:24.400> you<01:43:24.480> know 01:43:24.629 --> 01:43:24.639 align:start position:0% you have to make you have to you know 01:43:24.639 --> 01:43:25.270 align:start position:0% you have to make you have to you know you<01:43:24.719> don't<01:43:24.800> want<01:43:24.960> to 01:43:25.270 --> 01:43:25.280 align:start position:0% you don't want to 01:43:25.280 --> 01:43:26.790 align:start position:0% you don't want to shadow<01:43:25.679> close<01:43:25.920> your<01:43:26.080> list<01:43:26.239> so<01:43:26.400> you<01:43:26.560> make<01:43:26.719> a 01:43:26.790 --> 01:43:26.800 align:start position:0% shadow close your list so you make a 01:43:26.800 --> 01:43:29.990 align:start position:0% shadow close your list so you make a little<01:43:27.360> variable<01:43:27.840> version<01:43:28.239> or 01:43:29.990 --> 01:43:30.000 align:start position:0% little variable version or 01:43:30.000 --> 01:43:33.030 align:start position:0% little variable version or you<01:43:30.080> know<01:43:30.239> that's<01:43:30.480> better<01:43:30.800> the<01:43:30.880> haskell<01:43:31.280> style 01:43:33.030 --> 01:43:33.040 align:start position:0% you know that's better the haskell style 01:43:33.040 --> 01:43:37.270 align:start position:0% you know that's better the haskell style yeah<01:43:35.040> so 01:43:37.270 --> 01:43:37.280 align:start position:0% yeah so 01:43:37.280 --> 01:43:41.109 align:start position:0% yeah so yeah<01:43:38.639> yeah<01:43:39.679> uh<01:43:40.080> is<01:43:40.320> it<01:43:40.480> easy 01:43:41.109 --> 01:43:41.119 align:start position:0% yeah yeah uh is it easy 01:43:41.119 --> 01:43:44.870 align:start position:0% yeah yeah uh is it easy to<01:43:41.760> inspect<01:43:42.719> to<01:43:42.960> inspect<01:43:43.679> the<01:43:44.000> environment 01:43:44.870 --> 01:43:44.880 align:start position:0% to inspect to inspect the environment 01:43:44.880 --> 01:43:45.430 align:start position:0% to inspect to inspect the environment and<01:43:45.040> see 01:43:45.430 --> 01:43:45.440 align:start position:0% and see 01:43:45.440 --> 01:43:49.430 align:start position:0% and see all<01:43:45.600> the<01:43:45.840> symbols<01:43:46.800> as<01:43:47.280> data<01:43:47.840> yeah<01:43:48.400> so 01:43:49.430 --> 01:43:49.440 align:start position:0% all the symbols as data yeah so 01:43:49.440 --> 01:43:52.550 align:start position:0% all the symbols as data yeah so um<01:43:50.239> there<01:43:50.480> are<01:43:50.840> definitely<01:43:52.159> so 01:43:52.550 --> 01:43:52.560 align:start position:0% um there are definitely so 01:43:52.560 --> 01:43:54.790 align:start position:0% um there are definitely so in<01:43:52.719> the<01:43:52.800> same<01:43:53.040> way<01:43:53.360> that<01:43:53.920> closure<01:43:54.400> this<01:43:54.639> isn't 01:43:54.790 --> 01:43:54.800 align:start position:0% in the same way that closure this isn't 01:43:54.800 --> 01:43:58.229 align:start position:0% in the same way that closure this isn't going<01:43:54.880> to<01:43:55.040> work 01:43:58.229 --> 01:43:58.239 align:start position:0% 01:43:58.239 --> 01:44:01.189 align:start position:0% so<01:43:58.400> you<01:43:58.480> know<01:43:58.639> closure<01:43:59.119> offers<01:43:59.520> functions<01:44:00.080> for 01:44:01.189 --> 01:44:01.199 align:start position:0% so you know closure offers functions for 01:44:01.199 --> 01:44:02.310 align:start position:0% so you know closure offers functions for inspecting 01:44:02.310 --> 01:44:02.320 align:start position:0% inspecting 01:44:02.320 --> 01:44:03.669 align:start position:0% inspecting the<01:44:02.400> global<01:44:02.719> environment<01:44:03.280> looking<01:44:03.600> at 01:44:03.669 --> 01:44:03.679 align:start position:0% the global environment looking at 01:44:03.679 --> 01:44:06.310 align:start position:0% the global environment looking at packages<01:44:04.239> looking<01:44:04.480> for<01:44:04.719> things<01:44:04.960> in<01:44:05.119> packages 01:44:06.310 --> 01:44:06.320 align:start position:0% packages looking for things in packages 01:44:06.320 --> 01:44:11.030 align:start position:0% packages looking for things in packages a<01:44:06.560> common<01:44:06.800> list<01:44:07.040> is<01:44:07.119> the<01:44:07.280> same<01:44:07.440> way<01:44:07.679> there<01:44:08.000> are 01:44:11.030 --> 01:44:11.040 align:start position:0% 01:44:11.040 --> 01:44:12.310 align:start position:0% functions<01:44:11.360> for<01:44:11.520> doing<01:44:11.679> that<01:44:11.920> i'm<01:44:12.080> actually 01:44:12.310 --> 01:44:12.320 align:start position:0% functions for doing that i'm actually 01:44:12.320 --> 01:44:14.229 align:start position:0% functions for doing that i'm actually going<01:44:12.400> to 01:44:14.229 --> 01:44:14.239 align:start position:0% going to 01:44:14.239 --> 01:44:30.790 align:start position:0% going to share<01:44:14.480> my<01:44:14.639> whole<01:44:18.840> screen 01:44:30.790 --> 01:44:30.800 align:start position:0% 01:44:30.800 --> 01:44:38.790 align:start position:0% that's<01:44:31.040> not<01:44:31.199> the<01:44:31.280> one<01:44:31.520> i'm<01:44:31.600> looking<01:44:32.840> for 01:44:38.790 --> 01:44:38.800 align:start position:0% 01:44:38.800 --> 01:44:43.590 align:start position:0% so<01:44:38.960> i'm<01:44:39.119> at<01:44:39.199> the<01:44:39.280> hyperspec 01:44:43.590 --> 01:44:43.600 align:start position:0% 01:44:43.600 --> 01:44:46.629 align:start position:0% in<01:44:44.000> lisp<01:44:44.560> they<01:44:44.800> refer<01:44:45.199> to 01:44:46.629 --> 01:44:46.639 align:start position:0% in lisp they refer to 01:44:46.639 --> 01:44:48.229 align:start position:0% in lisp they refer to the<01:44:46.800> set<01:44:47.040> of<01:44:47.119> functions<01:44:47.679> and<01:44:47.840> symbols 01:44:48.229 --> 01:44:48.239 align:start position:0% the set of functions and symbols 01:44:48.239 --> 01:44:49.669 align:start position:0% the set of functions and symbols relevant<01:44:48.639> to<01:44:48.800> some<01:44:48.960> concept<01:44:49.440> as<01:44:49.520> that 01:44:49.669 --> 01:44:49.679 align:start position:0% relevant to some concept as that 01:44:49.679 --> 01:44:52.950 align:start position:0% relevant to some concept as that concept's<01:44:50.159> dictionary 01:44:52.950 --> 01:44:52.960 align:start position:0% 01:44:52.960 --> 01:44:55.030 align:start position:0% which<01:44:53.199> i<01:44:53.360> like<01:44:53.920> so<01:44:54.239> this<01:44:54.400> is<01:44:54.480> the<01:44:54.560> packages 01:44:55.030 --> 01:44:55.040 align:start position:0% which i like so this is the packages 01:44:55.040 --> 01:44:56.790 align:start position:0% which i like so this is the packages dictionary<01:44:55.600> and<01:44:55.760> you<01:44:55.840> can<01:44:56.000> see<01:44:56.239> there's<01:44:56.400> a<01:44:56.639> set 01:44:56.790 --> 01:44:56.800 align:start position:0% dictionary and you can see there's a set 01:44:56.800 --> 01:44:58.229 align:start position:0% dictionary and you can see there's a set of<01:44:56.960> symbols<01:44:57.360> and<01:44:57.520> each<01:44:57.679> symbol 01:44:58.229 --> 01:44:58.239 align:start position:0% of symbols and each symbol 01:44:58.239 --> 01:45:02.629 align:start position:0% of symbols and each symbol is<01:44:58.400> defined<01:44:58.800> either<01:44:59.040> by<01:45:00.840> its<01:45:01.920> function 01:45:02.629 --> 01:45:02.639 align:start position:0% is defined either by its function 01:45:02.639 --> 01:45:06.950 align:start position:0% is defined either by its function whether<01:45:02.960> it's<01:45:03.040> a<01:45:03.119> function<01:45:03.760> a<01:45:04.239> class<01:45:04.880> macro 01:45:06.950 --> 01:45:06.960 align:start position:0% whether it's a function a class macro 01:45:06.960 --> 01:45:13.030 align:start position:0% whether it's a function a class macro variable<01:45:09.360> so<01:45:09.520> we<01:45:09.679> can<01:45:09.840> look<01:45:10.080> at 01:45:13.030 --> 01:45:13.040 align:start position:0% 01:45:13.040 --> 01:45:16.790 align:start position:0% let's<01:45:13.199> look<01:45:13.360> at<01:45:13.520> find<01:45:14.840> symbol<01:45:16.000> yeah<01:45:16.239> so<01:45:16.480> find 01:45:16.790 --> 01:45:16.800 align:start position:0% let's look at find symbol yeah so find 01:45:16.800 --> 01:45:19.430 align:start position:0% let's look at find symbol yeah so find symbol<01:45:17.280> takes<01:45:17.520> a<01:45:17.679> string 01:45:19.430 --> 01:45:19.440 align:start position:0% symbol takes a string 01:45:19.440 --> 01:45:21.109 align:start position:0% symbol takes a string a<01:45:19.600> package<01:45:20.080> designator<01:45:20.719> so<01:45:20.880> this<01:45:21.040> is 01:45:21.109 --> 01:45:21.119 align:start position:0% a package designator so this is 01:45:21.119 --> 01:45:23.270 align:start position:0% a package designator so this is something<01:45:21.360> that<01:45:21.520> represents<01:45:21.920> a<01:45:22.000> package 01:45:23.270 --> 01:45:23.280 align:start position:0% something that represents a package 01:45:23.280 --> 01:45:24.870 align:start position:0% something that represents a package now<01:45:23.440> let's<01:45:23.679> let's<01:45:23.920> try<01:45:24.080> this<01:45:24.239> so<01:45:24.400> let's<01:45:24.639> let's 01:45:24.870 --> 01:45:24.880 align:start position:0% now let's let's try this so let's let's 01:45:24.880 --> 01:45:32.070 align:start position:0% now let's let's try this so let's let's do<01:45:28.840> um 01:45:32.070 --> 01:45:32.080 align:start position:0% 01:45:32.080 --> 01:45:35.510 align:start position:0% see<01:45:32.239> what<01:45:32.400> it<01:45:32.480> says<01:45:32.719> about<01:45:32.960> this<01:45:34.880> okay 01:45:35.510 --> 01:45:35.520 align:start position:0% see what it says about this okay 01:45:35.520 --> 01:45:37.350 align:start position:0% see what it says about this okay so<01:45:35.920> interesting<01:45:36.320> thing<01:45:36.560> popped<01:45:36.880> up<01:45:37.040> notice 01:45:37.350 --> 01:45:37.360 align:start position:0% so interesting thing popped up notice 01:45:37.360 --> 01:45:39.990 align:start position:0% so interesting thing popped up notice how<01:45:37.600> two<01:45:37.840> lines<01:45:38.159> of<01:45:38.239> output<01:45:38.560> printed 01:45:39.990 --> 01:45:40.000 align:start position:0% how two lines of output printed 01:45:40.000 --> 01:45:41.430 align:start position:0% how two lines of output printed this<01:45:40.239> means<01:45:40.480> that<01:45:40.639> this<01:45:40.800> function<01:45:41.119> returned 01:45:41.430 --> 01:45:41.440 align:start position:0% this means that this function returned 01:45:41.440 --> 01:45:43.510 align:start position:0% this means that this function returned two<01:45:41.679> values 01:45:43.510 --> 01:45:43.520 align:start position:0% two values 01:45:43.520 --> 01:45:45.669 align:start position:0% two values which<01:45:43.840> is<01:45:44.000> you<01:45:44.159> know<01:45:45.040> mathematically 01:45:45.669 --> 01:45:45.679 align:start position:0% which is you know mathematically 01:45:45.679 --> 01:45:48.550 align:start position:0% which is you know mathematically bankrupt<01:45:46.400> because<01:45:46.560> what<01:45:46.719> does<01:45:46.800> that<01:45:46.960> mean 01:45:48.550 --> 01:45:48.560 align:start position:0% bankrupt because what does that mean 01:45:48.560 --> 01:45:54.070 align:start position:0% bankrupt because what does that mean but<01:45:48.960> what<01:45:49.119> it<01:45:49.280> is<01:45:49.520> is<01:45:49.840> it's<01:45:50.080> an<01:45:50.239> efficiency 01:45:54.070 --> 01:45:54.080 align:start position:0% 01:45:54.080 --> 01:45:55.510 align:start position:0% normally<01:45:54.560> in<01:45:54.719> a<01:45:54.800> programming<01:45:55.199> language 01:45:55.510 --> 01:45:55.520 align:start position:0% normally in a programming language 01:45:55.520 --> 01:45:57.189 align:start position:0% normally in a programming language there's<01:45:55.920> conceptually<01:45:56.480> a<01:45:56.560> register<01:45:56.960> that<01:45:57.119> a 01:45:57.189 --> 01:45:57.199 align:start position:0% there's conceptually a register that a 01:45:57.199 --> 01:45:58.470 align:start position:0% there's conceptually a register that a return<01:45:57.440> value<01:45:57.760> is<01:45:57.840> put<01:45:58.000> into 01:45:58.470 --> 01:45:58.480 align:start position:0% return value is put into 01:45:58.480 --> 01:45:59.910 align:start position:0% return value is put into and<01:45:58.639> a<01:45:58.800> normal<01:45:59.119> programming<01:45:59.520> language 01:45:59.910 --> 01:45:59.920 align:start position:0% and a normal programming language 01:45:59.920 --> 01:46:02.149 align:start position:0% and a normal programming language maintains<01:46:00.400> one<01:46:00.560> such<01:46:00.880> register 01:46:02.149 --> 01:46:02.159 align:start position:0% maintains one such register 01:46:02.159 --> 01:46:05.590 align:start position:0% maintains one such register but<01:46:02.880> common<01:46:03.199> lisp<01:46:03.600> exposes<01:46:04.320> some<01:46:05.119> performance 01:46:05.590 --> 01:46:05.600 align:start position:0% but common lisp exposes some performance 01:46:05.600 --> 01:46:07.430 align:start position:0% but common lisp exposes some performance related<01:46:06.000> features<01:46:06.400> and<01:46:06.480> one<01:46:06.639> of<01:46:06.719> them<01:46:06.960> is<01:46:07.119> this 01:46:07.430 --> 01:46:07.440 align:start position:0% related features and one of them is this 01:46:07.440 --> 01:46:09.430 align:start position:0% related features and one of them is this idea<01:46:07.840> that<01:46:08.000> a<01:46:08.080> function<01:46:08.480> can<01:46:08.639> return<01:46:09.040> multiple 01:46:09.430 --> 01:46:09.440 align:start position:0% idea that a function can return multiple 01:46:09.440 --> 01:46:10.709 align:start position:0% idea that a function can return multiple values 01:46:10.709 --> 01:46:10.719 align:start position:0% values 01:46:10.719 --> 01:46:13.430 align:start position:0% values and<01:46:10.880> it's<01:46:11.199> based<01:46:11.520> on<01:46:11.600> the<01:46:11.840> observation<01:46:12.480> that 01:46:13.430 --> 01:46:13.440 align:start position:0% and it's based on the observation that 01:46:13.440 --> 01:46:14.470 align:start position:0% and it's based on the observation that um 01:46:14.470 --> 01:46:14.480 align:start position:0% um 01:46:14.480 --> 01:46:16.870 align:start position:0% um a<01:46:14.639> function<01:46:15.119> can<01:46:15.360> box<01:46:15.760> up<01:46:16.159> multiple<01:46:16.560> values 01:46:16.870 --> 01:46:16.880 align:start position:0% a function can box up multiple values 01:46:16.880 --> 01:46:17.750 align:start position:0% a function can box up multiple values into<01:46:17.119> a<01:46:17.199> list 01:46:17.750 --> 01:46:17.760 align:start position:0% into a list 01:46:17.760 --> 01:46:19.990 align:start position:0% into a list for<01:46:17.920> example<01:46:18.400> or<01:46:18.560> vector<01:46:18.880> enclosures<01:46:19.440> case 01:46:19.990 --> 01:46:20.000 align:start position:0% for example or vector enclosures case 01:46:20.000 --> 01:46:21.350 align:start position:0% for example or vector enclosures case but<01:46:20.159> that<01:46:20.320> means<01:46:20.560> that<01:46:20.639> you<01:46:20.719> need<01:46:20.880> to<01:46:20.960> allocate 01:46:21.350 --> 01:46:21.360 align:start position:0% but that means that you need to allocate 01:46:21.360 --> 01:46:22.950 align:start position:0% but that means that you need to allocate a<01:46:21.520> fresh<01:46:21.760> vector<01:46:22.159> that's<01:46:22.480> immediately<01:46:22.880> going 01:46:22.950 --> 01:46:22.960 align:start position:0% a fresh vector that's immediately going 01:46:22.960 --> 01:46:24.629 align:start position:0% a fresh vector that's immediately going to<01:46:23.040> be<01:46:23.199> thrown<01:46:23.440> away<01:46:23.760> by<01:46:23.920> the<01:46:24.000> consumer<01:46:24.560> it's 01:46:24.629 --> 01:46:24.639 align:start position:0% to be thrown away by the consumer it's 01:46:24.639 --> 01:46:27.430 align:start position:0% to be thrown away by the consumer it's going<01:46:24.719> to<01:46:24.800> be<01:46:24.960> destructured<01:46:25.600> and<01:46:25.679> then 01:46:27.430 --> 01:46:27.440 align:start position:0% going to be destructured and then 01:46:27.440 --> 01:46:30.470 align:start position:0% going to be destructured and then gc'd 01:46:30.470 --> 01:46:30.480 align:start position:0% 01:46:30.480 --> 01:46:32.550 align:start position:0% so<01:46:31.440> if<01:46:31.600> you<01:46:31.760> just<01:46:32.000> have<01:46:32.239> if<01:46:32.320> you<01:46:32.400> have<01:46:32.480> a 01:46:32.550 --> 01:46:32.560 align:start position:0% so if you just have if you have a 01:46:32.560 --> 01:46:34.390 align:start position:0% so if you just have if you have a concept<01:46:32.960> of<01:46:33.040> multiple<01:46:33.440> values<01:46:34.000> then<01:46:34.159> you<01:46:34.239> can 01:46:34.390 --> 01:46:34.400 align:start position:0% concept of multiple values then you can 01:46:34.400 --> 01:46:36.070 align:start position:0% concept of multiple values then you can maintain<01:46:34.800> a<01:46:34.880> set<01:46:35.119> of<01:46:35.199> registers<01:46:35.679> say<01:46:35.840> like<01:46:36.000> a 01:46:36.070 --> 01:46:36.080 align:start position:0% maintain a set of registers say like a 01:46:36.080 --> 01:46:37.109 align:start position:0% maintain a set of registers say like a hundred 01:46:37.109 --> 01:46:37.119 align:start position:0% hundred 01:46:37.119 --> 01:46:38.870 align:start position:0% hundred and<01:46:37.360> instead<01:46:37.600> of<01:46:37.760> allocating<01:46:38.239> a<01:46:38.320> new<01:46:38.560> vector 01:46:38.870 --> 01:46:38.880 align:start position:0% and instead of allocating a new vector 01:46:38.880 --> 01:46:40.310 align:start position:0% and instead of allocating a new vector when<01:46:39.040> somebody<01:46:39.360> wants<01:46:39.520> to<01:46:39.600> return<01:46:40.000> multiple 01:46:40.310 --> 01:46:40.320 align:start position:0% when somebody wants to return multiple 01:46:40.320 --> 01:46:41.350 align:start position:0% when somebody wants to return multiple things 01:46:41.350 --> 01:46:41.360 align:start position:0% things 01:46:41.360 --> 01:46:43.189 align:start position:0% things you<01:46:41.520> just<01:46:41.679> return<01:46:42.080> a<01:46:42.239> special<01:46:42.560> value<01:46:42.960> that 01:46:43.189 --> 01:46:43.199 align:start position:0% you just return a special value that 01:46:43.199 --> 01:46:45.270 align:start position:0% you just return a special value that indicates<01:46:44.320> there<01:46:44.480> are<01:46:44.560> multiple<01:46:44.960> values 01:46:45.270 --> 01:46:45.280 align:start position:0% indicates there are multiple values 01:46:45.280 --> 01:46:46.709 align:start position:0% indicates there are multiple values involved<01:46:45.679> and<01:46:45.760> then<01:46:45.840> you<01:46:45.920> could<01:46:46.080> pass<01:46:46.400> like<01:46:46.560> an 01:46:46.709 --> 01:46:46.719 align:start position:0% involved and then you could pass like an 01:46:46.719 --> 01:46:49.189 align:start position:0% involved and then you could pass like an offset<01:46:47.199> into<01:46:47.440> the<01:46:47.600> registers<01:46:48.159> or<01:46:48.239> something 01:46:49.189 --> 01:46:49.199 align:start position:0% offset into the registers or something 01:46:49.199 --> 01:46:50.550 align:start position:0% offset into the registers or something but<01:46:49.520> at<01:46:49.600> the<01:46:49.760> end<01:46:49.920> of<01:46:50.000> the<01:46:50.080> day<01:46:50.239> there's<01:46:50.400> no 01:46:50.550 --> 01:46:50.560 align:start position:0% but at the end of the day there's no 01:46:50.560 --> 01:46:52.629 align:start position:0% but at the end of the day there's no allocation<01:46:51.280> happening<01:46:51.679> necessarily 01:46:52.629 --> 01:46:52.639 align:start position:0% allocation happening necessarily 01:46:52.639 --> 01:46:57.189 align:start position:0% allocation happening necessarily so<01:46:52.880> no<01:46:53.040> pressure<01:46:53.360> on<01:46:53.440> the<01:46:53.520> gc<01:46:54.639> no<01:46:54.800> allocation 01:46:57.189 --> 01:46:57.199 align:start position:0% so no pressure on the gc no allocation 01:46:57.199 --> 01:47:00.149 align:start position:0% so no pressure on the gc no allocation and<01:46:57.440> the<01:46:58.000> caller<01:46:58.639> has<01:46:58.960> very<01:46:59.199> fast<01:46:59.600> access<01:47:00.000> to 01:47:00.149 --> 01:47:00.159 align:start position:0% and the caller has very fast access to 01:47:00.159 --> 01:47:03.590 align:start position:0% and the caller has very fast access to the<01:47:00.239> values<01:47:00.639> returned 01:47:03.590 --> 01:47:03.600 align:start position:0% 01:47:03.600 --> 01:47:05.910 align:start position:0% this<01:47:03.840> is<01:47:04.320> somewhat<01:47:04.719> famously<01:47:05.199> not<01:47:05.360> in<01:47:05.520> closure 01:47:05.910 --> 01:47:05.920 align:start position:0% this is somewhat famously not in closure 01:47:05.920 --> 01:47:07.430 align:start position:0% this is somewhat famously not in closure closure<01:47:06.159> doesn't<01:47:06.320> have<01:47:06.480> multiple<01:47:06.800> values 01:47:07.430 --> 01:47:07.440 align:start position:0% closure doesn't have multiple values 01:47:07.440 --> 01:47:09.350 align:start position:0% closure doesn't have multiple values probably<01:47:07.679> the<01:47:07.840> biggest<01:47:08.159> reason<01:47:08.639> is<01:47:08.800> because 01:47:09.350 --> 01:47:09.360 align:start position:0% probably the biggest reason is because 01:47:09.360 --> 01:47:10.950 align:start position:0% probably the biggest reason is because java<01:47:09.679> doesn't<01:47:09.840> have<01:47:10.000> multiple<01:47:10.320> values<01:47:10.800> and 01:47:10.950 --> 01:47:10.960 align:start position:0% java doesn't have multiple values and 01:47:10.960 --> 01:47:12.629 align:start position:0% java doesn't have multiple values and you<01:47:11.040> can<01:47:11.199> imagine<01:47:11.679> how<01:47:11.920> crazy<01:47:12.159> that<01:47:12.320> would<01:47:12.480> be 01:47:12.629 --> 01:47:12.639 align:start position:0% you can imagine how crazy that would be 01:47:12.639 --> 01:47:13.109 align:start position:0% you can imagine how crazy that would be to 01:47:13.109 --> 01:47:13.119 align:start position:0% to 01:47:13.119 --> 01:47:16.310 align:start position:0% to try<01:47:13.360> and<01:47:13.520> do<01:47:15.679> but 01:47:16.310 --> 01:47:16.320 align:start position:0% try and do but 01:47:16.320 --> 01:47:18.950 align:start position:0% try and do but closure<01:47:16.719> actually<01:47:16.960> defended<01:47:17.360> his<01:47:17.520> decision 01:47:18.950 --> 01:47:18.960 align:start position:0% closure actually defended his decision 01:47:18.960 --> 01:47:19.350 align:start position:0% closure actually defended his decision but 01:47:19.350 --> 01:47:19.360 align:start position:0% but 01:47:19.360 --> 01:47:20.950 align:start position:0% but richie<01:47:19.840> defended<01:47:20.239> his<01:47:20.400> decision<01:47:20.719> in<01:47:20.880> a 01:47:20.950 --> 01:47:20.960 align:start position:0% richie defended his decision in a 01:47:20.960 --> 01:47:22.629 align:start position:0% richie defended his decision in a separate<01:47:21.600> way 01:47:22.629 --> 01:47:22.639 align:start position:0% separate way 01:47:22.639 --> 01:47:24.070 align:start position:0% separate way he<01:47:22.880> a<01:47:22.960> couple<01:47:23.199> years<01:47:23.360> ago<01:47:23.520> maybe<01:47:23.760> like<01:47:23.920> 10 01:47:24.070 --> 01:47:24.080 align:start position:0% he a couple years ago maybe like 10 01:47:24.080 --> 01:47:25.669 align:start position:0% he a couple years ago maybe like 10 years<01:47:24.320> ago<01:47:24.480> he<01:47:24.639> had<01:47:24.719> a<01:47:24.800> discussion 01:47:25.669 --> 01:47:25.679 align:start position:0% years ago he had a discussion 01:47:25.679 --> 01:47:29.030 align:start position:0% years ago he had a discussion that<01:47:27.040> there<01:47:27.280> is<01:47:27.440> a 01:47:29.030 --> 01:47:29.040 align:start position:0% that there is a 01:47:29.040 --> 01:47:31.590 align:start position:0% that there is a there<01:47:29.280> is<01:47:29.520> a<01:47:29.760> um<01:47:30.480> this<01:47:30.719> is<01:47:30.880> written<01:47:31.119> down<01:47:31.360> but 01:47:31.590 --> 01:47:31.600 align:start position:0% there is a um this is written down but 01:47:31.600 --> 01:47:33.030 align:start position:0% there is a um this is written down but he<01:47:31.840> had<01:47:32.080> a<01:47:32.159> discussion<01:47:32.480> with<01:47:32.639> cliff 01:47:33.030 --> 01:47:33.040 align:start position:0% he had a discussion with cliff 01:47:33.040 --> 01:47:36.070 align:start position:0% he had a discussion with cliff click<01:47:34.320> uh<01:47:34.560> who's<01:47:34.880> a 01:47:36.070 --> 01:47:36.080 align:start position:0% click uh who's a 01:47:36.080 --> 01:47:37.590 align:start position:0% click uh who's a more<01:47:36.239> or<01:47:36.400> less<01:47:36.560> the<01:47:36.719> implementer<01:47:37.199> of<01:47:37.280> java's 01:47:37.590 --> 01:47:37.600 align:start position:0% more or less the implementer of java's 01:47:37.600 --> 01:47:40.229 align:start position:0% more or less the implementer of java's hot<01:47:37.840> spot<01:47:39.040> and 01:47:40.229 --> 01:47:40.239 align:start position:0% hot spot and 01:47:40.239 --> 01:47:42.470 align:start position:0% hot spot and daniel<01:47:40.639> weinreb<01:47:41.360> who<01:47:41.600> is<01:47:42.080> one<01:47:42.239> of<01:47:42.320> the 01:47:42.470 --> 01:47:42.480 align:start position:0% daniel weinreb who is one of the 01:47:42.480 --> 01:47:45.109 align:start position:0% daniel weinreb who is one of the symbolics<01:47:43.040> founders 01:47:45.109 --> 01:47:45.119 align:start position:0% symbolics founders 01:47:45.119 --> 01:47:48.550 align:start position:0% symbolics founders and<01:47:46.080> i<01:47:46.239> think<01:47:46.880> wine<01:47:47.199> rebb<01:47:47.600> mentioned<01:47:48.000> to<01:47:48.159> rich 01:47:48.550 --> 01:47:48.560 align:start position:0% and i think wine rebb mentioned to rich 01:47:48.560 --> 01:47:49.030 align:start position:0% and i think wine rebb mentioned to rich this 01:47:49.030 --> 01:47:49.040 align:start position:0% this 01:47:49.040 --> 01:47:51.189 align:start position:0% this lack<01:47:49.280> of<01:47:49.360> multiple<01:47:49.760> values<01:47:50.480> and<01:47:50.880> rich 01:47:51.189 --> 01:47:51.199 align:start position:0% lack of multiple values and rich 01:47:51.199 --> 01:47:52.149 align:start position:0% lack of multiple values and rich suggested<01:47:51.760> that 01:47:52.149 --> 01:47:52.159 align:start position:0% suggested that 01:47:52.159 --> 01:47:54.790 align:start position:0% suggested that multiple<01:47:52.480> values<01:47:53.920> were<01:47:54.159> not<01:47:54.320> even<01:47:54.560> really 01:47:54.790 --> 01:47:54.800 align:start position:0% multiple values were not even really 01:47:54.800 --> 01:47:55.830 align:start position:0% multiple values were not even really desirable<01:47:55.280> for 01:47:55.830 --> 01:47:55.840 align:start position:0% desirable for 01:47:55.840 --> 01:47:57.510 align:start position:0% desirable for performance<01:47:56.239> reasons<01:47:56.639> because<01:47:56.880> of<01:47:57.040> advances 01:47:57.510 --> 01:47:57.520 align:start position:0% performance reasons because of advances 01:47:57.520 --> 01:47:59.990 align:start position:0% performance reasons because of advances in<01:47:57.600> garbage<01:47:57.920> collection<01:47:58.719> since 01:47:59.990 --> 01:48:00.000 align:start position:0% in garbage collection since 01:48:00.000 --> 01:48:02.149 align:start position:0% in garbage collection since um<01:48:00.960> common<01:48:01.199> list<01:48:01.360> was<01:48:01.520> standardized<01:48:02.080> in 01:48:02.149 --> 01:48:02.159 align:start position:0% um common list was standardized in 01:48:02.159 --> 01:48:04.390 align:start position:0% um common list was standardized in particular<01:48:02.560> ephemeral<01:48:03.040> garbage<01:48:03.440> collection 01:48:04.390 --> 01:48:04.400 align:start position:0% particular ephemeral garbage collection 01:48:04.400 --> 01:48:06.310 align:start position:0% particular ephemeral garbage collection so<01:48:04.560> the<01:48:04.719> cost<01:48:05.119> of<01:48:05.280> allocating<01:48:05.920> something<01:48:06.239> on 01:48:06.310 --> 01:48:06.320 align:start position:0% so the cost of allocating something on 01:48:06.320 --> 01:48:08.390 align:start position:0% so the cost of allocating something on the<01:48:06.400> stack<01:48:06.800> from<01:48:06.960> the<01:48:07.040> garbage<01:48:07.360> collector 01:48:08.390 --> 01:48:08.400 align:start position:0% the stack from the garbage collector 01:48:08.400 --> 01:48:11.510 align:start position:0% the stack from the garbage collector is<01:48:08.560> very<01:48:08.800> very<01:48:09.040> low<01:48:09.280> nowadays<01:48:10.080> um 01:48:11.510 --> 01:48:11.520 align:start position:0% is very very low nowadays um 01:48:11.520 --> 01:48:14.470 align:start position:0% is very very low nowadays um on<01:48:11.760> java<01:48:12.400> on<01:48:12.719> on<01:48:13.040> any<01:48:13.280> system<01:48:13.760> that<01:48:14.080> has 01:48:14.470 --> 01:48:14.480 align:start position:0% on java on on any system that has 01:48:14.480 --> 01:48:17.189 align:start position:0% on java on on any system that has different 01:48:17.189 --> 01:48:17.199 align:start position:0% 01:48:17.199 --> 01:48:19.350 align:start position:0% uh<01:48:17.520> that<01:48:17.760> partitions<01:48:18.320> new<01:48:18.560> objects<01:48:18.960> based<01:48:19.280> on 01:48:19.350 --> 01:48:19.360 align:start position:0% uh that partitions new objects based on 01:48:19.360 --> 01:48:21.189 align:start position:0% uh that partitions new objects based on how<01:48:19.520> long<01:48:19.760> they've<01:48:19.920> been<01:48:20.080> around 01:48:21.189 --> 01:48:21.199 align:start position:0% how long they've been around 01:48:21.199 --> 01:48:23.030 align:start position:0% how long they've been around and<01:48:21.360> so<01:48:21.520> i<01:48:21.920> objects<01:48:22.320> that<01:48:22.560> haven't<01:48:22.880> been 01:48:23.030 --> 01:48:23.040 align:start position:0% and so i objects that haven't been 01:48:23.040 --> 01:48:24.629 align:start position:0% and so i objects that haven't been around<01:48:23.280> for<01:48:23.440> very<01:48:23.679> long<01:48:23.920> are<01:48:24.000> the<01:48:24.159> first<01:48:24.480> to 01:48:24.629 --> 01:48:24.639 align:start position:0% around for very long are the first to 01:48:24.639 --> 01:48:26.310 align:start position:0% around for very long are the first to get<01:48:24.800> collected 01:48:26.310 --> 01:48:26.320 align:start position:0% get collected 01:48:26.320 --> 01:48:29.430 align:start position:0% get collected usually<01:48:27.040> and<01:48:27.199> so<01:48:27.360> what<01:48:27.520> that<01:48:27.760> means<01:48:28.080> is<01:48:28.239> that 01:48:29.430 --> 01:48:29.440 align:start position:0% usually and so what that means is that 01:48:29.440 --> 01:48:31.669 align:start position:0% usually and so what that means is that the<01:48:29.600> cost<01:48:29.920> of<01:48:30.080> allocating<01:48:30.560> things<01:48:31.199> is<01:48:31.440> much 01:48:31.669 --> 01:48:31.679 align:start position:0% the cost of allocating things is much 01:48:31.679 --> 01:48:36.070 align:start position:0% the cost of allocating things is much lower 01:48:36.070 --> 01:48:36.080 align:start position:0% 01:48:36.080 --> 01:48:37.430 align:start position:0% in<01:48:36.239> practice<01:48:36.719> at<01:48:36.800> least<01:48:36.960> that<01:48:37.040> was<01:48:37.119> rich's 01:48:37.430 --> 01:48:37.440 align:start position:0% in practice at least that was rich's 01:48:37.440 --> 01:48:39.109 align:start position:0% in practice at least that was rich's argument 01:48:39.109 --> 01:48:39.119 align:start position:0% argument 01:48:39.119 --> 01:48:41.189 align:start position:0% argument but<01:48:39.360> anyway<01:48:39.840> in<01:48:40.000> case<01:48:40.239> rich<01:48:40.480> is<01:48:40.560> wrong<01:48:40.880> we<01:48:41.040> have 01:48:41.189 --> 01:48:41.199 align:start position:0% but anyway in case rich is wrong we have 01:48:41.199 --> 01:48:42.470 align:start position:0% but anyway in case rich is wrong we have multiple<01:48:41.520> values<01:48:42.080> in 01:48:42.470 --> 01:48:42.480 align:start position:0% multiple values in 01:48:42.480 --> 01:48:44.070 align:start position:0% multiple values in common<01:48:42.800> lisp<01:48:43.440> and<01:48:43.600> which<01:48:43.760> is<01:48:43.840> what<01:48:44.000> we're 01:48:44.070 --> 01:48:44.080 align:start position:0% common lisp and which is what we're 01:48:44.080 --> 01:48:45.669 align:start position:0% common lisp and which is what we're seeing<01:48:44.239> here<01:48:44.400> so<01:48:44.639> find<01:48:44.880> symbols<01:48:45.199> returning 01:48:45.669 --> 01:48:45.679 align:start position:0% seeing here so find symbols returning 01:48:45.679 --> 01:48:47.189 align:start position:0% seeing here so find symbols returning two<01:48:45.840> values 01:48:47.189 --> 01:48:47.199 align:start position:0% two values 01:48:47.199 --> 01:48:49.350 align:start position:0% two values symbol<01:48:47.600> plus<01:48:48.000> and<01:48:48.080> then<01:48:48.400> inherited<01:48:48.960> which<01:48:49.280> is 01:48:49.350 --> 01:48:49.360 align:start position:0% symbol plus and then inherited which is 01:48:49.360 --> 01:48:51.830 align:start position:0% symbol plus and then inherited which is a<01:48:49.520> keyword<01:48:49.840> that<01:48:50.000> means 01:48:51.830 --> 01:48:51.840 align:start position:0% a keyword that means 01:48:51.840 --> 01:48:54.149 align:start position:0% a keyword that means it's<01:48:52.080> present<01:48:52.480> in<01:48:52.560> the<01:48:52.639> package<01:48:53.040> as<01:48:53.119> an<01:48:53.360> in<01:48:53.840> oh 01:48:54.149 --> 01:48:54.159 align:start position:0% it's present in the package as an in oh 01:48:54.159 --> 01:48:55.430 align:start position:0% it's present in the package as an in oh uh 01:48:55.430 --> 01:48:55.440 align:start position:0% uh 01:48:55.440 --> 01:48:57.990 align:start position:0% uh ah<01:48:55.679> yes<01:48:56.159> it's<01:48:56.320> inherited<01:48:57.520> through<01:48:57.760> use 01:48:57.990 --> 01:48:58.000 align:start position:0% ah yes it's inherited through use 01:48:58.000 --> 01:49:00.310 align:start position:0% ah yes it's inherited through use package<01:48:58.320> so<01:48:58.480> what<01:48:58.560> this<01:48:58.800> means<01:48:59.119> is<01:48:59.199> that<01:48:59.440> like 01:49:00.310 --> 01:49:00.320 align:start position:0% package so what this means is that like 01:49:00.320 --> 01:49:03.030 align:start position:0% package so what this means is that like we're<01:49:00.560> in<01:49:00.800> a<01:49:00.880> package<01:49:01.440> cl<01:49:01.920> user<01:49:02.560> which<01:49:02.800> is 01:49:03.030 --> 01:49:03.040 align:start position:0% we're in a package cl user which is 01:49:03.040 --> 01:49:04.470 align:start position:0% we're in a package cl user which is analogous<01:49:03.600> to<01:49:03.679> closures<01:49:04.080> user 01:49:04.470 --> 01:49:04.480 align:start position:0% analogous to closures user 01:49:04.480 --> 01:49:07.669 align:start position:0% analogous to closures user user<01:49:04.719> package<01:49:05.760> and<01:49:06.080> plus<01:49:06.480> is<01:49:06.719> a<01:49:06.800> symbol<01:49:07.199> from 01:49:07.669 --> 01:49:07.679 align:start position:0% user package and plus is a symbol from 01:49:07.679 --> 01:49:10.629 align:start position:0% user package and plus is a symbol from a<01:49:07.760> different<01:49:08.080> package<01:49:09.280> but<01:49:09.920> when<01:49:10.080> we<01:49:10.239> type<01:49:10.480> it 01:49:10.629 --> 01:49:10.639 align:start position:0% a different package but when we type it 01:49:10.639 --> 01:49:10.870 align:start position:0% a different package but when we type it in 01:49:10.870 --> 01:49:10.880 align:start position:0% in 01:49:10.880 --> 01:49:12.830 align:start position:0% in without<01:49:11.199> a<01:49:11.280> namespace<01:49:12.080> or<01:49:12.239> a<01:49:12.320> package 01:49:12.830 --> 01:49:12.840 align:start position:0% without a namespace or a package 01:49:12.840 --> 01:49:14.070 align:start position:0% without a namespace or a package qualification 01:49:14.070 --> 01:49:14.080 align:start position:0% qualification 01:49:14.080 --> 01:49:15.669 align:start position:0% qualification uh<01:49:14.320> in<01:49:14.480> this<01:49:14.639> current<01:49:14.960> package<01:49:15.280> it's<01:49:15.440> going<01:49:15.599> to 01:49:15.669 --> 01:49:15.679 align:start position:0% uh in this current package it's going to 01:49:15.679 --> 01:49:17.830 align:start position:0% uh in this current package it's going to be<01:49:15.840> interpreted<01:49:16.560> to<01:49:16.719> mean<01:49:16.960> something<01:49:17.360> else 01:49:17.830 --> 01:49:17.840 align:start position:0% be interpreted to mean something else 01:49:17.840 --> 01:49:21.270 align:start position:0% be interpreted to mean something else so<01:49:17.920> it's<01:49:18.080> very<01:49:18.320> similar<01:49:18.719> to<01:49:18.880> closures<01:49:19.920> refer 01:49:21.270 --> 01:49:21.280 align:start position:0% so it's very similar to closures refer 01:49:21.280 --> 01:49:22.310 align:start position:0% so it's very similar to closures refer you<01:49:21.360> know<01:49:21.520> it's<01:49:21.599> the<01:49:21.679> same<01:49:21.840> way<01:49:22.000> that<01:49:22.159> you<01:49:22.239> can 01:49:22.310 --> 01:49:22.320 align:start position:0% you know it's the same way that you can 01:49:22.320 --> 01:49:23.910 align:start position:0% you know it's the same way that you can type<01:49:22.560> plus<01:49:22.800> in<01:49:22.880> the<01:49:22.960> username<01:49:23.360> space<01:49:23.599> and<01:49:23.760> it 01:49:23.910 --> 01:49:23.920 align:start position:0% type plus in the username space and it 01:49:23.920 --> 01:49:28.390 align:start position:0% type plus in the username space and it becomes<01:49:26.840> closures 01:49:28.390 --> 01:49:28.400 align:start position:0% becomes closures 01:49:28.400 --> 01:49:32.709 align:start position:0% becomes closures we<01:49:28.560> can<01:49:28.719> do<01:49:28.880> this<01:49:30.400> so 01:49:32.709 --> 01:49:32.719 align:start position:0% 01:49:32.719 --> 01:49:34.629 align:start position:0% we<01:49:32.880> can<01:49:33.119> look<01:49:33.280> up<01:49:33.520> the<01:49:33.679> package<01:49:34.159> where<01:49:34.400> the 01:49:34.629 --> 01:49:34.639 align:start position:0% we can look up the package where the 01:49:34.639 --> 01:49:37.270 align:start position:0% we can look up the package where the symbol<01:49:35.599> is<01:49:35.760> installed<01:49:36.320> or<01:49:36.480> interned<01:49:37.040> and<01:49:37.199> it 01:49:37.270 --> 01:49:37.280 align:start position:0% symbol is installed or interned and it 01:49:37.280 --> 01:49:39.189 align:start position:0% symbol is installed or interned and it says<01:49:37.520> the<01:49:37.679> common<01:49:38.000> list<01:49:38.239> package<01:49:38.639> which<01:49:38.880> is 01:49:39.189 --> 01:49:39.199 align:start position:0% says the common list package which is 01:49:39.199 --> 01:49:47.669 align:start position:0% says the common list package which is different<01:49:39.440> from<01:49:39.599> the<01:49:39.679> one<01:49:39.840> we're<01:49:40.840> in 01:49:47.669 --> 01:49:47.679 align:start position:0% 01:49:47.679 --> 01:49:51.830 align:start position:0% um<01:49:49.440> i<01:49:49.599> don't<01:49:49.840> have 01:49:51.830 --> 01:49:51.840 align:start position:0% um i don't have 01:49:51.840 --> 01:49:55.109 align:start position:0% um i don't have a<01:49:52.159> whole<01:49:52.560> lot<01:49:52.800> of<01:49:52.960> time<01:49:53.360> left<01:49:54.480> well<01:49:54.639> no<01:49:54.800> i<01:49:54.880> do 01:49:55.109 --> 01:49:55.119 align:start position:0% a whole lot of time left well no i do 01:49:55.119 --> 01:49:57.830 align:start position:0% a whole lot of time left well no i do let's<01:49:55.360> see<01:49:55.520> we've<01:49:55.679> been 01:49:57.830 --> 01:49:57.840 align:start position:0% let's see we've been 01:49:57.840 --> 01:50:01.350 align:start position:0% let's see we've been oh<01:49:58.000> yeah<01:49:58.239> i<01:49:58.320> have<01:49:58.480> to<01:49:58.560> go<01:49:58.719> soon<01:49:59.599> but<01:49:59.920> um 01:50:01.350 --> 01:50:01.360 align:start position:0% oh yeah i have to go soon but um 01:50:01.360 --> 01:50:02.550 align:start position:0% oh yeah i have to go soon but um there<01:50:01.520> were<01:50:01.679> a<01:50:01.679> few<01:50:01.840> things<01:50:02.000> i<01:50:02.080> wanted<01:50:02.320> to<01:50:02.400> show 01:50:02.550 --> 01:50:02.560 align:start position:0% there were a few things i wanted to show 01:50:02.560 --> 01:50:04.629 align:start position:0% there were a few things i wanted to show one<01:50:02.719> of<01:50:02.880> one<01:50:03.040> of<01:50:03.119> them<01:50:03.199> was<01:50:03.520> close 01:50:04.629 --> 01:50:04.639 align:start position:0% one of one of them was close 01:50:04.639 --> 01:50:06.550 align:start position:0% one of one of them was close common<01:50:04.880> lesson<01:50:05.440> system<01:50:06.080> it's<01:50:06.239> not<01:50:06.320> going<01:50:06.480> to 01:50:06.550 --> 01:50:06.560 align:start position:0% common lesson system it's not going to 01:50:06.560 --> 01:50:08.310 align:start position:0% common lesson system it's not going to happen<01:50:07.599> um 01:50:08.310 --> 01:50:08.320 align:start position:0% happen um 01:50:08.320 --> 01:50:09.510 align:start position:0% happen um but<01:50:08.480> i<01:50:08.560> will<01:50:08.719> show<01:50:08.880> you<01:50:08.960> this<01:50:09.119> which<01:50:09.360> is<01:50:09.440> the 01:50:09.510 --> 01:50:09.520 align:start position:0% but i will show you this which is the 01:50:09.520 --> 01:50:11.669 align:start position:0% but i will show you this which is the loop<01:50:09.760> macro<01:50:10.320> it's<01:50:10.480> simultaneously 01:50:11.669 --> 01:50:11.679 align:start position:0% loop macro it's simultaneously 01:50:11.679 --> 01:50:15.510 align:start position:0% loop macro it's simultaneously i<01:50:11.760> think<01:50:14.159> one<01:50:14.320> of<01:50:14.480> the 01:50:15.510 --> 01:50:15.520 align:start position:0% i think one of the 01:50:15.520 --> 01:50:19.350 align:start position:0% i think one of the most<01:50:16.960> offensive<01:50:18.159> macros<01:50:18.639> to<01:50:18.880> people<01:50:19.119> coming 01:50:19.350 --> 01:50:19.360 align:start position:0% most offensive macros to people coming 01:50:19.360 --> 01:50:21.270 align:start position:0% most offensive macros to people coming from<01:50:19.520> closure<01:50:19.920> and<01:50:20.080> i<01:50:20.320> think<01:50:20.560> also<01:50:20.800> one<01:50:20.960> of<01:50:21.040> the 01:50:21.270 --> 01:50:21.280 align:start position:0% from closure and i think also one of the 01:50:21.280 --> 01:50:22.790 align:start position:0% from closure and i think also one of the most<01:50:21.520> illustrative<01:50:22.159> of<01:50:22.239> the<01:50:22.320> differences 01:50:22.790 --> 01:50:22.800 align:start position:0% most illustrative of the differences 01:50:22.800 --> 01:50:25.430 align:start position:0% most illustrative of the differences between<01:50:23.040> common<01:50:23.280> lisp<01:50:23.520> and<01:50:23.599> closure 01:50:25.430 --> 01:50:25.440 align:start position:0% between common lisp and closure 01:50:25.440 --> 01:50:26.709 align:start position:0% between common lisp and closure but<01:50:25.599> there's<01:50:25.760> a<01:50:25.840> macro<01:50:26.239> in<01:50:26.320> common<01:50:26.560> list 01:50:26.709 --> 01:50:26.719 align:start position:0% but there's a macro in common list 01:50:26.719 --> 01:50:29.910 align:start position:0% but there's a macro in common list called<01:50:26.880> loop<01:50:28.320> and 01:50:29.910 --> 01:50:29.920 align:start position:0% called loop and 01:50:29.920 --> 01:50:42.470 align:start position:0% called loop and let<01:50:30.080> me<01:50:30.239> just<01:50:30.320> write<01:50:30.560> out<01:50:30.719> a<01:50:36.840> thing 01:50:42.470 --> 01:50:42.480 align:start position:0% 01:50:42.480 --> 01:50:50.790 align:start position:0% all<01:50:42.639> right<01:50:43.679> so 01:50:50.790 --> 01:50:50.800 align:start position:0% 01:50:50.800 --> 01:50:54.229 align:start position:0% it<01:50:50.960> looks<01:50:51.280> like<01:50:51.520> i'm<01:50:51.760> writing<01:50:52.960> in<01:50:53.119> blub<01:50:53.760> here 01:50:54.229 --> 01:50:54.239 align:start position:0% it looks like i'm writing in blub here 01:50:54.239 --> 01:50:56.470 align:start position:0% it looks like i'm writing in blub here right<01:50:55.040> it's<01:50:55.280> like<01:50:55.440> straight<01:50:55.760> up<01:50:55.920> imperative 01:50:56.470 --> 01:50:56.480 align:start position:0% right it's like straight up imperative 01:50:56.480 --> 01:50:57.750 align:start position:0% right it's like straight up imperative stuff 01:50:57.750 --> 01:50:57.760 align:start position:0% stuff 01:50:57.760 --> 01:51:00.790 align:start position:0% stuff um<01:50:58.880> but<01:50:59.040> what<01:50:59.199> this<01:50:59.440> is<01:50:59.599> is<01:50:59.679> this<01:50:59.840> is<01:51:00.000> the<01:51:00.080> dsl 01:51:00.790 --> 01:51:00.800 align:start position:0% um but what this is is this is the dsl 01:51:00.800 --> 01:51:04.830 align:start position:0% um but what this is is this is the dsl embedded<01:51:01.199> in<01:51:01.360> common<01:51:01.679> lisp<01:51:02.239> and<01:51:02.400> it<01:51:02.560> is<01:51:02.719> a 01:51:04.830 --> 01:51:04.840 align:start position:0% embedded in common lisp and it is a 01:51:04.840 --> 01:51:06.550 align:start position:0% embedded in common lisp and it is a really 01:51:06.550 --> 01:51:06.560 align:start position:0% really 01:51:06.560 --> 01:51:09.669 align:start position:0% really slash<01:51:07.119> complicated<01:51:08.880> language 01:51:09.669 --> 01:51:09.679 align:start position:0% slash complicated language 01:51:09.679 --> 01:51:13.589 align:start position:0% slash complicated language for<01:51:11.679> performing<01:51:12.159> iteration 01:51:13.589 --> 01:51:13.599 align:start position:0% for performing iteration 01:51:13.599 --> 01:51:15.910 align:start position:0% for performing iteration so<01:51:14.159> in<01:51:14.320> common<01:51:14.639> enclosure<01:51:15.199> we<01:51:15.280> have<01:51:15.599> lazy 01:51:15.910 --> 01:51:15.920 align:start position:0% so in common enclosure we have lazy 01:51:15.920 --> 01:51:16.790 align:start position:0% so in common enclosure we have lazy sequences 01:51:16.790 --> 01:51:16.800 align:start position:0% sequences 01:51:16.800 --> 01:51:21.109 align:start position:0% sequences we<01:51:17.040> have<01:51:17.679> uh<01:51:17.920> recursion<01:51:19.440> we<01:51:19.679> have 01:51:21.109 --> 01:51:21.119 align:start position:0% we have uh recursion we have 01:51:21.119 --> 01:51:24.470 align:start position:0% we have uh recursion we have uh<01:51:22.000> the<01:51:22.159> loop<01:51:22.480> recur<01:51:23.280> construct<01:51:24.080> for<01:51:24.239> doing 01:51:24.470 --> 01:51:24.480 align:start position:0% uh the loop recur construct for doing 01:51:24.480 --> 01:51:26.470 align:start position:0% uh the loop recur construct for doing iteration 01:51:26.470 --> 01:51:26.480 align:start position:0% iteration 01:51:26.480 --> 01:51:27.910 align:start position:0% iteration and<01:51:26.639> those<01:51:26.800> are<01:51:26.960> all<01:51:27.119> functional<01:51:27.679> in<01:51:27.760> the 01:51:27.910 --> 01:51:27.920 align:start position:0% and those are all functional in the 01:51:27.920 --> 01:51:29.830 align:start position:0% and those are all functional in the sense<01:51:28.320> that<01:51:28.639> they<01:51:28.800> don't 01:51:29.830 --> 01:51:29.840 align:start position:0% sense that they don't 01:51:29.840 --> 01:51:32.310 align:start position:0% sense that they don't imply<01:51:30.639> or<01:51:30.800> they<01:51:30.960> don't<01:51:31.119> necessitate<01:51:31.840> mutation 01:51:32.310 --> 01:51:32.320 align:start position:0% imply or they don't necessitate mutation 01:51:32.320 --> 01:51:34.070 align:start position:0% imply or they don't necessitate mutation of<01:51:32.400> anything<01:51:32.800> so<01:51:32.960> you<01:51:33.040> don't<01:51:33.280> need<01:51:33.440> to<01:51:33.679> name 01:51:34.070 --> 01:51:34.080 align:start position:0% of anything so you don't need to name 01:51:34.080 --> 01:51:36.550 align:start position:0% of anything so you don't need to name something<01:51:35.199> in<01:51:35.360> order<01:51:35.599> to<01:51:35.760> mutate<01:51:36.159> it<01:51:36.239> so<01:51:36.400> that 01:51:36.550 --> 01:51:36.560 align:start position:0% something in order to mutate it so that 01:51:36.560 --> 01:51:38.310 align:start position:0% something in order to mutate it so that you<01:51:36.639> can<01:51:36.800> add<01:51:37.040> something<01:51:37.360> to<01:51:37.599> it 01:51:38.310 --> 01:51:38.320 align:start position:0% you can add something to it 01:51:38.320 --> 01:51:41.510 align:start position:0% you can add something to it uh<01:51:39.199> lupercur<01:51:39.840> is<01:51:40.080> is<01:51:40.239> like<01:51:40.480> probably<01:51:41.119> closure 01:51:41.510 --> 01:51:41.520 align:start position:0% uh lupercur is is like probably closure 01:51:41.520 --> 01:51:43.430 align:start position:0% uh lupercur is is like probably closure is<01:51:41.679> most 01:51:43.430 --> 01:51:43.440 align:start position:0% is most 01:51:43.440 --> 01:51:44.790 align:start position:0% is most i<01:51:43.599> don't<01:51:43.679> know<01:51:43.840> i<01:51:44.000> feel<01:51:44.239> is<01:51:44.320> one<01:51:44.480> of<01:51:44.560> the<01:51:44.639> most 01:51:44.790 --> 01:51:44.800 align:start position:0% i don't know i feel is one of the most 01:51:44.800 --> 01:51:47.669 align:start position:0% i don't know i feel is one of the most elegant<01:51:45.119> things<01:51:45.360> in<01:51:45.440> closure<01:51:45.920> because 01:51:47.669 --> 01:51:47.679 align:start position:0% elegant things in closure because 01:51:47.679 --> 01:51:49.990 align:start position:0% elegant things in closure because it's<01:51:47.920> a<01:51:48.080> functional<01:51:48.639> iteration<01:51:49.280> construct 01:51:49.990 --> 01:51:50.000 align:start position:0% it's a functional iteration construct 01:51:50.000 --> 01:51:51.830 align:start position:0% it's a functional iteration construct and<01:51:50.159> it<01:51:50.400> bottles<01:51:50.880> up 01:51:51.830 --> 01:51:51.840 align:start position:0% and it bottles up 01:51:51.840 --> 01:51:53.109 align:start position:0% and it bottles up the<01:51:52.000> concept<01:51:52.320> of<01:51:52.480> iteration<01:51:52.880> in<01:51:52.960> an 01:51:53.109 --> 01:51:53.119 align:start position:0% the concept of iteration in an 01:51:53.119 --> 01:51:55.270 align:start position:0% the concept of iteration in an interesting<01:51:53.520> way<01:51:54.320> i<01:51:54.560> agree<01:51:54.960> and 01:51:55.270 --> 01:51:55.280 align:start position:0% interesting way i agree and 01:51:55.280 --> 01:51:58.149 align:start position:0% interesting way i agree and that's<01:51:55.520> the<01:51:55.599> equivalent<01:51:56.159> of<01:51:56.320> the<01:51:56.800> i<01:51:56.960> mean<01:51:57.119> if 01:51:58.149 --> 01:51:58.159 align:start position:0% that's the equivalent of the i mean if 01:51:58.159 --> 01:51:59.350 align:start position:0% that's the equivalent of the i mean if if<01:51:58.320> you<01:51:58.480> had 01:51:59.350 --> 01:51:59.360 align:start position:0% if you had 01:51:59.360 --> 01:52:01.910 align:start position:0% if you had visuality<01:52:00.080> recursion<01:52:00.639> in<01:52:00.719> the<01:52:00.960> jbm<01:52:01.520> then<01:52:01.760> you 01:52:01.910 --> 01:52:01.920 align:start position:0% visuality recursion in the jbm then you 01:52:01.920 --> 01:52:02.470 align:start position:0% visuality recursion in the jbm then you wouldn't 01:52:02.470 --> 01:52:02.480 align:start position:0% wouldn't 01:52:02.480 --> 01:52:03.910 align:start position:0% wouldn't you<01:52:02.560> wouldn't<01:52:02.880> even<01:52:03.040> need<01:52:03.280> the<01:52:03.360> recur<01:52:03.760> you 01:52:03.910 --> 01:52:03.920 align:start position:0% you wouldn't even need the recur you 01:52:03.920 --> 01:52:06.149 align:start position:0% you wouldn't even need the recur you could<01:52:04.080> you<01:52:04.239> just<01:52:04.480> use<01:52:04.719> the<01:52:04.880> same<01:52:05.199> symbol 01:52:06.149 --> 01:52:06.159 align:start position:0% could you just use the same symbol 01:52:06.159 --> 01:52:08.229 align:start position:0% could you just use the same symbol that<01:52:06.320> you<01:52:06.560> use<01:52:06.800> to<01:52:06.880> define<01:52:07.440> your<01:52:07.840> liking 01:52:08.229 --> 01:52:08.239 align:start position:0% that you use to define your liking 01:52:08.239 --> 01:52:09.510 align:start position:0% that you use to define your liking scheme<01:52:08.639> you<01:52:08.800> can 01:52:09.510 --> 01:52:09.520 align:start position:0% scheme you can 01:52:09.520 --> 01:52:13.910 align:start position:0% scheme you can do<01:52:09.679> very<01:52:10.159> elegant<01:52:10.560> reversion<01:52:11.679> right<01:52:12.239> right 01:52:13.910 --> 01:52:13.920 align:start position:0% do very elegant reversion right right 01:52:13.920 --> 01:52:18.229 align:start position:0% do very elegant reversion right right um<01:52:15.199> so<01:52:16.800> uh 01:52:18.229 --> 01:52:18.239 align:start position:0% um so uh 01:52:18.239 --> 01:52:20.550 align:start position:0% um so uh common<01:52:18.560> lisp<01:52:18.960> is<01:52:19.199> not<01:52:19.760> the<01:52:19.840> focus<01:52:20.239> of<01:52:20.320> common 01:52:20.550 --> 01:52:20.560 align:start position:0% common lisp is not the focus of common 01:52:20.560 --> 01:52:22.629 align:start position:0% common lisp is not the focus of common list<01:52:20.800> is<01:52:20.880> not<01:52:21.040> functional<01:52:21.440> programming 01:52:22.629 --> 01:52:22.639 align:start position:0% list is not functional programming 01:52:22.639 --> 01:52:24.950 align:start position:0% list is not functional programming um<01:52:23.040> it's<01:52:23.280> not<01:52:23.520> impossible<01:52:24.080> to<01:52:24.239> do<01:52:24.560> but<01:52:24.800> when 01:52:24.950 --> 01:52:24.960 align:start position:0% um it's not impossible to do but when 01:52:24.960 --> 01:52:26.550 align:start position:0% um it's not impossible to do but when it's<01:52:25.119> done<01:52:25.360> it's<01:52:25.520> done<01:52:25.760> by<01:52:26.000> convention<01:52:26.480> and 01:52:26.550 --> 01:52:26.560 align:start position:0% it's done it's done by convention and 01:52:26.560 --> 01:52:28.470 align:start position:0% it's done it's done by convention and with<01:52:26.800> the<01:52:26.880> help<01:52:27.119> of<01:52:27.360> libraries 01:52:28.470 --> 01:52:28.480 align:start position:0% with the help of libraries 01:52:28.480 --> 01:52:30.149 align:start position:0% with the help of libraries but<01:52:28.719> all<01:52:28.800> of<01:52:28.880> the<01:52:29.040> iteration<01:52:29.520> constructs<01:52:30.000> that 01:52:30.149 --> 01:52:30.159 align:start position:0% but all of the iteration constructs that 01:52:30.159 --> 01:52:31.589 align:start position:0% but all of the iteration constructs that are<01:52:30.320> in<01:52:30.400> common<01:52:30.719> lisp 01:52:31.589 --> 01:52:31.599 align:start position:0% are in common lisp 01:52:31.599 --> 01:52:35.109 align:start position:0% are in common lisp other<01:52:31.920> than<01:52:32.639> recursion<01:52:34.400> are 01:52:35.109 --> 01:52:35.119 align:start position:0% other than recursion are 01:52:35.119 --> 01:52:38.149 align:start position:0% other than recursion are uh<01:52:36.480> you<01:52:36.560> know<01:52:36.719> non-functional<01:52:37.599> or<01:52:37.760> at<01:52:37.840> least 01:52:38.149 --> 01:52:38.159 align:start position:0% uh you know non-functional or at least 01:52:38.159 --> 01:52:39.109 align:start position:0% uh you know non-functional or at least admit 01:52:39.109 --> 01:52:39.119 align:start position:0% admit 01:52:39.119 --> 01:52:41.910 align:start position:0% admit mutation<01:52:40.159> uh<01:52:40.320> or<01:52:40.560> imperative<01:52:41.360> stuff<01:52:41.679> into 01:52:41.910 --> 01:52:41.920 align:start position:0% mutation uh or imperative stuff into 01:52:41.920 --> 01:52:42.310 align:start position:0% mutation uh or imperative stuff into their 01:52:42.310 --> 01:52:42.320 align:start position:0% their 01:52:42.320 --> 01:52:47.109 align:start position:0% their paradigm<01:52:43.199> into<01:52:43.440> their<01:52:43.840> dsl 01:52:47.109 --> 01:52:47.119 align:start position:0% 01:52:47.119 --> 01:52:50.470 align:start position:0% so<01:52:47.520> loop 01:52:50.470 --> 01:52:50.480 align:start position:0% 01:52:50.480 --> 01:52:52.229 align:start position:0% is<01:52:50.719> a<01:52:51.040> basically<01:52:51.440> a<01:52:51.520> small<01:52:51.840> programming 01:52:52.229 --> 01:52:52.239 align:start position:0% is a basically a small programming 01:52:52.239 --> 01:52:54.229 align:start position:0% is a basically a small programming language<01:52:52.800> embedded<01:52:53.280> in<01:52:53.360> common<01:52:53.679> lisp 01:52:54.229 --> 01:52:54.239 align:start position:0% language embedded in common lisp 01:52:54.239 --> 01:52:58.149 align:start position:0% language embedded in common lisp and<01:52:54.400> it's<01:52:55.760> for<01:52:55.920> doing<01:52:56.880> iteration 01:52:58.149 --> 01:52:58.159 align:start position:0% and it's for doing iteration 01:52:58.159 --> 01:52:59.669 align:start position:0% and it's for doing iteration and<01:52:58.480> i<01:52:58.560> guess<01:52:58.800> you<01:52:58.960> can<01:52:59.199> use<01:52:59.360> it<01:52:59.520> in<01:52:59.599> a 01:52:59.669 --> 01:52:59.679 align:start position:0% and i guess you can use it in a 01:52:59.679 --> 01:53:00.950 align:start position:0% and i guess you can use it in a functional<01:53:00.159> way<01:53:00.400> like<01:53:00.560> here<01:53:00.800> we're 01:53:00.950 --> 01:53:00.960 align:start position:0% functional way like here we're 01:53:00.960 --> 01:53:02.470 align:start position:0% functional way like here we're collecting<01:53:01.440> a<01:53:01.520> list<01:53:01.760> we're<01:53:01.920> not<01:53:02.080> strictly 01:53:02.470 --> 01:53:02.480 align:start position:0% collecting a list we're not strictly 01:53:02.480 --> 01:53:03.990 align:start position:0% collecting a list we're not strictly mutating<01:53:02.960> anything 01:53:03.990 --> 01:53:04.000 align:start position:0% mutating anything 01:53:04.000 --> 01:53:12.709 align:start position:0% mutating anything but<01:53:04.320> it<01:53:04.480> supports<01:53:04.960> a<01:53:05.040> concept<01:53:10.840> of 01:53:12.709 --> 01:53:12.719 align:start position:0% but it supports a concept of 01:53:12.719 --> 01:53:22.070 align:start position:0% but it supports a concept of oh<01:53:13.280> oops 01:53:22.070 --> 01:53:22.080 align:start position:0% 01:53:22.080 --> 01:53:25.350 align:start position:0% yeah<01:53:22.719> so 01:53:25.350 --> 01:53:25.360 align:start position:0% 01:53:25.360 --> 01:53:27.270 align:start position:0% i<01:53:25.599> think<01:53:25.840> i<01:53:26.080> it's<01:53:26.320> not<01:53:26.480> clear<01:53:26.639> to<01:53:26.719> me<01:53:26.960> exactly 01:53:27.270 --> 01:53:27.280 align:start position:0% i think i it's not clear to me exactly 01:53:27.280 --> 01:53:28.950 align:start position:0% i think i it's not clear to me exactly what's<01:53:27.440> going<01:53:27.679> on<01:53:27.840> here<01:53:28.080> but 01:53:28.950 --> 01:53:28.960 align:start position:0% what's going on here but 01:53:28.960 --> 01:53:30.790 align:start position:0% what's going on here but there's<01:53:29.280> multiple<01:53:29.760> keywords<01:53:30.159> supported<01:53:30.639> in 01:53:30.790 --> 01:53:30.800 align:start position:0% there's multiple keywords supported in 01:53:30.800 --> 01:53:33.189 align:start position:0% there's multiple keywords supported in loop<01:53:31.280> four<01:53:31.920> creates 01:53:33.189 --> 01:53:33.199 align:start position:0% loop four creates 01:53:33.199 --> 01:53:35.669 align:start position:0% loop four creates the<01:53:33.360> bounds<01:53:33.679> of<01:53:33.840> an<01:53:34.000> iteration<01:53:34.719> and<01:53:34.880> then<01:53:35.199> when 01:53:35.669 --> 01:53:35.679 align:start position:0% the bounds of an iteration and then when 01:53:35.679 --> 01:53:37.910 align:start position:0% the bounds of an iteration and then when is<01:53:35.840> a<01:53:35.920> conditional<01:53:36.400> inside<01:53:36.639> the<01:53:36.800> body 01:53:37.910 --> 01:53:37.920 align:start position:0% is a conditional inside the body 01:53:37.920 --> 01:53:39.510 align:start position:0% is a conditional inside the body do<01:53:38.159> lets<01:53:38.400> you<01:53:38.480> do<01:53:38.639> a<01:53:38.719> side<01:53:38.880> effect<01:53:39.280> at<01:53:39.360> that 01:53:39.510 --> 01:53:39.520 align:start position:0% do lets you do a side effect at that 01:53:39.520 --> 01:53:41.669 align:start position:0% do lets you do a side effect at that point<01:53:39.679> in<01:53:39.760> the<01:53:39.920> iteration<01:53:40.480> and<01:53:40.639> then<01:53:40.880> collect 01:53:41.669 --> 01:53:41.679 align:start position:0% point in the iteration and then collect 01:53:41.679 --> 01:53:46.470 align:start position:0% point in the iteration and then collect will<01:53:42.000> contribute<01:53:42.719> a<01:53:42.880> value<01:53:43.360> to<01:53:43.679> an<01:53:43.840> implicit 01:53:46.470 --> 01:53:46.480 align:start position:0% 01:53:46.480 --> 01:53:49.109 align:start position:0% set<01:53:46.719> of<01:53:47.280> or<01:53:47.440> an<01:53:47.599> implicit<01:53:48.000> list<01:53:48.480> of<01:53:48.800> values 01:53:49.109 --> 01:53:49.119 align:start position:0% set of or an implicit list of values 01:53:49.119 --> 01:53:57.910 align:start position:0% set of or an implicit list of values you're<01:53:49.639> accumulating<01:53:52.840> um 01:53:57.910 --> 01:53:57.920 align:start position:0% 01:53:57.920 --> 01:53:59.589 align:start position:0% i<01:53:58.080> think<01:53:58.320> the<01:53:58.719> yeah<01:53:58.880> the<01:53:58.960> direction<01:53:59.280> i'm<01:53:59.440> going 01:53:59.589 --> 01:53:59.599 align:start position:0% i think the yeah the direction i'm going 01:53:59.599 --> 01:54:01.189 align:start position:0% i think the yeah the direction i'm going with<01:53:59.760> this<01:54:00.000> is<01:54:00.159> just<01:54:00.320> that<01:54:00.480> first<01:54:00.719> of<01:54:00.880> all<01:54:01.040> it's 01:54:01.189 --> 01:54:01.199 align:start position:0% with this is just that first of all it's 01:54:01.199 --> 01:54:02.629 align:start position:0% with this is just that first of all it's pretty<01:54:01.360> crazy<01:54:01.679> coming<01:54:01.920> from<01:54:02.080> closure 01:54:02.629 --> 01:54:02.639 align:start position:0% pretty crazy coming from closure 01:54:02.639 --> 01:54:05.350 align:start position:0% pretty crazy coming from closure to<01:54:02.880> have<01:54:03.360> this<01:54:03.920> involved<01:54:04.320> of<01:54:04.480> a<01:54:04.560> dsl<01:54:05.199> be 01:54:05.350 --> 01:54:05.360 align:start position:0% to have this involved of a dsl be 01:54:05.360 --> 01:54:08.790 align:start position:0% to have this involved of a dsl be supported<01:54:05.760> out<01:54:05.840> of<01:54:05.920> the<01:54:06.000> box<01:54:06.400> is<01:54:06.639> pretty<01:54:06.880> wild 01:54:08.790 --> 01:54:08.800 align:start position:0% supported out of the box is pretty wild 01:54:08.800 --> 01:54:10.790 align:start position:0% supported out of the box is pretty wild but<01:54:09.040> i<01:54:09.119> think<01:54:09.360> it<01:54:09.440> also<01:54:09.760> shows<01:54:10.239> and<01:54:10.320> for<01:54:10.480> me<01:54:10.639> it 01:54:10.790 --> 01:54:10.800 align:start position:0% but i think it also shows and for me it 01:54:10.800 --> 01:54:12.149 align:start position:0% but i think it also shows and for me it has<01:54:10.960> shown 01:54:12.149 --> 01:54:12.159 align:start position:0% has shown 01:54:12.159 --> 01:54:16.149 align:start position:0% has shown that 01:54:16.149 --> 01:54:16.159 align:start position:0% 01:54:16.159 --> 01:54:18.470 align:start position:0% you<01:54:16.639> there<01:54:16.880> is<01:54:17.360> the<01:54:17.520> value<01:54:17.840> of<01:54:17.920> this<01:54:18.080> deliver 01:54:18.470 --> 01:54:18.480 align:start position:0% you there is the value of this deliver 01:54:18.480 --> 01:54:20.629 align:start position:0% you there is the value of this deliver is<01:54:18.639> is<01:54:18.719> this<01:54:18.880> doesn't<01:54:19.199> rely<01:54:19.760> on<01:54:20.000> any<01:54:20.239> runtime 01:54:20.629 --> 01:54:20.639 align:start position:0% is is this doesn't rely on any runtime 01:54:20.639 --> 01:54:21.669 align:start position:0% is is this doesn't rely on any runtime abstractions 01:54:21.669 --> 01:54:21.679 align:start position:0% abstractions 01:54:21.679 --> 01:54:24.390 align:start position:0% abstractions so<01:54:21.920> there's<01:54:22.159> no<01:54:22.480> need<01:54:22.719> for<01:54:22.880> a<01:54:22.960> lazy<01:54:23.280> sequence 01:54:24.390 --> 01:54:24.400 align:start position:0% so there's no need for a lazy sequence 01:54:24.400 --> 01:54:25.750 align:start position:0% so there's no need for a lazy sequence abstraction 01:54:25.750 --> 01:54:25.760 align:start position:0% abstraction 01:54:25.760 --> 01:54:28.790 align:start position:0% abstraction loop<01:54:26.080> expands<01:54:26.719> into<01:54:27.920> the<01:54:28.080> lowest 01:54:28.790 --> 01:54:28.800 align:start position:0% loop expands into the lowest 01:54:28.800 --> 01:54:30.709 align:start position:0% loop expands into the lowest level<01:54:29.199> possible<01:54:29.760> common<01:54:30.080> lisp<01:54:30.320> code<01:54:30.560> like 01:54:30.709 --> 01:54:30.719 align:start position:0% level possible common lisp code like 01:54:30.719 --> 01:54:31.830 align:start position:0% level possible common lisp code like basically<01:54:31.119> go<01:54:31.360> to 01:54:31.830 --> 01:54:31.840 align:start position:0% basically go to 01:54:31.840 --> 01:54:33.669 align:start position:0% basically go to is<01:54:31.920> what<01:54:32.080> it<01:54:32.239> expands<01:54:32.639> into<01:54:32.960> go<01:54:33.119> to's<01:54:33.440> with 01:54:33.669 --> 01:54:33.679 align:start position:0% is what it expands into go to's with 01:54:33.679 --> 01:54:35.189 align:start position:0% is what it expands into go to's with mutating<01:54:34.320> and 01:54:35.189 --> 01:54:35.199 align:start position:0% mutating and 01:54:35.199 --> 01:54:38.229 align:start position:0% mutating and cutters<01:54:35.599> and<01:54:35.760> stuff<01:54:36.000> like<01:54:36.159> that<01:54:37.199> so<01:54:37.679> it's<01:54:37.920> high 01:54:38.229 --> 01:54:38.239 align:start position:0% cutters and stuff like that so it's high 01:54:38.239 --> 01:54:39.669 align:start position:0% cutters and stuff like that so it's high level<01:54:38.560> in<01:54:38.719> the<01:54:38.800> sense<01:54:39.040> that<01:54:39.199> it<01:54:39.280> gives<01:54:39.440> you<01:54:39.599> a 01:54:39.669 --> 01:54:39.679 align:start position:0% level in the sense that it gives you a 01:54:39.679 --> 01:54:41.589 align:start position:0% level in the sense that it gives you a high<01:54:39.840> level<01:54:40.080> language<01:54:40.480> to<01:54:40.639> work<01:54:40.880> with 01:54:41.589 --> 01:54:41.599 align:start position:0% high level language to work with 01:54:41.599 --> 01:54:43.750 align:start position:0% high level language to work with that<01:54:41.840> looks<01:54:42.080> pretty<01:54:42.320> much<01:54:42.560> like<01:54:43.119> python<01:54:43.679> or 01:54:43.750 --> 01:54:43.760 align:start position:0% that looks pretty much like python or 01:54:43.760 --> 01:54:44.870 align:start position:0% that looks pretty much like python or something 01:54:44.870 --> 01:54:44.880 align:start position:0% something 01:54:44.880 --> 01:54:47.910 align:start position:0% something but<01:54:45.119> it's<01:54:45.360> low<01:54:45.599> level<01:54:46.480> in<01:54:46.560> the<01:54:46.719> sense<01:54:47.040> that 01:54:47.910 --> 01:54:47.920 align:start position:0% but it's low level in the sense that 01:54:47.920 --> 01:54:50.950 align:start position:0% but it's low level in the sense that it<01:54:48.239> produces<01:54:48.800> code<01:54:49.760> that<01:54:49.920> depends<01:54:50.320> on<01:54:50.480> only 01:54:50.950 --> 01:54:50.960 align:start position:0% it produces code that depends on only 01:54:50.960 --> 01:54:53.189 align:start position:0% it produces code that depends on only commonly<01:54:51.679> lowest<01:54:52.080> level<01:54:52.560> runtime 01:54:53.189 --> 01:54:53.199 align:start position:0% commonly lowest level runtime 01:54:53.199 --> 01:54:55.430 align:start position:0% commonly lowest level runtime affordances 01:54:55.430 --> 01:54:55.440 align:start position:0% affordances 01:54:55.440 --> 01:54:59.350 align:start position:0% affordances and<01:54:55.760> that's<01:54:56.000> a<01:54:56.080> trade-off<01:54:56.719> obviously 01:54:59.350 --> 01:54:59.360 align:start position:0% 01:54:59.360 --> 01:55:01.990 align:start position:0% you<01:54:59.440> know<01:54:59.599> this<01:54:59.840> doesn't<01:55:00.239> participate<01:55:01.040> in<01:55:01.599> a 01:55:01.990 --> 01:55:02.000 align:start position:0% you know this doesn't participate in a 01:55:02.000 --> 01:55:03.750 align:start position:0% you know this doesn't participate in a system<01:55:02.560> of<01:55:02.719> runtime<01:55:03.199> constructs<01:55:03.679> or 01:55:03.750 --> 01:55:03.760 align:start position:0% system of runtime constructs or 01:55:03.760 --> 01:55:05.750 align:start position:0% system of runtime constructs or distractions<01:55:04.400> the<01:55:04.560> way<01:55:04.800> sequences<01:55:05.280> enclosure 01:55:05.750 --> 01:55:05.760 align:start position:0% distractions the way sequences enclosure 01:55:05.760 --> 01:55:07.669 align:start position:0% distractions the way sequences enclosure do 01:55:07.669 --> 01:55:07.679 align:start position:0% do 01:55:07.679 --> 01:55:09.510 align:start position:0% do but<01:55:07.920> at<01:55:08.000> the<01:55:08.080> same<01:55:08.400> time<01:55:08.800> you're<01:55:09.040> not<01:55:09.199> paying 01:55:09.510 --> 01:55:09.520 align:start position:0% but at the same time you're not paying 01:55:09.520 --> 01:55:10.950 align:start position:0% but at the same time you're not paying for<01:55:09.679> such<01:55:09.920> a<01:55:10.000> system 01:55:10.950 --> 01:55:10.960 align:start position:0% for such a system 01:55:10.960 --> 01:55:14.149 align:start position:0% for such a system so<01:55:12.000> um<01:55:12.960> yeah<01:55:13.199> just<01:55:13.360> kind<01:55:13.520> of<01:55:13.599> conceptually 01:55:14.149 --> 01:55:14.159 align:start position:0% so um yeah just kind of conceptually 01:55:14.159 --> 01:55:15.109 align:start position:0% so um yeah just kind of conceptually interesting 01:55:15.109 --> 01:55:15.119 align:start position:0% interesting 01:55:15.119 --> 01:55:17.589 align:start position:0% interesting thing<01:55:15.520> that<01:55:15.679> occupies<01:55:16.320> a<01:55:16.400> point<01:55:16.639> in<01:55:17.119> a<01:55:17.199> design 01:55:17.589 --> 01:55:17.599 align:start position:0% thing that occupies a point in a design 01:55:17.599 --> 01:55:20.950 align:start position:0% thing that occupies a point in a design space<01:55:17.840> that<01:55:18.000> i<01:55:18.159> don't<01:55:18.320> think<01:55:18.560> we 01:55:20.950 --> 01:55:20.960 align:start position:0% 01:55:20.960 --> 01:55:23.589 align:start position:0% use<01:55:21.440> or<01:55:21.679> are<01:55:21.840> supposed<01:55:22.239> to<01:55:22.320> use<01:55:22.719> enclosure 01:55:23.589 --> 01:55:23.599 align:start position:0% use or are supposed to use enclosure 01:55:23.599 --> 01:55:25.910 align:start position:0% use or are supposed to use enclosure because<01:55:23.840> we<01:55:23.920> have<01:55:24.080> lazy<01:55:24.400> sequences<01:55:24.960> and 01:55:25.910 --> 01:55:25.920 align:start position:0% because we have lazy sequences and 01:55:25.920 --> 01:55:28.550 align:start position:0% because we have lazy sequences and recursion<01:55:26.400> and<01:55:26.480> so<01:55:26.639> forth<01:55:28.000> if<01:55:28.159> that<01:55:28.320> makes 01:55:28.550 --> 01:55:28.560 align:start position:0% recursion and so forth if that makes 01:55:28.560 --> 01:55:33.350 align:start position:0% recursion and so forth if that makes sense 01:55:33.350 --> 01:55:33.360 align:start position:0% 01:55:33.360 --> 01:55:37.189 align:start position:0% cool<01:55:34.880> well<01:55:35.119> i<01:55:35.199> think<01:55:35.360> with<01:55:35.599> that 01:55:37.189 --> 01:55:37.199 align:start position:0% cool well i think with that 01:55:37.199 --> 01:55:38.550 align:start position:0% cool well i think with that i<01:55:37.360> should<01:55:37.520> probably<01:55:37.760> go<01:55:37.920> but<01:55:38.080> maybe<01:55:38.320> i'll<01:55:38.400> take 01:55:38.550 --> 01:55:38.560 align:start position:0% i should probably go but maybe i'll take 01:55:38.560 --> 01:55:44.149 align:start position:0% i should probably go but maybe i'll take one<01:55:38.719> more<01:55:38.960> question 01:55:44.149 --> 01:55:44.159 align:start position:0% 01:55:44.159 --> 01:55:46.310 align:start position:0% i'm<01:55:44.560> not<01:55:44.800> sure<01:55:44.960> we<01:55:45.119> have<01:55:45.360> the<01:55:45.520> time<01:55:45.840> for<01:55:46.000> that 01:55:46.310 --> 01:55:46.320 align:start position:0% i'm not sure we have the time for that 01:55:46.320 --> 01:55:47.430 align:start position:0% i'm not sure we have the time for that but 01:55:47.430 --> 01:55:47.440 align:start position:0% but 01:55:47.440 --> 01:55:51.030 align:start position:0% but i<01:55:47.679> can't<01:55:48.480> help<01:55:49.599> asking 01:55:51.030 --> 01:55:51.040 align:start position:0% i can't help asking 01:55:51.040 --> 01:55:54.870 align:start position:0% i can't help asking the<01:55:51.199> one<01:55:51.440> thing<01:55:51.599> you<01:55:51.760> didn't<01:55:52.000> talk<01:55:52.239> about<01:55:53.280> and 01:55:54.870 --> 01:55:54.880 align:start position:0% the one thing you didn't talk about and 01:55:54.880 --> 01:55:58.950 align:start position:0% the one thing you didn't talk about and are<01:55:55.840> in<01:55:56.080> this<01:55:56.960> whole<01:55:57.360> universe<01:55:57.920> of<01:55:58.000> yours 01:55:58.950 --> 01:55:58.960 align:start position:0% are in this whole universe of yours 01:55:58.960 --> 01:56:02.470 align:start position:0% are in this whole universe of yours oh<01:55:59.599> yeah<01:56:00.960> well 01:56:02.470 --> 01:56:02.480 align:start position:0% oh yeah well 01:56:02.480 --> 01:56:05.669 align:start position:0% oh yeah well i<01:56:03.360> i<01:56:04.000> enjoyed<01:56:04.400> working<01:56:04.719> with<01:56:04.960> r<01:56:05.360> and 01:56:05.669 --> 01:56:05.679 align:start position:0% i i enjoyed working with r and 01:56:05.679 --> 01:56:09.109 align:start position:0% i i enjoyed working with r and i<01:56:05.760> think<01:56:06.080> r<01:56:06.560> is<01:56:07.840> i<01:56:08.000> mean 01:56:09.109 --> 01:56:09.119 align:start position:0% i think r is i mean 01:56:09.119 --> 01:56:11.910 align:start position:0% i think r is i mean by<01:56:09.360> mccarthy's<01:56:10.000> definition<01:56:10.880> r<01:56:11.119> is<01:56:11.280> a<01:56:11.360> lisp<01:56:11.840> i 01:56:11.910 --> 01:56:11.920 align:start position:0% by mccarthy's definition r is a lisp i 01:56:11.920 --> 01:56:12.790 align:start position:0% by mccarthy's definition r is a lisp i mean<01:56:12.080> it<01:56:12.239> is<01:56:12.400> written 01:56:12.790 --> 01:56:12.800 align:start position:0% mean it is written 01:56:12.800 --> 01:56:16.070 align:start position:0% mean it is written in<01:56:13.599> data<01:56:13.920> structures<01:56:15.360> that<01:56:15.679> you<01:56:15.840> have 01:56:16.070 --> 01:56:16.080 align:start position:0% in data structures that you have 01:56:16.080 --> 01:56:16.790 align:start position:0% in data structures that you have accessible 01:56:16.790 --> 01:56:16.800 align:start position:0% accessible 01:56:16.800 --> 01:56:18.550 align:start position:0% accessible at<01:56:16.960> runtime<01:56:17.440> and<01:56:17.520> it's<01:56:17.679> an<01:56:17.760> online<01:56:18.080> compiler 01:56:18.550 --> 01:56:18.560 align:start position:0% at runtime and it's an online compiler 01:56:18.560 --> 01:56:22.149 align:start position:0% at runtime and it's an online compiler and<01:56:18.639> everything<01:56:19.760> um 01:56:22.149 --> 01:56:22.159 align:start position:0% 01:56:22.159 --> 01:56:25.589 align:start position:0% i<01:56:22.320> think<01:56:22.639> r<01:56:23.360> so 01:56:25.589 --> 01:56:25.599 align:start position:0% i think r so 01:56:25.599 --> 01:56:28.070 align:start position:0% i think r so i<01:56:26.480> did<01:56:26.639> not<01:56:26.800> find<01:56:27.040> myself<01:56:27.360> getting<01:56:27.679> obsessed 01:56:28.070 --> 01:56:28.080 align:start position:0% i did not find myself getting obsessed 01:56:28.080 --> 01:56:29.350 align:start position:0% i did not find myself getting obsessed with<01:56:28.239> it<01:56:28.320> the<01:56:28.400> way<01:56:28.560> that<01:56:28.639> i<01:56:28.719> am<01:56:28.880> obsessed<01:56:29.199> with 01:56:29.350 --> 01:56:29.360 align:start position:0% with it the way that i am obsessed with 01:56:29.360 --> 01:56:29.990 align:start position:0% with it the way that i am obsessed with common<01:56:29.599> lisp 01:56:29.990 --> 01:56:30.000 align:start position:0% common lisp 01:56:30.000 --> 01:56:31.990 align:start position:0% common lisp i<01:56:30.080> don't<01:56:30.239> know<01:56:30.320> why<01:56:30.480> that<01:56:30.719> is<01:56:31.440> i<01:56:31.520> don't<01:56:31.679> know<01:56:31.840> if 01:56:31.990 --> 01:56:32.000 align:start position:0% i don't know why that is i don't know if 01:56:32.000 --> 01:56:33.510 align:start position:0% i don't know why that is i don't know if it's<01:56:32.159> because<01:56:32.400> i'm<01:56:32.560> just<01:56:32.800> immune<01:56:33.119> to<01:56:33.280> being 01:56:33.510 --> 01:56:33.520 align:start position:0% it's because i'm just immune to being 01:56:33.520 --> 01:56:36.310 align:start position:0% it's because i'm just immune to being obsessed<01:56:33.840> with<01:56:33.920> things<01:56:34.159> that<01:56:34.239> are<01:56:34.320> popular 01:56:36.310 --> 01:56:36.320 align:start position:0% obsessed with things that are popular 01:56:36.320 --> 01:56:38.950 align:start position:0% obsessed with things that are popular um<01:56:36.960> i<01:56:37.199> i<01:56:37.280> don't<01:56:37.520> know<01:56:37.840> i<01:56:38.080> i<01:56:38.239> certainly<01:56:38.560> never 01:56:38.950 --> 01:56:38.960 align:start position:0% um i i don't know i i certainly never 01:56:38.960 --> 01:56:40.390 align:start position:0% um i i don't know i i certainly never really<01:56:39.199> had<01:56:39.360> any<01:56:39.520> problems<01:56:39.840> with<01:56:40.000> r<01:56:40.159> and<01:56:40.320> i 01:56:40.390 --> 01:56:40.400 align:start position:0% really had any problems with r and i 01:56:40.400 --> 01:56:40.870 align:start position:0% really had any problems with r and i think<01:56:40.639> it 01:56:40.870 --> 01:56:40.880 align:start position:0% think it 01:56:40.880 --> 01:56:42.790 align:start position:0% think it occupies<01:56:41.440> again<01:56:41.840> another<01:56:42.239> point<01:56:42.480> in<01:56:42.719> the 01:56:42.790 --> 01:56:42.800 align:start position:0% occupies again another point in the 01:56:42.800 --> 01:56:44.550 align:start position:0% occupies again another point in the design<01:56:43.119> space<01:56:43.440> that's<01:56:43.679> very<01:56:44.000> valuable<01:56:44.400> to 01:56:44.550 --> 01:56:44.560 align:start position:0% design space that's very valuable to 01:56:44.560 --> 01:56:46.310 align:start position:0% design space that's very valuable to lots<01:56:44.800> of<01:56:44.880> people 01:56:46.310 --> 01:56:46.320 align:start position:0% lots of people 01:56:46.320 --> 01:56:49.910 align:start position:0% lots of people um<01:56:48.320> an<01:56:48.560> interesting<01:56:48.960> thing<01:56:49.199> about 01:56:49.910 --> 01:56:49.920 align:start position:0% um an interesting thing about 01:56:49.920 --> 01:56:51.750 align:start position:0% um an interesting thing about maybe<01:56:50.159> you<01:56:50.480> need<01:56:50.800> s<01:56:51.040> expressions<01:56:51.520> in<01:56:51.599> your 01:56:51.750 --> 01:56:51.760 align:start position:0% maybe you need s expressions in your 01:56:51.760 --> 01:56:53.750 align:start position:0% maybe you need s expressions in your life<01:56:52.719> say<01:56:52.960> that<01:56:53.040> again 01:56:53.750 --> 01:56:53.760 align:start position:0% life say that again 01:56:53.760 --> 01:56:55.430 align:start position:0% life say that again maybe<01:56:54.080> you<01:56:54.159> need<01:56:54.400> s-expressions<01:56:55.119> in<01:56:55.280> your 01:56:55.430 --> 01:56:55.440 align:start position:0% maybe you need s-expressions in your 01:56:55.440 --> 01:56:58.149 align:start position:0% maybe you need s-expressions in your life 01:56:58.149 --> 01:56:58.159 align:start position:0% 01:56:58.159 --> 01:57:01.030 align:start position:0% maybe<01:56:58.880> maybe<01:56:59.119> that's<01:56:59.360> what<01:56:59.440> it<01:56:59.599> is<01:57:00.719> yeah<01:57:00.960> i 01:57:01.030 --> 01:57:01.040 align:start position:0% maybe maybe that's what it is yeah i 01:57:01.040 --> 01:57:01.430 align:start position:0% maybe maybe that's what it is yeah i think 01:57:01.430 --> 01:57:01.440 align:start position:0% think 01:57:01.440 --> 01:57:04.709 align:start position:0% think um<01:57:02.960> you<01:57:03.040> know<01:57:03.280> like<01:57:04.000> common<01:57:04.320> lisp 01:57:04.709 --> 01:57:04.719 align:start position:0% um you know like common lisp 01:57:04.719 --> 01:57:07.030 align:start position:0% um you know like common lisp r<01:57:05.040> is<01:57:05.280> also<01:57:05.599> has<01:57:05.760> kind<01:57:05.920> of<01:57:06.080> an<01:57:06.239> old-timey<01:57:06.719> feel 01:57:07.030 --> 01:57:07.040 align:start position:0% r is also has kind of an old-timey feel 01:57:07.040 --> 01:57:08.870 align:start position:0% r is also has kind of an old-timey feel it's<01:57:07.199> descended<01:57:07.599> from<01:57:07.760> a<01:57:08.480> pretty<01:57:08.719> old 01:57:08.870 --> 01:57:08.880 align:start position:0% it's descended from a pretty old 01:57:08.880 --> 01:57:10.550 align:start position:0% it's descended from a pretty old language<01:57:09.119> called<01:57:09.440> s 01:57:10.550 --> 01:57:10.560 align:start position:0% language called s 01:57:10.560 --> 01:57:13.990 align:start position:0% language called s and<01:57:11.360> um<01:57:12.080> the<01:57:12.239> ideas<01:57:12.639> go<01:57:12.800> back<01:57:13.119> decades 01:57:13.990 --> 01:57:14.000 align:start position:0% and um the ideas go back decades 01:57:14.000 --> 01:57:18.070 align:start position:0% and um the ideas go back decades and<01:57:15.599> uh<01:57:16.719> that's<01:57:16.960> fun 01:57:18.070 --> 01:57:18.080 align:start position:0% and uh that's fun 01:57:18.080 --> 01:57:23.510 align:start position:0% and uh that's fun bye<01:57:18.320> tori<01:57:18.639> thanks<01:57:18.800> for<01:57:18.960> coming<01:57:20.960> um 01:57:23.510 --> 01:57:23.520 align:start position:0% 01:57:23.520 --> 01:57:24.950 align:start position:0% there<01:57:23.679> is<01:57:23.840> a<01:57:23.920> very<01:57:24.159> interesting<01:57:24.480> thing<01:57:24.639> about 01:57:24.950 --> 01:57:24.960 align:start position:0% there is a very interesting thing about 01:57:24.960 --> 01:57:26.870 align:start position:0% there is a very interesting thing about r<01:57:25.280> that<01:57:25.520> is<01:57:25.679> unique<01:57:26.320> to<01:57:26.560> r 01:57:26.870 --> 01:57:26.880 align:start position:0% r that is unique to r 01:57:26.880 --> 01:57:29.750 align:start position:0% r that is unique to r among<01:57:27.599> lisps<01:57:28.159> and<01:57:28.719> among<01:57:29.040> all<01:57:29.199> languages<01:57:29.599> that 01:57:29.750 --> 01:57:29.760 align:start position:0% among lisps and among all languages that 01:57:29.760 --> 01:57:31.750 align:start position:0% among lisps and among all languages that i've<01:57:29.920> ever<01:57:30.159> known<01:57:30.480> which<01:57:30.719> is<01:57:30.880> that<01:57:31.119> r<01:57:31.360> has 01:57:31.750 --> 01:57:31.760 align:start position:0% i've ever known which is that r has 01:57:31.760 --> 01:57:34.950 align:start position:0% i've ever known which is that r has f<01:57:32.000> expressions<01:57:32.639> fespers<01:57:34.239> so 01:57:34.950 --> 01:57:34.960 align:start position:0% f expressions fespers so 01:57:34.960 --> 01:57:38.070 align:start position:0% f expressions fespers so r<01:57:35.280> is<01:57:35.440> a<01:57:35.520> call<01:57:35.760> by<01:57:36.000> need<01:57:36.480> language<01:57:37.599> and<01:57:37.760> lazy 01:57:38.070 --> 01:57:38.080 align:start position:0% r is a call by need language and lazy 01:57:38.080 --> 01:57:39.510 align:start position:0% r is a call by need language and lazy evaluation 01:57:39.510 --> 01:57:39.520 align:start position:0% evaluation 01:57:39.520 --> 01:57:42.149 align:start position:0% evaluation and<01:57:40.080> ours<01:57:40.800> so<01:57:41.199> you<01:57:41.280> know<01:57:41.440> common<01:57:41.760> lisp<01:57:42.000> has 01:57:42.149 --> 01:57:42.159 align:start position:0% and ours so you know common lisp has 01:57:42.159 --> 01:57:43.270 align:start position:0% and ours so you know common lisp has first<01:57:42.400> class<01:57:42.639> a<01:57:42.719> lot<01:57:42.800> of<01:57:42.880> things<01:57:43.040> that<01:57:43.119> come 01:57:43.270 --> 01:57:43.280 align:start position:0% first class a lot of things that come 01:57:43.280 --> 01:57:44.390 align:start position:0% first class a lot of things that come unless<01:57:43.520> our<01:57:43.599> first<01:57:43.840> class<01:57:44.000> but<01:57:44.159> one<01:57:44.239> thing 01:57:44.390 --> 01:57:44.400 align:start position:0% unless our first class but one thing 01:57:44.400 --> 01:57:45.189 align:start position:0% unless our first class but one thing that's<01:57:44.639> not<01:57:44.880> for 01:57:45.189 --> 01:57:45.199 align:start position:0% that's not for 01:57:45.199 --> 01:57:47.510 align:start position:0% that's not for first<01:57:45.440> class<01:57:45.679> is<01:57:45.760> the<01:57:45.920> lexical<01:57:46.400> environment 01:57:47.510 --> 01:57:47.520 align:start position:0% first class is the lexical environment 01:57:47.520 --> 01:57:48.310 align:start position:0% first class is the lexical environment which<01:57:47.760> is<01:57:47.840> that 01:57:48.310 --> 01:57:48.320 align:start position:0% which is that 01:57:48.320 --> 01:57:50.229 align:start position:0% which is that inside<01:57:48.719> a<01:57:48.800> function<01:57:49.280> you<01:57:49.440> don't<01:57:49.599> have<01:57:49.840> access 01:57:50.229 --> 01:57:50.239 align:start position:0% inside a function you don't have access 01:57:50.239 --> 01:57:52.709 align:start position:0% inside a function you don't have access to<01:57:50.400> that<01:57:50.639> function's<01:57:51.199> lexical<01:57:51.760> scope 01:57:52.709 --> 01:57:52.719 align:start position:0% to that function's lexical scope 01:57:52.719 --> 01:57:55.030 align:start position:0% to that function's lexical scope that's<01:57:52.960> all<01:57:53.119> been<01:57:53.280> compiled<01:57:53.760> away<01:57:54.719> into 01:57:55.030 --> 01:57:55.040 align:start position:0% that's all been compiled away into 01:57:55.040 --> 01:57:56.629 align:start position:0% that's all been compiled away into identifiers<01:57:55.760> that<01:57:55.840> are<01:57:56.000> gone<01:57:56.239> by<01:57:56.400> the<01:57:56.480> time 01:57:56.629 --> 01:57:56.639 align:start position:0% identifiers that are gone by the time 01:57:56.639 --> 01:57:57.910 align:start position:0% identifiers that are gone by the time your<01:57:56.800> function<01:57:57.119> actually<01:57:57.440> runs 01:57:57.910 --> 01:57:57.920 align:start position:0% your function actually runs 01:57:57.920 --> 01:57:59.030 align:start position:0% your function actually runs so<01:57:58.159> this<01:57:58.239> is<01:57:58.320> something<01:57:58.560> the<01:57:58.639> compiler 01:57:59.030 --> 01:57:59.040 align:start position:0% so this is something the compiler 01:57:59.040 --> 01:58:01.669 align:start position:0% so this is something the compiler manages<01:57:59.440> for<01:57:59.679> you<01:57:59.840> at<01:57:59.920> compile<01:58:00.320> time 01:58:01.669 --> 01:58:01.679 align:start position:0% manages for you at compile time 01:58:01.679 --> 01:58:03.910 align:start position:0% manages for you at compile time but<01:58:01.920> in<01:58:02.159> r<01:58:02.719> the<01:58:02.880> environ<01:58:03.440> the<01:58:03.520> runtime 01:58:03.910 --> 01:58:03.920 align:start position:0% but in r the environ the runtime 01:58:03.920 --> 01:58:05.430 align:start position:0% but in r the environ the runtime environment<01:58:04.400> of<01:58:04.480> a<01:58:04.560> function 01:58:05.430 --> 01:58:05.440 align:start position:0% environment of a function 01:58:05.440 --> 01:58:07.669 align:start position:0% environment of a function is<01:58:05.679> attached<01:58:06.000> to<01:58:06.080> the<01:58:06.159> function<01:58:06.480> object<01:58:07.520> and 01:58:07.669 --> 01:58:07.679 align:start position:0% is attached to the function object and 01:58:07.679 --> 01:58:08.709 align:start position:0% is attached to the function object and you<01:58:07.840> can<01:58:08.000> actually 01:58:08.709 --> 01:58:08.719 align:start position:0% you can actually 01:58:08.719 --> 01:58:10.470 align:start position:0% you can actually look<01:58:08.960> at<01:58:09.119> the<01:58:09.280> variable<01:58:09.760> the<01:58:10.000> lexical 01:58:10.470 --> 01:58:10.480 align:start position:0% look at the variable the lexical 01:58:10.480 --> 01:58:12.149 align:start position:0% look at the variable the lexical variables<01:58:10.960> inside<01:58:11.280> a<01:58:11.360> function<01:58:11.760> like<01:58:12.000> from 01:58:12.149 --> 01:58:12.159 align:start position:0% variables inside a function like from 01:58:12.159 --> 01:58:13.030 align:start position:0% variables inside a function like from the<01:58:12.239> reply 01:58:13.030 --> 01:58:13.040 align:start position:0% the reply 01:58:13.040 --> 01:58:15.750 align:start position:0% the reply and<01:58:13.199> even<01:58:13.440> modify<01:58:13.840> them<01:58:14.639> so<01:58:14.800> like<01:58:15.040> if<01:58:15.360> inside<01:58:15.679> a 01:58:15.750 --> 01:58:15.760 align:start position:0% and even modify them so like if inside a 01:58:15.760 --> 01:58:17.109 align:start position:0% and even modify them so like if inside a function<01:58:16.080> body<01:58:16.400> there's<01:58:16.639> imagine<01:58:16.960> like 01:58:17.109 --> 01:58:17.119 align:start position:0% function body there's imagine like 01:58:17.119 --> 01:58:18.470 align:start position:0% function body there's imagine like there's<01:58:17.280> a<01:58:17.360> let<01:58:17.599> binding 01:58:18.470 --> 01:58:18.480 align:start position:0% there's a let binding 01:58:18.480 --> 01:58:20.709 align:start position:0% there's a let binding and<01:58:19.280> the<01:58:19.440> outermost<01:58:20.000> let<01:58:20.239> in<01:58:20.320> the<01:58:20.400> function 01:58:20.709 --> 01:58:20.719 align:start position:0% and the outermost let in the function 01:58:20.719 --> 01:58:22.470 align:start position:0% and the outermost let in the function binding<01:58:21.040> says<01:58:21.280> x1<01:58:21.840> and<01:58:21.920> then<01:58:22.080> there's<01:58:22.239> a<01:58:22.320> bunch 01:58:22.470 --> 01:58:22.480 align:start position:0% binding says x1 and then there's a bunch 01:58:22.480 --> 01:58:23.589 align:start position:0% binding says x1 and then there's a bunch of<01:58:22.560> stuff 01:58:23.589 --> 01:58:23.599 align:start position:0% of stuff 01:58:23.599 --> 01:58:26.709 align:start position:0% of stuff in<01:58:23.840> r<01:58:24.159> you<01:58:24.239> can<01:58:24.400> do<01:58:24.560> the<01:58:24.719> moral<01:58:25.040> equivalent<01:58:25.679> of 01:58:26.709 --> 01:58:26.719 align:start position:0% in r you can do the moral equivalent of 01:58:26.719 --> 01:58:28.629 align:start position:0% in r you can do the moral equivalent of after<01:58:27.040> that<01:58:27.199> function<01:58:27.520> has<01:58:27.679> been<01:58:27.840> defined<01:58:28.480> go 01:58:28.629 --> 01:58:28.639 align:start position:0% after that function has been defined go 01:58:28.639 --> 01:58:30.390 align:start position:0% after that function has been defined go in<01:58:28.800> there<01:58:29.520> mutate 01:58:30.390 --> 01:58:30.400 align:start position:0% in there mutate 01:58:30.400 --> 01:58:34.629 align:start position:0% in there mutate its<01:58:30.719> environ<01:58:31.280> internal<01:58:31.800> environment<01:58:32.960> um 01:58:34.629 --> 01:58:34.639 align:start position:0% its environ internal environment um 01:58:34.639 --> 01:58:38.070 align:start position:0% its environ internal environment um which<01:58:35.040> uh<01:58:36.480> you<01:58:36.560> know<01:58:36.719> again<01:58:37.119> pretty<01:58:37.360> egregious 01:58:38.070 --> 01:58:38.080 align:start position:0% which uh you know again pretty egregious 01:58:38.080 --> 01:58:39.669 align:start position:0% which uh you know again pretty egregious from<01:58:38.239> the<01:58:38.320> closure<01:58:38.719> functional<01:58:39.040> perspective 01:58:39.669 --> 01:58:39.679 align:start position:0% from the closure functional perspective 01:58:39.679 --> 01:58:41.350 align:start position:0% from the closure functional perspective i<01:58:39.760> think<01:58:40.000> that's<01:58:40.239> possible 01:58:41.350 --> 01:58:41.360 align:start position:0% i think that's possible 01:58:41.360 --> 01:58:43.990 align:start position:0% i think that's possible but<01:58:42.239> uh<01:58:42.560> it<01:58:42.719> also<01:58:42.960> gives<01:58:43.199> you<01:58:43.280> a<01:58:43.360> level<01:58:43.679> of<01:58:43.760> meta 01:58:43.990 --> 01:58:44.000 align:start position:0% but uh it also gives you a level of meta 01:58:44.000 --> 01:58:45.270 align:start position:0% but uh it also gives you a level of meta programming<01:58:44.480> capability 01:58:45.270 --> 01:58:45.280 align:start position:0% programming capability 01:58:45.280 --> 01:58:48.629 align:start position:0% programming capability that<01:58:45.599> is<01:58:46.000> i<01:58:46.080> think<01:58:46.840> unparalleled<01:58:47.760> uh 01:58:48.629 --> 01:58:48.639 align:start position:0% that is i think unparalleled uh 01:58:48.639 --> 01:58:51.669 align:start position:0% that is i think unparalleled uh except<01:58:48.960> by<01:58:49.199> other<01:58:49.440> lips<01:58:50.320> so 01:58:51.669 --> 01:58:51.679 align:start position:0% except by other lips so 01:58:51.679 --> 01:58:56.149 align:start position:0% except by other lips so um<01:58:52.719> very<01:58:53.040> very<01:58:53.199> interesting<01:58:53.599> language<01:58:54.320> um 01:58:56.149 --> 01:58:56.159 align:start position:0% um very very interesting language um 01:58:56.159 --> 01:59:00.149 align:start position:0% um very very interesting language um and<01:58:56.719> i<01:58:56.880> think<01:58:57.280> you<01:58:57.440> know<01:58:59.040> the<01:58:59.280> the<01:58:59.440> reason 01:59:00.149 --> 01:59:00.159 align:start position:0% and i think you know the the reason 01:59:00.159 --> 01:59:02.550 align:start position:0% and i think you know the the reason that<01:59:00.480> f<01:59:00.719> expert<01:59:01.040> thing<01:59:01.199> did<01:59:01.440> exist<01:59:01.760> in<01:59:02.239> lisps 01:59:02.550 --> 01:59:02.560 align:start position:0% that f expert thing did exist in lisps 01:59:02.560 --> 01:59:03.990 align:start position:0% that f expert thing did exist in lisps for<01:59:02.719> decades<01:59:03.119> before<01:59:03.360> common<01:59:03.599> list<01:59:03.840> and<01:59:03.920> i 01:59:03.990 --> 01:59:04.000 align:start position:0% for decades before common list and i 01:59:04.000 --> 01:59:05.270 align:start position:0% for decades before common list and i think<01:59:04.080> it<01:59:04.159> was<01:59:04.320> thrown<01:59:04.560> out<01:59:04.639> for<01:59:04.800> performance 01:59:05.270 --> 01:59:05.280 align:start position:0% think it was thrown out for performance 01:59:05.280 --> 01:59:06.629 align:start position:0% think it was thrown out for performance reasons 01:59:06.629 --> 01:59:06.639 align:start position:0% reasons 01:59:06.639 --> 01:59:08.229 align:start position:0% reasons long<01:59:06.880> before<01:59:07.199> common<01:59:07.520> list<01:59:07.840> came<01:59:08.000> to<01:59:08.080> be 01:59:08.229 --> 01:59:08.239 align:start position:0% long before common list came to be 01:59:08.239 --> 01:59:10.149 align:start position:0% long before common list came to be standardized<01:59:09.440> um 01:59:10.149 --> 01:59:10.159 align:start position:0% standardized um 01:59:10.159 --> 01:59:11.750 align:start position:0% standardized um but<01:59:10.560> one<01:59:10.800> thing<01:59:10.960> that<01:59:11.280> this<01:59:11.440> is<01:59:11.520> kind<01:59:11.679> of 01:59:11.750 --> 01:59:11.760 align:start position:0% but one thing that this is kind of 01:59:11.760 --> 01:59:13.750 align:start position:0% but one thing that this is kind of another<01:59:12.000> observation<01:59:12.480> i<01:59:12.560> have<01:59:12.800> is<01:59:12.880> that 01:59:13.750 --> 01:59:13.760 align:start position:0% another observation i have is that 01:59:13.760 --> 01:59:16.950 align:start position:0% another observation i have is that um<01:59:15.440> there's<01:59:15.679> a<01:59:15.760> concept<01:59:16.080> of<01:59:16.239> computer 01:59:16.950 --> 01:59:16.960 align:start position:0% um there's a concept of computer 01:59:16.960 --> 01:59:18.229 align:start position:0% um there's a concept of computer performance<01:59:17.440> and<01:59:17.599> there's<01:59:17.760> a<01:59:17.840> concept<01:59:18.159> of 01:59:18.229 --> 01:59:18.239 align:start position:0% performance and there's a concept of 01:59:18.239 --> 01:59:20.229 align:start position:0% performance and there's a concept of human<01:59:18.560> performance<01:59:19.840> and 01:59:20.229 --> 01:59:20.239 align:start position:0% human performance and 01:59:20.239 --> 01:59:22.470 align:start position:0% human performance and it's<01:59:20.480> okay<01:59:21.360> for<01:59:21.520> something<01:59:21.840> to<01:59:22.000> have<01:59:22.239> very 01:59:22.470 --> 01:59:22.480 align:start position:0% it's okay for something to have very 01:59:22.480 --> 01:59:24.470 align:start position:0% it's okay for something to have very poor<01:59:22.800> computer<01:59:23.199> performance 01:59:24.470 --> 01:59:24.480 align:start position:0% poor computer performance 01:59:24.480 --> 01:59:26.390 align:start position:0% poor computer performance if<01:59:24.719> it<01:59:24.960> unlocks<01:59:25.520> some<01:59:25.760> kind<01:59:25.920> of<01:59:26.080> human 01:59:26.390 --> 01:59:26.400 align:start position:0% if it unlocks some kind of human 01:59:26.400 --> 01:59:28.149 align:start position:0% if it unlocks some kind of human performance<01:59:27.040> because 01:59:28.149 --> 01:59:28.159 align:start position:0% performance because 01:59:28.159 --> 01:59:30.550 align:start position:0% performance because yes<01:59:28.960> our<01:59:29.440> relatives<01:59:29.920> are<01:59:30.080> things<01:59:30.320> kind<01:59:30.480> of 01:59:30.550 --> 01:59:30.560 align:start position:0% yes our relatives are things kind of 01:59:30.560 --> 01:59:31.750 align:start position:0% yes our relatives are things kind of slow<01:59:30.880> because<01:59:31.119> of<01:59:31.199> this<01:59:31.280> first<01:59:31.520> class 01:59:31.750 --> 01:59:31.760 align:start position:0% slow because of this first class 01:59:31.760 --> 01:59:33.030 align:start position:0% slow because of this first class environments<01:59:32.239> thing 01:59:33.030 --> 01:59:33.040 align:start position:0% environments thing 01:59:33.040 --> 01:59:34.950 align:start position:0% environments thing but<01:59:33.360> you<01:59:33.440> can<01:59:33.679> use<01:59:33.920> it<01:59:34.000> to<01:59:34.159> make<01:59:34.320> a<01:59:34.480> really<01:59:34.719> nice 01:59:34.950 --> 01:59:34.960 align:start position:0% but you can use it to make a really nice 01:59:34.960 --> 01:59:36.790 align:start position:0% but you can use it to make a really nice dsl<01:59:35.679> on<01:59:35.840> top<01:59:36.080> of<01:59:36.159> something<01:59:36.400> that's<01:59:36.560> written 01:59:36.790 --> 01:59:36.800 align:start position:0% dsl on top of something that's written 01:59:36.800 --> 01:59:37.350 align:start position:0% dsl on top of something that's written in<01:59:36.880> c 01:59:37.350 --> 01:59:37.360 align:start position:0% in c 01:59:37.360 --> 01:59:41.350 align:start position:0% in c plus<01:59:37.679> for<01:59:37.840> example<01:59:39.199> so<01:59:39.679> it<01:59:40.000> gives<01:59:40.320> you 01:59:41.350 --> 01:59:41.360 align:start position:0% plus for example so it gives you 01:59:41.360 --> 01:59:45.669 align:start position:0% plus for example so it gives you a<01:59:43.119> testbed<01:59:43.760> in<01:59:43.840> which<01:59:44.080> to<01:59:44.239> prototype 01:59:45.669 --> 01:59:45.679 align:start position:0% a testbed in which to prototype 01:59:45.679 --> 01:59:48.310 align:start position:0% a testbed in which to prototype uh<01:59:46.960> constructs<01:59:47.520> and<01:59:47.679> semantics<01:59:48.080> that<01:59:48.239> are 01:59:48.310 --> 01:59:48.320 align:start position:0% uh constructs and semantics that are 01:59:48.320 --> 01:59:49.990 align:start position:0% uh constructs and semantics that are valuable<01:59:48.719> to<01:59:48.880> people 01:59:49.990 --> 01:59:50.000 align:start position:0% valuable to people 01:59:50.000 --> 01:59:52.870 align:start position:0% valuable to people and<01:59:50.159> then<01:59:50.639> later<01:59:51.360> if<01:59:51.520> at<01:59:51.679> all<01:59:52.239> you<01:59:52.560> have<01:59:52.800> a 01:59:52.870 --> 01:59:52.880 align:start position:0% and then later if at all you have a 01:59:52.880 --> 01:59:54.229 align:start position:0% and then later if at all you have a layer<01:59:53.199> on<01:59:53.280> which<01:59:53.440> you<01:59:53.599> can<01:59:53.679> make<01:59:53.840> those<01:59:54.000> things 01:59:54.229 --> 01:59:54.239 align:start position:0% layer on which you can make those things 01:59:54.239 --> 01:59:56.390 align:start position:0% layer on which you can make those things more<01:59:54.400> efficient 01:59:56.390 --> 01:59:56.400 align:start position:0% more efficient 01:59:56.400 --> 01:59:58.310 align:start position:0% more efficient and<01:59:56.480> it<01:59:56.639> makes<01:59:56.800> me<01:59:57.040> regret<01:59:57.440> that<01:59:57.599> not<01:59:57.760> adding<01:59:58.080> r 01:59:58.310 --> 01:59:58.320 align:start position:0% and it makes me regret that not adding r 01:59:58.320 --> 01:59:59.990 align:start position:0% and it makes me regret that not adding r to<01:59:58.480> my<01:59:58.639> little<01:59:58.880> platform<01:59:59.360> and<01:59:59.440> abstraction 01:59:59.990 --> 02:00:00.000 align:start position:0% to my little platform and abstraction 02:00:00.000 --> 02:00:01.109 align:start position:0% to my little platform and abstraction level 02:00:01.109 --> 02:00:01.119 align:start position:0% level 02:00:01.119 --> 02:00:02.709 align:start position:0% level chart<02:00:01.520> like<02:00:01.679> that's<02:00:01.840> sort<02:00:02.000> of<02:00:02.080> a<02:00:02.159> bar<02:00:02.400> chart 02:00:02.709 --> 02:00:02.719 align:start position:0% chart like that's sort of a bar chart 02:00:02.719 --> 02:00:04.550 align:start position:0% chart like that's sort of a bar chart really<02:00:03.520> um 02:00:04.550 --> 02:00:04.560 align:start position:0% really um 02:00:04.560 --> 02:00:07.669 align:start position:0% really um you<02:00:04.719> know<02:00:05.199> r<02:00:06.239> sits<02:00:06.639> even<02:00:06.880> higher<02:00:07.119> than<02:00:07.280> closure 02:00:07.669 --> 02:00:07.679 align:start position:0% you know r sits even higher than closure 02:00:07.679 --> 02:00:08.470 align:start position:0% you know r sits even higher than closure maybe 02:00:08.470 --> 02:00:08.480 align:start position:0% maybe 02:00:08.480 --> 02:00:12.070 align:start position:0% maybe on<02:00:08.639> the<02:00:08.880> on<02:00:09.119> or<02:00:09.280> well<02:00:09.760> i<02:00:09.840> guess<02:00:10.080> it's<02:00:10.840> a<02:00:11.920> it's 02:00:12.070 --> 02:00:12.080 align:start position:0% on the on or well i guess it's a it's 02:00:12.080 --> 02:00:13.270 align:start position:0% on the on or well i guess it's a it's complicated<02:00:12.560> i<02:00:12.639> have<02:00:12.719> to<02:00:12.800> think<02:00:12.960> about<02:00:13.119> that 02:00:13.270 --> 02:00:13.280 align:start position:0% complicated i have to think about that 02:00:13.280 --> 02:00:13.830 align:start position:0% complicated i have to think about that more 02:00:13.830 --> 02:00:13.840 align:start position:0% more 02:00:13.840 --> 02:00:17.030 align:start position:0% more but<02:00:14.159> um<02:00:15.520> it<02:00:15.760> too<02:00:16.000> offers<02:00:16.560> semantic 02:00:17.030 --> 02:00:17.040 align:start position:0% but um it too offers semantic 02:00:17.040 --> 02:00:19.109 align:start position:0% but um it too offers semantic affordances<02:00:17.679> at<02:00:17.760> a<02:00:17.840> very<02:00:18.080> high<02:00:18.239> level 02:00:19.109 --> 02:00:19.119 align:start position:0% affordances at a very high level 02:00:19.119 --> 02:00:21.030 align:start position:0% affordances at a very high level and<02:00:19.599> there<02:00:19.760> are<02:00:19.920> trade-offs<02:00:20.400> with<02:00:20.719> the<02:00:20.800> ones 02:00:21.030 --> 02:00:21.040 align:start position:0% and there are trade-offs with the ones 02:00:21.040 --> 02:00:22.149 align:start position:0% and there are trade-offs with the ones it<02:00:21.119> does<02:00:21.360> offer 02:00:22.149 --> 02:00:22.159 align:start position:0% it does offer 02:00:22.159 --> 02:00:24.310 align:start position:0% it does offer and<02:00:22.400> it<02:00:22.560> occupies<02:00:23.040> a<02:00:23.119> unique<02:00:23.760> like<02:00:23.920> closure 02:00:24.310 --> 02:00:24.320 align:start position:0% and it occupies a unique like closure 02:00:24.320 --> 02:00:26.790 align:start position:0% and it occupies a unique like closure occupies<02:00:24.880> a<02:00:25.280> point<02:00:25.840> in<02:00:26.000> the<02:00:26.080> design<02:00:26.400> space 02:00:26.790 --> 02:00:26.800 align:start position:0% occupies a point in the design space 02:00:26.800 --> 02:00:28.629 align:start position:0% occupies a point in the design space that<02:00:26.960> has<02:00:27.280> benefits<02:00:27.760> for<02:00:27.920> people<02:00:28.159> who<02:00:28.400> do<02:00:28.560> a 02:00:28.629 --> 02:00:28.639 align:start position:0% that has benefits for people who do a 02:00:28.639 --> 02:00:29.910 align:start position:0% that has benefits for people who do a certain<02:00:28.880> kind<02:00:28.960> of<02:00:29.040> thing<02:00:29.280> or<02:00:29.440> like<02:00:29.599> a<02:00:29.679> certain 02:00:29.910 --> 02:00:29.920 align:start position:0% certain kind of thing or like a certain 02:00:29.920 --> 02:00:33.030 align:start position:0% certain kind of thing or like a certain kind<02:00:30.080> of<02:00:30.159> thing 02:00:33.030 --> 02:00:33.040 align:start position:0% 02:00:33.040 --> 02:00:36.550 align:start position:0% yeah<02:00:33.440> i<02:00:33.520> still<02:00:33.760> really<02:00:33.920> like<02:00:34.159> it<02:00:34.320> and 02:00:36.550 --> 02:00:36.560 align:start position:0% 02:00:36.560 --> 02:00:39.109 align:start position:0% i<02:00:37.119> uh<02:00:37.840> i<02:00:38.000> enjoyed<02:00:38.320> the<02:00:38.400> process<02:00:38.719> of<02:00:38.800> learning 02:00:39.109 --> 02:00:39.119 align:start position:0% i uh i enjoyed the process of learning 02:00:39.119 --> 02:00:40.149 align:start position:0% i uh i enjoyed the process of learning it<02:00:39.280> it<02:00:39.360> also<02:00:39.840> it 02:00:40.149 --> 02:00:40.159 align:start position:0% it it also it 02:00:40.159 --> 02:00:42.070 align:start position:0% it it also it also<02:00:40.400> light<02:00:40.560> closure<02:00:40.960> is<02:00:41.119> significantly 02:00:42.070 --> 02:00:42.080 align:start position:0% also light closure is significantly 02:00:42.080 --> 02:00:43.589 align:start position:0% also light closure is significantly influenced<02:00:42.480> by<02:00:42.639> common<02:00:42.960> lisp 02:00:43.589 --> 02:00:43.599 align:start position:0% influenced by common lisp 02:00:43.599 --> 02:00:46.950 align:start position:0% influenced by common lisp which<02:00:43.840> is<02:00:44.000> fun<02:00:45.119> so<02:00:45.360> it's<02:00:45.520> kind<02:00:45.679> of<02:00:45.840> a<02:00:46.480> sibling 02:00:46.950 --> 02:00:46.960 align:start position:0% which is fun so it's kind of a sibling 02:00:46.960 --> 02:00:54.550 align:start position:0% which is fun so it's kind of a sibling to<02:00:47.119> closure<02:00:47.440> in<02:00:47.520> that<02:00:52.840> way<02:00:53.920> with<02:00:54.159> that 02:00:54.550 --> 02:00:54.560 align:start position:0% to closure in that way with that 02:00:54.560 --> 02:00:57.510 align:start position:0% to closure in that way with that i<02:00:54.639> think<02:00:54.880> i<02:00:54.960> shall<02:00:55.840> leave<02:00:56.159> you<02:00:56.239> fine<02:00:56.480> people<02:00:57.360> do 02:00:57.510 --> 02:00:57.520 align:start position:0% i think i shall leave you fine people do 02:00:57.520 --> 02:00:58.550 align:start position:0% i think i shall leave you fine people do your<02:00:57.679> own<02:00:57.840> programming 02:00:58.550 --> 02:00:58.560 align:start position:0% your own programming 02:00:58.560 --> 02:01:00.950 align:start position:0% your own programming that<02:00:58.800> was<02:00:58.960> a<02:00:59.040> phenomenal<02:00:59.679> talk<02:01:00.400> thank<02:01:00.560> you<02:01:00.719> so 02:01:00.950 --> 02:01:00.960 align:start position:0% that was a phenomenal talk thank you so 02:01:00.960 --> 02:01:02.870 align:start position:0% that was a phenomenal talk thank you so much 02:01:02.870 --> 02:01:02.880 align:start position:0% much 02:01:02.880 --> 02:01:05.510 align:start position:0% much thank<02:01:03.119> you<02:01:03.199> everyone<02:01:04.719> yep<02:01:05.040> thank<02:01:05.199> you<02:01:05.440> i 02:01:05.510 --> 02:01:05.520 align:start position:0% thank you everyone yep thank you i 02:01:05.520 --> 02:01:06.149 align:start position:0% thank you everyone yep thank you i enjoyed<02:01:05.840> that 02:01:06.149 --> 02:01:06.159 align:start position:0% enjoyed that 02:01:06.159 --> 02:01:07.589 align:start position:0% enjoyed that you're<02:01:06.400> very<02:01:06.560> welcome<02:01:06.960> yeah<02:01:07.199> thank<02:01:07.360> you<02:01:07.440> so 02:01:07.589 --> 02:01:07.599 align:start position:0% you're very welcome yeah thank you so 02:01:07.599 --> 02:01:09.270 align:start position:0% you're very welcome yeah thank you so much<02:01:07.760> for<02:01:07.920> coming<02:01:08.239> and<02:01:08.480> uh<02:01:08.639> yeah<02:01:08.880> i'll 02:01:09.270 --> 02:01:09.280 align:start position:0% much for coming and uh yeah i'll 02:01:09.280 --> 02:01:11.990 align:start position:0% much for coming and uh yeah i'll i'll<02:01:09.520> send<02:01:09.679> the<02:01:09.760> slides<02:01:10.159> to<02:01:10.239> the<02:01:10.320> daniels<02:01:11.679> and 02:01:11.990 --> 02:01:12.000 align:start position:0% i'll send the slides to the daniels and 02:01:12.000 --> 02:01:13.189 align:start position:0% i'll send the slides to the daniels and um 02:01:13.189 --> 02:01:13.199 align:start position:0% um 02:01:13.199 --> 02:01:14.229 align:start position:0% um and<02:01:13.280> there's<02:01:13.440> links<02:01:13.679> on<02:01:13.760> there<02:01:13.920> on<02:01:14.000> how<02:01:14.159> to 02:01:14.229 --> 02:01:14.239 align:start position:0% and there's links on there on how to 02:01:14.239 --> 02:01:15.750 align:start position:0% and there's links on there on how to contact<02:01:14.560> me<02:01:14.800> and<02:01:14.960> stuff<02:01:15.119> to<02:01:15.280> look<02:01:15.440> at<02:01:15.520> and<02:01:15.599> so 02:01:15.750 --> 02:01:15.760 align:start position:0% contact me and stuff to look at and so 02:01:15.760 --> 02:01:17.189 align:start position:0% contact me and stuff to look at and so forth<02:01:16.080> but<02:01:16.320> uh 02:01:17.189 --> 02:01:17.199 align:start position:0% forth but uh 02:01:17.199 --> 02:01:19.350 align:start position:0% forth but uh uh<02:01:17.520> yeah<02:01:17.679> thanks<02:01:17.920> for<02:01:18.080> coming<02:01:18.960> thanks<02:01:19.280> for 02:01:19.350 --> 02:01:19.360 align:start position:0% uh yeah thanks for coming thanks for 02:01:19.360 --> 02:01:22.080 align:start position:0% uh yeah thanks for coming thanks for watching