WEBVTT Kind: captions Language: en 00:00:06.480 --> 00:00:08.950 align:start position:0% so<00:00:06.640> earlier<00:00:07.040> this<00:00:07.279> year<00:00:07.600> i<00:00:07.919> decided<00:00:08.480> that<00:00:08.800> i 00:00:08.950 --> 00:00:08.960 align:start position:0% so earlier this year i decided that i 00:00:08.960 --> 00:00:11.270 align:start position:0% so earlier this year i decided that i wanted<00:00:09.200> to<00:00:09.360> start<00:00:09.599> working<00:00:10.080> on<00:00:10.400> the<00:00:10.719> clojures 00:00:11.270 --> 00:00:11.280 align:start position:0% wanted to start working on the clojures 00:00:11.280 --> 00:00:12.390 align:start position:0% wanted to start working on the clojures project 00:00:12.390 --> 00:00:12.400 align:start position:0% project 00:00:12.400 --> 00:00:14.150 align:start position:0% project and<00:00:12.639> the<00:00:12.800> first<00:00:13.120> thing<00:00:13.360> i<00:00:13.440> noticed<00:00:13.759> whenever<00:00:14.080> i 00:00:14.150 --> 00:00:14.160 align:start position:0% and the first thing i noticed whenever i 00:00:14.160 --> 00:00:16.950 align:start position:0% and the first thing i noticed whenever i looked<00:00:14.400> at<00:00:14.480> clojars<00:00:15.120> was<00:00:15.599> there<00:00:15.839> was<00:00:16.400> no<00:00:16.720> test 00:00:16.950 --> 00:00:16.960 align:start position:0% looked at clojars was there was no test 00:00:16.960 --> 00:00:18.550 align:start position:0% looked at clojars was there was no test suite<00:00:17.279> whatsoever 00:00:18.550 --> 00:00:18.560 align:start position:0% suite whatsoever 00:00:18.560 --> 00:00:22.870 align:start position:0% suite whatsoever so<00:00:19.279> and<00:00:19.439> i'm<00:00:19.680> a<00:00:19.920> big<00:00:20.400> fan<00:00:21.039> of<00:00:21.520> tests<00:00:22.240> for<00:00:22.720> my 00:00:22.870 --> 00:00:22.880 align:start position:0% so and i'm a big fan of tests for my 00:00:22.880 --> 00:00:24.550 align:start position:0% so and i'm a big fan of tests for my programs<00:00:23.519> particularly<00:00:24.080> ones<00:00:24.320> that<00:00:24.400> are 00:00:24.550 --> 00:00:24.560 align:start position:0% programs particularly ones that are 00:00:24.560 --> 00:00:26.470 align:start position:0% programs particularly ones that are acceptance<00:00:25.039> tests<00:00:25.279> that<00:00:25.439> say<00:00:26.000> the<00:00:26.160> user 00:00:26.470 --> 00:00:26.480 align:start position:0% acceptance tests that say the user 00:00:26.480 --> 00:00:28.230 align:start position:0% acceptance tests that say the user actually<00:00:26.800> logs<00:00:27.199> in<00:00:27.519> and<00:00:27.599> when<00:00:27.760> they<00:00:27.920> log<00:00:28.160> in 00:00:28.230 --> 00:00:28.240 align:start position:0% actually logs in and when they log in 00:00:28.240 --> 00:00:29.910 align:start position:0% actually logs in and when they log in they<00:00:28.400> can<00:00:28.560> view<00:00:29.039> you<00:00:29.119> know<00:00:29.359> their<00:00:29.599> photo 00:00:29.910 --> 00:00:29.920 align:start position:0% they can view you know their photo 00:00:29.920 --> 00:00:32.150 align:start position:0% they can view you know their photo stream<00:00:30.240> if<00:00:30.400> it's<00:00:30.480> something<00:00:30.800> that<00:00:30.880> direction 00:00:32.150 --> 00:00:32.160 align:start position:0% stream if it's something that direction 00:00:32.160 --> 00:00:33.270 align:start position:0% stream if it's something that direction um 00:00:33.270 --> 00:00:33.280 align:start position:0% um 00:00:33.280 --> 00:00:36.229 align:start position:0% um towards<00:00:33.760> this<00:00:34.000> end<00:00:34.399> i've<00:00:34.719> built<00:00:35.120> a<00:00:35.200> couple<00:00:35.520> of 00:00:36.229 --> 00:00:36.239 align:start position:0% towards this end i've built a couple of 00:00:36.239 --> 00:00:37.990 align:start position:0% towards this end i've built a couple of libraries<00:00:36.719> for<00:00:36.960> doing<00:00:37.280> ring<00:00:37.520> interaction<00:00:37.920> and 00:00:37.990 --> 00:00:38.000 align:start position:0% libraries for doing ring interaction and 00:00:38.000 --> 00:00:39.270 align:start position:0% libraries for doing ring interaction and testing 00:00:39.270 --> 00:00:39.280 align:start position:0% testing 00:00:39.280 --> 00:00:40.630 align:start position:0% testing the<00:00:39.440> first<00:00:39.600> one<00:00:39.760> i<00:00:39.840> want<00:00:39.920> to<00:00:40.000> talk<00:00:40.160> about<00:00:40.480> is 00:00:40.630 --> 00:00:40.640 align:start position:0% the first one i want to talk about is 00:00:40.640 --> 00:00:41.590 align:start position:0% the first one i want to talk about is called 00:00:41.590 --> 00:00:41.600 align:start position:0% called 00:00:41.600 --> 00:00:43.030 align:start position:0% called peridot 00:00:43.030 --> 00:00:43.040 align:start position:0% peridot 00:00:43.040 --> 00:00:46.549 align:start position:0% peridot it<00:00:43.360> is<00:00:43.760> basically<00:00:44.480> a<00:00:44.719> port<00:00:45.040> of<00:00:45.360> rack<00:00:45.760> test<00:00:46.399> if 00:00:46.549 --> 00:00:46.559 align:start position:0% it is basically a port of rack test if 00:00:46.559 --> 00:00:49.029 align:start position:0% it is basically a port of rack test if you're<00:00:46.800> familiar<00:00:47.200> with<00:00:47.360> that<00:00:47.600> from<00:00:47.840> the<00:00:48.160> ruby 00:00:49.029 --> 00:00:49.039 align:start position:0% you're familiar with that from the ruby 00:00:49.039 --> 00:00:50.310 align:start position:0% you're familiar with that from the ruby community 00:00:50.310 --> 00:00:50.320 align:start position:0% community 00:00:50.320 --> 00:00:53.590 align:start position:0% community uh<00:00:50.640> it<00:00:50.879> uses<00:00:51.280> the<00:00:51.600> thread<00:00:51.920> first<00:00:52.239> macro<00:00:52.800> to 00:00:53.590 --> 00:00:53.600 align:start position:0% uh it uses the thread first macro to 00:00:53.600 --> 00:00:57.990 align:start position:0% uh it uses the thread first macro to simulate<00:00:54.399> an<00:00:54.719> iterative<00:00:55.680> or<00:00:56.320> an<00:00:56.480> imperative 00:00:57.990 --> 00:00:58.000 align:start position:0% simulate an iterative or an imperative 00:00:58.000 --> 00:00:59.990 align:start position:0% simulate an iterative or an imperative interaction 00:00:59.990 --> 00:01:00.000 align:start position:0% interaction 00:01:00.000 --> 00:01:03.189 align:start position:0% interaction you<00:01:00.239> start<00:01:00.480> first<00:01:00.879> by<00:01:01.359> creating<00:01:01.760> a<00:01:01.920> session 00:01:03.189 --> 00:01:03.199 align:start position:0% you start first by creating a session 00:01:03.199 --> 00:01:04.950 align:start position:0% you start first by creating a session and<00:01:03.280> then<00:01:03.520> you<00:01:03.680> can<00:01:03.840> actually<00:01:04.080> do<00:01:04.239> a<00:01:04.400> request 00:01:04.950 --> 00:01:04.960 align:start position:0% and then you can actually do a request 00:01:04.960 --> 00:01:06.630 align:start position:0% and then you can actually do a request in<00:01:05.119> this<00:01:05.280> particular<00:01:05.840> case<00:01:06.080> we're<00:01:06.240> doing<00:01:06.560> a 00:01:06.630 --> 00:01:06.640 align:start position:0% in this particular case we're doing a 00:01:06.640 --> 00:01:08.390 align:start position:0% in this particular case we're doing a request<00:01:07.119> to<00:01:07.280> a<00:01:07.360> login 00:01:08.390 --> 00:01:08.400 align:start position:0% request to a login 00:01:08.400 --> 00:01:10.710 align:start position:0% request to a login and<00:01:08.560> actually<00:01:08.880> passing<00:01:09.280> some<00:01:09.680> parameters 00:01:10.710 --> 00:01:10.720 align:start position:0% and actually passing some parameters 00:01:10.720 --> 00:01:12.950 align:start position:0% and actually passing some parameters keyword<00:01:11.040> parameters<00:01:11.600> through 00:01:12.950 --> 00:01:12.960 align:start position:0% keyword parameters through 00:01:12.960 --> 00:01:14.789 align:start position:0% keyword parameters through uses<00:01:13.280> ring<00:01:13.520> mock<00:01:13.840> underneath<00:01:14.320> so<00:01:14.479> these 00:01:14.789 --> 00:01:14.799 align:start position:0% uses ring mock underneath so these 00:01:14.799 --> 00:01:17.109 align:start position:0% uses ring mock underneath so these actually<00:01:15.360> are<00:01:15.760> the<00:01:15.920> exact<00:01:16.400> keywords<00:01:16.880> that<00:01:16.960> you 00:01:17.109 --> 00:01:17.119 align:start position:0% actually are the exact keywords that you 00:01:17.119 --> 00:01:21.670 align:start position:0% actually are the exact keywords that you see<00:01:17.520> in<00:01:17.680> the<00:01:18.159> ring<00:01:18.479> spec<00:01:19.119> for<00:01:19.600> your<00:01:19.759> requests 00:01:21.670 --> 00:01:21.680 align:start position:0% see in the ring spec for your requests 00:01:21.680 --> 00:01:24.230 align:start position:0% see in the ring spec for your requests uh<00:01:22.400> you're<00:01:22.640> also<00:01:23.040> able<00:01:23.280> to<00:01:23.520> do<00:01:23.840> things<00:01:24.080> like 00:01:24.230 --> 00:01:24.240 align:start position:0% uh you're also able to do things like 00:01:24.240 --> 00:01:26.230 align:start position:0% uh you're also able to do things like follow<00:01:24.560> redirections<00:01:25.200> if<00:01:25.280> you<00:01:25.360> get<00:01:25.520> a 00:01:26.230 --> 00:01:26.240 align:start position:0% follow redirections if you get a 00:01:26.240 --> 00:01:27.990 align:start position:0% follow redirections if you get a redirect<00:01:26.720> at<00:01:26.799> that<00:01:26.960> point 00:01:27.990 --> 00:01:28.000 align:start position:0% redirect at that point 00:01:28.000 --> 00:01:29.510 align:start position:0% redirect at that point it<00:01:28.159> parses<00:01:28.560> it<00:01:28.720> out<00:01:28.799> and<00:01:28.880> figures<00:01:29.200> out<00:01:29.280> what 00:01:29.510 --> 00:01:29.520 align:start position:0% it parses it out and figures out what 00:01:29.520 --> 00:01:31.749 align:start position:0% it parses it out and figures out what the<00:01:29.600> url<00:01:30.240> and<00:01:30.640> creates<00:01:30.880> the<00:01:30.960> next<00:01:31.520> next 00:01:31.749 --> 00:01:31.759 align:start position:0% the url and creates the next next 00:01:31.759 --> 00:01:33.510 align:start position:0% the url and creates the next next requests<00:01:32.159> and<00:01:32.320> such<00:01:32.560> for<00:01:32.720> you 00:01:33.510 --> 00:01:33.520 align:start position:0% requests and such for you 00:01:33.520 --> 00:01:34.390 align:start position:0% requests and such for you uh 00:01:34.390 --> 00:01:34.400 align:start position:0% uh 00:01:34.400 --> 00:01:36.789 align:start position:0% uh this<00:01:34.640> example 00:01:36.789 --> 00:01:36.799 align:start position:0% this example 00:01:36.799 --> 00:01:38.149 align:start position:0% this example does<00:01:37.040> a<00:01:37.119> request 00:01:38.149 --> 00:01:38.159 align:start position:0% does a request 00:01:38.159 --> 00:01:39.830 align:start position:0% does a request follows<00:01:38.479> redirect<00:01:38.880> and<00:01:38.960> then<00:01:39.119> actually<00:01:39.520> logs 00:01:39.830 --> 00:01:39.840 align:start position:0% follows redirect and then actually logs 00:01:39.840 --> 00:01:41.590 align:start position:0% follows redirect and then actually logs in<00:01:40.000> as<00:01:40.079> a<00:01:40.159> user<00:01:40.400> follows<00:01:40.720> the<00:01:40.799> redirect<00:01:41.439> and 00:01:41.590 --> 00:01:41.600 align:start position:0% in as a user follows the redirect and 00:01:41.600 --> 00:01:43.510 align:start position:0% in as a user follows the redirect and then<00:01:41.759> actually<00:01:42.079> looks<00:01:42.320> at<00:01:42.400> the<00:01:42.560> task<00:01:43.200> has<00:01:43.360> an 00:01:43.510 --> 00:01:43.520 align:start position:0% then actually looks at the task has an 00:01:43.520 --> 00:01:45.830 align:start position:0% then actually looks at the task has an example<00:01:43.840> has<00:01:44.000> a<00:01:44.400> dot<00:01:44.640> dot<00:01:44.880> there<00:01:45.119> for<00:01:45.439> creating 00:01:45.830 --> 00:01:45.840 align:start position:0% example has a dot dot there for creating 00:01:45.840 --> 00:01:47.030 align:start position:0% example has a dot dot there for creating a<00:01:45.920> task 00:01:47.030 --> 00:01:47.040 align:start position:0% a task 00:01:47.040 --> 00:01:48.310 align:start position:0% a task and 00:01:48.310 --> 00:01:48.320 align:start position:0% and 00:01:48.320 --> 00:01:50.069 align:start position:0% and will<00:01:48.560> then<00:01:48.720> go<00:01:48.960> and<00:01:49.040> actually<00:01:49.360> view<00:01:49.520> the<00:01:49.600> test 00:01:50.069 --> 00:01:50.079 align:start position:0% will then go and actually view the test 00:01:50.079 --> 00:01:51.109 align:start position:0% will then go and actually view the test the<00:01:50.240> task 00:01:51.109 --> 00:01:51.119 align:start position:0% the task 00:01:51.119 --> 00:01:52.550 align:start position:0% the task and<00:01:51.280> this<00:01:51.600> is 00:01:52.550 --> 00:01:52.560 align:start position:0% and this is 00:01:52.560 --> 00:01:55.270 align:start position:0% and this is uh<00:01:53.280> a<00:01:53.360> little<00:01:53.520> bit<00:01:53.680> beyond<00:01:54.079> what<00:01:54.640> ring<00:01:54.960> mock 00:01:55.270 --> 00:01:55.280 align:start position:0% uh a little bit beyond what ring mock 00:01:55.280 --> 00:01:56.789 align:start position:0% uh a little bit beyond what ring mock itself<00:01:55.600> will<00:01:55.759> do<00:01:55.920> because<00:01:56.159> it<00:01:56.240> will<00:01:56.479> actually 00:01:56.789 --> 00:01:56.799 align:start position:0% itself will do because it will actually 00:01:56.799 --> 00:01:59.030 align:start position:0% itself will do because it will actually parse<00:01:57.200> out<00:01:57.360> the<00:01:57.439> cookies<00:01:57.840> for<00:01:58.079> you 00:01:59.030 --> 00:01:59.040 align:start position:0% parse out the cookies for you 00:01:59.040 --> 00:02:01.190 align:start position:0% parse out the cookies for you and<00:01:59.200> keep<00:01:59.439> those<00:01:59.600> around<00:01:59.920> in<00:02:00.000> a<00:02:00.079> cookie<00:02:00.399> jar<00:02:01.040> so 00:02:01.190 --> 00:02:01.200 align:start position:0% and keep those around in a cookie jar so 00:02:01.200 --> 00:02:02.550 align:start position:0% and keep those around in a cookie jar so that<00:02:01.360> as<00:02:01.520> you're<00:02:01.600> moving<00:02:01.920> along<00:02:02.240> through<00:02:02.399> the 00:02:02.550 --> 00:02:02.560 align:start position:0% that as you're moving along through the 00:02:02.560 --> 00:02:04.630 align:start position:0% that as you're moving along through the session<00:02:02.960> you<00:02:03.119> actually<00:02:03.439> stay<00:02:03.840> logged<00:02:04.159> in<00:02:04.399> as 00:02:04.630 --> 00:02:04.640 align:start position:0% session you actually stay logged in as 00:02:04.640 --> 00:02:07.350 align:start position:0% session you actually stay logged in as that<00:02:04.880> particular<00:02:05.360> user 00:02:07.350 --> 00:02:07.360 align:start position:0% that particular user 00:02:07.360 --> 00:02:10.309 align:start position:0% that particular user uh<00:02:08.080> as<00:02:08.319> part<00:02:08.560> of<00:02:08.800> the<00:02:09.520> what<00:02:09.679> it<00:02:09.920> what<00:02:10.080> each<00:02:10.239> one 00:02:10.309 --> 00:02:10.319 align:start position:0% uh as part of the what it what each one 00:02:10.319 --> 00:02:11.830 align:start position:0% uh as part of the what it what each one of<00:02:10.399> these<00:02:10.560> actions<00:02:10.879> return<00:02:11.280> is<00:02:11.440> a<00:02:11.520> little 00:02:11.830 --> 00:02:11.840 align:start position:0% of these actions return is a little 00:02:11.840 --> 00:02:14.630 align:start position:0% of these actions return is a little hashmap<00:02:12.640> uh<00:02:12.879> hash<00:02:13.200> state<00:02:13.920> state<00:02:14.160> map<00:02:14.400> there<00:02:14.560> we 00:02:14.630 --> 00:02:14.640 align:start position:0% hashmap uh hash state state map there we 00:02:14.640 --> 00:02:15.510 align:start position:0% hashmap uh hash state state map there we go 00:02:15.510 --> 00:02:15.520 align:start position:0% go 00:02:15.520 --> 00:02:17.830 align:start position:0% go uh<00:02:15.840> it<00:02:15.920> contains<00:02:16.400> the<00:02:16.560> last<00:02:16.879> response<00:02:17.520> and<00:02:17.680> the 00:02:17.830 --> 00:02:17.840 align:start position:0% uh it contains the last response and the 00:02:17.840 --> 00:02:19.830 align:start position:0% uh it contains the last response and the request<00:02:18.560> that<00:02:18.800> was<00:02:19.120> used<00:02:19.440> during<00:02:19.680> that 00:02:19.830 --> 00:02:19.840 align:start position:0% request that was used during that 00:02:19.840 --> 00:02:21.750 align:start position:0% request that was used during that interaction<00:02:20.800> so<00:02:20.959> you<00:02:21.040> can<00:02:21.200> actually<00:02:21.520> pull 00:02:21.750 --> 00:02:21.760 align:start position:0% interaction so you can actually pull 00:02:21.760 --> 00:02:23.990 align:start position:0% interaction so you can actually pull those<00:02:22.080> out<00:02:22.400> and<00:02:22.879> test<00:02:23.440> against<00:02:23.760> those 00:02:23.990 --> 00:02:24.000 align:start position:0% those out and test against those 00:02:24.000 --> 00:02:26.229 align:start position:0% those out and test against those particular<00:02:24.560> values<00:02:25.280> for<00:02:25.520> that<00:02:25.760> point<00:02:26.000> in<00:02:26.080> the 00:02:26.229 --> 00:02:26.239 align:start position:0% particular values for that point in the 00:02:26.239 --> 00:02:27.110 align:start position:0% particular values for that point in the uh 00:02:27.110 --> 00:02:27.120 align:start position:0% uh 00:02:27.120 --> 00:02:29.190 align:start position:0% uh in<00:02:27.200> your<00:02:27.520> in<00:02:27.680> your<00:02:27.840> interaction 00:02:29.190 --> 00:02:29.200 align:start position:0% in your in your interaction 00:02:29.200 --> 00:02:30.150 align:start position:0% in your in your interaction uh 00:02:30.150 --> 00:02:30.160 align:start position:0% uh 00:02:30.160 --> 00:02:32.150 align:start position:0% uh there's<00:02:30.400> the<00:02:30.560> app<00:02:30.879> and<00:02:31.040> the<00:02:31.120> cookie<00:02:31.440> jar<00:02:31.840> as<00:02:32.000> i 00:02:32.150 --> 00:02:32.160 align:start position:0% there's the app and the cookie jar as i 00:02:32.160 --> 00:02:34.390 align:start position:0% there's the app and the cookie jar as i have<00:02:32.640> already<00:02:33.040> mentioned 00:02:34.390 --> 00:02:34.400 align:start position:0% have already mentioned 00:02:34.400 --> 00:02:36.550 align:start position:0% have already mentioned and<00:02:34.959> there's<00:02:35.680> a<00:02:35.760> couple<00:02:36.000> of<00:02:36.160> extra<00:02:36.400> things 00:02:36.550 --> 00:02:36.560 align:start position:0% and there's a couple of extra things 00:02:36.560 --> 00:02:38.390 align:start position:0% and there's a couple of extra things there<00:02:36.879> down<00:02:37.040> at<00:02:37.120> the<00:02:37.200> bottom<00:02:37.599> for<00:02:38.000> content 00:02:38.390 --> 00:02:38.400 align:start position:0% there down at the bottom for content 00:02:38.400 --> 00:02:39.990 align:start position:0% there down at the bottom for content type<00:02:38.640> and<00:02:38.720> headers<00:02:39.120> because 00:02:39.990 --> 00:02:40.000 align:start position:0% type and headers because 00:02:40.000 --> 00:02:41.830 align:start position:0% type and headers because it's<00:02:40.160> nice<00:02:40.480> to<00:02:40.560> be<00:02:40.720> able<00:02:40.879> to<00:02:41.040> say<00:02:41.440> for<00:02:41.599> all 00:02:41.830 --> 00:02:41.840 align:start position:0% it's nice to be able to say for all 00:02:41.840 --> 00:02:44.070 align:start position:0% it's nice to be able to say for all future<00:02:42.160> requests<00:02:42.720> in<00:02:42.800> this<00:02:43.040> session<00:02:43.760> i<00:02:43.920> want 00:02:44.070 --> 00:02:44.080 align:start position:0% future requests in this session i want 00:02:44.080 --> 00:02:45.990 align:start position:0% future requests in this session i want to<00:02:44.160> use<00:02:44.400> the<00:02:44.560> json<00:02:45.040> content<00:02:45.440> type<00:02:45.680> because<00:02:45.840> i'm 00:02:45.990 --> 00:02:46.000 align:start position:0% to use the json content type because i'm 00:02:46.000 --> 00:02:48.869 align:start position:0% to use the json content type because i'm actually<00:02:46.239> testing<00:02:46.640> say<00:02:46.800> a<00:02:46.879> json<00:02:47.280> api 00:02:48.869 --> 00:02:48.879 align:start position:0% actually testing say a json api 00:02:48.879 --> 00:02:51.670 align:start position:0% actually testing say a json api um 00:02:51.670 --> 00:02:51.680 align:start position:0% um 00:02:51.680 --> 00:02:54.309 align:start position:0% um and<00:02:51.840> so<00:02:52.080> this<00:02:52.400> works<00:02:53.200> this<00:02:53.519> looks<00:02:53.760> decently 00:02:54.309 --> 00:02:54.319 align:start position:0% and so this works this looks decently 00:02:54.319 --> 00:02:55.670 align:start position:0% and so this works this looks decently well<00:02:54.640> for 00:02:55.670 --> 00:02:55.680 align:start position:0% well for 00:02:55.680 --> 00:02:58.070 align:start position:0% well for you<00:02:55.840> know<00:02:56.000> hitting<00:02:56.400> user<00:02:56.800> or<00:02:57.120> use<00:02:57.360> hitting<00:02:57.680> uh 00:02:58.070 --> 00:02:58.080 align:start position:0% you know hitting user or use hitting uh 00:02:58.080 --> 00:03:00.229 align:start position:0% you know hitting user or use hitting uh api<00:02:58.560> endpoints<00:02:59.360> but<00:02:59.599> it<00:02:59.680> doesn't<00:02:59.920> really 00:03:00.229 --> 00:03:00.239 align:start position:0% api endpoints but it doesn't really 00:03:00.239 --> 00:03:02.710 align:start position:0% api endpoints but it doesn't really represent<00:03:00.879> what<00:03:01.120> a<00:03:01.360> user<00:03:01.680> does<00:03:02.000> whenever<00:03:02.319> they 00:03:02.710 --> 00:03:02.720 align:start position:0% represent what a user does whenever they 00:03:02.720 --> 00:03:05.030 align:start position:0% represent what a user does whenever they interact<00:03:03.120> with<00:03:03.280> your<00:03:03.440> application 00:03:05.030 --> 00:03:05.040 align:start position:0% interact with your application 00:03:05.040 --> 00:03:07.270 align:start position:0% interact with your application there<00:03:05.280> we<00:03:05.440> have<00:03:05.680> the<00:03:06.239> we've<00:03:06.480> manually<00:03:06.879> put<00:03:07.120> in 00:03:07.270 --> 00:03:07.280 align:start position:0% there we have the we've manually put in 00:03:07.280 --> 00:03:09.750 align:start position:0% there we have the we've manually put in where<00:03:07.440> the<00:03:07.599> login<00:03:08.000> url<00:03:08.640> we<00:03:08.800> have 00:03:09.750 --> 00:03:09.760 align:start position:0% where the login url we have 00:03:09.760 --> 00:03:11.589 align:start position:0% where the login url we have the<00:03:10.000> parameters<00:03:10.640> went<00:03:10.959> with<00:03:11.120> the<00:03:11.200> username 00:03:11.589 --> 00:03:11.599 align:start position:0% the parameters went with the username 00:03:11.599 --> 00:03:13.190 align:start position:0% the parameters went with the username and<00:03:11.680> password<00:03:12.080> where<00:03:12.239> we've<00:03:12.640> manually<00:03:13.040> put 00:03:13.190 --> 00:03:13.200 align:start position:0% and password where we've manually put 00:03:13.200 --> 00:03:15.030 align:start position:0% and password where we've manually put those<00:03:13.440> in<00:03:13.599> ourselves<00:03:14.480> and<00:03:14.720> there's<00:03:14.959> this 00:03:15.030 --> 00:03:15.040 align:start position:0% those in ourselves and there's this 00:03:15.040 --> 00:03:17.509 align:start position:0% those in ourselves and there's this whole<00:03:15.280> html<00:03:15.920> view<00:03:16.480> if<00:03:16.640> you're<00:03:16.720> doing<00:03:16.959> html 00:03:17.509 --> 00:03:17.519 align:start position:0% whole html view if you're doing html 00:03:17.519 --> 00:03:18.710 align:start position:0% whole html view if you're doing html site 00:03:18.710 --> 00:03:18.720 align:start position:0% site 00:03:18.720 --> 00:03:19.750 align:start position:0% site where 00:03:19.750 --> 00:03:19.760 align:start position:0% where 00:03:19.760 --> 00:03:21.910 align:start position:0% where you<00:03:20.000> also<00:03:20.239> have<00:03:20.400> to<00:03:20.480> place<00:03:20.800> those<00:03:21.120> particular 00:03:21.910 --> 00:03:21.920 align:start position:0% you also have to place those particular 00:03:21.920 --> 00:03:23.270 align:start position:0% you also have to place those particular elements<00:03:22.400> and<00:03:22.480> if<00:03:22.560> you<00:03:22.640> get<00:03:22.800> those<00:03:23.040> out<00:03:23.120> of 00:03:23.270 --> 00:03:23.280 align:start position:0% elements and if you get those out of 00:03:23.280 --> 00:03:24.790 align:start position:0% elements and if you get those out of sync<00:03:23.519> you've<00:03:23.599> got<00:03:23.760> to<00:03:23.840> go<00:03:24.159> fix<00:03:24.480> all<00:03:24.560> of<00:03:24.640> your 00:03:24.790 --> 00:03:24.800 align:start position:0% sync you've got to go fix all of your 00:03:24.800 --> 00:03:26.790 align:start position:0% sync you've got to go fix all of your tests<00:03:25.120> if<00:03:25.280> they<00:03:25.440> break 00:03:26.790 --> 00:03:26.800 align:start position:0% tests if they break 00:03:26.800 --> 00:03:30.070 align:start position:0% tests if they break and<00:03:26.959> i<00:03:27.120> prefer<00:03:27.840> something<00:03:28.239> a<00:03:28.319> little<00:03:28.560> bit 00:03:30.070 --> 00:03:30.080 align:start position:0% and i prefer something a little bit 00:03:30.080 --> 00:03:31.910 align:start position:0% and i prefer something a little bit more<00:03:30.319> what<00:03:30.480> it<00:03:30.720> looks<00:03:31.200> actually<00:03:31.440> like<00:03:31.680> what<00:03:31.840> a 00:03:31.910 --> 00:03:31.920 align:start position:0% more what it looks actually like what a 00:03:31.920 --> 00:03:33.270 align:start position:0% more what it looks actually like what a user<00:03:32.159> does 00:03:33.270 --> 00:03:33.280 align:start position:0% user does 00:03:33.280 --> 00:03:36.070 align:start position:0% user does so<00:03:33.680> to<00:03:33.840> that<00:03:34.159> end<00:03:34.400> i<00:03:34.560> built<00:03:34.959> a<00:03:35.040> library<00:03:35.599> called 00:03:36.070 --> 00:03:36.080 align:start position:0% so to that end i built a library called 00:03:36.080 --> 00:03:37.270 align:start position:0% so to that end i built a library called caradin 00:03:37.270 --> 00:03:37.280 align:start position:0% caradin 00:03:37.280 --> 00:03:38.789 align:start position:0% caradin and<00:03:37.440> this<00:03:37.760> is 00:03:38.789 --> 00:03:38.799 align:start position:0% and this is 00:03:38.799 --> 00:03:41.509 align:start position:0% and this is inspired<00:03:39.599> by<00:03:39.920> a<00:03:40.080> library<00:03:40.480> called<00:03:40.720> capybara 00:03:41.509 --> 00:03:41.519 align:start position:0% inspired by a library called capybara 00:03:41.519 --> 00:03:43.750 align:start position:0% inspired by a library called capybara from<00:03:41.680> the<00:03:41.760> ruby<00:03:42.080> world 00:03:43.750 --> 00:03:43.760 align:start position:0% from the ruby world 00:03:43.760 --> 00:03:45.910 align:start position:0% from the ruby world here's<00:03:44.000> an<00:03:44.080> example<00:03:44.400> of<00:03:44.560> logging<00:03:44.879> in<00:03:45.040> with<00:03:45.200> it 00:03:45.910 --> 00:03:45.920 align:start position:0% here's an example of logging in with it 00:03:45.920 --> 00:03:48.390 align:start position:0% here's an example of logging in with it you<00:03:46.319> start<00:03:46.560> a<00:03:46.640> session<00:03:47.120> you<00:03:47.280> go<00:03:47.519> visit<00:03:48.159> the 00:03:48.390 --> 00:03:48.400 align:start position:0% you start a session you go visit the 00:03:48.400 --> 00:03:50.710 align:start position:0% you start a session you go visit the actual<00:03:48.799> root<00:03:49.040> page<00:03:49.840> and<00:03:49.920> then<00:03:50.159> you<00:03:50.319> can<00:03:50.480> tell 00:03:50.710 --> 00:03:50.720 align:start position:0% actual root page and then you can tell 00:03:50.720 --> 00:03:53.990 align:start position:0% actual root page and then you can tell it<00:03:50.879> to<00:03:51.200> fill<00:03:51.440> in<00:03:51.760> these<00:03:52.000> elements<00:03:52.480> on<00:03:52.560> the<00:03:52.720> form 00:03:53.990 --> 00:03:54.000 align:start position:0% it to fill in these elements on the form 00:03:54.000 --> 00:03:55.509 align:start position:0% it to fill in these elements on the form with<00:03:54.159> the<00:03:54.319> particular<00:03:54.799> login<00:03:55.120> name<00:03:55.360> and<00:03:55.440> the 00:03:55.509 --> 00:03:55.519 align:start position:0% with the particular login name and the 00:03:55.519 --> 00:03:57.030 align:start position:0% with the particular login name and the password<00:03:56.000> and<00:03:56.080> you<00:03:56.159> can<00:03:56.319> tell<00:03:56.480> it<00:03:56.560> to<00:03:56.640> go<00:03:56.799> press 00:03:57.030 --> 00:03:57.040 align:start position:0% password and you can tell it to go press 00:03:57.040 --> 00:03:58.229 align:start position:0% password and you can tell it to go press this<00:03:57.200> button 00:03:58.229 --> 00:03:58.239 align:start position:0% this button 00:03:58.239 --> 00:03:59.990 align:start position:0% this button and<00:03:58.879> in<00:03:58.959> this<00:03:59.120> case<00:03:59.280> follow<00:03:59.519> the<00:03:59.680> redirect 00:03:59.990 --> 00:04:00.000 align:start position:0% and in this case follow the redirect 00:04:00.000 --> 00:04:01.270 align:start position:0% and in this case follow the redirect around 00:04:01.270 --> 00:04:01.280 align:start position:0% around 00:04:01.280 --> 00:04:04.070 align:start position:0% around this<00:04:01.599> uses<00:04:02.400> in<00:04:02.560> live<00:04:02.879> underneath<00:04:03.360> to<00:04:03.599> actually 00:04:04.070 --> 00:04:04.080 align:start position:0% this uses in live underneath to actually 00:04:04.080 --> 00:04:05.990 align:start position:0% this uses in live underneath to actually parse<00:04:04.560> the<00:04:04.720> html 00:04:05.990 --> 00:04:06.000 align:start position:0% parse the html 00:04:06.000 --> 00:04:07.670 align:start position:0% parse the html to<00:04:06.560> figure<00:04:06.799> out<00:04:06.879> what<00:04:06.959> the<00:04:07.120> different<00:04:07.280> nodes 00:04:07.670 --> 00:04:07.680 align:start position:0% to figure out what the different nodes 00:04:07.680 --> 00:04:10.070 align:start position:0% to figure out what the different nodes are<00:04:07.920> and<00:04:08.640> actually<00:04:08.959> to<00:04:09.120> update<00:04:09.439> them<00:04:09.680> as<00:04:09.920> you 00:04:10.070 --> 00:04:10.080 align:start position:0% are and actually to update them as you 00:04:10.080 --> 00:04:11.429 align:start position:0% are and actually to update them as you do<00:04:10.319> the 00:04:11.429 --> 00:04:11.439 align:start position:0% do the 00:04:11.439 --> 00:04:16.229 align:start position:0% do the the<00:04:11.760> form<00:04:12.159> the<00:04:12.400> form<00:04:12.640> interaction 00:04:16.229 --> 00:04:16.239 align:start position:0% 00:04:16.239 --> 00:04:19.430 align:start position:0% since<00:04:17.040> you<00:04:17.199> don't<00:04:17.440> always<00:04:17.840> have<00:04:18.400> fields 00:04:19.430 --> 00:04:19.440 align:start position:0% since you don't always have fields 00:04:19.440 --> 00:04:22.069 align:start position:0% since you don't always have fields particular<00:04:20.400> in<00:04:20.479> this<00:04:20.639> case<00:04:21.359> this<00:04:21.680> looks<00:04:21.919> at 00:04:22.069 --> 00:04:22.079 align:start position:0% particular in this case this looks at 00:04:22.079 --> 00:04:24.790 align:start position:0% particular in this case this looks at the<00:04:22.240> labels<00:04:22.720> for<00:04:22.960> say<00:04:23.199> the<00:04:23.600> the<00:04:24.160> login<00:04:24.560> looks 00:04:24.790 --> 00:04:24.800 align:start position:0% the labels for say the the login looks 00:04:24.800 --> 00:04:27.030 align:start position:0% the labels for say the the login looks at<00:04:24.880> the<00:04:24.960> label<00:04:25.600> and<00:04:25.680> then<00:04:25.919> finds<00:04:26.240> the<00:04:26.639> the<00:04:26.800> text 00:04:27.030 --> 00:04:27.040 align:start position:0% at the label and then finds the the text 00:04:27.040 --> 00:04:28.550 align:start position:0% at the label and then finds the the text field<00:04:27.280> associated<00:04:27.759> with<00:04:28.000> it<00:04:28.080> to<00:04:28.320> do<00:04:28.479> the 00:04:28.550 --> 00:04:28.560 align:start position:0% field associated with it to do the 00:04:28.560 --> 00:04:30.070 align:start position:0% field associated with it to do the username 00:04:30.070 --> 00:04:30.080 align:start position:0% username 00:04:30.080 --> 00:04:31.990 align:start position:0% username you<00:04:30.160> don't<00:04:30.400> always<00:04:30.720> have 00:04:31.990 --> 00:04:32.000 align:start position:0% you don't always have 00:04:32.000 --> 00:04:35.270 align:start position:0% you don't always have labels<00:04:32.400> so<00:04:32.880> it<00:04:33.120> also<00:04:33.360> allows<00:04:33.600> you<00:04:33.759> to<00:04:33.840> do<00:04:34.160> css 00:04:35.270 --> 00:04:35.280 align:start position:0% labels so it also allows you to do css 00:04:35.280 --> 00:04:38.629 align:start position:0% labels so it also allows you to do css the<00:04:35.440> in<00:04:35.600> live<00:04:35.840> selector<00:04:36.240> syntax<00:04:36.880> to<00:04:37.199> choose 00:04:38.629 --> 00:04:38.639 align:start position:0% the in live selector syntax to choose 00:04:38.639 --> 00:04:40.550 align:start position:0% the in live selector syntax to choose what<00:04:38.880> html<00:04:39.440> elements<00:04:39.840> you're<00:04:40.000> interacting 00:04:40.550 --> 00:04:40.560 align:start position:0% what html elements you're interacting 00:04:40.560 --> 00:04:42.150 align:start position:0% what html elements you're interacting with 00:04:42.150 --> 00:04:42.160 align:start position:0% with 00:04:42.160 --> 00:04:44.150 align:start position:0% with in<00:04:42.320> addition<00:04:42.639> there's<00:04:42.960> a<00:04:43.199> within<00:04:43.680> form<00:04:43.919> that<00:04:44.000> i 00:04:44.150 --> 00:04:44.160 align:start position:0% in addition there's a within form that i 00:04:44.160 --> 00:04:45.510 align:start position:0% in addition there's a within form that i added<00:04:44.400> up<00:04:44.560> on<00:04:44.639> that<00:04:44.880> slide<00:04:45.120> that<00:04:45.199> was<00:04:45.280> not<00:04:45.440> on 00:04:45.510 --> 00:04:45.520 align:start position:0% added up on that slide that was not on 00:04:45.520 --> 00:04:46.710 align:start position:0% added up on that slide that was not on the<00:04:45.600> previous<00:04:45.919> one 00:04:46.710 --> 00:04:46.720 align:start position:0% the previous one 00:04:46.720 --> 00:04:50.150 align:start position:0% the previous one that<00:04:46.960> allows<00:04:47.280> you<00:04:47.520> to<00:04:47.840> scope<00:04:48.639> all<00:04:49.040> of<00:04:49.680> the 00:04:50.150 --> 00:04:50.160 align:start position:0% that allows you to scope all of the 00:04:50.160 --> 00:04:52.230 align:start position:0% that allows you to scope all of the interactions<00:04:50.639> in<00:04:50.720> the<00:04:50.800> body<00:04:51.360> to<00:04:52.000> that 00:04:52.230 --> 00:04:52.240 align:start position:0% interactions in the body to that 00:04:52.240 --> 00:04:58.310 align:start position:0% interactions in the body to that particular<00:04:52.720> section<00:04:53.120> of<00:04:53.199> the<00:04:53.440> html 00:04:58.310 --> 00:04:58.320 align:start position:0% 00:04:58.320 --> 00:05:01.110 align:start position:0% uh<00:04:58.479> in<00:04:58.639> addition<00:04:59.199> i<00:04:59.440> like<00:04:59.680> to<00:05:00.080> to<00:05:00.320> be<00:05:00.479> able<00:05:00.639> to 00:05:01.110 --> 00:05:01.120 align:start position:0% uh in addition i like to to be able to 00:05:01.120 --> 00:05:04.230 align:start position:0% uh in addition i like to to be able to go<00:05:01.440> through<00:05:02.000> a<00:05:02.160> portion<00:05:02.560> of<00:05:03.199> the<00:05:03.360> test 00:05:04.230 --> 00:05:04.240 align:start position:0% go through a portion of the test 00:05:04.240 --> 00:05:06.070 align:start position:0% go through a portion of the test to<00:05:04.400> do<00:05:05.040> some<00:05:05.280> interaction<00:05:05.600> with<00:05:05.759> the<00:05:05.840> website 00:05:06.070 --> 00:05:06.080 align:start position:0% to do some interaction with the website 00:05:06.080 --> 00:05:08.390 align:start position:0% to do some interaction with the website and<00:05:06.160> then<00:05:06.320> actually<00:05:06.639> test<00:05:06.880> some<00:05:07.039> of<00:05:07.120> the<00:05:07.360> uh 00:05:08.390 --> 00:05:08.400 align:start position:0% and then actually test some of the uh 00:05:08.400 --> 00:05:09.909 align:start position:0% and then actually test some of the uh that<00:05:08.639> i'm<00:05:08.800> actually<00:05:09.039> getting<00:05:09.280> what<00:05:09.440> i<00:05:09.600> expect 00:05:09.909 --> 00:05:09.919 align:start position:0% that i'm actually getting what i expect 00:05:09.919 --> 00:05:12.390 align:start position:0% that i'm actually getting what i expect and<00:05:10.000> then<00:05:10.160> continue<00:05:10.560> on<00:05:11.199> so<00:05:11.360> carried<00:05:11.680> in<00:05:11.840> has<00:05:12.080> a 00:05:12.390 --> 00:05:12.400 align:start position:0% and then continue on so carried in has a 00:05:12.400 --> 00:05:13.990 align:start position:0% and then continue on so carried in has a selection<00:05:13.120> a<00:05:13.199> small<00:05:13.520> selection<00:05:13.840> at<00:05:13.919> the 00:05:13.990 --> 00:05:14.000 align:start position:0% selection a small selection at the 00:05:14.000 --> 00:05:16.150 align:start position:0% selection a small selection at the moment<00:05:14.400> of<00:05:14.800> test<00:05:15.039> helpers 00:05:16.150 --> 00:05:16.160 align:start position:0% moment of test helpers 00:05:16.160 --> 00:05:17.590 align:start position:0% moment of test helpers uh 00:05:17.590 --> 00:05:17.600 align:start position:0% uh 00:05:17.600 --> 00:05:19.749 align:start position:0% uh you<00:05:17.840> wrap<00:05:18.080> them<00:05:18.240> in<00:05:18.320> the<00:05:18.400> has<00:05:18.720> function<00:05:19.440> and<00:05:19.680> in 00:05:19.749 --> 00:05:19.759 align:start position:0% you wrap them in the has function and in 00:05:19.759 --> 00:05:21.110 align:start position:0% you wrap them in the has function and in this<00:05:19.919> case<00:05:20.160> we're<00:05:20.320> actually<00:05:20.639> checking 00:05:21.110 --> 00:05:21.120 align:start position:0% this case we're actually checking 00:05:21.120 --> 00:05:22.629 align:start position:0% this case we're actually checking whenever<00:05:21.440> we<00:05:21.520> go<00:05:21.680> to<00:05:21.759> the<00:05:21.840> root<00:05:22.000> page<00:05:22.400> did<00:05:22.560> we 00:05:22.629 --> 00:05:22.639 align:start position:0% whenever we go to the root page did we 00:05:22.639 --> 00:05:25.430 align:start position:0% whenever we go to the root page did we get<00:05:22.720> a<00:05:22.880> 200<00:05:23.280> response<00:05:24.000> uh<00:05:24.400> status 00:05:25.430 --> 00:05:25.440 align:start position:0% get a 200 response uh status 00:05:25.440 --> 00:05:27.590 align:start position:0% get a 200 response uh status and<00:05:25.759> does<00:05:25.919> it<00:05:26.080> have<00:05:26.720> does<00:05:26.880> the<00:05:26.960> page<00:05:27.280> text 00:05:27.590 --> 00:05:27.600 align:start position:0% and does it have does the page text 00:05:27.600 --> 00:05:29.830 align:start position:0% and does it have does the page text actually<00:05:27.919> have<00:05:28.400> hello<00:05:28.720> world<00:05:28.960> in<00:05:29.120> it<00:05:29.520> so<00:05:29.680> it 00:05:29.830 --> 00:05:29.840 align:start position:0% actually have hello world in it so it 00:05:29.840 --> 00:05:31.830 align:start position:0% actually have hello world in it so it actually<00:05:30.160> parses<00:05:30.639> out<00:05:31.039> you<00:05:31.120> know<00:05:31.280> goes<00:05:31.520> uses 00:05:31.830 --> 00:05:31.840 align:start position:0% actually parses out you know goes uses 00:05:31.840 --> 00:05:33.590 align:start position:0% actually parses out you know goes uses in<00:05:32.000> live<00:05:32.160> and<00:05:32.320> checks<00:05:32.639> through<00:05:32.880> the<00:05:32.960> html<00:05:33.520> and 00:05:33.590 --> 00:05:33.600 align:start position:0% in live and checks through the html and 00:05:33.600 --> 00:05:35.590 align:start position:0% in live and checks through the html and gets<00:05:33.840> out<00:05:33.919> what's<00:05:34.240> in<00:05:34.320> the<00:05:34.400> body<00:05:34.720> and 00:05:35.590 --> 00:05:35.600 align:start position:0% gets out what's in the body and 00:05:35.600 --> 00:05:38.310 align:start position:0% gets out what's in the body and checks<00:05:35.840> the<00:05:36.000> text<00:05:36.240> for<00:05:36.400> that 00:05:38.310 --> 00:05:38.320 align:start position:0% checks the text for that 00:05:38.320 --> 00:05:39.350 align:start position:0% checks the text for that and<00:05:38.400> then<00:05:38.560> once<00:05:38.800> we've<00:05:38.960> done<00:05:39.120> those 00:05:39.350 --> 00:05:39.360 align:start position:0% and then once we've done those 00:05:39.360 --> 00:05:41.029 align:start position:0% and then once we've done those particular<00:05:39.840> tests<00:05:40.080> we<00:05:40.160> can<00:05:40.400> it<00:05:40.560> will<00:05:40.720> actually 00:05:41.029 --> 00:05:41.039 align:start position:0% particular tests we can it will actually 00:05:41.039 --> 00:05:43.590 align:start position:0% particular tests we can it will actually continue<00:05:41.440> running<00:05:41.919> and<00:05:42.479> we'll<00:05:43.120> as<00:05:43.360> you<00:05:43.440> see 00:05:43.590 --> 00:05:43.600 align:start position:0% continue running and we'll as you see 00:05:43.600 --> 00:05:46.230 align:start position:0% continue running and we'll as you see that<00:05:43.680> i<00:05:43.759> can<00:05:43.919> do<00:05:44.160> a<00:05:44.560> following<00:05:45.120> of<00:05:45.280> a<00:05:45.360> link<00:05:46.080> in 00:05:46.230 --> 00:05:46.240 align:start position:0% that i can do a following of a link in 00:05:46.240 --> 00:05:50.150 align:start position:0% that i can do a following of a link in this<00:05:46.400> case<00:05:46.720> to<00:05:47.120> whatever<00:05:47.600> reason<00:05:48.000> would<00:05:48.160> be 00:05:50.150 --> 00:05:50.160 align:start position:0% this case to whatever reason would be 00:05:50.160 --> 00:05:53.909 align:start position:0% this case to whatever reason would be this<00:05:50.479> works<00:05:50.880> by<00:05:51.199> hooking<00:05:51.840> into<00:05:52.560> closure.test 00:05:53.909 --> 00:05:53.919 align:start position:0% this works by hooking into closure.test 00:05:53.919 --> 00:05:55.350 align:start position:0% this works by hooking into closure.test as 00:05:55.350 --> 00:05:55.360 align:start position:0% as 00:05:55.360 --> 00:05:56.390 align:start position:0% as through<00:05:55.600> some<00:05:55.759> of<00:05:55.840> the<00:05:56.000> underlying 00:05:56.390 --> 00:05:56.400 align:start position:0% through some of the underlying 00:05:56.400 --> 00:05:58.950 align:start position:0% through some of the underlying mechanisms<00:05:56.960> of<00:05:57.120> it<00:05:57.680> i<00:05:57.840> don't<00:05:58.080> have<00:05:58.240> anything 00:05:58.950 --> 00:05:58.960 align:start position:0% mechanisms of it i don't have anything 00:05:58.960 --> 00:06:00.230 align:start position:0% mechanisms of it i don't have anything for 00:06:00.230 --> 00:06:00.240 align:start position:0% for 00:06:00.240 --> 00:06:02.710 align:start position:0% for expectations<00:06:01.039> or<00:06:01.280> midge<00:06:02.000> as<00:06:02.240> i<00:06:02.320> do<00:06:02.479> not 00:06:02.710 --> 00:06:02.720 align:start position:0% expectations or midge as i do not 00:06:02.720 --> 00:06:04.830 align:start position:0% expectations or midge as i do not particularly<00:06:03.199> use<00:06:03.360> those<00:06:03.600> ones 00:06:04.830 --> 00:06:04.840 align:start position:0% particularly use those ones 00:06:04.840 --> 00:06:07.670 align:start position:0% particularly use those ones yet<00:06:05.600> uh<00:06:06.160> let's<00:06:06.400> see 00:06:07.670 --> 00:06:07.680 align:start position:0% yet uh let's see 00:06:07.680 --> 00:06:09.590 align:start position:0% yet uh let's see in<00:06:07.759> the<00:06:07.919> future<00:06:08.720> uh<00:06:09.039> there's<00:06:09.199> still<00:06:09.360> some 00:06:09.590 --> 00:06:09.600 align:start position:0% in the future uh there's still some 00:06:09.600 --> 00:06:11.270 align:start position:0% in the future uh there's still some additions<00:06:09.919> that<00:06:10.000> need<00:06:10.160> to<00:06:10.240> be<00:06:10.400> made<00:06:11.039> uh 00:06:11.270 --> 00:06:11.280 align:start position:0% additions that need to be made uh 00:06:11.280 --> 00:06:12.629 align:start position:0% additions that need to be made uh peridot<00:06:11.759> for<00:06:11.840> example<00:06:12.160> doesn't<00:06:12.400> really 00:06:12.629 --> 00:06:12.639 align:start position:0% peridot for example doesn't really 00:06:12.639 --> 00:06:15.590 align:start position:0% peridot for example doesn't really support<00:06:13.360> uh<00:06:13.680> nested<00:06:14.000> parameters 00:06:15.590 --> 00:06:15.600 align:start position:0% support uh nested parameters 00:06:15.600 --> 00:06:17.430 align:start position:0% support uh nested parameters uh<00:06:16.160> so<00:06:16.479> it'd<00:06:16.560> be<00:06:16.720> nice<00:06:16.880> to<00:06:17.039> actually<00:06:17.280> have 00:06:17.430 --> 00:06:17.440 align:start position:0% uh so it'd be nice to actually have 00:06:17.440 --> 00:06:18.790 align:start position:0% uh so it'd be nice to actually have those<00:06:17.759> go<00:06:17.919> in<00:06:18.080> where 00:06:18.790 --> 00:06:18.800 align:start position:0% those go in where 00:06:18.800 --> 00:06:20.790 align:start position:0% those go in where if<00:06:18.960> you<00:06:19.039> have<00:06:19.280> the<00:06:19.440> wrap<00:06:19.680> nested<00:06:20.000> parameters 00:06:20.790 --> 00:06:20.800 align:start position:0% if you have the wrap nested parameters 00:06:20.800 --> 00:06:22.710 align:start position:0% if you have the wrap nested parameters uh 00:06:22.710 --> 00:06:22.720 align:start position:0% uh 00:06:22.720 --> 00:06:24.070 align:start position:0% uh middleware 00:06:24.070 --> 00:06:24.080 align:start position:0% middleware 00:06:24.080 --> 00:06:25.909 align:start position:0% middleware you<00:06:24.240> can<00:06:24.479> actually<00:06:24.880> keep<00:06:25.120> those<00:06:25.440> in<00:06:25.520> line<00:06:25.759> as 00:06:25.909 --> 00:06:25.919 align:start position:0% you can actually keep those in line as 00:06:25.919 --> 00:06:27.990 align:start position:0% you can actually keep those in line as you<00:06:26.000> would<00:06:26.160> expect 00:06:27.990 --> 00:06:28.000 align:start position:0% you would expect 00:06:28.000 --> 00:06:29.590 align:start position:0% you would expect that<00:06:28.240> actually<00:06:28.639> might<00:06:28.880> end<00:06:29.039> up<00:06:29.120> being<00:06:29.360> better 00:06:29.590 --> 00:06:29.600 align:start position:0% that actually might end up being better 00:06:29.600 --> 00:06:31.749 align:start position:0% that actually might end up being better off<00:06:29.840> in<00:06:30.080> ring<00:06:30.400> box<00:06:30.800> so<00:06:30.960> if<00:06:31.120> i<00:06:31.280> when<00:06:31.440> i<00:06:31.600> get<00:06:31.680> to 00:06:31.749 --> 00:06:31.759 align:start position:0% off in ring box so if i when i get to 00:06:31.759 --> 00:06:33.189 align:start position:0% off in ring box so if i when i get to that<00:06:32.000> it<00:06:32.080> might<00:06:32.319> end<00:06:32.479> up<00:06:32.560> being<00:06:32.800> a<00:06:32.880> patch<00:06:33.120> in 00:06:33.189 --> 00:06:33.199 align:start position:0% that it might end up being a patch in 00:06:33.199 --> 00:06:35.430 align:start position:0% that it might end up being a patch in that<00:06:33.360> direction 00:06:35.430 --> 00:06:35.440 align:start position:0% that direction 00:06:35.440 --> 00:06:37.830 align:start position:0% that direction in<00:06:35.600> addition<00:06:36.000> keratin<00:06:36.479> doesn't<00:06:37.199> yet<00:06:37.440> support 00:06:37.830 --> 00:06:37.840 align:start position:0% in addition keratin doesn't yet support 00:06:37.840 --> 00:06:39.510 align:start position:0% in addition keratin doesn't yet support all<00:06:38.000> of<00:06:38.160> the<00:06:38.319> different<00:06:38.560> html<00:06:39.039> elements<00:06:39.440> i 00:06:39.510 --> 00:06:39.520 align:start position:0% all of the different html elements i 00:06:39.520 --> 00:06:41.189 align:start position:0% all of the different html elements i need<00:06:39.680> to<00:06:39.759> make<00:06:39.919> it<00:06:40.240> understand<00:06:40.720> things<00:06:40.960> about 00:06:41.189 --> 00:06:41.199 align:start position:0% need to make it understand things about 00:06:41.199 --> 00:06:43.749 align:start position:0% need to make it understand things about check<00:06:41.440> boxes<00:06:42.000> and<00:06:42.160> radio<00:06:42.479> buttons<00:06:43.360> and<00:06:43.520> drop 00:06:43.749 --> 00:06:43.759 align:start position:0% check boxes and radio buttons and drop 00:06:43.759 --> 00:06:46.710 align:start position:0% check boxes and radio buttons and drop downs<00:06:44.400> and<00:06:44.560> then<00:06:44.800> just<00:06:45.520> figure<00:06:45.840> out<00:06:46.080> what<00:06:46.479> else 00:06:46.710 --> 00:06:46.720 align:start position:0% downs and then just figure out what else 00:06:46.720 --> 00:06:50.070 align:start position:0% downs and then just figure out what else works<00:06:47.120> good<00:06:47.440> for<00:06:47.840> test<00:06:48.080> helpers 00:06:50.070 --> 00:06:50.080 align:start position:0% works good for test helpers 00:06:50.080 --> 00:06:52.070 align:start position:0% works good for test helpers not<00:06:50.400> on<00:06:50.560> here<00:06:50.880> is<00:06:51.039> i'd<00:06:51.199> like<00:06:51.440> to<00:06:51.600> eventually 00:06:52.070 --> 00:06:52.080 align:start position:0% not on here is i'd like to eventually 00:06:52.080 --> 00:06:54.469 align:start position:0% not on here is i'd like to eventually even<00:06:52.479> have<00:06:52.639> it<00:06:52.800> the<00:06:52.880> ability<00:06:53.280> to<00:06:53.919> say<00:06:54.240> instead 00:06:54.469 --> 00:06:54.479 align:start position:0% even have it the ability to say instead 00:06:54.479 --> 00:06:56.790 align:start position:0% even have it the ability to say instead of<00:06:54.560> using<00:06:55.120> peridot<00:06:55.600> and<00:06:55.759> in<00:06:55.919> live 00:06:56.790 --> 00:06:56.800 align:start position:0% of using peridot and in live 00:06:56.800 --> 00:06:59.510 align:start position:0% of using peridot and in live can<00:06:56.960> you<00:06:57.120> instead<00:06:57.440> use<00:06:57.680> clj<00:06:58.160> webdriver 00:06:59.510 --> 00:06:59.520 align:start position:0% can you instead use clj webdriver 00:06:59.520 --> 00:07:01.110 align:start position:0% can you instead use clj webdriver as<00:06:59.680> part<00:06:59.840> of<00:06:59.919> this<00:07:00.080> session<00:07:00.479> so<00:07:00.639> that<00:07:00.720> you<00:07:00.880> can 00:07:01.110 --> 00:07:01.120 align:start position:0% as part of this session so that you can 00:07:01.120 --> 00:07:03.189 align:start position:0% as part of this session so that you can actually<00:07:01.599> do<00:07:02.000> javascript<00:07:02.639> you<00:07:02.800> know<00:07:02.880> testing 00:07:03.189 --> 00:07:03.199 align:start position:0% actually do javascript you know testing 00:07:03.199 --> 00:07:04.790 align:start position:0% actually do javascript you know testing so<00:07:03.360> that<00:07:03.440> whenever<00:07:03.680> you<00:07:03.759> actually<00:07:04.160> start<00:07:04.639> you 00:07:04.790 --> 00:07:04.800 align:start position:0% so that whenever you actually start you 00:07:04.800 --> 00:07:06.070 align:start position:0% so that whenever you actually start you have<00:07:04.880> your<00:07:04.960> html<00:07:05.360> page<00:07:05.599> and<00:07:05.680> you<00:07:05.759> got<00:07:05.840> a<00:07:05.919> little 00:07:06.070 --> 00:07:06.080 align:start position:0% have your html page and you got a little 00:07:06.080 --> 00:07:08.230 align:start position:0% have your html page and you got a little bit<00:07:06.160> of<00:07:06.240> ajax<00:07:06.720> you<00:07:06.800> don't<00:07:06.960> have<00:07:07.039> to<00:07:07.199> port 00:07:08.230 --> 00:07:08.240 align:start position:0% bit of ajax you don't have to port 00:07:08.240 --> 00:07:09.749 align:start position:0% bit of ajax you don't have to port you<00:07:08.319> know<00:07:08.560> whatever<00:07:08.960> in<00:07:09.039> your<00:07:09.199> test<00:07:09.360> suite<00:07:09.680> it 00:07:09.749 --> 00:07:09.759 align:start position:0% you know whatever in your test suite it 00:07:09.759 --> 00:07:11.510 align:start position:0% you know whatever in your test suite it is<00:07:09.840> that<00:07:10.000> now<00:07:10.240> has<00:07:10.400> to<00:07:10.479> do<00:07:10.560> with<00:07:10.720> the<00:07:10.800> ajax<00:07:11.199> call 00:07:11.510 --> 00:07:11.520 align:start position:0% is that now has to do with the ajax call 00:07:11.520 --> 00:07:14.830 align:start position:0% is that now has to do with the ajax call you<00:07:11.599> can<00:07:11.680> just<00:07:12.240> flip<00:07:12.479> a<00:07:12.560> switch<00:07:12.880> hopefully 00:07:14.830 --> 00:07:14.840 align:start position:0% you can just flip a switch hopefully 00:07:14.840 --> 00:07:18.390 align:start position:0% you can just flip a switch hopefully uh<00:07:16.000> there<00:07:16.319> are<00:07:16.560> where<00:07:16.720> they<00:07:16.880> are<00:07:17.120> on<00:07:17.280> github 00:07:18.390 --> 00:07:18.400 align:start position:0% uh there are where they are on github 00:07:18.400 --> 00:07:20.710 align:start position:0% uh there are where they are on github uh<00:07:18.639> that's<00:07:18.880> my<00:07:19.120> url<00:07:19.680> and<00:07:19.919> twitter<00:07:20.160> handler<00:07:20.639> if 00:07:20.710 --> 00:07:20.720 align:start position:0% uh that's my url and twitter handler if 00:07:20.720 --> 00:07:21.909 align:start position:0% uh that's my url and twitter handler if you<00:07:20.800> want<00:07:21.039> twitter<00:07:21.360> handle<00:07:21.599> if<00:07:21.680> you<00:07:21.759> want<00:07:21.840> to 00:07:21.909 --> 00:07:21.919 align:start position:0% you want twitter handle if you want to 00:07:21.919 --> 00:07:23.189 align:start position:0% you want twitter handle if you want to find<00:07:22.240> me 00:07:23.189 --> 00:07:23.199 align:start position:0% find me 00:07:23.199 --> 00:07:25.350 align:start position:0% find me and<00:07:23.680> if<00:07:23.840> you<00:07:23.919> want<00:07:24.080> to<00:07:24.160> see<00:07:24.400> some<00:07:24.560> examples<00:07:25.120> of 00:07:25.350 --> 00:07:25.360 align:start position:0% and if you want to see some examples of 00:07:25.360 --> 00:07:27.589 align:start position:0% and if you want to see some examples of keratin<00:07:25.919> actually<00:07:26.240> in<00:07:26.400> use<00:07:27.039> if<00:07:27.120> you<00:07:27.199> go<00:07:27.360> check 00:07:27.589 --> 00:07:27.599 align:start position:0% keratin actually in use if you go check 00:07:27.599 --> 00:07:30.309 align:start position:0% keratin actually in use if you go check out<00:07:27.759> the<00:07:28.000> clojars<00:07:28.639> test<00:07:28.800> suite<00:07:29.440> there<00:07:29.919> are 00:07:30.309 --> 00:07:30.319 align:start position:0% out the clojars test suite there are 00:07:30.319 --> 00:07:32.230 align:start position:0% out the clojars test suite there are lots<00:07:30.560> of<00:07:30.720> examples<00:07:31.120> of<00:07:31.280> it<00:07:31.520> this<00:07:31.680> is<00:07:31.840> actually 00:07:32.230 --> 00:07:32.240 align:start position:0% lots of examples of it this is actually 00:07:32.240 --> 00:07:34.550 align:start position:0% lots of examples of it this is actually what<00:07:32.800> the<00:07:32.960> reason<00:07:33.280> i<00:07:33.440> ended<00:07:33.599> up<00:07:33.759> building<00:07:34.240> uh 00:07:34.550 --> 00:07:34.560 align:start position:0% what the reason i ended up building uh 00:07:34.560 --> 00:07:36.629 align:start position:0% what the reason i ended up building uh these<00:07:34.720> particular<00:07:35.120> tools<00:07:35.440> for 00:07:36.629 --> 00:07:36.639 align:start position:0% these particular tools for 00:07:36.639 --> 00:07:39.270 align:start position:0% these particular tools for thank<00:07:36.800> you 00:07:39.270 --> 00:07:39.280 align:start position:0% 00:07:39.280 --> 00:07:41.430 align:start position:0% here 00:07:41.430 --> 00:07:41.440 align:start position:0% here 00:07:41.440 --> 00:07:42.150 align:start position:0% here hi 00:07:42.150 --> 00:07:42.160 align:start position:0% hi 00:07:42.160 --> 00:07:44.710 align:start position:0% hi i'm<00:07:42.319> dan<00:07:42.560> ledrill<00:07:42.880> porter<00:07:43.599> i<00:07:44.160> am<00:07:44.319> frequently 00:07:44.710 --> 00:07:44.720 align:start position:0% i'm dan ledrill porter i am frequently 00:07:44.720 --> 00:07:47.589 align:start position:0% i'm dan ledrill porter i am frequently known<00:07:44.960> on<00:07:45.039> the<00:07:45.120> internet<00:07:45.599> as<00:07:46.240> a<00:07:46.400> periodic 00:07:47.589 --> 00:07:47.599 align:start position:0% known on the internet as a periodic 00:07:47.599 --> 00:07:49.510 align:start position:0% known on the internet as a periodic and<00:07:47.840> i'm<00:07:48.000> someone<00:07:48.400> who<00:07:48.639> until<00:07:48.960> five<00:07:49.199> or<00:07:49.280> six 00:07:49.510 --> 00:07:49.520 align:start position:0% and i'm someone who until five or six 00:07:49.520 --> 00:07:51.350 align:start position:0% and i'm someone who until five or six years<00:07:49.759> ago<00:07:50.000> would<00:07:50.240> have<00:07:50.319> described<00:07:50.720> myself<00:07:51.120> as 00:07:51.350 --> 00:07:51.360 align:start position:0% years ago would have described myself as 00:07:51.360 --> 00:07:53.990 align:start position:0% years ago would have described myself as primarily<00:07:52.000> a<00:07:52.080> visual<00:07:52.479> artist<00:07:53.199> uh<00:07:53.599> now<00:07:53.759> i<00:07:53.840> like 00:07:53.990 --> 00:07:54.000 align:start position:0% primarily a visual artist uh now i like 00:07:54.000 --> 00:07:56.309 align:start position:0% primarily a visual artist uh now i like to<00:07:54.080> call<00:07:54.319> myself<00:07:54.720> a<00:07:54.879> programmer<00:07:55.680> and<00:07:55.840> the<00:07:56.080> big 00:07:56.309 --> 00:07:56.319 align:start position:0% to call myself a programmer and the big 00:07:56.319 --> 00:07:59.270 align:start position:0% to call myself a programmer and the big reason<00:07:56.639> for<00:07:56.720> that<00:07:56.960> change<00:07:57.440> is<00:07:57.759> processing<00:07:58.879> so 00:07:59.270 --> 00:07:59.280 align:start position:0% reason for that change is processing so 00:07:59.280 --> 00:08:01.029 align:start position:0% reason for that change is processing so if<00:07:59.360> you<00:07:59.520> haven't<00:07:59.680> heard<00:07:59.840> of<00:08:00.000> it<00:08:00.080> processing<00:08:00.879> is 00:08:01.029 --> 00:08:01.039 align:start position:0% if you haven't heard of it processing is 00:08:01.039 --> 00:08:02.950 align:start position:0% if you haven't heard of it processing is a<00:08:01.280> programming<00:08:01.759> language 00:08:02.950 --> 00:08:02.960 align:start position:0% a programming language 00:08:02.960 --> 00:08:05.270 align:start position:0% a programming language environment<00:08:03.840> that's<00:08:04.240> uh<00:08:04.479> was<00:08:04.720> designed<00:08:05.120> with 00:08:05.270 --> 00:08:05.280 align:start position:0% environment that's uh was designed with 00:08:05.280 --> 00:08:07.670 align:start position:0% environment that's uh was designed with the<00:08:05.440> aim<00:08:05.759> of<00:08:06.319> encouraging<00:08:06.879> programming<00:08:07.440> among 00:08:07.670 --> 00:08:07.680 align:start position:0% the aim of encouraging programming among 00:08:07.680 --> 00:08:08.950 align:start position:0% the aim of encouraging programming among the<00:08:07.759> visual<00:08:08.160> arts 00:08:08.950 --> 00:08:08.960 align:start position:0% the visual arts 00:08:08.960 --> 00:08:11.029 align:start position:0% the visual arts um<00:08:09.280> so<00:08:09.520> it's<00:08:09.680> got<00:08:09.919> a<00:08:10.160> straightforward<00:08:10.639> drawing 00:08:11.029 --> 00:08:11.039 align:start position:0% um so it's got a straightforward drawing 00:08:11.039 --> 00:08:13.270 align:start position:0% um so it's got a straightforward drawing api<00:08:11.440> that's<00:08:12.160> sort<00:08:12.319> of<00:08:12.400> similar<00:08:12.720> to<00:08:12.800> html 00:08:13.270 --> 00:08:13.280 align:start position:0% api that's sort of similar to html 00:08:13.280 --> 00:08:14.309 align:start position:0% api that's sort of similar to html canvas 00:08:14.309 --> 00:08:14.319 align:start position:0% canvas 00:08:14.319 --> 00:08:15.909 align:start position:0% canvas but<00:08:14.479> it<00:08:14.560> has<00:08:14.720> a<00:08:14.720> lot<00:08:14.879> of<00:08:15.039> other<00:08:15.199> capabilities 00:08:15.909 --> 00:08:15.919 align:start position:0% but it has a lot of other capabilities 00:08:15.919 --> 00:08:18.230 align:start position:0% but it has a lot of other capabilities besides<00:08:16.400> it<00:08:16.479> can<00:08:16.639> do<00:08:16.879> 3d<00:08:17.520> you<00:08:17.680> can<00:08:17.759> do<00:08:18.000> video 00:08:18.230 --> 00:08:18.240 align:start position:0% besides it can do 3d you can do video 00:08:18.240 --> 00:08:20.390 align:start position:0% besides it can do 3d you can do video rendering<00:08:18.720> audio<00:08:19.039> input<00:08:19.360> audio<00:08:19.680> synthesis<00:08:20.240> it 00:08:20.390 --> 00:08:20.400 align:start position:0% rendering audio input audio synthesis it 00:08:20.400 --> 00:08:22.150 align:start position:0% rendering audio input audio synthesis it can<00:08:20.479> talk<00:08:20.639> to<00:08:20.720> arduinos<00:08:21.360> it<00:08:21.440> can<00:08:21.520> get<00:08:21.759> inputs 00:08:22.150 --> 00:08:22.160 align:start position:0% can talk to arduinos it can get inputs 00:08:22.160 --> 00:08:24.469 align:start position:0% can talk to arduinos it can get inputs from<00:08:22.879> k'nex<00:08:23.599> um 00:08:24.469 --> 00:08:24.479 align:start position:0% from k'nex um 00:08:24.479 --> 00:08:26.790 align:start position:0% from k'nex um a<00:08:24.639> whole<00:08:24.800> bunch<00:08:25.039> of<00:08:25.120> stuff<00:08:25.840> so<00:08:26.000> the<00:08:26.160> neat<00:08:26.479> handy 00:08:26.790 --> 00:08:26.800 align:start position:0% a whole bunch of stuff so the neat handy 00:08:26.800 --> 00:08:28.950 align:start position:0% a whole bunch of stuff so the neat handy thing<00:08:26.960> about<00:08:27.360> processing<00:08:28.000> is<00:08:28.160> that<00:08:28.639> under<00:08:28.879> the 00:08:28.950 --> 00:08:28.960 align:start position:0% thing about processing is that under the 00:08:28.960 --> 00:08:30.230 align:start position:0% thing about processing is that under the hood<00:08:29.280> it's<00:08:29.440> really<00:08:29.599> just<00:08:29.759> some<00:08:29.919> java 00:08:30.230 --> 00:08:30.240 align:start position:0% hood it's really just some java 00:08:30.240 --> 00:08:32.469 align:start position:0% hood it's really just some java libraries<00:08:31.039> uh<00:08:31.280> so<00:08:31.440> that<00:08:31.599> means<00:08:31.759> we<00:08:31.919> can<00:08:32.080> use<00:08:32.320> it 00:08:32.469 --> 00:08:32.479 align:start position:0% libraries uh so that means we can use it 00:08:32.479 --> 00:08:34.550 align:start position:0% libraries uh so that means we can use it in<00:08:32.560> closure<00:08:33.440> and<00:08:33.680> that's<00:08:33.839> where<00:08:34.000> quilt<00:08:34.240> comes 00:08:34.550 --> 00:08:34.560 align:start position:0% in closure and that's where quilt comes 00:08:34.560 --> 00:08:36.709 align:start position:0% in closure and that's where quilt comes in<00:08:34.880> it<00:08:34.959> was<00:08:35.200> originally<00:08:35.680> started 00:08:36.709 --> 00:08:36.719 align:start position:0% in it was originally started 00:08:36.719 --> 00:08:39.589 align:start position:0% in it was originally started as<00:08:36.959> clj<00:08:37.519> processing<00:08:38.080> by<00:08:38.240> roland<00:08:38.560> stadowski<00:08:39.519> it 00:08:39.589 --> 00:08:39.599 align:start position:0% as clj processing by roland stadowski it 00:08:39.599 --> 00:08:41.909 align:start position:0% as clj processing by roland stadowski it was<00:08:39.839> now<00:08:40.159> primarily<00:08:40.640> maintained<00:08:41.039> by<00:08:41.360> sam<00:08:41.599> erin 00:08:41.909 --> 00:08:41.919 align:start position:0% was now primarily maintained by sam erin 00:08:41.919 --> 00:08:44.310 align:start position:0% was now primarily maintained by sam erin who<00:08:42.080> gave<00:08:42.320> it<00:08:42.399> the<00:08:42.640> quill<00:08:42.880> moniker 00:08:44.310 --> 00:08:44.320 align:start position:0% who gave it the quill moniker 00:08:44.320 --> 00:08:45.430 align:start position:0% who gave it the quill moniker and<00:08:44.480> it's<00:08:44.560> just<00:08:44.800> a<00:08:44.880> wrapper<00:08:45.200> around 00:08:45.430 --> 00:08:45.440 align:start position:0% and it's just a wrapper around 00:08:45.440 --> 00:08:47.030 align:start position:0% and it's just a wrapper around processing<00:08:46.000> that<00:08:46.160> makes<00:08:46.399> it<00:08:46.560> a<00:08:46.640> lot<00:08:46.800> more 00:08:47.030 --> 00:08:47.040 align:start position:0% processing that makes it a lot more 00:08:47.040 --> 00:08:49.910 align:start position:0% processing that makes it a lot more pleasant<00:08:47.440> to<00:08:47.680> use<00:08:48.399> in<00:08:48.560> closure<00:08:49.120> than<00:08:49.680> if<00:08:49.839> we 00:08:49.910 --> 00:08:49.920 align:start position:0% pleasant to use in closure than if we 00:08:49.920 --> 00:08:52.310 align:start position:0% pleasant to use in closure than if we had<00:08:50.080> to<00:08:50.160> do<00:08:50.240> a<00:08:50.320> lot<00:08:50.480> of<00:08:50.640> java<00:08:50.959> interop 00:08:52.310 --> 00:08:52.320 align:start position:0% had to do a lot of java interop 00:08:52.320 --> 00:08:54.070 align:start position:0% had to do a lot of java interop so<00:08:52.560> what<00:08:52.800> i'm<00:08:52.959> going<00:08:53.120> to<00:08:53.200> do<00:08:53.519> is<00:08:53.680> i'm<00:08:53.760> going<00:08:53.920> to 00:08:54.070 --> 00:08:54.080 align:start position:0% so what i'm going to do is i'm going to 00:08:54.080 --> 00:08:55.829 align:start position:0% so what i'm going to do is i'm going to walk<00:08:54.320> you<00:08:54.480> through<00:08:54.720> creating<00:08:55.200> a<00:08:55.600> pretty 00:08:55.829 --> 00:08:55.839 align:start position:0% walk you through creating a pretty 00:08:55.839 --> 00:08:58.230 align:start position:0% walk you through creating a pretty simple<00:08:56.320> quill<00:08:56.560> sketch<00:08:57.040> in<00:08:57.120> the<00:08:57.279> next<00:08:57.920> six<00:08:58.160> and 00:08:58.230 --> 00:08:58.240 align:start position:0% simple quill sketch in the next six and 00:08:58.240 --> 00:09:00.150 align:start position:0% simple quill sketch in the next six and a<00:08:58.320> half<00:08:58.560> minutes<00:08:58.880> or<00:08:58.959> so<00:08:59.440> what<00:08:59.600> the<00:08:59.760> sketch<00:09:00.080> is 00:09:00.150 --> 00:09:00.160 align:start position:0% a half minutes or so what the sketch is 00:09:00.160 --> 00:09:01.750 align:start position:0% a half minutes or so what the sketch is going<00:09:00.399> to<00:09:00.480> do<00:09:00.800> is<00:09:00.959> uh<00:09:01.200> it's<00:09:01.440> going<00:09:01.519> to 00:09:01.750 --> 00:09:01.760 align:start position:0% going to do is uh it's going to 00:09:01.760 --> 00:09:04.470 align:start position:0% going to do is uh it's going to implement<00:09:02.160> a<00:09:02.800> common<00:09:03.120> visual<00:09:03.440> trope<00:09:03.760> among 00:09:04.470 --> 00:09:04.480 align:start position:0% implement a common visual trope among 00:09:04.480 --> 00:09:06.230 align:start position:0% implement a common visual trope among hollywood<00:09:04.959> guise<00:09:05.440> and<00:09:05.600> games<00:09:05.920> and<00:09:06.080> other 00:09:06.230 --> 00:09:06.240 align:start position:0% hollywood guise and games and other 00:09:06.240 --> 00:09:07.750 align:start position:0% hollywood guise and games and other flashy<00:09:06.640> interfaces<00:09:07.120> that<00:09:07.200> don't<00:09:07.360> really<00:09:07.519> do 00:09:07.750 --> 00:09:07.760 align:start position:0% flashy interfaces that don't really do 00:09:07.760 --> 00:09:09.670 align:start position:0% flashy interfaces that don't really do anything<00:09:08.560> where<00:09:08.800> you<00:09:08.880> have<00:09:09.040> a<00:09:09.120> lot<00:09:09.279> of 00:09:09.670 --> 00:09:09.680 align:start position:0% anything where you have a lot of 00:09:09.680 --> 00:09:11.910 align:start position:0% anything where you have a lot of spinning<00:09:10.160> circular<00:09:10.640> arc<00:09:10.880> segments<00:09:11.360> nested 00:09:11.910 --> 00:09:11.920 align:start position:0% spinning circular arc segments nested 00:09:11.920 --> 00:09:13.829 align:start position:0% spinning circular arc segments nested inside<00:09:12.320> one<00:09:12.480> or<00:09:12.560> the<00:09:12.640> other<00:09:13.360> so<00:09:13.519> let's<00:09:13.680> get 00:09:13.829 --> 00:09:13.839 align:start position:0% inside one or the other so let's get 00:09:13.839 --> 00:09:16.310 align:start position:0% inside one or the other so let's get started<00:09:14.640> i've<00:09:14.800> got<00:09:14.959> my<00:09:15.519> project<00:09:15.839> here<00:09:16.080> that<00:09:16.160> i 00:09:16.310 --> 00:09:16.320 align:start position:0% started i've got my project here that i 00:09:16.320 --> 00:09:18.870 align:start position:0% started i've got my project here that i just<00:09:16.560> recently<00:09:16.959> created<00:09:17.440> with<00:09:17.680> line<00:09:17.920> new 00:09:18.870 --> 00:09:18.880 align:start position:0% just recently created with line new 00:09:18.880 --> 00:09:20.310 align:start position:0% just recently created with line new the<00:09:18.959> only<00:09:19.200> thing<00:09:19.360> i've<00:09:19.519> added<00:09:19.760> to<00:09:19.839> the<00:09:20.000> project 00:09:20.310 --> 00:09:20.320 align:start position:0% the only thing i've added to the project 00:09:20.320 --> 00:09:22.550 align:start position:0% the only thing i've added to the project at<00:09:20.399> clj<00:09:21.040> is<00:09:21.200> the<00:09:21.440> quill<00:09:21.600> dependency<00:09:22.240> down<00:09:22.399> here 00:09:22.550 --> 00:09:22.560 align:start position:0% at clj is the quill dependency down here 00:09:22.560 --> 00:09:23.590 align:start position:0% at clj is the quill dependency down here at<00:09:22.640> the<00:09:22.720> bottom 00:09:23.590 --> 00:09:23.600 align:start position:0% at the bottom 00:09:23.600 --> 00:09:26.790 align:start position:0% at the bottom i've<00:09:23.839> pre-warmed<00:09:24.320> my<00:09:24.480> swank<00:09:24.800> server 00:09:26.790 --> 00:09:26.800 align:start position:0% i've pre-warmed my swank server 00:09:26.800 --> 00:09:28.230 align:start position:0% i've pre-warmed my swank server it<00:09:27.040> is 00:09:28.230 --> 00:09:28.240 align:start position:0% it is 00:09:28.240 --> 00:09:34.870 align:start position:0% it is oh<00:09:28.480> god 00:09:34.870 --> 00:09:34.880 align:start position:0% 00:09:34.880 --> 00:09:37.670 align:start position:0% uh<00:09:35.680> how<00:09:35.839> do<00:09:35.920> i<00:09:36.000> do<00:09:36.160> that<00:09:36.800> i<00:09:36.959> don't<00:09:37.200> know<00:09:37.360> how<00:09:37.519> to 00:09:37.670 --> 00:09:37.680 align:start position:0% uh how do i do that i don't know how to 00:09:37.680 --> 00:09:45.829 align:start position:0% uh how do i do that i don't know how to use<00:09:37.920> my<00:09:38.080> terminal 00:09:45.829 --> 00:09:45.839 align:start position:0% 00:09:45.839 --> 00:09:48.310 align:start position:0% okay 00:09:48.310 --> 00:09:48.320 align:start position:0% 00:09:48.320 --> 00:09:50.550 align:start position:0% that's<00:09:48.800> still<00:09:48.959> not<00:09:49.200> big<00:09:49.360> enough 00:09:50.550 --> 00:09:50.560 align:start position:0% that's still not big enough 00:09:50.560 --> 00:09:52.790 align:start position:0% that's still not big enough is<00:09:50.720> that<00:09:50.880> big<00:09:51.040> enough 00:09:52.790 --> 00:09:52.800 align:start position:0% is that big enough 00:09:52.800 --> 00:09:53.829 align:start position:0% is that big enough okay 00:09:53.829 --> 00:09:53.839 align:start position:0% okay 00:09:53.839 --> 00:09:55.430 align:start position:0% okay color<00:09:54.160> is<00:09:54.320> bad 00:09:55.430 --> 00:09:55.440 align:start position:0% color is bad 00:09:55.440 --> 00:09:59.590 align:start position:0% color is bad i<00:09:55.600> don't<00:09:55.839> know<00:09:56.000> how<00:09:56.160> to<00:09:56.240> change<00:09:56.480> the<00:09:56.640> color 00:09:59.590 --> 00:09:59.600 align:start position:0% 00:09:59.600 --> 00:10:01.590 align:start position:0% all<00:09:59.760> right<00:10:00.160> um<00:10:00.480> i<00:10:00.640> really<00:10:00.800> hope<00:10:01.040> you<00:10:01.120> can<00:10:01.279> see 00:10:01.590 --> 00:10:01.600 align:start position:0% all right um i really hope you can see 00:10:01.600 --> 00:10:03.269 align:start position:0% all right um i really hope you can see if<00:10:01.680> you<00:10:01.839> can't<00:10:02.240> i'm<00:10:02.399> very<00:10:02.640> sorry<00:10:02.959> you<00:10:03.120> should 00:10:03.269 --> 00:10:03.279 align:start position:0% if you can't i'm very sorry you should 00:10:03.279 --> 00:10:06.070 align:start position:0% if you can't i'm very sorry you should find<00:10:03.440> me<00:10:03.600> afterward<00:10:04.480> uh<00:10:04.720> so 00:10:06.070 --> 00:10:06.080 align:start position:0% find me afterward uh so 00:10:06.080 --> 00:10:07.350 align:start position:0% find me afterward uh so the<00:10:06.160> first<00:10:06.399> thing<00:10:06.640> i'm<00:10:06.720> going<00:10:06.880> to<00:10:06.959> do<00:10:07.200> is 00:10:07.350 --> 00:10:07.360 align:start position:0% the first thing i'm going to do is 00:10:07.360 --> 00:10:10.389 align:start position:0% the first thing i'm going to do is define<00:10:07.760> the<00:10:07.839> one<00:10:08.080> true<00:10:08.240> circle<00:10:08.560> constant<00:10:09.440> tau 00:10:10.389 --> 00:10:10.399 align:start position:0% define the one true circle constant tau 00:10:10.399 --> 00:10:12.150 align:start position:0% define the one true circle constant tau i<00:10:10.560> just<00:10:10.720> find<00:10:10.959> it<00:10:11.040> a<00:10:11.120> lot<00:10:11.279> easier<00:10:11.600> to<00:10:11.680> reason 00:10:12.150 --> 00:10:12.160 align:start position:0% i just find it a lot easier to reason 00:10:12.160 --> 00:10:13.910 align:start position:0% i just find it a lot easier to reason about<00:10:12.320> than<00:10:12.480> 2<00:10:12.720> pi 00:10:13.910 --> 00:10:13.920 align:start position:0% about than 2 pi 00:10:13.920 --> 00:10:15.750 align:start position:0% about than 2 pi so<00:10:14.560> the<00:10:14.800> first<00:10:15.040> question<00:10:15.360> we<00:10:15.519> probably<00:10:15.680> want 00:10:15.750 --> 00:10:15.760 align:start position:0% so the first question we probably want 00:10:15.760 --> 00:10:17.269 align:start position:0% so the first question we probably want to<00:10:15.839> ask<00:10:16.000> ourselves<00:10:16.399> is<00:10:16.640> conscientious 00:10:17.269 --> 00:10:17.279 align:start position:0% to ask ourselves is conscientious 00:10:17.279 --> 00:10:19.030 align:start position:0% to ask ourselves is conscientious clojurians<00:10:18.000> is<00:10:18.160> what<00:10:18.320> sort<00:10:18.480> of<00:10:18.560> data<00:10:18.880> we're 00:10:19.030 --> 00:10:19.040 align:start position:0% clojurians is what sort of data we're 00:10:19.040 --> 00:10:20.790 align:start position:0% clojurians is what sort of data we're going<00:10:19.200> to<00:10:19.360> need<00:10:20.079> we're<00:10:20.240> going<00:10:20.320> to<00:10:20.399> need<00:10:20.640> some 00:10:20.790 --> 00:10:20.800 align:start position:0% going to need we're going to need some 00:10:20.800 --> 00:10:23.430 align:start position:0% going to need we're going to need some way<00:10:21.200> of<00:10:21.920> describing<00:10:22.560> the<00:10:22.800> arcs<00:10:23.040> that<00:10:23.200> we<00:10:23.279> want 00:10:23.430 --> 00:10:23.440 align:start position:0% way of describing the arcs that we want 00:10:23.440 --> 00:10:25.910 align:start position:0% way of describing the arcs that we want to<00:10:23.519> draw<00:10:24.160> and<00:10:24.240> this<00:10:24.480> is<00:10:25.040> so<00:10:25.279> like<00:10:25.519> i<00:10:25.600> said<00:10:25.760> this 00:10:25.910 --> 00:10:25.920 align:start position:0% to draw and this is so like i said this 00:10:25.920 --> 00:10:27.430 align:start position:0% to draw and this is so like i said this is<00:10:26.000> not<00:10:26.160> going<00:10:26.240> to<00:10:26.320> be<00:10:26.560> idiomatic<00:10:27.120> closure 00:10:27.430 --> 00:10:27.440 align:start position:0% is not going to be idiomatic closure 00:10:27.440 --> 00:10:29.190 align:start position:0% is not going to be idiomatic closure code<00:10:28.000> because<00:10:28.160> we're<00:10:28.240> initiating<00:10:28.720> processing 00:10:29.190 --> 00:10:29.200 align:start position:0% code because we're initiating processing 00:10:29.200 --> 00:10:30.870 align:start position:0% code because we're initiating processing underneath<00:10:29.920> so<00:10:30.079> we're<00:10:30.160> going<00:10:30.240> to<00:10:30.320> need<00:10:30.480> a 00:10:30.870 --> 00:10:30.880 align:start position:0% underneath so we're going to need a 00:10:30.880 --> 00:10:32.550 align:start position:0% underneath so we're going to need a place<00:10:31.120> to<00:10:31.279> put<00:10:31.440> this<00:10:31.680> that<00:10:31.839> the<00:10:32.000> draw<00:10:32.160> loop<00:10:32.399> can 00:10:32.550 --> 00:10:32.560 align:start position:0% place to put this that the draw loop can 00:10:32.560 --> 00:10:34.230 align:start position:0% place to put this that the draw loop can find<00:10:32.800> because<00:10:32.959> the<00:10:33.040> draw<00:10:33.279> loop<00:10:33.839> can't<00:10:34.079> take 00:10:34.230 --> 00:10:34.240 align:start position:0% find because the draw loop can't take 00:10:34.240 --> 00:10:36.150 align:start position:0% find because the draw loop can't take any<00:10:34.480> arguments<00:10:35.200> so<00:10:35.360> i'm<00:10:35.440> going<00:10:35.519> to<00:10:35.600> define<00:10:35.920> an 00:10:36.150 --> 00:10:36.160 align:start position:0% any arguments so i'm going to define an 00:10:36.160 --> 00:10:37.910 align:start position:0% any arguments so i'm going to define an atom<00:10:36.399> called<00:10:36.720> arcs<00:10:37.120> and<00:10:37.279> it<00:10:37.360> just<00:10:37.519> contains 00:10:37.910 --> 00:10:37.920 align:start position:0% atom called arcs and it just contains 00:10:37.920 --> 00:10:40.470 align:start position:0% atom called arcs and it just contains the<00:10:38.079> empty<00:10:38.320> vector<00:10:38.640> for<00:10:38.800> now 00:10:40.470 --> 00:10:40.480 align:start position:0% the empty vector for now 00:10:40.480 --> 00:10:43.430 align:start position:0% the empty vector for now and<00:10:40.560> so<00:10:40.720> now<00:10:40.959> i<00:10:41.120> need<00:10:41.279> a<00:10:41.360> way<00:10:41.760> of<00:10:42.320> making<00:10:43.120> one<00:10:43.279> of 00:10:43.430 --> 00:10:43.440 align:start position:0% and so now i need a way of making one of 00:10:43.440 --> 00:10:44.870 align:start position:0% and so now i need a way of making one of my<00:10:43.600> arc<00:10:43.920> objects 00:10:44.870 --> 00:10:44.880 align:start position:0% my arc objects 00:10:44.880 --> 00:10:46.389 align:start position:0% my arc objects so<00:10:45.120> i'm<00:10:45.200> going<00:10:45.279> to<00:10:45.360> define<00:10:45.680> a<00:10:45.760> function<00:10:46.079> to<00:10:46.240> do 00:10:46.389 --> 00:10:46.399 align:start position:0% so i'm going to define a function to do 00:10:46.399 --> 00:10:48.710 align:start position:0% so i'm going to define a function to do that<00:10:46.800> it<00:10:46.959> takes<00:10:47.519> one<00:10:47.760> argument<00:10:48.160> which<00:10:48.399> is<00:10:48.480> the 00:10:48.710 --> 00:10:48.720 align:start position:0% that it takes one argument which is the 00:10:48.720 --> 00:10:50.949 align:start position:0% that it takes one argument which is the index<00:10:49.360> this<00:10:49.600> is<00:10:49.839> the<00:10:50.000> way<00:10:50.160> that<00:10:50.320> it'll<00:10:50.720> be<00:10:50.880> able 00:10:50.949 --> 00:10:50.959 align:start position:0% index this is the way that it'll be able 00:10:50.959 --> 00:10:55.910 align:start position:0% index this is the way that it'll be able to<00:10:51.120> set<00:10:51.360> a<00:10:51.440> different<00:10:51.680> radius<00:10:52.160> for<00:10:52.320> each<00:10:52.640> arc 00:10:55.910 --> 00:10:55.920 align:start position:0% 00:10:55.920 --> 00:10:58.069 align:start position:0% that's<00:10:56.240> not 00:10:58.069 --> 00:10:58.079 align:start position:0% that's not 00:10:58.079 --> 00:11:00.470 align:start position:0% that's not so<00:10:58.320> there<00:10:58.560> are<00:10:59.040> four<00:10:59.279> properties<00:10:59.760> to<00:10:59.920> each<00:11:00.160> arc 00:11:00.470 --> 00:11:00.480 align:start position:0% so there are four properties to each arc 00:11:00.480 --> 00:11:02.150 align:start position:0% so there are four properties to each arc it<00:11:00.560> has<00:11:00.800> a<00:11:01.040> position<00:11:01.519> on<00:11:01.600> the<00:11:01.680> unit<00:11:01.920> circle 00:11:02.150 --> 00:11:02.160 align:start position:0% it has a position on the unit circle 00:11:02.160 --> 00:11:04.150 align:start position:0% it has a position on the unit circle where<00:11:02.320> it<00:11:02.480> starts<00:11:03.040> it<00:11:03.200> has<00:11:03.360> an<00:11:03.519> angular<00:11:03.920> width 00:11:04.150 --> 00:11:04.160 align:start position:0% where it starts it has an angular width 00:11:04.160 --> 00:11:07.590 align:start position:0% where it starts it has an angular width that<00:11:04.399> it<00:11:04.480> spans<00:11:05.360> it<00:11:05.519> has<00:11:05.760> a<00:11:06.240> radius<00:11:06.959> and<00:11:07.360> some 00:11:07.590 --> 00:11:07.600 align:start position:0% that it spans it has a radius and some 00:11:07.600 --> 00:11:09.670 align:start position:0% that it spans it has a radius and some angular<00:11:08.000> velocity<00:11:08.880> uh<00:11:09.040> so<00:11:09.200> the<00:11:09.279> new<00:11:09.519> arc 00:11:09.670 --> 00:11:09.680 align:start position:0% angular velocity uh so the new arc 00:11:09.680 --> 00:11:11.269 align:start position:0% angular velocity uh so the new arc function<00:11:10.000> just<00:11:10.160> creates<00:11:10.480> a<00:11:10.560> map<00:11:10.880> with<00:11:11.040> all<00:11:11.200> of 00:11:11.269 --> 00:11:11.279 align:start position:0% function just creates a map with all of 00:11:11.279 --> 00:11:13.430 align:start position:0% function just creates a map with all of those<00:11:11.519> properties<00:11:12.160> um<00:11:12.560> and<00:11:12.800> fills<00:11:13.040> them<00:11:13.279> in 00:11:13.430 --> 00:11:13.440 align:start position:0% those properties um and fills them in 00:11:13.440 --> 00:11:14.550 align:start position:0% those properties um and fills them in with<00:11:13.600> some 00:11:14.550 --> 00:11:14.560 align:start position:0% with some 00:11:14.560 --> 00:11:16.630 align:start position:0% with some nice<00:11:14.800> looking<00:11:15.279> random<00:11:15.600> values<00:11:16.000> that<00:11:16.160> i<00:11:16.240> won't 00:11:16.630 --> 00:11:16.640 align:start position:0% nice looking random values that i won't 00:11:16.640 --> 00:11:17.910 align:start position:0% nice looking random values that i won't explain 00:11:17.910 --> 00:11:17.920 align:start position:0% explain 00:11:17.920 --> 00:11:20.069 align:start position:0% explain so<00:11:18.079> there<00:11:18.399> are<00:11:18.560> two<00:11:18.800> fundamental<00:11:19.360> functions 00:11:20.069 --> 00:11:20.079 align:start position:0% so there are two fundamental functions 00:11:20.079 --> 00:11:21.590 align:start position:0% so there are two fundamental functions to<00:11:20.160> every<00:11:20.399> coil<00:11:20.560> sketch 00:11:21.590 --> 00:11:21.600 align:start position:0% to every coil sketch 00:11:21.600 --> 00:11:23.910 align:start position:0% to every coil sketch the<00:11:21.760> first<00:11:22.000> one<00:11:22.240> is<00:11:22.399> called<00:11:22.720> setup<00:11:23.519> it's<00:11:23.680> run 00:11:23.910 --> 00:11:23.920 align:start position:0% the first one is called setup it's run 00:11:23.920 --> 00:11:25.590 align:start position:0% the first one is called setup it's run once<00:11:24.240> at<00:11:24.320> the<00:11:24.480> beginning<00:11:24.800> of<00:11:24.880> your<00:11:25.040> sketch<00:11:25.440> and 00:11:25.590 --> 00:11:25.600 align:start position:0% once at the beginning of your sketch and 00:11:25.600 --> 00:11:27.190 align:start position:0% once at the beginning of your sketch and it's<00:11:25.760> a<00:11:25.839> good<00:11:26.000> place<00:11:26.160> to<00:11:26.320> set<00:11:26.560> up<00:11:26.720> any<00:11:26.880> initial 00:11:27.190 --> 00:11:27.200 align:start position:0% it's a good place to set up any initial 00:11:27.200 --> 00:11:29.030 align:start position:0% it's a good place to set up any initial state<00:11:27.600> or<00:11:27.839> configure<00:11:28.320> things<00:11:28.560> that<00:11:28.720> will<00:11:28.880> be 00:11:29.030 --> 00:11:29.040 align:start position:0% state or configure things that will be 00:11:29.040 --> 00:11:30.389 align:start position:0% state or configure things that will be constant<00:11:29.360> throughout<00:11:29.760> the<00:11:29.920> entirety<00:11:30.240> of<00:11:30.320> your 00:11:30.389 --> 00:11:30.399 align:start position:0% constant throughout the entirety of your 00:11:30.399 --> 00:11:31.430 align:start position:0% constant throughout the entirety of your sketch 00:11:31.430 --> 00:11:31.440 align:start position:0% sketch 00:11:31.440 --> 00:11:33.110 align:start position:0% sketch and<00:11:31.600> the<00:11:31.680> other<00:11:31.839> one<00:11:32.160> is<00:11:32.240> called<00:11:32.480> draw<00:11:32.959> and 00:11:33.110 --> 00:11:33.120 align:start position:0% and the other one is called draw and 00:11:33.120 --> 00:11:34.790 align:start position:0% and the other one is called draw and this<00:11:33.360> is<00:11:33.440> your<00:11:33.600> main<00:11:33.760> loop<00:11:34.160> um<00:11:34.320> this<00:11:34.560> is<00:11:34.640> what 00:11:34.790 --> 00:11:34.800 align:start position:0% this is your main loop um this is what 00:11:34.800 --> 00:11:36.550 align:start position:0% this is your main loop um this is what actually<00:11:35.120> draws<00:11:35.360> stuff<00:11:35.600> to<00:11:35.680> the<00:11:35.839> screen<00:11:36.399> it's 00:11:36.550 --> 00:11:36.560 align:start position:0% actually draws stuff to the screen it's 00:11:36.560 --> 00:11:39.750 align:start position:0% actually draws stuff to the screen it's called<00:11:36.800> by<00:11:36.959> default<00:11:37.440> 60<00:11:37.760> times<00:11:38.000> a<00:11:38.079> second 00:11:39.750 --> 00:11:39.760 align:start position:0% called by default 60 times a second 00:11:39.760 --> 00:11:40.870 align:start position:0% called by default 60 times a second so<00:11:40.000> let's 00:11:40.870 --> 00:11:40.880 align:start position:0% so let's 00:11:40.880 --> 00:11:42.550 align:start position:0% so let's fill<00:11:41.120> in 00:11:42.550 --> 00:11:42.560 align:start position:0% fill in 00:11:42.560 --> 00:11:44.550 align:start position:0% fill in setup<00:11:43.440> there's<00:11:43.600> not<00:11:43.760> much<00:11:43.920> happening<00:11:44.320> here 00:11:44.550 --> 00:11:44.560 align:start position:0% setup there's not much happening here 00:11:44.560 --> 00:11:46.150 align:start position:0% setup there's not much happening here the<00:11:44.800> only<00:11:44.959> configuration<00:11:45.600> we<00:11:45.680> do<00:11:45.839> is<00:11:45.920> call 00:11:46.150 --> 00:11:46.160 align:start position:0% the only configuration we do is call 00:11:46.160 --> 00:11:48.069 align:start position:0% the only configuration we do is call smooth<00:11:46.560> to<00:11:46.640> turn<00:11:46.880> on<00:11:47.040> anti-aliasing<00:11:47.839> make 00:11:48.069 --> 00:11:48.079 align:start position:0% smooth to turn on anti-aliasing make 00:11:48.079 --> 00:11:49.670 align:start position:0% smooth to turn on anti-aliasing make everything<00:11:48.320> nice<00:11:48.560> and<00:11:48.720> pretty 00:11:49.670 --> 00:11:49.680 align:start position:0% everything nice and pretty 00:11:49.680 --> 00:11:51.750 align:start position:0% everything nice and pretty uh<00:11:50.079> and<00:11:50.240> then 00:11:51.750 --> 00:11:51.760 align:start position:0% uh and then 00:11:51.760 --> 00:11:54.389 align:start position:0% uh and then 15<00:11:52.160> times<00:11:52.560> over<00:11:52.959> we're<00:11:53.120> just<00:11:53.360> going<00:11:53.680> to 00:11:54.389 --> 00:11:54.399 align:start position:0% 15 times over we're just going to 00:11:54.399 --> 00:11:57.030 align:start position:0% 15 times over we're just going to make<00:11:54.640> a<00:11:54.720> new<00:11:54.959> art<00:11:55.440> arc<00:11:55.839> and<00:11:56.079> swap<00:11:56.399> it<00:11:56.560> into<00:11:56.880> the 00:11:57.030 --> 00:11:57.040 align:start position:0% make a new art arc and swap it into the 00:11:57.040 --> 00:12:01.590 align:start position:0% make a new art arc and swap it into the end<00:11:57.440> of<00:11:57.600> the<00:11:58.000> arcs<00:11:58.320> atom 00:12:01.590 --> 00:12:01.600 align:start position:0% 00:12:01.600 --> 00:12:03.190 align:start position:0% so<00:12:01.760> now<00:12:01.920> we're<00:12:02.079> ready<00:12:02.240> to<00:12:02.399> get<00:12:02.720> going<00:12:03.040> to<00:12:03.120> the 00:12:03.190 --> 00:12:03.200 align:start position:0% so now we're ready to get going to the 00:12:03.200 --> 00:12:04.550 align:start position:0% so now we're ready to get going to the draw<00:12:03.440> function 00:12:04.550 --> 00:12:04.560 align:start position:0% draw function 00:12:04.560 --> 00:12:06.389 align:start position:0% draw function there's<00:12:05.040> a<00:12:05.120> few<00:12:05.279> lines<00:12:05.600> happening<00:12:06.160> a<00:12:06.240> few 00:12:06.389 --> 00:12:06.399 align:start position:0% there's a few lines happening a few 00:12:06.399 --> 00:12:08.470 align:start position:0% there's a few lines happening a few lines<00:12:06.720> here<00:12:06.880> but<00:12:07.200> only<00:12:07.680> really<00:12:08.000> two<00:12:08.160> basic 00:12:08.470 --> 00:12:08.480 align:start position:0% lines here but only really two basic 00:12:08.480 --> 00:12:10.550 align:start position:0% lines here but only really two basic things<00:12:08.800> going<00:12:09.040> on<00:12:09.680> this<00:12:09.920> block<00:12:10.160> here<00:12:10.399> just 00:12:10.550 --> 00:12:10.560 align:start position:0% things going on this block here just 00:12:10.560 --> 00:12:12.470 align:start position:0% things going on this block here just sets<00:12:10.800> up<00:12:10.959> some<00:12:11.120> visual<00:12:11.440> properties<00:12:12.160> of<00:12:12.320> the 00:12:12.470 --> 00:12:12.480 align:start position:0% sets up some visual properties of the 00:12:12.480 --> 00:12:13.829 align:start position:0% sets up some visual properties of the sketch<00:12:13.040> we're<00:12:13.200> going<00:12:13.279> to<00:12:13.360> draw<00:12:13.519> a<00:12:13.600> black 00:12:13.829 --> 00:12:13.839 align:start position:0% sketch we're going to draw a black 00:12:13.839 --> 00:12:15.430 align:start position:0% sketch we're going to draw a black background<00:12:14.320> every<00:12:14.560> frame 00:12:15.430 --> 00:12:15.440 align:start position:0% background every frame 00:12:15.440 --> 00:12:16.870 align:start position:0% background every frame we're<00:12:15.600> going<00:12:15.680> to<00:12:15.760> turn<00:12:16.000> off<00:12:16.320> filling<00:12:16.720> in 00:12:16.870 --> 00:12:16.880 align:start position:0% we're going to turn off filling in 00:12:16.880 --> 00:12:18.310 align:start position:0% we're going to turn off filling in objects<00:12:17.200> so<00:12:17.360> we<00:12:17.440> just<00:12:17.600> get<00:12:17.760> the<00:12:17.920> borders<00:12:18.240> of 00:12:18.310 --> 00:12:18.320 align:start position:0% objects so we just get the borders of 00:12:18.320 --> 00:12:20.629 align:start position:0% objects so we just get the borders of the<00:12:18.480> arcs<00:12:18.720> rather<00:12:18.959> than<00:12:19.120> the<00:12:19.200> full<00:12:19.440> pie<00:12:19.600> slice 00:12:20.629 --> 00:12:20.639 align:start position:0% the arcs rather than the full pie slice 00:12:20.639 --> 00:12:22.310 align:start position:0% the arcs rather than the full pie slice we're<00:12:20.800> going<00:12:20.880> to<00:12:20.959> make<00:12:21.200> them<00:12:21.680> pure<00:12:22.000> white 00:12:22.310 --> 00:12:22.320 align:start position:0% we're going to make them pure white 00:12:22.320 --> 00:12:24.629 align:start position:0% we're going to make them pure white stroke<00:12:22.880> make<00:12:23.120> them<00:12:23.519> 10<00:12:23.760> pixels<00:12:24.160> wide<00:12:24.399> and<00:12:24.480> give 00:12:24.629 --> 00:12:24.639 align:start position:0% stroke make them 10 pixels wide and give 00:12:24.639 --> 00:12:26.069 align:start position:0% stroke make them 10 pixels wide and give them<00:12:24.800> square<00:12:25.120> caps 00:12:26.069 --> 00:12:26.079 align:start position:0% them square caps 00:12:26.079 --> 00:12:28.470 align:start position:0% them square caps and<00:12:26.240> so<00:12:26.399> after<00:12:26.720> we<00:12:27.279> finish<00:12:27.680> doing<00:12:27.839> that<00:12:28.079> we<00:12:28.240> can 00:12:28.470 --> 00:12:28.480 align:start position:0% and so after we finish doing that we can 00:12:28.480 --> 00:12:30.629 align:start position:0% and so after we finish doing that we can move<00:12:28.720> on<00:12:28.800> to<00:12:28.880> actually<00:12:29.120> drawing<00:12:29.440> them 00:12:30.629 --> 00:12:30.639 align:start position:0% move on to actually drawing them 00:12:30.639 --> 00:12:31.670 align:start position:0% move on to actually drawing them so<00:12:30.880> we 00:12:31.670 --> 00:12:31.680 align:start position:0% so we 00:12:31.680 --> 00:12:34.230 align:start position:0% so we first<00:12:32.399> by<00:12:32.560> default<00:12:32.959> the<00:12:33.120> origin<00:12:33.680> is<00:12:33.839> in<00:12:33.920> the 00:12:34.230 --> 00:12:34.240 align:start position:0% first by default the origin is in the 00:12:34.240 --> 00:12:36.230 align:start position:0% first by default the origin is in the top<00:12:34.560> left<00:12:35.040> as<00:12:35.200> you<00:12:35.519> probably<00:12:35.839> expect<00:12:36.160> if 00:12:36.230 --> 00:12:36.240 align:start position:0% top left as you probably expect if 00:12:36.240 --> 00:12:37.190 align:start position:0% top left as you probably expect if you're<00:12:36.399> familiar<00:12:36.720> with<00:12:36.800> graphics 00:12:37.190 --> 00:12:37.200 align:start position:0% you're familiar with graphics 00:12:37.200 --> 00:12:38.790 align:start position:0% you're familiar with graphics programming<00:12:37.920> and<00:12:38.079> we're<00:12:38.240> just<00:12:38.399> going<00:12:38.560> to<00:12:38.639> move 00:12:38.790 --> 00:12:38.800 align:start position:0% programming and we're just going to move 00:12:38.800 --> 00:12:41.269 align:start position:0% programming and we're just going to move that<00:12:38.959> down<00:12:39.120> to<00:12:39.279> the<00:12:39.360> middle<00:12:39.680> with<00:12:39.920> a<00:12:40.160> translate 00:12:41.269 --> 00:12:41.279 align:start position:0% that down to the middle with a translate 00:12:41.279 --> 00:12:43.110 align:start position:0% that down to the middle with a translate the<00:12:41.519> translation<00:12:42.000> matrix<00:12:42.399> is<00:12:42.480> reset<00:12:42.880> every 00:12:43.110 --> 00:12:43.120 align:start position:0% the translation matrix is reset every 00:12:43.120 --> 00:12:44.310 align:start position:0% the translation matrix is reset every frame<00:12:43.279> so<00:12:43.440> we're<00:12:43.519> not<00:12:43.920> we<00:12:44.000> don't<00:12:44.160> have<00:12:44.240> to 00:12:44.310 --> 00:12:44.320 align:start position:0% frame so we're not we don't have to 00:12:44.320 --> 00:12:45.750 align:start position:0% frame so we're not we don't have to worry<00:12:44.560> about<00:12:44.800> scooting<00:12:45.200> off<00:12:45.360> to<00:12:45.440> the<00:12:45.519> bottom 00:12:45.750 --> 00:12:45.760 align:start position:0% worry about scooting off to the bottom 00:12:45.760 --> 00:12:47.269 align:start position:0% worry about scooting off to the bottom right<00:12:46.000> of<00:12:46.079> the<00:12:46.160> frame 00:12:47.269 --> 00:12:47.279 align:start position:0% right of the frame 00:12:47.279 --> 00:12:49.269 align:start position:0% right of the frame and<00:12:47.360> then<00:12:47.519> we<00:12:47.680> just<00:12:48.079> iterate<00:12:48.560> over<00:12:48.880> all<00:12:49.040> of<00:12:49.200> our 00:12:49.269 --> 00:12:49.279 align:start position:0% and then we just iterate over all of our 00:12:49.279 --> 00:12:53.350 align:start position:0% and then we just iterate over all of our arcmaps<00:12:50.079> for<00:12:50.240> side<00:12:50.480> effects 00:12:53.350 --> 00:12:53.360 align:start position:0% arcmaps for side effects 00:12:53.360 --> 00:12:55.990 align:start position:0% arcmaps for side effects we<00:12:53.600> pull<00:12:53.839> out<00:12:54.000> the<00:12:54.240> position<00:12:55.040> within<00:12:55.440> radius 00:12:55.990 --> 00:12:56.000 align:start position:0% we pull out the position within radius 00:12:56.000 --> 00:12:57.110 align:start position:0% we pull out the position within radius properties 00:12:57.110 --> 00:12:57.120 align:start position:0% properties 00:12:57.120 --> 00:12:58.949 align:start position:0% properties and<00:12:57.279> then<00:12:57.440> we<00:12:57.680> can<00:12:57.839> just<00:12:58.079> use<00:12:58.320> quill's<00:12:58.720> arc 00:12:58.949 --> 00:12:58.959 align:start position:0% and then we can just use quill's arc 00:12:58.959 --> 00:13:00.710 align:start position:0% and then we can just use quill's arc function<00:12:59.279> to<00:12:59.440> actually<00:12:59.600> do<00:12:59.760> the<00:12:59.920> drawing<00:13:00.560> it 00:13:00.710 --> 00:13:00.720 align:start position:0% function to actually do the drawing it 00:13:00.720 --> 00:13:03.030 align:start position:0% function to actually do the drawing it takes<00:13:01.360> six<00:13:01.600> arguments<00:13:02.160> the<00:13:02.240> first<00:13:02.560> two<00:13:02.880> are 00:13:03.030 --> 00:13:03.040 align:start position:0% takes six arguments the first two are 00:13:03.040 --> 00:13:05.190 align:start position:0% takes six arguments the first two are the<00:13:03.519> x<00:13:03.760> and<00:13:03.839> y<00:13:04.079> positions<00:13:04.480> of<00:13:04.560> the<00:13:04.720> center<00:13:05.120> of 00:13:05.190 --> 00:13:05.200 align:start position:0% the x and y positions of the center of 00:13:05.200 --> 00:13:06.389 align:start position:0% the x and y positions of the center of the<00:13:05.360> arcs 00:13:06.389 --> 00:13:06.399 align:start position:0% the arcs 00:13:06.399 --> 00:13:07.430 align:start position:0% the arcs ellipse 00:13:07.430 --> 00:13:07.440 align:start position:0% ellipse 00:13:07.440 --> 00:13:09.430 align:start position:0% ellipse the<00:13:07.680> next<00:13:07.920> two<00:13:08.240> are<00:13:08.399> the<00:13:08.720> semi-major<00:13:09.360> and 00:13:09.430 --> 00:13:09.440 align:start position:0% the next two are the semi-major and 00:13:09.440 --> 00:13:12.150 align:start position:0% the next two are the semi-major and semi-minor<00:13:10.160> axis<00:13:10.800> lengths<00:13:11.519> and<00:13:11.680> we<00:13:11.920> want 00:13:12.150 --> 00:13:12.160 align:start position:0% semi-minor axis lengths and we want 00:13:12.160 --> 00:13:13.269 align:start position:0% semi-minor axis lengths and we want circular<00:13:12.560> arcs<00:13:12.800> so<00:13:12.880> we're<00:13:12.959> just<00:13:13.120> going<00:13:13.200> to 00:13:13.269 --> 00:13:13.279 align:start position:0% circular arcs so we're just going to 00:13:13.279 --> 00:13:14.949 align:start position:0% circular arcs so we're just going to give<00:13:13.360> it<00:13:13.440> the<00:13:13.519> radius<00:13:13.839> for<00:13:13.920> both<00:13:14.160> of<00:13:14.240> those<00:13:14.880> and 00:13:14.949 --> 00:13:14.959 align:start position:0% give it the radius for both of those and 00:13:14.959 --> 00:13:16.389 align:start position:0% give it the radius for both of those and then<00:13:15.120> the<00:13:15.200> last<00:13:15.519> two<00:13:15.839> are<00:13:15.920> the<00:13:16.000> angular 00:13:16.389 --> 00:13:16.399 align:start position:0% then the last two are the angular 00:13:16.399 --> 00:13:18.710 align:start position:0% then the last two are the angular positions<00:13:16.880> to<00:13:17.040> start<00:13:17.360> and<00:13:17.519> stop<00:13:18.000> drawing<00:13:18.560> the 00:13:18.710 --> 00:13:18.720 align:start position:0% positions to start and stop drawing the 00:13:18.720 --> 00:13:20.310 align:start position:0% positions to start and stop drawing the arc<00:13:19.360> so<00:13:19.519> we're<00:13:19.680> going<00:13:19.760> to<00:13:19.839> start<00:13:20.079> at<00:13:20.160> the 00:13:20.310 --> 00:13:20.320 align:start position:0% arc so we're going to start at the 00:13:20.320 --> 00:13:21.990 align:start position:0% arc so we're going to start at the position<00:13:20.800> and<00:13:20.959> stop<00:13:21.279> at<00:13:21.360> the<00:13:21.440> sum<00:13:21.760> of<00:13:21.920> the 00:13:21.990 --> 00:13:22.000 align:start position:0% position and stop at the sum of the 00:13:22.000 --> 00:13:24.790 align:start position:0% position and stop at the sum of the position<00:13:22.560> and<00:13:22.720> the<00:13:22.800> width 00:13:24.790 --> 00:13:24.800 align:start position:0% position and the width 00:13:24.800 --> 00:13:26.949 align:start position:0% position and the width so<00:13:24.959> now<00:13:25.120> we<00:13:25.279> have<00:13:25.680> all<00:13:25.760> the<00:13:25.920> functions<00:13:26.399> we<00:13:26.560> need 00:13:26.949 --> 00:13:26.959 align:start position:0% so now we have all the functions we need 00:13:26.959 --> 00:13:28.870 align:start position:0% so now we have all the functions we need uh<00:13:27.200> the<00:13:27.279> last<00:13:27.519> thing<00:13:27.680> we<00:13:27.839> need<00:13:28.000> to<00:13:28.079> do<00:13:28.560> is 00:13:28.870 --> 00:13:28.880 align:start position:0% uh the last thing we need to do is 00:13:28.880 --> 00:13:30.710 align:start position:0% uh the last thing we need to do is actually<00:13:29.120> define<00:13:29.519> a<00:13:29.680> sketch<00:13:30.000> and<00:13:30.079> kick<00:13:30.320> it<00:13:30.480> off 00:13:30.710 --> 00:13:30.720 align:start position:0% actually define a sketch and kick it off 00:13:30.720 --> 00:13:32.310 align:start position:0% actually define a sketch and kick it off and<00:13:30.800> we<00:13:30.959> do<00:13:31.120> that<00:13:31.360> with<00:13:31.600> the 00:13:32.310 --> 00:13:32.320 align:start position:0% and we do that with the 00:13:32.320 --> 00:13:34.949 align:start position:0% and we do that with the death<00:13:32.560> sketch<00:13:32.880> macro<00:13:34.240> so<00:13:34.399> there<00:13:34.560> are<00:13:34.639> three 00:13:34.949 --> 00:13:34.959 align:start position:0% death sketch macro so there are three 00:13:34.959 --> 00:13:36.550 align:start position:0% death sketch macro so there are three important<00:13:35.360> keyword<00:13:35.839> arguments<00:13:36.240> to<00:13:36.320> this 00:13:36.550 --> 00:13:36.560 align:start position:0% important keyword arguments to this 00:13:36.560 --> 00:13:39.190 align:start position:0% important keyword arguments to this macro<00:13:37.360> the<00:13:37.519> first<00:13:37.920> is<00:13:38.320> the<00:13:38.560> size<00:13:38.880> which<00:13:39.120> is 00:13:39.190 --> 00:13:39.200 align:start position:0% macro the first is the size which is 00:13:39.200 --> 00:13:41.030 align:start position:0% macro the first is the size which is just<00:13:39.360> a<00:13:39.440> two<00:13:39.680> vector<00:13:40.160> defining<00:13:40.560> the<00:13:40.720> width<00:13:40.959> and 00:13:41.030 --> 00:13:41.040 align:start position:0% just a two vector defining the width and 00:13:41.040 --> 00:13:43.990 align:start position:0% just a two vector defining the width and the<00:13:41.120> height<00:13:41.440> of<00:13:41.600> the<00:13:41.920> sketches<00:13:42.639> window 00:13:43.990 --> 00:13:44.000 align:start position:0% the height of the sketches window 00:13:44.000 --> 00:13:45.190 align:start position:0% the height of the sketches window and<00:13:44.079> then<00:13:44.240> it<00:13:44.320> needs<00:13:44.480> to<00:13:44.639> know<00:13:44.720> the<00:13:44.880> names<00:13:45.040> of 00:13:45.190 --> 00:13:45.200 align:start position:0% and then it needs to know the names of 00:13:45.200 --> 00:13:47.030 align:start position:0% and then it needs to know the names of our<00:13:45.440> setup<00:13:45.760> and<00:13:45.920> draw<00:13:46.160> functions<00:13:46.720> which<00:13:46.959> in 00:13:47.030 --> 00:13:47.040 align:start position:0% our setup and draw functions which in 00:13:47.040 --> 00:13:49.670 align:start position:0% our setup and draw functions which in this<00:13:47.200> case<00:13:48.000> are<00:13:48.079> just<00:13:48.320> set<00:13:48.480> up<00:13:48.639> and<00:13:48.720> draw 00:13:49.670 --> 00:13:49.680 align:start position:0% this case are just set up and draw 00:13:49.680 --> 00:13:51.430 align:start position:0% this case are just set up and draw so 00:13:51.430 --> 00:13:51.440 align:start position:0% so 00:13:51.440 --> 00:13:53.990 align:start position:0% so let<00:13:51.600> me<00:13:51.760> open<00:13:52.000> up 00:13:53.990 --> 00:13:54.000 align:start position:0% let me open up 00:13:54.000 --> 00:13:59.030 align:start position:0% let me open up oh<00:13:54.240> crap 00:13:59.030 --> 00:13:59.040 align:start position:0% 00:13:59.040 --> 00:14:01.590 align:start position:0% so<00:13:59.519> here's<00:13:59.760> a<00:13:59.839> very<00:14:00.079> cramped<00:14:00.320> repo 00:14:01.590 --> 00:14:01.600 align:start position:0% so here's a very cramped repo 00:14:01.600 --> 00:14:03.910 align:start position:0% so here's a very cramped repo let's<00:14:01.920> evaluate<00:14:02.480> everything<00:14:03.279> and<00:14:03.680> now<00:14:03.839> we 00:14:03.910 --> 00:14:03.920 align:start position:0% let's evaluate everything and now we 00:14:03.920 --> 00:14:05.189 align:start position:0% let's evaluate everything and now we have<00:14:04.000> some<00:14:04.160> marks 00:14:05.189 --> 00:14:05.199 align:start position:0% have some marks 00:14:05.199 --> 00:14:08.389 align:start position:0% have some marks so<00:14:05.760> you<00:14:05.920> might<00:14:06.160> be<00:14:06.399> uh<00:14:07.040> asking<00:14:07.360> me<00:14:07.839> that<00:14:08.079> i<00:14:08.240> told 00:14:08.389 --> 00:14:08.399 align:start position:0% so you might be uh asking me that i told 00:14:08.399 --> 00:14:09.829 align:start position:0% so you might be uh asking me that i told you<00:14:08.560> the<00:14:08.720> arcs<00:14:08.959> would<00:14:09.040> be<00:14:09.120> spinning<00:14:09.600> and<00:14:09.680> they 00:14:09.829 --> 00:14:09.839 align:start position:0% you the arcs would be spinning and they 00:14:09.839 --> 00:14:15.430 align:start position:0% you the arcs would be spinning and they are<00:14:10.000> clearly<00:14:10.320> not<00:14:10.880> so<00:14:11.040> let's<00:14:11.279> fix<00:14:11.519> that 00:14:15.430 --> 00:14:15.440 align:start position:0% 00:14:15.440 --> 00:14:17.350 align:start position:0% i<00:14:15.600> have<00:14:15.760> a<00:14:15.839> habit<00:14:16.240> of<00:14:16.480> uh<00:14:16.800> where<00:14:16.959> i<00:14:17.040> like<00:14:17.199> to 00:14:17.350 --> 00:14:17.360 align:start position:0% i have a habit of uh where i like to 00:14:17.360 --> 00:14:19.189 align:start position:0% i have a habit of uh where i like to separate<00:14:17.920> out<00:14:18.240> the<00:14:18.480> part<00:14:18.720> of<00:14:18.800> my<00:14:18.959> draw 00:14:19.189 --> 00:14:19.199 align:start position:0% separate out the part of my draw 00:14:19.199 --> 00:14:20.870 align:start position:0% separate out the part of my draw function<00:14:19.519> that<00:14:19.680> actually<00:14:20.160> changes<00:14:20.560> the<00:14:20.639> state 00:14:20.870 --> 00:14:20.880 align:start position:0% function that actually changes the state 00:14:20.880 --> 00:14:22.150 align:start position:0% function that actually changes the state from<00:14:21.040> the<00:14:21.120> part<00:14:21.279> that<00:14:21.440> just<00:14:21.600> does<00:14:21.760> the<00:14:21.839> drawing 00:14:22.150 --> 00:14:22.160 align:start position:0% from the part that just does the drawing 00:14:22.160 --> 00:14:23.590 align:start position:0% from the part that just does the drawing and<00:14:22.240> i<00:14:22.399> like<00:14:22.560> to<00:14:22.639> put<00:14:22.800> that<00:14:22.959> in<00:14:23.040> a<00:14:23.120> function 00:14:23.590 --> 00:14:23.600 align:start position:0% and i like to put that in a function 00:14:23.600 --> 00:14:25.269 align:start position:0% and i like to put that in a function called<00:14:23.839> tick<00:14:24.079> bang 00:14:25.269 --> 00:14:25.279 align:start position:0% called tick bang 00:14:25.279 --> 00:14:26.389 align:start position:0% called tick bang so<00:14:25.440> this<00:14:25.680> is 00:14:26.389 --> 00:14:26.399 align:start position:0% so this is 00:14:26.399 --> 00:14:28.150 align:start position:0% so this is not<00:14:26.560> very<00:14:26.720> much<00:14:26.959> happening<00:14:27.360> here<00:14:27.760> we're<00:14:27.920> just 00:14:28.150 --> 00:14:28.160 align:start position:0% not very much happening here we're just 00:14:28.160 --> 00:14:31.430 align:start position:0% not very much happening here we're just gonna<00:14:28.800> loop<00:14:29.120> through<00:14:29.920> all<00:14:30.079> of<00:14:30.240> our<00:14:30.800> arcs<00:14:31.279> and 00:14:31.430 --> 00:14:31.440 align:start position:0% gonna loop through all of our arcs and 00:14:31.440 --> 00:14:34.230 align:start position:0% gonna loop through all of our arcs and pull<00:14:31.600> out<00:14:31.839> the<00:14:32.079> position<00:14:32.639> and<00:14:32.800> velocity<00:14:33.519> keys 00:14:34.230 --> 00:14:34.240 align:start position:0% pull out the position and velocity keys 00:14:34.240 --> 00:14:36.310 align:start position:0% pull out the position and velocity keys and<00:14:34.399> then<00:14:34.560> we<00:14:34.880> just<00:14:35.279> update<00:14:35.600> the<00:14:35.760> position<00:14:36.240> to 00:14:36.310 --> 00:14:36.320 align:start position:0% and then we just update the position to 00:14:36.320 --> 00:14:38.230 align:start position:0% and then we just update the position to be<00:14:36.480> the<00:14:36.639> sum<00:14:36.880> of<00:14:36.959> the<00:14:37.040> position<00:14:37.360> of<00:14:37.440> velocity 00:14:38.230 --> 00:14:38.240 align:start position:0% be the sum of the position of velocity 00:14:38.240 --> 00:14:39.670 align:start position:0% be the sum of the position of velocity and<00:14:38.320> then<00:14:38.560> once<00:14:38.800> we<00:14:38.880> have<00:14:39.040> the<00:14:39.120> shifted<00:14:39.519> arcs 00:14:39.670 --> 00:14:39.680 align:start position:0% and then once we have the shifted arcs 00:14:39.680 --> 00:14:41.269 align:start position:0% and then once we have the shifted arcs we<00:14:39.839> just<00:14:40.000> reset<00:14:40.320> the<00:14:40.399> atom<00:14:40.720> to<00:14:40.880> contain<00:14:41.199> the 00:14:41.269 --> 00:14:41.279 align:start position:0% we just reset the atom to contain the 00:14:41.279 --> 00:14:42.629 align:start position:0% we just reset the atom to contain the new<00:14:41.440> ones 00:14:42.629 --> 00:14:42.639 align:start position:0% new ones 00:14:42.639 --> 00:14:46.310 align:start position:0% new ones so<00:14:42.800> we<00:14:42.959> can<00:14:44.079> define<00:14:44.480> this<00:14:45.199> and<00:14:45.440> go<00:14:45.600> down<00:14:46.000> and 00:14:46.310 --> 00:14:46.320 align:start position:0% so we can define this and go down and 00:14:46.320 --> 00:14:48.069 align:start position:0% so we can define this and go down and call<00:14:46.560> tick<00:14:46.959> at<00:14:47.040> the<00:14:47.120> beginning<00:14:47.600> of<00:14:47.760> our<00:14:47.839> draw 00:14:48.069 --> 00:14:48.079 align:start position:0% call tick at the beginning of our draw 00:14:48.079 --> 00:14:50.790 align:start position:0% call tick at the beginning of our draw function<00:14:48.800> and<00:14:48.959> redefine<00:14:49.440> it<00:14:49.920> and<00:14:50.320> we<00:14:50.480> go<00:14:50.639> back 00:14:50.790 --> 00:14:50.800 align:start position:0% function and redefine it and we go back 00:14:50.800 --> 00:14:51.910 align:start position:0% function and redefine it and we go back and<00:14:50.880> you'll<00:14:51.040> notice<00:14:51.279> without<00:14:51.519> us<00:14:51.600> having<00:14:51.839> to 00:14:51.910 --> 00:14:51.920 align:start position:0% and you'll notice without us having to 00:14:51.920 --> 00:14:53.670 align:start position:0% and you'll notice without us having to do<00:14:52.079> anything<00:14:52.639> the<00:14:52.800> sketch<00:14:53.120> has<00:14:53.279> picked<00:14:53.519> up<00:14:53.600> on 00:14:53.670 --> 00:14:53.680 align:start position:0% do anything the sketch has picked up on 00:14:53.680 --> 00:14:55.670 align:start position:0% do anything the sketch has picked up on our<00:14:53.839> new<00:14:54.399> draw<00:14:54.639> function<00:14:55.040> and<00:14:55.199> now<00:14:55.360> the<00:14:55.440> arcs 00:14:55.670 --> 00:14:55.680 align:start position:0% our new draw function and now the arcs 00:14:55.680 --> 00:14:56.870 align:start position:0% our new draw function and now the arcs are<00:14:55.760> all<00:14:55.920> spinning 00:14:56.870 --> 00:14:56.880 align:start position:0% are all spinning 00:14:56.880 --> 00:14:58.150 align:start position:0% are all spinning this<00:14:57.120> is<00:14:57.199> really<00:14:57.360> cool<00:14:57.600> because<00:14:57.760> it<00:14:57.839> means<00:14:58.000> we 00:14:58.150 --> 00:14:58.160 align:start position:0% this is really cool because it means we 00:14:58.160 --> 00:14:59.910 align:start position:0% this is really cool because it means we can<00:14:58.240> do<00:14:58.399> a<00:14:58.399> lot<00:14:58.560> of<00:14:58.720> experimentation 00:14:59.910 --> 00:14:59.920 align:start position:0% can do a lot of experimentation 00:14:59.920 --> 00:15:02.150 align:start position:0% can do a lot of experimentation basically<00:15:00.480> instantaneously<00:15:01.519> so<00:15:01.760> let's<00:15:01.920> say 00:15:02.150 --> 00:15:02.160 align:start position:0% basically instantaneously so let's say 00:15:02.160 --> 00:15:06.150 align:start position:0% basically instantaneously so let's say we<00:15:02.240> wanted<00:15:02.560> to<00:15:02.639> make<00:15:02.800> the<00:15:02.959> arcs<00:15:03.680> thicker 00:15:06.150 --> 00:15:06.160 align:start position:0% 00:15:06.160 --> 00:15:07.590 align:start position:0% just<00:15:06.399> happens 00:15:07.590 --> 00:15:07.600 align:start position:0% just happens 00:15:07.600 --> 00:15:12.949 align:start position:0% just happens we<00:15:07.760> can<00:15:08.240> make<00:15:08.480> them<00:15:08.959> bright<00:15:09.279> pink 00:15:12.949 --> 00:15:12.959 align:start position:0% 00:15:12.959 --> 00:15:15.350 align:start position:0% oh<00:15:13.279> that's<00:15:13.519> redefined 00:15:15.350 --> 00:15:15.360 align:start position:0% oh that's redefined 00:15:15.360 --> 00:15:16.870 align:start position:0% oh that's redefined uh<00:15:15.680> and<00:15:15.760> so<00:15:15.920> this<00:15:16.079> is<00:15:16.240> really<00:15:16.480> great<00:15:16.639> because 00:15:16.870 --> 00:15:16.880 align:start position:0% uh and so this is really great because 00:15:16.880 --> 00:15:18.629 align:start position:0% uh and so this is really great because it<00:15:17.199> allows<00:15:17.440> you<00:15:17.600> to<00:15:17.760> do<00:15:18.320> lots<00:15:18.560> of 00:15:18.629 --> 00:15:18.639 align:start position:0% it allows you to do lots of 00:15:18.639 --> 00:15:20.790 align:start position:0% it allows you to do lots of experimentation<00:15:19.760> really<00:15:20.000> fast<00:15:20.480> which<00:15:20.720> is 00:15:20.790 --> 00:15:20.800 align:start position:0% experimentation really fast which is 00:15:20.800 --> 00:15:22.870 align:start position:0% experimentation really fast which is what<00:15:20.959> i<00:15:21.440> found<00:15:21.760> so 00:15:22.870 --> 00:15:22.880 align:start position:0% what i found so 00:15:22.880 --> 00:15:24.710 align:start position:0% what i found so seductive<00:15:23.440> about<00:15:23.680> programming<00:15:24.240> in<00:15:24.399> the<00:15:24.480> first 00:15:24.710 --> 00:15:24.720 align:start position:0% seductive about programming in the first 00:15:24.720 --> 00:15:27.110 align:start position:0% seductive about programming in the first place 00:15:27.110 --> 00:15:27.120 align:start position:0% 00:15:27.120 --> 00:15:29.030 align:start position:0% so<00:15:27.279> that<00:15:27.360> was<00:15:27.519> a<00:15:27.519> little<00:15:27.920> taste<00:15:28.160> of<00:15:28.320> quill<00:15:28.880> if 00:15:29.030 --> 00:15:29.040 align:start position:0% so that was a little taste of quill if 00:15:29.040 --> 00:15:30.949 align:start position:0% so that was a little taste of quill if you<00:15:29.120> want<00:15:29.279> to<00:15:29.760> talk<00:15:29.920> to<00:15:30.079> me<00:15:30.160> more<00:15:30.399> about 00:15:30.949 --> 00:15:30.959 align:start position:0% you want to talk to me more about 00:15:30.959 --> 00:15:33.670 align:start position:0% you want to talk to me more about creating<00:15:31.440> art<00:15:31.600> with<00:15:31.760> code<00:15:32.399> check<00:15:32.639> out<00:15:32.800> some<00:15:33.199> 3d 00:15:33.670 --> 00:15:33.680 align:start position:0% creating art with code check out some 3d 00:15:33.680 --> 00:15:35.670 align:start position:0% creating art with code check out some 3d printed<00:15:34.000> sculptures<00:15:34.480> i<00:15:34.560> made<00:15:34.720> with<00:15:34.959> quill 00:15:35.670 --> 00:15:35.680 align:start position:0% printed sculptures i made with quill 00:15:35.680 --> 00:15:37.590 align:start position:0% printed sculptures i made with quill find<00:15:35.839> me<00:15:36.000> around<00:15:36.240> later<00:15:36.880> and<00:15:37.279> thanks<00:15:37.440> for 00:15:37.590 --> 00:15:37.600 align:start position:0% find me around later and thanks for 00:15:37.600 --> 00:15:43.590 align:start position:0% find me around later and thanks for listening 00:15:43.590 --> 00:15:43.600 align:start position:0% 00:15:43.600 --> 00:15:45.750 align:start position:0% good<00:15:43.839> afternoon<00:15:44.480> my<00:15:44.639> name<00:15:44.720> is<00:15:44.880> hugh<00:15:45.120> goodman 00:15:45.750 --> 00:15:45.760 align:start position:0% good afternoon my name is hugh goodman 00:15:45.760 --> 00:15:48.230 align:start position:0% good afternoon my name is hugh goodman i've<00:15:46.560> worked<00:15:46.800> with<00:15:46.959> lisbenwyc<00:15:47.760> and<00:15:47.839> my<00:15:48.000> day 00:15:48.230 --> 00:15:48.240 align:start position:0% i've worked with lisbenwyc and my day 00:15:48.240 --> 00:15:50.470 align:start position:0% i've worked with lisbenwyc and my day job<00:15:48.480> is<00:15:48.560> at<00:15:48.720> brander<00:15:49.199> group<00:15:49.759> we're<00:15:50.000> an<00:15:50.079> amazon 00:15:50.470 --> 00:15:50.480 align:start position:0% job is at brander group we're an amazon 00:15:50.480 --> 00:15:52.629 align:start position:0% job is at brander group we're an amazon web<00:15:50.720> services<00:15:51.199> company<00:15:51.680> and<00:15:52.000> shockingly<00:15:52.560> we 00:15:52.629 --> 00:15:52.639 align:start position:0% web services company and shockingly we 00:15:52.639 --> 00:15:54.150 align:start position:0% web services company and shockingly we like<00:15:52.800> to<00:15:52.959> do<00:15:53.120> our<00:15:53.199> software<00:15:53.519> development<00:15:54.000> in 00:15:54.150 --> 00:15:54.160 align:start position:0% like to do our software development in 00:15:54.160 --> 00:15:56.310 align:start position:0% like to do our software development in lisp 00:15:56.310 --> 00:15:56.320 align:start position:0% lisp 00:15:56.320 --> 00:15:57.990 align:start position:0% lisp however<00:15:56.639> during<00:15:56.880> the<00:15:56.959> day<00:15:57.440> this<00:15:57.600> is<00:15:57.680> what<00:15:57.839> i'd 00:15:57.990 --> 00:15:58.000 align:start position:0% however during the day this is what i'd 00:15:58.000 --> 00:15:59.430 align:start position:0% however during the day this is what i'd really<00:15:58.240> like<00:15:58.399> to<00:15:58.560> do<00:15:58.800> a<00:15:58.880> whole<00:15:59.040> bunch<00:15:59.279> of 00:15:59.430 --> 00:15:59.440 align:start position:0% really like to do a whole bunch of 00:15:59.440 --> 00:16:01.749 align:start position:0% really like to do a whole bunch of nothing 00:16:01.749 --> 00:16:01.759 align:start position:0% nothing 00:16:01.759 --> 00:16:03.749 align:start position:0% nothing one<00:16:01.920> day<00:16:02.320> my<00:16:02.480> wife<00:16:02.880> walked<00:16:03.199> up<00:16:03.279> to<00:16:03.360> me<00:16:03.600> and 00:16:03.749 --> 00:16:03.759 align:start position:0% one day my wife walked up to me and 00:16:03.759 --> 00:16:05.910 align:start position:0% one day my wife walked up to me and asked<00:16:04.160> are<00:16:04.320> you<00:16:04.480> happy 00:16:05.910 --> 00:16:05.920 align:start position:0% asked are you happy 00:16:05.920 --> 00:16:08.069 align:start position:0% asked are you happy and<00:16:06.480> yeah<00:16:06.720> sure<00:16:07.120> i'm<00:16:07.360> on<00:16:07.519> my<00:16:07.600> own<00:16:07.759> private 00:16:08.069 --> 00:16:08.079 align:start position:0% and yeah sure i'm on my own private 00:16:08.079 --> 00:16:11.829 align:start position:0% and yeah sure i'm on my own private island<00:16:08.639> i'm<00:16:08.880> very<00:16:09.040> happy 00:16:11.829 --> 00:16:11.839 align:start position:0% 00:16:11.839 --> 00:16:14.150 align:start position:0% so<00:16:12.000> yeah 00:16:14.150 --> 00:16:14.160 align:start position:0% so yeah 00:16:14.160 --> 00:16:15.829 align:start position:0% so yeah but<00:16:14.320> she<00:16:14.480> said<00:16:14.720> are<00:16:14.800> you<00:16:14.959> really<00:16:15.279> happy<00:16:15.680> are 00:16:15.829 --> 00:16:15.839 align:start position:0% but she said are you really happy are 00:16:15.839 --> 00:16:17.910 align:start position:0% but she said are you really happy are you<00:16:15.920> like<00:16:16.240> jump<00:16:16.480> up<00:16:16.639> and<00:16:16.720> down<00:16:16.959> happy 00:16:17.910 --> 00:16:17.920 align:start position:0% you like jump up and down happy 00:16:17.920 --> 00:16:19.910 align:start position:0% you like jump up and down happy and<00:16:18.240> like<00:16:18.399> a<00:16:18.480> typical<00:16:18.880> guy<00:16:19.199> i<00:16:19.360> said<00:16:19.519> well<00:16:19.759> yeah 00:16:19.910 --> 00:16:19.920 align:start position:0% and like a typical guy i said well yeah 00:16:19.920 --> 00:16:23.990 align:start position:0% and like a typical guy i said well yeah i'm<00:16:20.079> happy<00:16:20.800> whatever 00:16:23.990 --> 00:16:24.000 align:start position:0% 00:16:24.000 --> 00:16:25.509 align:start position:0% then<00:16:24.240> she<00:16:24.399> said 00:16:25.509 --> 00:16:25.519 align:start position:0% then she said 00:16:25.519 --> 00:16:28.069 align:start position:0% then she said really<00:16:25.920> how<00:16:26.160> happy<00:16:26.560> are<00:16:26.639> you 00:16:28.069 --> 00:16:28.079 align:start position:0% really how happy are you 00:16:28.079 --> 00:16:29.749 align:start position:0% really how happy are you and<00:16:28.240> this<00:16:28.480> is<00:16:28.639> when<00:16:28.880> the<00:16:28.959> alarm<00:16:29.279> bells<00:16:29.519> went 00:16:29.749 --> 00:16:29.759 align:start position:0% and this is when the alarm bells went 00:16:29.759 --> 00:16:31.590 align:start position:0% and this is when the alarm bells went off<00:16:29.920> in<00:16:30.000> my<00:16:30.160> head 00:16:31.590 --> 00:16:31.600 align:start position:0% off in my head 00:16:31.600 --> 00:16:34.230 align:start position:0% off in my head because<00:16:32.000> my<00:16:32.240> wife<00:16:32.560> is<00:16:32.720> a<00:16:32.800> data<00:16:33.279> junkie 00:16:34.230 --> 00:16:34.240 align:start position:0% because my wife is a data junkie 00:16:34.240 --> 00:16:36.870 align:start position:0% because my wife is a data junkie she<00:16:34.399> likes<00:16:34.720> to<00:16:34.959> collect<00:16:35.279> data<00:16:36.079> she<00:16:36.240> likes<00:16:36.560> to 00:16:36.870 --> 00:16:36.880 align:start position:0% she likes to collect data she likes to 00:16:36.880 --> 00:16:38.470 align:start position:0% she likes to collect data she likes to manage<00:16:37.199> data<00:16:37.519> she<00:16:37.680> likes<00:16:37.839> to<00:16:37.920> graph<00:16:38.160> it<00:16:38.240> over 00:16:38.470 --> 00:16:38.480 align:start position:0% manage data she likes to graph it over 00:16:38.480 --> 00:16:40.550 align:start position:0% manage data she likes to graph it over time<00:16:38.800> she<00:16:38.959> likes<00:16:39.279> to<00:16:39.920> you<00:16:40.000> know<00:16:40.079> do<00:16:40.240> everything 00:16:40.550 --> 00:16:40.560 align:start position:0% time she likes to you know do everything 00:16:40.560 --> 00:16:43.670 align:start position:0% time she likes to you know do everything you<00:16:40.639> can<00:16:40.720> think<00:16:40.880> of<00:16:41.040> it<00:16:41.279> it's<00:16:41.519> amazing 00:16:43.670 --> 00:16:43.680 align:start position:0% you can think of it it's amazing 00:16:43.680 --> 00:16:45.030 align:start position:0% you can think of it it's amazing and<00:16:43.759> what<00:16:43.920> she's<00:16:44.160> interested<00:16:44.560> now<00:16:44.800> is 00:16:45.030 --> 00:16:45.040 align:start position:0% and what she's interested now is 00:16:45.040 --> 00:16:48.870 align:start position:0% and what she's interested now is quantifying<00:16:45.680> happiness 00:16:48.870 --> 00:16:48.880 align:start position:0% 00:16:48.880 --> 00:16:50.870 align:start position:0% really<00:16:49.120> what<00:16:49.279> she<00:16:49.440> wants<00:16:49.600> to<00:16:49.680> do<00:16:50.000> is<00:16:50.560> track<00:16:50.800> her 00:16:50.870 --> 00:16:50.880 align:start position:0% really what she wants to do is track her 00:16:50.880 --> 00:16:52.949 align:start position:0% really what she wants to do is track her happiness<00:16:51.360> over<00:16:51.600> time<00:16:52.240> as<00:16:52.399> well<00:16:52.639> as<00:16:52.800> what 00:16:52.949 --> 00:16:52.959 align:start position:0% happiness over time as well as what 00:16:52.959 --> 00:16:54.629 align:start position:0% happiness over time as well as what she's<00:16:53.199> doing<00:16:53.440> at<00:16:53.519> the<00:16:53.680> time<00:16:54.079> to<00:16:54.240> see<00:16:54.480> if 00:16:54.629 --> 00:16:54.639 align:start position:0% she's doing at the time to see if 00:16:54.639 --> 00:16:56.150 align:start position:0% she's doing at the time to see if there's<00:16:54.800> any<00:16:54.959> correlation 00:16:56.150 --> 00:16:56.160 align:start position:0% there's any correlation 00:16:56.160 --> 00:17:00.069 align:start position:0% there's any correlation and<00:16:56.320> also<00:16:56.560> long-term<00:16:57.040> trends 00:17:00.069 --> 00:17:00.079 align:start position:0% 00:17:00.079 --> 00:17:06.789 align:start position:0% so<00:17:00.320> really 00:17:06.789 --> 00:17:06.799 align:start position:0% 00:17:06.799 --> 00:17:09.510 align:start position:0% the<00:17:06.959> thing<00:17:07.199> she's<00:17:07.439> looking<00:17:07.760> for 00:17:09.510 --> 00:17:09.520 align:start position:0% the thing she's looking for 00:17:09.520 --> 00:17:11.270 align:start position:0% the thing she's looking for you<00:17:09.600> know<00:17:09.839> is<00:17:10.000> capturing<00:17:10.400> contacts<00:17:11.039> have 00:17:11.270 --> 00:17:11.280 align:start position:0% you know is capturing contacts have 00:17:11.280 --> 00:17:12.789 align:start position:0% you know is capturing contacts have something<00:17:11.600> easy<00:17:11.839> to<00:17:11.919> use<00:17:12.160> that<00:17:12.319> she<00:17:12.480> can<00:17:12.559> use 00:17:12.789 --> 00:17:12.799 align:start position:0% something easy to use that she can use 00:17:12.799 --> 00:17:14.710 align:start position:0% something easy to use that she can use anywhere<00:17:13.439> and<00:17:13.600> myself<00:17:14.079> i<00:17:14.240> have<00:17:14.319> very<00:17:14.480> simple 00:17:14.710 --> 00:17:14.720 align:start position:0% anywhere and myself i have very simple 00:17:14.720 --> 00:17:18.069 align:start position:0% anywhere and myself i have very simple needs 00:17:18.069 --> 00:17:18.079 align:start position:0% 00:17:18.079 --> 00:17:21.110 align:start position:0% are<00:17:18.240> however<00:17:18.559> a<00:17:19.039> mixed<00:17:19.360> couple<00:17:20.000> uh<00:17:20.319> she<00:17:20.720> has 00:17:21.110 --> 00:17:21.120 align:start position:0% are however a mixed couple uh she has 00:17:21.120 --> 00:17:23.029 align:start position:0% are however a mixed couple uh she has android<00:17:21.839> i<00:17:21.919> mean<00:17:22.079> i<00:17:22.160> have<00:17:22.400> android<00:17:22.720> and<00:17:22.880> she 00:17:23.029 --> 00:17:23.039 align:start position:0% android i mean i have android and she 00:17:23.039 --> 00:17:24.309 align:start position:0% android i mean i have android and she has<00:17:23.360> iphone 00:17:24.309 --> 00:17:24.319 align:start position:0% has iphone 00:17:24.319 --> 00:17:25.429 align:start position:0% has iphone so<00:17:24.480> we're<00:17:24.559> not<00:17:24.720> going<00:17:24.799> to<00:17:24.799> be<00:17:24.959> writing<00:17:25.280> any 00:17:25.429 --> 00:17:25.439 align:start position:0% so we're not going to be writing any 00:17:25.439 --> 00:17:27.270 align:start position:0% so we're not going to be writing any phone<00:17:25.679> apps<00:17:26.079> instead 00:17:27.270 --> 00:17:27.280 align:start position:0% phone apps instead 00:17:27.280 --> 00:17:28.230 align:start position:0% phone apps instead i'm<00:17:27.439> just<00:17:27.520> going<00:17:27.600> to<00:17:27.679> whip<00:17:27.919> out<00:17:28.000> a<00:17:28.079> simple 00:17:28.230 --> 00:17:28.240 align:start position:0% i'm just going to whip out a simple 00:17:28.240 --> 00:17:30.830 align:start position:0% i'm just going to whip out a simple little<00:17:28.400> web<00:17:28.640> app<00:17:29.120> how<00:17:29.280> hard<00:17:29.440> can<00:17:29.600> this 00:17:30.830 --> 00:17:30.840 align:start position:0% little web app how hard can this 00:17:30.840 --> 00:17:33.430 align:start position:0% little web app how hard can this be<00:17:32.000> this<00:17:32.160> when<00:17:32.400> i<00:17:32.720> this<00:17:32.880> is<00:17:32.960> when<00:17:33.120> i<00:17:33.200> start 00:17:33.430 --> 00:17:33.440 align:start position:0% be this when i this is when i start 00:17:33.440 --> 00:17:35.590 align:start position:0% be this when i this is when i start thinking<00:17:33.760> about<00:17:34.000> it<00:17:34.480> because 00:17:35.590 --> 00:17:35.600 align:start position:0% thinking about it because 00:17:35.600 --> 00:17:37.590 align:start position:0% thinking about it because at<00:17:35.760> my<00:17:35.919> day<00:17:36.080> job<00:17:36.320> we<00:17:36.480> have<00:17:36.640> hundreds<00:17:37.039> of<00:17:37.200> hosts 00:17:37.590 --> 00:17:37.600 align:start position:0% at my day job we have hundreds of hosts 00:17:37.600 --> 00:17:39.029 align:start position:0% at my day job we have hundreds of hosts however<00:17:37.919> they're<00:17:38.080> all<00:17:38.160> being<00:17:38.320> used<00:17:38.799> and 00:17:39.029 --> 00:17:39.039 align:start position:0% however they're all being used and 00:17:39.039 --> 00:17:41.510 align:start position:0% however they're all being used and personally<00:17:39.440> i<00:17:39.600> have<00:17:39.760> dozens<00:17:40.720> and<00:17:41.120> i<00:17:41.280> don't 00:17:41.510 --> 00:17:41.520 align:start position:0% personally i have dozens and i don't 00:17:41.520 --> 00:17:43.029 align:start position:0% personally i have dozens and i don't really<00:17:41.760> need<00:17:42.000> another<00:17:42.320> one 00:17:43.029 --> 00:17:43.039 align:start position:0% really need another one 00:17:43.039 --> 00:17:44.710 align:start position:0% really need another one and<00:17:43.200> there's<00:17:43.360> a<00:17:43.440> lot<00:17:43.600> to<00:17:43.760> owning<00:17:44.000> a<00:17:44.080> host<00:17:44.559> for 00:17:44.710 --> 00:17:44.720 align:start position:0% and there's a lot to owning a host for 00:17:44.720 --> 00:17:46.870 align:start position:0% and there's a lot to owning a host for an<00:17:45.039> initial<00:17:45.440> setup<00:17:45.760> to<00:17:45.919> maintenance<00:17:46.320> security 00:17:46.870 --> 00:17:46.880 align:start position:0% an initial setup to maintenance security 00:17:46.880 --> 00:17:49.029 align:start position:0% an initial setup to maintenance security updates<00:17:47.679> there's<00:17:47.840> some<00:17:48.000> non-trivial<00:17:48.640> amazon 00:17:49.029 --> 00:17:49.039 align:start position:0% updates there's some non-trivial amazon 00:17:49.039 --> 00:17:51.270 align:start position:0% updates there's some non-trivial amazon stuff<00:17:49.280> if<00:17:49.440> you<00:17:49.679> do<00:17:49.919> it<00:17:50.000> up<00:17:50.160> there<00:17:50.799> monitoring 00:17:51.270 --> 00:17:51.280 align:start position:0% stuff if you do it up there monitoring 00:17:51.280 --> 00:17:52.470 align:start position:0% stuff if you do it up there monitoring and<00:17:51.360> if<00:17:51.440> you<00:17:51.520> have<00:17:51.679> monitoring<00:17:52.080> then<00:17:52.240> you<00:17:52.320> get 00:17:52.470 --> 00:17:52.480 align:start position:0% and if you have monitoring then you get 00:17:52.480 --> 00:17:55.270 align:start position:0% and if you have monitoring then you get pages<00:17:53.120> and<00:17:53.280> really<00:17:53.600> i<00:17:53.760> just<00:17:54.000> don't<00:17:54.160> want<00:17:54.400> that 00:17:55.270 --> 00:17:55.280 align:start position:0% pages and really i just don't want that 00:17:55.280 --> 00:17:57.990 align:start position:0% pages and really i just don't want that and<00:17:55.919> ultimately<00:17:56.400> the<00:17:56.559> monetary<00:17:57.039> cost 00:17:57.990 --> 00:17:58.000 align:start position:0% and ultimately the monetary cost 00:17:58.000 --> 00:18:00.230 align:start position:0% and ultimately the monetary cost is<00:17:58.400> uh<00:17:58.880> it<00:17:59.200> doesn't<00:17:59.520> matter<00:17:59.760> to<00:17:59.919> me<00:18:00.080> i<00:18:00.160> just 00:18:00.230 --> 00:18:00.240 align:start position:0% is uh it doesn't matter to me i just 00:18:00.240 --> 00:18:02.549 align:start position:0% is uh it doesn't matter to me i just don't<00:18:00.400> want<00:18:00.559> another<00:18:00.880> host 00:18:02.549 --> 00:18:02.559 align:start position:0% don't want another host 00:18:02.559 --> 00:18:04.950 align:start position:0% don't want another host all<00:18:02.720> i<00:18:02.799> want<00:18:03.039> is<00:18:03.200> a<00:18:03.280> simple<00:18:03.520> web<00:18:03.760> app 00:18:04.950 --> 00:18:04.960 align:start position:0% all i want is a simple web app 00:18:04.960 --> 00:18:05.990 align:start position:0% all i want is a simple web app and<00:18:05.120> this<00:18:05.200> is<00:18:05.280> when<00:18:05.440> i<00:18:05.520> started<00:18:05.760> looking<00:18:05.919> at 00:18:05.990 --> 00:18:06.000 align:start position:0% and this is when i started looking at 00:18:06.000 --> 00:18:08.710 align:start position:0% and this is when i started looking at heroku<00:18:06.880> it's<00:18:07.120> really<00:18:07.600> a<00:18:07.840> simple<00:18:08.160> cloud<00:18:08.480> app 00:18:08.710 --> 00:18:08.720 align:start position:0% heroku it's really a simple cloud app 00:18:08.720 --> 00:18:09.750 align:start position:0% heroku it's really a simple cloud app platform 00:18:09.750 --> 00:18:09.760 align:start position:0% platform 00:18:09.760 --> 00:18:12.549 align:start position:0% platform it's<00:18:10.080> very<00:18:10.320> easy<00:18:10.640> to<00:18:10.799> do<00:18:11.120> you<00:18:11.360> uh<00:18:11.919> it's<00:18:12.160> sold<00:18:12.400> as 00:18:12.549 --> 00:18:12.559 align:start position:0% it's very easy to do you uh it's sold as 00:18:12.559 --> 00:18:14.630 align:start position:0% it's very easy to do you uh it's sold as a<00:18:12.640> service<00:18:13.039> so<00:18:13.200> basically<00:18:13.600> your<00:18:13.840> closure<00:18:14.240> app 00:18:14.630 --> 00:18:14.640 align:start position:0% a service so basically your closure app 00:18:14.640 --> 00:18:16.150 align:start position:0% a service so basically your closure app is<00:18:14.880> up<00:18:15.039> and<00:18:15.120> running 00:18:16.150 --> 00:18:16.160 align:start position:0% is up and running 00:18:16.160 --> 00:18:17.110 align:start position:0% is up and running and 00:18:17.110 --> 00:18:17.120 align:start position:0% and 00:18:17.120 --> 00:18:19.669 align:start position:0% and basically<00:18:17.600> what<00:18:17.760> you<00:18:18.000> don't<00:18:18.320> do<00:18:18.799> is<00:18:19.280> manage<00:18:19.600> a 00:18:19.669 --> 00:18:19.679 align:start position:0% basically what you don't do is manage a 00:18:19.679 --> 00:18:21.510 align:start position:0% basically what you don't do is manage a whole<00:18:19.840> lot<00:18:20.000> of<00:18:20.160> stuff<00:18:20.960> they're<00:18:21.200> going<00:18:21.280> to<00:18:21.360> be 00:18:21.510 --> 00:18:21.520 align:start position:0% whole lot of stuff they're going to be 00:18:21.520 --> 00:18:23.590 align:start position:0% whole lot of stuff they're going to be taking<00:18:21.760> care<00:18:21.919> of<00:18:22.080> host<00:18:22.320> failures<00:18:23.039> data<00:18:23.280> center 00:18:23.590 --> 00:18:23.600 align:start position:0% taking care of host failures data center 00:18:23.600 --> 00:18:25.909 align:start position:0% taking care of host failures data center problems<00:18:24.240> all<00:18:24.640> things<00:18:24.880> with<00:18:25.039> security<00:18:25.760> as 00:18:25.909 --> 00:18:25.919 align:start position:0% problems all things with security as 00:18:25.919 --> 00:18:27.350 align:start position:0% problems all things with security as well<00:18:26.080> as<00:18:26.240> anything<00:18:26.559> that<00:18:26.640> has<00:18:26.880> to<00:18:26.960> happen<00:18:27.200> with 00:18:27.350 --> 00:18:27.360 align:start position:0% well as anything that has to happen with 00:18:27.360 --> 00:18:28.470 align:start position:0% well as anything that has to happen with the<00:18:27.520> update 00:18:28.470 --> 00:18:28.480 align:start position:0% the update 00:18:28.480 --> 00:18:30.230 align:start position:0% the update as<00:18:28.640> a<00:18:28.640> matter<00:18:28.880> of<00:18:28.960> fact<00:18:29.600> you've<00:18:29.760> probably<00:18:30.080> seen 00:18:30.230 --> 00:18:30.240 align:start position:0% as a matter of fact you've probably seen 00:18:30.240 --> 00:18:32.549 align:start position:0% as a matter of fact you've probably seen in<00:18:30.320> the<00:18:30.400> news<00:18:30.720> last<00:18:30.960> week<00:18:31.520> i<00:18:31.679> spent<00:18:32.240> almost<00:18:32.480> the 00:18:32.549 --> 00:18:32.559 align:start position:0% in the news last week i spent almost the 00:18:32.559 --> 00:18:34.230 align:start position:0% in the news last week i spent almost the entire<00:18:32.880> week<00:18:33.039> just<00:18:33.280> watching<00:18:33.679> new<00:18:33.840> york<00:18:34.000> city 00:18:34.230 --> 00:18:34.240 align:start position:0% entire week just watching new york city 00:18:34.240 --> 00:18:35.990 align:start position:0% entire week just watching new york city data<00:18:34.480> centers<00:18:34.799> go<00:18:34.960> up<00:18:35.120> and<00:18:35.200> down 00:18:35.990 --> 00:18:36.000 align:start position:0% data centers go up and down 00:18:36.000 --> 00:18:37.510 align:start position:0% data centers go up and down and<00:18:36.320> then<00:18:36.640> three<00:18:36.799> days<00:18:37.039> later<00:18:37.280> when<00:18:37.440> the 00:18:37.510 --> 00:18:37.520 align:start position:0% and then three days later when the 00:18:37.520 --> 00:18:39.029 align:start position:0% and then three days later when the gasoline<00:18:38.000> ran<00:18:38.160> out<00:18:38.320> the<00:18:38.400> same<00:18:38.559> thing<00:18:38.720> happened 00:18:39.029 --> 00:18:39.039 align:start position:0% gasoline ran out the same thing happened 00:18:39.039 --> 00:18:40.549 align:start position:0% gasoline ran out the same thing happened in<00:18:39.120> new<00:18:39.280> jersey 00:18:40.549 --> 00:18:40.559 align:start position:0% in new jersey 00:18:40.559 --> 00:18:42.710 align:start position:0% in new jersey and<00:18:41.039> uh<00:18:41.600> yeah<00:18:41.760> i<00:18:41.840> had<00:18:42.000> apparently<00:18:42.400> plenty<00:18:42.640> of 00:18:42.710 --> 00:18:42.720 align:start position:0% and uh yeah i had apparently plenty of 00:18:42.720 --> 00:18:44.470 align:start position:0% and uh yeah i had apparently plenty of machines<00:18:43.039> to<00:18:43.120> worry<00:18:43.440> about<00:18:43.679> but<00:18:44.000> heroku 00:18:44.470 --> 00:18:44.480 align:start position:0% machines to worry about but heroku 00:18:44.480 --> 00:18:47.190 align:start position:0% machines to worry about but heroku wasn't<00:18:44.720> one<00:18:44.880> of<00:18:44.960> them 00:18:47.190 --> 00:18:47.200 align:start position:0% 00:18:47.200 --> 00:18:48.950 align:start position:0% and<00:18:47.360> to<00:18:47.440> write<00:18:47.600> software<00:18:48.160> for<00:18:48.320> heroku<00:18:48.880> is 00:18:48.950 --> 00:18:48.960 align:start position:0% and to write software for heroku is 00:18:48.960 --> 00:18:51.110 align:start position:0% and to write software for heroku is actually<00:18:49.200> really<00:18:49.440> easy<00:18:50.000> um<00:18:50.480> you<00:18:50.640> just<00:18:50.880> hack 00:18:51.110 --> 00:18:51.120 align:start position:0% actually really easy um you just hack 00:18:51.120 --> 00:18:53.510 align:start position:0% actually really easy um you just hack out<00:18:51.200> your<00:18:51.360> closure<00:18:52.240> you<00:18:52.480> update<00:18:52.799> it 00:18:53.510 --> 00:18:53.520 align:start position:0% out your closure you update it 00:18:53.520 --> 00:18:55.430 align:start position:0% out your closure you update it with<00:18:53.760> git<00:18:54.080> basically<00:18:54.640> you<00:18:54.799> send<00:18:55.039> it<00:18:55.120> right<00:18:55.360> up 00:18:55.430 --> 00:18:55.440 align:start position:0% with git basically you send it right up 00:18:55.440 --> 00:18:56.390 align:start position:0% with git basically you send it right up to<00:18:55.520> heroku 00:18:56.390 --> 00:18:56.400 align:start position:0% to heroku 00:18:56.400 --> 00:18:58.230 align:start position:0% to heroku and<00:18:56.480> they<00:18:56.640> will<00:18:57.200> launch<00:18:57.440> it<00:18:57.600> and<00:18:57.760> manage<00:18:58.000> it<00:18:58.160> on 00:18:58.230 --> 00:18:58.240 align:start position:0% and they will launch it and manage it on 00:18:58.240 --> 00:19:00.150 align:start position:0% and they will launch it and manage it on their<00:18:58.400> servers<00:18:59.120> you<00:18:59.200> can<00:18:59.360> then<00:18:59.600> point<00:18:59.919> to<00:19:00.000> dot 00:19:00.150 --> 00:19:00.160 align:start position:0% their servers you can then point to dot 00:19:00.160 --> 00:19:03.669 align:start position:0% their servers you can then point to dot com<00:19:00.400> to<00:19:00.559> it<00:19:01.039> and<00:19:01.120> you're<00:19:01.280> all<00:19:01.440> set 00:19:03.669 --> 00:19:03.679 align:start position:0% com to it and you're all set 00:19:03.679 --> 00:19:06.789 align:start position:0% com to it and you're all set roku<00:19:04.080> conveniently<00:19:04.559> runs<00:19:04.880> on<00:19:05.039> amazon 00:19:06.789 --> 00:19:06.799 align:start position:0% roku conveniently runs on amazon 00:19:06.799 --> 00:19:08.870 align:start position:0% roku conveniently runs on amazon you<00:19:07.039> probably<00:19:07.200> heard<00:19:07.440> of<00:19:07.520> ec2<00:19:08.240> for<00:19:08.640> their 00:19:08.870 --> 00:19:08.880 align:start position:0% you probably heard of ec2 for their 00:19:08.880 --> 00:19:11.029 align:start position:0% you probably heard of ec2 for their virtual<00:19:09.200> machines<00:19:09.919> everything<00:19:10.400> else<00:19:10.559> i<00:19:10.720> have 00:19:11.029 --> 00:19:11.039 align:start position:0% virtual machines everything else i have 00:19:11.039 --> 00:19:12.789 align:start position:0% virtual machines everything else i have dozens<00:19:11.440> of<00:19:11.600> other<00:19:11.840> services<00:19:12.480> which<00:19:12.720> are 00:19:12.789 --> 00:19:12.799 align:start position:0% dozens of other services which are 00:19:12.799 --> 00:19:13.909 align:start position:0% dozens of other services which are really<00:19:13.039> nice 00:19:13.909 --> 00:19:13.919 align:start position:0% really nice 00:19:13.919 --> 00:19:16.470 align:start position:0% really nice um<00:19:14.720> s3<00:19:15.280> has<00:19:15.440> recently<00:19:15.840> recently<00:19:16.160> come<00:19:16.320> out 00:19:16.470 --> 00:19:16.480 align:start position:0% um s3 has recently recently come out 00:19:16.480 --> 00:19:17.750 align:start position:0% um s3 has recently recently come out with<00:19:16.559> a<00:19:16.640> new<00:19:16.799> version<00:19:17.440> where<00:19:17.600> they're 00:19:17.750 --> 00:19:17.760 align:start position:0% with a new version where they're 00:19:17.760 --> 00:19:19.830 align:start position:0% with a new version where they're charging<00:19:18.240> a<00:19:18.480> dollar<00:19:18.799> i<00:19:18.799> mean<00:19:19.039> a<00:19:19.200> penny<00:19:19.679> a 00:19:19.830 --> 00:19:19.840 align:start position:0% charging a dollar i mean a penny a 00:19:19.840 --> 00:19:21.190 align:start position:0% charging a dollar i mean a penny a gigabyte 00:19:21.190 --> 00:19:21.200 align:start position:0% gigabyte 00:19:21.200 --> 00:19:22.710 align:start position:0% gigabyte and<00:19:21.360> that's<00:19:21.679> that's<00:19:21.919> really<00:19:22.160> game<00:19:22.320> changer 00:19:22.710 --> 00:19:22.720 align:start position:0% and that's that's really game changer 00:19:22.720 --> 00:19:25.350 align:start position:0% and that's that's really game changer and<00:19:22.880> they<00:19:23.039> also<00:19:23.360> offer<00:19:24.000> databases<00:19:25.200> the 00:19:25.350 --> 00:19:25.360 align:start position:0% and they also offer databases the 00:19:25.360 --> 00:19:26.950 align:start position:0% and they also offer databases the queuing<00:19:25.679> service<00:19:26.000> has<00:19:26.160> saved<00:19:26.400> my<00:19:26.480> bacon<00:19:26.799> more 00:19:26.950 --> 00:19:26.960 align:start position:0% queuing service has saved my bacon more 00:19:26.960 --> 00:19:28.150 align:start position:0% queuing service has saved my bacon more than<00:19:27.120> once 00:19:28.150 --> 00:19:28.160 align:start position:0% than once 00:19:28.160 --> 00:19:30.310 align:start position:0% than once and<00:19:28.320> stuff<00:19:28.559> like<00:19:28.720> this 00:19:30.310 --> 00:19:30.320 align:start position:0% and stuff like this 00:19:30.320 --> 00:19:31.990 align:start position:0% and stuff like this so<00:19:30.559> really<00:19:30.720> for<00:19:30.880> my<00:19:31.039> simple<00:19:31.280> happiness<00:19:31.760> web 00:19:31.990 --> 00:19:32.000 align:start position:0% so really for my simple happiness web 00:19:32.000 --> 00:19:34.789 align:start position:0% so really for my simple happiness web app<00:19:32.480> what<00:19:32.640> i<00:19:32.720> want<00:19:32.880> to<00:19:32.960> do<00:19:33.200> is<00:19:33.440> collect<00:19:33.919> data<00:19:34.640> i 00:19:34.789 --> 00:19:34.799 align:start position:0% app what i want to do is collect data i 00:19:34.799 --> 00:19:36.630 align:start position:0% app what i want to do is collect data i want<00:19:34.960> to<00:19:35.039> store<00:19:35.440> data<00:19:35.919> and<00:19:36.000> then<00:19:36.160> i<00:19:36.240> also<00:19:36.400> want 00:19:36.630 --> 00:19:36.640 align:start position:0% want to store data and then i also want 00:19:36.640 --> 00:19:37.909 align:start position:0% want to store data and then i also want to<00:19:36.720> send<00:19:36.960> out<00:19:37.039> collection<00:19:37.440> reminders 00:19:37.909 --> 00:19:37.919 align:start position:0% to send out collection reminders 00:19:37.919 --> 00:19:39.270 align:start position:0% to send out collection reminders throughout<00:19:38.240> the<00:19:38.320> day 00:19:39.270 --> 00:19:39.280 align:start position:0% throughout the day 00:19:39.280 --> 00:19:41.430 align:start position:0% throughout the day with<00:19:39.600> both<00:19:40.000> both<00:19:40.240> text<00:19:40.559> messages<00:19:41.039> as<00:19:41.120> well<00:19:41.280> as 00:19:41.430 --> 00:19:41.440 align:start position:0% with both both text messages as well as 00:19:41.440 --> 00:19:45.830 align:start position:0% with both both text messages as well as email<00:19:41.840> so<00:19:42.000> you<00:19:42.080> can<00:19:42.240> get<00:19:42.400> randomized<00:19:42.960> samples 00:19:45.830 --> 00:19:45.840 align:start position:0% 00:19:45.840 --> 00:19:47.430 align:start position:0% this<00:19:46.080> means<00:19:46.320> a<00:19:46.400> simple<00:19:46.640> web<00:19:46.880> app<00:19:47.039> is<00:19:47.120> suddenly 00:19:47.430 --> 00:19:47.440 align:start position:0% this means a simple web app is suddenly 00:19:47.440 --> 00:19:49.270 align:start position:0% this means a simple web app is suddenly becoming<00:19:47.840> a<00:19:47.840> little<00:19:48.000> more<00:19:48.160> sophisticated<00:19:49.120> now 00:19:49.270 --> 00:19:49.280 align:start position:0% becoming a little more sophisticated now 00:19:49.280 --> 00:19:50.710 align:start position:0% becoming a little more sophisticated now you<00:19:49.440> have<00:19:49.600> to<00:19:49.679> deal<00:19:49.840> with<00:19:49.919> the<00:19:50.000> database<00:19:50.559> as 00:19:50.710 --> 00:19:50.720 align:start position:0% you have to deal with the database as 00:19:50.720 --> 00:19:53.510 align:start position:0% you have to deal with the database as well<00:19:51.039> as<00:19:52.000> either<00:19:52.320> mail<00:19:52.559> server<00:19:52.960> or<00:19:53.120> some<00:19:53.360> sort 00:19:53.510 --> 00:19:53.520 align:start position:0% well as either mail server or some sort 00:19:53.520 --> 00:19:55.270 align:start position:0% well as either mail server or some sort of<00:19:53.679> service<00:19:53.919> for<00:19:54.080> dealing<00:19:54.320> with<00:19:54.480> all<00:19:54.559> that<00:19:55.120> and 00:19:55.270 --> 00:19:55.280 align:start position:0% of service for dealing with all that and 00:19:55.280 --> 00:19:57.430 align:start position:0% of service for dealing with all that and these<00:19:55.600> are<00:19:55.919> two<00:19:56.160> more<00:19:56.400> services<00:19:56.880> that<00:19:57.039> i<00:19:57.280> do 00:19:57.430 --> 00:19:57.440 align:start position:0% these are two more services that i do 00:19:57.440 --> 00:19:59.270 align:start position:0% these are two more services that i do not<00:19:57.679> want<00:19:57.919> to<00:19:58.000> manage 00:19:59.270 --> 00:19:59.280 align:start position:0% not want to manage 00:19:59.280 --> 00:20:02.230 align:start position:0% not want to manage much<00:19:59.520> less<00:19:59.760> two<00:19:59.919> more<00:20:00.160> hosts 00:20:02.230 --> 00:20:02.240 align:start position:0% much less two more hosts 00:20:02.240 --> 00:20:04.630 align:start position:0% much less two more hosts and<00:20:02.640> with<00:20:02.880> amazon<00:20:03.600> and<00:20:03.679> heroku<00:20:04.240> we<00:20:04.400> can<00:20:04.480> do 00:20:04.630 --> 00:20:04.640 align:start position:0% and with amazon and heroku we can do 00:20:04.640 --> 00:20:05.669 align:start position:0% and with amazon and heroku we can do that 00:20:05.669 --> 00:20:05.679 align:start position:0% that 00:20:05.679 --> 00:20:06.950 align:start position:0% that so 00:20:06.950 --> 00:20:06.960 align:start position:0% so 00:20:06.960 --> 00:20:09.029 align:start position:0% so from<00:20:07.120> the<00:20:07.679> time<00:20:07.919> i<00:20:08.000> bought<00:20:08.240> the<00:20:08.400> dot<00:20:08.640> com<00:20:08.880> which 00:20:09.029 --> 00:20:09.039 align:start position:0% from the time i bought the dot com which 00:20:09.039 --> 00:20:10.470 align:start position:0% from the time i bought the dot com which is<00:20:09.200> meow<00:20:09.520> meter 00:20:10.470 --> 00:20:10.480 align:start position:0% is meow meter 00:20:10.480 --> 00:20:11.750 align:start position:0% is meow meter um<00:20:10.799> you<00:20:10.880> can<00:20:10.960> tell<00:20:11.200> all<00:20:11.280> the<00:20:11.360> good<00:20:11.520> ones<00:20:11.679> are 00:20:11.750 --> 00:20:11.760 align:start position:0% um you can tell all the good ones are 00:20:11.760 --> 00:20:13.270 align:start position:0% um you can tell all the good ones are taken 00:20:13.270 --> 00:20:13.280 align:start position:0% taken 00:20:13.280 --> 00:20:14.390 align:start position:0% taken uh<00:20:13.600> to<00:20:13.760> the 00:20:14.390 --> 00:20:14.400 align:start position:0% uh to the 00:20:14.400 --> 00:20:15.669 align:start position:0% uh to the to<00:20:14.640> when<00:20:14.799> it<00:20:14.880> was<00:20:14.960> up<00:20:15.120> and<00:20:15.200> running<00:20:15.440> was<00:20:15.600> a 00:20:15.669 --> 00:20:15.679 align:start position:0% to when it was up and running was a 00:20:15.679 --> 00:20:17.590 align:start position:0% to when it was up and running was a total<00:20:15.919> time<00:20:16.080> of<00:20:16.240> four<00:20:16.480> hours<00:20:16.960> and<00:20:17.120> really<00:20:17.440> only 00:20:17.590 --> 00:20:17.600 align:start position:0% total time of four hours and really only 00:20:17.600 --> 00:20:19.029 align:start position:0% total time of four hours and really only about<00:20:17.760> half<00:20:18.000> of<00:20:18.080> that<00:20:18.240> was<00:20:18.400> involved<00:20:18.799> in<00:20:18.880> the 00:20:19.029 --> 00:20:19.039 align:start position:0% about half of that was involved in the 00:20:19.039 --> 00:20:22.150 align:start position:0% about half of that was involved in the technology<00:20:19.520> side 00:20:22.150 --> 00:20:22.160 align:start position:0% 00:20:22.160 --> 00:20:25.110 align:start position:0% and<00:20:22.559> it<00:20:22.720> is<00:20:22.799> indeed<00:20:23.120> very<00:20:23.280> simple 00:20:25.110 --> 00:20:25.120 align:start position:0% and it is indeed very simple 00:20:25.120 --> 00:20:27.590 align:start position:0% and it is indeed very simple i'll<00:20:25.360> ask<00:20:25.600> for<00:20:25.760> is<00:20:25.919> your<00:20:26.080> name 00:20:27.590 --> 00:20:27.600 align:start position:0% i'll ask for is your name 00:20:27.600 --> 00:20:29.029 align:start position:0% i'll ask for is your name the<00:20:27.760> contacts<00:20:28.159> that<00:20:28.240> you're<00:20:28.400> doing<00:20:28.720> and<00:20:28.880> then 00:20:29.029 --> 00:20:29.039 align:start position:0% the contacts that you're doing and then 00:20:29.039 --> 00:20:31.909 align:start position:0% the contacts that you're doing and then a<00:20:29.200> big<00:20:29.440> giant<00:20:29.760> button<00:20:30.159> of<00:20:30.320> how<00:20:30.559> happy<00:20:30.880> are<00:20:31.039> you 00:20:31.909 --> 00:20:31.919 align:start position:0% a big giant button of how happy are you 00:20:31.919 --> 00:20:33.750 align:start position:0% a big giant button of how happy are you clearly<00:20:32.320> everybody<00:20:32.640> here<00:20:32.799> is<00:20:32.880> a<00:20:32.960> nine 00:20:33.750 --> 00:20:33.760 align:start position:0% clearly everybody here is a nine 00:20:33.760 --> 00:20:36.070 align:start position:0% clearly everybody here is a nine ding 00:20:36.070 --> 00:20:36.080 align:start position:0% 00:20:36.080 --> 00:20:38.310 align:start position:0% once<00:20:36.400> you<00:20:36.640> uh<00:20:37.039> enter<00:20:37.360> in<00:20:37.520> some<00:20:37.840> information 00:20:38.310 --> 00:20:38.320 align:start position:0% once you uh enter in some information 00:20:38.320 --> 00:20:39.990 align:start position:0% once you uh enter in some information it'll<00:20:38.559> give<00:20:38.640> you<00:20:38.799> some<00:20:38.960> happiness<00:20:39.360> back<00:20:39.760> it'll 00:20:39.990 --> 00:20:40.000 align:start position:0% it'll give you some happiness back it'll 00:20:40.000 --> 00:20:41.750 align:start position:0% it'll give you some happiness back it'll throw<00:20:40.159> up<00:20:40.320> a<00:20:40.400> little<00:20:40.640> um 00:20:41.750 --> 00:20:41.760 align:start position:0% throw up a little um 00:20:41.760 --> 00:20:43.750 align:start position:0% throw up a little um little<00:20:42.000> quote<00:20:42.720> and<00:20:43.120> actually<00:20:43.440> i<00:20:43.520> think<00:20:43.679> i 00:20:43.750 --> 00:20:43.760 align:start position:0% little quote and actually i think i 00:20:43.760 --> 00:20:45.350 align:start position:0% little quote and actually i think i spent<00:20:44.240> about<00:20:44.480> half<00:20:44.720> the<00:20:44.799> time<00:20:44.960> looking<00:20:45.200> for 00:20:45.350 --> 00:20:45.360 align:start position:0% spent about half the time looking for 00:20:45.360 --> 00:20:47.110 align:start position:0% spent about half the time looking for quotes 00:20:47.110 --> 00:20:47.120 align:start position:0% quotes 00:20:47.120 --> 00:20:50.470 align:start position:0% quotes seriously<00:20:47.919> it's<00:20:48.080> not<00:20:48.240> that<00:20:48.480> easy 00:20:50.470 --> 00:20:50.480 align:start position:0% seriously it's not that easy 00:20:50.480 --> 00:20:52.310 align:start position:0% seriously it's not that easy and<00:20:50.640> then<00:20:50.799> every<00:20:50.960> other<00:20:51.120> time<00:20:51.280> you<00:20:51.440> log<00:20:51.760> in 00:20:52.310 --> 00:20:52.320 align:start position:0% and then every other time you log in 00:20:52.320 --> 00:20:53.750 align:start position:0% and then every other time you log in it's<00:20:52.559> even<00:20:52.799> easier<00:20:53.039> it<00:20:53.120> doesn't<00:20:53.360> need<00:20:53.520> to<00:20:53.600> know 00:20:53.750 --> 00:20:53.760 align:start position:0% it's even easier it doesn't need to know 00:20:53.760 --> 00:20:55.830 align:start position:0% it's even easier it doesn't need to know who<00:20:53.919> you<00:20:54.080> are<00:20:54.400> because<00:20:54.640> it<00:20:54.720> has<00:20:54.880> a<00:20:54.960> cookie<00:20:55.600> uh 00:20:55.830 --> 00:20:55.840 align:start position:0% who you are because it has a cookie uh 00:20:55.840 --> 00:20:56.950 align:start position:0% who you are because it has a cookie uh and<00:20:56.000> as<00:20:56.159> a<00:20:56.159> matter<00:20:56.320> of<00:20:56.400> fact<00:20:56.559> you<00:20:56.720> don't<00:20:56.799> even 00:20:56.950 --> 00:20:56.960 align:start position:0% and as a matter of fact you don't even 00:20:56.960 --> 00:20:57.990 align:start position:0% and as a matter of fact you don't even have<00:20:57.039> to<00:20:57.120> tell<00:20:57.280> it<00:20:57.360> what<00:20:57.440> you're<00:20:57.600> doing<00:20:57.919> you 00:20:57.990 --> 00:20:58.000 align:start position:0% have to tell it what you're doing you 00:20:58.000 --> 00:20:59.510 align:start position:0% have to tell it what you're doing you can<00:20:58.080> just<00:20:58.240> give<00:20:58.400> it<00:20:58.480> a<00:20:58.559> number<00:20:58.880> boom<00:20:59.200> it<00:20:59.280> knows 00:20:59.510 --> 00:20:59.520 align:start position:0% can just give it a number boom it knows 00:20:59.520 --> 00:21:02.070 align:start position:0% can just give it a number boom it knows the<00:20:59.600> date<00:21:00.400> and<00:21:00.640> all<00:21:00.799> this<00:21:01.039> is<00:21:01.200> being<00:21:01.440> stored<00:21:01.919> in 00:21:02.070 --> 00:21:02.080 align:start position:0% the date and all this is being stored in 00:21:02.080 --> 00:21:04.149 align:start position:0% the date and all this is being stored in a<00:21:02.159> database<00:21:03.039> actually 00:21:04.149 --> 00:21:04.159 align:start position:0% a database actually 00:21:04.159 --> 00:21:06.470 align:start position:0% a database actually and<00:21:04.400> works<00:21:04.720> great<00:21:04.960> on 00:21:06.470 --> 00:21:06.480 align:start position:0% and works great on 00:21:06.480 --> 00:21:10.149 align:start position:0% and works great on phones<00:21:06.960> as<00:21:07.039> well<00:21:07.200> as<00:21:07.360> tablets<00:21:07.840> etc 00:21:10.149 --> 00:21:10.159 align:start position:0% phones as well as tablets etc 00:21:10.159 --> 00:21:12.789 align:start position:0% phones as well as tablets etc this<00:21:10.400> is<00:21:10.480> the<00:21:10.559> codebase<00:21:11.200> it's<00:21:11.440> shockingly<00:21:12.159> 54 00:21:12.789 --> 00:21:12.799 align:start position:0% this is the codebase it's shockingly 54 00:21:12.799 --> 00:21:16.549 align:start position:0% this is the codebase it's shockingly 54 lines<00:21:13.200> long<00:21:13.679> this<00:21:13.919> includes<00:21:14.400> the<00:21:14.960> inline<00:21:15.440> html 00:21:16.549 --> 00:21:16.559 align:start position:0% lines long this includes the inline html 00:21:16.559 --> 00:21:18.070 align:start position:0% lines long this includes the inline html the<00:21:16.799> uh<00:21:17.280> everything<00:21:17.600> to<00:21:17.760> deal<00:21:17.919> with<00:21:18.000> the 00:21:18.070 --> 00:21:18.080 align:start position:0% the uh everything to deal with the 00:21:18.080 --> 00:21:19.110 align:start position:0% the uh everything to deal with the database 00:21:19.110 --> 00:21:19.120 align:start position:0% database 00:21:19.120 --> 00:21:23.669 align:start position:0% database uh<00:21:19.360> the<00:21:19.520> form<00:21:19.840> processing<00:21:20.320> is<00:21:20.400> here<00:21:20.640> too 00:21:23.669 --> 00:21:23.679 align:start position:0% 00:21:23.679 --> 00:21:25.270 align:start position:0% i<00:21:23.840> also<00:21:24.080> put<00:21:24.240> in<00:21:24.320> something<00:21:24.640> so<00:21:24.799> if<00:21:24.960> you<00:21:25.039> type 00:21:25.270 --> 00:21:25.280 align:start position:0% i also put in something so if you type 00:21:25.280 --> 00:21:27.270 align:start position:0% i also put in something so if you type in<00:21:25.440> test<00:21:25.919> it<00:21:26.000> doesn't<00:21:26.320> actually<00:21:26.640> store<00:21:26.960> it<00:21:27.120> so 00:21:27.270 --> 00:21:27.280 align:start position:0% in test it doesn't actually store it so 00:21:27.280 --> 00:21:28.789 align:start position:0% in test it doesn't actually store it so i<00:21:27.360> can<00:21:27.600> test<00:21:27.840> the<00:21:28.000> infrastructure<00:21:28.480> just<00:21:28.640> see 00:21:28.789 --> 00:21:28.799 align:start position:0% i can test the infrastructure just see 00:21:28.799 --> 00:21:32.230 align:start position:0% i can test the infrastructure just see if<00:21:28.880> things<00:21:29.120> are<00:21:29.200> working<00:21:30.240> and<00:21:31.039> yeah<00:21:31.840> and<00:21:32.080> it's 00:21:32.230 --> 00:21:32.240 align:start position:0% if things are working and yeah and it's 00:21:32.240 --> 00:21:36.710 align:start position:0% if things are working and yeah and it's basically<00:21:32.720> a<00:21:33.039> quick<00:21:33.200> little<00:21:33.440> jetty<00:21:33.760> app 00:21:36.710 --> 00:21:36.720 align:start position:0% 00:21:36.720 --> 00:21:38.870 align:start position:0% the<00:21:36.880> moral<00:21:37.120> of<00:21:37.200> the<00:21:37.280> story<00:21:37.679> is<00:21:37.840> that 00:21:38.870 --> 00:21:38.880 align:start position:0% the moral of the story is that 00:21:38.880 --> 00:21:40.630 align:start position:0% the moral of the story is that the<00:21:39.039> use<00:21:39.280> of<00:21:39.360> simple<00:21:39.600> services<00:21:40.080> really<00:21:40.320> allows 00:21:40.630 --> 00:21:40.640 align:start position:0% the use of simple services really allows 00:21:40.640 --> 00:21:42.549 align:start position:0% the use of simple services really allows you<00:21:40.960> a<00:21:41.039> lot<00:21:41.200> of<00:21:41.280> flexibility<00:21:42.159> especially<00:21:42.480> when 00:21:42.549 --> 00:21:42.559 align:start position:0% you a lot of flexibility especially when 00:21:42.559 --> 00:21:44.950 align:start position:0% you a lot of flexibility especially when it<00:21:42.640> comes<00:21:42.799> to<00:21:42.960> management<00:21:44.159> and<00:21:44.240> total<00:21:44.559> cost<00:21:44.799> of 00:21:44.950 --> 00:21:44.960 align:start position:0% it comes to management and total cost of 00:21:44.960 --> 00:21:46.870 align:start position:0% it comes to management and total cost of ownership<00:21:45.679> you<00:21:45.760> know<00:21:45.919> it<00:21:46.240> seriously<00:21:46.559> matters 00:21:46.870 --> 00:21:46.880 align:start position:0% ownership you know it seriously matters 00:21:46.880 --> 00:21:49.350 align:start position:0% ownership you know it seriously matters for<00:21:47.039> me<00:21:47.600> i'd<00:21:47.840> much<00:21:48.080> rather<00:21:48.400> have 00:21:49.350 --> 00:21:49.360 align:start position:0% for me i'd much rather have 00:21:49.360 --> 00:21:51.110 align:start position:0% for me i'd much rather have just<00:21:49.600> a<00:21:49.679> few 00:21:51.110 --> 00:21:51.120 align:start position:0% just a few 00:21:51.120 --> 00:21:53.430 align:start position:0% just a few deal<00:21:51.360> with<00:21:51.440> a<00:21:51.520> few<00:21:51.760> servers 00:21:53.430 --> 00:21:53.440 align:start position:0% deal with a few servers 00:21:53.440 --> 00:21:55.270 align:start position:0% deal with a few servers than<00:21:53.600> hundreds<00:21:53.919> of<00:21:54.000> servers<00:21:54.559> and<00:21:54.799> especially 00:21:55.270 --> 00:21:55.280 align:start position:0% than hundreds of servers and especially 00:21:55.280 --> 00:21:56.710 align:start position:0% than hundreds of servers and especially when<00:21:55.679> we<00:21:55.840> have 00:21:56.710 --> 00:21:56.720 align:start position:0% when we have 00:21:56.720 --> 00:21:58.630 align:start position:0% when we have clients<00:21:57.039> with<00:21:57.200> small<00:21:57.520> needs<00:21:58.080> you<00:21:58.159> know<00:21:58.400> that 00:21:58.630 --> 00:21:58.640 align:start position:0% clients with small needs you know that 00:21:58.640 --> 00:22:00.870 align:start position:0% clients with small needs you know that might<00:21:58.799> necessarily<00:21:59.360> need<00:21:59.520> us<00:21:59.760> need<00:22:00.000> a<00:22:00.080> server 00:22:00.870 --> 00:22:00.880 align:start position:0% might necessarily need us need a server 00:22:00.880 --> 00:22:02.390 align:start position:0% might necessarily need us need a server um 00:22:02.390 --> 00:22:02.400 align:start position:0% um 00:22:02.400 --> 00:22:04.070 align:start position:0% um that<00:22:02.640> that's<00:22:02.880> typically<00:22:03.360> the<00:22:03.600> the<00:22:03.760> problem 00:22:04.070 --> 00:22:04.080 align:start position:0% that that's typically the the problem 00:22:04.080 --> 00:22:05.590 align:start position:0% that that's typically the the problem people<00:22:04.320> walk<00:22:04.480> in<00:22:04.559> the<00:22:04.720> door<00:22:04.880> say<00:22:05.039> we<00:22:05.200> need<00:22:05.360> 50 00:22:05.590 --> 00:22:05.600 align:start position:0% people walk in the door say we need 50 00:22:05.600 --> 00:22:07.350 align:start position:0% people walk in the door say we need 50 servers<00:22:06.000> usually<00:22:06.240> they<00:22:06.400> need<00:22:06.559> one<00:22:06.960> we<00:22:07.120> need<00:22:07.280> a 00:22:07.350 --> 00:22:07.360 align:start position:0% servers usually they need one we need a 00:22:07.360 --> 00:22:10.230 align:start position:0% servers usually they need one we need a server<00:22:07.679> sometimes<00:22:08.000> they<00:22:08.080> don't<00:22:08.240> need<00:22:08.480> any 00:22:10.230 --> 00:22:10.240 align:start position:0% server sometimes they don't need any 00:22:10.240 --> 00:22:12.710 align:start position:0% server sometimes they don't need any this<00:22:10.400> is<00:22:10.480> where<00:22:10.640> heroku<00:22:11.039> comes<00:22:11.280> in<00:22:11.679> and<00:22:12.320> yeah 00:22:12.710 --> 00:22:12.720 align:start position:0% this is where heroku comes in and yeah 00:22:12.720 --> 00:22:15.909 align:start position:0% this is where heroku comes in and yeah it<00:22:12.799> really<00:22:13.039> does<00:22:13.200> make<00:22:13.360> me<00:22:13.520> very<00:22:13.760> happy 00:22:15.909 --> 00:22:15.919 align:start position:0% it really does make me very happy 00:22:15.919 --> 00:22:22.230 align:start position:0% it really does make me very happy thank<00:22:16.080> you 00:22:22.230 --> 00:22:22.240 align:start position:0% 00:22:22.240 --> 00:22:25.190 align:start position:0% all<00:22:22.400> right<00:22:22.559> so<00:22:22.880> uh 00:22:25.190 --> 00:22:25.200 align:start position:0% all right so uh 00:22:25.200 --> 00:22:27.669 align:start position:0% all right so uh yeah<00:22:25.919> thank<00:22:26.080> you 00:22:27.669 --> 00:22:27.679 align:start position:0% yeah thank you 00:22:27.679 --> 00:22:28.950 align:start position:0% yeah thank you um 00:22:28.950 --> 00:22:28.960 align:start position:0% um 00:22:28.960 --> 00:22:30.789 align:start position:0% um yeah<00:22:29.200> so<00:22:29.440> i<00:22:29.679> i<00:22:29.760> have<00:22:29.919> a<00:22:30.000> raspberry<00:22:30.400> pi<00:22:30.640> in<00:22:30.720> my 00:22:30.789 --> 00:22:30.799 align:start position:0% yeah so i i have a raspberry pi in my 00:22:30.799 --> 00:22:32.390 align:start position:0% yeah so i i have a raspberry pi in my bag<00:22:31.039> they're<00:22:31.200> really<00:22:31.440> cool<00:22:31.840> uh<00:22:32.080> the<00:22:32.159> one<00:22:32.320> i 00:22:32.390 --> 00:22:32.400 align:start position:0% bag they're really cool uh the one i 00:22:32.400 --> 00:22:34.070 align:start position:0% bag they're really cool uh the one i have<00:22:32.559> in<00:22:32.640> my<00:22:32.799> bag<00:22:33.039> is<00:22:33.120> running<00:22:33.360> closure<00:22:33.840> it's 00:22:34.070 --> 00:22:34.080 align:start position:0% have in my bag is running closure it's 00:22:34.080 --> 00:22:35.669 align:start position:0% have in my bag is running closure it's it's<00:22:34.400> great<00:22:34.799> but<00:22:34.960> i'm<00:22:35.039> not<00:22:35.200> gonna<00:22:35.280> talk<00:22:35.440> about 00:22:35.669 --> 00:22:35.679 align:start position:0% it's great but i'm not gonna talk about 00:22:35.679 --> 00:22:37.110 align:start position:0% it's great but i'm not gonna talk about it<00:22:36.240> uh 00:22:37.110 --> 00:22:37.120 align:start position:0% it uh 00:22:37.120 --> 00:22:38.390 align:start position:0% it uh so<00:22:37.280> if<00:22:37.360> you<00:22:37.840> are<00:22:38.000> interested<00:22:38.240> in<00:22:38.320> the 00:22:38.390 --> 00:22:38.400 align:start position:0% so if you are interested in the 00:22:38.400 --> 00:22:41.190 align:start position:0% so if you are interested in the raspberry<00:22:38.799> pi<00:22:38.960> i<00:22:39.039> want<00:22:39.120> to<00:22:39.200> see<00:22:39.440> one<00:22:40.000> find<00:22:40.240> me 00:22:41.190 --> 00:22:41.200 align:start position:0% raspberry pi i want to see one find me 00:22:41.200 --> 00:22:42.470 align:start position:0% raspberry pi i want to see one find me i<00:22:41.360> kind<00:22:41.520> of<00:22:41.600> switched<00:22:41.840> topics<00:22:42.159> at<00:22:42.240> the<00:22:42.320> last 00:22:42.470 --> 00:22:42.480 align:start position:0% i kind of switched topics at the last 00:22:42.480 --> 00:22:43.909 align:start position:0% i kind of switched topics at the last minute<00:22:42.799> just<00:22:42.960> because<00:22:43.280> this<00:22:43.440> is<00:22:43.600> where<00:22:43.760> my 00:22:43.909 --> 00:22:43.919 align:start position:0% minute just because this is where my 00:22:43.919 --> 00:22:45.350 align:start position:0% minute just because this is where my head<00:22:44.159> is<00:22:44.320> right<00:22:44.480> now<00:22:44.720> and<00:22:44.799> i'm<00:22:44.960> like<00:22:45.120> fully 00:22:45.350 --> 00:22:45.360 align:start position:0% head is right now and i'm like fully 00:22:45.360 --> 00:22:47.990 align:start position:0% head is right now and i'm like fully loaded<00:22:45.679> on<00:22:45.840> frp<00:22:46.880> and<00:22:47.039> i<00:22:47.360> have<00:22:47.520> reached<00:22:47.760> some 00:22:47.990 --> 00:22:48.000 align:start position:0% loaded on frp and i have reached some 00:22:48.000 --> 00:22:50.789 align:start position:0% loaded on frp and i have reached some crystal<00:22:48.480> of<00:22:48.720> understanding<00:22:49.280> that<00:22:49.360> i<00:22:49.440> wish<00:22:49.679> to 00:22:50.789 --> 00:22:50.799 align:start position:0% crystal of understanding that i wish to 00:22:50.799 --> 00:22:52.230 align:start position:0% crystal of understanding that i wish to convey 00:22:52.230 --> 00:22:52.240 align:start position:0% convey 00:22:52.240 --> 00:22:54.630 align:start position:0% convey so<00:22:52.880> functional<00:22:53.280> reactive<00:22:53.679> programming<00:22:54.320> um 00:22:54.630 --> 00:22:54.640 align:start position:0% so functional reactive programming um 00:22:54.640 --> 00:22:57.190 align:start position:0% so functional reactive programming um it's<00:22:54.799> a<00:22:54.880> thing<00:22:55.600> i<00:22:55.840> work<00:22:56.000> at<00:22:56.159> a<00:22:56.240> place<00:22:56.480> called 00:22:57.190 --> 00:22:57.200 align:start position:0% it's a thing i work at a place called 00:22:57.200 --> 00:22:58.549 align:start position:0% it's a thing i work at a place called lonocloud<00:22:57.760> where<00:22:57.919> i've<00:22:58.080> been<00:22:58.159> doing<00:22:58.320> a<00:22:58.320> lot<00:22:58.480> of 00:22:58.549 --> 00:22:58.559 align:start position:0% lonocloud where i've been doing a lot of 00:22:58.559 --> 00:23:00.149 align:start position:0% lonocloud where i've been doing a lot of closure<00:22:58.880> script<00:22:59.280> recently<00:22:59.679> to<00:22:59.840> write 00:23:00.149 --> 00:23:00.159 align:start position:0% closure script recently to write 00:23:00.159 --> 00:23:02.950 align:start position:0% closure script recently to write web-based<00:23:01.039> visualization<00:23:01.679> tools<00:23:02.080> for 00:23:02.950 --> 00:23:02.960 align:start position:0% web-based visualization tools for 00:23:02.960 --> 00:23:03.750 align:start position:0% web-based visualization tools for uh 00:23:03.750 --> 00:23:03.760 align:start position:0% uh 00:23:03.760 --> 00:23:06.390 align:start position:0% uh various<00:23:04.159> cloud<00:23:04.640> tools<00:23:05.039> that<00:23:05.360> we<00:23:05.600> operate<00:23:06.080> so<00:23:06.320> i 00:23:06.390 --> 00:23:06.400 align:start position:0% various cloud tools that we operate so i 00:23:06.400 --> 00:23:07.990 align:start position:0% various cloud tools that we operate so i once<00:23:06.559> again<00:23:06.799> found<00:23:07.039> myself<00:23:07.360> in<00:23:07.440> the<00:23:07.520> world<00:23:07.760> of 00:23:07.990 --> 00:23:08.000 align:start position:0% once again found myself in the world of 00:23:08.000 --> 00:23:09.830 align:start position:0% once again found myself in the world of of<00:23:08.240> web<00:23:08.720> programming 00:23:09.830 --> 00:23:09.840 align:start position:0% of web programming 00:23:09.840 --> 00:23:12.630 align:start position:0% of web programming and<00:23:10.320> uh<00:23:10.960> callback<00:23:11.520> uh 00:23:12.630 --> 00:23:12.640 align:start position:0% and uh callback uh 00:23:12.640 --> 00:23:14.070 align:start position:0% and uh callback uh hell 00:23:14.070 --> 00:23:14.080 align:start position:0% hell 00:23:14.080 --> 00:23:17.350 align:start position:0% hell and<00:23:14.480> um<00:23:15.280> i'd<00:23:15.440> heard<00:23:15.679> things<00:23:15.840> about<00:23:16.080> frp<00:23:16.640> and<00:23:17.039> uh 00:23:17.350 --> 00:23:17.360 align:start position:0% and um i'd heard things about frp and uh 00:23:17.360 --> 00:23:19.270 align:start position:0% and um i'd heard things about frp and uh over<00:23:17.520> the<00:23:17.600> past<00:23:17.840> few<00:23:18.000> weeks<00:23:18.400> um<00:23:18.880> with<00:23:19.039> the<00:23:19.120> help 00:23:19.270 --> 00:23:19.280 align:start position:0% over the past few weeks um with the help 00:23:19.280 --> 00:23:21.350 align:start position:0% over the past few weeks um with the help of<00:23:19.360> my<00:23:19.520> co-workers<00:23:20.000> and<00:23:20.400> a<00:23:20.480> few<00:23:20.640> friends<00:23:21.280> i 00:23:21.350 --> 00:23:21.360 align:start position:0% of my co-workers and a few friends i 00:23:21.360 --> 00:23:22.549 align:start position:0% of my co-workers and a few friends i think<00:23:21.520> i've<00:23:21.840> reached<00:23:22.080> light<00:23:22.240> at<00:23:22.320> the<00:23:22.400> end<00:23:22.480> of 00:23:22.549 --> 00:23:22.559 align:start position:0% think i've reached light at the end of 00:23:22.559 --> 00:23:23.830 align:start position:0% think i've reached light at the end of the<00:23:22.640> tunnel<00:23:22.880> so<00:23:23.120> i'm<00:23:23.200> going<00:23:23.280> to<00:23:23.440> try<00:23:23.679> this 00:23:23.830 --> 00:23:23.840 align:start position:0% the tunnel so i'm going to try this 00:23:23.840 --> 00:23:25.510 align:start position:0% the tunnel so i'm going to try this explanation<00:23:24.400> on<00:23:24.480> you<00:23:24.640> guys 00:23:25.510 --> 00:23:25.520 align:start position:0% explanation on you guys 00:23:25.520 --> 00:23:27.029 align:start position:0% explanation on you guys um 00:23:27.029 --> 00:23:27.039 align:start position:0% um 00:23:27.039 --> 00:23:28.310 align:start position:0% um if<00:23:27.200> i'm<00:23:27.280> not<00:23:27.440> doing<00:23:27.600> a<00:23:27.679> good<00:23:27.840> job<00:23:28.000> maybe<00:23:28.240> i'll 00:23:28.310 --> 00:23:28.320 align:start position:0% if i'm not doing a good job maybe i'll 00:23:28.320 --> 00:23:29.430 align:start position:0% if i'm not doing a good job maybe i'll just<00:23:28.480> switch<00:23:28.640> back<00:23:28.799> over<00:23:28.960> to<00:23:29.120> talking<00:23:29.360> about 00:23:29.430 --> 00:23:29.440 align:start position:0% just switch back over to talking about 00:23:29.440 --> 00:23:31.669 align:start position:0% just switch back over to talking about raspberry<00:23:29.840> pi<00:23:30.240> but<00:23:30.400> here<00:23:30.559> we<00:23:30.640> go 00:23:31.669 --> 00:23:31.679 align:start position:0% raspberry pi but here we go 00:23:31.679 --> 00:23:33.350 align:start position:0% raspberry pi but here we go so<00:23:31.840> what<00:23:32.000> is<00:23:32.159> frp 00:23:33.350 --> 00:23:33.360 align:start position:0% so what is frp 00:23:33.360 --> 00:23:34.470 align:start position:0% so what is frp it<00:23:33.520> is<00:23:33.679> a 00:23:34.470 --> 00:23:34.480 align:start position:0% it is a 00:23:34.480 --> 00:23:36.310 align:start position:0% it is a fundamentally<00:23:35.039> a<00:23:35.200> programming<00:23:35.679> paradigm 00:23:36.310 --> 00:23:36.320 align:start position:0% fundamentally a programming paradigm 00:23:36.320 --> 00:23:38.149 align:start position:0% fundamentally a programming paradigm what<00:23:36.480> is<00:23:36.640> a<00:23:36.720> paradigm<00:23:37.280> well<00:23:37.520> a<00:23:37.600> paradigm<00:23:38.080> is 00:23:38.149 --> 00:23:38.159 align:start position:0% what is a paradigm well a paradigm is 00:23:38.159 --> 00:23:39.909 align:start position:0% what is a paradigm well a paradigm is usually<00:23:38.480> delivered<00:23:38.799> to<00:23:38.960> us<00:23:39.200> in<00:23:39.280> the<00:23:39.360> form<00:23:39.679> of 00:23:39.909 --> 00:23:39.919 align:start position:0% usually delivered to us in the form of 00:23:39.919 --> 00:23:42.310 align:start position:0% usually delivered to us in the form of an<00:23:40.080> implementation<00:23:41.200> which<00:23:41.440> is<00:23:41.520> either<00:23:42.080> some 00:23:42.310 --> 00:23:42.320 align:start position:0% an implementation which is either some 00:23:42.320 --> 00:23:44.070 align:start position:0% an implementation which is either some language<00:23:42.799> or<00:23:42.960> some<00:23:43.120> library<00:23:43.600> or<00:23:43.760> some 00:23:44.070 --> 00:23:44.080 align:start position:0% language or some library or some 00:23:44.080 --> 00:23:47.029 align:start position:0% language or some library or some combination<00:23:44.640> of<00:23:45.280> language<00:23:45.679> and<00:23:45.840> library 00:23:47.029 --> 00:23:47.039 align:start position:0% combination of language and library 00:23:47.039 --> 00:23:48.549 align:start position:0% combination of language and library if<00:23:47.200> you<00:23:47.280> look<00:23:47.440> at<00:23:47.520> all<00:23:47.600> the<00:23:47.760> frp<00:23:48.159> stuff<00:23:48.320> that's 00:23:48.549 --> 00:23:48.559 align:start position:0% if you look at all the frp stuff that's 00:23:48.559 --> 00:23:50.390 align:start position:0% if you look at all the frp stuff that's out<00:23:48.640> there<00:23:48.799> to<00:23:48.960> include<00:23:49.280> the<00:23:49.440> papers<00:23:50.240> you<00:23:50.320> know 00:23:50.390 --> 00:23:50.400 align:start position:0% out there to include the papers you know 00:23:50.400 --> 00:23:51.510 align:start position:0% out there to include the papers you know some<00:23:50.559> of<00:23:50.640> which<00:23:50.799> i've<00:23:50.960> skimmed<00:23:51.200> in<00:23:51.360> all<00:23:51.440> the 00:23:51.510 --> 00:23:51.520 align:start position:0% some of which i've skimmed in all the 00:23:51.520 --> 00:23:52.870 align:start position:0% some of which i've skimmed in all the various<00:23:51.840> implementations<00:23:52.480> whether<00:23:52.720> they're 00:23:52.870 --> 00:23:52.880 align:start position:0% various implementations whether they're 00:23:52.880 --> 00:23:55.430 align:start position:0% various implementations whether they're languages<00:23:53.360> libraries<00:23:53.760> or<00:23:53.919> frameworks 00:23:55.430 --> 00:23:55.440 align:start position:0% languages libraries or frameworks 00:23:55.440 --> 00:23:57.909 align:start position:0% languages libraries or frameworks two<00:23:55.760> key<00:23:56.000> ideas<00:23:56.480> stick<00:23:56.799> out<00:23:57.280> the<00:23:57.440> first<00:23:57.760> is<00:23:57.840> the 00:23:57.909 --> 00:23:57.919 align:start position:0% two key ideas stick out the first is the 00:23:57.919 --> 00:24:00.630 align:start position:0% two key ideas stick out the first is the notion<00:23:58.240> of<00:23:58.320> a<00:23:58.480> time<00:23:58.960> varying<00:23:59.520> value 00:24:00.630 --> 00:24:00.640 align:start position:0% notion of a time varying value 00:24:00.640 --> 00:24:02.470 align:start position:0% notion of a time varying value and<00:24:00.880> i'm<00:24:01.120> using<00:24:01.280> terminology<00:24:01.919> from<00:24:02.320> my 00:24:02.470 --> 00:24:02.480 align:start position:0% and i'm using terminology from my 00:24:02.480 --> 00:24:03.830 align:start position:0% and i'm using terminology from my favorite<00:24:02.720> paper<00:24:02.960> which<00:24:03.120> is<00:24:03.200> the<00:24:03.360> flapjacks 00:24:03.830 --> 00:24:03.840 align:start position:0% favorite paper which is the flapjacks 00:24:03.840 --> 00:24:05.750 align:start position:0% favorite paper which is the flapjacks paper<00:24:04.159> but<00:24:04.799> they<00:24:04.960> talk<00:24:05.120> a<00:24:05.200> lot<00:24:05.360> about<00:24:05.520> time 00:24:05.750 --> 00:24:05.760 align:start position:0% paper but they talk a lot about time 00:24:05.760 --> 00:24:07.750 align:start position:0% paper but they talk a lot about time varying<00:24:06.159> values<00:24:06.880> which<00:24:07.120> one<00:24:07.280> way<00:24:07.440> to<00:24:07.600> think 00:24:07.750 --> 00:24:07.760 align:start position:0% varying values which one way to think 00:24:07.760 --> 00:24:09.669 align:start position:0% varying values which one way to think about<00:24:07.919> them<00:24:08.080> in<00:24:08.159> closure<00:24:08.559> terms<00:24:08.880> as 00:24:09.669 --> 00:24:09.679 align:start position:0% about them in closure terms as 00:24:09.679 --> 00:24:12.470 align:start position:0% about them in closure terms as is<00:24:09.919> as<00:24:10.240> reference<00:24:10.799> types 00:24:12.470 --> 00:24:12.480 align:start position:0% is as reference types 00:24:12.480 --> 00:24:13.830 align:start position:0% is as reference types however<00:24:13.039> in 00:24:13.830 --> 00:24:13.840 align:start position:0% however in 00:24:13.840 --> 00:24:15.830 align:start position:0% however in closure<00:24:14.400> if<00:24:14.559> you<00:24:14.640> want<00:24:14.799> to<00:24:14.960> know<00:24:15.120> the<00:24:15.200> value<00:24:15.600> of 00:24:15.830 --> 00:24:15.840 align:start position:0% closure if you want to know the value of 00:24:15.840 --> 00:24:17.430 align:start position:0% closure if you want to know the value of a<00:24:16.000> reference<00:24:16.320> type<00:24:16.559> you<00:24:16.799> you<00:24:16.960> are<00:24:17.120> the<00:24:17.200> one 00:24:17.430 --> 00:24:17.440 align:start position:0% a reference type you you are the one 00:24:17.440 --> 00:24:19.029 align:start position:0% a reference type you you are the one responsible<00:24:18.000> for<00:24:18.159> asking<00:24:18.480> the<00:24:18.559> question<00:24:18.960> the 00:24:19.029 --> 00:24:19.039 align:start position:0% responsible for asking the question the 00:24:19.039 --> 00:24:20.789 align:start position:0% responsible for asking the question the value<00:24:19.360> is<00:24:19.440> not<00:24:19.600> pushed<00:24:19.840> to<00:24:20.000> you<00:24:20.640> you 00:24:20.789 --> 00:24:20.799 align:start position:0% value is not pushed to you you 00:24:20.799 --> 00:24:22.630 align:start position:0% value is not pushed to you you dereference<00:24:21.440> it<00:24:21.520> with<00:24:21.679> a<00:24:21.840> little<00:24:22.159> you<00:24:22.320> know<00:24:22.480> at 00:24:22.630 --> 00:24:22.640 align:start position:0% dereference it with a little you know at 00:24:22.640 --> 00:24:24.310 align:start position:0% dereference it with a little you know at symbol<00:24:23.039> reader<00:24:23.279> macro 00:24:24.310 --> 00:24:24.320 align:start position:0% symbol reader macro 00:24:24.320 --> 00:24:26.310 align:start position:0% symbol reader macro these<00:24:24.480> time<00:24:24.720> varying<00:24:25.120> values<00:24:25.520> are<00:24:25.840> reference 00:24:26.310 --> 00:24:26.320 align:start position:0% these time varying values are reference 00:24:26.320 --> 00:24:28.630 align:start position:0% these time varying values are reference types<00:24:26.640> the<00:24:26.960> value<00:24:27.360> of<00:24:27.679> which<00:24:28.080> changes<00:24:28.400> over 00:24:28.630 --> 00:24:28.640 align:start position:0% types the value of which changes over 00:24:28.640 --> 00:24:30.230 align:start position:0% types the value of which changes over time<00:24:28.799> but<00:24:28.960> that<00:24:29.120> value<00:24:29.520> is<00:24:29.679> conveyed<00:24:30.080> to 00:24:30.230 --> 00:24:30.240 align:start position:0% time but that value is conveyed to 00:24:30.240 --> 00:24:34.149 align:start position:0% time but that value is conveyed to consumers<00:24:31.200> as<00:24:31.360> a<00:24:31.520> stream<00:24:32.240> of<00:24:32.720> changes<00:24:33.600> so<00:24:33.919> time 00:24:34.149 --> 00:24:34.159 align:start position:0% consumers as a stream of changes so time 00:24:34.159 --> 00:24:36.549 align:start position:0% consumers as a stream of changes so time varying<00:24:34.400> values 00:24:36.549 --> 00:24:36.559 align:start position:0% varying values 00:24:36.559 --> 00:24:38.070 align:start position:0% varying values once<00:24:36.799> you<00:24:36.880> have<00:24:37.039> these<00:24:37.200> time<00:24:37.440> varying<00:24:37.679> values 00:24:38.070 --> 00:24:38.080 align:start position:0% once you have these time varying values 00:24:38.080 --> 00:24:39.830 align:start position:0% once you have these time varying values these<00:24:38.240> streams<00:24:38.720> of<00:24:38.799> changes<00:24:39.360> then<00:24:39.520> you<00:24:39.679> can 00:24:39.830 --> 00:24:39.840 align:start position:0% these streams of changes then you can 00:24:39.840 --> 00:24:41.990 align:start position:0% these streams of changes then you can work<00:24:40.000> with<00:24:40.159> them<00:24:40.480> in<00:24:40.640> a<00:24:40.720> similar<00:24:41.120> way 00:24:41.990 --> 00:24:42.000 align:start position:0% work with them in a similar way 00:24:42.000 --> 00:24:42.950 align:start position:0% work with them in a similar way uh 00:24:42.950 --> 00:24:42.960 align:start position:0% uh 00:24:42.960 --> 00:24:44.710 align:start position:0% uh to<00:24:43.200> working<00:24:43.440> with<00:24:43.600> sequences<00:24:44.159> enclosure<00:24:44.559> with 00:24:44.710 --> 00:24:44.720 align:start position:0% to working with sequences enclosure with 00:24:44.720 --> 00:24:46.390 align:start position:0% to working with sequences enclosure with the<00:24:44.799> sequence<00:24:45.120> library<00:24:45.919> you<00:24:46.080> have<00:24:46.159> these 00:24:46.390 --> 00:24:46.400 align:start position:0% the sequence library you have these 00:24:46.400 --> 00:24:48.549 align:start position:0% the sequence library you have these streams<00:24:46.799> of<00:24:46.960> events<00:24:47.360> that<00:24:47.520> you<00:24:47.679> can<00:24:48.240> you<00:24:48.320> know 00:24:48.549 --> 00:24:48.559 align:start position:0% streams of events that you can you know 00:24:48.559 --> 00:24:51.110 align:start position:0% streams of events that you can you know compose<00:24:49.120> or<00:24:49.360> interleave<00:24:50.080> or<00:24:50.400> transpose<00:24:51.039> in 00:24:51.110 --> 00:24:51.120 align:start position:0% compose or interleave or transpose in 00:24:51.120 --> 00:24:52.230 align:start position:0% compose or interleave or transpose in the<00:24:51.200> same<00:24:51.360> way<00:24:51.520> we're<00:24:51.679> used<00:24:51.840> to<00:24:51.919> working<00:24:52.159> with 00:24:52.230 --> 00:24:52.240 align:start position:0% the same way we're used to working with 00:24:52.240 --> 00:24:54.230 align:start position:0% the same way we're used to working with sequences 00:24:54.230 --> 00:24:54.240 align:start position:0% sequences 00:24:54.240 --> 00:24:56.070 align:start position:0% sequences what<00:24:54.400> this<00:24:54.640> does<00:24:54.960> is<00:24:55.120> allow<00:24:55.360> you<00:24:55.520> to<00:24:55.679> program 00:24:56.070 --> 00:24:56.080 align:start position:0% what this does is allow you to program 00:24:56.080 --> 00:24:58.789 align:start position:0% what this does is allow you to program with<00:24:56.320> events<00:24:56.799> as<00:24:57.039> if<00:24:57.200> they<00:24:57.360> were<00:24:57.600> values 00:24:58.789 --> 00:24:58.799 align:start position:0% with events as if they were values 00:24:58.799 --> 00:25:00.070 align:start position:0% with events as if they were values one<00:24:58.960> of<00:24:59.039> the<00:24:59.200> other<00:24:59.360> themes<00:24:59.600> in<00:24:59.679> a<00:24:59.760> lot<00:24:59.840> of<00:24:59.919> the 00:25:00.070 --> 00:25:00.080 align:start position:0% one of the other themes in a lot of the 00:25:00.080 --> 00:25:01.830 align:start position:0% one of the other themes in a lot of the papers<00:25:00.480> is<00:25:00.640> this<00:25:00.880> point<00:25:01.120> that's<00:25:01.360> made<00:25:01.600> that 00:25:01.830 --> 00:25:01.840 align:start position:0% papers is this point that's made that 00:25:01.840 --> 00:25:03.350 align:start position:0% papers is this point that's made that whenever<00:25:02.159> you're<00:25:02.320> working<00:25:02.480> with<00:25:02.640> callbacks 00:25:03.350 --> 00:25:03.360 align:start position:0% whenever you're working with callbacks 00:25:03.360 --> 00:25:04.149 align:start position:0% whenever you're working with callbacks or 00:25:04.149 --> 00:25:04.159 align:start position:0% or 00:25:04.159 --> 00:25:06.149 align:start position:0% or watches 00:25:06.149 --> 00:25:06.159 align:start position:0% watches 00:25:06.159 --> 00:25:08.149 align:start position:0% watches you<00:25:06.320> don't<00:25:06.480> have<00:25:06.720> types<00:25:07.279> you<00:25:07.440> know<00:25:07.600> a<00:25:07.679> callback 00:25:08.149 --> 00:25:08.159 align:start position:0% you don't have types you know a callback 00:25:08.159 --> 00:25:09.909 align:start position:0% you don't have types you know a callback is<00:25:08.559> a<00:25:08.640> void<00:25:08.960> type 00:25:09.909 --> 00:25:09.919 align:start position:0% is a void type 00:25:09.919 --> 00:25:11.590 align:start position:0% is a void type for<00:25:10.080> those<00:25:10.320> of<00:25:10.400> us<00:25:10.559> enclosure 00:25:11.590 --> 00:25:11.600 align:start position:0% for those of us enclosure 00:25:11.600 --> 00:25:13.350 align:start position:0% for those of us enclosure it<00:25:11.679> means<00:25:11.919> we<00:25:12.000> don't<00:25:12.159> have<00:25:12.320> a<00:25:12.400> value 00:25:13.350 --> 00:25:13.360 align:start position:0% it means we don't have a value 00:25:13.360 --> 00:25:15.190 align:start position:0% it means we don't have a value it's<00:25:13.840> you<00:25:13.919> know<00:25:14.240> usually<00:25:14.559> the<00:25:14.720> function<00:25:15.039> that 00:25:15.190 --> 00:25:15.200 align:start position:0% it's you know usually the function that 00:25:15.200 --> 00:25:16.870 align:start position:0% it's you know usually the function that adds<00:25:15.440> a<00:25:15.520> callback<00:25:15.919> is<00:25:16.320> void<00:25:16.640> it<00:25:16.720> doesn't 00:25:16.870 --> 00:25:16.880 align:start position:0% adds a callback is void it doesn't 00:25:16.880 --> 00:25:18.710 align:start position:0% adds a callback is void it doesn't return<00:25:17.200> anything<00:25:17.520> and<00:25:17.679> of<00:25:17.760> course<00:25:18.320> callbacks 00:25:18.710 --> 00:25:18.720 align:start position:0% return anything and of course callbacks 00:25:18.720 --> 00:25:21.029 align:start position:0% return anything and of course callbacks are<00:25:18.799> not<00:25:18.960> values<00:25:19.360> so<00:25:20.000> what<00:25:20.159> this<00:25:20.400> allows<00:25:20.880> one 00:25:21.029 --> 00:25:21.039 align:start position:0% are not values so what this allows one 00:25:21.039 --> 00:25:23.029 align:start position:0% are not values so what this allows one to<00:25:21.200> do<00:25:21.600> is<00:25:21.840> work<00:25:22.080> with 00:25:23.029 --> 00:25:23.039 align:start position:0% to do is work with 00:25:23.039 --> 00:25:23.990 align:start position:0% to do is work with events 00:25:23.990 --> 00:25:24.000 align:start position:0% events 00:25:24.000 --> 00:25:25.909 align:start position:0% events as<00:25:24.240> streams<00:25:24.640> of<00:25:24.720> values<00:25:25.200> and<00:25:25.279> compose<00:25:25.760> in<00:25:25.840> the 00:25:25.909 --> 00:25:25.919 align:start position:0% as streams of values and compose in the 00:25:25.919 --> 00:25:27.669 align:start position:0% as streams of values and compose in the same<00:25:26.080> way<00:25:26.240> we<00:25:26.400> would<00:25:26.640> any<00:25:26.799> stream<00:25:27.120> of<00:25:27.520> any 00:25:27.669 --> 00:25:27.679 align:start position:0% same way we would any stream of any 00:25:27.679 --> 00:25:29.750 align:start position:0% same way we would any stream of any value 00:25:29.750 --> 00:25:29.760 align:start position:0% value 00:25:29.760 --> 00:25:31.350 align:start position:0% value so 00:25:31.350 --> 00:25:31.360 align:start position:0% so 00:25:31.360 --> 00:25:33.029 align:start position:0% so there's<00:25:31.600> tons<00:25:31.840> of<00:25:31.919> stuff<00:25:32.159> again<00:25:32.640> i'm<00:25:32.880> not 00:25:33.029 --> 00:25:33.039 align:start position:0% there's tons of stuff again i'm not 00:25:33.039 --> 00:25:34.549 align:start position:0% there's tons of stuff again i'm not going<00:25:33.120> to<00:25:33.200> go<00:25:33.360> over<00:25:33.520> it<00:25:34.000> all<00:25:34.159> of<00:25:34.240> the<00:25:34.320> stuff 00:25:34.549 --> 00:25:34.559 align:start position:0% going to go over it all of the stuff 00:25:34.559 --> 00:25:36.870 align:start position:0% going to go over it all of the stuff listed<00:25:34.880> except<00:25:35.120> for<00:25:35.279> flapjacks<00:25:35.919> is<00:25:36.080> either<00:25:36.720> on 00:25:36.870 --> 00:25:36.880 align:start position:0% listed except for flapjacks is either on 00:25:36.880 --> 00:25:38.549 align:start position:0% listed except for flapjacks is either on a<00:25:36.960> platform<00:25:37.440> i<00:25:37.520> can't<00:25:37.679> use<00:25:37.840> for<00:25:38.000> operational 00:25:38.549 --> 00:25:38.559 align:start position:0% a platform i can't use for operational 00:25:38.559 --> 00:25:40.630 align:start position:0% a platform i can't use for operational reasons<00:25:39.360> is<00:25:39.520> too<00:25:39.679> much 00:25:40.630 --> 00:25:40.640 align:start position:0% reasons is too much 00:25:40.640 --> 00:25:43.510 align:start position:0% reasons is too much is<00:25:40.799> too<00:25:41.039> little<00:25:42.159> or<00:25:42.400> just<00:25:42.559> sucks 00:25:43.510 --> 00:25:43.520 align:start position:0% is too little or just sucks 00:25:43.520 --> 00:25:45.909 align:start position:0% is too little or just sucks so<00:25:44.080> of<00:25:44.320> all<00:25:44.400> of<00:25:44.559> these<00:25:44.799> i<00:25:44.880> like<00:25:45.039> flapjacks<00:25:45.760> and 00:25:45.909 --> 00:25:45.919 align:start position:0% so of all of these i like flapjacks and 00:25:45.919 --> 00:25:48.390 align:start position:0% so of all of these i like flapjacks and that's<00:25:46.080> what<00:25:46.240> i'm<00:25:46.320> going<00:25:46.400> to<00:25:46.480> talk<00:25:46.640> about 00:25:48.390 --> 00:25:48.400 align:start position:0% that's what i'm going to talk about 00:25:48.400 --> 00:25:50.310 align:start position:0% that's what i'm going to talk about what<00:25:48.559> does<00:25:48.640> slapjacks<00:25:49.200> give<00:25:49.440> us 00:25:50.310 --> 00:25:50.320 align:start position:0% what does slapjacks give us 00:25:50.320 --> 00:25:52.870 align:start position:0% what does slapjacks give us um<00:25:50.880> so<00:25:51.200> a<00:25:51.440> lot<00:25:51.520> of<00:25:51.600> the<00:25:51.760> frp<00:25:52.159> solutions<00:25:52.640> claim 00:25:52.870 --> 00:25:52.880 align:start position:0% um so a lot of the frp solutions claim 00:25:52.880 --> 00:25:54.549 align:start position:0% um so a lot of the frp solutions claim to<00:25:52.960> give<00:25:53.039> you<00:25:53.120> all<00:25:53.279> kinds<00:25:53.440> of<00:25:53.600> stuff 00:25:54.549 --> 00:25:54.559 align:start position:0% to give you all kinds of stuff 00:25:54.559 --> 00:25:56.549 align:start position:0% to give you all kinds of stuff to<00:25:54.960> you<00:25:55.120> know<00:25:55.520> that<00:25:55.679> help<00:25:55.919> you<00:25:56.080> solve<00:25:56.480> all 00:25:56.549 --> 00:25:56.559 align:start position:0% to you know that help you solve all 00:25:56.559 --> 00:25:58.149 align:start position:0% to you know that help you solve all kinds<00:25:56.799> of<00:25:56.880> things<00:25:57.120> in<00:25:57.279> in<00:25:57.440> the<00:25:57.520> domain<00:25:58.080> you 00:25:58.149 --> 00:25:58.159 align:start position:0% kinds of things in in the domain you 00:25:58.159 --> 00:26:00.230 align:start position:0% kinds of things in in the domain you know<00:25:58.799> this<00:25:59.039> is<00:25:59.200> this<00:25:59.440> is<00:25:59.520> how<00:25:59.679> you<00:25:59.840> build<00:26:00.000> web 00:26:00.230 --> 00:26:00.240 align:start position:0% know this is this is how you build web 00:26:00.240 --> 00:26:01.750 align:start position:0% know this is this is how you build web apps<00:26:00.480> now<00:26:00.640> we<00:26:00.799> give<00:26:00.880> you<00:26:01.120> uh<00:26:01.279> templating 00:26:01.750 --> 00:26:01.760 align:start position:0% apps now we give you uh templating 00:26:01.760 --> 00:26:03.830 align:start position:0% apps now we give you uh templating language<00:26:02.240> language<00:26:02.720> and 00:26:03.830 --> 00:26:03.840 align:start position:0% language language and 00:26:03.840 --> 00:26:05.110 align:start position:0% language language and graphics<00:26:04.320> stuff 00:26:05.110 --> 00:26:05.120 align:start position:0% graphics stuff 00:26:05.120 --> 00:26:06.789 align:start position:0% graphics stuff flapjacks<00:26:05.679> just<00:26:05.840> gives<00:26:06.080> us<00:26:06.240> one<00:26:06.400> thing<00:26:06.559> which 00:26:06.789 --> 00:26:06.799 align:start position:0% flapjacks just gives us one thing which 00:26:06.799 --> 00:26:08.789 align:start position:0% flapjacks just gives us one thing which is<00:26:06.960> this<00:26:07.120> ability<00:26:07.520> to<00:26:07.679> turn<00:26:07.919> events<00:26:08.480> into 00:26:08.789 --> 00:26:08.799 align:start position:0% is this ability to turn events into 00:26:08.799 --> 00:26:10.070 align:start position:0% is this ability to turn events into streams<00:26:09.120> of<00:26:09.200> events<00:26:09.520> so<00:26:09.679> that<00:26:09.760> we<00:26:09.840> can<00:26:09.919> work 00:26:10.070 --> 00:26:10.080 align:start position:0% streams of events so that we can work 00:26:10.080 --> 00:26:11.510 align:start position:0% streams of events so that we can work with<00:26:10.240> them<00:26:10.400> like<00:26:10.559> values 00:26:11.510 --> 00:26:11.520 align:start position:0% with them like values 00:26:11.520 --> 00:26:13.510 align:start position:0% with them like values and<00:26:11.679> in<00:26:11.840> a<00:26:11.919> browser<00:26:12.559> there<00:26:12.799> are<00:26:13.200> a<00:26:13.279> couple 00:26:13.510 --> 00:26:13.520 align:start position:0% and in a browser there are a couple 00:26:13.520 --> 00:26:14.710 align:start position:0% and in a browser there are a couple different<00:26:13.760> flavors<00:26:14.080> of<00:26:14.159> event<00:26:14.480> there<00:26:14.559> are 00:26:14.710 --> 00:26:14.720 align:start position:0% different flavors of event there are 00:26:14.720 --> 00:26:16.310 align:start position:0% different flavors of event there are user<00:26:15.039> events<00:26:15.440> you<00:26:15.520> know<00:26:15.679> bob<00:26:16.000> click<00:26:16.240> the 00:26:16.310 --> 00:26:16.320 align:start position:0% user events you know bob click the 00:26:16.320 --> 00:26:17.909 align:start position:0% user events you know bob click the button<00:26:17.039> there<00:26:17.120> are<00:26:17.279> events<00:26:17.520> that<00:26:17.600> come<00:26:17.760> from 00:26:17.909 --> 00:26:17.919 align:start position:0% button there are events that come from 00:26:17.919 --> 00:26:19.510 align:start position:0% button there are events that come from the<00:26:18.080> dom<00:26:18.400> that<00:26:18.559> you<00:26:18.720> may<00:26:18.880> or<00:26:19.039> may<00:26:19.200> not<00:26:19.360> have 00:26:19.510 --> 00:26:19.520 align:start position:0% the dom that you may or may not have 00:26:19.520 --> 00:26:21.590 align:start position:0% the dom that you may or may not have initiated<00:26:20.000> like<00:26:20.480> success<00:26:20.880> of<00:26:21.039> an<00:26:21.200> ajax 00:26:21.590 --> 00:26:21.600 align:start position:0% initiated like success of an ajax 00:26:21.600 --> 00:26:22.630 align:start position:0% initiated like success of an ajax callback 00:26:22.630 --> 00:26:22.640 align:start position:0% callback 00:26:22.640 --> 00:26:24.470 align:start position:0% callback and<00:26:22.880> in<00:26:23.039> a<00:26:23.039> lot<00:26:23.200> of<00:26:23.279> systems<00:26:23.840> with<00:26:24.000> events<00:26:24.320> you 00:26:24.470 --> 00:26:24.480 align:start position:0% and in a lot of systems with events you 00:26:24.480 --> 00:26:25.990 align:start position:0% and in a lot of systems with events you have<00:26:24.559> scheduled<00:26:24.960> or<00:26:25.039> periodic<00:26:25.520> events<00:26:25.840> like 00:26:25.990 --> 00:26:26.000 align:start position:0% have scheduled or periodic events like 00:26:26.000 --> 00:26:27.750 align:start position:0% have scheduled or periodic events like heartbeats<00:26:26.559> or<00:26:26.799> refresh<00:26:27.200> the<00:26:27.279> buddy<00:26:27.520> list 00:26:27.750 --> 00:26:27.760 align:start position:0% heartbeats or refresh the buddy list 00:26:27.760 --> 00:26:30.230 align:start position:0% heartbeats or refresh the buddy list every<00:26:28.000> minute 00:26:30.230 --> 00:26:30.240 align:start position:0% every minute 00:26:30.240 --> 00:26:31.669 align:start position:0% every minute flapjacks 00:26:31.669 --> 00:26:31.679 align:start position:0% flapjacks 00:26:31.679 --> 00:26:32.870 align:start position:0% flapjacks gives<00:26:31.919> us<00:26:32.000> tools<00:26:32.240> for<00:26:32.400> working<00:26:32.640> with<00:26:32.799> all 00:26:32.870 --> 00:26:32.880 align:start position:0% gives us tools for working with all 00:26:32.880 --> 00:26:34.630 align:start position:0% gives us tools for working with all those<00:26:33.039> kinds<00:26:33.200> of<00:26:33.360> events 00:26:34.630 --> 00:26:34.640 align:start position:0% those kinds of events 00:26:34.640 --> 00:26:36.230 align:start position:0% those kinds of events and<00:26:34.799> then<00:26:34.960> again<00:26:35.120> once<00:26:35.279> your<00:26:35.440> streams<00:26:36.000> there's 00:26:36.230 --> 00:26:36.240 align:start position:0% and then again once your streams there's 00:26:36.240 --> 00:26:37.990 align:start position:0% and then again once your streams there's this<00:26:36.480> general<00:26:36.799> notion<00:26:37.120> of<00:26:37.200> consumption<00:26:37.840> and 00:26:37.990 --> 00:26:38.000 align:start position:0% this general notion of consumption and 00:26:38.000 --> 00:26:39.830 align:start position:0% this general notion of consumption and generation<00:26:38.640> and<00:26:38.799> fusion<00:26:39.200> and<00:26:39.279> filtering<00:26:39.760> and 00:26:39.830 --> 00:26:39.840 align:start position:0% generation and fusion and filtering and 00:26:39.840 --> 00:26:40.950 align:start position:0% generation and fusion and filtering and so<00:26:40.080> on 00:26:40.950 --> 00:26:40.960 align:start position:0% so on 00:26:40.960 --> 00:26:42.149 align:start position:0% so on um 00:26:42.149 --> 00:26:42.159 align:start position:0% um 00:26:42.159 --> 00:26:44.630 align:start position:0% um what<00:26:42.320> flat<00:26:42.640> jacks<00:26:43.039> gives<00:26:43.279> you<00:26:43.679> is<00:26:44.080> a<00:26:44.240> general 00:26:44.630 --> 00:26:44.640 align:start position:0% what flat jacks gives you is a general 00:26:44.640 --> 00:26:46.630 align:start position:0% what flat jacks gives you is a general set<00:26:44.799> of<00:26:44.880> tools<00:26:45.200> for<00:26:45.520> for<00:26:45.679> doing<00:26:45.919> what<00:26:46.400> a<00:26:46.480> lot<00:26:46.559> of 00:26:46.630 --> 00:26:46.640 align:start position:0% set of tools for for doing what a lot of 00:26:46.640 --> 00:26:48.390 align:start position:0% set of tools for for doing what a lot of people<00:26:46.799> who<00:26:46.960> work<00:26:47.200> with<00:26:47.279> events 00:26:48.390 --> 00:26:48.400 align:start position:0% people who work with events 00:26:48.400 --> 00:26:49.830 align:start position:0% people who work with events noaa's<00:26:48.720> wiring<00:26:49.200> you<00:26:49.279> know<00:26:49.440> we<00:26:49.520> talk<00:26:49.679> about 00:26:49.830 --> 00:26:49.840 align:start position:0% noaa's wiring you know we talk about 00:26:49.840 --> 00:26:51.750 align:start position:0% noaa's wiring you know we talk about wiring<00:26:50.240> up<00:26:50.320> the<00:26:50.400> mock-up<00:26:50.799> wiring<00:26:51.200> up<00:26:51.600> our 00:26:51.750 --> 00:26:51.760 align:start position:0% wiring up the mock-up wiring up our 00:26:51.760 --> 00:26:54.149 align:start position:0% wiring up the mock-up wiring up our program<00:26:52.480> this<00:26:52.640> is<00:26:52.799> a<00:26:52.880> genuine<00:26:53.760> general 00:26:54.149 --> 00:26:54.159 align:start position:0% program this is a genuine general 00:26:54.159 --> 00:26:56.470 align:start position:0% program this is a genuine general purpose<00:26:54.559> wiring<00:26:55.039> library<00:26:55.600> for 00:26:56.470 --> 00:26:56.480 align:start position:0% purpose wiring library for 00:26:56.480 --> 00:26:59.750 align:start position:0% purpose wiring library for wiring<00:26:56.880> together<00:26:57.200> behaviors<00:26:57.679> in<00:26:57.760> the<00:26:57.840> browser 00:26:59.750 --> 00:26:59.760 align:start position:0% wiring together behaviors in the browser 00:26:59.760 --> 00:27:04.830 align:start position:0% wiring together behaviors in the browser demo<00:27:00.080> time 00:27:04.830 --> 00:27:04.840 align:start position:0% 00:27:04.840 --> 00:27:11.830 align:start position:0% so<00:27:05.760> how's<00:27:06.000> that<00:27:06.159> look<00:27:06.480> it<00:27:06.720> look<00:27:06.960> awesome<00:27:07.679> yeah 00:27:11.830 --> 00:27:11.840 align:start position:0% 00:27:11.840 --> 00:27:15.269 align:start position:0% so<00:27:12.080> we're<00:27:12.240> traveling<00:27:12.559> back<00:27:12.799> in<00:27:12.880> time 00:27:15.269 --> 00:27:15.279 align:start position:0% 00:27:15.279 --> 00:27:16.390 align:start position:0% oh 00:27:16.390 --> 00:27:16.400 align:start position:0% oh 00:27:16.400 --> 00:27:17.909 align:start position:0% oh maybe<00:27:16.720> the<00:27:16.799> full<00:27:16.960> screen<00:27:17.279> is<00:27:17.440> a<00:27:17.440> little<00:27:17.679> too 00:27:17.909 --> 00:27:17.919 align:start position:0% maybe the full screen is a little too 00:27:17.919 --> 00:27:27.669 align:start position:0% maybe the full screen is a little too awesome 00:27:27.669 --> 00:27:27.679 align:start position:0% 00:27:27.679 --> 00:27:29.510 align:start position:0% how's<00:27:28.000> that<00:27:28.400> yeah 00:27:29.510 --> 00:27:29.520 align:start position:0% how's that yeah 00:27:29.520 --> 00:27:31.029 align:start position:0% how's that yeah all<00:27:29.679> right<00:27:29.840> so<00:27:30.080> uh<00:27:30.400> what<00:27:30.559> we're<00:27:30.640> looking<00:27:30.880> at 00:27:31.029 --> 00:27:31.039 align:start position:0% all right so uh what we're looking at 00:27:31.039 --> 00:27:33.350 align:start position:0% all right so uh what we're looking at here<00:27:31.360> is<00:27:31.760> the 00:27:33.350 --> 00:27:33.360 align:start position:0% here is the 00:27:33.360 --> 00:27:35.590 align:start position:0% here is the sort<00:27:33.520> of<00:27:33.679> the<00:27:33.760> fibonacci<00:27:34.400> or<00:27:34.480> the<00:27:34.799> factorial 00:27:35.590 --> 00:27:35.600 align:start position:0% sort of the fibonacci or the factorial 00:27:35.600 --> 00:27:37.990 align:start position:0% sort of the fibonacci or the factorial of<00:27:36.000> browser<00:27:36.480> event<00:27:37.200> things<00:27:37.520> which<00:27:37.760> is<00:27:37.919> you 00:27:37.990 --> 00:27:38.000 align:start position:0% of browser event things which is you 00:27:38.000 --> 00:27:38.950 align:start position:0% of browser event things which is you know<00:27:38.080> we're<00:27:38.240> going<00:27:38.240> to<00:27:38.320> add<00:27:38.480> some<00:27:38.640> numbers 00:27:38.950 --> 00:27:38.960 align:start position:0% know we're going to add some numbers 00:27:38.960 --> 00:27:39.909 align:start position:0% know we're going to add some numbers together 00:27:39.909 --> 00:27:39.919 align:start position:0% together 00:27:39.919 --> 00:27:42.390 align:start position:0% together in<00:27:40.080> a<00:27:40.159> cool<00:27:40.400> way 00:27:42.390 --> 00:27:42.400 align:start position:0% in a cool way 00:27:42.400 --> 00:27:44.470 align:start position:0% in a cool way um<00:27:42.880> so<00:27:43.200> you'll<00:27:43.679> you<00:27:43.840> know<00:27:44.000> i<00:27:44.080> can<00:27:44.240> do<00:27:44.320> this 00:27:44.470 --> 00:27:44.480 align:start position:0% um so you'll you know i can do this 00:27:44.480 --> 00:27:45.909 align:start position:0% um so you'll you know i can do this thing<00:27:44.720> where<00:27:44.880> i<00:27:45.039> can<00:27:45.200> tab<00:27:45.440> between<00:27:45.760> these 00:27:45.909 --> 00:27:45.919 align:start position:0% thing where i can tab between these 00:27:45.919 --> 00:27:47.990 align:start position:0% thing where i can tab between these fields<00:27:46.799> and<00:27:46.960> change<00:27:47.279> the<00:27:47.360> values<00:27:47.760> of<00:27:47.840> the 00:27:47.990 --> 00:27:48.000 align:start position:0% fields and change the values of the 00:27:48.000 --> 00:27:49.350 align:start position:0% fields and change the values of the fields 00:27:49.350 --> 00:27:49.360 align:start position:0% fields 00:27:49.360 --> 00:27:51.350 align:start position:0% fields and<00:27:49.840> they<00:27:50.000> get<00:27:50.159> summed<00:27:50.480> up<00:27:50.720> and<00:27:50.880> printed<00:27:51.279> at 00:27:51.350 --> 00:27:51.360 align:start position:0% and they get summed up and printed at 00:27:51.360 --> 00:27:52.710 align:start position:0% and they get summed up and printed at the<00:27:51.520> bottom 00:27:52.710 --> 00:27:52.720 align:start position:0% the bottom 00:27:52.720 --> 00:27:54.230 align:start position:0% the bottom interesting<00:27:53.120> thing<00:27:53.279> to<00:27:53.440> note 00:27:54.230 --> 00:27:54.240 align:start position:0% interesting thing to note 00:27:54.240 --> 00:27:55.029 align:start position:0% interesting thing to note if 00:27:55.029 --> 00:27:55.039 align:start position:0% if 00:27:55.039 --> 00:27:56.710 align:start position:0% if i<00:27:55.279> zero<00:27:55.600> all<00:27:55.760> these<00:27:55.919> out<00:27:56.159> or<00:27:56.320> if<00:27:56.399> some<00:27:56.559> of<00:27:56.640> them 00:27:56.710 --> 00:27:56.720 align:start position:0% i zero all these out or if some of them 00:27:56.720 --> 00:27:58.389 align:start position:0% i zero all these out or if some of them are<00:27:56.880> empty<00:27:57.360> it<00:27:57.440> does<00:27:57.600> the<00:27:57.760> right<00:27:57.919> thing<00:27:58.240> so 00:27:58.389 --> 00:27:58.399 align:start position:0% are empty it does the right thing so 00:27:58.399 --> 00:28:00.230 align:start position:0% are empty it does the right thing so there's<00:27:58.640> some<00:27:58.799> ground<00:27:59.120> value<00:27:59.520> for<00:28:00.000> these 00:28:00.230 --> 00:28:00.240 align:start position:0% there's some ground value for these 00:28:00.240 --> 00:28:02.789 align:start position:0% there's some ground value for these event<00:28:00.559> sources<00:28:01.120> in<00:28:01.200> this<00:28:01.360> case<00:28:01.600> zero 00:28:02.789 --> 00:28:02.799 align:start position:0% event sources in this case zero 00:28:02.799 --> 00:28:05.350 align:start position:0% event sources in this case zero um<00:28:03.120> if<00:28:03.200> i<00:28:03.360> type<00:28:03.520> in<00:28:03.679> something<00:28:03.919> that<00:28:04.320> you<00:28:04.480> can't 00:28:05.350 --> 00:28:05.360 align:start position:0% um if i type in something that you can't 00:28:05.360 --> 00:28:07.830 align:start position:0% um if i type in something that you can't meaningfully<00:28:06.159> sum<00:28:06.640> like<00:28:06.880> you<00:28:06.960> know<00:28:07.600> some 00:28:07.830 --> 00:28:07.840 align:start position:0% meaningfully sum like you know some 00:28:07.840 --> 00:28:08.870 align:start position:0% meaningfully sum like you know some string 00:28:08.870 --> 00:28:08.880 align:start position:0% string 00:28:08.880 --> 00:28:10.710 align:start position:0% string nothing<00:28:09.200> blew<00:28:09.520> up 00:28:10.710 --> 00:28:10.720 align:start position:0% nothing blew up 00:28:10.720 --> 00:28:11.750 align:start position:0% nothing blew up so<00:28:10.960> um 00:28:11.750 --> 00:28:11.760 align:start position:0% so um 00:28:11.760 --> 00:28:13.190 align:start position:0% so um you<00:28:11.840> know<00:28:12.080> at<00:28:12.159> least<00:28:12.320> this<00:28:12.559> experience<00:28:12.960> is<00:28:13.039> not 00:28:13.190 --> 00:28:13.200 align:start position:0% you know at least this experience is not 00:28:13.200 --> 00:28:14.710 align:start position:0% you know at least this experience is not unsophisticated<00:28:14.000> it<00:28:14.080> does<00:28:14.240> some<00:28:14.399> amount<00:28:14.640> of 00:28:14.710 --> 00:28:14.720 align:start position:0% unsophisticated it does some amount of 00:28:14.720 --> 00:28:17.510 align:start position:0% unsophisticated it does some amount of error<00:28:14.960> handling 00:28:17.510 --> 00:28:17.520 align:start position:0% error handling 00:28:17.520 --> 00:28:20.470 align:start position:0% error handling and<00:28:18.000> things<00:28:18.240> happen<00:28:18.480> as<00:28:18.640> i<00:28:18.799> type 00:28:20.470 --> 00:28:20.480 align:start position:0% and things happen as i type 00:28:20.480 --> 00:28:22.630 align:start position:0% and things happen as i type what<00:28:20.799> is<00:28:20.960> the<00:28:21.039> code<00:28:21.279> for<00:28:21.440> this<00:28:21.919> well<00:28:22.320> here<00:28:22.480> it 00:28:22.630 --> 00:28:22.640 align:start position:0% what is the code for this well here it 00:28:22.640 --> 00:28:24.870 align:start position:0% what is the code for this well here it is 00:28:24.870 --> 00:28:24.880 align:start position:0% 00:28:24.880 --> 00:28:29.190 align:start position:0% what<00:28:25.120> we're<00:28:25.440> looking<00:28:25.760> at 00:28:29.190 --> 00:28:29.200 align:start position:0% 00:28:29.200 --> 00:28:34.950 align:start position:0% here 00:28:34.950 --> 00:28:34.960 align:start position:0% 00:28:34.960 --> 00:28:36.389 align:start position:0% um<00:28:35.200> so<00:28:35.360> this<00:28:35.520> is<00:28:35.600> all<00:28:35.760> of<00:28:35.840> the<00:28:35.919> closure<00:28:36.240> code 00:28:36.389 --> 00:28:36.399 align:start position:0% um so this is all of the closure code 00:28:36.399 --> 00:28:37.750 align:start position:0% um so this is all of the closure code that<00:28:36.559> drives<00:28:36.799> all<00:28:36.960> the<00:28:37.039> behavior<00:28:37.360> on<00:28:37.440> the<00:28:37.520> page 00:28:37.750 --> 00:28:37.760 align:start position:0% that drives all the behavior on the page 00:28:37.760 --> 00:28:39.110 align:start position:0% that drives all the behavior on the page we<00:28:37.919> just<00:28:38.080> saw 00:28:39.110 --> 00:28:39.120 align:start position:0% we just saw 00:28:39.120 --> 00:28:40.070 align:start position:0% we just saw i'm<00:28:39.200> going<00:28:39.279> to<00:28:39.360> walk<00:28:39.520> through<00:28:39.760> each<00:28:39.840> function 00:28:40.070 --> 00:28:40.080 align:start position:0% i'm going to walk through each function 00:28:40.080 --> 00:28:42.389 align:start position:0% i'm going to walk through each function there<00:28:40.240> are<00:28:40.320> these<00:28:40.480> five<00:28:40.720> functions 00:28:42.389 --> 00:28:42.399 align:start position:0% there are these five functions 00:28:42.399 --> 00:28:44.470 align:start position:0% there are these five functions and<00:28:42.880> explain<00:28:43.279> the<00:28:43.360> bits<00:28:43.679> of<00:28:43.840> flapjacks<00:28:44.399> that 00:28:44.470 --> 00:28:44.480 align:start position:0% and explain the bits of flapjacks that 00:28:44.480 --> 00:28:47.029 align:start position:0% and explain the bits of flapjacks that are<00:28:44.559> relevant<00:28:44.960> to<00:28:45.120> this<00:28:45.840> closure<00:28:46.159> script<00:28:46.960> the 00:28:47.029 --> 00:28:47.039 align:start position:0% are relevant to this closure script the 00:28:47.039 --> 00:28:48.389 align:start position:0% are relevant to this closure script the first<00:28:47.279> function<00:28:47.600> is<00:28:47.679> kind<00:28:47.840> of<00:28:47.919> a<00:28:48.000> helper 00:28:48.389 --> 00:28:48.399 align:start position:0% first function is kind of a helper 00:28:48.399 --> 00:28:50.630 align:start position:0% first function is kind of a helper function<00:28:48.720> called<00:28:48.960> parsefloat<00:28:50.000> that<00:28:50.240> takes<00:28:50.480> a 00:28:50.630 --> 00:28:50.640 align:start position:0% function called parsefloat that takes a 00:28:50.640 --> 00:28:53.110 align:start position:0% function called parsefloat that takes a string<00:28:51.200> and<00:28:51.360> a<00:28:51.440> default<00:28:51.840> value<00:28:52.480> to<00:28:52.640> return<00:28:53.039> in 00:28:53.110 --> 00:28:53.120 align:start position:0% string and a default value to return in 00:28:53.120 --> 00:28:54.870 align:start position:0% string and a default value to return in case<00:28:53.279> that<00:28:53.520> string<00:28:53.760> can't<00:28:54.000> be<00:28:54.159> parsed<00:28:54.640> as<00:28:54.799> a 00:28:54.870 --> 00:28:54.880 align:start position:0% case that string can't be parsed as a 00:28:54.880 --> 00:28:58.549 align:start position:0% case that string can't be parsed as a number<00:28:55.679> so<00:28:55.840> this<00:28:56.000> is<00:28:56.320> the<00:28:56.640> sort<00:28:56.799> of<00:28:56.960> guard<00:28:57.520> that 00:28:58.549 --> 00:28:58.559 align:start position:0% number so this is the sort of guard that 00:28:58.559 --> 00:28:59.909 align:start position:0% number so this is the sort of guard that percolates<00:28:59.039> a<00:28:59.120> number<00:28:59.360> through<00:28:59.600> the<00:28:59.679> event 00:28:59.909 --> 00:28:59.919 align:start position:0% percolates a number through the event 00:28:59.919 --> 00:29:01.669 align:start position:0% percolates a number through the event streams<00:29:00.399> if<00:29:00.559> there<00:29:00.720> isn't<00:29:00.960> an<00:29:01.120> input<00:29:01.440> in<00:29:01.520> the 00:29:01.669 --> 00:29:01.679 align:start position:0% streams if there isn't an input in the 00:29:01.679 --> 00:29:03.830 align:start position:0% streams if there isn't an input in the text<00:29:01.919> field<00:29:02.240> or<00:29:02.320> if<00:29:02.480> it's<00:29:02.559> a<00:29:02.640> string<00:29:02.960> that 00:29:03.830 --> 00:29:03.840 align:start position:0% text field or if it's a string that 00:29:03.840 --> 00:29:05.669 align:start position:0% text field or if it's a string that parsefloat<00:29:04.399> doesn't<00:29:04.720> doesn't<00:29:04.960> work<00:29:05.200> with<00:29:05.520> so 00:29:05.669 --> 00:29:05.679 align:start position:0% parsefloat doesn't doesn't work with so 00:29:05.679 --> 00:29:07.269 align:start position:0% parsefloat doesn't doesn't work with so that's<00:29:05.840> just<00:29:06.080> a<00:29:06.480> that's<00:29:06.720> just<00:29:06.880> a<00:29:06.960> simple 00:29:07.269 --> 00:29:07.279 align:start position:0% that's just a that's just a simple 00:29:07.279 --> 00:29:08.389 align:start position:0% that's just a that's just a simple function<00:29:07.600> there's<00:29:07.760> no<00:29:07.919> event<00:29:08.159> stuff 00:29:08.389 --> 00:29:08.399 align:start position:0% function there's no event stuff 00:29:08.399 --> 00:29:09.590 align:start position:0% function there's no event stuff happening 00:29:09.590 --> 00:29:09.600 align:start position:0% happening 00:29:09.600 --> 00:29:10.710 align:start position:0% happening the<00:29:09.679> next<00:29:09.840> thing<00:29:10.000> we<00:29:10.080> do<00:29:10.240> is<00:29:10.320> define<00:29:10.640> a 00:29:10.710 --> 00:29:10.720 align:start position:0% the next thing we do is define a 00:29:10.720 --> 00:29:13.590 align:start position:0% the next thing we do is define a function<00:29:11.120> called<00:29:11.760> extract<00:29:12.480> number<00:29:12.880> e<00:29:13.440> and 00:29:13.590 --> 00:29:13.600 align:start position:0% function called extract number e and 00:29:13.600 --> 00:29:14.630 align:start position:0% function called extract number e and you'll<00:29:13.760> see<00:29:13.919> this<00:29:14.080> when<00:29:14.159> you're<00:29:14.320> working<00:29:14.559> with 00:29:14.630 --> 00:29:14.640 align:start position:0% you'll see this when you're working with 00:29:14.640 --> 00:29:16.470 align:start position:0% you'll see this when you're working with flapjacks<00:29:15.279> this<00:29:15.440> convention<00:29:15.840> of<00:29:15.919> the<00:29:16.080> capital 00:29:16.470 --> 00:29:16.480 align:start position:0% flapjacks this convention of the capital 00:29:16.480 --> 00:29:17.750 align:start position:0% flapjacks this convention of the capital e<00:29:16.720> at<00:29:16.799> the<00:29:16.960> end 00:29:17.750 --> 00:29:17.760 align:start position:0% e at the end 00:29:17.760 --> 00:29:19.190 align:start position:0% e at the end that's<00:29:18.000> the<00:29:18.159> convention<00:29:18.559> for<00:29:18.720> a<00:29:18.880> function 00:29:19.190 --> 00:29:19.200 align:start position:0% that's the convention for a function 00:29:19.200 --> 00:29:21.190 align:start position:0% that's the convention for a function that<00:29:19.360> returns<00:29:19.840> an<00:29:20.000> event<00:29:20.320> stream<00:29:20.799> object 00:29:21.190 --> 00:29:21.200 align:start position:0% that returns an event stream object 00:29:21.200 --> 00:29:23.590 align:start position:0% that returns an event stream object where<00:29:21.440> an<00:29:21.520> event<00:29:21.760> stream<00:29:22.640> is<00:29:22.880> an<00:29:23.039> object 00:29:23.590 --> 00:29:23.600 align:start position:0% where an event stream is an object 00:29:23.600 --> 00:29:25.350 align:start position:0% where an event stream is an object that's<00:29:23.840> part<00:29:24.000> of<00:29:24.080> the<00:29:24.159> flapjacks 00:29:25.350 --> 00:29:25.360 align:start position:0% that's part of the flapjacks 00:29:25.360 --> 00:29:27.669 align:start position:0% that's part of the flapjacks api 00:29:27.669 --> 00:29:27.679 align:start position:0% api 00:29:27.679 --> 00:29:30.310 align:start position:0% api that<00:29:27.919> represents<00:29:28.320> a<00:29:28.399> stream<00:29:28.720> of<00:29:28.799> events 00:29:30.310 --> 00:29:30.320 align:start position:0% that represents a stream of events 00:29:30.320 --> 00:29:32.549 align:start position:0% that represents a stream of events so<00:29:30.640> here<00:29:31.200> we're<00:29:31.520> creating<00:29:32.000> a<00:29:32.159> stream<00:29:32.399> of 00:29:32.549 --> 00:29:32.559 align:start position:0% so here we're creating a stream of 00:29:32.559 --> 00:29:36.230 align:start position:0% so here we're creating a stream of events<00:29:32.960> that's<00:29:33.279> backed<00:29:33.679> by<00:29:34.000> an<00:29:34.159> html 00:29:36.230 --> 00:29:36.240 align:start position:0% events that's backed by an html 00:29:36.240 --> 00:29:39.110 align:start position:0% events that's backed by an html element<00:29:37.039> with<00:29:37.200> the<00:29:37.360> id<00:29:37.919> id 00:29:39.110 --> 00:29:39.120 align:start position:0% element with the id id 00:29:39.120 --> 00:29:41.269 align:start position:0% element with the id id we're<00:29:39.360> using<00:29:39.679> flapjacks's 00:29:41.269 --> 00:29:41.279 align:start position:0% we're using flapjacks's 00:29:41.279 --> 00:29:43.909 align:start position:0% we're using flapjacks's map<00:29:42.000> which<00:29:42.320> is<00:29:42.799> specialized<00:29:43.440> for<00:29:43.600> mapping 00:29:43.909 --> 00:29:43.919 align:start position:0% map which is specialized for mapping 00:29:43.919 --> 00:29:45.110 align:start position:0% map which is specialized for mapping over<00:29:44.159> events 00:29:45.110 --> 00:29:45.120 align:start position:0% over events 00:29:45.120 --> 00:29:46.789 align:start position:0% over events and<00:29:45.279> we're<00:29:45.440> mapping<00:29:45.840> over<00:29:46.080> each<00:29:46.320> event<00:29:46.559> with 00:29:46.789 --> 00:29:46.799 align:start position:0% and we're mapping over each event with 00:29:46.799 --> 00:29:48.070 align:start position:0% and we're mapping over each event with parse<00:29:47.120> float 00:29:48.070 --> 00:29:48.080 align:start position:0% parse float 00:29:48.080 --> 00:29:50.870 align:start position:0% parse float so<00:29:48.240> every<00:29:48.480> time<00:29:48.960> the<00:29:49.120> html<00:29:50.159> element<00:29:50.640> we 00:29:50.870 --> 00:29:50.880 align:start position:0% so every time the html element we 00:29:50.880 --> 00:29:53.110 align:start position:0% so every time the html element we specify<00:29:51.679> generates<00:29:52.080> an<00:29:52.240> event<00:29:52.559> like<00:29:52.880> has<00:29:53.039> a 00:29:53.110 --> 00:29:53.120 align:start position:0% specify generates an event like has a 00:29:53.120 --> 00:29:56.870 align:start position:0% specify generates an event like has a new<00:29:53.279> value<00:29:54.080> we<00:29:54.480> run<00:29:54.720> parse<00:29:55.039> float<00:29:55.360> on<00:29:55.520> it<00:29:55.840> and 00:29:56.870 --> 00:29:56.880 align:start position:0% new value we run parse float on it and 00:29:56.880 --> 00:29:58.470 align:start position:0% new value we run parse float on it and then<00:29:57.120> that<00:29:57.360> gets<00:29:57.600> applied<00:29:57.840> to<00:29:58.000> whoever<00:29:58.320> is 00:29:58.470 --> 00:29:58.480 align:start position:0% then that gets applied to whoever is 00:29:58.480 --> 00:30:00.549 align:start position:0% then that gets applied to whoever is consuming<00:29:58.960> the<00:29:59.039> stream 00:30:00.549 --> 00:30:00.559 align:start position:0% consuming the stream 00:30:00.559 --> 00:30:02.950 align:start position:0% consuming the stream the<00:30:00.720> next<00:30:00.880> thing<00:30:01.039> we<00:30:01.200> do<00:30:01.520> is<00:30:01.840> define<00:30:02.559> what<00:30:02.880> in 00:30:02.950 --> 00:30:02.960 align:start position:0% the next thing we do is define what in 00:30:02.960 --> 00:30:05.430 align:start position:0% the next thing we do is define what in flapjacks<00:30:03.600> is<00:30:03.679> a<00:30:03.840> behavior<00:30:04.559> so<00:30:05.039> things<00:30:05.279> that 00:30:05.430 --> 00:30:05.440 align:start position:0% flapjacks is a behavior so things that 00:30:05.440 --> 00:30:07.269 align:start position:0% flapjacks is a behavior so things that end<00:30:05.600> in<00:30:05.679> capital<00:30:06.000> e<00:30:06.240> are<00:30:06.320> event<00:30:06.640> streams 00:30:07.269 --> 00:30:07.279 align:start position:0% end in capital e are event streams 00:30:07.279 --> 00:30:08.870 align:start position:0% end in capital e are event streams things<00:30:07.520> that<00:30:07.679> end<00:30:07.840> in<00:30:07.919> capital<00:30:08.320> b<00:30:08.559> are<00:30:08.640> called 00:30:08.870 --> 00:30:08.880 align:start position:0% things that end in capital b are called 00:30:08.880 --> 00:30:11.909 align:start position:0% things that end in capital b are called behaviors<00:30:09.440> in<00:30:09.520> flapjacks<00:30:10.159> world 00:30:11.909 --> 00:30:11.919 align:start position:0% behaviors in flapjacks world 00:30:11.919 --> 00:30:14.389 align:start position:0% behaviors in flapjacks world these<00:30:12.399> are<00:30:12.720> those<00:30:13.120> time<00:30:13.440> varying<00:30:13.919> values<00:30:14.320> that 00:30:14.389 --> 00:30:14.399 align:start position:0% these are those time varying values that 00:30:14.399 --> 00:30:16.310 align:start position:0% these are those time varying values that i<00:30:14.480> was<00:30:14.640> talking<00:30:14.960> about<00:30:15.440> and<00:30:15.760> the<00:30:15.919> difference 00:30:16.310 --> 00:30:16.320 align:start position:0% i was talking about and the difference 00:30:16.320 --> 00:30:18.470 align:start position:0% i was talking about and the difference they<00:30:16.399> have<00:30:16.640> with<00:30:16.799> event<00:30:17.120> streams<00:30:17.520> is<00:30:17.919> they 00:30:18.470 --> 00:30:18.480 align:start position:0% they have with event streams is they 00:30:18.480 --> 00:30:20.310 align:start position:0% they have with event streams is they represent<00:30:18.880> a<00:30:18.960> value<00:30:19.360> even<00:30:19.600> if<00:30:19.760> an<00:30:19.919> event<00:30:20.159> has 00:30:20.310 --> 00:30:20.320 align:start position:0% represent a value even if an event has 00:30:20.320 --> 00:30:23.029 align:start position:0% represent a value even if an event has not<00:30:20.480> yet<00:30:20.720> been<00:30:20.960> fired<00:30:21.520> so<00:30:21.679> for<00:30:21.919> instance 00:30:23.029 --> 00:30:23.039 align:start position:0% not yet been fired so for instance 00:30:23.039 --> 00:30:24.389 align:start position:0% not yet been fired so for instance when<00:30:23.200> i<00:30:23.279> opened<00:30:23.520> the<00:30:23.600> page<00:30:23.840> i<00:30:23.919> didn't<00:30:24.080> get<00:30:24.240> any 00:30:24.389 --> 00:30:24.399 align:start position:0% when i opened the page i didn't get any 00:30:24.399 --> 00:30:26.070 align:start position:0% when i opened the page i didn't get any errors<00:30:24.720> or<00:30:24.799> anything<00:30:25.200> that's<00:30:25.520> because<00:30:25.919> the 00:30:26.070 --> 00:30:26.080 align:start position:0% errors or anything that's because the 00:30:26.080 --> 00:30:27.830 align:start position:0% errors or anything that's because the inputs<00:30:26.480> are<00:30:26.559> behaviors<00:30:27.360> and<00:30:27.520> i<00:30:27.600> had<00:30:27.760> the 00:30:27.830 --> 00:30:27.840 align:start position:0% inputs are behaviors and i had the 00:30:27.840 --> 00:30:30.310 align:start position:0% inputs are behaviors and i had the ability<00:30:28.159> to<00:30:28.320> specify<00:30:28.799> a<00:30:28.880> default<00:30:29.200> value<00:30:29.679> so 00:30:30.310 --> 00:30:30.320 align:start position:0% ability to specify a default value so 00:30:30.320 --> 00:30:31.909 align:start position:0% ability to specify a default value so what<00:30:30.559> is<00:30:30.640> the<00:30:30.720> value<00:30:31.039> of<00:30:31.120> this<00:30:31.279> thing<00:30:31.520> before 00:30:31.909 --> 00:30:31.919 align:start position:0% what is the value of this thing before 00:30:31.919 --> 00:30:33.830 align:start position:0% what is the value of this thing before anybody<00:30:32.240> has<00:30:32.399> fired<00:30:32.720> an<00:30:32.880> event<00:30:33.200> on<00:30:33.440> it<00:30:33.600> that's 00:30:33.830 --> 00:30:33.840 align:start position:0% anybody has fired an event on it that's 00:30:33.840 --> 00:30:36.389 align:start position:0% anybody has fired an event on it that's what<00:30:33.919> a<00:30:34.000> behavior<00:30:34.480> is 00:30:36.389 --> 00:30:36.399 align:start position:0% what a behavior is 00:30:36.399 --> 00:30:38.149 align:start position:0% what a behavior is and<00:30:36.480> then<00:30:36.640> finally<00:30:37.200> now<00:30:37.440> that<00:30:37.679> we<00:30:37.919> have 00:30:38.149 --> 00:30:38.159 align:start position:0% and then finally now that we have 00:30:38.159 --> 00:30:39.830 align:start position:0% and then finally now that we have expressed<00:30:38.640> all<00:30:38.720> of<00:30:38.880> the<00:30:38.960> inputs<00:30:39.360> on<00:30:39.440> our<00:30:39.520> page 00:30:39.830 --> 00:30:39.840 align:start position:0% expressed all of the inputs on our page 00:30:39.840 --> 00:30:41.830 align:start position:0% expressed all of the inputs on our page in<00:30:40.000> terms<00:30:40.320> of<00:30:40.640> behaviors 00:30:41.830 --> 00:30:41.840 align:start position:0% in terms of behaviors 00:30:41.840 --> 00:30:44.230 align:start position:0% in terms of behaviors we<00:30:42.000> can<00:30:42.159> start<00:30:42.320> to<00:30:42.480> compose<00:30:43.039> behaviors<00:30:43.919> and 00:30:44.230 --> 00:30:44.240 align:start position:0% we can start to compose behaviors and 00:30:44.240 --> 00:30:46.230 align:start position:0% we can start to compose behaviors and this<00:30:44.480> is<00:30:44.640> the<00:30:44.720> kind<00:30:44.880> of<00:30:44.960> composition<00:30:45.919> that<00:30:46.080> you 00:30:46.230 --> 00:30:46.240 align:start position:0% this is the kind of composition that you 00:30:46.240 --> 00:30:48.070 align:start position:0% this is the kind of composition that you just<00:30:46.880> there<00:30:47.039> are<00:30:47.120> no<00:30:47.279> means<00:30:47.520> of<00:30:47.600> composition 00:30:48.070 --> 00:30:48.080 align:start position:0% just there are no means of composition 00:30:48.080 --> 00:30:48.950 align:start position:0% just there are no means of composition no 00:30:48.950 --> 00:30:48.960 align:start position:0% no 00:30:48.960 --> 00:30:51.029 align:start position:0% no legitimate<00:30:49.600> same<00:30:50.080> means<00:30:50.320> of<00:30:50.399> composition<00:30:50.880> for 00:30:51.029 --> 00:30:51.039 align:start position:0% legitimate same means of composition for 00:30:51.039 --> 00:30:53.350 align:start position:0% legitimate same means of composition for callbacks<00:30:51.600> or<00:30:51.760> watches 00:30:53.350 --> 00:30:53.360 align:start position:0% callbacks or watches 00:30:53.360 --> 00:30:54.789 align:start position:0% callbacks or watches so<00:30:53.520> this<00:30:53.760> is<00:30:53.840> where<00:30:54.000> we<00:30:54.080> start<00:30:54.240> to<00:30:54.399> really<00:30:54.559> reap 00:30:54.789 --> 00:30:54.799 align:start position:0% so this is where we start to really reap 00:30:54.799 --> 00:30:56.630 align:start position:0% so this is where we start to really reap the<00:30:54.880> benefits<00:30:55.279> of<00:30:55.360> working<00:30:55.600> with<00:30:55.679> behaviors 00:30:56.630 --> 00:30:56.640 align:start position:0% the benefits of working with behaviors 00:30:56.640 --> 00:30:57.830 align:start position:0% the benefits of working with behaviors because<00:30:56.880> here<00:30:57.039> we're<00:30:57.200> defining<00:30:57.600> a<00:30:57.679> thing 00:30:57.830 --> 00:30:57.840 align:start position:0% because here we're defining a thing 00:30:57.840 --> 00:31:00.389 align:start position:0% because here we're defining a thing called<00:30:58.159> sum<00:30:58.480> b<00:30:59.120> which<00:30:59.360> is<00:30:59.520> a<00:30:59.600> function<00:31:00.080> of<00:31:00.159> one 00:31:00.389 --> 00:31:00.399 align:start position:0% called sum b which is a function of one 00:31:00.399 --> 00:31:02.830 align:start position:0% called sum b which is a function of one or<00:31:00.480> more<00:31:00.880> or<00:31:01.120> zero<00:31:01.360> or<00:31:01.520> more 00:31:02.830 --> 00:31:02.840 align:start position:0% or more or zero or more 00:31:02.840 --> 00:31:05.669 align:start position:0% or more or zero or more behaviors<00:31:03.919> that<00:31:04.399> allows<00:31:04.799> us<00:31:04.880> to<00:31:05.039> apply<00:31:05.520> a 00:31:05.669 --> 00:31:05.679 align:start position:0% behaviors that allows us to apply a 00:31:05.679 --> 00:31:08.310 align:start position:0% behaviors that allows us to apply a function<00:31:06.559> to<00:31:06.720> the<00:31:06.880> snapshot<00:31:07.520> values<00:31:07.919> of<00:31:08.080> those 00:31:08.310 --> 00:31:08.320 align:start position:0% function to the snapshot values of those 00:31:08.320 --> 00:31:10.470 align:start position:0% function to the snapshot values of those behaviors<00:31:09.279> together<00:31:09.760> and<00:31:09.840> then<00:31:10.000> return 00:31:10.470 --> 00:31:10.480 align:start position:0% behaviors together and then return 00:31:10.480 --> 00:31:12.070 align:start position:0% behaviors together and then return another<00:31:10.880> behavior 00:31:12.070 --> 00:31:12.080 align:start position:0% another behavior 00:31:12.080 --> 00:31:13.430 align:start position:0% another behavior so<00:31:12.240> we're<00:31:12.399> looking<00:31:12.640> at<00:31:12.720> a<00:31:12.799> system<00:31:13.200> where<00:31:13.360> we 00:31:13.430 --> 00:31:13.440 align:start position:0% so we're looking at a system where we 00:31:13.440 --> 00:31:15.190 align:start position:0% so we're looking at a system where we have<00:31:13.679> inputs<00:31:14.240> we<00:31:14.399> lift<00:31:14.640> them<00:31:14.799> up<00:31:14.960> to<00:31:15.039> this 00:31:15.190 --> 00:31:15.200 align:start position:0% have inputs we lift them up to this 00:31:15.200 --> 00:31:17.269 align:start position:0% have inputs we lift them up to this flapjacks<00:31:15.840> behavior<00:31:16.240> level<00:31:16.799> and<00:31:16.960> now<00:31:17.120> we<00:31:17.200> can 00:31:17.269 --> 00:31:17.279 align:start position:0% flapjacks behavior level and now we can 00:31:17.279 --> 00:31:19.190 align:start position:0% flapjacks behavior level and now we can define<00:31:17.679> new<00:31:17.840> behaviors<00:31:18.480> expressed<00:31:18.880> in<00:31:18.960> terms 00:31:19.190 --> 00:31:19.200 align:start position:0% define new behaviors expressed in terms 00:31:19.200 --> 00:31:21.269 align:start position:0% define new behaviors expressed in terms of<00:31:19.360> existing<00:31:19.760> behaviors<00:31:20.559> that<00:31:20.799> are<00:31:20.960> totally 00:31:21.269 --> 00:31:21.279 align:start position:0% of existing behaviors that are totally 00:31:21.279 --> 00:31:24.789 align:start position:0% of existing behaviors that are totally general<00:31:21.760> and<00:31:21.919> not<00:31:22.159> coupled<00:31:22.480> to<00:31:22.720> even<00:31:22.960> the<00:31:23.120> dom 00:31:24.789 --> 00:31:24.799 align:start position:0% general and not coupled to even the dom 00:31:24.799 --> 00:31:27.029 align:start position:0% general and not coupled to even the dom lastly<00:31:25.200> we<00:31:25.360> have<00:31:25.440> a<00:31:25.520> function<00:31:25.919> calculate<00:31:26.799> and 00:31:27.029 --> 00:31:27.039 align:start position:0% lastly we have a function calculate and 00:31:27.039 --> 00:31:28.549 align:start position:0% lastly we have a function calculate and this<00:31:27.200> is<00:31:27.279> what<00:31:27.520> actually<00:31:28.000> does<00:31:28.240> all<00:31:28.399> the 00:31:28.549 --> 00:31:28.559 align:start position:0% this is what actually does all the 00:31:28.559 --> 00:31:30.710 align:start position:0% this is what actually does all the wiring<00:31:29.039> and<00:31:29.520> and<00:31:29.760> causes<00:31:30.159> things<00:31:30.320> to<00:31:30.480> happen 00:31:30.710 --> 00:31:30.720 align:start position:0% wiring and and causes things to happen 00:31:30.720 --> 00:31:32.549 align:start position:0% wiring and and causes things to happen when<00:31:30.880> we<00:31:30.960> load<00:31:31.200> the<00:31:31.279> page<00:31:31.600> up<00:31:32.159> but<00:31:32.320> it's<00:31:32.480> a 00:31:32.549 --> 00:31:32.559 align:start position:0% when we load the page up but it's a 00:31:32.559 --> 00:31:34.310 align:start position:0% when we load the page up but it's a function<00:31:32.880> that<00:31:32.960> takes<00:31:33.200> a<00:31:33.279> target<00:31:33.600> id<00:31:34.000> place<00:31:34.159> to 00:31:34.310 --> 00:31:34.320 align:start position:0% function that takes a target id place to 00:31:34.320 --> 00:31:37.269 align:start position:0% function that takes a target id place to put<00:31:34.480> the<00:31:34.559> sum<00:31:35.279> and<00:31:35.520> some<00:31:35.679> source<00:31:36.000> ids 00:31:37.269 --> 00:31:37.279 align:start position:0% put the sum and some source ids 00:31:37.279 --> 00:31:39.430 align:start position:0% put the sum and some source ids and<00:31:37.440> here<00:31:37.679> we<00:31:37.840> map<00:31:38.080> our<00:31:38.240> extract<00:31:38.799> number<00:31:39.120> b 00:31:39.430 --> 00:31:39.440 align:start position:0% and here we map our extract number b 00:31:39.440 --> 00:31:41.269 align:start position:0% and here we map our extract number b over<00:31:39.600> the<00:31:39.679> source<00:31:40.000> ids 00:31:41.269 --> 00:31:41.279 align:start position:0% over the source ids 00:31:41.279 --> 00:31:44.870 align:start position:0% over the source ids actually<00:31:41.600> i'm<00:31:41.760> going<00:31:41.840> to<00:31:42.080> flip<00:31:42.399> open<00:31:42.720> the 00:31:44.870 --> 00:31:44.880 align:start position:0% actually i'm going to flip open the 00:31:44.880 --> 00:31:47.990 align:start position:0% actually i'm going to flip open the html<00:31:45.519> going<00:31:45.679> on<00:31:45.919> here 00:31:47.990 --> 00:31:48.000 align:start position:0% html going on here 00:31:48.000 --> 00:31:49.830 align:start position:0% html going on here so<00:31:48.240> i<00:31:48.320> have<00:31:48.480> an<00:31:48.640> onload<00:31:49.120> which<00:31:49.360> calls<00:31:49.679> my 00:31:49.830 --> 00:31:49.840 align:start position:0% so i have an onload which calls my 00:31:49.840 --> 00:31:52.070 align:start position:0% so i have an onload which calls my closure<00:31:50.159> script<00:31:50.399> function<00:31:50.880> with<00:31:51.440> the<00:31:51.600> id<00:31:51.840> of 00:31:52.070 --> 00:31:52.080 align:start position:0% closure script function with the id of 00:31:52.080 --> 00:31:54.149 align:start position:0% closure script function with the id of the<00:31:52.159> thing<00:31:52.399> to<00:31:52.480> put<00:31:52.640> the<00:31:53.039> results<00:31:53.519> and<00:31:53.760> the<00:31:53.919> id 00:31:54.149 --> 00:31:54.159 align:start position:0% the thing to put the results and the id 00:31:54.159 --> 00:31:55.590 align:start position:0% the thing to put the results and the id of<00:31:54.240> the<00:31:54.399> inputs<00:31:55.039> and<00:31:55.120> then<00:31:55.279> here<00:31:55.440> are<00:31:55.519> the 00:31:55.590 --> 00:31:55.600 align:start position:0% of the inputs and then here are the 00:31:55.600 --> 00:32:00.389 align:start position:0% of the inputs and then here are the inputs<00:31:55.919> down<00:31:56.159> here 00:32:00.389 --> 00:32:00.399 align:start position:0% 00:32:00.399 --> 00:32:02.310 align:start position:0% so<00:32:00.720> this<00:32:00.880> function<00:32:01.200> takes<00:32:01.440> the<00:32:01.600> ids<00:32:02.000> wires 00:32:02.310 --> 00:32:02.320 align:start position:0% so this function takes the ids wires 00:32:02.320 --> 00:32:04.310 align:start position:0% so this function takes the ids wires them<00:32:02.559> together<00:32:03.200> and<00:32:03.279> then<00:32:03.440> we're<00:32:03.679> using<00:32:04.080> uh 00:32:04.310 --> 00:32:04.320 align:start position:0% them together and then we're using uh 00:32:04.320 --> 00:32:05.669 align:start position:0% them together and then we're using uh one<00:32:04.480> of<00:32:04.559> the<00:32:04.799> few 00:32:05.669 --> 00:32:05.679 align:start position:0% one of the few 00:32:05.679 --> 00:32:07.990 align:start position:0% one of the few i<00:32:05.919> o<00:32:06.080> functions<00:32:06.480> that<00:32:06.559> comes<00:32:06.799> with<00:32:06.960> flapjacks 00:32:07.990 --> 00:32:08.000 align:start position:0% i o functions that comes with flapjacks 00:32:08.000 --> 00:32:10.149 align:start position:0% i o functions that comes with flapjacks which<00:32:08.480> is<00:32:08.640> a<00:32:08.720> function<00:32:09.039> called<00:32:09.279> insert<00:32:09.760> value 00:32:10.149 --> 00:32:10.159 align:start position:0% which is a function called insert value 00:32:10.159 --> 00:32:12.070 align:start position:0% which is a function called insert value b<00:32:10.399> which<00:32:10.559> will<00:32:10.720> continue<00:32:11.360> continuously 00:32:12.070 --> 00:32:12.080 align:start position:0% b which will continue continuously 00:32:12.080 --> 00:32:14.870 align:start position:0% b which will continue continuously update<00:32:12.799> an<00:32:13.039> attribute<00:32:13.600> at<00:32:13.840> an<00:32:14.000> html<00:32:14.559> element 00:32:14.870 --> 00:32:14.880 align:start position:0% update an attribute at an html element 00:32:14.880 --> 00:32:16.789 align:start position:0% update an attribute at an html element of<00:32:15.039> your<00:32:15.200> choosing<00:32:15.679> with<00:32:15.840> a<00:32:15.919> value<00:32:16.399> given<00:32:16.720> a 00:32:16.789 --> 00:32:16.799 align:start position:0% of your choosing with a value given a 00:32:16.799 --> 00:32:18.389 align:start position:0% of your choosing with a value given a behavior<00:32:17.200> and<00:32:17.279> there's<00:32:17.519> also<00:32:17.760> an<00:32:18.080> insert 00:32:18.389 --> 00:32:18.399 align:start position:0% behavior and there's also an insert 00:32:18.399 --> 00:32:20.230 align:start position:0% behavior and there's also an insert value<00:32:18.640> e<00:32:18.960> to<00:32:19.120> do<00:32:19.200> the<00:32:19.279> same<00:32:19.440> thing<00:32:19.600> with<00:32:19.760> event 00:32:20.230 --> 00:32:20.240 align:start position:0% value e to do the same thing with event 00:32:20.240 --> 00:32:24.789 align:start position:0% value e to do the same thing with event streams 00:32:24.789 --> 00:32:24.799 align:start position:0% 00:32:24.799 --> 00:32:27.269 align:start position:0% so<00:32:24.960> that's<00:32:25.279> pretty<00:32:25.600> much<00:32:26.000> it 00:32:27.269 --> 00:32:27.279 align:start position:0% so that's pretty much it 00:32:27.279 --> 00:32:28.549 align:start position:0% so that's pretty much it i've<00:32:27.519> like<00:32:27.679> been<00:32:27.840> out<00:32:27.919> of<00:32:28.000> time<00:32:28.159> for<00:32:28.320> almost 00:32:28.549 --> 00:32:28.559 align:start position:0% i've like been out of time for almost 00:32:28.559 --> 00:32:30.630 align:start position:0% i've like been out of time for almost two<00:32:28.720> hours<00:32:28.880> now<00:32:29.039> according<00:32:29.360> to<00:32:29.440> that<00:32:29.600> thing 00:32:30.630 --> 00:32:30.640 align:start position:0% two hours now according to that thing 00:32:30.640 --> 00:32:32.070 align:start position:0% two hours now according to that thing um 00:32:32.070 --> 00:32:32.080 align:start position:0% um 00:32:32.080 --> 00:32:33.509 align:start position:0% um so<00:32:32.399> i<00:32:32.480> guess<00:32:32.640> i'll<00:32:32.799> just<00:32:32.960> stop<00:32:33.120> and<00:32:33.200> respect 00:32:33.509 --> 00:32:33.519 align:start position:0% so i guess i'll just stop and respect 00:32:33.519 --> 00:32:36.070 align:start position:0% so i guess i'll just stop and respect people's<00:32:33.760> time<00:32:34.399> um<00:32:35.039> needless<00:32:35.360> to<00:32:35.519> say<00:32:35.760> there's 00:32:36.070 --> 00:32:36.080 align:start position:0% people's time um needless to say there's 00:32:36.080 --> 00:32:38.070 align:start position:0% people's time um needless to say there's a<00:32:36.399> lot<00:32:36.559> of<00:32:36.640> fun<00:32:36.799> stuff<00:32:36.960> to<00:32:37.120> do<00:32:37.200> with<00:32:37.279> events<00:32:37.760> and 00:32:38.070 --> 00:32:38.080 align:start position:0% a lot of fun stuff to do with events and 00:32:38.080 --> 00:32:39.269 align:start position:0% a lot of fun stuff to do with events and i'm<00:32:38.240> working<00:32:38.399> on<00:32:38.480> a<00:32:38.559> closure<00:32:38.799> script<00:32:39.039> board<00:32:39.200> if 00:32:39.269 --> 00:32:39.279 align:start position:0% i'm working on a closure script board if 00:32:39.279 --> 00:32:40.870 align:start position:0% i'm working on a closure script board if you<00:32:39.360> want<00:32:39.440> to<00:32:39.519> talk<00:32:39.679> about<00:32:39.919> it 00:32:40.870 --> 00:32:40.880 align:start position:0% you want to talk about it 00:32:40.880 --> 00:32:41.830 align:start position:0% you want to talk about it i<00:32:40.960> think<00:32:41.120> it's<00:32:41.200> a<00:32:41.279> general<00:32:41.600> purpose 00:32:41.830 --> 00:32:41.840 align:start position:0% i think it's a general purpose 00:32:41.840 --> 00:32:43.190 align:start position:0% i think it's a general purpose evaluation<00:32:42.399> model<00:32:42.640> that<00:32:42.720> could<00:32:42.799> also<00:32:42.960> work 00:32:43.190 --> 00:32:43.200 align:start position:0% evaluation model that could also work 00:32:43.200 --> 00:32:44.389 align:start position:0% evaluation model that could also work enclosure<00:32:43.519> in<00:32:43.600> the<00:32:43.679> jvm<00:32:44.080> for<00:32:44.240> doing 00:32:44.389 --> 00:32:44.399 align:start position:0% enclosure in the jvm for doing 00:32:44.399 --> 00:32:45.909 align:start position:0% enclosure in the jvm for doing interesting<00:32:44.799> things 00:32:45.909 --> 00:32:45.919 align:start position:0% interesting things 00:32:45.919 --> 00:32:47.190 align:start position:0% interesting things and 00:32:47.190 --> 00:32:47.200 align:start position:0% and 00:32:47.200 --> 00:32:58.070 align:start position:0% and thanks 00:32:58.070 --> 00:32:58.080 align:start position:0% 00:32:58.080 --> 00:33:00.159 align:start position:0% you