WEBVTT Kind: captions Language: en 00:00:01.970 --> 00:00:04.760 align:start position:0% hi<00:00:02.970> everybody<00:00:03.210> my<00:00:03.540> name<00:00:03.810> is<00:00:03.959> Alan<00:00:04.319> diapered 00:00:04.760 --> 00:00:04.770 align:start position:0% hi everybody my name is Alan diapered 00:00:04.770 --> 00:00:06.369 align:start position:0% hi everybody my name is Alan diapered and<00:00:04.980> I'll<00:00:05.370> be<00:00:05.520> talking<00:00:05.730> today<00:00:06.029> about 00:00:06.369 --> 00:00:06.379 align:start position:0% and I'll be talking today about 00:00:06.379 --> 00:00:09.440 align:start position:0% and I'll be talking today about JavaScript<00:00:07.379> assisted<00:00:08.010> common<00:00:08.700> lisp<00:00:09.030> or<00:00:09.240> as<00:00:09.360> I 00:00:09.440 --> 00:00:09.450 align:start position:0% JavaScript assisted common lisp or as I 00:00:09.450 --> 00:00:12.709 align:start position:0% JavaScript assisted common lisp or as I like<00:00:09.570> to<00:00:09.750> call<00:00:09.990> it<00:00:10.050> jackal<00:00:11.010> the<00:00:11.849> jackal<00:00:12.269> is<00:00:12.450> a 00:00:12.709 --> 00:00:12.719 align:start position:0% like to call it jackal the jackal is a 00:00:12.719 --> 00:00:14.749 align:start position:0% like to call it jackal the jackal is a new<00:00:13.200> Common<00:00:13.620> Lisp<00:00:13.650> implementation<00:00:14.610> that 00:00:14.749 --> 00:00:14.759 align:start position:0% new Common Lisp implementation that 00:00:14.759 --> 00:00:21.050 align:start position:0% new Common Lisp implementation that targets<00:00:15.240> the<00:00:15.450> JavaScript<00:00:16.049> platform<00:00:20.060> my 00:00:21.050 --> 00:00:21.060 align:start position:0% targets the JavaScript platform my 00:00:21.060 --> 00:00:24.370 align:start position:0% targets the JavaScript platform my agenda<00:00:21.660> consists<00:00:22.140> of<00:00:22.230> three<00:00:22.890> major<00:00:23.580> topics 00:00:24.370 --> 00:00:24.380 align:start position:0% agenda consists of three major topics 00:00:24.380 --> 00:00:26.420 align:start position:0% agenda consists of three major topics first<00:00:25.380> of<00:00:25.529> all<00:00:25.619> I'd<00:00:25.710> like<00:00:25.769> to<00:00:25.859> set<00:00:26.130> the<00:00:26.250> scene 00:00:26.420 --> 00:00:26.430 align:start position:0% first of all I'd like to set the scene 00:00:26.430 --> 00:00:28.700 align:start position:0% first of all I'd like to set the scene for<00:00:26.460> you<00:00:26.939> to<00:00:27.449> give<00:00:27.570> you<00:00:27.660> a<00:00:27.720> little<00:00:27.930> context<00:00:28.500> and 00:00:28.700 --> 00:00:28.710 align:start position:0% for you to give you a little context and 00:00:28.710 --> 00:00:30.019 align:start position:0% for you to give you a little context and background<00:00:28.859> that<00:00:29.550> could<00:00:29.789> help<00:00:29.910> you 00:00:30.019 --> 00:00:30.029 align:start position:0% background that could help you 00:00:30.029 --> 00:00:31.790 align:start position:0% background that could help you understand<00:00:30.480> jackal<00:00:30.960> and<00:00:31.109> determine<00:00:31.650> whether 00:00:31.790 --> 00:00:31.800 align:start position:0% understand jackal and determine whether 00:00:31.800 --> 00:00:33.319 align:start position:0% understand jackal and determine whether or<00:00:31.890> not<00:00:32.009> it's<00:00:32.219> something<00:00:32.340> that's<00:00:33.090> applicable 00:00:33.319 --> 00:00:33.329 align:start position:0% or not it's something that's applicable 00:00:33.329 --> 00:00:36.530 align:start position:0% or not it's something that's applicable to<00:00:33.660> what<00:00:33.780> you<00:00:33.870> do<00:00:34.020> I<00:00:34.230> find<00:00:35.130> that<00:00:35.420> projects<00:00:36.420> are 00:00:36.530 --> 00:00:36.540 align:start position:0% to what you do I find that projects are 00:00:36.540 --> 00:00:39.350 align:start position:0% to what you do I find that projects are much<00:00:36.630> easier<00:00:36.690> to<00:00:37.020> understand<00:00:37.559> if<00:00:38.300> there's<00:00:39.300> a 00:00:39.350 --> 00:00:39.360 align:start position:0% much easier to understand if there's a 00:00:39.360 --> 00:00:41.360 align:start position:0% much easier to understand if there's a if<00:00:39.629> if<00:00:40.079> you<00:00:40.200> have<00:00:40.350> a<00:00:40.379> little<00:00:40.530> background<00:00:40.860> about 00:00:41.360 --> 00:00:41.370 align:start position:0% if if you have a little background about 00:00:41.370 --> 00:00:42.979 align:start position:0% if if you have a little background about why<00:00:41.730> that<00:00:42.030> project<00:00:42.420> came<00:00:42.570> to<00:00:42.690> be<00:00:42.780> and<00:00:42.930> what 00:00:42.979 --> 00:00:42.989 align:start position:0% why that project came to be and what 00:00:42.989 --> 00:00:44.990 align:start position:0% why that project came to be and what motivated<00:00:43.469> it<00:00:43.680> what<00:00:43.860> experience<00:00:44.309> experience 00:00:44.990 --> 00:00:45.000 align:start position:0% motivated it what experience experience 00:00:45.000 --> 00:00:47.450 align:start position:0% motivated it what experience experience has<00:00:45.210> led<00:00:45.390> to<00:00:45.510> its<00:00:45.629> creation<00:00:46.110> and<00:00:46.379> in<00:00:46.620> this<00:00:47.219> part 00:00:47.450 --> 00:00:47.460 align:start position:0% has led to its creation and in this part 00:00:47.460 --> 00:00:49.250 align:start position:0% has led to its creation and in this part of<00:00:47.520> my<00:00:47.579> talk<00:00:47.670> all<00:00:48.059> hope<00:00:48.300> to<00:00:48.329> illuminate<00:00:49.079> that 00:00:49.250 --> 00:00:49.260 align:start position:0% of my talk all hope to illuminate that 00:00:49.260 --> 00:00:52.069 align:start position:0% of my talk all hope to illuminate that for<00:00:49.410> you<00:00:49.640> I'll<00:00:50.640> also<00:00:50.910> talk<00:00:51.180> about<00:00:51.239> the 00:00:52.069 --> 00:00:52.079 align:start position:0% for you I'll also talk about the 00:00:52.079 --> 00:00:53.540 align:start position:0% for you I'll also talk about the JavaScript<00:00:52.260> platform<00:00:52.949> and<00:00:53.219> why<00:00:53.430> I'm 00:00:53.540 --> 00:00:53.550 align:start position:0% JavaScript platform and why I'm 00:00:53.550 --> 00:00:55.639 align:start position:0% JavaScript platform and why I'm interested<00:00:54.000> in<00:00:54.120> it<00:00:54.270> what<00:00:55.050> it<00:00:55.140> can<00:00:55.260> do 00:00:55.639 --> 00:00:55.649 align:start position:0% interested in it what it can do 00:00:55.649 --> 00:00:58.119 align:start position:0% interested in it what it can do and<00:00:55.739> what<00:00:55.949> it's<00:00:56.070> not<00:00:56.129> what<00:00:56.370> it<00:00:56.460> can't<00:00:56.640> do<00:00:56.820> and 00:00:58.119 --> 00:00:58.129 align:start position:0% and what it's not what it can't do and 00:00:58.129 --> 00:01:03.009 align:start position:0% and what it's not what it can't do and set<00:00:59.129> the<00:00:59.280> stage<00:00:59.579> technically<00:01:00.920> for<00:01:01.920> jackal 00:01:03.009 --> 00:01:03.019 align:start position:0% set the stage technically for jackal 00:01:03.019 --> 00:01:06.289 align:start position:0% set the stage technically for jackal then<00:01:04.019> we'll<00:01:04.140> get<00:01:04.199> into<00:01:04.379> jackal<00:01:04.979> itself<00:01:05.299> its 00:01:06.289 --> 00:01:06.299 align:start position:0% then we'll get into jackal itself its 00:01:06.299 --> 00:01:08.750 align:start position:0% then we'll get into jackal itself its high-level<00:01:06.560> organization<00:01:07.560> the<00:01:08.369> features 00:01:08.750 --> 00:01:08.760 align:start position:0% high-level organization the features 00:01:08.760 --> 00:01:09.920 align:start position:0% high-level organization the features that<00:01:08.939> I<00:01:09.000> think<00:01:09.240> are<00:01:09.330> interesting<00:01:09.479> and 00:01:09.920 --> 00:01:09.930 align:start position:0% that I think are interesting and 00:01:09.930 --> 00:01:12.140 align:start position:0% that I think are interesting and important<00:01:10.320> and<00:01:10.439> the<00:01:11.400> parts<00:01:11.610> of<00:01:11.700> it<00:01:11.820> that<00:01:11.880> are 00:01:12.140 --> 00:01:12.150 align:start position:0% important and the parts of it that are 00:01:12.150 --> 00:01:15.710 align:start position:0% important and the parts of it that are maybe<00:01:12.330> speculative<00:01:14.150> finally<00:01:15.150> I'll<00:01:15.390> do<00:01:15.689> a 00:01:15.710 --> 00:01:15.720 align:start position:0% maybe speculative finally I'll do a 00:01:15.720 --> 00:01:17.960 align:start position:0% maybe speculative finally I'll do a little<00:01:15.960> demonstration<00:01:16.140> and<00:01:16.770> we<00:01:17.640> can<00:01:17.790> see 00:01:17.960 --> 00:01:17.970 align:start position:0% little demonstration and we can see 00:01:17.970 --> 00:01:20.270 align:start position:0% little demonstration and we can see jackal<00:01:18.390> in<00:01:18.479> the<00:01:18.570> browser<00:01:18.780> running<00:01:19.200> and<00:01:19.650> I'll 00:01:20.270 --> 00:01:20.280 align:start position:0% jackal in the browser running and I'll 00:01:20.280 --> 00:01:23.719 align:start position:0% jackal in the browser running and I'll also<00:01:20.460> show<00:01:20.990> jackals<00:01:21.990> repple<00:01:22.380> client<00:01:22.860> facility 00:01:23.719 --> 00:01:23.729 align:start position:0% also show jackals repple client facility 00:01:23.729 --> 00:01:25.490 align:start position:0% also show jackals repple client facility which<00:01:24.030> is<00:01:24.060> unkind<00:01:24.720> of<00:01:24.780> a<00:01:24.840> novel<00:01:25.140> thing<00:01:25.259> about 00:01:25.490 --> 00:01:25.500 align:start position:0% which is unkind of a novel thing about 00:01:25.500 --> 00:01:28.340 align:start position:0% which is unkind of a novel thing about jackal<00:01:26.600> because<00:01:27.600> it<00:01:27.780> involves<00:01:28.229> this 00:01:28.340 --> 00:01:28.350 align:start position:0% jackal because it involves this 00:01:28.350 --> 00:01:33.340 align:start position:0% jackal because it involves this asynchronous<00:01:28.790> reader<00:01:29.790> that<00:01:30.750> I'll<00:01:30.869> talk<00:01:31.020> about 00:01:33.340 --> 00:01:33.350 align:start position:0% 00:01:33.350 --> 00:01:36.649 align:start position:0% my<00:01:34.350> wrote<00:01:34.890> to<00:01:35.070> jackal<00:01:35.490> began<00:01:35.790> I<00:01:36.030> think<00:01:36.060> around 00:01:36.649 --> 00:01:36.659 align:start position:0% my wrote to jackal began I think around 00:01:36.659 --> 00:01:40.580 align:start position:0% my wrote to jackal began I think around 1994<00:01:37.470> I<00:01:37.740> was<00:01:38.700> learning<00:01:39.360> basic<00:01:39.869> at<00:01:39.990> the<00:01:40.079> time<00:01:40.290> I 00:01:40.580 --> 00:01:40.590 align:start position:0% 1994 I was learning basic at the time I 00:01:40.590 --> 00:01:45.280 align:start position:0% 1994 I was learning basic at the time I think<00:01:40.740> quick<00:01:41.040> basic<00:01:41.490> and<00:01:42.799> my<00:01:43.799> dad<00:01:44.310> who<00:01:45.000> was<00:01:45.119> a 00:01:45.280 --> 00:01:45.290 align:start position:0% think quick basic and my dad who was a 00:01:45.290 --> 00:01:47.719 align:start position:0% think quick basic and my dad who was a taught<00:01:46.290> me<00:01:46.409> programming<00:01:46.950> has<00:01:47.040> been<00:01:47.070> a<00:01:47.250> big 00:01:47.719 --> 00:01:47.729 align:start position:0% taught me programming has been a big 00:01:47.729 --> 00:01:49.520 align:start position:0% taught me programming has been a big inspiration<00:01:47.939> for<00:01:48.540> a<00:01:49.049> lot<00:01:49.079> of<00:01:49.259> things<00:01:49.380> that<00:01:49.470> I 00:01:49.520 --> 00:01:49.530 align:start position:0% inspiration for a lot of things that I 00:01:49.530 --> 00:01:53.149 align:start position:0% inspiration for a lot of things that I do<00:01:50.689> after<00:01:51.689> I<00:01:51.960> learned<00:01:52.200> about<00:01:52.290> arrays<00:01:52.680> he<00:01:52.950> said 00:01:53.149 --> 00:01:53.159 align:start position:0% do after I learned about arrays he said 00:01:53.159 --> 00:01:54.710 align:start position:0% do after I learned about arrays he said Allan<00:01:53.490> arrays<00:01:53.850> are<00:01:54.060> really<00:01:54.270> cool<00:01:54.360> aren't<00:01:54.630> they 00:01:54.710 --> 00:01:54.720 align:start position:0% Allan arrays are really cool aren't they 00:01:54.720 --> 00:01:56.959 align:start position:0% Allan arrays are really cool aren't they and<00:01:54.810> I<00:01:54.840> said<00:01:54.990> yeah<00:01:55.140> yeah<00:01:55.290> very<00:01:55.500> cool<00:01:55.680> and<00:01:55.969> he 00:01:56.959 --> 00:01:56.969 align:start position:0% and I said yeah yeah very cool and he 00:01:56.969 --> 00:01:58.880 align:start position:0% and I said yeah yeah very cool and he said<00:01:57.270> to<00:01:57.390> me<00:01:57.479> you<00:01:57.600> know<00:01:57.750> there's<00:01:58.649> a<00:01:58.710> whole 00:01:58.880 --> 00:01:58.890 align:start position:0% said to me you know there's a whole 00:01:58.890 --> 00:02:01.870 align:start position:0% said to me you know there's a whole language<00:01:59.210> oriented<00:02:00.210> around<00:02:00.329> the<00:02:00.570> idea<00:02:00.899> of 00:02:01.870 --> 00:02:01.880 align:start position:0% language oriented around the idea of 00:02:01.880 --> 00:02:05.600 align:start position:0% language oriented around the idea of arrays<00:02:02.880> and<00:02:03.689> I<00:02:04.680> distinctly<00:02:05.369> remember 00:02:05.600 --> 00:02:05.610 align:start position:0% arrays and I distinctly remember 00:02:05.610 --> 00:02:09.090 align:start position:0% arrays and I distinctly remember thinking<00:02:06.180> wow<00:02:06.390> that<00:02:06.960> sounds<00:02:07.350> so<00:02:07.590> dumb 00:02:09.090 --> 00:02:09.100 align:start position:0% thinking wow that sounds so dumb 00:02:09.100 --> 00:02:12.660 align:start position:0% thinking wow that sounds so dumb and<00:02:09.730> I'm<00:02:10.720> sure<00:02:10.930> he<00:02:11.200> laughed<00:02:11.860> a<00:02:12.070> little<00:02:12.190> scoffed 00:02:12.660 --> 00:02:12.670 align:start position:0% and I'm sure he laughed a little scoffed 00:02:12.670 --> 00:02:15.510 align:start position:0% and I'm sure he laughed a little scoffed and<00:02:12.940> brushed<00:02:13.150> aside<00:02:13.300> my<00:02:14.040> absolutely<00:02:15.040> ignorant 00:02:15.510 --> 00:02:15.520 align:start position:0% and brushed aside my absolutely ignorant 00:02:15.520 --> 00:02:19.200 align:start position:0% and brushed aside my absolutely ignorant comment<00:02:15.880> and<00:02:16.030> I<00:02:17.070> went<00:02:18.070> on<00:02:18.190> to<00:02:18.520> program<00:02:19.060> and<00:02:19.180> a 00:02:19.200 --> 00:02:19.210 align:start position:0% comment and I went on to program and a 00:02:19.210 --> 00:02:24.450 align:start position:0% comment and I went on to program and a few<00:02:19.390> other<00:02:19.510> kinds<00:02:19.810> of<00:02:19.840> languages<00:02:20.610> I<00:02:23.460> returned 00:02:24.450 --> 00:02:24.460 align:start position:0% few other kinds of languages I returned 00:02:24.460 --> 00:02:27.750 align:start position:0% few other kinds of languages I returned to<00:02:24.640> Lisp<00:02:24.970> in<00:02:25.240> a<00:02:25.330> big<00:02:25.480> way<00:02:25.720> with<00:02:26.290> in<00:02:26.650> 2009<00:02:27.370> when<00:02:27.730> I 00:02:27.750 --> 00:02:27.760 align:start position:0% to Lisp in a big way with in 2009 when I 00:02:27.760 --> 00:02:30.090 align:start position:0% to Lisp in a big way with in 2009 when I learned<00:02:28.000> about<00:02:28.060> closure<00:02:28.450> and<00:02:28.810> I<00:02:29.560> started<00:02:29.980> to 00:02:30.090 --> 00:02:30.100 align:start position:0% learned about closure and I started to 00:02:30.100 --> 00:02:33.150 align:start position:0% learned about closure and I started to use<00:02:30.340> closure<00:02:30.670> professionally<00:02:31.420> and<00:02:31.950> a<00:02:32.950> few 00:02:33.150 --> 00:02:33.160 align:start position:0% use closure professionally and a few 00:02:33.160 --> 00:02:35.790 align:start position:0% use closure professionally and a few years<00:02:33.340> after<00:02:33.460> that<00:02:33.790> I<00:02:34.330> was<00:02:34.600> involved<00:02:35.380> in<00:02:35.620> an 00:02:35.790 --> 00:02:35.800 align:start position:0% years after that I was involved in an 00:02:35.800 --> 00:02:37.140 align:start position:0% years after that I was involved in an effort<00:02:36.100> to<00:02:36.250> create<00:02:36.430> something<00:02:37.000> called 00:02:37.140 --> 00:02:37.150 align:start position:0% effort to create something called 00:02:37.150 --> 00:02:41.250 align:start position:0% effort to create something called closure<00:02:37.600> script<00:02:38.020> which<00:02:38.710> was<00:02:38.950> a<00:02:40.020> variant<00:02:41.020> of 00:02:41.250 --> 00:02:41.260 align:start position:0% closure script which was a variant of 00:02:41.260 --> 00:02:43.070 align:start position:0% closure script which was a variant of closure<00:02:41.590> that<00:02:41.920> compiled<00:02:42.460> to<00:02:42.820> JavaScript 00:02:43.070 --> 00:02:43.080 align:start position:0% closure that compiled to JavaScript 00:02:43.080 --> 00:02:46.500 align:start position:0% closure that compiled to JavaScript instead<00:02:44.080> of<00:02:44.380> to<00:02:44.620> the<00:02:44.650> JVM<00:02:45.220> but<00:02:46.210> still 00:02:46.500 --> 00:02:46.510 align:start position:0% instead of to the JVM but still 00:02:46.510 --> 00:02:49.010 align:start position:0% instead of to the JVM but still emphasizing<00:02:46.690> functional<00:02:47.620> programming 00:02:49.010 --> 00:02:49.020 align:start position:0% emphasizing functional programming 00:02:49.020 --> 00:02:52.260 align:start position:0% emphasizing functional programming closure<00:02:50.020> script<00:02:50.350> was<00:02:50.500> really<00:02:50.790> eye-opening<00:02:51.790> to 00:02:52.260 --> 00:02:52.270 align:start position:0% closure script was really eye-opening to 00:02:52.270 --> 00:02:54.990 align:start position:0% closure script was really eye-opening to me<00:02:52.300> in<00:02:52.480> a<00:02:52.540> couple<00:02:52.720> regards<00:02:53.640> first<00:02:54.640> of<00:02:54.760> all<00:02:54.880> it 00:02:54.990 --> 00:02:55.000 align:start position:0% me in a couple regards first of all it 00:02:55.000 --> 00:02:56.070 align:start position:0% me in a couple regards first of all it was<00:02:55.090> the<00:02:55.210> first<00:02:55.390> time<00:02:55.510> I<00:02:55.570> had<00:02:55.720> been<00:02:55.750> involved 00:02:56.070 --> 00:02:56.080 align:start position:0% was the first time I had been involved 00:02:56.080 --> 00:02:57.720 align:start position:0% was the first time I had been involved in<00:02:56.260> any<00:02:56.410> kind<00:02:56.620> of<00:02:56.650> compiler<00:02:57.100> development<00:02:57.610> and 00:02:57.720 --> 00:02:57.730 align:start position:0% in any kind of compiler development and 00:02:57.730 --> 00:02:58.980 align:start position:0% in any kind of compiler development and I<00:02:57.910> got<00:02:58.060> to<00:02:58.180> see<00:02:58.360> how<00:02:58.480> that<00:02:58.630> was<00:02:58.750> done 00:02:58.980 --> 00:02:58.990 align:start position:0% I got to see how that was done 00:02:58.990 --> 00:03:03.350 align:start position:0% I got to see how that was done that<00:02:59.440> was<00:02:59.530> really<00:02:59.710> interesting<00:03:00.010> and<00:03:01.500> maybe<00:03:02.500> my 00:03:03.350 --> 00:03:03.360 align:start position:0% that was really interesting and maybe my 00:03:03.360 --> 00:03:06.450 align:start position:0% that was really interesting and maybe my abiding<00:03:04.360> memory<00:03:04.720> from<00:03:05.620> that<00:03:05.680> experience<00:03:06.310> is 00:03:06.450 --> 00:03:06.460 align:start position:0% abiding memory from that experience is 00:03:06.460 --> 00:03:09.600 align:start position:0% abiding memory from that experience is just<00:03:06.490> that<00:03:06.850> wow<00:03:07.230> it's<00:03:08.230> you<00:03:08.530> could<00:03:09.070> you<00:03:09.520> know 00:03:09.600 --> 00:03:09.610 align:start position:0% just that wow it's you could you know 00:03:09.610 --> 00:03:12.030 align:start position:0% just that wow it's you could you know even<00:03:09.940> lowly<00:03:10.600> application<00:03:11.380> developers<00:03:11.860> like 00:03:12.030 --> 00:03:12.040 align:start position:0% even lowly application developers like 00:03:12.040 --> 00:03:14.400 align:start position:0% even lowly application developers like myself<00:03:12.250> can<00:03:12.640> benefit<00:03:13.090> from<00:03:13.150> making<00:03:14.110> the<00:03:14.260> right 00:03:14.400 --> 00:03:14.410 align:start position:0% myself can benefit from making the right 00:03:14.410 --> 00:03:15.900 align:start position:0% myself can benefit from making the right kind<00:03:14.620> of<00:03:14.680> compiler<00:03:15.160> to<00:03:15.340> fit<00:03:15.490> the<00:03:15.610> right<00:03:15.700> kind 00:03:15.900 --> 00:03:15.910 align:start position:0% kind of compiler to fit the right kind 00:03:15.910 --> 00:03:18.180 align:start position:0% kind of compiler to fit the right kind of<00:03:16.000> problem<00:03:16.360> it's<00:03:16.960> a<00:03:17.020> great<00:03:17.260> tool<00:03:17.500> to<00:03:17.860> be<00:03:18.070> able 00:03:18.180 --> 00:03:18.190 align:start position:0% of problem it's a great tool to be able 00:03:18.190 --> 00:03:22.590 align:start position:0% of problem it's a great tool to be able to<00:03:18.310> make<00:03:18.490> and<00:03:18.640> to<00:03:18.730> apply<00:03:20.820> the<00:03:21.820> other<00:03:22.000> thing 00:03:22.590 --> 00:03:22.600 align:start position:0% to make and to apply the other thing 00:03:22.600 --> 00:03:24.780 align:start position:0% to make and to apply the other thing about<00:03:22.900> it<00:03:23.200> was<00:03:23.500> that<00:03:23.740> closure<00:03:24.130> script<00:03:24.550> from 00:03:24.780 --> 00:03:24.790 align:start position:0% about it was that closure script from 00:03:24.790 --> 00:03:26.850 align:start position:0% about it was that closure script from the<00:03:25.120> beginning<00:03:25.660> was<00:03:25.810> really<00:03:26.140> oriented<00:03:26.440> toward 00:03:26.850 --> 00:03:26.860 align:start position:0% the beginning was really oriented toward 00:03:26.860 --> 00:03:31.830 align:start position:0% the beginning was really oriented toward industrial<00:03:27.870> application<00:03:28.870> and<00:03:30.840> performance 00:03:31.830 --> 00:03:31.840 align:start position:0% industrial application and performance 00:03:31.840 --> 00:03:34.470 align:start position:0% industrial application and performance both<00:03:32.770> in<00:03:32.920> terms<00:03:33.130> of<00:03:33.250> code<00:03:33.490> size<00:03:33.760> and<00:03:34.150> in<00:03:34.270> terms 00:03:34.470 --> 00:03:34.480 align:start position:0% both in terms of code size and in terms 00:03:34.480 --> 00:03:37.350 align:start position:0% both in terms of code size and in terms of<00:03:34.690> speed<00:03:35.140> are<00:03:35.490> really<00:03:36.490> important<00:03:36.910> in<00:03:37.060> the 00:03:37.350 --> 00:03:37.360 align:start position:0% of speed are really important in the 00:03:37.360 --> 00:03:39.870 align:start position:0% of speed are really important in the JavaScript<00:03:37.840> world<00:03:38.020> because<00:03:38.980> of<00:03:39.010> various 00:03:39.870 --> 00:03:39.880 align:start position:0% JavaScript world because of various 00:03:39.880 --> 00:03:42.270 align:start position:0% JavaScript world because of various limitations<00:03:40.770> surrounding<00:03:41.770> JavaScript 00:03:42.270 --> 00:03:42.280 align:start position:0% limitations surrounding JavaScript 00:03:42.280 --> 00:03:44.460 align:start position:0% limitations surrounding JavaScript including<00:03:42.670> the<00:03:42.760> fact<00:03:42.970> that<00:03:43.060> when<00:03:43.270> people<00:03:43.470> run 00:03:44.460 --> 00:03:44.470 align:start position:0% including the fact that when people run 00:03:44.470 --> 00:03:45.720 align:start position:0% including the fact that when people run your<00:03:44.620> program<00:03:44.950> they<00:03:45.100> need<00:03:45.250> to<00:03:45.340> download<00:03:45.640> the 00:03:45.720 --> 00:03:45.730 align:start position:0% your program they need to download the 00:03:45.730 --> 00:03:50.130 align:start position:0% your program they need to download the whole<00:03:45.820> program<00:03:46.180> every<00:03:46.390> time<00:03:46.570> usually<00:03:47.670> and<00:03:49.140> the 00:03:50.130 --> 00:03:50.140 align:start position:0% whole program every time usually and the 00:03:50.140 --> 00:03:52.460 align:start position:0% whole program every time usually and the designer<00:03:50.530> of<00:03:50.770> closure<00:03:50.980> script<00:03:51.430> rich<00:03:52.000> Hickey 00:03:52.460 --> 00:03:52.470 align:start position:0% designer of closure script rich Hickey 00:03:52.470 --> 00:03:57.990 align:start position:0% designer of closure script rich Hickey he<00:03:53.470> made<00:03:54.100> a<00:03:54.130> very<00:03:54.370> I<00:03:54.850> think<00:03:56.070> yeah<00:03:57.070> he<00:03:57.850> had<00:03:57.940> a 00:03:57.990 --> 00:03:58.000 align:start position:0% he made a very I think yeah he had a 00:03:58.000 --> 00:04:01.710 align:start position:0% he made a very I think yeah he had a very<00:03:58.120> key<00:03:58.330> insight<00:03:59.010> related<00:04:00.010> to<00:04:00.420> code<00:04:01.420> size 00:04:01.710 --> 00:04:01.720 align:start position:0% very key insight related to code size 00:04:01.720 --> 00:04:04.740 align:start position:0% very key insight related to code size and<00:04:02.170> then<00:04:02.770> code<00:04:02.950> improvement<00:04:03.460> which<00:04:03.580> was<00:04:03.760> it's 00:04:04.740 --> 00:04:04.750 align:start position:0% and then code improvement which was it's 00:04:04.750 --> 00:04:06.450 align:start position:0% and then code improvement which was it's possible<00:04:05.260> to<00:04:05.350> lean<00:04:05.560> on<00:04:05.740> third-party<00:04:05.950> tools 00:04:06.450 --> 00:04:06.460 align:start position:0% possible to lean on third-party tools 00:04:06.460 --> 00:04:09.480 align:start position:0% possible to lean on third-party tools like<00:04:07.030> Google<00:04:07.420> closure<00:04:07.660> compiler<00:04:08.040> to<00:04:09.040> do<00:04:09.250> that 00:04:09.480 --> 00:04:09.490 align:start position:0% like Google closure compiler to do that 00:04:09.490 --> 00:04:11.880 align:start position:0% like Google closure compiler to do that part<00:04:09.850> of<00:04:10.060> the<00:04:10.180> compilation<00:04:10.480> pipeline<00:04:11.110> and<00:04:11.380> the 00:04:11.880 --> 00:04:11.890 align:start position:0% part of the compilation pipeline and the 00:04:11.890 --> 00:04:13.590 align:start position:0% part of the compilation pipeline and the advantage<00:04:12.490> of<00:04:12.550> that<00:04:12.670> is<00:04:12.790> you<00:04:13.000> can<00:04:13.270> keep<00:04:13.420> your 00:04:13.590 --> 00:04:13.600 align:start position:0% advantage of that is you can keep your 00:04:13.600 --> 00:04:15.630 align:start position:0% advantage of that is you can keep your main<00:04:13.840> compiler<00:04:14.290> quite<00:04:14.830> simple<00:04:15.220> and<00:04:15.340> easy<00:04:15.490> to 00:04:15.630 --> 00:04:15.640 align:start position:0% main compiler quite simple and easy to 00:04:15.640 --> 00:04:17.900 align:start position:0% main compiler quite simple and easy to work<00:04:15.760> on 00:04:17.900 --> 00:04:17.910 align:start position:0% work on 00:04:17.910 --> 00:04:19.520 align:start position:0% work on so<00:04:18.209> fast-forward<00:04:18.510> a<00:04:18.780> few<00:04:18.810> years<00:04:19.200> I<00:04:19.350> did<00:04:19.500> a 00:04:19.520 --> 00:04:19.530 align:start position:0% so fast-forward a few years I did a 00:04:19.530 --> 00:04:21.050 align:start position:0% so fast-forward a few years I did a bunch<00:04:19.800> of<00:04:19.920> industrial<00:04:20.459> closure<00:04:20.760> script 00:04:21.050 --> 00:04:21.060 align:start position:0% bunch of industrial closure script 00:04:21.060 --> 00:04:22.340 align:start position:0% bunch of industrial closure script development<00:04:21.239> I<00:04:21.570> used<00:04:21.750> it<00:04:21.840> at<00:04:21.930> work<00:04:22.080> and 00:04:22.340 --> 00:04:22.350 align:start position:0% development I used it at work and 00:04:22.350 --> 00:04:25.030 align:start position:0% development I used it at work and successfully<00:04:22.980> and<00:04:23.310> continue<00:04:23.880> to<00:04:23.970> do<00:04:24.090> closure 00:04:25.030 --> 00:04:25.040 align:start position:0% successfully and continue to do closure 00:04:25.040 --> 00:04:29.360 align:start position:0% successfully and continue to do closure around<00:04:26.040> 2016<00:04:27.620> sort<00:04:28.620> of<00:04:28.710> randomly<00:04:29.070> just<00:04:29.220> got 00:04:29.360 --> 00:04:29.370 align:start position:0% around 2016 sort of randomly just got 00:04:29.370 --> 00:04:30.830 align:start position:0% around 2016 sort of randomly just got into<00:04:29.580> common<00:04:29.880> list<00:04:30.090> but<00:04:30.270> we<00:04:30.390> had<00:04:30.510> been<00:04:30.630> always 00:04:30.830 --> 00:04:30.840 align:start position:0% into common list but we had been always 00:04:30.840 --> 00:04:32.390 align:start position:0% into common list but we had been always kind<00:04:31.110> of<00:04:31.170> a<00:04:31.260> blind<00:04:31.410> spot<00:04:31.740> for<00:04:31.920> me<00:04:32.040> in<00:04:32.130> the<00:04:32.220> list 00:04:32.390 --> 00:04:32.400 align:start position:0% kind of a blind spot for me in the list 00:04:32.400 --> 00:04:35.030 align:start position:0% kind of a blind spot for me in the list world<00:04:32.700> and<00:04:32.940> I<00:04:33.300> knew<00:04:33.480> rich<00:04:34.380> Hickey<00:04:34.590> had<00:04:34.890> been 00:04:35.030 --> 00:04:35.040 align:start position:0% world and I knew rich Hickey had been 00:04:35.040 --> 00:04:37.340 align:start position:0% world and I knew rich Hickey had been influenced<00:04:35.490> by<00:04:35.520> common<00:04:35.880> lisp<00:04:36.110> before<00:04:37.110> he<00:04:37.230> made 00:04:37.340 --> 00:04:37.350 align:start position:0% influenced by common lisp before he made 00:04:37.350 --> 00:04:39.340 align:start position:0% influenced by common lisp before he made closure<00:04:37.620> and<00:04:37.890> I<00:04:38.430> had<00:04:38.610> brushes<00:04:38.850> with<00:04:39.150> it 00:04:39.340 --> 00:04:39.350 align:start position:0% closure and I had brushes with it 00:04:39.350 --> 00:04:41.750 align:start position:0% closure and I had brushes with it through<00:04:40.350> closure<00:04:40.620> but<00:04:41.010> I'd<00:04:41.130> never<00:04:41.280> really<00:04:41.550> sat 00:04:41.750 --> 00:04:41.760 align:start position:0% through closure but I'd never really sat 00:04:41.760 --> 00:04:44.870 align:start position:0% through closure but I'd never really sat down<00:04:41.790> with<00:04:42.390> it<00:04:42.510> myself<00:04:42.690> and<00:04:43.370> the<00:04:44.370> more<00:04:44.610> time<00:04:44.850> I 00:04:44.870 --> 00:04:44.880 align:start position:0% down with it myself and the more time I 00:04:44.880 --> 00:04:46.610 align:start position:0% down with it myself and the more time I spent<00:04:45.210> with<00:04:45.240> it<00:04:45.450> the<00:04:45.540> more<00:04:45.660> I<00:04:45.720> grew<00:04:46.320> to<00:04:46.410> really 00:04:46.610 --> 00:04:46.620 align:start position:0% spent with it the more I grew to really 00:04:46.620 --> 00:04:49.340 align:start position:0% spent with it the more I grew to really really<00:04:46.830> liked<00:04:47.010> it<00:04:47.450> it's<00:04:48.450> I<00:04:48.720> think<00:04:48.930> in<00:04:49.110> a<00:04:49.170> lot<00:04:49.200> of 00:04:49.340 --> 00:04:49.350 align:start position:0% really liked it it's I think in a lot of 00:04:49.350 --> 00:04:51.410 align:start position:0% really liked it it's I think in a lot of respects<00:04:49.680> lower<00:04:49.890> level<00:04:50.280> than<00:04:50.550> closure<00:04:50.880> but<00:04:51.240> I 00:04:51.410 --> 00:04:51.420 align:start position:0% respects lower level than closure but I 00:04:51.420 --> 00:04:53.930 align:start position:0% respects lower level than closure but I think<00:04:51.660> that<00:04:51.840> that<00:04:52.130> lower<00:04:53.130> level<00:04:53.400> aspect 00:04:53.930 --> 00:04:53.940 align:start position:0% think that that lower level aspect 00:04:53.940 --> 00:04:57.590 align:start position:0% think that that lower level aspect defers<00:04:54.510> more<00:04:55.010> capability<00:04:56.010> to<00:04:56.460> the<00:04:56.820> programmer 00:04:57.590 --> 00:04:57.600 align:start position:0% defers more capability to the programmer 00:04:57.600 --> 00:05:01.160 align:start position:0% defers more capability to the programmer there's<00:04:58.260> more<00:04:58.530> room<00:04:58.910> to<00:04:59.910> make<00:05:00.090> the<00:05:00.870> language 00:05:01.160 --> 00:05:01.170 align:start position:0% there's more room to make the language 00:05:01.170 --> 00:05:03.520 align:start position:0% there's more room to make the language of<00:05:01.320> the<00:05:01.380> problem<00:05:01.740> as<00:05:02.010> I've<00:05:02.310> heard<00:05:02.430> it<00:05:02.550> called 00:05:03.520 --> 00:05:03.530 align:start position:0% of the problem as I've heard it called 00:05:03.530 --> 00:05:07.880 align:start position:0% of the problem as I've heard it called so<00:05:04.530> as<00:05:04.770> my<00:05:05.040> Lisp<00:05:05.850> fanaticism<00:05:06.570> grew<00:05:07.020> I<00:05:07.320> had<00:05:07.770> this 00:05:07.880 --> 00:05:07.890 align:start position:0% so as my Lisp fanaticism grew I had this 00:05:07.890 --> 00:05:10.880 align:start position:0% so as my Lisp fanaticism grew I had this idea<00:05:08.040> to<00:05:08.340> make<00:05:08.490> jackal<00:05:09.530> but<00:05:10.530> there<00:05:10.620> actually<00:05:10.710> a 00:05:10.880 --> 00:05:10.890 align:start position:0% idea to make jackal but there actually a 00:05:10.890 --> 00:05:12.890 align:start position:0% idea to make jackal but there actually a few<00:05:11.040> other<00:05:11.160> ideas<00:05:11.550> that<00:05:11.820> that<00:05:12.090> led<00:05:12.330> to<00:05:12.480> jackal 00:05:12.890 --> 00:05:12.900 align:start position:0% few other ideas that that led to jackal 00:05:12.900 --> 00:05:16.430 align:start position:0% few other ideas that that led to jackal that<00:05:13.170> happen<00:05:13.470> kind<00:05:13.620> of<00:05:13.740> concurrently<00:05:15.170> at<00:05:16.170> one 00:05:16.430 --> 00:05:16.440 align:start position:0% that happen kind of concurrently at one 00:05:16.440 --> 00:05:18.710 align:start position:0% that happen kind of concurrently at one point<00:05:16.710> I<00:05:16.950> had<00:05:17.220> the<00:05:17.340> idea<00:05:17.430> to<00:05:17.610> make<00:05:17.700> my<00:05:17.940> own<00:05:17.970> lisp 00:05:18.710 --> 00:05:18.720 align:start position:0% point I had the idea to make my own lisp 00:05:18.720 --> 00:05:21.080 align:start position:0% point I had the idea to make my own lisp dialect<00:05:19.230> called<00:05:19.440> beta<00:05:19.710> Lisp<00:05:20.010> that<00:05:20.850> was<00:05:20.970> going 00:05:21.080 --> 00:05:21.090 align:start position:0% dialect called beta Lisp that was going 00:05:21.090 --> 00:05:23.660 align:start position:0% dialect called beta Lisp that was going to<00:05:21.150> be<00:05:21.240> an<00:05:21.390> experimental<00:05:22.050> vehicle<00:05:22.950> to<00:05:23.430> play 00:05:23.660 --> 00:05:23.670 align:start position:0% to be an experimental vehicle to play 00:05:23.670 --> 00:05:25.520 align:start position:0% to be an experimental vehicle to play with<00:05:23.820> this<00:05:23.940> idea<00:05:24.270> that<00:05:24.450> macros<00:05:25.020> receive 00:05:25.520 --> 00:05:25.530 align:start position:0% with this idea that macros receive 00:05:25.530 --> 00:05:27.980 align:start position:0% with this idea that macros receive arguments<00:05:26.130> macro<00:05:26.760> expanded<00:05:27.240> by<00:05:27.360> DeVault<00:05:27.720> and 00:05:27.980 --> 00:05:27.990 align:start position:0% arguments macro expanded by DeVault and 00:05:27.990 --> 00:05:29.780 align:start position:0% arguments macro expanded by DeVault and so<00:05:28.380> the<00:05:28.500> beta<00:05:28.680> and<00:05:28.950> beta<00:05:29.010> List<00:05:29.430> comes<00:05:29.670> from 00:05:29.780 --> 00:05:29.790 align:start position:0% so the beta and beta List comes from 00:05:29.790 --> 00:05:32.990 align:start position:0% so the beta and beta List comes from beta<00:05:30.000> reduction<00:05:30.510> lambda<00:05:31.410> calculus<00:05:31.830> I<00:05:32.550> had 00:05:32.990 --> 00:05:33.000 align:start position:0% beta reduction lambda calculus I had 00:05:33.000 --> 00:05:34.040 align:start position:0% beta reduction lambda calculus I had this<00:05:33.090> idea<00:05:33.270> that<00:05:33.570> that<00:05:33.660> would<00:05:33.780> you<00:05:33.930> know 00:05:34.040 --> 00:05:34.050 align:start position:0% this idea that that would you know 00:05:34.050 --> 00:05:37.630 align:start position:0% this idea that that would you know dramatically<00:05:34.560> clean<00:05:34.919> up<00:05:35.100> the<00:05:35.840> lisp 00:05:37.630 --> 00:05:37.640 align:start position:0% dramatically clean up the lisp 00:05:37.640 --> 00:05:40.190 align:start position:0% dramatically clean up the lisp implementation<00:05:38.640> but<00:05:38.790> didn't<00:05:39.630> really<00:05:39.810> work 00:05:40.190 --> 00:05:40.200 align:start position:0% implementation but didn't really work 00:05:40.200 --> 00:05:41.750 align:start position:0% implementation but didn't really work out<00:05:40.350> that<00:05:40.410> way<00:05:40.710> there<00:05:41.160> are<00:05:41.190> other<00:05:41.370> problems 00:05:41.750 --> 00:05:41.760 align:start position:0% out that way there are other problems 00:05:41.760 --> 00:05:44.330 align:start position:0% out that way there are other problems associated<00:05:42.060> with<00:05:42.390> that<00:05:42.890> and<00:05:43.890> I<00:05:43.980> didn't<00:05:44.220> get 00:05:44.330 --> 00:05:44.340 align:start position:0% associated with that and I didn't get 00:05:44.340 --> 00:05:45.770 align:start position:0% associated with that and I didn't get too<00:05:44.430> far<00:05:44.460> with<00:05:44.760> it<00:05:44.790> but<00:05:45.030> I<00:05:45.060> did<00:05:45.270> stumble<00:05:45.690> on 00:05:45.770 --> 00:05:45.780 align:start position:0% too far with it but I did stumble on 00:05:45.780 --> 00:05:47.120 align:start position:0% too far with it but I did stumble on this<00:05:45.930> idea<00:05:46.230> of<00:05:46.290> an<00:05:46.380> asynchronous<00:05:46.710> reader 00:05:47.120 --> 00:05:47.130 align:start position:0% this idea of an asynchronous reader 00:05:47.130 --> 00:05:49.460 align:start position:0% this idea of an asynchronous reader which<00:05:47.430> I'll<00:05:47.550> talk<00:05:47.669> about<00:05:47.910> again<00:05:48.120> soon<00:05:48.690> in<00:05:49.260> the 00:05:49.460 --> 00:05:49.470 align:start position:0% which I'll talk about again soon in the 00:05:49.470 --> 00:05:53.840 align:start position:0% which I'll talk about again soon in the talk<00:05:51.260> at<00:05:52.260> one<00:05:52.410> point<00:05:52.560> I<00:05:52.680> picked<00:05:52.860> up<00:05:52.950> a<00:05:53.130> copy<00:05:53.550> of 00:05:53.840 --> 00:05:53.850 align:start position:0% talk at one point I picked up a copy of 00:05:53.850 --> 00:05:55.610 align:start position:0% talk at one point I picked up a copy of Common<00:05:54.150> Lisp<00:05:54.180> the<00:05:54.450> language<00:05:54.780> second<00:05:55.230> edition 00:05:55.610 --> 00:05:55.620 align:start position:0% Common Lisp the language second edition 00:05:55.620 --> 00:06:00.290 align:start position:0% Common Lisp the language second edition by<00:05:55.650> guy<00:05:56.070> Steele<00:05:56.400> and<00:05:57.740> I<00:05:58.740> also<00:05:59.250> read<00:05:59.910> through<00:06:00.270> a 00:06:00.290 --> 00:06:00.300 align:start position:0% by guy Steele and I also read through a 00:06:00.300 --> 00:06:02.480 align:start position:0% by guy Steele and I also read through a bunch<00:06:00.720> of<00:06:00.810> the<00:06:00.900> early<00:06:01.290> Common<00:06:01.680> Lisp<00:06:01.710> design 00:06:02.480 --> 00:06:02.490 align:start position:0% bunch of the early Common Lisp design 00:06:02.490 --> 00:06:06.530 align:start position:0% bunch of the early Common Lisp design discussion<00:06:03.120> emails<00:06:03.480> and<00:06:03.810> this<00:06:04.620> su<00:06:05.070> -<00:06:05.340> AI<00:06:05.669> DARPA 00:06:06.530 --> 00:06:06.540 align:start position:0% discussion emails and this su - AI DARPA 00:06:06.540 --> 00:06:09.200 align:start position:0% discussion emails and this su - AI DARPA mailing<00:06:06.840> list<00:06:07.020> thing<00:06:07.230> and<00:06:07.940> that<00:06:08.940> got<00:06:09.120> me 00:06:09.200 --> 00:06:09.210 align:start position:0% mailing list thing and that got me 00:06:09.210 --> 00:06:13.159 align:start position:0% mailing list thing and that got me interested<00:06:09.390> in<00:06:11.150> or<00:06:12.150> I<00:06:12.210> think<00:06:12.450> gave<00:06:12.990> me<00:06:13.110> an 00:06:13.159 --> 00:06:13.169 align:start position:0% interested in or I think gave me an 00:06:13.169 --> 00:06:15.230 align:start position:0% interested in or I think gave me an appreciation<00:06:13.350> for<00:06:13.770> the<00:06:13.980> amount<00:06:14.040> of<00:06:14.669> design 00:06:15.230 --> 00:06:15.240 align:start position:0% appreciation for the amount of design 00:06:15.240 --> 00:06:18.200 align:start position:0% appreciation for the amount of design work<00:06:15.630> that<00:06:15.660> went<00:06:16.050> into<00:06:16.169> Common<00:06:16.560> Lisp<00:06:17.210> which 00:06:18.200 --> 00:06:18.210 align:start position:0% work that went into Common Lisp which 00:06:18.210 --> 00:06:19.700 align:start position:0% work that went into Common Lisp which was<00:06:18.390> really<00:06:18.600> refreshing<00:06:18.840> to<00:06:19.200> me<00:06:19.350> because<00:06:19.680> I 00:06:19.700 --> 00:06:19.710 align:start position:0% was really refreshing to me because I 00:06:19.710 --> 00:06:22.580 align:start position:0% was really refreshing to me because I had<00:06:19.919> just<00:06:19.950> failed<00:06:20.370> to<00:06:20.520> design<00:06:20.910> a<00:06:20.940> language<00:06:21.590> and 00:06:22.580 --> 00:06:22.590 align:start position:0% had just failed to design a language and 00:06:22.590 --> 00:06:25.130 align:start position:0% had just failed to design a language and I<00:06:23.340> felt<00:06:23.669> better<00:06:24.030> about<00:06:24.390> failing<00:06:24.660> to<00:06:24.840> do<00:06:24.960> so 00:06:25.130 --> 00:06:25.140 align:start position:0% I felt better about failing to do so 00:06:25.140 --> 00:06:27.620 align:start position:0% I felt better about failing to do so when<00:06:25.290> I<00:06:25.320> realized<00:06:25.560> how<00:06:25.979> much<00:06:26.210> how<00:06:27.210> difficult 00:06:27.620 --> 00:06:27.630 align:start position:0% when I realized how much how difficult 00:06:27.630 --> 00:06:30.140 align:start position:0% when I realized how much how difficult that<00:06:27.690> really<00:06:27.930> was<00:06:28.080> to<00:06:28.200> do<00:06:28.320> and<00:06:28.950> I<00:06:29.820> realized 00:06:30.140 --> 00:06:30.150 align:start position:0% that really was to do and I realized 00:06:30.150 --> 00:06:31.379 align:start position:0% that really was to do and I realized that<00:06:30.210> implementing<00:06:30.720> a<00:06:30.810> spec 00:06:31.379 --> 00:06:31.389 align:start position:0% that implementing a spec 00:06:31.389 --> 00:06:33.600 align:start position:0% that implementing a spec he's<00:06:31.960> gonna<00:06:32.139> would<00:06:32.500> be<00:06:32.620> a<00:06:32.650> lot<00:06:32.889> easier<00:06:32.919> than 00:06:33.600 --> 00:06:33.610 align:start position:0% he's gonna would be a lot easier than 00:06:33.610 --> 00:06:35.879 align:start position:0% he's gonna would be a lot easier than designing<00:06:34.360> a<00:06:34.509> language<00:06:34.689> like<00:06:35.349> orders<00:06:35.740> of 00:06:35.879 --> 00:06:35.889 align:start position:0% designing a language like orders of 00:06:35.889 --> 00:06:38.820 align:start position:0% designing a language like orders of magnitude<00:06:36.539> and<00:06:37.539> at<00:06:37.689> least<00:06:37.870> one<00:06:38.020> reason<00:06:38.379> is<00:06:38.530> if 00:06:38.820 --> 00:06:38.830 align:start position:0% magnitude and at least one reason is if 00:06:38.830 --> 00:06:41.399 align:start position:0% magnitude and at least one reason is if you're<00:06:39.039> handed<00:06:39.340> a<00:06:39.430> spec<00:06:39.780> you<00:06:40.780> can<00:06:40.810> work<00:06:41.110> on<00:06:41.259> it 00:06:41.399 --> 00:06:41.409 align:start position:0% you're handed a spec you can work on it 00:06:41.409 --> 00:06:43.140 align:start position:0% you're handed a spec you can work on it in<00:06:41.530> pretty<00:06:41.949> small<00:06:42.219> increments<00:06:42.699> and<00:06:42.879> make 00:06:43.140 --> 00:06:43.150 align:start position:0% in pretty small increments and make 00:06:43.150 --> 00:06:45.929 align:start position:0% in pretty small increments and make really<00:06:43.629> gratifying<00:06:44.280> progress<00:06:45.280> over<00:06:45.729> a<00:06:45.789> long 00:06:45.929 --> 00:06:45.939 align:start position:0% really gratifying progress over a long 00:06:45.939 --> 00:06:47.369 align:start position:0% really gratifying progress over a long period<00:06:46.180> of<00:06:46.210> time<00:06:46.389> and<00:06:46.629> that<00:06:46.750> progress<00:06:46.960> be 00:06:47.369 --> 00:06:47.379 align:start position:0% period of time and that progress be 00:06:47.379 --> 00:06:49.409 align:start position:0% period of time and that progress be continuous<00:06:47.919> but<00:06:48.759> if<00:06:48.909> you're<00:06:49.030> working<00:06:49.180> on<00:06:49.389> a 00:06:49.409 --> 00:06:49.419 align:start position:0% continuous but if you're working on a 00:06:49.419 --> 00:06:53.040 align:start position:0% continuous but if you're working on a design<00:06:49.840> of<00:06:50.139> a<00:06:50.199> language<00:06:50.560> that's<00:06:50.740> that<00:06:52.050> that's 00:06:53.040 --> 00:06:53.050 align:start position:0% design of a language that's that that's 00:06:53.050 --> 00:06:56.369 align:start position:0% design of a language that's that that's something<00:06:53.289> that<00:06:53.409> requires<00:06:53.770> a<00:06:55.319> lot<00:06:56.319> more 00:06:56.369 --> 00:06:56.379 align:start position:0% something that requires a lot more 00:06:56.379 --> 00:07:00.360 align:start position:0% something that requires a lot more effort<00:06:57.210> so<00:06:58.210> I<00:06:58.539> just<00:06:59.259> started<00:06:59.620> to<00:06:59.770> play<00:07:00.219> with 00:07:00.360 --> 00:07:00.370 align:start position:0% effort so I just started to play with 00:07:00.370 --> 00:07:01.920 align:start position:0% effort so I just started to play with this<00:07:00.460> idea<00:07:00.610> of<00:07:00.849> implementing<00:07:01.270> a<00:07:01.419> common<00:07:01.750> lisp 00:07:01.920 --> 00:07:01.930 align:start position:0% this idea of implementing a common lisp 00:07:01.930 --> 00:07:03.869 align:start position:0% this idea of implementing a common lisp and<00:07:02.169> I<00:07:02.199> knew<00:07:02.349> I<00:07:02.560> knew<00:07:02.860> common<00:07:03.189> list<00:07:03.340> was<00:07:03.460> huge 00:07:03.869 --> 00:07:03.879 align:start position:0% and I knew I knew common list was huge 00:07:03.879 --> 00:07:05.459 align:start position:0% and I knew I knew common list was huge and<00:07:04.180> that<00:07:04.389> it<00:07:04.479> would<00:07:04.689> probably<00:07:04.870> never<00:07:05.080> be<00:07:05.289> done 00:07:05.459 --> 00:07:05.469 align:start position:0% and that it would probably never be done 00:07:05.469 --> 00:07:07.980 align:start position:0% and that it would probably never be done but<00:07:05.860> I<00:07:05.889> just<00:07:06.069> couldn't<00:07:06.340> help<00:07:06.400> myself<00:07:06.550> and<00:07:07.180> as<00:07:07.870> I 00:07:07.980 --> 00:07:07.990 align:start position:0% but I just couldn't help myself and as I 00:07:07.990 --> 00:07:09.420 align:start position:0% but I just couldn't help myself and as I got<00:07:08.110> going<00:07:08.439> I<00:07:08.529> realized<00:07:08.889> I<00:07:09.129> had<00:07:09.310> this 00:07:09.420 --> 00:07:09.430 align:start position:0% got going I realized I had this 00:07:09.430 --> 00:07:12.390 align:start position:0% got going I realized I had this opportunity<00:07:09.699> to<00:07:10.439> maybe<00:07:11.439> maybe<00:07:11.889> achieve<00:07:12.189> some 00:07:12.390 --> 00:07:12.400 align:start position:0% opportunity to maybe maybe achieve some 00:07:12.400 --> 00:07:14.730 align:start position:0% opportunity to maybe maybe achieve some things<00:07:12.610> with<00:07:12.759> a<00:07:12.789> new<00:07:13.000> Common<00:07:13.330> Lisp<00:07:13.560> first<00:07:14.560> I 00:07:14.730 --> 00:07:14.740 align:start position:0% things with a new Common Lisp first I 00:07:14.740 --> 00:07:20.519 align:start position:0% things with a new Common Lisp first I knew<00:07:14.889> that<00:07:15.129> the<00:07:15.550> browser<00:07:15.939> platform<00:07:19.259> suggest<00:07:20.259> a 00:07:20.519 --> 00:07:20.529 align:start position:0% knew that the browser platform suggest a 00:07:20.529 --> 00:07:23.040 align:start position:0% knew that the browser platform suggest a lot<00:07:20.800> of<00:07:20.979> language<00:07:21.729> level<00:07:22.060> ideas<00:07:22.449> to<00:07:22.629> solving 00:07:23.040 --> 00:07:23.050 align:start position:0% lot of language level ideas to solving 00:07:23.050 --> 00:07:25.559 align:start position:0% lot of language level ideas to solving various<00:07:23.439> problems<00:07:23.919> and<00:07:24.219> I<00:07:25.120> thought<00:07:25.330> you<00:07:25.479> know 00:07:25.559 --> 00:07:25.569 align:start position:0% various problems and I thought you know 00:07:25.569 --> 00:07:27.360 align:start position:0% various problems and I thought you know if<00:07:25.659> I'm<00:07:25.750> gonna<00:07:25.900> be<00:07:26.050> making<00:07:26.349> languages<00:07:26.919> to 00:07:27.360 --> 00:07:27.370 align:start position:0% if I'm gonna be making languages to 00:07:27.370 --> 00:07:29.610 align:start position:0% if I'm gonna be making languages to target<00:07:27.669> JavaScript<00:07:28.240> what<00:07:29.169> better<00:07:29.349> way<00:07:29.590> to 00:07:29.610 --> 00:07:29.620 align:start position:0% target JavaScript what better way to 00:07:29.620 --> 00:07:31.679 align:start position:0% target JavaScript what better way to start<00:07:30.129> than<00:07:30.520> with<00:07:30.580> common<00:07:31.210> lisp<00:07:31.419> as<00:07:31.659> a 00:07:31.679 --> 00:07:31.689 align:start position:0% start than with common lisp as a 00:07:31.689 --> 00:07:34.140 align:start position:0% start than with common lisp as a substrate<00:07:32.490> because<00:07:33.490> it's<00:07:33.669> it's<00:07:33.879> a<00:07:33.969> known 00:07:34.140 --> 00:07:34.150 align:start position:0% substrate because it's it's a known 00:07:34.150 --> 00:07:37.010 align:start position:0% substrate because it's it's a known quantity<00:07:34.330> and<00:07:34.810> it's<00:07:34.960> a<00:07:35.020> proven<00:07:35.199> substrate<00:07:35.770> and 00:07:37.010 --> 00:07:37.020 align:start position:0% quantity and it's a proven substrate and 00:07:37.020 --> 00:07:39.719 align:start position:0% quantity and it's a proven substrate and I<00:07:38.020> also<00:07:38.409> realized<00:07:38.830> I<00:07:38.949> had<00:07:39.069> an<00:07:39.159> opportunity<00:07:39.400> to 00:07:39.719 --> 00:07:39.729 align:start position:0% I also realized I had an opportunity to 00:07:39.729 --> 00:07:41.309 align:start position:0% I also realized I had an opportunity to pursue<00:07:40.120> this<00:07:40.569> idea<00:07:40.900> of<00:07:40.990> an<00:07:41.080> asynchronous 00:07:41.309 --> 00:07:41.319 align:start position:0% pursue this idea of an asynchronous 00:07:41.319 --> 00:07:45.050 align:start position:0% pursue this idea of an asynchronous reader<00:07:41.919> because<00:07:42.909> I<00:07:43.210> had<00:07:43.569> a<00:07:43.599> suspicion<00:07:44.259> that 00:07:45.050 --> 00:07:45.060 align:start position:0% reader because I had a suspicion that 00:07:45.060 --> 00:07:49.140 align:start position:0% reader because I had a suspicion that with<00:07:46.060> a<00:07:46.330> annecy<00:07:46.990> asynchronous<00:07:47.710> reader<00:07:47.979> a<00:07:48.310> new 00:07:49.140 --> 00:07:49.150 align:start position:0% with a annecy asynchronous reader a new 00:07:49.150 --> 00:07:51.119 align:start position:0% with a annecy asynchronous reader a new level<00:07:49.389> of<00:07:49.779> residential<00:07:50.379> development<00:07:50.409> could 00:07:51.119 --> 00:07:51.129 align:start position:0% level of residential development could 00:07:51.129 --> 00:07:53.610 align:start position:0% level of residential development could become<00:07:51.430> possible<00:07:51.940> which<00:07:52.120> is<00:07:52.270> to<00:07:52.449> say<00:07:52.659> that<00:07:52.930> the 00:07:53.610 --> 00:07:53.620 align:start position:0% become possible which is to say that the 00:07:53.620 --> 00:07:54.990 align:start position:0% become possible which is to say that the development<00:07:54.159> time<00:07:54.310> and<00:07:54.610> the<00:07:54.789> runtime 00:07:54.990 --> 00:07:55.000 align:start position:0% development time and the runtime 00:07:55.000 --> 00:07:57.089 align:start position:0% development time and the runtime environments<00:07:55.930> could<00:07:56.169> be<00:07:56.319> integrated<00:07:56.589> in<00:07:57.009> a 00:07:57.089 --> 00:07:57.099 align:start position:0% environments could be integrated in a 00:07:57.099 --> 00:07:59.279 align:start position:0% environments could be integrated in a way<00:07:57.250> that<00:07:57.490> they<00:07:57.610> haven't<00:07:57.849> yet<00:07:58.060> been<00:07:58.360> with<00:07:59.139> any 00:07:59.279 --> 00:07:59.289 align:start position:0% way that they haven't yet been with any 00:07:59.289 --> 00:08:00.600 align:start position:0% way that they haven't yet been with any of<00:07:59.409> the<00:07:59.500> Lisp<00:07:59.680> implementations<00:07:59.830> that<00:08:00.490> I'd 00:08:00.600 --> 00:08:00.610 align:start position:0% of the Lisp implementations that I'd 00:08:00.610 --> 00:08:03.629 align:start position:0% of the Lisp implementations that I'd experimented<00:08:01.180> with<00:08:01.210> and<00:08:01.620> plus<00:08:02.620> you<00:08:03.339> can't<00:08:03.550> go 00:08:03.629 --> 00:08:03.639 align:start position:0% experimented with and plus you can't go 00:08:03.639 --> 00:08:05.159 align:start position:0% experimented with and plus you can't go wrong<00:08:03.819> if<00:08:04.029> you<00:08:04.089> have<00:08:04.240> you<00:08:04.330> have<00:08:04.360> a<00:08:04.659> nice<00:08:04.810> Common 00:08:05.159 --> 00:08:05.169 align:start position:0% wrong if you have you have a nice Common 00:08:05.169 --> 00:08:06.570 align:start position:0% wrong if you have you have a nice Common Lisp<00:08:05.199> to<00:08:05.529> work<00:08:05.770> with<00:08:05.979> and<00:08:06.159> I<00:08:06.189> thought<00:08:06.370> you<00:08:06.490> know 00:08:06.570 --> 00:08:06.580 align:start position:0% Lisp to work with and I thought you know 00:08:06.580 --> 00:08:07.860 align:start position:0% Lisp to work with and I thought you know if<00:08:06.699> I'm<00:08:06.789> going<00:08:06.879> to<00:08:06.939> be<00:08:07.060> doing<00:08:07.180> browser<00:08:07.509> stuff 00:08:07.860 --> 00:08:07.870 align:start position:0% if I'm going to be doing browser stuff 00:08:07.870 --> 00:08:09.749 align:start position:0% if I'm going to be doing browser stuff for<00:08:08.020> the<00:08:08.110> rest<00:08:08.229> of<00:08:08.349> my<00:08:08.409> career<00:08:08.469> be<00:08:09.430> nice<00:08:09.580> to 00:08:09.749 --> 00:08:09.759 align:start position:0% for the rest of my career be nice to 00:08:09.759 --> 00:08:11.550 align:start position:0% for the rest of my career be nice to have<00:08:09.879> a<00:08:09.909> common<00:08:10.120> lisp<00:08:10.449> that<00:08:10.719> I<00:08:10.750> can<00:08:10.990> I<00:08:11.139> can<00:08:11.379> use 00:08:11.550 --> 00:08:11.560 align:start position:0% have a common lisp that I can I can use 00:08:11.560 --> 00:08:17.399 align:start position:0% have a common lisp that I can I can use so<00:08:11.770> that<00:08:11.889> I<00:08:11.919> can<00:08:12.099> write<00:08:12.279> Common<00:08:12.610> Lisp<00:08:15.479> so<00:08:16.479> the 00:08:17.399 --> 00:08:17.409 align:start position:0% so that I can write Common Lisp so the 00:08:17.409 --> 00:08:19.290 align:start position:0% so that I can write Common Lisp so the JavaScript<00:08:17.710> platform<00:08:18.279> which<00:08:18.460> I'm<00:08:18.610> interested 00:08:19.290 --> 00:08:19.300 align:start position:0% JavaScript platform which I'm interested 00:08:19.300 --> 00:08:20.999 align:start position:0% JavaScript platform which I'm interested in<00:08:19.389> compiling<00:08:19.689> to<00:08:19.930> in<00:08:20.020> which<00:08:20.169> jackal<00:08:20.860> is 00:08:20.999 --> 00:08:21.009 align:start position:0% in compiling to in which jackal is 00:08:21.009 --> 00:08:25.800 align:start position:0% in compiling to in which jackal is intimately<00:08:21.460> related<00:08:24.150> in<00:08:25.150> a<00:08:25.270> nutshell<00:08:25.449> it 00:08:25.800 --> 00:08:25.810 align:start position:0% intimately related in a nutshell it 00:08:25.810 --> 00:08:28.320 align:start position:0% intimately related in a nutshell it makes<00:08:26.050> the<00:08:26.169> browser<00:08:26.379> programmable<00:08:27.159> so<00:08:27.939> prior 00:08:28.320 --> 00:08:28.330 align:start position:0% makes the browser programmable so prior 00:08:28.330 --> 00:08:30.149 align:start position:0% makes the browser programmable so prior to<00:08:28.509> the<00:08:28.629> advent<00:08:28.750> of<00:08:29.020> JavaScript<00:08:29.560> the<00:08:29.740> web 00:08:30.149 --> 00:08:30.159 align:start position:0% to the advent of JavaScript the web 00:08:30.159 --> 00:08:31.649 align:start position:0% to the advent of JavaScript the web browsers<00:08:30.520> were<00:08:30.669> effectively<00:08:31.120> static 00:08:31.649 --> 00:08:31.659 align:start position:0% browsers were effectively static 00:08:31.659 --> 00:08:33.180 align:start position:0% browsers were effectively static document<00:08:32.140> viewers<00:08:32.409> with<00:08:32.709> some<00:08:32.860> styling 00:08:33.180 --> 00:08:33.190 align:start position:0% document viewers with some styling 00:08:33.190 --> 00:08:35.069 align:start position:0% document viewers with some styling capability<00:08:33.779> javascript<00:08:34.779> makes<00:08:34.930> them 00:08:35.069 --> 00:08:35.079 align:start position:0% capability javascript makes them 00:08:35.079 --> 00:08:38.360 align:start position:0% capability javascript makes them full-blown<00:08:35.500> programming<00:08:36.130> environments 00:08:38.360 --> 00:08:38.370 align:start position:0% full-blown programming environments 00:08:38.370 --> 00:08:40.279 align:start position:0% full-blown programming environments it's<00:08:38.490> interesting<00:08:39.330> and<00:08:39.779> important<00:08:40.260> and 00:08:40.279 --> 00:08:40.289 align:start position:0% it's interesting and important and 00:08:40.289 --> 00:08:42.769 align:start position:0% it's interesting and important and valuable<00:08:41.099> in<00:08:41.640> an<00:08:42.150> industrial<00:08:42.599> setting 00:08:42.769 --> 00:08:42.779 align:start position:0% valuable in an industrial setting 00:08:42.779 --> 00:08:45.040 align:start position:0% valuable in an industrial setting because<00:08:43.229> it<00:08:43.800> makes<00:08:44.130> people<00:08:44.460> feel<00:08:44.640> like 00:08:45.040 --> 00:08:45.050 align:start position:0% because it makes people feel like 00:08:45.050 --> 00:08:47.450 align:start position:0% because it makes people feel like webpages<00:08:46.050> are<00:08:46.380> faster<00:08:46.800> they're<00:08:47.279> not 00:08:47.450 --> 00:08:47.460 align:start position:0% webpages are faster they're not 00:08:47.460 --> 00:08:49.280 align:start position:0% webpages are faster they're not necessarily<00:08:47.940> actually<00:08:48.240> doing<00:08:48.690> work<00:08:48.839> faster 00:08:49.280 --> 00:08:49.290 align:start position:0% necessarily actually doing work faster 00:08:49.290 --> 00:08:53.120 align:start position:0% necessarily actually doing work faster but<00:08:49.470> they're<00:08:49.589> more<00:08:49.710> responsive<00:08:52.130> modern 00:08:53.120 --> 00:08:53.130 align:start position:0% but they're more responsive modern 00:08:53.130 --> 00:08:55.370 align:start position:0% but they're more responsive modern JavaScript<00:08:53.600> runtimes<00:08:54.600> are<00:08:54.810> also<00:08:54.990> quite 00:08:55.370 --> 00:08:55.380 align:start position:0% JavaScript runtimes are also quite 00:08:55.380 --> 00:08:57.890 align:start position:0% JavaScript runtimes are also quite efficient<00:08:55.920> and<00:08:56.070> fast<00:08:56.370> they<00:08:57.330> have<00:08:57.540> world-class 00:08:57.890 --> 00:08:57.900 align:start position:0% efficient and fast they have world-class 00:08:57.900 --> 00:09:00.440 align:start position:0% efficient and fast they have world-class garbage<00:08:58.650> collectors<00:08:59.040> now<00:08:59.250> in<00:08:59.580> Firefox<00:09:00.180> and 00:09:00.440 --> 00:09:00.450 align:start position:0% garbage collectors now in Firefox and 00:09:00.450 --> 00:09:03.530 align:start position:0% garbage collectors now in Firefox and Chrome<00:09:00.510> and<00:09:01.430> world-class<00:09:02.430> tracing<00:09:03.060> Jets 00:09:03.530 --> 00:09:03.540 align:start position:0% Chrome and world-class tracing Jets 00:09:03.540 --> 00:09:07.400 align:start position:0% Chrome and world-class tracing Jets really<00:09:03.990> incredible<00:09:04.710> technology<00:09:06.410> the 00:09:07.400 --> 00:09:07.410 align:start position:0% really incredible technology the 00:09:07.410 --> 00:09:09.320 align:start position:0% really incredible technology the javascript<00:09:07.860> is<00:09:07.950> quite<00:09:08.130> a<00:09:08.160> fast<00:09:08.460> language<00:09:09.029> even 00:09:09.320 --> 00:09:09.330 align:start position:0% javascript is quite a fast language even 00:09:09.330 --> 00:09:12.710 align:start position:0% javascript is quite a fast language even in<00:09:09.600> commodity<00:09:10.110> web<00:09:10.260> browsers<00:09:11.630> there's<00:09:12.630> a 00:09:12.710 --> 00:09:12.720 align:start position:0% in commodity web browsers there's a 00:09:12.720 --> 00:09:15.829 align:start position:0% in commodity web browsers there's a document<00:09:13.440> object<00:09:13.589> model<00:09:13.920> a<00:09:14.480> model<00:09:15.480> extra 00:09:15.829 --> 00:09:15.839 align:start position:0% document object model a model extra 00:09:15.839 --> 00:09:19.460 align:start position:0% document object model a model extra abstraction<00:09:16.410> in<00:09:18.140> JavaScript<00:09:19.140> and<00:09:19.230> this<00:09:19.350> is 00:09:19.460 --> 00:09:19.470 align:start position:0% abstraction in JavaScript and this is 00:09:19.470 --> 00:09:22.130 align:start position:0% abstraction in JavaScript and this is how<00:09:19.589> one<00:09:19.830> presents<00:09:20.730> user<00:09:21.360> interfaces<00:09:21.960> and 00:09:22.130 --> 00:09:22.140 align:start position:0% how one presents user interfaces and 00:09:22.140 --> 00:09:25.750 align:start position:0% how one presents user interfaces and collects<00:09:22.410> input<00:09:22.740> from<00:09:22.860> the<00:09:23.010> browser<00:09:24.710> the 00:09:25.750 --> 00:09:25.760 align:start position:0% collects input from the browser the 00:09:25.760 --> 00:09:28.610 align:start position:0% collects input from the browser the JavaScript<00:09:26.760> platform<00:09:27.480> is<00:09:27.690> heavily<00:09:28.470> heavily 00:09:28.610 --> 00:09:28.620 align:start position:0% JavaScript platform is heavily heavily 00:09:28.620 --> 00:09:30.800 align:start position:0% JavaScript platform is heavily heavily restricted<00:09:29.310> and<00:09:29.700> it<00:09:29.760> has<00:09:29.880> severe<00:09:30.210> limitations 00:09:30.800 --> 00:09:30.810 align:start position:0% restricted and it has severe limitations 00:09:30.810 --> 00:09:33.110 align:start position:0% restricted and it has severe limitations and<00:09:31.080> it<00:09:31.710> has<00:09:31.920> those<00:09:32.070> limitations<00:09:32.520> because 00:09:33.110 --> 00:09:33.120 align:start position:0% and it has those limitations because 00:09:33.120 --> 00:09:36.230 align:start position:0% and it has those limitations because it's<00:09:33.810> fundamentally<00:09:34.110> for<00:09:34.860> running<00:09:35.580> untrusted 00:09:36.230 --> 00:09:36.240 align:start position:0% it's fundamentally for running untrusted 00:09:36.240 --> 00:09:38.510 align:start position:0% it's fundamentally for running untrusted code<00:09:36.500> people<00:09:37.500> have<00:09:37.650> to<00:09:37.770> believe<00:09:38.040> that<00:09:38.070> if<00:09:38.370> they 00:09:38.510 --> 00:09:38.520 align:start position:0% code people have to believe that if they 00:09:38.520 --> 00:09:40.130 align:start position:0% code people have to believe that if they have<00:09:38.880> JavaScript<00:09:39.420> on<00:09:39.600> and<00:09:39.900> their<00:09:39.990> web<00:09:40.110> browser 00:09:40.130 --> 00:09:40.140 align:start position:0% have JavaScript on and their web browser 00:09:40.140 --> 00:09:44.000 align:start position:0% have JavaScript on and their web browser and<00:09:40.440> they<00:09:40.589> go<00:09:40.860> to<00:09:40.920> a<00:09:41.810> website<00:09:42.810> that<00:09:43.230> the 00:09:44.000 --> 00:09:44.010 align:start position:0% and they go to a website that the 00:09:44.010 --> 00:09:45.470 align:start position:0% and they go to a website that the website<00:09:44.370> will<00:09:44.490> not<00:09:44.550> have<00:09:44.790> access<00:09:44.940> to<00:09:45.330> their 00:09:45.470 --> 00:09:45.480 align:start position:0% website will not have access to their 00:09:45.480 --> 00:09:47.449 align:start position:0% website will not have access to their file<00:09:46.170> their<00:09:46.440> personal<00:09:46.830> files<00:09:47.010> and<00:09:47.250> will<00:09:47.370> not 00:09:47.449 --> 00:09:47.459 align:start position:0% file their personal files and will not 00:09:47.459 --> 00:09:52.269 align:start position:0% file their personal files and will not be<00:09:47.610> able<00:09:47.670> to<00:09:47.760> crash<00:09:47.970> their<00:09:48.209> computer<00:09:48.950> so 00:09:52.269 --> 00:09:52.279 align:start position:0% 00:09:52.279 --> 00:09:54.920 align:start position:0% that's<00:09:53.279> probably<00:09:53.730> the<00:09:53.940> major<00:09:54.240> reason<00:09:54.779> that 00:09:54.920 --> 00:09:54.930 align:start position:0% that's probably the major reason that 00:09:54.930 --> 00:09:57.199 align:start position:0% that's probably the major reason that javascript<00:09:55.529> does<00:09:56.160> not<00:09:56.370> have<00:09:56.730> multiple 00:09:57.199 --> 00:09:57.209 align:start position:0% javascript does not have multiple 00:09:57.209 --> 00:09:59.480 align:start position:0% javascript does not have multiple threads<00:09:57.480> multiple<00:09:58.230> any<00:09:58.770> kind<00:09:59.010> of<00:09:59.040> concurrent 00:09:59.480 --> 00:09:59.490 align:start position:0% threads multiple any kind of concurrent 00:09:59.490 --> 00:10:02.000 align:start position:0% threads multiple any kind of concurrent execution<00:09:59.550> model<00:10:00.300> it's<00:10:00.930> single<00:10:01.290> process<00:10:01.740> and 00:10:02.000 --> 00:10:02.010 align:start position:0% execution model it's single process and 00:10:02.010 --> 00:10:04.490 align:start position:0% execution model it's single process and it<00:10:02.550> has<00:10:02.730> an<00:10:02.970> event<00:10:03.360> loop<00:10:03.660> which<00:10:04.020> is<00:10:04.170> to<00:10:04.320> say 00:10:04.490 --> 00:10:04.500 align:start position:0% it has an event loop which is to say 00:10:04.500 --> 00:10:10.180 align:start position:0% it has an event loop which is to say that<00:10:05.540> inputs<00:10:06.890> can<00:10:07.890> happen<00:10:08.730> in<00:10:08.940> JavaScript<00:10:09.630> but 00:10:10.180 --> 00:10:10.190 align:start position:0% that inputs can happen in JavaScript but 00:10:10.190 --> 00:10:13.280 align:start position:0% that inputs can happen in JavaScript but inputs<00:10:11.190> are<00:10:11.310> in<00:10:11.459> queued<00:10:11.820> on<00:10:12.120> an<00:10:12.690> event<00:10:12.930> queue 00:10:13.280 --> 00:10:13.290 align:start position:0% inputs are in queued on an event queue 00:10:13.290 --> 00:10:18.230 align:start position:0% inputs are in queued on an event queue and<00:10:13.560> that<00:10:14.100> event<00:10:14.370> queue<00:10:15.500> can<00:10:16.500> can<00:10:16.880> can<00:10:17.880> only<00:10:18.029> be 00:10:18.230 --> 00:10:18.240 align:start position:0% and that event queue can can can only be 00:10:18.240 --> 00:10:20.480 align:start position:0% and that event queue can can can only be consumed<00:10:18.810> by<00:10:19.080> one<00:10:19.380> process<00:10:19.950> which<00:10:20.190> is<00:10:20.310> the 00:10:20.480 --> 00:10:20.490 align:start position:0% consumed by one process which is the 00:10:20.490 --> 00:10:25.199 align:start position:0% consumed by one process which is the single<00:10:21.120> JavaScript<00:10:21.660> process 00:10:25.199 --> 00:10:25.209 align:start position:0% 00:10:25.209 --> 00:10:27.869 align:start position:0% so<00:10:25.929> jackal<00:10:26.649> brings<00:10:27.040> to<00:10:27.189> bear<00:10:27.220> in<00:10:27.670> the 00:10:27.869 --> 00:10:27.879 align:start position:0% so jackal brings to bear in the 00:10:27.879 --> 00:10:31.530 align:start position:0% so jackal brings to bear in the JavaScript<00:10:28.499> arena<00:10:29.499> a<00:10:30.189> few<00:10:30.850> a<00:10:30.879> few<00:10:31.269> different 00:10:31.530 --> 00:10:31.540 align:start position:0% JavaScript arena a few a few different 00:10:31.540 --> 00:10:33.749 align:start position:0% JavaScript arena a few a few different tools<00:10:31.660> the<00:10:32.619> first<00:10:32.649> set<00:10:32.980> of<00:10:33.009> tools<00:10:33.249> is<00:10:33.399> related 00:10:33.749 --> 00:10:33.759 align:start position:0% tools the first set of tools is related 00:10:33.759 --> 00:10:36.059 align:start position:0% tools the first set of tools is related to<00:10:33.790> inter<00:10:34.029> operation<00:10:34.600> with<00:10:35.050> JavaScript<00:10:35.800> and<00:10:35.920> I 00:10:36.059 --> 00:10:36.069 align:start position:0% to inter operation with JavaScript and I 00:10:36.069 --> 00:10:38.100 align:start position:0% to inter operation with JavaScript and I mentioned<00:10:36.579> some<00:10:36.759> a<00:10:36.850> few<00:10:37.149> special<00:10:37.480> forms<00:10:37.809> here 00:10:38.100 --> 00:10:38.110 align:start position:0% mentioned some a few special forms here 00:10:38.110 --> 00:10:40.079 align:start position:0% mentioned some a few special forms here that<00:10:38.740> allow<00:10:38.980> one<00:10:39.160> to<00:10:39.220> call<00:10:39.519> JavaScript 00:10:40.079 --> 00:10:40.089 align:start position:0% that allow one to call JavaScript 00:10:40.089 --> 00:10:42.809 align:start position:0% that allow one to call JavaScript functions<00:10:40.449> access<00:10:41.459> JavaScript<00:10:42.459> object 00:10:42.809 --> 00:10:42.819 align:start position:0% functions access JavaScript object 00:10:42.819 --> 00:10:45.090 align:start position:0% functions access JavaScript object fields<00:10:43.240> and<00:10:43.449> to<00:10:43.990> generate<00:10:44.319> obvious<00:10:44.559> arbitrary 00:10:45.090 --> 00:10:45.100 align:start position:0% fields and to generate obvious arbitrary 00:10:45.100 --> 00:10:48.179 align:start position:0% fields and to generate obvious arbitrary JavaScript<00:10:45.519> code<00:10:46.559> there<00:10:47.559> are<00:10:47.679> other<00:10:47.800> aspects 00:10:48.179 --> 00:10:48.189 align:start position:0% JavaScript code there are other aspects 00:10:48.189 --> 00:10:49.559 align:start position:0% JavaScript code there are other aspects of<00:10:48.339> this<00:10:48.429> that<00:10:48.610> aren't<00:10:48.759> on<00:10:48.910> the<00:10:48.999> slide<00:10:49.209> like 00:10:49.559 --> 00:10:49.569 align:start position:0% of this that aren't on the slide like 00:10:49.569 --> 00:10:54.090 align:start position:0% of this that aren't on the slide like you<00:10:50.499> know<00:10:50.679> the<00:10:51.429> jackal<00:10:51.910> numeric<00:10:52.660> type<00:10:52.959> the<00:10:53.559> fix 00:10:54.090 --> 00:10:54.100 align:start position:0% you know the jackal numeric type the fix 00:10:54.100 --> 00:10:56.160 align:start position:0% you know the jackal numeric type the fix num<00:10:54.279> is<00:10:54.550> a<00:10:54.999> JavaScript<00:10:55.809> floating-point 00:10:56.160 --> 00:10:56.170 align:start position:0% num is a JavaScript floating-point 00:10:56.170 --> 00:11:00.239 align:start position:0% num is a JavaScript floating-point number<00:10:57.540> so<00:10:58.540> the<00:10:59.290> relationship<00:10:59.829> there<00:10:59.980> is<00:11:00.069> very 00:11:00.239 --> 00:11:00.249 align:start position:0% number so the relationship there is very 00:11:00.249 --> 00:11:02.429 align:start position:0% number so the relationship there is very tight<00:11:00.519> and<00:11:00.999> it's<00:11:01.480> actually<00:11:01.809> that<00:11:02.079> tightness 00:11:02.429 --> 00:11:02.439 align:start position:0% tight and it's actually that tightness 00:11:02.439 --> 00:11:05.549 align:start position:0% tight and it's actually that tightness is<00:11:02.829> an<00:11:03.069> effort<00:11:03.699> towards<00:11:03.850> efficiency<00:11:04.509> since<00:11:05.410> I 00:11:05.549 --> 00:11:05.559 align:start position:0% is an effort towards efficiency since I 00:11:05.559 --> 00:11:07.679 align:start position:0% is an effort towards efficiency since I don't<00:11:05.769> need<00:11:06.399> to<00:11:06.550> ship<00:11:06.790> my<00:11:07.509> own 00:11:07.679 --> 00:11:07.689 align:start position:0% don't need to ship my own 00:11:07.689 --> 00:11:10.799 align:start position:0% don't need to ship my own implementations<00:11:08.529> of<00:11:08.649> things<00:11:08.829> like<00:11:09.809> fixed 00:11:10.799 --> 00:11:10.809 align:start position:0% implementations of things like fixed 00:11:10.809 --> 00:11:14.730 align:start position:0% implementations of things like fixed noms<00:11:10.959> or<00:11:11.259> flown<00:11:11.709> ohms<00:11:12.629> but<00:11:13.629> that<00:11:14.139> level<00:11:14.649> of 00:11:14.730 --> 00:11:14.740 align:start position:0% noms or flown ohms but that level of 00:11:14.740 --> 00:11:16.710 align:start position:0% noms or flown ohms but that level of integration<00:11:14.980> is<00:11:15.550> also<00:11:15.879> primarily<00:11:16.179> what<00:11:16.569> will 00:11:16.710 --> 00:11:16.720 align:start position:0% integration is also primarily what will 00:11:16.720 --> 00:11:19.319 align:start position:0% integration is also primarily what will preclude<00:11:17.249> jackal<00:11:18.249> from<00:11:18.429> becoming<00:11:18.819> any<00:11:19.089> kind 00:11:19.319 --> 00:11:19.329 align:start position:0% preclude jackal from becoming any kind 00:11:19.329 --> 00:11:22.549 align:start position:0% preclude jackal from becoming any kind of<00:11:19.480> you<00:11:20.410> know<00:11:20.529> a<00:11:20.790> compliant<00:11:21.790> conforming 00:11:22.549 --> 00:11:22.559 align:start position:0% of you know a compliant conforming 00:11:22.559 --> 00:11:26.299 align:start position:0% of you know a compliant conforming implementation<00:11:23.559> javascript<00:11:24.339> is<00:11:24.429> just<00:11:24.610> too 00:11:26.299 --> 00:11:26.309 align:start position:0% implementation javascript is just too 00:11:26.309 --> 00:11:28.439 align:start position:0% implementation javascript is just too too<00:11:27.309> restrictive<00:11:27.790> for<00:11:27.819> that's<00:11:28.059> ever<00:11:28.269> be 00:11:28.439 --> 00:11:28.449 align:start position:0% too restrictive for that's ever be 00:11:28.449 --> 00:11:33.749 align:start position:0% too restrictive for that's ever be possible<00:11:30.569> another<00:11:31.569> the<00:11:31.839> second<00:11:32.199> major<00:11:32.759> aspect 00:11:33.749 --> 00:11:33.759 align:start position:0% possible another the second major aspect 00:11:33.759 --> 00:11:35.549 align:start position:0% possible another the second major aspect of<00:11:33.850> jackal<00:11:34.269> is<00:11:34.449> that<00:11:34.749> it<00:11:34.929> needs<00:11:35.079> to<00:11:35.170> be<00:11:35.230> able<00:11:35.319> to 00:11:35.549 --> 00:11:35.559 align:start position:0% of jackal is that it needs to be able to 00:11:35.559 --> 00:11:38.699 align:start position:0% of jackal is that it needs to be able to make<00:11:35.709> small<00:11:35.949> and<00:11:36.459> efficient<00:11:36.790> code<00:11:37.199> as<00:11:38.199> I 00:11:38.699 --> 00:11:38.709 align:start position:0% make small and efficient code as I 00:11:38.709 --> 00:11:39.960 align:start position:0% make small and efficient code as I mentioned<00:11:38.980> earlier<00:11:39.220> I<00:11:39.279> want<00:11:39.490> to<00:11:39.549> use<00:11:39.639> this<00:11:39.790> at 00:11:39.960 --> 00:11:39.970 align:start position:0% mentioned earlier I want to use this at 00:11:39.970 --> 00:11:41.369 align:start position:0% mentioned earlier I want to use this at work<00:11:40.119> someday<00:11:40.389> and<00:11:40.779> needs<00:11:40.929> to<00:11:40.990> be<00:11:41.079> competitive 00:11:41.369 --> 00:11:41.379 align:start position:0% work someday and needs to be competitive 00:11:41.379 --> 00:11:45.689 align:start position:0% work someday and needs to be competitive with<00:11:41.769> whatever<00:11:43.319> language<00:11:44.319> to<00:11:44.499> your<00:11:44.649> people<00:11:45.579> in 00:11:45.689 --> 00:11:45.699 align:start position:0% with whatever language to your people in 00:11:45.699 --> 00:11:48.749 align:start position:0% with whatever language to your people in that<00:11:45.790> in<00:11:45.939> my<00:11:46.089> field<00:11:46.240> are<00:11:46.449> using<00:11:46.749> and<00:11:47.549> I<00:11:48.549> learned 00:11:48.749 --> 00:11:48.759 align:start position:0% that in my field are using and I learned 00:11:48.759 --> 00:11:50.369 align:start position:0% that in my field are using and I learned from<00:11:48.879> the<00:11:48.999> closure<00:11:49.179> script<00:11:49.509> experience<00:11:50.019> that 00:11:50.369 --> 00:11:50.379 align:start position:0% from the closure script experience that 00:11:50.379 --> 00:11:53.400 align:start position:0% from the closure script experience that I<00:11:50.709> don't<00:11:51.249> necessarily<00:11:51.399> need<00:11:52.149> to<00:11:52.209> be<00:11:52.410> the 00:11:53.400 --> 00:11:53.410 align:start position:0% I don't necessarily need to be the 00:11:53.410 --> 00:11:55.079 align:start position:0% I don't necessarily need to be the person<00:11:53.589> who<00:11:53.920> writes<00:11:54.399> those<00:11:54.639> optimizations 00:11:55.079 --> 00:11:55.089 align:start position:0% person who writes those optimizations 00:11:55.089 --> 00:11:56.759 align:start position:0% person who writes those optimizations because<00:11:55.839> I<00:11:56.019> just<00:11:56.199> need<00:11:56.319> to<00:11:56.439> generate 00:11:56.759 --> 00:11:56.769 align:start position:0% because I just need to generate 00:11:56.769 --> 00:11:58.410 align:start position:0% because I just need to generate JavaScript<00:11:57.339> that<00:11:57.519> other<00:11:57.759> JavaScript 00:11:58.410 --> 00:11:58.420 align:start position:0% JavaScript that other JavaScript 00:11:58.420 --> 00:12:01.079 align:start position:0% JavaScript that other JavaScript optimizers<00:11:58.990> can<00:11:59.199> understand<00:11:59.679> and<00:11:59.980> this<00:12:00.910> is 00:12:01.079 --> 00:12:01.089 align:start position:0% optimizers can understand and this is 00:12:01.089 --> 00:12:02.819 align:start position:0% optimizers can understand and this is great<00:12:01.360> as<00:12:01.990> you<00:12:02.259> know<00:12:02.379> an<00:12:02.439> individual 00:12:02.819 --> 00:12:02.829 align:start position:0% great as you know an individual 00:12:02.829 --> 00:12:04.559 align:start position:0% great as you know an individual contributors<00:12:03.369> this<00:12:03.579> is<00:12:03.639> my<00:12:03.730> personal<00:12:04.119> project 00:12:04.559 --> 00:12:04.569 align:start position:0% contributors this is my personal project 00:12:04.569 --> 00:12:06.419 align:start position:0% contributors this is my personal project this<00:12:05.259> means<00:12:05.499> that<00:12:05.649> I<00:12:05.709> can<00:12:05.889> focus<00:12:06.069> on<00:12:06.309> other 00:12:06.419 --> 00:12:06.429 align:start position:0% this means that I can focus on other 00:12:06.429 --> 00:12:09.650 align:start position:0% this means that I can focus on other parts<00:12:06.790> that<00:12:06.850> of<00:12:07.299> the<00:12:07.569> codebase<00:12:08.049> and<00:12:08.519> defer 00:12:09.650 --> 00:12:09.660 align:start position:0% parts that of the codebase and defer 00:12:09.660 --> 00:12:12.030 align:start position:0% parts that of the codebase and defer optimizations<00:12:10.660> to<00:12:10.839> third-party<00:12:11.049> tools<00:12:11.499> which 00:12:12.030 --> 00:12:12.040 align:start position:0% optimizations to third-party tools which 00:12:12.040 --> 00:12:16.230 align:start position:0% optimizations to third-party tools which are<00:12:12.160> excellent<00:12:14.279> the<00:12:15.279> third<00:12:15.639> thing<00:12:15.910> that 00:12:16.230 --> 00:12:16.240 align:start position:0% are excellent the third thing that 00:12:16.240 --> 00:12:18.210 align:start position:0% are excellent the third thing that jackal<00:12:16.809> focuses<00:12:17.470> on<00:12:17.619> which<00:12:17.799> is<00:12:17.949> the<00:12:18.040> most 00:12:18.210 --> 00:12:18.220 align:start position:0% jackal focuses on which is the most 00:12:18.220 --> 00:12:19.949 align:start position:0% jackal focuses on which is the most speculative<00:12:18.790> but<00:12:19.179> also<00:12:19.420> maybe<00:12:19.629> the<00:12:19.839> most 00:12:19.949 --> 00:12:19.959 align:start position:0% speculative but also maybe the most 00:12:19.959 --> 00:12:22.139 align:start position:0% speculative but also maybe the most interesting<00:12:20.139> is<00:12:20.740> that<00:12:21.490> I<00:12:21.519> have<00:12:21.819> this<00:12:21.939> idea 00:12:22.139 --> 00:12:22.149 align:start position:0% interesting is that I have this idea 00:12:22.149 --> 00:12:26.309 align:start position:0% interesting is that I have this idea that<00:12:22.720> there<00:12:23.319> is<00:12:23.589> advantage<00:12:24.429> to<00:12:24.790> doing<00:12:25.720> what 00:12:26.309 --> 00:12:26.319 align:start position:0% that there is advantage to doing what 00:12:26.319 --> 00:12:28.289 align:start position:0% that there is advantage to doing what has<00:12:26.439> been<00:12:26.470> called<00:12:26.769> residential<00:12:27.429> development 00:12:28.289 --> 00:12:28.299 align:start position:0% has been called residential development 00:12:28.299 --> 00:12:30.019 align:start position:0% has been called residential development and<00:12:28.420> residential<00:12:29.139> development<00:12:29.170> is<00:12:29.799> a 00:12:30.019 --> 00:12:30.029 align:start position:0% and residential development is a 00:12:30.029 --> 00:12:33.230 align:start position:0% and residential development is a development<00:12:31.029> workflow<00:12:31.749> and<00:12:32.139> sort<00:12:32.439> of<00:12:32.470> ethos 00:12:33.230 --> 00:12:33.240 align:start position:0% development workflow and sort of ethos 00:12:33.240 --> 00:12:36.059 align:start position:0% development workflow and sort of ethos characterized<00:12:34.240> by<00:12:34.509> this<00:12:34.569> idea<00:12:34.809> of<00:12:35.069> closely 00:12:36.059 --> 00:12:36.069 align:start position:0% characterized by this idea of closely 00:12:36.069 --> 00:12:37.660 align:start position:0% characterized by this idea of closely integrating<00:12:36.669> the<00:12:36.819> runtime 00:12:37.660 --> 00:12:37.670 align:start position:0% integrating the runtime 00:12:37.670 --> 00:12:41.980 align:start position:0% integrating the runtime and<00:12:37.760> the<00:12:38.480> development<00:12:40.120> environments<00:12:41.120> so<00:12:41.810> the 00:12:41.980 --> 00:12:41.990 align:start position:0% and the development environments so the 00:12:41.990 --> 00:12:43.600 align:start position:0% and the development environments so the same<00:12:42.200> tools<00:12:42.500> that<00:12:42.830> you<00:12:42.920> use<00:12:43.070> to<00:12:43.250> build<00:12:43.460> your 00:12:43.600 --> 00:12:43.610 align:start position:0% same tools that you use to build your 00:12:43.610 --> 00:12:45.100 align:start position:0% same tools that you use to build your application<00:12:44.300> might<00:12:44.480> be<00:12:44.630> tools<00:12:44.870> that<00:12:45.050> you 00:12:45.100 --> 00:12:45.110 align:start position:0% application might be tools that you 00:12:45.110 --> 00:12:46.660 align:start position:0% application might be tools that you would<00:12:45.200> use<00:12:45.260> in<00:12:45.500> the<00:12:45.590> application<00:12:45.680> itself<00:12:46.400> and 00:12:46.660 --> 00:12:46.670 align:start position:0% would use in the application itself and 00:12:46.670 --> 00:12:49.240 align:start position:0% would use in the application itself and the<00:12:47.210> line<00:12:47.450> between<00:12:47.720> application<00:12:48.650> and<00:12:48.830> tooling 00:12:49.240 --> 00:12:49.250 align:start position:0% the line between application and tooling 00:12:49.250 --> 00:12:53.350 align:start position:0% the line between application and tooling is<00:12:49.460> very<00:12:50.090> fuzzy<00:12:51.760> interesting<00:12:52.760> consequences 00:12:53.350 --> 00:12:53.360 align:start position:0% is very fuzzy interesting consequences 00:12:53.360 --> 00:12:56.550 align:start position:0% is very fuzzy interesting consequences of<00:12:53.540> this<00:12:53.750> include<00:12:54.620> the<00:12:55.490> idea<00:12:55.760> that 00:12:56.550 --> 00:12:56.560 align:start position:0% of this include the idea that 00:12:56.560 --> 00:12:59.200 align:start position:0% of this include the idea that development<00:12:57.560> tools<00:12:57.740> can<00:12:58.460> inhabit<00:12:59.090> the 00:12:59.200 --> 00:12:59.210 align:start position:0% development tools can inhabit the 00:12:59.210 --> 00:13:01.690 align:start position:0% development tools can inhabit the application<00:12:59.870> through<00:13:00.470> to<00:13:00.800> deployment<00:13:01.430> and 00:13:01.690 --> 00:13:01.700 align:start position:0% application through to deployment and 00:13:01.700 --> 00:13:07.120 align:start position:0% application through to deployment and even<00:13:01.940> after<00:13:04.660> small<00:13:05.660> talk<00:13:05.870> and<00:13:06.140> Lisp<00:13:06.620> both 00:13:07.120 --> 00:13:07.130 align:start position:0% even after small talk and Lisp both 00:13:07.130 --> 00:13:08.980 align:start position:0% even after small talk and Lisp both historically<00:13:07.970> supported<00:13:08.240> this<00:13:08.660> kind<00:13:08.930> of 00:13:08.980 --> 00:13:08.990 align:start position:0% historically supported this kind of 00:13:08.990 --> 00:13:15.400 align:start position:0% historically supported this kind of development<00:13:10.060> although<00:13:11.110> an<00:13:12.220> IDE<00:13:13.220> like<00:13:14.050> a<00:13:15.050> lisp 00:13:15.400 --> 00:13:15.410 align:start position:0% development although an IDE like a lisp 00:13:15.410 --> 00:13:17.440 align:start position:0% development although an IDE like a lisp machine<00:13:15.470> or<00:13:16.100> a<00:13:16.430> small<00:13:16.700> talk<00:13:16.880> environment<00:13:17.360> is 00:13:17.440 --> 00:13:17.450 align:start position:0% machine or a small talk environment is 00:13:17.450 --> 00:13:19.630 align:start position:0% machine or a small talk environment is not<00:13:17.660> really<00:13:18.110> in<00:13:18.320> my<00:13:18.620> personal<00:13:19.130> scope<00:13:19.430> that's 00:13:19.630 --> 00:13:19.640 align:start position:0% not really in my personal scope that's 00:13:19.640 --> 00:13:20.830 align:start position:0% not really in my personal scope that's just<00:13:19.790> a<00:13:19.850> little<00:13:20.030> more<00:13:20.210> work<00:13:20.390> that<00:13:20.540> I'm<00:13:20.630> willing 00:13:20.830 --> 00:13:20.840 align:start position:0% just a little more work that I'm willing 00:13:20.840 --> 00:13:22.690 align:start position:0% just a little more work that I'm willing to<00:13:20.870> take<00:13:21.080> on<00:13:21.260> and<00:13:22.070> I'm<00:13:22.280> not<00:13:22.400> particularly 00:13:22.690 --> 00:13:22.700 align:start position:0% to take on and I'm not particularly 00:13:22.700 --> 00:13:25.930 align:start position:0% to take on and I'm not particularly interested<00:13:23.360> in<00:13:23.600> doing<00:13:23.840> that<00:13:23.960> but<00:13:24.800> I<00:13:25.220> think 00:13:25.930 --> 00:13:25.940 align:start position:0% interested in doing that but I think 00:13:25.940 --> 00:13:27.100 align:start position:0% interested in doing that but I think there<00:13:26.180> might<00:13:26.270> be<00:13:26.330> advantaged<00:13:26.780> in<00:13:26.900> not 00:13:27.100 --> 00:13:27.110 align:start position:0% there might be advantaged in not 00:13:27.110 --> 00:13:31.300 align:start position:0% there might be advantaged in not precluding<00:13:27.830> that<00:13:28.270> because<00:13:29.830> whatever<00:13:30.830> tools<00:13:31.190> I 00:13:31.300 --> 00:13:31.310 align:start position:0% precluding that because whatever tools I 00:13:31.310 --> 00:13:33.460 align:start position:0% precluding that because whatever tools I develop<00:13:31.700> would<00:13:31.940> converge<00:13:32.390> on<00:13:32.690> an<00:13:32.990> integrated 00:13:33.460 --> 00:13:33.470 align:start position:0% develop would converge on an integrated 00:13:33.470 --> 00:13:35.920 align:start position:0% develop would converge on an integrated development<00:13:34.310> environment<00:13:34.850> and<00:13:35.000> I<00:13:35.690> just 00:13:35.920 --> 00:13:35.930 align:start position:0% development environment and I just 00:13:35.930 --> 00:13:37.360 align:start position:0% development environment and I just wouldn't<00:13:36.260> want<00:13:36.380> to<00:13:36.500> make<00:13:36.620> that<00:13:36.800> kind<00:13:37.130> of<00:13:37.220> thing 00:13:37.360 --> 00:13:37.370 align:start position:0% wouldn't want to make that kind of thing 00:13:37.370 --> 00:13:39.640 align:start position:0% wouldn't want to make that kind of thing impossible<00:13:38.090> and<00:13:38.300> in<00:13:38.960> the<00:13:39.050> meantime<00:13:39.200> I 00:13:39.640 --> 00:13:39.650 align:start position:0% impossible and in the meantime I 00:13:39.650 --> 00:13:42.610 align:start position:0% impossible and in the meantime I personally<00:13:40.280> use<00:13:40.460> a<00:13:40.660> Emacs<00:13:41.660> with<00:13:41.960> a<00:13:41.990> network 00:13:42.610 --> 00:13:42.620 align:start position:0% personally use a Emacs with a network 00:13:42.620 --> 00:13:46.840 align:start position:0% personally use a Emacs with a network repple<00:13:43.010> which<00:13:43.190> I'll<00:13:43.340> demonstrate<00:13:45.520> so<00:13:46.520> I 00:13:46.840 --> 00:13:46.850 align:start position:0% repple which I'll demonstrate so I 00:13:46.850 --> 00:13:48.700 align:start position:0% repple which I'll demonstrate so I mentioned<00:13:47.150> that<00:13:47.360> the<00:13:47.570> a<00:13:47.780> asynchronous<00:13:48.500> reader 00:13:48.700 --> 00:13:48.710 align:start position:0% mentioned that the a asynchronous reader 00:13:48.710 --> 00:13:50.320 align:start position:0% mentioned that the a asynchronous reader was<00:13:48.920> kind<00:13:49.130> of<00:13:49.160> a<00:13:49.280> banner<00:13:49.460> feature<00:13:50.000> in 00:13:50.320 --> 00:13:50.330 align:start position:0% was kind of a banner feature in 00:13:50.330 --> 00:13:51.730 align:start position:0% was kind of a banner feature in Jaqueline<00:13:50.870> and<00:13:51.050> the<00:13:51.110> reason<00:13:51.380> for<00:13:51.410> that<00:13:51.530> is 00:13:51.730 --> 00:13:51.740 align:start position:0% Jaqueline and the reason for that is 00:13:51.740 --> 00:13:53.290 align:start position:0% Jaqueline and the reason for that is kind<00:13:52.130> of<00:13:52.160> a<00:13:52.220> linchpin<00:13:52.700> of<00:13:52.730> the<00:13:52.940> residential 00:13:53.290 --> 00:13:53.300 align:start position:0% kind of a linchpin of the residential 00:13:53.300 --> 00:13:55.840 align:start position:0% kind of a linchpin of the residential development<00:13:53.950> environment<00:13:54.950> workflow 00:13:55.840 --> 00:13:55.850 align:start position:0% development environment workflow 00:13:55.850 --> 00:13:59.350 align:start position:0% development environment workflow experiment<00:13:57.640> the<00:13:58.640> fundamental<00:13:59.060> problem<00:13:59.330> here 00:13:59.350 --> 00:13:59.360 align:start position:0% experiment the fundamental problem here 00:13:59.360 --> 00:14:02.620 align:start position:0% experiment the fundamental problem here is<00:13:59.600> Java<00:13:59.840> scripts<00:14:00.200> model<00:14:00.530> of<00:14:00.650> input<00:14:01.300> input<00:14:02.300> can 00:14:02.620 --> 00:14:02.630 align:start position:0% is Java scripts model of input input can 00:14:02.630 --> 00:14:04.570 align:start position:0% is Java scripts model of input input can only<00:14:02.750> be<00:14:02.930> consumed<00:14:03.410> asynchronously<00:14:04.220> via 00:14:04.570 --> 00:14:04.580 align:start position:0% only be consumed asynchronously via 00:14:04.580 --> 00:14:08.200 align:start position:0% only be consumed asynchronously via callback<00:14:05.090> so<00:14:05.990> if<00:14:06.560> one<00:14:07.130> were<00:14:07.250> to<00:14:07.280> say<00:14:07.430> consume 00:14:08.200 --> 00:14:08.210 align:start position:0% callback so if one were to say consume 00:14:08.210 --> 00:14:11.560 align:start position:0% callback so if one were to say consume characters<00:14:08.810> in<00:14:08.990> JavaScript<00:14:10.210> you<00:14:11.210> wouldn't<00:14:11.480> be 00:14:11.560 --> 00:14:11.570 align:start position:0% characters in JavaScript you wouldn't be 00:14:11.570 --> 00:14:13.750 align:start position:0% characters in JavaScript you wouldn't be able<00:14:11.630> to<00:14:11.780> read<00:14:12.080> new<00:14:12.350> characters<00:14:12.950> from<00:14:13.460> some 00:14:13.750 --> 00:14:13.760 align:start position:0% able to read new characters from some 00:14:13.760 --> 00:14:16.810 align:start position:0% able to read new characters from some input<00:14:14.120> source<00:14:14.380> until<00:14:15.380> your<00:14:16.190> code<00:14:16.520> is<00:14:16.670> done 00:14:16.810 --> 00:14:16.820 align:start position:0% input source until your code is done 00:14:16.820 --> 00:14:18.820 align:start position:0% input source until your code is done running<00:14:17.090> because<00:14:17.870> there's<00:14:18.020> a<00:14:18.080> single<00:14:18.350> process 00:14:18.820 --> 00:14:18.830 align:start position:0% running because there's a single process 00:14:18.830 --> 00:14:21.460 align:start position:0% running because there's a single process code<00:14:19.700> can<00:14:19.880> only<00:14:19.940> because<00:14:20.330> objects<00:14:21.230> would<00:14:21.320> only 00:14:21.460 --> 00:14:21.470 align:start position:0% code can only because objects would only 00:14:21.470 --> 00:14:23.500 align:start position:0% code can only because objects would only be<00:14:21.650> consumed<00:14:21.950> from<00:14:22.100> the<00:14:22.280> event<00:14:22.730> loop<00:14:22.910> of<00:14:23.390> the 00:14:23.500 --> 00:14:23.510 align:start position:0% be consumed from the event loop of the 00:14:23.510 --> 00:14:27.580 align:start position:0% be consumed from the event loop of the event<00:14:23.720> queue<00:14:24.070> once<00:14:25.070> the<00:14:25.250> stack<00:14:25.490> is<00:14:26.120> empty<00:14:26.590> so 00:14:27.580 --> 00:14:27.590 align:start position:0% event queue once the stack is empty so 00:14:27.590 --> 00:14:30.220 align:start position:0% event queue once the stack is empty so there's<00:14:27.800> no<00:14:27.920> blocking<00:14:28.600> which<00:14:29.600> means<00:14:29.870> that<00:14:30.140> the 00:14:30.220 --> 00:14:30.230 align:start position:0% there's no blocking which means that the 00:14:30.230 --> 00:14:32.140 align:start position:0% there's no blocking which means that the straightforward<00:14:30.980> traditional<00:14:31.730> approach<00:14:31.970> to 00:14:32.140 --> 00:14:32.150 align:start position:0% straightforward traditional approach to 00:14:32.150 --> 00:14:35.590 align:start position:0% straightforward traditional approach to a<00:14:32.180> lisp<00:14:32.390> reader<00:14:32.630> is<00:14:32.900> not<00:14:33.110> really<00:14:34.600> effective 00:14:35.590 --> 00:14:35.600 align:start position:0% a lisp reader is not really effective 00:14:35.600 --> 00:14:37.900 align:start position:0% a lisp reader is not really effective because<00:14:36.260> you<00:14:36.530> can<00:14:36.890> make<00:14:37.040> a<00:14:37.100> lisp<00:14:37.400> reader<00:14:37.640> in 00:14:37.900 --> 00:14:37.910 align:start position:0% because you can make a lisp reader in 00:14:37.910 --> 00:14:40.000 align:start position:0% because you can make a lisp reader in the<00:14:38.090> traditional<00:14:38.510> style<00:14:38.690> but<00:14:39.530> it<00:14:39.650> will<00:14:39.740> block 00:14:40.000 --> 00:14:40.010 align:start position:0% the traditional style but it will block 00:14:40.010 --> 00:14:42.280 align:start position:0% the traditional style but it will block everything<00:14:40.550> else<00:14:40.730> in<00:14:41.030> the<00:14:41.450> browser<00:14:41.630> tab<00:14:41.960> and 00:14:42.280 --> 00:14:42.290 align:start position:0% everything else in the browser tab and 00:14:42.290 --> 00:14:45.630 align:start position:0% everything else in the browser tab and your<00:14:42.920> program<00:14:43.220> could<00:14:43.370> be<00:14:43.430> deadlocked<00:14:43.760> easily 00:14:45.630 --> 00:14:45.640 align:start position:0% your program could be deadlocked easily 00:14:45.640 --> 00:14:49.240 align:start position:0% your program could be deadlocked easily so<00:14:46.640> in<00:14:47.000> jackal<00:14:47.720> what<00:14:48.170> we<00:14:48.260> do<00:14:48.440> is<00:14:48.710> we<00:14:49.040> have<00:14:49.160> an 00:14:49.240 --> 00:14:49.250 align:start position:0% so in jackal what we do is we have an 00:14:49.250 --> 00:14:51.160 align:start position:0% so in jackal what we do is we have an asynchronous<00:14:49.610> reader<00:14:50.090> abstraction<00:14:50.840> which 00:14:51.160 --> 00:14:51.170 align:start position:0% asynchronous reader abstraction which 00:14:51.170 --> 00:14:52.720 align:start position:0% asynchronous reader abstraction which it's<00:14:51.529> a<00:14:51.649> stateful<00:14:51.889> object<00:14:52.370> you<00:14:52.490> instantiate 00:14:52.720 --> 00:14:52.730 align:start position:0% it's a stateful object you instantiate 00:14:52.730 --> 00:14:55.750 align:start position:0% it's a stateful object you instantiate one<00:14:53.089> of<00:14:53.149> these<00:14:53.269> asynchronous<00:14:53.540> readers<00:14:54.050> and<00:14:54.760> it 00:14:55.750 --> 00:14:55.760 align:start position:0% one of these asynchronous readers and it 00:14:55.760 --> 00:14:57.759 align:start position:0% one of these asynchronous readers and it has<00:14:56.209> a<00:14:56.240> method<00:14:56.600> for<00:14:56.720> pushing<00:14:57.079> characters<00:14:57.470> into 00:14:57.759 --> 00:14:57.769 align:start position:0% has a method for pushing characters into 00:14:57.769 --> 00:14:59.579 align:start position:0% has a method for pushing characters into it<00:14:57.889> and<00:14:58.040> every<00:14:58.310> time<00:14:58.490> you<00:14:58.610> call<00:14:58.970> the<00:14:59.120> method 00:14:59.579 --> 00:14:59.589 align:start position:0% it and every time you call the method 00:14:59.589 --> 00:15:02.110 align:start position:0% it and every time you call the method and<00:15:00.589> push<00:15:00.829> characters<00:15:01.339> internally 00:15:02.110 --> 00:15:02.120 align:start position:0% and push characters internally 00:15:02.120 --> 00:15:03.970 align:start position:0% and push characters internally incrementally<00:15:02.899> it<00:15:03.110> parses<00:15:03.649> with<00:15:03.860> an 00:15:03.970 --> 00:15:03.980 align:start position:0% incrementally it parses with an 00:15:03.980 --> 00:15:06.100 align:start position:0% incrementally it parses with an incremental<00:15:04.399> it's<00:15:04.820> an<00:15:04.970> online<00:15:05.149> incremental 00:15:06.100 --> 00:15:06.110 align:start position:0% incremental it's an online incremental 00:15:06.110 --> 00:15:09.850 align:start position:0% incremental it's an online incremental parser<00:15:06.470> and<00:15:07.360> when<00:15:08.360> it's<00:15:08.540> accumulated<00:15:08.899> a<00:15:09.410> data 00:15:09.850 --> 00:15:09.860 align:start position:0% parser and when it's accumulated a data 00:15:09.860 --> 00:15:12.310 align:start position:0% parser and when it's accumulated a data structure<00:15:10.220> with<00:15:10.370> it<00:15:10.490> that's<00:15:10.670> a<00:15:10.760> list<00:15:11.000> or<00:15:11.360> a 00:15:12.310 --> 00:15:12.320 align:start position:0% structure with it that's a list or a 00:15:12.320 --> 00:15:14.110 align:start position:0% structure with it that's a list or a symbol<00:15:12.589> or<00:15:12.800> whatever<00:15:12.949> it<00:15:13.550> will<00:15:13.730> invoke<00:15:14.060> a 00:15:14.110 --> 00:15:14.120 align:start position:0% symbol or whatever it will invoke a 00:15:14.120 --> 00:15:19.860 align:start position:0% symbol or whatever it will invoke a callback<00:15:14.420> with<00:15:14.899> that<00:15:15.079> data<00:15:15.410> structure<00:15:17.050> so 00:15:19.860 --> 00:15:19.870 align:start position:0% callback with that data structure so 00:15:19.870 --> 00:15:22.590 align:start position:0% callback with that data structure so next<00:15:20.870> up<00:15:21.050> is<00:15:21.170> a<00:15:21.230> demonstration<00:15:21.529> and<00:15:22.070> I'll<00:15:22.310> show 00:15:22.590 --> 00:15:22.600 align:start position:0% next up is a demonstration and I'll show 00:15:22.600 --> 00:15:26.920 align:start position:0% next up is a demonstration and I'll show interaction<00:15:23.600> in<00:15:23.690> the<00:15:23.779> browser<00:15:23.990> and<00:15:25.810> what<00:15:26.810> you 00:15:26.920 --> 00:15:26.930 align:start position:0% interaction in the browser and what you 00:15:26.930 --> 00:15:28.750 align:start position:0% interaction in the browser and what you other<00:15:27.199> sort<00:15:27.860> of<00:15:27.889> what<00:15:28.070> it<00:15:28.160> looks<00:15:28.310> like<00:15:28.459> to<00:15:28.579> run 00:15:28.750 --> 00:15:28.760 align:start position:0% other sort of what it looks like to run 00:15:28.760 --> 00:15:30.189 align:start position:0% other sort of what it looks like to run Jackel<00:15:29.089> in<00:15:29.149> the<00:15:29.240> browser<00:15:29.420> and<00:15:29.839> I'll<00:15:29.990> show<00:15:30.170> the 00:15:30.189 --> 00:15:30.199 align:start position:0% Jackel in the browser and I'll show the 00:15:30.199 --> 00:15:32.680 align:start position:0% Jackel in the browser and I'll show the integration<00:15:30.800> with<00:15:31.160> JavaScript<00:15:31.760> and<00:15:32.570> we'll 00:15:32.680 --> 00:15:32.690 align:start position:0% integration with JavaScript and we'll 00:15:32.690 --> 00:15:35.500 align:start position:0% integration with JavaScript and we'll show<00:15:32.839> the<00:15:32.959> asynchronous<00:15:33.769> reader<00:15:34.160> and<00:15:34.510> then 00:15:35.500 --> 00:15:35.510 align:start position:0% show the asynchronous reader and then 00:15:35.510 --> 00:15:38.470 align:start position:0% show the asynchronous reader and then I'll<00:15:35.779> show<00:15:36.110> what<00:15:37.100> the<00:15:37.579> development 00:15:38.470 --> 00:15:38.480 align:start position:0% I'll show what the development 00:15:38.480 --> 00:15:40.540 align:start position:0% I'll show what the development experience<00:15:39.050> currently<00:15:39.470> looks<00:15:39.649> like<00:15:39.740> using 00:15:40.540 --> 00:15:40.550 align:start position:0% experience currently looks like using 00:15:40.550 --> 00:15:42.879 align:start position:0% experience currently looks like using this<00:15:40.850> Jackal<00:15:41.300> ripple<00:15:41.630> client<00:15:42.019> connecting<00:15:42.769> to 00:15:42.879 --> 00:15:42.889 align:start position:0% this Jackal ripple client connecting to 00:15:42.889 --> 00:15:50.350 align:start position:0% this Jackal ripple client connecting to a<00:15:42.920> remote<00:15:43.010> browser<00:15:43.610> and<00:15:43.880> evaluating<00:15:49.060> okay<00:15:50.060> we 00:15:50.350 --> 00:15:50.360 align:start position:0% a remote browser and evaluating okay we 00:15:50.360 --> 00:15:55.030 align:start position:0% a remote browser and evaluating okay we are<00:15:50.510> back<00:15:50.779> now<00:15:51.139> with<00:15:51.529> a<00:15:51.940> demonstration<00:15:54.040> so 00:15:55.030 --> 00:15:55.040 align:start position:0% are back now with a demonstration so 00:15:55.040 --> 00:15:56.740 align:start position:0% are back now with a demonstration so over<00:15:55.579> on<00:15:55.610> the<00:15:55.730> left<00:15:55.910> hand<00:15:56.060> side<00:15:56.300> here<00:15:56.540> we've 00:15:56.740 --> 00:15:56.750 align:start position:0% over on the left hand side here we've 00:15:56.750 --> 00:16:00.130 align:start position:0% over on the left hand side here we've got<00:15:56.959> a<00:15:57.019> terminal<00:15:57.640> open<00:15:58.640> and<00:15:58.880> I'm<00:15:59.449> running<00:15:59.810> a 00:16:00.130 --> 00:16:00.140 align:start position:0% got a terminal open and I'm running a 00:16:00.140 --> 00:16:03.189 align:start position:0% got a terminal open and I'm running a local<00:16:00.800> web<00:16:01.640> server<00:16:01.670> on<00:16:02.089> port<00:16:02.120> 8000<00:16:02.899> from<00:16:03.110> the 00:16:03.189 --> 00:16:03.199 align:start position:0% local web server on port 8000 from the 00:16:03.199 --> 00:16:06.699 align:start position:0% local web server on port 8000 from the Jackal<00:16:03.560> distribution<00:16:04.810> directory<00:16:05.810> and<00:16:06.470> on<00:16:06.620> the 00:16:06.699 --> 00:16:06.709 align:start position:0% Jackal distribution directory and on the 00:16:06.709 --> 00:16:08.019 align:start position:0% Jackal distribution directory and on the right<00:16:06.829> hand<00:16:07.040> side<00:16:07.130> we're<00:16:07.430> looking<00:16:07.699> at<00:16:07.880> the 00:16:08.019 --> 00:16:08.029 align:start position:0% right hand side we're looking at the 00:16:08.029 --> 00:16:11.800 align:start position:0% right hand side we're looking at the Jackal<00:16:08.449> tests<00:16:09.880> which<00:16:10.880> are<00:16:11.029> just<00:16:11.149> basic<00:16:11.510> tests 00:16:11.800 --> 00:16:11.810 align:start position:0% Jackal tests which are just basic tests 00:16:11.810 --> 00:16:17.439 align:start position:0% Jackal tests which are just basic tests of<00:16:11.899> Jackel<00:16:13.420> woefully<00:16:14.420> incomplete<00:16:15.940> but<00:16:16.940> the 00:16:17.439 --> 00:16:17.449 align:start position:0% of Jackel woefully incomplete but the 00:16:17.449 --> 00:16:18.699 align:start position:0% of Jackel woefully incomplete but the important<00:16:17.839> thing<00:16:17.959> about<00:16:17.990> the<00:16:18.290> browser<00:16:18.500> on<00:16:18.680> the 00:16:18.699 --> 00:16:18.709 align:start position:0% important thing about the browser on the 00:16:18.709 --> 00:16:20.650 align:start position:0% important thing about the browser on the right<00:16:18.800> is<00:16:19.190> that<00:16:19.220> Jackal<00:16:19.910> is<00:16:19.940> loaded<00:16:20.269> into<00:16:20.420> it 00:16:20.650 --> 00:16:20.660 align:start position:0% right is that Jackal is loaded into it 00:16:20.660 --> 00:16:24.490 align:start position:0% right is that Jackal is loaded into it and<00:16:21.339> we<00:16:22.339> can<00:16:22.459> actually<00:16:22.730> interact<00:16:23.029> with<00:16:23.500> Jackel 00:16:24.490 --> 00:16:24.500 align:start position:0% and we can actually interact with Jackel 00:16:24.500 --> 00:16:25.600 align:start position:0% and we can actually interact with Jackel through<00:16:24.740> the<00:16:24.860> browser's<00:16:25.220> built-in 00:16:25.600 --> 00:16:25.610 align:start position:0% through the browser's built-in 00:16:25.610 --> 00:16:29.290 align:start position:0% through the browser's built-in development<00:16:26.089> tools<00:16:26.240> and<00:16:27.940> I'll<00:16:28.940> show<00:16:29.089> you<00:16:29.120> how 00:16:29.290 --> 00:16:29.300 align:start position:0% development tools and I'll show you how 00:16:29.300 --> 00:16:32.230 align:start position:0% development tools and I'll show you how that's<00:16:29.420> done<00:16:29.540> here<00:16:29.690> I'll<00:16:30.380> make<00:16:30.560> this<00:16:31.120> font<00:16:32.120> a 00:16:32.230 --> 00:16:32.240 align:start position:0% that's done here I'll make this font a 00:16:32.240 --> 00:16:38.350 align:start position:0% that's done here I'll make this font a little<00:16:32.269> bigger<00:16:32.570> so<00:16:34.269> I<00:16:36.760> happen<00:16:37.760> to<00:16:37.790> know<00:16:38.060> that 00:16:38.350 --> 00:16:38.360 align:start position:0% little bigger so I happen to know that 00:16:38.360 --> 00:16:41.829 align:start position:0% little bigger so I happen to know that there<00:16:39.170> is<00:16:39.579> the<00:16:40.579> moral<00:16:41.000> equivalent<00:16:41.569> of<00:16:41.690> an 00:16:41.829 --> 00:16:41.839 align:start position:0% there is the moral equivalent of an 00:16:41.839 --> 00:16:43.449 align:start position:0% there is the moral equivalent of an input<00:16:42.170> stream<00:16:42.470> set<00:16:42.860> up<00:16:42.949> in<00:16:43.100> this<00:16:43.220> browser 00:16:43.449 --> 00:16:43.459 align:start position:0% input stream set up in this browser 00:16:43.459 --> 00:16:45.490 align:start position:0% input stream set up in this browser ready<00:16:43.910> to<00:16:44.089> receive<00:16:44.360> characters<00:16:44.899> from<00:16:45.050> us 00:16:45.490 --> 00:16:45.500 align:start position:0% ready to receive characters from us 00:16:45.500 --> 00:16:48.220 align:start position:0% ready to receive characters from us now<00:16:46.040> of<00:16:46.160> course<00:16:46.220> this<00:16:47.060> console<00:16:47.510> here<00:16:47.810> is<00:16:47.959> a 00:16:48.220 --> 00:16:48.230 align:start position:0% now of course this console here is a 00:16:48.230 --> 00:16:51.699 align:start position:0% now of course this console here is a JavaScript<00:16:48.980> console<00:16:49.420> but<00:16:50.420> we<00:16:51.230> can<00:16:51.470> write 00:16:51.699 --> 00:16:51.709 align:start position:0% JavaScript console but we can write 00:16:51.709 --> 00:16:53.769 align:start position:0% JavaScript console but we can write JavaScript<00:16:52.339> code<00:16:52.579> that<00:16:52.610> pushes<00:16:53.300> characters 00:16:53.769 --> 00:16:53.779 align:start position:0% JavaScript code that pushes characters 00:16:53.779 --> 00:16:58.030 align:start position:0% JavaScript code that pushes characters into<00:16:54.500> the<00:16:55.310> compilers<00:16:56.440> reader<00:16:57.440> or<00:16:57.800> with<00:16:57.949> the 00:16:58.030 --> 00:16:58.040 align:start position:0% into the compilers reader or with the 00:16:58.040 --> 00:17:00.340 align:start position:0% into the compilers reader or with the Rebels<00:16:58.399> reader<00:16:58.720> and<00:16:59.720> I<00:16:59.810> think<00:17:00.019> it's<00:17:00.110> called 00:17:00.340 --> 00:17:00.350 align:start position:0% Rebels reader and I think it's called 00:17:00.350 --> 00:17:03.189 align:start position:0% Rebels reader and I think it's called ripple<00:17:00.620> input<00:17:01.100> stream<00:17:01.630> so<00:17:02.630> we<00:17:02.720> can<00:17:02.810> do<00:17:02.899> Ruppel 00:17:03.189 --> 00:17:03.199 align:start position:0% ripple input stream so we can do Ruppel 00:17:03.199 --> 00:17:04.660 align:start position:0% ripple input stream so we can do Ruppel input<00:17:03.500> stream 00:17:04.660 --> 00:17:04.670 align:start position:0% input stream 00:17:04.670 --> 00:17:07.570 align:start position:0% input stream right<00:17:04.820> each<00:17:05.650> which<00:17:06.650> will<00:17:06.830> take<00:17:06.950> a<00:17:07.010> sequence<00:17:07.490> of 00:17:07.570 --> 00:17:07.580 align:start position:0% right each which will take a sequence of 00:17:07.580 --> 00:17:10.150 align:start position:0% right each which will take a sequence of characters<00:17:07.880> and<00:17:08.420> we<00:17:09.320> can<00:17:09.440> send<00:17:09.710> it<00:17:09.860> just<00:17:09.890> the 00:17:10.150 --> 00:17:10.160 align:start position:0% characters and we can send it just the 00:17:10.160 --> 00:17:19.000 align:start position:0% characters and we can send it just the number<00:17:10.400> one<00:17:10.700> two<00:17:10.820> three<00:17:12.640> cool<00:17:17.800> the<00:17:18.800> killer 00:17:19.000 --> 00:17:19.010 align:start position:0% number one two three cool the killer 00:17:19.010 --> 00:17:21.040 align:start position:0% number one two three cool the killer feature<00:17:19.220> of<00:17:19.610> the<00:17:19.940> jackal<00:17:20.240> ripple<00:17:20.570> is<00:17:20.720> that 00:17:21.040 --> 00:17:21.050 align:start position:0% feature of the jackal ripple is that 00:17:21.050 --> 00:17:25.210 align:start position:0% feature of the jackal ripple is that it's<00:17:21.220> incremental<00:17:22.220> so<00:17:23.110> when<00:17:24.110> we<00:17:24.230> sent<00:17:25.130> the 00:17:25.210 --> 00:17:25.220 align:start position:0% it's incremental so when we sent the 00:17:25.220 --> 00:17:27.640 align:start position:0% it's incremental so when we sent the characters<00:17:25.550> one<00:17:25.760> two<00:17:25.910> three<00:17:26.240> with<00:17:26.780> a<00:17:26.810> terminal 00:17:27.640 --> 00:17:27.650 align:start position:0% characters one two three with a terminal 00:17:27.650 --> 00:17:31.090 align:start position:0% characters one two three with a terminal space<00:17:28.190> it<00:17:29.000> read<00:17:29.270> the<00:17:29.300> token<00:17:29.780> but<00:17:30.380> because<00:17:30.860> this 00:17:31.090 --> 00:17:31.100 align:start position:0% space it read the token but because this 00:17:31.100 --> 00:17:34.030 align:start position:0% space it read the token but because this is<00:17:31.160> an<00:17:31.370> incremental<00:17:31.880> parser<00:17:32.410> we<00:17:33.410> can<00:17:33.590> send<00:17:33.860> it 00:17:34.030 --> 00:17:34.040 align:start position:0% is an incremental parser we can send it 00:17:34.040 --> 00:17:39.160 align:start position:0% is an incremental parser we can send it characters<00:17:34.640> one<00:17:35.600> at<00:17:35.720> a<00:17:35.810> time<00:17:37.180> and<00:17:38.180> it<00:17:39.080> will 00:17:39.160 --> 00:17:39.170 align:start position:0% characters one at a time and it will 00:17:39.170 --> 00:17:43.990 align:start position:0% characters one at a time and it will digest<00:17:39.740> them<00:17:39.980> and<00:17:40.190> only<00:17:41.680> read<00:17:42.700> compile<00:17:43.700> and 00:17:43.990 --> 00:17:44.000 align:start position:0% digest them and only read compile and 00:17:44.000 --> 00:17:47.080 align:start position:0% digest them and only read compile and evaluate<00:17:44.630> when<00:17:45.470> an<00:17:45.680> entire<00:17:45.920> token<00:17:46.430> or<00:17:46.940> an 00:17:47.080 --> 00:17:47.090 align:start position:0% evaluate when an entire token or an 00:17:47.090 --> 00:17:52.510 align:start position:0% evaluate when an entire token or an entire<00:17:47.390> data<00:17:47.930> has<00:17:48.500> been<00:17:48.770> accumulated<00:17:50.470> a<00:17:51.520> list 00:17:52.510 --> 00:17:52.520 align:start position:0% entire data has been accumulated a list 00:17:52.520 --> 00:17:54.010 align:start position:0% entire data has been accumulated a list is<00:17:52.700> of<00:17:52.820> course<00:17:53.060> the<00:17:53.240> best<00:17:53.360> demonstration<00:17:53.930> of 00:17:54.010 --> 00:17:54.020 align:start position:0% is of course the best demonstration of 00:17:54.020 --> 00:17:58.570 align:start position:0% is of course the best demonstration of this<00:17:54.140> so<00:17:55.450> make<00:17:56.450> a<00:17:56.480> list<00:17:56.750> here<00:17:57.080> with<00:17:57.680> just<00:17:57.980> one 00:17:58.570 --> 00:17:58.580 align:start position:0% this so make a list here with just one 00:17:58.580 --> 00:18:01.720 align:start position:0% this so make a list here with just one and<00:17:58.760> two<00:17:58.910> I'd<00:17:59.210> better<00:17:59.480> quote<00:17:59.720> it<00:18:00.430> and<00:18:01.430> let's 00:18:01.720 --> 00:18:01.730 align:start position:0% and two I'd better quote it and let's 00:18:01.730 --> 00:18:06.880 align:start position:0% and two I'd better quote it and let's send<00:18:01.970> in<00:18:02.180> three<00:18:03.070> see<00:18:04.070> the<00:18:04.220> effect<00:18:05.140> now<00:18:06.140> we<00:18:06.650> sent 00:18:06.880 --> 00:18:06.890 align:start position:0% send in three see the effect now we sent 00:18:06.890 --> 00:18:09.240 align:start position:0% send in three see the effect now we sent in<00:18:07.070> a<00:18:07.220> list<00:18:07.520> which<00:18:07.640> you<00:18:07.790> can<00:18:08.030> see<00:18:08.330> gets 00:18:09.240 --> 00:18:09.250 align:start position:0% in a list which you can see gets 00:18:09.250 --> 00:18:12.160 align:start position:0% in a list which you can see gets evaluated<00:18:10.250> and<00:18:10.760> compiled<00:18:11.090> or<00:18:11.480> compiled<00:18:11.990> and 00:18:12.160 --> 00:18:12.170 align:start position:0% evaluated and compiled or compiled and 00:18:12.170 --> 00:18:16.750 align:start position:0% evaluated and compiled or compiled and evaluated<00:18:12.680> as<00:18:12.800> a<00:18:13.130> cons<00:18:13.480> type<00:18:14.480> object<00:18:14.900> and<00:18:15.760> we 00:18:16.750 --> 00:18:16.760 align:start position:0% evaluated as a cons type object and we 00:18:16.760 --> 00:18:21.150 align:start position:0% evaluated as a cons type object and we can<00:18:17.020> inspect<00:18:18.020> that<00:18:18.320> object<00:18:18.860> using<00:18:19.460> the 00:18:21.150 --> 00:18:21.160 align:start position:0% can inspect that object using the 00:18:21.160 --> 00:18:24.130 align:start position:0% can inspect that object using the JavaScript<00:18:22.300> object<00:18:23.300> inspector<00:18:23.510> so<00:18:23.930> you<00:18:24.020> can 00:18:24.130 --> 00:18:24.140 align:start position:0% JavaScript object inspector so you can 00:18:24.140 --> 00:18:25.840 align:start position:0% JavaScript object inspector so you can see<00:18:24.260> it<00:18:24.350> has<00:18:24.500> two<00:18:24.680> slots<00:18:24.920> car<00:18:25.340> and<00:18:25.640> cutter 00:18:25.840 --> 00:18:25.850 align:start position:0% see it has two slots car and cutter 00:18:25.850 --> 00:18:31.030 align:start position:0% see it has two slots car and cutter cutter<00:18:26.840> is<00:18:26.960> a<00:18:26.990> cons<00:18:27.790> with<00:18:28.790> 23<00:18:29.720> and<00:18:29.870> then<00:18:30.320> the 00:18:31.030 --> 00:18:31.040 align:start position:0% cutter is a cons with 23 and then the 00:18:31.040 --> 00:18:34.000 align:start position:0% cutter is a cons with 23 and then the car<00:18:31.220> of<00:18:31.370> that<00:18:32.350> excuse<00:18:33.350> me<00:18:33.380> the<00:18:33.560> cutter<00:18:33.710> of<00:18:33.860> that 00:18:34.000 --> 00:18:34.010 align:start position:0% car of that excuse me the cutter of that 00:18:34.010 --> 00:18:36.700 align:start position:0% car of that excuse me the cutter of that second<00:18:34.430> cons<00:18:34.580> is<00:18:34.850> null<00:18:35.090> this<00:18:35.750> is<00:18:35.870> a<00:18:35.960> proper 00:18:36.700 --> 00:18:36.710 align:start position:0% second cons is null this is a proper 00:18:36.710 --> 00:18:40.600 align:start position:0% second cons is null this is a proper list<00:18:38.140> we<00:18:39.140> can<00:18:39.230> also<00:18:39.380> read<00:18:39.650> symbols<00:18:39.950> so<00:18:40.430> let<00:18:40.550> me 00:18:40.600 --> 00:18:40.610 align:start position:0% list we can also read symbols so let me 00:18:40.610 --> 00:18:42.640 align:start position:0% list we can also read symbols so let me read<00:18:40.820> a<00:18:40.850> symbol<00:18:41.120> and<00:18:41.540> the<00:18:41.780> symbol<00:18:42.140> can<00:18:42.320> be<00:18:42.470> our 00:18:42.640 --> 00:18:42.650 align:start position:0% read a symbol and the symbol can be our 00:18:42.650 --> 00:18:50.130 align:start position:0% read a symbol and the symbol can be our entry<00:18:42.920> point<00:18:43.490> into<00:18:45.700> the<00:18:48.520> package<00:18:49.520> system<00:18:49.730> oh 00:18:50.130 --> 00:18:50.140 align:start position:0% entry point into the package system oh 00:18:50.140 --> 00:18:53.140 align:start position:0% entry point into the package system oh of<00:18:51.140> course<00:18:51.290> it's<00:18:51.770> not<00:18:51.950> done<00:18:52.730> reading<00:18:52.910> that 00:18:53.140 --> 00:18:53.150 align:start position:0% of course it's not done reading that 00:18:53.150 --> 00:18:54.220 align:start position:0% of course it's not done reading that symbol<00:18:53.420> because<00:18:53.570> I<00:18:53.630> have<00:18:53.750> to<00:18:53.840> send<00:18:53.960> it<00:18:54.080> some 00:18:54.220 --> 00:18:54.230 align:start position:0% symbol because I have to send it some 00:18:54.230 --> 00:18:56.800 align:start position:0% symbol because I have to send it some white<00:18:54.380> space<00:18:54.880> but<00:18:55.880> when<00:18:56.030> it<00:18:56.150> did<00:18:56.330> you<00:18:56.630> can<00:18:56.660> see 00:18:56.800 --> 00:18:56.810 align:start position:0% white space but when it did you can see 00:18:56.810 --> 00:18:59.140 align:start position:0% white space but when it did you can see we<00:18:57.020> get<00:18:57.110> a<00:18:57.170> symbol<00:18:57.470> back<00:18:57.650> and<00:18:58.040> you<00:18:58.850> can<00:18:59.000> see 00:18:59.140 --> 00:18:59.150 align:start position:0% we get a symbol back and you can see 00:18:59.150 --> 00:19:00.310 align:start position:0% we get a symbol back and you can see that<00:18:59.330> there's<00:18:59.600> a<00:18:59.630> lot<00:18:59.780> more<00:18:59.900> going<00:19:00.080> on<00:19:00.260> with 00:19:00.310 --> 00:19:00.320 align:start position:0% that there's a lot more going on with 00:19:00.320 --> 00:19:03.550 align:start position:0% that there's a lot more going on with symbols<00:19:00.770> than<00:19:01.010> with<00:19:01.190> cons<00:19:01.670> as'<00:19:02.050> plus<00:19:03.050> here<00:19:03.380> is 00:19:03.550 --> 00:19:03.560 align:start position:0% symbols than with cons as' plus here is 00:19:03.560 --> 00:19:05.830 align:start position:0% symbols than with cons as' plus here is refers<00:19:04.460> to<00:19:04.490> the<00:19:04.730> plus<00:19:04.940> from<00:19:05.150> the<00:19:05.360> Common<00:19:05.810> Lisp 00:19:05.830 --> 00:19:05.840 align:start position:0% refers to the plus from the Common Lisp 00:19:05.840 --> 00:19:10.000 align:start position:0% refers to the plus from the Common Lisp user<00:19:06.290> package<00:19:08.080> so<00:19:09.080> you<00:19:09.290> can<00:19:09.530> see<00:19:09.710> that<00:19:09.920> we're 00:19:10.000 --> 00:19:10.010 align:start position:0% user package so you can see that we're 00:19:10.010 --> 00:19:12.880 align:start position:0% user package so you can see that we're in<00:19:10.100> an<00:19:10.220> environment<00:19:10.760> where<00:19:11.170> the<00:19:12.170> CL<00:19:12.500> package 00:19:12.880 --> 00:19:12.890 align:start position:0% in an environment where the CL package 00:19:12.890 --> 00:19:15.480 align:start position:0% in an environment where the CL package has<00:19:13.040> not<00:19:13.190> been<00:19:13.430> referred 00:19:15.480 --> 00:19:15.490 align:start position:0% has not been referred 00:19:15.490 --> 00:19:18.520 align:start position:0% has not been referred you<00:19:16.490> can<00:19:16.640> see<00:19:16.790> some<00:19:17.030> metadata<00:19:17.780> here<00:19:18.230> that's 00:19:18.520 --> 00:19:18.530 align:start position:0% you can see some metadata here that's 00:19:18.530 --> 00:19:20.140 align:start position:0% you can see some metadata here that's interesting<00:19:18.680> to<00:19:19.160> the<00:19:19.280> the<00:19:19.520> runtime<00:19:19.910> like 00:19:20.140 --> 00:19:20.150 align:start position:0% interesting to the the runtime like 00:19:20.150 --> 00:19:21.790 align:start position:0% interesting to the the runtime like whether<00:19:20.300> it's<00:19:20.480> constant<00:19:20.900> a<00:19:20.990> macro<00:19:21.350> special 00:19:21.790 --> 00:19:21.800 align:start position:0% whether it's constant a macro special 00:19:21.800 --> 00:19:26.260 align:start position:0% whether it's constant a macro special variable<00:19:22.870> and<00:19:24.220> yeah<00:19:25.220> you<00:19:25.460> can<00:19:25.580> see<00:19:25.730> the<00:19:26.030> stack 00:19:26.260 --> 00:19:26.270 align:start position:0% variable and yeah you can see the stack 00:19:26.270 --> 00:19:27.520 align:start position:0% variable and yeah you can see the stack field<00:19:26.570> here<00:19:26.810> this<00:19:26.990> has<00:19:27.140> to<00:19:27.170> do<00:19:27.410> with 00:19:27.520 --> 00:19:27.530 align:start position:0% field here this has to do with 00:19:27.530 --> 00:19:32.530 align:start position:0% field here this has to do with supporting<00:19:27.860> dynamic<00:19:28.580> binding<00:19:30.070> okay<00:19:31.070> so<00:19:31.540> that 00:19:32.530 --> 00:19:32.540 align:start position:0% supporting dynamic binding okay so that 00:19:32.540 --> 00:19:34.390 align:start position:0% supporting dynamic binding okay so that actually<00:19:33.020> wasn't<00:19:33.290> as<00:19:33.500> interesting<00:19:33.950> as<00:19:34.100> I<00:19:34.250> had 00:19:34.390 --> 00:19:34.400 align:start position:0% actually wasn't as interesting as I had 00:19:34.400 --> 00:19:36.700 align:start position:0% actually wasn't as interesting as I had hoped<00:19:34.670> so<00:19:35.030> let's<00:19:35.690> use<00:19:35.840> a<00:19:35.870> different<00:19:35.990> runtime 00:19:36.700 --> 00:19:36.710 align:start position:0% hoped so let's use a different runtime 00:19:36.710 --> 00:19:38.650 align:start position:0% hoped so let's use a different runtime facility<00:19:37.190> to<00:19:37.370> look<00:19:37.610> at<00:19:37.760> the<00:19:37.970> all<00:19:38.330> of<00:19:38.570> the 00:19:38.650 --> 00:19:38.660 align:start position:0% facility to look at the all of the 00:19:38.660 --> 00:19:40.870 align:start position:0% facility to look at the all of the packages<00:19:39.110> that<00:19:39.140> are<00:19:39.320> loaded<00:19:39.680> so<00:19:40.460> I<00:19:40.490> think<00:19:40.610> I 00:19:40.870 --> 00:19:40.880 align:start position:0% packages that are loaded so I think I 00:19:40.880 --> 00:19:48.820 align:start position:0% packages that are loaded so I think I can<00:19:41.030> do<00:19:42.400> packages<00:19:46.450> so<00:19:47.450> that's<00:19:47.780> a<00:19:47.900> JavaScript 00:19:48.820 --> 00:19:48.830 align:start position:0% can do packages so that's a JavaScript 00:19:48.830 --> 00:19:51.340 align:start position:0% can do packages so that's a JavaScript global<00:19:49.190> variable<00:19:49.610> called<00:19:49.640> all<00:19:50.240> caps<00:19:50.690> packages 00:19:51.340 --> 00:19:51.350 align:start position:0% global variable called all caps packages 00:19:51.350 --> 00:19:56.380 align:start position:0% global variable called all caps packages and<00:19:51.740> you<00:19:52.610> can<00:19:52.760> see<00:19:53.000> that<00:19:53.510> it<00:19:53.630> contains<00:19:55.390> many 00:19:56.380 --> 00:19:56.390 align:start position:0% and you can see that it contains many 00:19:56.390 --> 00:19:58.750 align:start position:0% and you can see that it contains many entries<00:19:56.900> including<00:19:57.440> jackal<00:19:57.860> jeaious<00:19:58.250> Common 00:19:58.750 --> 00:19:58.760 align:start position:0% entries including jackal jeaious Common 00:19:58.760 --> 00:20:01.540 align:start position:0% entries including jackal jeaious Common Lisp<00:19:58.790> and<00:19:59.210> then<00:19:59.360> some<00:19:59.570> aliases<00:20:00.350> that<00:20:01.220> keyword 00:20:01.540 --> 00:20:01.550 align:start position:0% Lisp and then some aliases that keyword 00:20:01.550 --> 00:20:04.030 align:start position:0% Lisp and then some aliases that keyword package<00:20:01.940> of<00:20:02.060> course<00:20:02.270> let's<00:20:03.200> drill<00:20:03.530> into<00:20:03.770> the 00:20:04.030 --> 00:20:04.040 align:start position:0% package of course let's drill into the 00:20:04.040 --> 00:20:09.010 align:start position:0% package of course let's drill into the common<00:20:04.340> list<00:20:04.520> package<00:20:07.030> well<00:20:08.030> you<00:20:08.300> can<00:20:08.450> see<00:20:08.750> the 00:20:09.010 --> 00:20:09.020 align:start position:0% common list package well you can see the 00:20:09.020 --> 00:20:12.640 align:start position:0% common list package well you can see the list<00:20:09.200> of<00:20:09.350> exports<00:20:09.920> and<00:20:11.050> all<00:20:12.050> of<00:20:12.230> the<00:20:12.320> symbols 00:20:12.640 --> 00:20:12.650 align:start position:0% list of exports and all of the symbols 00:20:12.650 --> 00:20:16.420 align:start position:0% list of exports and all of the symbols that<00:20:12.770> are<00:20:12.830> interned<00:20:13.190> in<00:20:13.340> there<00:20:14.770> so<00:20:15.770> if<00:20:15.890> we<00:20:16.040> can 00:20:16.420 --> 00:20:16.430 align:start position:0% that are interned in there so if we can 00:20:16.430 --> 00:20:24.420 align:start position:0% that are interned in there so if we can find<00:20:16.610> a<00:20:16.730> symbol<00:20:17.090> that's<00:20:17.270> a<00:20:17.420> function<00:20:19.030> like<00:20:22.030> not 00:20:24.420 --> 00:20:24.430 align:start position:0% find a symbol that's a function like not 00:20:24.430 --> 00:20:27.760 align:start position:0% find a symbol that's a function like not okay<00:20:25.430> we<00:20:25.910> can<00:20:26.030> see<00:20:26.120> that's<00:20:26.240> a<00:20:26.390> value<00:20:26.900> the<00:20:27.560> list 00:20:27.760 --> 00:20:27.770 align:start position:0% okay we can see that's a value the list 00:20:27.770 --> 00:20:29.530 align:start position:0% okay we can see that's a value the list symbol<00:20:28.070> is<00:20:28.250> the<00:20:28.370> value<00:20:28.730> and<00:20:29.030> it<00:20:29.150> has<00:20:29.180> an<00:20:29.390> F 00:20:29.530 --> 00:20:29.540 align:start position:0% symbol is the value and it has an F 00:20:29.540 --> 00:20:31.780 align:start position:0% symbol is the value and it has an F value<00:20:29.960> so<00:20:30.260> this<00:20:30.980> is<00:20:31.190> a<00:20:31.220> symbol<00:20:31.640> with<00:20:31.760> a 00:20:31.780 --> 00:20:31.790 align:start position:0% value so this is a symbol with a 00:20:31.790 --> 00:20:36.460 align:start position:0% value so this is a symbol with a function<00:20:32.240> slot<00:20:32.540> of<00:20:33.040> or<00:20:34.040> an<00:20:34.130> F<00:20:34.250> definition<00:20:35.320> of<00:20:36.320> a 00:20:36.460 --> 00:20:36.470 align:start position:0% function slot of or an F definition of a 00:20:36.470 --> 00:20:38.830 align:start position:0% function slot of or an F definition of a particular<00:20:36.770> function<00:20:37.340> and<00:20:37.460> that<00:20:38.420> function<00:20:38.480> is 00:20:38.830 --> 00:20:38.840 align:start position:0% particular function and that function is 00:20:38.840 --> 00:20:41.560 align:start position:0% particular function and that function is a<00:20:38.870> JavaScript<00:20:39.350> function<00:20:39.470> and<00:20:40.210> so<00:20:41.210> we<00:20:41.450> could 00:20:41.560 --> 00:20:41.570 align:start position:0% a JavaScript function and so we could 00:20:41.570 --> 00:20:44.710 align:start position:0% a JavaScript function and so we could actually<00:20:41.960> right<00:20:42.470> click<00:20:42.500> here<00:20:43.070> to<00:20:43.520> store<00:20:44.510> as 00:20:44.710 --> 00:20:44.720 align:start position:0% actually right click here to store as 00:20:44.720 --> 00:20:47.050 align:start position:0% actually right click here to store as global<00:20:45.050> variable<00:20:45.500> and<00:20:45.820> now<00:20:46.820> in<00:20:46.970> the 00:20:47.050 --> 00:20:47.060 align:start position:0% global variable and now in the 00:20:47.060 --> 00:20:48.610 align:start position:0% global variable and now in the JavaScript<00:20:47.570> environment<00:20:47.690> we<00:20:48.080> have<00:20:48.200> a<00:20:48.230> handle 00:20:48.610 --> 00:20:48.620 align:start position:0% JavaScript environment we have a handle 00:20:48.620 --> 00:20:50.710 align:start position:0% JavaScript environment we have a handle to<00:20:48.770> this<00:20:48.890> function<00:20:49.100> and<00:20:49.550> you<00:20:50.210> can<00:20:50.330> see<00:20:50.480> it's<00:20:50.630> a 00:20:50.710 --> 00:20:50.720 align:start position:0% to this function and you can see it's a 00:20:50.720 --> 00:20:55.300 align:start position:0% to this function and you can see it's a compiled<00:20:51.080> function<00:20:52.270> and<00:20:53.270> let's<00:20:53.450> call<00:20:53.660> it<00:20:54.310> so 00:20:55.300 --> 00:20:55.310 align:start position:0% compiled function and let's call it so 00:20:55.310 --> 00:20:57.970 align:start position:0% compiled function and let's call it so if<00:20:55.400> we<00:20:55.490> call<00:20:55.610> it<00:20:55.730> with<00:20:55.850> null<00:20:56.440> it<00:20:57.440> returns<00:20:57.740> true 00:20:57.970 --> 00:20:57.980 align:start position:0% if we call it with null it returns true 00:20:57.980 --> 00:21:02.860 align:start position:0% if we call it with null it returns true if<00:20:58.280> we<00:20:58.670> call<00:20:59.150> it<00:20:59.300> with<00:20:59.390> true<00:21:00.850> returns<00:21:01.850> null<00:21:02.030> so 00:21:02.860 --> 00:21:02.870 align:start position:0% if we call it with true returns null so 00:21:02.870 --> 00:21:04.240 align:start position:0% if we call it with true returns null so all<00:21:02.990> of<00:21:03.110> this<00:21:03.170> is<00:21:03.320> to<00:21:03.440> demonstrate<00:21:03.950> that 00:21:04.240 --> 00:21:04.250 align:start position:0% all of this is to demonstrate that 00:21:04.250 --> 00:21:05.950 align:start position:0% all of this is to demonstrate that Jackal<00:21:04.850> functions<00:21:05.240> are<00:21:05.390> JavaScript 00:21:05.950 --> 00:21:05.960 align:start position:0% Jackal functions are JavaScript 00:21:05.960 --> 00:21:08.620 align:start position:0% Jackal functions are JavaScript functions<00:21:06.370> you<00:21:07.370> can<00:21:07.520> see<00:21:07.670> here<00:21:07.850> that<00:21:07.970> the 00:21:08.620 --> 00:21:08.630 align:start position:0% functions you can see here that the 00:21:08.630 --> 00:21:10.120 align:start position:0% functions you can see here that the Jackal<00:21:08.930> function<00:21:09.260> does<00:21:09.410> an<00:21:09.530> argument<00:21:09.950> length 00:21:10.120 --> 00:21:10.130 align:start position:0% Jackal function does an argument length 00:21:10.130 --> 00:21:12.280 align:start position:0% Jackal function does an argument length checking<00:21:10.550> which<00:21:11.210> javascript<00:21:11.750> does<00:21:11.840> not<00:21:11.960> do<00:21:12.140> by 00:21:12.280 --> 00:21:12.290 align:start position:0% checking which javascript does not do by 00:21:12.290 --> 00:21:14.920 align:start position:0% checking which javascript does not do by default<00:21:13.720> okay 00:21:14.920 --> 00:21:14.930 align:start position:0% default okay 00:21:14.930 --> 00:21:16.960 align:start position:0% default okay enough<00:21:15.260> tinkering<00:21:15.740> in<00:21:15.860> the<00:21:15.920> browser<00:21:16.190> let's<00:21:16.610> do 00:21:16.960 --> 00:21:16.970 align:start position:0% enough tinkering in the browser let's do 00:21:16.970 --> 00:21:18.700 align:start position:0% enough tinkering in the browser let's do some<00:21:17.180> stuff<00:21:17.420> from<00:21:17.570> Emacs<00:21:17.990> because<00:21:18.380> it's<00:21:18.530> not<00:21:18.680> a 00:21:18.700 --> 00:21:18.710 align:start position:0% some stuff from Emacs because it's not a 00:21:18.710 --> 00:21:21.490 align:start position:0% some stuff from Emacs because it's not a real<00:21:18.770> Lisp<00:21:19.160> until<00:21:19.870> doing<00:21:20.870> stuff<00:21:21.050> for<00:21:21.200> me<00:21:21.290> backs 00:21:21.490 --> 00:21:21.500 align:start position:0% real Lisp until doing stuff for me backs 00:21:21.500 --> 00:21:22.670 align:start position:0% real Lisp until doing stuff for me backs right 00:21:22.670 --> 00:21:22.680 align:start position:0% right 00:21:22.680 --> 00:21:27.470 align:start position:0% right so<00:21:23.240> flipping<00:21:24.240> over<00:21:24.360> to<00:21:24.510> Emax<00:21:24.870> here<00:21:26.300> these<00:21:27.300> are 00:21:27.470 --> 00:21:27.480 align:start position:0% so flipping over to Emax here these are 00:21:27.480 --> 00:21:29.990 align:start position:0% so flipping over to Emax here these are the<00:21:27.600> jackal<00:21:28.350> tests<00:21:28.800> actually<00:21:29.100> all<00:21:29.220> this<00:21:29.520> this 00:21:29.990 --> 00:21:30.000 align:start position:0% the jackal tests actually all this this 00:21:30.000 --> 00:21:35.030 align:start position:0% the jackal tests actually all this this test<00:21:30.390> results<00:21:31.020> screen<00:21:31.170> here<00:21:31.500> is<00:21:31.850> run<00:21:33.650> as<00:21:34.650> a 00:21:35.030 --> 00:21:35.040 align:start position:0% test results screen here is run as a 00:21:35.040 --> 00:21:37.040 align:start position:0% test results screen here is run as a consequence<00:21:35.520> of<00:21:35.670> this<00:21:35.820> code<00:21:36.030> running<00:21:36.270> I<00:21:36.540> just 00:21:37.040 --> 00:21:37.050 align:start position:0% consequence of this code running I just 00:21:37.050 --> 00:21:38.030 align:start position:0% consequence of this code running I just have<00:21:37.170> this<00:21:37.260> open<00:21:37.530> there<00:21:37.620> just<00:21:37.740> to<00:21:37.830> show<00:21:37.980> some 00:21:38.030 --> 00:21:38.040 align:start position:0% have this open there just to show some 00:21:38.040 --> 00:21:40.190 align:start position:0% have this open there just to show some jackal<00:21:38.460> code<00:21:38.610> but<00:21:39.270> we<00:21:39.420> want<00:21:39.660> to<00:21:39.750> start<00:21:40.020> a 00:21:40.190 --> 00:21:40.200 align:start position:0% jackal code but we want to start a 00:21:40.200 --> 00:21:42.530 align:start position:0% jackal code but we want to start a ripple<00:21:40.860> and<00:21:41.040> the<00:21:41.730> way<00:21:41.850> we<00:21:41.970> can<00:21:42.120> do<00:21:42.240> that<00:21:42.360> is 00:21:42.530 --> 00:21:42.540 align:start position:0% ripple and the way we can do that is 00:21:42.540 --> 00:21:44.270 align:start position:0% ripple and the way we can do that is with<00:21:42.690> the<00:21:42.900> jackal<00:21:43.350> tool<00:21:43.590> that<00:21:43.830> ships<00:21:44.070> with<00:21:44.250> the 00:21:44.270 --> 00:21:44.280 align:start position:0% with the jackal tool that ships with the 00:21:44.280 --> 00:21:47.210 align:start position:0% with the jackal tool that ships with the jackal<00:21:44.700> distribution<00:21:45.450> currently<00:21:46.070> so<00:21:47.070> this 00:21:47.210 --> 00:21:47.220 align:start position:0% jackal distribution currently so this 00:21:47.220 --> 00:21:49.850 align:start position:0% jackal distribution currently so this browser<00:21:47.460> on<00:21:47.640> the<00:21:47.670> right<00:21:47.850> hand<00:21:48.000> side<00:21:48.090> is<00:21:48.860> I 00:21:49.850 --> 00:21:49.860 align:start position:0% browser on the right hand side is I 00:21:49.860 --> 00:21:53.630 align:start position:0% browser on the right hand side is I started<00:21:50.760> it<00:21:50.910> with<00:21:51.060> the<00:21:51.090> proper<00:21:52.430> command<00:21:53.430> line 00:21:53.630 --> 00:21:53.640 align:start position:0% started it with the proper command line 00:21:53.640 --> 00:21:57.380 align:start position:0% started it with the proper command line flag<00:21:53.970> to<00:21:54.810> turn<00:21:55.080> on<00:21:55.320> remote<00:21:55.920> debugging<00:21:56.310> and<00:21:56.640> the 00:21:57.380 --> 00:21:57.390 align:start position:0% flag to turn on remote debugging and the 00:21:57.390 --> 00:21:59.990 align:start position:0% flag to turn on remote debugging and the jackal<00:21:57.810> repple<00:21:58.200> tool<00:21:58.580> leverages<00:21:59.580> the<00:21:59.730> fact 00:21:59.990 --> 00:22:00.000 align:start position:0% jackal repple tool leverages the fact 00:22:00.000 --> 00:22:02.870 align:start position:0% jackal repple tool leverages the fact that<00:22:00.690> the<00:22:00.810> browser<00:22:01.080> is<00:22:01.310> effectively<00:22:02.310> a<00:22:02.430> server 00:22:02.870 --> 00:22:02.880 align:start position:0% that the browser is effectively a server 00:22:02.880 --> 00:22:04.700 align:start position:0% that the browser is effectively a server and<00:22:03.180> it<00:22:03.360> connects<00:22:03.720> to<00:22:03.780> that<00:22:03.870> server<00:22:04.230> in<00:22:04.590> order 00:22:04.700 --> 00:22:04.710 align:start position:0% and it connects to that server in order 00:22:04.710 --> 00:22:09.500 align:start position:0% and it connects to that server in order to<00:22:04.980> send<00:22:05.280> it<00:22:05.460> data<00:22:06.240> characters<00:22:07.790> so<00:22:08.790> just<00:22:09.270> start 00:22:09.500 --> 00:22:09.510 align:start position:0% to send it data characters so just start 00:22:09.510 --> 00:22:12.890 align:start position:0% to send it data characters so just start this<00:22:09.660> up<00:22:09.900> I<00:22:10.110> do<00:22:10.170> in<00:22:11.040> Emacs<00:22:11.430> I<00:22:11.760> can<00:22:12.000> do<00:22:12.090> ctrl<00:22:12.540> you 00:22:12.890 --> 00:22:12.900 align:start position:0% this up I do in Emacs I can do ctrl you 00:22:12.900 --> 00:22:17.480 align:start position:0% this up I do in Emacs I can do ctrl you meta<00:22:13.350> X<00:22:13.820> run<00:22:14.820> -<00:22:15.270> Lisp<00:22:15.810> and<00:22:16.190> instead<00:22:17.190> of<00:22:17.340> the 00:22:17.480 --> 00:22:17.490 align:start position:0% meta X run - Lisp and instead of the 00:22:17.490 --> 00:22:19.210 align:start position:0% meta X run - Lisp and instead of the list<00:22:17.670> command<00:22:18.030> I'm<00:22:18.300> going<00:22:18.420> to<00:22:18.480> give<00:22:18.600> it<00:22:18.750> a 00:22:19.210 --> 00:22:19.220 align:start position:0% list command I'm going to give it a 00:22:19.220 --> 00:22:27.140 align:start position:0% list command I'm going to give it a jackal<00:22:20.220> command<00:22:21.410> and<00:22:25.490> this<00:22:26.490> is<00:22:26.670> actually 00:22:27.140 --> 00:22:27.150 align:start position:0% jackal command and this is actually 00:22:27.150 --> 00:22:29.000 align:start position:0% jackal command and this is actually hosed<00:22:27.390> in<00:22:27.720> some<00:22:27.930> way<00:22:28.080> oh<00:22:28.290> right<00:22:28.590> because<00:22:28.740> we 00:22:29.000 --> 00:22:29.010 align:start position:0% hosed in some way oh right because we 00:22:29.010 --> 00:22:30.710 align:start position:0% hosed in some way oh right because we have<00:22:29.160> a<00:22:29.190> dev<00:22:29.460> tool<00:22:29.640> session<00:22:30.060> over<00:22:30.300> here<00:22:30.510> we 00:22:30.710 --> 00:22:30.720 align:start position:0% have a dev tool session over here we 00:22:30.720 --> 00:22:32.570 align:start position:0% have a dev tool session over here we can't<00:22:31.020> start<00:22:31.260> a<00:22:31.350> new<00:22:31.530> one<00:22:31.680> over<00:22:31.890> any<00:22:32.160> max<00:22:32.370> so 00:22:32.570 --> 00:22:32.580 align:start position:0% can't start a new one over any max so 00:22:32.580 --> 00:22:35.600 align:start position:0% can't start a new one over any max so I'm<00:22:32.670> gonna<00:22:32.820> reboot<00:22:33.690> this<00:22:34.220> then<00:22:35.220> I'm<00:22:35.340> gonna<00:22:35.430> use 00:22:35.600 --> 00:22:35.610 align:start position:0% I'm gonna reboot this then I'm gonna use 00:22:35.610 --> 00:22:37.400 align:start position:0% I'm gonna reboot this then I'm gonna use a<00:22:35.640> shortcut<00:22:36.030> I<00:22:36.180> have<00:22:36.420> an<00:22:36.540> Emacs<00:22:36.870> called<00:22:37.140> jackal 00:22:37.400 --> 00:22:37.410 align:start position:0% a shortcut I have an Emacs called jackal 00:22:37.410 --> 00:22:39.500 align:start position:0% a shortcut I have an Emacs called jackal repple<00:22:37.890> this<00:22:38.610> function<00:22:39.060> eat<00:22:39.180> list<00:22:39.360> function 00:22:39.500 --> 00:22:39.510 align:start position:0% repple this function eat list function 00:22:39.510 --> 00:22:43.490 align:start position:0% repple this function eat list function okay<00:22:40.280> now<00:22:41.280> over<00:22:41.760> in<00:22:42.030> the<00:22:42.060> Emacs<00:22:42.870> ID<00:22:43.110> we're 00:22:43.490 --> 00:22:43.500 align:start position:0% okay now over in the Emacs ID we're 00:22:43.500 --> 00:22:45.170 align:start position:0% okay now over in the Emacs ID we're connected<00:22:44.010> up<00:22:44.130> to<00:22:44.160> the<00:22:44.460> browser<00:22:44.760> on<00:22:45.060> the<00:22:45.090> right 00:22:45.170 --> 00:22:45.180 align:start position:0% connected up to the browser on the right 00:22:45.180 --> 00:22:48.440 align:start position:0% connected up to the browser on the right hand<00:22:45.510> side<00:22:45.720> so<00:22:46.460> I<00:22:47.460> can<00:22:47.670> do<00:22:47.850> stuff<00:22:48.150> but<00:22:48.360> you're 00:22:48.440 --> 00:22:48.450 align:start position:0% hand side so I can do stuff but you're 00:22:48.450 --> 00:22:53.350 align:start position:0% hand side so I can do stuff but you're not<00:22:48.600> really<00:22:48.780> seeing<00:22:49.110> it<00:22:49.260> take<00:22:49.410> effect<00:22:49.830> because 00:22:53.350 --> 00:22:53.360 align:start position:0% 00:22:53.360 --> 00:22:55.070 align:start position:0% evaluating<00:22:54.360> the<00:22:54.420> number<00:22:54.630> one<00:22:54.780> two<00:22:54.900> three 00:22:55.070 --> 00:22:55.080 align:start position:0% evaluating the number one two three 00:22:55.080 --> 00:22:57.470 align:start position:0% evaluating the number one two three doesn't<00:22:55.320> do<00:22:55.380> anything<00:22:55.680> in<00:22:55.770> the<00:22:55.830> browser<00:22:56.480> but 00:22:57.470 --> 00:22:57.480 align:start position:0% doesn't do anything in the browser but 00:22:57.480 --> 00:23:00.620 align:start position:0% doesn't do anything in the browser but we<00:22:57.720> can<00:22:57.990> use<00:22:58.290> the<00:22:58.800> jackal<00:22:59.730> special<00:23:00.120> forms<00:23:00.480> to 00:23:00.620 --> 00:23:00.630 align:start position:0% we can use the jackal special forms to 00:23:00.630 --> 00:23:02.600 align:start position:0% we can use the jackal special forms to do<00:23:00.750> things<00:23:00.990> like<00:23:01.110> call<00:23:01.860> the<00:23:02.160> alert<00:23:02.400> function 00:23:02.600 --> 00:23:02.610 align:start position:0% do things like call the alert function 00:23:02.610 --> 00:23:06.050 align:start position:0% do things like call the alert function to<00:23:03.180> produce<00:23:03.510> a<00:23:03.750> box<00:23:03.990> and<00:23:04.350> on<00:23:04.620> the<00:23:04.770> browser<00:23:05.060> so 00:23:06.050 --> 00:23:06.060 align:start position:0% to produce a box and on the browser so 00:23:06.060 --> 00:23:08.660 align:start position:0% to produce a box and on the browser so let<00:23:06.210> me<00:23:06.330> do<00:23:06.710> well<00:23:07.710> first<00:23:07.950> let<00:23:08.220> me<00:23:08.250> go<00:23:08.400> down<00:23:08.520> to 00:23:08.660 --> 00:23:08.670 align:start position:0% let me do well first let me go down to 00:23:08.670 --> 00:23:12.080 align:start position:0% let me do well first let me go down to the<00:23:08.790> jackal<00:23:09.120> tests<00:23:09.540> file<00:23:09.990> and<00:23:10.940> I'm<00:23:11.940> going<00:23:12.060> to 00:23:12.080 --> 00:23:12.090 align:start position:0% the jackal tests file and I'm going to 00:23:12.090 --> 00:23:15.140 align:start position:0% the jackal tests file and I'm going to evaluate<00:23:12.740> this<00:23:13.740> to<00:23:14.040> enable<00:23:14.250> some<00:23:14.970> of<00:23:15.090> the 00:23:15.140 --> 00:23:15.150 align:start position:0% evaluate this to enable some of the 00:23:15.150 --> 00:23:18.230 align:start position:0% evaluate this to enable some of the reader<00:23:15.330> macros<00:23:15.750> for<00:23:16.050> Jo<00:23:16.230> syntax<00:23:17.030> so<00:23:18.030> we're 00:23:18.230 --> 00:23:18.240 align:start position:0% reader macros for Jo syntax so we're 00:23:18.240 --> 00:23:20.270 align:start position:0% reader macros for Jo syntax so we're interested<00:23:18.480> in<00:23:18.780> the<00:23:19.110> alert<00:23:19.380> function<00:23:19.590> and<00:23:20.040> I'm 00:23:20.270 --> 00:23:20.280 align:start position:0% interested in the alert function and I'm 00:23:20.280 --> 00:23:21.820 align:start position:0% interested in the alert function and I'm going<00:23:20.310> to<00:23:20.490> reference<00:23:20.820> it<00:23:20.940> here<00:23:21.120> from<00:23:21.330> jackal 00:23:21.820 --> 00:23:21.830 align:start position:0% going to reference it here from jackal 00:23:21.830 --> 00:23:24.080 align:start position:0% going to reference it here from jackal you<00:23:22.830> can<00:23:22.950> see<00:23:23.070> the<00:23:23.160> repple<00:23:23.430> doesn't<00:23:23.790> pretty 00:23:24.080 --> 00:23:24.090 align:start position:0% you can see the repple doesn't pretty 00:23:24.090 --> 00:23:27.350 align:start position:0% you can see the repple doesn't pretty print<00:23:24.360> stuff<00:23:24.660> and<00:23:25.850> it's<00:23:26.850> just<00:23:27.030> basically 00:23:27.350 --> 00:23:27.360 align:start position:0% print stuff and it's just basically 00:23:27.360 --> 00:23:29.600 align:start position:0% print stuff and it's just basically spewing<00:23:27.780> the<00:23:28.020> javascript<00:23:28.610> textual 00:23:29.600 --> 00:23:29.610 align:start position:0% spewing the javascript textual 00:23:29.610 --> 00:23:32.510 align:start position:0% spewing the javascript textual representation<00:23:30.000> of<00:23:30.390> things<00:23:30.570> but<00:23:31.530> that<00:23:31.650> @pipe 00:23:32.510 --> 00:23:32.520 align:start position:0% representation of things but that @pipe 00:23:32.520 --> 00:23:35.400 align:start position:0% representation of things but that @pipe reader<00:23:33.450> macro<00:23:33.900> is<00:23:34.140> a<00:23:34.170> way<00:23:34.380> for<00:23:34.560> us<00:23:34.590> to<00:23:34.680> access 00:23:35.400 --> 00:23:35.410 align:start position:0% reader macro is a way for us to access 00:23:35.410 --> 00:23:40.500 align:start position:0% reader macro is a way for us to access variables<00:23:36.510> so<00:23:37.510> we<00:23:37.930> can<00:23:38.200> do<00:23:39.030> we<00:23:40.030> can<00:23:40.060> use<00:23:40.210> the 00:23:40.500 --> 00:23:40.510 align:start position:0% variables so we can do we can use the 00:23:40.510 --> 00:23:42.420 align:start position:0% variables so we can do we can use the the<00:23:41.020> well<00:23:41.680> has<00:23:41.800> a<00:23:41.830> couple<00:23:42.040> ways<00:23:42.130> we<00:23:42.160> can<00:23:42.370> do 00:23:42.420 --> 00:23:42.430 align:start position:0% the well has a couple ways we can do 00:23:42.430 --> 00:23:47.550 align:start position:0% the well has a couple ways we can do this<00:23:42.550> we<00:23:42.640> can<00:23:42.670> use<00:23:42.790> jackal<00:23:43.270> call<00:23:44.520> and<00:23:46.290> pass<00:23:47.290> it 00:23:47.550 --> 00:23:47.560 align:start position:0% this we can use jackal call and pass it 00:23:47.560 --> 00:23:51.720 align:start position:0% this we can use jackal call and pass it a<00:23:47.970> topic<00:23:48.970> or<00:23:49.270> a<00:23:49.300> function<00:23:49.840> the<00:23:50.260> alert<00:23:50.560> and<00:23:50.890> then 00:23:51.720 --> 00:23:51.730 align:start position:0% a topic or a function the alert and then 00:23:51.730 --> 00:23:58.940 align:start position:0% a topic or a function the alert and then let's<00:23:51.940> pass<00:23:52.150> it<00:23:52.180> a<00:23:52.420> JavaScript<00:23:53.020> string<00:23:57.450> boom 00:23:58.940 --> 00:23:58.950 align:start position:0% let's pass it a JavaScript string boom 00:23:58.950 --> 00:24:04.500 align:start position:0% let's pass it a JavaScript string boom cool<00:24:01.710> we<00:24:02.710> can<00:24:02.830> use<00:24:03.040> a<00:24:03.070> little<00:24:03.400> more<00:24:03.520> sugar<00:24:03.910> to 00:24:04.500 --> 00:24:04.510 align:start position:0% cool we can use a little more sugar to 00:24:04.510 --> 00:24:14.760 align:start position:0% cool we can use a little more sugar to do<00:24:04.630> something<00:24:05.020> like<00:24:05.260> that<00:24:12.540> oh<00:24:13.540> I<00:24:14.320> didn't<00:24:14.620> like 00:24:14.760 --> 00:24:14.770 align:start position:0% do something like that oh I didn't like 00:24:14.770 --> 00:24:28.290 align:start position:0% do something like that oh I didn't like it<00:24:14.950> oh<00:24:15.070> I<00:24:15.130> think<00:24:15.280> I<00:24:15.490> know<00:24:26.850> how<00:24:27.850> something<00:24:28.150> might 00:24:28.290 --> 00:24:28.300 align:start position:0% it oh I think I know how something might 00:24:28.300 --> 00:24:32.940 align:start position:0% it oh I think I know how something might be<00:24:28.510> broken<00:24:28.780> there<00:24:31.140> anyway<00:24:32.140> more<00:24:32.500> work<00:24:32.680> for<00:24:32.830> me 00:24:32.940 --> 00:24:32.950 align:start position:0% be broken there anyway more work for me 00:24:32.950 --> 00:24:36.270 align:start position:0% be broken there anyway more work for me to<00:24:32.980> do<00:24:33.220> but<00:24:33.730> this<00:24:34.390> concludes<00:24:34.930> the<00:24:35.350> demo<00:24:35.680> and<00:24:35.920> I 00:24:36.270 --> 00:24:36.280 align:start position:0% to do but this concludes the demo and I 00:24:36.280 --> 00:24:38.940 align:start position:0% to do but this concludes the demo and I thank<00:24:36.640> you<00:24:36.730> very<00:24:36.850> much<00:24:37.060> for<00:24:37.210> your<00:24:37.330> time<00:24:37.540> and<00:24:38.230> I 00:24:38.940 --> 00:24:38.950 align:start position:0% thank you very much for your time and I 00:24:38.950 --> 00:24:40.680 align:start position:0% thank you very much for your time and I hope<00:24:39.340> you<00:24:39.490> learned<00:24:39.760> something<00:24:40.390> from<00:24:40.510> my 00:24:40.680 --> 00:24:40.690 align:start position:0% hope you learned something from my 00:24:40.690 --> 00:24:42.030 align:start position:0% hope you learned something from my presentation<00:24:41.050> I<00:24:41.350> look<00:24:41.500> forward<00:24:41.740> to<00:24:41.800> answering 00:24:42.030 --> 00:24:42.040 align:start position:0% presentation I look forward to answering 00:24:42.040 --> 00:24:45.810 align:start position:0% presentation I look forward to answering your<00:24:42.250> questions<00:24:42.480> thank<00:24:43.480> you<00:24:43.510> very<00:24:43.570> much