WEBVTT Kind: captions Language: en 00:00:12.040 --> 00:00:13.870 align:start position:0% hello<00:00:12.280> everybody<00:00:12.719> I'm<00:00:12.880> Alexi<00:00:13.200> kov<00:00:13.759> the 00:00:13.870 --> 00:00:13.880 align:start position:0% hello everybody I'm Alexi kov the 00:00:13.880 --> 00:00:16.349 align:start position:0% hello everybody I'm Alexi kov the organizer<00:00:14.440> of<00:00:14.599> SF<00:00:14.920> Scola<00:00:15.559> and<00:00:15.759> here<00:00:16.000> we<00:00:16.199> on 00:00:16.349 --> 00:00:16.359 align:start position:0% organizer of SF Scola and here we on 00:00:16.359 --> 00:00:19.150 align:start position:0% organizer of SF Scola and here we on location<00:00:16.800> at<00:00:17.000> typ<00:00:17.359> safe<00:00:17.960> and<00:00:18.640> with<00:00:18.800> us<00:00:18.920> today 00:00:19.150 --> 00:00:19.160 align:start position:0% location at typ safe and with us today 00:00:19.160 --> 00:00:21.189 align:start position:0% location at typ safe and with us today we<00:00:19.279> have<00:00:19.439> Conor<00:00:19.720> Bowski<00:00:20.320> who<00:00:20.439> is<00:00:20.560> a<00:00:20.800> software 00:00:21.189 --> 00:00:21.199 align:start position:0% we have Conor Bowski who is a software 00:00:21.199 --> 00:00:24.429 align:start position:0% we have Conor Bowski who is a software engineer<00:00:21.880> on<00:00:22.039> the<00:00:22.160> AA<00:00:22.439> team<00:00:22.920> hello<00:00:23.160> everyone<00:00:23.760> H 00:00:24.429 --> 00:00:24.439 align:start position:0% engineer on the AA team hello everyone H 00:00:24.439 --> 00:00:27.269 align:start position:0% engineer on the AA team hello everyone H yeah<00:00:25.119> so<00:00:25.640> uh<00:00:26.359> Conor<00:00:26.640> is<00:00:26.720> going<00:00:26.800> to<00:00:26.920> talk<00:00:27.039> about 00:00:27.269 --> 00:00:27.279 align:start position:0% yeah so uh Conor is going to talk about 00:00:27.279 --> 00:00:29.550 align:start position:0% yeah so uh Conor is going to talk about ractive<00:00:27.640> dreams<00:00:28.640> he's<00:00:28.880> a<00:00:29.160> well-known 00:00:29.550 --> 00:00:29.560 align:start position:0% ractive dreams he's a well-known 00:00:29.560 --> 00:00:31.589 align:start position:0% ractive dreams he's a well-known contributor<00:00:30.240> scholar<00:00:30.519> community<00:00:31.199> and<00:00:31.400> he 00:00:31.589 --> 00:00:31.599 align:start position:0% contributor scholar community and he 00:00:31.599 --> 00:00:35.190 align:start position:0% contributor scholar community and he resides<00:00:32.040> in<00:00:32.239> in<00:00:32.360> kov<00:00:32.800> in<00:00:32.920> Poland<00:00:33.600> yeah<00:00:34.040> and<00:00:34.640> uh 00:00:35.190 --> 00:00:35.200 align:start position:0% resides in in kov in Poland yeah and uh 00:00:35.200 --> 00:00:37.310 align:start position:0% resides in in kov in Poland yeah and uh it's<00:00:35.399> you<00:00:35.559> know<00:00:35.840> not<00:00:35.960> often<00:00:36.239> we<00:00:36.360> get<00:00:36.480> Con<00:00:37.200> in 00:00:37.310 --> 00:00:37.320 align:start position:0% it's you know not often we get Con in 00:00:37.320 --> 00:00:38.590 align:start position:0% it's you know not often we get Con in this<00:00:37.520> parts<00:00:37.719> of<00:00:37.800> the<00:00:37.960> world<00:00:38.160> so<00:00:38.320> we're<00:00:38.480> going 00:00:38.590 --> 00:00:38.600 align:start position:0% this parts of the world so we're going 00:00:38.600 --> 00:00:40.150 align:start position:0% this parts of the world so we're going to<00:00:38.800> ask<00:00:38.960> him<00:00:39.079> all<00:00:39.239> kinds<00:00:39.360> of<00:00:39.520> questions<00:00:39.920> about 00:00:40.150 --> 00:00:40.160 align:start position:0% to ask him all kinds of questions about 00:00:40.160 --> 00:00:43.990 align:start position:0% to ask him all kinds of questions about schola<00:00:40.840> and<00:00:41.000> open<00:00:41.320> source<00:00:42.320> so<00:00:43.039> um<00:00:43.680> first<00:00:43.840> of 00:00:43.990 --> 00:00:44.000 align:start position:0% schola and open source so um first of 00:00:44.000 --> 00:00:46.590 align:start position:0% schola and open source so um first of all<00:00:44.920> I<00:00:45.079> noticed<00:00:45.680> you<00:00:45.800> know<00:00:46.120> through<00:00:46.399> many 00:00:46.590 --> 00:00:46.600 align:start position:0% all I noticed you know through many 00:00:46.600 --> 00:00:49.110 align:start position:0% all I noticed you know through many channels<00:00:46.960> like<00:00:47.079> I<00:00:47.199> see<00:00:47.800> very<00:00:48.199> strong<00:00:48.760> uh<00:00:48.879> open 00:00:49.110 --> 00:00:49.120 align:start position:0% channels like I see very strong uh open 00:00:49.120 --> 00:00:50.750 align:start position:0% channels like I see very strong uh open source<00:00:49.399> community<00:00:49.760> in<00:00:49.920> Poland<00:00:50.320> specifically 00:00:50.750 --> 00:00:50.760 align:start position:0% source community in Poland specifically 00:00:50.760 --> 00:00:54.470 align:start position:0% source community in Poland specifically a<00:00:50.840> lot<00:00:51.000> of<00:00:51.360> strong<00:00:51.559> Scala<00:00:52.359> centc<00:00:52.920> companies<00:00:53.920> uh 00:00:54.470 --> 00:00:54.480 align:start position:0% a lot of strong Scala centc companies uh 00:00:54.480 --> 00:00:56.470 align:start position:0% a lot of strong Scala centc companies uh what<00:00:54.600> is<00:00:54.719> it<00:00:54.960> about<00:00:55.600> polish<00:00:55.960> open<00:00:56.199> source 00:00:56.470 --> 00:00:56.480 align:start position:0% what is it about polish open source 00:00:56.480 --> 00:00:58.470 align:start position:0% what is it about polish open source Community<00:00:57.000> which<00:00:57.320> kind<00:00:57.440> of<00:00:57.719> create<00:00:58.079> this 00:00:58.470 --> 00:00:58.480 align:start position:0% Community which kind of create this 00:00:58.480 --> 00:01:01.389 align:start position:0% Community which kind of create this strong<00:00:59.199> uh<00:00:59.359> culture<00:01:00.239> yeah<00:01:00.559> so<00:01:01.000> that's 00:01:01.389 --> 00:01:01.399 align:start position:0% strong uh culture yeah so that's 00:01:01.399 --> 00:01:03.029 align:start position:0% strong uh culture yeah so that's actually<00:01:01.640> a<00:01:01.760> funny<00:01:02.039> story<00:01:02.280> so<00:01:02.480> when<00:01:02.640> I<00:01:02.800> first 00:01:03.029 --> 00:01:03.039 align:start position:0% actually a funny story so when I first 00:01:03.039 --> 00:01:06.070 align:start position:0% actually a funny story so when I first started<00:01:03.879> Scara<00:01:04.879> four<00:01:05.119> or<00:01:05.239> five<00:01:05.439> years<00:01:05.640> ago<00:01:05.920> I 00:01:06.070 --> 00:01:06.080 align:start position:0% started Scara four or five years ago I 00:01:06.080 --> 00:01:08.749 align:start position:0% started Scara four or five years ago I guess<00:01:06.520> um<00:01:07.520> there<00:01:07.680> wasn't<00:01:08.119> many<00:01:08.360> scholar 00:01:08.749 --> 00:01:08.759 align:start position:0% guess um there wasn't many scholar 00:01:08.759 --> 00:01:11.149 align:start position:0% guess um there wasn't many scholar developers<00:01:09.280> so<00:01:09.400> in<00:01:09.520> kco<00:01:09.960> it<00:01:10.040> was<00:01:10.240> basically<00:01:10.640> me 00:01:11.149 --> 00:01:11.159 align:start position:0% developers so in kco it was basically me 00:01:11.159 --> 00:01:12.910 align:start position:0% developers so in kco it was basically me and<00:01:11.360> when<00:01:11.479> I<00:01:11.720> would<00:01:11.880> go<00:01:12.000> to<00:01:12.119> a<00:01:12.240> Meetup<00:01:12.600> and<00:01:12.720> say 00:01:12.910 --> 00:01:12.920 align:start position:0% and when I would go to a Meetup and say 00:01:12.920 --> 00:01:14.670 align:start position:0% and when I would go to a Meetup and say I'm<00:01:13.159> really<00:01:13.360> interested<00:01:13.720> in<00:01:13.840> scholar<00:01:14.280> people 00:01:14.670 --> 00:01:14.680 align:start position:0% I'm really interested in scholar people 00:01:14.680 --> 00:01:17.550 align:start position:0% I'm really interested in scholar people would<00:01:14.920> you<00:01:15.040> know<00:01:15.320> laugh<00:01:15.600> a<00:01:15.680> lot<00:01:15.960> about<00:01:16.200> me<00:01:17.159> like 00:01:17.550 --> 00:01:17.560 align:start position:0% would you know laugh a lot about me like 00:01:17.560 --> 00:01:18.990 align:start position:0% would you know laugh a lot about me like what<00:01:17.680> is<00:01:17.880> this<00:01:18.040> funny<00:01:18.320> language<00:01:18.680> you're 00:01:18.990 --> 00:01:19.000 align:start position:0% what is this funny language you're 00:01:19.000 --> 00:01:20.590 align:start position:0% what is this funny language you're you're<00:01:19.200> interested<00:01:19.600> in<00:01:19.759> and<00:01:19.920> nowadays<00:01:20.439> yeah 00:01:20.590 --> 00:01:20.600 align:start position:0% you're interested in and nowadays yeah 00:01:20.600 --> 00:01:22.749 align:start position:0% you're interested in and nowadays yeah it's<00:01:20.759> really<00:01:20.960> crazy<00:01:21.360> like<00:01:21.520> everybody's<00:01:22.400> both 00:01:22.749 --> 00:01:22.759 align:start position:0% it's really crazy like everybody's both 00:01:22.759 --> 00:01:25.350 align:start position:0% it's really crazy like everybody's both into<00:01:23.079> it<00:01:23.320> and<00:01:23.560> actually<00:01:24.520> lots<00:01:24.720> of<00:01:24.880> companies 00:01:25.350 --> 00:01:25.360 align:start position:0% into it and actually lots of companies 00:01:25.360 --> 00:01:27.510 align:start position:0% into it and actually lots of companies really<00:01:25.640> centering<00:01:26.200> around<00:01:26.479> it<00:01:26.759> and<00:01:27.040> support 00:01:27.510 --> 00:01:27.520 align:start position:0% really centering around it and support 00:01:27.520 --> 00:01:29.710 align:start position:0% really centering around it and support and<00:01:27.799> just<00:01:28.079> helping<00:01:28.520> other<00:01:28.799> companies<00:01:29.400> to<00:01:29.560> go 00:01:29.710 --> 00:01:29.720 align:start position:0% and just helping other companies to go 00:01:29.720 --> 00:01:32.230 align:start position:0% and just helping other companies to go in<00:01:29.960> into<00:01:30.240> it<00:01:30.560> and<00:01:31.000> deliver<00:01:31.759> you<00:01:31.880> know<00:01:32.079> an 00:01:32.230 --> 00:01:32.240 align:start position:0% in into it and deliver you know an 00:01:32.240 --> 00:01:34.069 align:start position:0% in into it and deliver you know an entire<00:01:32.640> team<00:01:33.000> basically<00:01:33.399> to<00:01:33.560> help<00:01:33.840> your 00:01:34.069 --> 00:01:34.079 align:start position:0% entire team basically to help your 00:01:34.079 --> 00:01:35.950 align:start position:0% entire team basically to help your company<00:01:34.479> start<00:01:34.840> with<00:01:34.960> it<00:01:35.439> so<00:01:35.640> that's<00:01:35.799> the 00:01:35.950 --> 00:01:35.960 align:start position:0% company start with it so that's the 00:01:35.960 --> 00:01:38.789 align:start position:0% company start with it so that's the usual<00:01:36.280> setup<00:01:36.640> I<00:01:36.759> see<00:01:37.360> nowadays<00:01:38.360> uh<00:01:38.479> with<00:01:38.640> the 00:01:38.789 --> 00:01:38.799 align:start position:0% usual setup I see nowadays uh with the 00:01:38.799 --> 00:01:42.030 align:start position:0% usual setup I see nowadays uh with the new<00:01:39.040> company<00:01:39.439> starting<00:01:39.759> out<00:01:39.920> with<00:01:40.079> Scola<00:01:41.040> and 00:01:42.030 --> 00:01:42.040 align:start position:0% new company starting out with Scola and 00:01:42.040 --> 00:01:44.389 align:start position:0% new company starting out with Scola and helping<00:01:42.320> out<00:01:42.560> others<00:01:42.880> so<00:01:43.119> Poland<00:01:43.479> is<00:01:43.720> Al<00:01:44.040> also 00:01:44.389 --> 00:01:44.399 align:start position:0% helping out others so Poland is Al also 00:01:44.399 --> 00:01:47.030 align:start position:0% helping out others so Poland is Al also very<00:01:44.719> popular<00:01:45.159> for<00:01:46.159> what<00:01:46.280> do<00:01:46.360> we<00:01:46.520> call<00:01:46.759> I<00:01:46.880> guess 00:01:47.030 --> 00:01:47.040 align:start position:0% very popular for what do we call I guess 00:01:47.040 --> 00:01:49.550 align:start position:0% very popular for what do we call I guess near<00:01:47.360> Shoring<00:01:48.159> so<00:01:48.320> it's<00:01:48.479> not<00:01:48.759> Outsourcing 00:01:49.550 --> 00:01:49.560 align:start position:0% near Shoring so it's not Outsourcing 00:01:49.560 --> 00:01:51.670 align:start position:0% near Shoring so it's not Outsourcing it's<00:01:49.719> just<00:01:49.840> near<00:01:50.079> Shoring<00:01:50.759> so<00:01:50.960> people<00:01:51.200> realize 00:01:51.670 --> 00:01:51.680 align:start position:0% it's just near Shoring so people realize 00:01:51.680 --> 00:01:53.910 align:start position:0% it's just near Shoring so people realize we<00:01:51.840> really<00:01:52.040> want<00:01:52.240> a<00:01:52.600> strong<00:01:52.799> team<00:01:53.600> and<00:01:53.719> i' 00:01:53.910 --> 00:01:53.920 align:start position:0% we really want a strong team and i' 00:01:53.920 --> 00:01:55.830 align:start position:0% we really want a strong team and i' rather<00:01:54.200> pay<00:01:54.399> for<00:01:54.520> a<00:01:54.840> strong<00:01:55.040> team<00:01:55.280> and<00:01:55.600> two 00:01:55.830 --> 00:01:55.840 align:start position:0% rather pay for a strong team and two 00:01:55.840 --> 00:01:58.469 align:start position:0% rather pay for a strong team and two free<00:01:56.240> guys<00:01:56.640> and<00:01:56.960> have<00:01:57.159> them<00:01:57.360> either<00:01:57.960> visit<00:01:58.240> me 00:01:58.469 --> 00:01:58.479 align:start position:0% free guys and have them either visit me 00:01:58.479 --> 00:02:00.870 align:start position:0% free guys and have them either visit me very<00:01:58.840> often<00:01:59.920> maybe<00:02:00.119> in<00:02:00.200> England<00:02:00.560> maybe<00:02:00.759> in 00:02:00.870 --> 00:02:00.880 align:start position:0% very often maybe in England maybe in 00:02:00.880 --> 00:02:02.990 align:start position:0% very often maybe in England maybe in Poland<00:02:01.200> maybe<00:02:01.399> in<00:02:01.560> Germany<00:02:02.079> MH<00:02:02.520> so<00:02:02.680> that's<00:02:02.840> a 00:02:02.990 --> 00:02:03.000 align:start position:0% Poland maybe in Germany MH so that's a 00:02:03.000 --> 00:02:05.069 align:start position:0% Poland maybe in Germany MH so that's a usual<00:02:03.280> settlement<00:02:03.840> that's<00:02:04.119> how<00:02:04.640> people<00:02:04.880> got 00:02:05.069 --> 00:02:05.079 align:start position:0% usual settlement that's how people got 00:02:05.079 --> 00:02:06.990 align:start position:0% usual settlement that's how people got into<00:02:05.320> Scola<00:02:05.799> I<00:02:05.920> think<00:02:06.240> because<00:02:06.520> there's<00:02:06.840> both 00:02:06.990 --> 00:02:07.000 align:start position:0% into Scola I think because there's both 00:02:07.000 --> 00:02:09.630 align:start position:0% into Scola I think because there's both a<00:02:07.200> very<00:02:07.560> strong<00:02:07.759> need<00:02:08.039> in<00:02:08.280> Europe<00:02:08.640> for<00:02:09.399> strong 00:02:09.630 --> 00:02:09.640 align:start position:0% a very strong need in Europe for strong 00:02:09.640 --> 00:02:12.110 align:start position:0% a very strong need in Europe for strong experts<00:02:10.080> in<00:02:10.200> the<00:02:10.440> area<00:02:11.440> and<00:02:11.599> these<00:02:11.800> polish 00:02:12.110 --> 00:02:12.120 align:start position:0% experts in the area and these polish 00:02:12.120 --> 00:02:13.630 align:start position:0% experts in the area and these polish companies<00:02:12.440> kind<00:02:12.599> of<00:02:12.720> recognized<00:02:13.239> the<00:02:13.400> need 00:02:13.630 --> 00:02:13.640 align:start position:0% companies kind of recognized the need 00:02:13.640 --> 00:02:16.949 align:start position:0% companies kind of recognized the need and<00:02:14.160> now<00:02:14.319> are<00:02:14.519> benefiting<00:02:15.040> from<00:02:15.239> it<00:02:15.760> that<00:02:16.560> why 00:02:16.949 --> 00:02:16.959 align:start position:0% and now are benefiting from it that why 00:02:16.959 --> 00:02:19.869 align:start position:0% and now are benefiting from it that why are<00:02:17.200> they<00:02:17.480> kind<00:02:17.640> of<00:02:18.120> such<00:02:18.480> such<00:02:18.640> a<00:02:19.000> you<00:02:19.080> know 00:02:19.869 --> 00:02:19.879 align:start position:0% are they kind of such such a you know 00:02:19.879 --> 00:02:21.949 align:start position:0% are they kind of such such a you know good<00:02:20.160> amount<00:02:20.519> of<00:02:20.840> strong<00:02:21.239> Engineers<00:02:21.680> was<00:02:21.800> it 00:02:21.949 --> 00:02:21.959 align:start position:0% good amount of strong Engineers was it 00:02:21.959 --> 00:02:23.470 align:start position:0% good amount of strong Engineers was it because<00:02:22.200> of 00:02:23.470 --> 00:02:23.480 align:start position:0% because of 00:02:23.480 --> 00:02:25.550 align:start position:0% because of Education<00:02:24.480> Community<00:02:25.120> like<00:02:25.239> what<00:02:25.319> are<00:02:25.440> the 00:02:25.550 --> 00:02:25.560 align:start position:0% Education Community like what are the 00:02:25.560 --> 00:02:27.750 align:start position:0% Education Community like what are the driving<00:02:25.879> forces<00:02:26.760> uh<00:02:26.959> both<00:02:27.239> things<00:02:27.480> that<00:02:27.640> you 00:02:27.750 --> 00:02:27.760 align:start position:0% driving forces uh both things that you 00:02:27.760 --> 00:02:30.070 align:start position:0% driving forces uh both things that you actually<00:02:28.000> mentioned<00:02:28.480> so<00:02:28.920> both<00:02:29.239> education 00:02:30.070 --> 00:02:30.080 align:start position:0% actually mentioned so both education 00:02:30.080 --> 00:02:32.350 align:start position:0% actually mentioned so both education very<00:02:30.280> very<00:02:30.680> strong<00:02:31.080> like<00:02:31.440> universities<00:02:32.160> in 00:02:32.350 --> 00:02:32.360 align:start position:0% very very strong like universities in 00:02:32.360 --> 00:02:35.030 align:start position:0% very very strong like universities in Poland<00:02:33.200> are<00:02:33.360> really<00:02:33.640> topnotch<00:02:34.640> uh 00:02:35.030 --> 00:02:35.040 align:start position:0% Poland are really topnotch uh 00:02:35.040 --> 00:02:37.630 align:start position:0% Poland are really topnotch uh technically<00:02:36.040> um<00:02:36.599> I<00:02:36.720> mean<00:02:37.000> well<00:02:37.160> technically 00:02:37.630 --> 00:02:37.640 align:start position:0% technically um I mean well technically 00:02:37.640 --> 00:02:39.949 align:start position:0% technically um I mean well technically has<00:02:37.760> a<00:02:37.959> wrong<00:02:38.200> meaning<00:02:38.560> in<00:02:38.800> English 00:02:39.949 --> 00:02:39.959 align:start position:0% has a wrong meaning in English 00:02:39.959 --> 00:02:43.790 align:start position:0% has a wrong meaning in English um<00:02:40.959> in<00:02:41.920> technological<00:02:42.760> Fields<00:02:43.440> that's<00:02:43.599> what<00:02:43.720> I 00:02:43.790 --> 00:02:43.800 align:start position:0% um in technological Fields that's what I 00:02:43.800 --> 00:02:45.869 align:start position:0% um in technological Fields that's what I meant<00:02:44.000> to<00:02:44.080> say<00:02:44.400> yes<00:02:44.599> nonh<00:02:44.879> humanitarian<00:02:45.640> yeah 00:02:45.869 --> 00:02:45.879 align:start position:0% meant to say yes nonh humanitarian yeah 00:02:45.879 --> 00:02:49.470 align:start position:0% meant to say yes nonh humanitarian yeah correct<00:02:46.319> so<00:02:46.680> in<00:02:46.840> kco<00:02:47.360> we<00:02:47.959> have<00:02:48.959> yeah<00:02:49.200> five 00:02:49.470 --> 00:02:49.480 align:start position:0% correct so in kco we have yeah five 00:02:49.480 --> 00:02:52.390 align:start position:0% correct so in kco we have yeah five universities<00:02:50.360> and<00:02:51.080> two<00:02:51.440> of<00:02:51.680> which<00:02:51.840> are<00:02:52.120> really 00:02:52.390 --> 00:02:52.400 align:start position:0% universities and two of which are really 00:02:52.400 --> 00:02:57.070 align:start position:0% universities and two of which are really like<00:02:52.640> topnotch<00:02:53.360> and<00:02:54.040> top<00:02:54.760> tens<00:02:55.360> of<00:02:56.080> worldwi 00:02:57.070 --> 00:02:57.080 align:start position:0% like topnotch and top tens of worldwi 00:02:57.080 --> 00:03:01.070 align:start position:0% like topnotch and top tens of worldwi yski<00:02:58.080> and<00:02:58.400> the<00:02:59.040> aggh<00:03:00.000> which<00:03:00.120> is<00:03:00.319> the 00:03:01.070 --> 00:03:01.080 align:start position:0% yski and the aggh which is the 00:03:01.080 --> 00:03:03.430 align:start position:0% yski and the aggh which is the technology<00:03:02.080> University<00:03:03.000> that's<00:03:03.159> where<00:03:03.280> I 00:03:03.430 --> 00:03:03.440 align:start position:0% technology University that's where I 00:03:03.440 --> 00:03:05.589 align:start position:0% technology University that's where I graduated<00:03:04.040> from<00:03:04.640> and<00:03:04.760> in<00:03:04.959> warsa<00:03:05.319> we<00:03:05.440> have 00:03:05.589 --> 00:03:05.599 align:start position:0% graduated from and in warsa we have 00:03:05.599 --> 00:03:08.190 align:start position:0% graduated from and in warsa we have another<00:03:05.879> one<00:03:06.080> which<00:03:06.200> is<00:03:06.360> also<00:03:06.680> top<00:03:06.920> 10<00:03:07.319> of<00:03:07.840> in 00:03:08.190 --> 00:03:08.200 align:start position:0% another one which is also top 10 of in 00:03:08.200 --> 00:03:10.149 align:start position:0% another one which is also top 10 of in the<00:03:08.360> worldwide<00:03:08.920> rankings<00:03:09.560> so<00:03:09.760> that's<00:03:09.959> one 00:03:10.149 --> 00:03:10.159 align:start position:0% the worldwide rankings so that's one 00:03:10.159 --> 00:03:11.589 align:start position:0% the worldwide rankings so that's one part<00:03:10.319> of<00:03:10.440> it<00:03:10.680> but<00:03:10.920> that's<00:03:11.120> doesn't<00:03:11.480> that 00:03:11.589 --> 00:03:11.599 align:start position:0% part of it but that's doesn't that 00:03:11.599 --> 00:03:14.190 align:start position:0% part of it but that's doesn't that doesn't<00:03:11.840> make<00:03:12.000> a<00:03:12.599> good<00:03:13.200> software<00:03:13.680> developer 00:03:14.190 --> 00:03:14.200 align:start position:0% doesn't make a good software developer 00:03:14.200 --> 00:03:17.070 align:start position:0% doesn't make a good software developer in<00:03:14.360> the<00:03:14.519> real<00:03:14.799> world<00:03:15.560> but<00:03:15.799> may<00:03:16.400> make<00:03:16.599> a<00:03:16.760> good 00:03:17.070 --> 00:03:17.080 align:start position:0% in the real world but may make a good 00:03:17.080 --> 00:03:19.670 align:start position:0% in the real world but may make a good algorithmic<00:03:18.080> like<00:03:18.360> person<00:03:18.760> right<00:03:19.400> but<00:03:19.519> then 00:03:19.670 --> 00:03:19.680 align:start position:0% algorithmic like person right but then 00:03:19.680 --> 00:03:21.990 align:start position:0% algorithmic like person right but then you<00:03:19.760> need<00:03:19.920> to<00:03:20.080> do<00:03:20.319> the<00:03:20.480> brid<00:03:20.840> kind<00:03:21.000> of<00:03:21.120> to<00:03:21.760> what 00:03:21.990 --> 00:03:22.000 align:start position:0% you need to do the brid kind of to what 00:03:22.000 --> 00:03:24.670 align:start position:0% you need to do the brid kind of to what those<00:03:22.319> act<00:03:22.840> businesses<00:03:23.319> need<00:03:23.720> right<00:03:24.159> there's 00:03:24.670 --> 00:03:24.680 align:start position:0% those act businesses need right there's 00:03:24.680 --> 00:03:26.630 align:start position:0% those act businesses need right there's lots<00:03:24.879> of<00:03:25.040> Trends<00:03:25.400> and<00:03:25.599> lots<00:03:25.760> of<00:03:25.920> Technology 00:03:26.630 --> 00:03:26.640 align:start position:0% lots of Trends and lots of Technology 00:03:26.640 --> 00:03:28.869 align:start position:0% lots of Trends and lots of Technology that's<00:03:27.319> somewhat<00:03:27.680> related<00:03:28.000> to<00:03:28.159> algorithmic 00:03:28.869 --> 00:03:28.879 align:start position:0% that's somewhat related to algorithmic 00:03:28.879 --> 00:03:31.309 align:start position:0% that's somewhat related to algorithmic stuff<00:03:29.280> but<00:03:29.799> not<00:03:30.000> directly<00:03:30.519> right<00:03:30.920> so<00:03:31.080> we<00:03:31.200> have 00:03:31.309 --> 00:03:31.319 align:start position:0% stuff but not directly right so we have 00:03:31.319 --> 00:03:34.390 align:start position:0% stuff but not directly right so we have a<00:03:31.480> very<00:03:31.879> strong<00:03:32.360> community<00:03:32.959> in<00:03:33.120> terms<00:03:33.480> of<00:03:33.959> um 00:03:34.390 --> 00:03:34.400 align:start position:0% a very strong community in terms of um 00:03:34.400 --> 00:03:37.910 align:start position:0% a very strong community in terms of um conferences<00:03:35.080> and<00:03:35.280> user<00:03:35.680> groups<00:03:36.680> so<00:03:37.159> there<00:03:37.760> for 00:03:37.910 --> 00:03:37.920 align:start position:0% conferences and user groups so there for 00:03:37.920 --> 00:03:39.630 align:start position:0% conferences and user groups so there for all<00:03:38.120> kinds<00:03:38.280> of 00:03:39.630 --> 00:03:39.640 align:start position:0% all kinds of 00:03:39.640 --> 00:03:42.470 align:start position:0% all kinds of Technologies<00:03:40.640> user<00:03:40.920> groups<00:03:41.239> in<00:03:41.640> many<00:03:41.959> cities 00:03:42.470 --> 00:03:42.480 align:start position:0% Technologies user groups in many cities 00:03:42.480 --> 00:03:44.509 align:start position:0% Technologies user groups in many cities so<00:03:42.640> it's<00:03:42.799> not<00:03:43.040> very<00:03:43.280> centered<00:03:43.840> in<00:03:44.040> only<00:03:44.280> one 00:03:44.509 --> 00:03:44.519 align:start position:0% so it's not very centered in only one 00:03:44.519 --> 00:03:46.390 align:start position:0% so it's not very centered in only one city<00:03:44.840> but<00:03:45.000> in<00:03:45.159> all<00:03:45.319> the<00:03:45.480> cities<00:03:45.840> you<00:03:46.000> basically 00:03:46.390 --> 00:03:46.400 align:start position:0% city but in all the cities you basically 00:03:46.400 --> 00:03:48.070 align:start position:0% city but in all the cities you basically have<00:03:46.560> some<00:03:46.760> kind<00:03:46.920> of<00:03:47.040> user<00:03:47.360> group<00:03:47.560> for<00:03:47.760> Eva 00:03:48.070 --> 00:03:48.080 align:start position:0% have some kind of user group for Eva 00:03:48.080 --> 00:03:51.149 align:start position:0% have some kind of user group for Eva Scara<00:03:48.519> or<00:03:49.200> random<00:03:49.560> technology<00:03:50.159> name<00:03:50.560> whatnot 00:03:51.149 --> 00:03:51.159 align:start position:0% Scara or random technology name whatnot 00:03:51.159 --> 00:03:52.910 align:start position:0% Scara or random technology name whatnot right<00:03:51.720> and<00:03:51.840> then<00:03:52.000> we<00:03:52.120> have<00:03:52.239> a<00:03:52.400> bunch<00:03:52.599> of 00:03:52.910 --> 00:03:52.920 align:start position:0% right and then we have a bunch of 00:03:52.920 --> 00:03:55.229 align:start position:0% right and then we have a bunch of community-driven<00:03:53.920> conferences<00:03:54.920> one<00:03:55.040> of 00:03:55.229 --> 00:03:55.239 align:start position:0% community-driven conferences one of 00:03:55.239 --> 00:03:57.390 align:start position:0% community-driven conferences one of which<00:03:55.439> I'm<00:03:55.799> also<00:03:56.040> running<00:03:56.640> it's<00:03:56.840> the<00:03:57.000> geekon 00:03:57.390 --> 00:03:57.400 align:start position:0% which I'm also running it's the geekon 00:03:57.400 --> 00:03:59.509 align:start position:0% which I'm also running it's the geekon conference<00:03:57.920> so<00:03:58.159> geek<00:03:58.480> conference<00:03:59.040> uh<00:03:59.439> and 00:03:59.509 --> 00:03:59.519 align:start position:0% conference so geek conference uh and 00:03:59.519 --> 00:04:01.990 align:start position:0% conference so geek conference uh and it's<00:03:59.840> been<00:03:59.959> running<00:04:00.480> uh<00:04:00.720> 6<00:04:01.079> years<00:04:01.400> now<00:04:01.599> we<00:04:01.720> got 00:04:01.990 --> 00:04:02.000 align:start position:0% it's been running uh 6 years now we got 00:04:02.000 --> 00:04:04.589 align:start position:0% it's been running uh 6 years now we got 1,200<00:04:02.760> people<00:04:03.040> each<00:04:03.360> time<00:04:03.879> so<00:04:04.079> pretty<00:04:04.319> big<00:04:04.480> we 00:04:04.589 --> 00:04:04.599 align:start position:0% 1,200 people each time so pretty big we 00:04:04.599 --> 00:04:06.470 align:start position:0% 1,200 people each time so pretty big we rent<00:04:04.840> a<00:04:04.959> cinema<00:04:05.400> basically<00:04:05.959> nice<00:04:06.159> when<00:04:06.280> do<00:04:06.360> you 00:04:06.470 --> 00:04:06.480 align:start position:0% rent a cinema basically nice when do you 00:04:06.480 --> 00:04:08.789 align:start position:0% rent a cinema basically nice when do you run<00:04:06.680> it<00:04:06.920> usually<00:04:07.360> it's<00:04:07.480> in<00:04:07.599> May<00:04:08.000> every<00:04:08.319> May<00:04:08.560> in 00:04:08.789 --> 00:04:08.799 align:start position:0% run it usually it's in May every May in 00:04:08.799 --> 00:04:12.229 align:start position:0% run it usually it's in May every May in CCO<00:04:09.480> and<00:04:09.840> what<00:04:10.040> dates<00:04:11.040> uh<00:04:11.239> second<00:04:11.560> week<00:04:11.760> of<00:04:11.920> May 00:04:12.229 --> 00:04:12.239 align:start position:0% CCO and what dates uh second week of May 00:04:12.239 --> 00:04:14.990 align:start position:0% CCO and what dates uh second week of May always<00:04:13.239> yeah<00:04:13.640> if<00:04:13.720> you<00:04:13.840> want<00:04:13.920> to<00:04:14.079> come<00:04:14.360> down<00:04:14.720> we 00:04:14.990 --> 00:04:15.000 align:start position:0% always yeah if you want to come down we 00:04:15.000 --> 00:04:17.469 align:start position:0% always yeah if you want to come down we usually<00:04:15.319> help<00:04:15.680> out<00:04:16.440> um<00:04:16.880> if<00:04:16.959> you're<00:04:17.160> from<00:04:17.320> the 00:04:17.469 --> 00:04:17.479 align:start position:0% usually help out um if you're from the 00:04:17.479 --> 00:04:19.110 align:start position:0% usually help out um if you're from the US<00:04:17.759> for<00:04:17.959> example<00:04:18.239> and<00:04:18.359> you<00:04:18.440> want<00:04:18.519> to<00:04:18.680> speak<00:04:18.919> in 00:04:19.110 --> 00:04:19.120 align:start position:0% US for example and you want to speak in 00:04:19.120 --> 00:04:21.509 align:start position:0% US for example and you want to speak in Europe<00:04:19.600> we<00:04:19.799> usually<00:04:20.759> try<00:04:20.959> to<00:04:21.120> help<00:04:21.320> out 00:04:21.509 --> 00:04:21.519 align:start position:0% Europe we usually try to help out 00:04:21.519 --> 00:04:24.070 align:start position:0% Europe we usually try to help out speakers<00:04:21.880> to<00:04:22.040> come<00:04:22.280> over<00:04:23.280> not<00:04:23.479> always<00:04:23.800> can<00:04:23.919> we 00:04:24.070 --> 00:04:24.080 align:start position:0% speakers to come over not always can we 00:04:24.080 --> 00:04:25.909 align:start position:0% speakers to come over not always can we cover<00:04:24.320> all<00:04:24.520> the<00:04:24.720> costs<00:04:25.120> but<00:04:25.520> sometimes<00:04:25.759> we 00:04:25.909 --> 00:04:25.919 align:start position:0% cover all the costs but sometimes we 00:04:25.919 --> 00:04:28.110 align:start position:0% cover all the costs but sometimes we split<00:04:26.199> it<00:04:26.320> up<00:04:26.520> so<00:04:26.680> we<00:04:26.840> pay<00:04:27.040> the<00:04:27.400> flight<00:04:27.840> and<00:04:27.960> you 00:04:28.110 --> 00:04:28.120 align:start position:0% split it up so we pay the flight and you 00:04:28.120 --> 00:04:29.710 align:start position:0% split it up so we pay the flight and you pay<00:04:28.280> the<00:04:28.440> hotel<00:04:28.800> or<00:04:28.919> something<00:04:29.240> like<00:04:29.400> that 00:04:29.710 --> 00:04:29.720 align:start position:0% pay the hotel or something like that 00:04:29.720 --> 00:04:31.310 align:start position:0% pay the hotel or something like that because<00:04:29.880> it's<00:04:30.000> a<00:04:30.120> Community<00:04:30.560> Driven<00:04:30.919> thing 00:04:31.310 --> 00:04:31.320 align:start position:0% because it's a Community Driven thing 00:04:31.320 --> 00:04:33.390 align:start position:0% because it's a Community Driven thing that's<00:04:31.479> good<00:04:31.600> to<00:04:31.720> know<00:04:32.199> may<00:04:32.759> every<00:04:33.039> year 00:04:33.390 --> 00:04:33.400 align:start position:0% that's good to know may every year 00:04:33.400 --> 00:04:35.790 align:start position:0% that's good to know may every year correct<00:04:34.160> okay<00:04:34.280> cool<00:04:35.000> keep<00:04:35.120> it<00:04:35.240> in<00:04:35.360> mind<00:04:35.680> and 00:04:35.790 --> 00:04:35.800 align:start position:0% correct okay cool keep it in mind and 00:04:35.800 --> 00:04:37.110 align:start position:0% correct okay cool keep it in mind and because<00:04:36.000> it's<00:04:36.160> Community<00:04:36.560> Driven<00:04:36.880> and<00:04:37.000> the 00:04:37.110 --> 00:04:37.120 align:start position:0% because it's Community Driven and the 00:04:37.120 --> 00:04:38.909 align:start position:0% because it's Community Driven and the community<00:04:37.520> nowadays<00:04:37.960> is<00:04:38.080> very<00:04:38.240> inter<00:04:38.520> scholar 00:04:38.909 --> 00:04:38.919 align:start position:0% community nowadays is very inter scholar 00:04:38.919 --> 00:04:40.310 align:start position:0% community nowadays is very inter scholar so<00:04:39.080> there's<00:04:39.280> been<00:04:39.440> a<00:04:39.560> lot<00:04:39.680> of<00:04:39.759> scholar<00:04:40.120> talks 00:04:40.310 --> 00:04:40.320 align:start position:0% so there's been a lot of scholar talks 00:04:40.320 --> 00:04:43.189 align:start position:0% so there's been a lot of scholar talks on<00:04:40.560> that<00:04:40.680> one<00:04:41.400> even<00:04:41.759> though<00:04:42.199> the<00:04:42.520> focus<00:04:42.880> of<00:04:43.000> the 00:04:43.189 --> 00:04:43.199 align:start position:0% on that one even though the focus of the 00:04:43.199 --> 00:04:45.070 align:start position:0% on that one even though the focus of the conference<00:04:43.600> is<00:04:43.800> very<00:04:44.360> anything<00:04:44.720> around<00:04:44.960> the 00:04:45.070 --> 00:04:45.080 align:start position:0% conference is very anything around the 00:04:45.080 --> 00:04:47.950 align:start position:0% conference is very anything around the jvm<00:04:45.560> basically<00:04:46.120> yes<00:04:46.560> and<00:04:46.720> nowadays<00:04:47.400> Scola<00:04:47.840> is 00:04:47.950 --> 00:04:47.960 align:start position:0% jvm basically yes and nowadays Scola is 00:04:47.960 --> 00:04:50.310 align:start position:0% jvm basically yes and nowadays Scola is very<00:04:48.160> much<00:04:48.320> on<00:04:48.479> top<00:04:48.680> of<00:04:48.919> that<00:04:49.479> and<00:04:49.720> with<00:04:49.960> the 00:04:50.310 --> 00:04:50.320 align:start position:0% very much on top of that and with the 00:04:50.320 --> 00:04:52.629 align:start position:0% very much on top of that and with the fast<00:04:50.680> data<00:04:51.039> things<00:04:51.360> like<00:04:51.560> spark<00:04:52.120> and<00:04:52.320> all<00:04:52.479> the 00:04:52.629 --> 00:04:52.639 align:start position:0% fast data things like spark and all the 00:04:52.639 --> 00:04:54.749 align:start position:0% fast data things like spark and all the other<00:04:52.880> things<00:04:53.160> around<00:04:53.440> it<00:04:54.240> there's<00:04:54.520> really 00:04:54.749 --> 00:04:54.759 align:start position:0% other things around it there's really 00:04:54.759 --> 00:04:56.749 align:start position:0% other things around it there's really lots<00:04:54.919> of<00:04:55.160> scolar<00:04:55.600> happening<00:04:55.960> in<00:04:56.120> those<00:04:56.360> areas 00:04:56.749 --> 00:04:56.759 align:start position:0% lots of scolar happening in those areas 00:04:56.759 --> 00:04:58.390 align:start position:0% lots of scolar happening in those areas as<00:04:56.880> well<00:04:57.160> so<00:04:57.400> this<00:04:57.600> again<00:04:57.800> feeds<00:04:58.120> into 00:04:58.390 --> 00:04:58.400 align:start position:0% as well so this again feeds into 00:04:58.400 --> 00:05:00.469 align:start position:0% as well so this again feeds into interest<00:04:58.919> which<00:04:59.080> feeds<00:04:59.360> into<00:04:59.880> interest<00:05:00.240> into 00:05:00.469 --> 00:05:00.479 align:start position:0% interest which feeds into interest into 00:05:00.479 --> 00:05:01.909 align:start position:0% interest which feeds into interest into the<00:05:00.600> meetups<00:05:01.080> which<00:05:01.199> feeds<00:05:01.479> into<00:05:01.759> good 00:05:01.909 --> 00:05:01.919 align:start position:0% the meetups which feeds into good 00:05:01.919 --> 00:05:04.870 align:start position:0% the meetups which feeds into good developers<00:05:02.680> so<00:05:02.960> yes<00:05:03.960> interesting<00:05:04.360> so<00:05:04.600> here's 00:05:04.870 --> 00:05:04.880 align:start position:0% developers so yes interesting so here's 00:05:04.880 --> 00:05:06.790 align:start position:0% developers so yes interesting so here's kind<00:05:05.000> of<00:05:05.240> question<00:05:05.560> I<00:05:05.639> don't<00:05:05.880> have<00:05:06.000> an<00:05:06.160> answer 00:05:06.790 --> 00:05:06.800 align:start position:0% kind of question I don't have an answer 00:05:06.800 --> 00:05:09.070 align:start position:0% kind of question I don't have an answer right<00:05:07.000> I<00:05:07.160> have<00:05:07.320> theories<00:05:07.680> but<00:05:08.280> so<00:05:08.560> you<00:05:08.720> know 00:05:09.070 --> 00:05:09.080 align:start position:0% right I have theories but so you know 00:05:09.080 --> 00:05:10.469 align:start position:0% right I have theories but so you know for<00:05:09.280> many<00:05:09.479> years<00:05:09.720> we<00:05:09.880> have<00:05:10.000> all<00:05:10.120> these<00:05:10.240> Niche 00:05:10.469 --> 00:05:10.479 align:start position:0% for many years we have all these Niche 00:05:10.479 --> 00:05:13.029 align:start position:0% for many years we have all these Niche languages<00:05:11.000> and<00:05:11.240> FP<00:05:12.039> F<00:05:12.360> programming<00:05:12.840> was 00:05:13.029 --> 00:05:13.039 align:start position:0% languages and FP F programming was 00:05:13.039 --> 00:05:14.790 align:start position:0% languages and FP F programming was pretty<00:05:13.280> Niche<00:05:13.680> and<00:05:13.840> we<00:05:13.960> had<00:05:14.080> you<00:05:14.160> know<00:05:14.320> Hill 00:05:14.790 --> 00:05:14.800 align:start position:0% pretty Niche and we had you know Hill 00:05:14.800 --> 00:05:17.230 align:start position:0% pretty Niche and we had you know Hill and<00:05:14.919> a<00:05:15.120> camel<00:05:15.880> now<00:05:16.039> there's<00:05:16.199> a<00:05:16.320> list<00:05:16.919> before 00:05:17.230 --> 00:05:17.240 align:start position:0% and a camel now there's a list before 00:05:17.240 --> 00:05:20.150 align:start position:0% and a camel now there's a list before that<00:05:17.400> and<00:05:17.680> scheme<00:05:18.520> and<00:05:18.720> airling<00:05:19.639> and<00:05:20.000> right 00:05:20.150 --> 00:05:20.160 align:start position:0% that and scheme and airling and right 00:05:20.160 --> 00:05:23.110 align:start position:0% that and scheme and airling and right all<00:05:20.319> kind<00:05:20.479> of<00:05:20.800> stuff<00:05:21.039> and<00:05:21.160> it<00:05:21.520> basically<00:05:22.520> stays 00:05:23.110 --> 00:05:23.120 align:start position:0% all kind of stuff and it basically stays 00:05:23.120 --> 00:05:25.629 align:start position:0% all kind of stuff and it basically stays about<00:05:23.360> the<00:05:23.440> same<00:05:23.720> size<00:05:24.000> so<00:05:24.120> you<00:05:24.240> know<00:05:24.680> uh<00:05:25.080> M<00:05:25.479> of 00:05:25.629 --> 00:05:25.639 align:start position:0% about the same size so you know uh M of 00:05:25.639 --> 00:05:27.189 align:start position:0% about the same size so you know uh M of some<00:05:25.759> of<00:05:25.880> these<00:05:26.039> languages<00:05:26.600> you<00:05:26.680> know<00:05:26.880> in<00:05:27.000> San 00:05:27.189 --> 00:05:27.199 align:start position:0% some of these languages you know in San 00:05:27.199 --> 00:05:29.230 align:start position:0% some of these languages you know in San Francisco<00:05:27.800> basically<00:05:28.199> 20<00:05:28.440> 30<00:05:28.759> people<00:05:29.120> right 00:05:29.230 --> 00:05:29.240 align:start position:0% Francisco basically 20 30 people right 00:05:29.240 --> 00:05:31.670 align:start position:0% Francisco basically 20 30 people right like<00:05:29.360> in<00:05:29.800> in<00:05:29.880> the<00:05:30.000> bakery<00:05:31.000> uh<00:05:31.120> you<00:05:31.240> know<00:05:31.479> when 00:05:31.670 --> 00:05:31.680 align:start position:0% like in in the bakery uh you know when 00:05:31.680 --> 00:05:34.749 align:start position:0% like in in the bakery uh you know when we<00:05:31.960> do<00:05:32.479> meet<00:05:32.680> up<00:05:32.880> like<00:05:33.039> tonight<00:05:33.479> we<00:05:33.639> have<00:05:33.960> 250 00:05:34.749 --> 00:05:34.759 align:start position:0% we do meet up like tonight we have 250 00:05:34.759 --> 00:05:37.550 align:start position:0% we do meet up like tonight we have 250 people<00:05:35.000> on<00:05:35.160> the<00:05:35.319> weight<00:05:35.600> list<00:05:36.360> right<00:05:36.600> and<00:05:36.759> so 00:05:37.550 --> 00:05:37.560 align:start position:0% people on the weight list right and so 00:05:37.560 --> 00:05:40.950 align:start position:0% people on the weight list right and so um<00:05:38.440> what<00:05:38.600> is<00:05:38.720> it<00:05:38.919> about<00:05:39.199> Scala<00:05:40.160> which<00:05:40.400> made<00:05:40.639> it 00:05:40.950 --> 00:05:40.960 align:start position:0% um what is it about Scala which made it 00:05:40.960 --> 00:05:43.830 align:start position:0% um what is it about Scala which made it basically<00:05:41.560> the<00:05:42.240> main<00:05:43.240> kind<00:05:43.360> of<00:05:43.520> function 00:05:43.830 --> 00:05:43.840 align:start position:0% basically the main kind of function 00:05:43.840 --> 00:05:45.710 align:start position:0% basically the main kind of function program<00:05:44.160> language<00:05:44.800> object<00:05:45.160> function<00:05:45.520> which 00:05:45.710 --> 00:05:45.720 align:start position:0% program language object function which 00:05:45.720 --> 00:05:48.309 align:start position:0% program language object function which broke<00:05:46.039> through<00:05:46.360> to<00:05:46.919> mainstream<00:05:47.919> I<00:05:48.000> mean<00:05:48.160> it's 00:05:48.309 --> 00:05:48.319 align:start position:0% broke through to mainstream I mean it's 00:05:48.319 --> 00:05:51.790 align:start position:0% broke through to mainstream I mean it's not<00:05:48.520> as<00:05:48.680> big<00:05:48.840> as<00:05:49.080> Java<00:05:49.639> but<00:05:49.880> it's<00:05:50.160> fairly<00:05:50.960> big 00:05:51.790 --> 00:05:51.800 align:start position:0% not as big as Java but it's fairly big 00:05:51.800 --> 00:05:54.430 align:start position:0% not as big as Java but it's fairly big right<00:05:52.160> so<00:05:52.600> what<00:05:53.440> kind<00:05:53.520> of<00:05:53.759> made<00:05:54.000> it<00:05:54.199> I<00:05:54.280> would 00:05:54.430 --> 00:05:54.440 align:start position:0% right so what kind of made it I would 00:05:54.440 --> 00:05:56.590 align:start position:0% right so what kind of made it I would say<00:05:54.680> the<00:05:54.800> main<00:05:55.400> IND<00:05:55.880> support<00:05:56.280> function 00:05:56.590 --> 00:05:56.600 align:start position:0% say the main IND support function 00:05:56.600 --> 00:05:57.950 align:start position:0% say the main IND support function program<00:05:56.880> langage<00:05:57.240> what<00:05:57.440> what<00:05:57.520> do<00:05:57.600> you<00:05:57.680> think 00:05:57.950 --> 00:05:57.960 align:start position:0% program langage what what do you think 00:05:57.960 --> 00:05:59.950 align:start position:0% program langage what what do you think why<00:05:58.080> did<00:05:58.240> this<00:05:58.440> happen<00:05:58.960> right<00:05:59.120> so<00:05:59.400> I<00:05:59.680> I<00:05:59.759> think 00:05:59.950 --> 00:05:59.960 align:start position:0% why did this happen right so I I think 00:05:59.960 --> 00:06:02.670 align:start position:0% why did this happen right so I I think the<00:06:00.280> main<00:06:01.280> thing<00:06:01.520> about<00:06:01.759> it<00:06:01.960> can<00:06:02.080> be<00:06:02.240> described 00:06:02.670 --> 00:06:02.680 align:start position:0% the main thing about it can be described 00:06:02.680 --> 00:06:05.070 align:start position:0% the main thing about it can be described in<00:06:02.800> one<00:06:03.039> word<00:06:03.360> which<00:06:03.479> is<00:06:03.680> pragmatism<00:06:04.479> MH 00:06:05.070 --> 00:06:05.080 align:start position:0% in one word which is pragmatism MH 00:06:05.080 --> 00:06:07.270 align:start position:0% in one word which is pragmatism MH because<00:06:05.680> um<00:06:06.240> like<00:06:06.400> some<00:06:06.560> of<00:06:06.680> the<00:06:06.840> languages 00:06:07.270 --> 00:06:07.280 align:start position:0% because um like some of the languages 00:06:07.280 --> 00:06:10.950 align:start position:0% because um like some of the languages you<00:06:07.599> said<00:06:08.199> um<00:06:08.599> like<00:06:08.880> hll<00:06:09.880> very<00:06:10.160> nice<00:06:10.599> pure 00:06:10.950 --> 00:06:10.960 align:start position:0% you said um like hll very nice pure 00:06:10.960 --> 00:06:13.150 align:start position:0% you said um like hll very nice pure functional<00:06:11.560> Concepts 00:06:13.150 --> 00:06:13.160 align:start position:0% functional Concepts 00:06:13.160 --> 00:06:16.070 align:start position:0% functional Concepts but<00:06:14.160> not<00:06:14.400> as<00:06:14.599> much<00:06:14.919> real<00:06:15.199> world<00:06:15.520> application 00:06:16.070 --> 00:06:16.080 align:start position:0% but not as much real world application 00:06:16.080 --> 00:06:19.029 align:start position:0% but not as much real world application of<00:06:16.280> them<00:06:16.720> right<00:06:17.000> and<00:06:17.479> sometimes<00:06:18.240> when<00:06:18.400> we<00:06:18.560> took 00:06:19.029 --> 00:06:19.039 align:start position:0% of them right and sometimes when we took 00:06:19.039 --> 00:06:22.150 align:start position:0% of them right and sometimes when we took Concepts<00:06:19.919> that's<00:06:20.080> a<00:06:20.479> a<00:06:20.680> Side<00:06:20.919> Story<00:06:21.280> maybe<00:06:21.639> but 00:06:22.150 --> 00:06:22.160 align:start position:0% Concepts that's a a Side Story maybe but 00:06:22.160 --> 00:06:24.469 align:start position:0% Concepts that's a a Side Story maybe but such<00:06:22.479> pure<00:06:22.720> functional<00:06:23.120> Concepts<00:06:23.720> taken<00:06:24.120> from 00:06:24.469 --> 00:06:24.479 align:start position:0% such pure functional Concepts taken from 00:06:24.479 --> 00:06:26.950 align:start position:0% such pure functional Concepts taken from H<00:06:25.000> directly<00:06:25.360> into<00:06:25.599> scolar<00:06:26.240> one<00:06:26.360> of<00:06:26.479> them<00:06:26.639> being 00:06:26.950 --> 00:06:26.960 align:start position:0% H directly into scolar one of them being 00:06:26.960 --> 00:06:30.150 align:start position:0% H directly into scolar one of them being enumerates<00:06:27.800> and<00:06:28.000> ites<00:06:29.000> back<00:06:29.199> there<00:06:29.880> a<00:06:29.960> few 00:06:30.150 --> 00:06:30.160 align:start position:0% enumerates and ites back there a few 00:06:30.160 --> 00:06:33.430 align:start position:0% enumerates and ites back there a few years<00:06:30.319> ago<00:06:30.560> in<00:06:30.759> play<00:06:31.680> turns<00:06:32.039> out<00:06:32.880> well<00:06:33.080> one 00:06:33.430 --> 00:06:33.440 align:start position:0% years ago in play turns out well one 00:06:33.440 --> 00:06:36.469 align:start position:0% years ago in play turns out well one they're<00:06:33.880> too<00:06:34.120> complex<00:06:34.759> really<00:06:35.759> it's<00:06:35.919> a<00:06:36.120> very 00:06:36.469 --> 00:06:36.479 align:start position:0% they're too complex really it's a very 00:06:36.479 --> 00:06:38.150 align:start position:0% they're too complex really it's a very nice<00:06:36.759> pure<00:06:37.120> model<00:06:37.400> but<00:06:37.560> is<00:06:37.720> really<00:06:37.919> too 00:06:38.150 --> 00:06:38.160 align:start position:0% nice pure model but is really too 00:06:38.160 --> 00:06:41.909 align:start position:0% nice pure model but is really too complex<00:06:38.599> and<00:06:38.759> two<00:06:39.599> well<00:06:39.840> not<00:06:40.319> not<00:06:40.720> that<00:06:41.000> fast 00:06:41.909 --> 00:06:41.919 align:start position:0% complex and two well not not that fast 00:06:41.919 --> 00:06:44.029 align:start position:0% complex and two well not not that fast right<00:06:42.240> so<00:06:42.520> it's<00:06:42.720> very<00:06:42.919> pure<00:06:43.240> it's<00:06:43.440> very<00:06:43.639> nice 00:06:44.029 --> 00:06:44.039 align:start position:0% right so it's very pure it's very nice 00:06:44.039 --> 00:06:46.189 align:start position:0% right so it's very pure it's very nice and<00:06:44.240> we<00:06:44.400> strive<00:06:44.840> to<00:06:45.120> go<00:06:45.319> into<00:06:45.599> the<00:06:45.720> functional 00:06:46.189 --> 00:06:46.199 align:start position:0% and we strive to go into the functional 00:06:46.199 --> 00:06:48.629 align:start position:0% and we strive to go into the functional direction<00:06:46.560> of<00:06:46.759> languages<00:06:47.360> but<00:06:47.680> sometimes<00:06:48.479> we 00:06:48.629 --> 00:06:48.639 align:start position:0% direction of languages but sometimes we 00:06:48.639 --> 00:06:51.230 align:start position:0% direction of languages but sometimes we are<00:06:49.080> pragmatic<00:06:49.680> enough<00:06:49.880> to<00:06:50.080> say<00:06:50.479> well<00:06:51.080> it's 00:06:51.230 --> 00:06:51.240 align:start position:0% are pragmatic enough to say well it's 00:06:51.240 --> 00:06:53.629 align:start position:0% are pragmatic enough to say well it's not<00:06:51.400> worth<00:06:51.639> the<00:06:51.880> tradeoff<00:06:52.880> and<00:06:53.039> I<00:06:53.120> think<00:06:53.360> that 00:06:53.629 --> 00:06:53.639 align:start position:0% not worth the tradeoff and I think that 00:06:53.639 --> 00:06:55.869 align:start position:0% not worth the tradeoff and I think that pragmatism<00:06:54.280> has<00:06:54.440> driven<00:06:54.800> Scara<00:06:55.280> into<00:06:55.479> a<00:06:55.639> good 00:06:55.869 --> 00:06:55.879 align:start position:0% pragmatism has driven Scara into a good 00:06:55.879 --> 00:06:58.589 align:start position:0% pragmatism has driven Scara into a good spot<00:06:56.639> where<00:06:57.120> we<00:06:57.280> do<00:06:57.479> get<00:06:57.720> all<00:06:57.919> the<00:06:58.080> benefits<00:06:58.440> of 00:06:58.589 --> 00:06:58.599 align:start position:0% spot where we do get all the benefits of 00:06:58.599 --> 00:07:00.589 align:start position:0% spot where we do get all the benefits of functional<00:06:59.039> programming<00:06:59.680> and<00:06:59.879> thinking<00:07:00.400> in 00:07:00.589 --> 00:07:00.599 align:start position:0% functional programming and thinking in 00:07:00.599 --> 00:07:03.350 align:start position:0% functional programming and thinking in that<00:07:00.879> style<00:07:01.840> however<00:07:02.319> sometimes<00:07:02.720> we<00:07:02.919> do 00:07:03.350 --> 00:07:03.360 align:start position:0% that style however sometimes we do 00:07:03.360 --> 00:07:06.230 align:start position:0% that style however sometimes we do acknowledge<00:07:04.360> well<00:07:04.560> sorting<00:07:05.000> an<00:07:05.160> array<00:07:05.599> just 00:07:06.230 --> 00:07:06.240 align:start position:0% acknowledge well sorting an array just 00:07:06.240 --> 00:07:07.710 align:start position:0% acknowledge well sorting an array just that's<00:07:06.479> the<00:07:06.639> fastest<00:07:07.039> way<00:07:07.199> so<00:07:07.360> I'm<00:07:07.560> going<00:07:07.639> to 00:07:07.710 --> 00:07:07.720 align:start position:0% that's the fastest way so I'm going to 00:07:07.720 --> 00:07:11.150 align:start position:0% that's the fastest way so I'm going to sort<00:07:07.960> an<00:07:08.080> array<00:07:08.879> yes<00:07:09.479> right<00:07:10.240> makes<00:07:10.479> sense<00:07:11.039> and 00:07:11.150 --> 00:07:11.160 align:start position:0% sort an array yes right makes sense and 00:07:11.160 --> 00:07:14.070 align:start position:0% sort an array yes right makes sense and so<00:07:11.360> with<00:07:11.560> people<00:07:12.280> uh<00:07:12.440> we<00:07:12.599> mention<00:07:13.080> complexity 00:07:14.070 --> 00:07:14.080 align:start position:0% so with people uh we mention complexity 00:07:14.080 --> 00:07:16.749 align:start position:0% so with people uh we mention complexity right<00:07:14.360> and<00:07:14.560> so<00:07:15.479> that's<00:07:15.639> a<00:07:15.800> typical<00:07:16.120> objection 00:07:16.749 --> 00:07:16.759 align:start position:0% right and so that's a typical objection 00:07:16.759 --> 00:07:18.950 align:start position:0% right and so that's a typical objection we<00:07:16.960> get<00:07:17.520> right<00:07:17.759> that<00:07:17.960> kind<00:07:18.120> of<00:07:18.199> scull<00:07:18.479> is<00:07:18.599> too 00:07:18.950 --> 00:07:18.960 align:start position:0% we get right that kind of scull is too 00:07:18.960 --> 00:07:22.350 align:start position:0% we get right that kind of scull is too complex<00:07:19.960> so<00:07:20.440> when<00:07:20.960> companies<00:07:21.319> are<00:07:21.599> avalia<00:07:22.039> in 00:07:22.350 --> 00:07:22.360 align:start position:0% complex so when companies are avalia in 00:07:22.360 --> 00:07:25.790 align:start position:0% complex so when companies are avalia in this<00:07:23.319> right<00:07:24.280> how<00:07:24.599> do<00:07:24.680> you<00:07:24.879> discuss<00:07:25.400> this<00:07:25.680> kind 00:07:25.790 --> 00:07:25.800 align:start position:0% this right how do you discuss this kind 00:07:25.800 --> 00:07:28.350 align:start position:0% this right how do you discuss this kind of<00:07:26.120> what<00:07:26.520> what's<00:07:26.759> kind<00:07:26.919> of<00:07:27.319> your<00:07:27.680> way<00:07:27.960> to 00:07:28.350 --> 00:07:28.360 align:start position:0% of what what's kind of your way to 00:07:28.360 --> 00:07:30.270 align:start position:0% of what what's kind of your way to discuss<00:07:28.759> you<00:07:28.919> know<00:07:29.080> this<00:07:29.240> argument<00:07:29.720> the<00:07:29.840> SCH 00:07:30.270 --> 00:07:30.280 align:start position:0% discuss you know this argument the SCH 00:07:30.280 --> 00:07:34.670 align:start position:0% discuss you know this argument the SCH complex<00:07:31.280> yeah<00:07:31.879> um<00:07:32.680> the<00:07:32.960> best<00:07:33.720> counter<00:07:34.240> example 00:07:34.670 --> 00:07:34.680 align:start position:0% complex yeah um the best counter example 00:07:34.680 --> 00:07:37.469 align:start position:0% complex yeah um the best counter example to<00:07:34.879> that<00:07:35.120> claim<00:07:35.440> I<00:07:35.599> have<00:07:35.960> is<00:07:36.520> um<00:07:36.960> so<00:07:37.160> before 00:07:37.469 --> 00:07:37.479 align:start position:0% to that claim I have is um so before 00:07:37.479 --> 00:07:40.670 align:start position:0% to that claim I have is um so before joining<00:07:37.759> types<00:07:38.560> I<00:07:38.639> was<00:07:38.800> working<00:07:39.080> at<00:07:39.240> eBay<00:07:39.800> mhm 00:07:40.670 --> 00:07:40.680 align:start position:0% joining types I was working at eBay mhm 00:07:40.680 --> 00:07:43.309 align:start position:0% joining types I was working at eBay mhm so<00:07:41.440> maybe<00:07:41.720> not<00:07:42.039> that<00:07:42.240> known<00:07:42.520> for<00:07:42.759> adapting<00:07:43.199> the 00:07:43.309 --> 00:07:43.319 align:start position:0% so maybe not that known for adapting the 00:07:43.319 --> 00:07:46.350 align:start position:0% so maybe not that known for adapting the latest<00:07:43.599> and<00:07:43.800> greatest<00:07:44.759> however<00:07:45.680> um<00:07:46.080> so<00:07:46.240> we 00:07:46.350 --> 00:07:46.360 align:start position:0% latest and greatest however um so we 00:07:46.360 --> 00:07:48.309 align:start position:0% latest and greatest however um so we were<00:07:46.599> basically<00:07:47.159> one<00:07:47.280> of<00:07:47.440> the<00:07:47.560> first<00:07:47.879> teams<00:07:48.199> in 00:07:48.309 --> 00:07:48.319 align:start position:0% were basically one of the first teams in 00:07:48.319 --> 00:07:50.469 align:start position:0% were basically one of the first teams in the<00:07:48.479> London<00:07:48.840> offices<00:07:49.520> MH<00:07:50.000> and<00:07:50.120> of<00:07:50.280> course 00:07:50.469 --> 00:07:50.479 align:start position:0% the London offices MH and of course 00:07:50.479 --> 00:07:52.510 align:start position:0% the London offices MH and of course starting<00:07:50.800> out<00:07:51.319> with<00:07:51.440> the<00:07:51.639> existing<00:07:52.000> stack 00:07:52.510 --> 00:07:52.520 align:start position:0% starting out with the existing stack 00:07:52.520 --> 00:07:54.309 align:start position:0% starting out with the existing stack which<00:07:52.720> was<00:07:53.000> all<00:07:53.280> Java<00:07:53.599> based<00:07:53.879> and<00:07:54.000> spring 00:07:54.309 --> 00:07:54.319 align:start position:0% which was all Java based and spring 00:07:54.319 --> 00:07:56.990 align:start position:0% which was all Java based and spring based<00:07:54.639> and<00:07:54.960> whatnot<00:07:55.960> however<00:07:56.400> I<00:07:56.520> managed<00:07:56.879> and 00:07:56.990 --> 00:07:57.000 align:start position:0% based and whatnot however I managed and 00:07:57.000 --> 00:07:58.990 align:start position:0% based and whatnot however I managed and a<00:07:57.120> few<00:07:57.280> other<00:07:57.479> guys<00:07:57.680> managed<00:07:58.000> to<00:07:58.159> convince<00:07:58.639> the 00:07:58.990 --> 00:07:59.000 align:start position:0% a few other guys managed to convince the 00:07:59.000 --> 00:08:02.990 align:start position:0% a few other guys managed to convince the rest<00:07:59.159> of<00:07:59.599> teams<00:07:59.919> to<00:08:00.159> Tri<00:08:00.440> out<00:08:00.639> Scara<00:08:01.199> mhm<00:08:02.000> and 00:08:02.990 --> 00:08:03.000 align:start position:0% rest of teams to Tri out Scara mhm and 00:08:03.000 --> 00:08:05.230 align:start position:0% rest of teams to Tri out Scara mhm and well<00:08:03.199> one<00:08:03.319> of<00:08:03.479> the<00:08:03.680> things<00:08:04.479> these<00:08:04.720> teams<00:08:05.000> were 00:08:05.230 --> 00:08:05.240 align:start position:0% well one of the things these teams were 00:08:05.240 --> 00:08:06.990 align:start position:0% well one of the things these teams were saying<00:08:05.599> then<00:08:05.919> that<00:08:06.240> well<00:08:06.400> actually<00:08:06.720> this<00:08:06.840> is 00:08:06.990 --> 00:08:07.000 align:start position:0% saying then that well actually this is 00:08:07.000 --> 00:08:10.350 align:start position:0% saying then that well actually this is so<00:08:07.520> simple<00:08:08.520> and<00:08:08.759> what<00:08:08.919> I'm<00:08:09.080> getting<00:08:09.360> at<00:08:09.720> is 00:08:10.350 --> 00:08:10.360 align:start position:0% so simple and what I'm getting at is 00:08:10.360 --> 00:08:13.909 align:start position:0% so simple and what I'm getting at is well<00:08:11.000> the<00:08:11.520> entirety<00:08:12.280> of<00:08:12.560> Scala<00:08:13.560> yeah<00:08:13.759> it's 00:08:13.909 --> 00:08:13.919 align:start position:0% well the entirety of Scala yeah it's 00:08:13.919 --> 00:08:15.469 align:start position:0% well the entirety of Scala yeah it's pretty<00:08:14.199> complex<00:08:14.560> because<00:08:14.759> it's<00:08:14.879> marrying<00:08:15.319> a 00:08:15.469 --> 00:08:15.479 align:start position:0% pretty complex because it's marrying a 00:08:15.479 --> 00:08:17.469 align:start position:0% pretty complex because it's marrying a lot<00:08:15.599> of<00:08:15.759> Concepts<00:08:16.360> however<00:08:16.560> it's<00:08:16.720> doing<00:08:17.000> so<00:08:17.280> in 00:08:17.469 --> 00:08:17.479 align:start position:0% lot of Concepts however it's doing so in 00:08:17.479 --> 00:08:22.950 align:start position:0% lot of Concepts however it's doing so in a<00:08:18.479> um<00:08:19.400> consistent<00:08:20.080> way<00:08:20.680> right<00:08:21.319> so<00:08:21.599> even<00:08:21.960> though 00:08:22.950 --> 00:08:22.960 align:start position:0% a um consistent way right so even though 00:08:22.960 --> 00:08:25.550 align:start position:0% a um consistent way right so even though you<00:08:23.199> learn<00:08:23.680> maybe<00:08:24.039> more<00:08:24.520> Concepts<00:08:25.199> but<00:08:25.400> they 00:08:25.550 --> 00:08:25.560 align:start position:0% you learn maybe more Concepts but they 00:08:25.560 --> 00:08:29.550 align:start position:0% you learn maybe more Concepts but they fit<00:08:26.360> together<00:08:27.360> so<00:08:28.120> I<00:08:28.199> think<00:08:28.400> the<00:08:28.599> term<00:08:28.960> complex 00:08:29.550 --> 00:08:29.560 align:start position:0% fit together so I think the term complex 00:08:29.560 --> 00:08:32.630 align:start position:0% fit together so I think the term complex is<00:08:29.720> overloaded<00:08:30.400> it's<00:08:30.560> a<00:08:31.240> broad<00:08:31.720> language<00:08:32.360> as<00:08:32.479> I 00:08:32.630 --> 00:08:32.640 align:start position:0% is overloaded it's a broad language as I 00:08:32.640 --> 00:08:34.630 align:start position:0% is overloaded it's a broad language as I like<00:08:32.800> to<00:08:33.080> put<00:08:33.240> it<00:08:33.839> and<00:08:33.959> you<00:08:34.080> don't<00:08:34.320> need<00:08:34.479> to 00:08:34.630 --> 00:08:34.640 align:start position:0% like to put it and you don't need to 00:08:34.640 --> 00:08:37.909 align:start position:0% like to put it and you don't need to learn<00:08:35.240> or<00:08:35.479> even<00:08:35.839> use<00:08:36.240> all<00:08:36.399> of<00:08:36.560> the<00:08:36.760> breath<00:08:37.760> of 00:08:37.909 --> 00:08:37.919 align:start position:0% learn or even use all of the breath of 00:08:37.919 --> 00:08:40.509 align:start position:0% learn or even use all of the breath of it<00:08:38.519> yes<00:08:38.719> and<00:08:38.839> even<00:08:39.000> in<00:08:39.120> our<00:08:39.360> teams<00:08:39.839> we<00:08:40.240> would 00:08:40.509 --> 00:08:40.519 align:start position:0% it yes and even in our teams we would 00:08:40.519 --> 00:08:42.430 align:start position:0% it yes and even in our teams we would decide<00:08:41.000> well<00:08:41.159> let's<00:08:41.360> not<00:08:41.519> go<00:08:41.719> into<00:08:42.000> the<00:08:42.159> Super 00:08:42.430 --> 00:08:42.440 align:start position:0% decide well let's not go into the Super 00:08:42.440 --> 00:08:43.909 align:start position:0% decide well let's not go into the Super advanced<00:08:42.959> stuff<00:08:43.279> because<00:08:43.519> we're<00:08:43.719> just 00:08:43.909 --> 00:08:43.919 align:start position:0% advanced stuff because we're just 00:08:43.919 --> 00:08:46.190 align:start position:0% advanced stuff because we're just learning<00:08:44.519> right<00:08:45.160> because<00:08:45.399> we're<00:08:45.560> a<00:08:45.680> new<00:08:45.880> team 00:08:46.190 --> 00:08:46.200 align:start position:0% learning right because we're a new team 00:08:46.200 --> 00:08:48.590 align:start position:0% learning right because we're a new team we're<00:08:46.560> you<00:08:46.680> know<00:08:46.880> starting<00:08:47.279> out<00:08:48.080> and<00:08:48.240> when<00:08:48.360> you 00:08:48.590 --> 00:08:48.600 align:start position:0% we're you know starting out and when you 00:08:48.600 --> 00:08:50.670 align:start position:0% we're you know starting out and when you actually<00:08:48.880> restrain<00:08:49.320> yourself<00:08:49.640> to<00:08:49.800> the<00:08:50.000> very 00:08:50.670 --> 00:08:50.680 align:start position:0% actually restrain yourself to the very 00:08:50.680 --> 00:08:53.269 align:start position:0% actually restrain yourself to the very simple<00:08:51.160> things<00:08:52.160> the<00:08:52.320> good<00:08:52.519> parts<00:08:52.839> as<00:08:52.959> Martin 00:08:53.269 --> 00:08:53.279 align:start position:0% simple things the good parts as Martin 00:08:53.279 --> 00:08:55.509 align:start position:0% simple things the good parts as Martin likes<00:08:53.519> to<00:08:53.680> call<00:08:53.920> them<00:08:54.519> and<00:08:54.680> actually<00:08:54.920> the<00:08:55.279> code 00:08:55.509 --> 00:08:55.519 align:start position:0% likes to call them and actually the code 00:08:55.519 --> 00:08:58.269 align:start position:0% likes to call them and actually the code is<00:08:55.720> both<00:08:56.040> much<00:08:56.279> simpler<00:08:57.080> where<00:08:57.240> is<00:08:57.600> less<00:08:57.880> code 00:08:58.269 --> 00:08:58.279 align:start position:0% is both much simpler where is less code 00:08:58.279 --> 00:09:00.710 align:start position:0% is both much simpler where is less code for<00:08:58.480> one<00:08:58.760> thing<00:08:59.519> and<00:08:59.680> it's<00:08:59.839> more<00:09:00.079> types<00:09:00.399> safe 00:09:00.710 --> 00:09:00.720 align:start position:0% for one thing and it's more types safe 00:09:00.720 --> 00:09:03.389 align:start position:0% for one thing and it's more types safe in<00:09:01.000> terms<00:09:01.519> of<00:09:01.800> when<00:09:01.920> you<00:09:02.079> compare<00:09:02.440> it<00:09:02.600> to<00:09:02.800> a<00:09:03.120> um 00:09:03.389 --> 00:09:03.399 align:start position:0% in terms of when you compare it to a um 00:09:03.399 --> 00:09:06.470 align:start position:0% in terms of when you compare it to a um Java<00:09:04.079> I<00:09:04.160> don't<00:09:04.320> know<00:09:04.800> um<00:09:05.120> annotation<00:09:05.760> driven 00:09:06.470 --> 00:09:06.480 align:start position:0% Java I don't know um annotation driven 00:09:06.480 --> 00:09:08.630 align:start position:0% Java I don't know um annotation driven application<00:09:07.480> you<00:09:07.600> lose<00:09:07.920> all<00:09:08.279> all<00:09:08.399> of<00:09:08.480> the 00:09:08.630 --> 00:09:08.640 align:start position:0% application you lose all all of the 00:09:08.640 --> 00:09:10.710 align:start position:0% application you lose all all of the safety<00:09:08.959> guarantees<00:09:09.600> because<00:09:09.839> it's<00:09:10.040> now<00:09:10.240> all 00:09:10.710 --> 00:09:10.720 align:start position:0% safety guarantees because it's now all 00:09:10.720 --> 00:09:12.470 align:start position:0% safety guarantees because it's now all annotation<00:09:11.240> driven<00:09:11.640> which<00:09:11.760> is<00:09:11.959> not<00:09:12.240> type 00:09:12.470 --> 00:09:12.480 align:start position:0% annotation driven which is not type 00:09:12.480 --> 00:09:15.509 align:start position:0% annotation driven which is not type checked<00:09:12.800> at<00:09:12.959> all<00:09:13.440> yes<00:09:14.000> so<00:09:14.279> you<00:09:14.519> get<00:09:15.000> more 00:09:15.509 --> 00:09:15.519 align:start position:0% checked at all yes so you get more 00:09:15.519 --> 00:09:17.470 align:start position:0% checked at all yes so you get more safety<00:09:16.000> even<00:09:16.279> while<00:09:16.560> working<00:09:16.880> on<00:09:17.040> the<00:09:17.200> code 00:09:17.470 --> 00:09:17.480 align:start position:0% safety even while working on the code 00:09:17.480 --> 00:09:21.030 align:start position:0% safety even while working on the code base<00:09:18.160> so<00:09:18.399> I<00:09:18.560> do<00:09:18.760> think<00:09:19.040> it's<00:09:19.440> a<00:09:20.440> sometimes 00:09:21.030 --> 00:09:21.040 align:start position:0% base so I do think it's a sometimes 00:09:21.040 --> 00:09:24.509 align:start position:0% base so I do think it's a sometimes misunderstood<00:09:22.040> term<00:09:22.480> in<00:09:22.720> the<00:09:23.240> um<00:09:23.959> from<00:09:24.279> people 00:09:24.509 --> 00:09:24.519 align:start position:0% misunderstood term in the um from people 00:09:24.519 --> 00:09:26.990 align:start position:0% misunderstood term in the um from people who<00:09:24.720> don't<00:09:24.959> know<00:09:25.160> Scola<00:09:25.680> yet<00:09:26.160> yes<00:09:26.560> yes<00:09:26.800> makes 00:09:26.990 --> 00:09:27.000 align:start position:0% who don't know Scola yet yes yes makes 00:09:27.000 --> 00:09:29.110 align:start position:0% who don't know Scola yet yes yes makes sense<00:09:27.480> yeah<00:09:27.720> I<00:09:27.880> I<00:09:28.000> remember<00:09:28.360> you<00:09:28.440> know<00:09:28.680> Mar 00:09:29.110 --> 00:09:29.120 align:start position:0% sense yeah I I remember you know Mar 00:09:29.120 --> 00:09:31.430 align:start position:0% sense yeah I I remember you know Mar basically<00:09:29.480> has<00:09:29.560> a<00:09:29.680> talk<00:09:30.120> where<00:09:30.320> you<00:09:30.440> know<00:09:31.000> he 00:09:31.430 --> 00:09:31.440 align:start position:0% basically has a talk where you know he 00:09:31.440 --> 00:09:33.710 align:start position:0% basically has a talk where you know he explains<00:09:31.920> that<00:09:32.160> SC<00:09:32.399> is<00:09:32.519> actually<00:09:32.839> simple<00:09:33.399> and 00:09:33.710 --> 00:09:33.720 align:start position:0% explains that SC is actually simple and 00:09:33.720 --> 00:09:36.030 align:start position:0% explains that SC is actually simple and kind<00:09:33.839> of<00:09:34.120> he<00:09:34.320> actually<00:09:34.680> I<00:09:34.760> think<00:09:35.279> shows<00:09:35.760> how 00:09:36.030 --> 00:09:36.040 align:start position:0% kind of he actually I think shows how 00:09:36.040 --> 00:09:37.750 align:start position:0% kind of he actually I think shows how you<00:09:36.120> know<00:09:36.360> object<00:09:36.839> orientation<00:09:37.480> function 00:09:37.750 --> 00:09:37.760 align:start position:0% you know object orientation function 00:09:37.760 --> 00:09:40.870 align:start position:0% you know object orientation function program<00:09:38.079> work<00:09:38.399> together<00:09:38.959> yeah<00:09:39.279> and<00:09:39.560> to<00:09:39.760> me<00:09:40.160> the 00:09:40.870 --> 00:09:40.880 align:start position:0% program work together yeah and to me the 00:09:40.880 --> 00:09:43.030 align:start position:0% program work together yeah and to me the way<00:09:41.360> like<00:09:41.600> the<00:09:41.839> easiest<00:09:42.200> proof<00:09:42.519> how<00:09:42.680> simple<00:09:42.959> it 00:09:43.030 --> 00:09:43.040 align:start position:0% way like the easiest proof how simple it 00:09:43.040 --> 00:09:45.150 align:start position:0% way like the easiest proof how simple it is<00:09:43.279> that<00:09:43.399> success<00:09:43.680> of<00:09:43.800> spark<00:09:44.240> right<00:09:44.399> and<00:09:44.839> Mark 00:09:45.150 --> 00:09:45.160 align:start position:0% is that success of spark right and Mark 00:09:45.160 --> 00:09:47.310 align:start position:0% is that success of spark right and Mark has<00:09:45.279> this<00:09:45.440> talk<00:09:45.680> called<00:09:45.920> you<00:09:46.000> know<00:09:46.680> spark<00:09:47.240> the 00:09:47.310 --> 00:09:47.320 align:start position:0% has this talk called you know spark the 00:09:47.320 --> 00:09:48.829 align:start position:0% has this talk called you know spark the ultimate<00:09:47.640> scull<00:09:47.920> collections<00:09:48.320> at<00:09:48.480> Big<00:09:48.640> dat 00:09:48.829 --> 00:09:48.839 align:start position:0% ultimate scull collections at Big dat 00:09:48.839 --> 00:09:51.350 align:start position:0% ultimate scull collections at Big dat skull<00:09:49.079> in<00:09:49.160> August<00:09:49.640> and<00:09:50.000> uh<00:09:50.760> where<00:09:50.959> he<00:09:51.120> actually 00:09:51.350 --> 00:09:51.360 align:start position:0% skull in August and uh where he actually 00:09:51.360 --> 00:09:53.949 align:start position:0% skull in August and uh where he actually said<00:09:51.600> that<00:09:51.720> spark<00:09:52.000> is<00:09:52.079> a<00:09:52.240> sculla<00:09:52.560> DSL<00:09:53.399> right 00:09:53.949 --> 00:09:53.959 align:start position:0% said that spark is a sculla DSL right 00:09:53.959 --> 00:09:55.870 align:start position:0% said that spark is a sculla DSL right scull<00:09:54.279> makes<00:09:54.440> it<00:09:54.640> very<00:09:54.880> easy<00:09:55.480> to<00:09:55.640> write 00:09:55.870 --> 00:09:55.880 align:start position:0% scull makes it very easy to write 00:09:55.880 --> 00:09:57.230 align:start position:0% scull makes it very easy to write something<00:09:56.120> like<00:09:56.279> spark<00:09:56.760> right<00:09:57.079> the 00:09:57.230 --> 00:09:57.240 align:start position:0% something like spark right the 00:09:57.240 --> 00:09:59.829 align:start position:0% something like spark right the collection<00:09:57.760> interface<00:09:58.279> is<00:09:58.519> very<00:09:58.720> intuitive 00:09:59.829 --> 00:09:59.839 align:start position:0% collection interface is very intuitive 00:09:59.839 --> 00:10:02.030 align:start position:0% collection interface is very intuitive yeah<00:10:00.200> right<00:10:00.360> so<00:10:00.560> I<00:10:00.640> think<00:10:00.839> that's<00:10:00.959> a<00:10:01.160> testimony 00:10:02.030 --> 00:10:02.040 align:start position:0% yeah right so I think that's a testimony 00:10:02.040 --> 00:10:04.269 align:start position:0% yeah right so I think that's a testimony right<00:10:02.240> in<00:10:02.399> my<00:10:02.600> mind<00:10:03.000> the<00:10:03.399> reason<00:10:03.760> for<00:10:03.920> spark 00:10:04.269 --> 00:10:04.279 align:start position:0% right in my mind the reason for spark 00:10:04.279 --> 00:10:06.069 align:start position:0% right in my mind the reason for spark adoption<00:10:05.000> one<00:10:05.120> of<00:10:05.200> the<00:10:05.320> key<00:10:05.480> reasons<00:10:05.800> was<00:10:05.959> the 00:10:06.069 --> 00:10:06.079 align:start position:0% adoption one of the key reasons was the 00:10:06.079 --> 00:10:07.910 align:start position:0% adoption one of the key reasons was the Simplicity<00:10:07.000> of<00:10:07.079> the<00:10:07.200> collection<00:10:07.760> yeah 00:10:07.910 --> 00:10:07.920 align:start position:0% Simplicity of the collection yeah 00:10:07.920 --> 00:10:10.870 align:start position:0% Simplicity of the collection yeah exactly<00:10:08.399> very<00:10:08.640> good<00:10:08.839> point<00:10:09.440> and<00:10:09.560> it<00:10:09.720> was<00:10:10.480> both 00:10:10.870 --> 00:10:10.880 align:start position:0% exactly very good point and it was both 00:10:10.880 --> 00:10:13.430 align:start position:0% exactly very good point and it was both simple<00:10:11.200> to<00:10:11.399> write<00:10:11.640> such<00:10:11.800> a<00:10:11.959> DSL<00:10:12.360> in<00:10:12.560> scolar<00:10:13.279> and 00:10:13.430 --> 00:10:13.440 align:start position:0% simple to write such a DSL in scolar and 00:10:13.440 --> 00:10:15.430 align:start position:0% simple to write such a DSL in scolar and then<00:10:13.600> it's<00:10:13.800> simple<00:10:14.079> to<00:10:14.240> use<00:10:14.519> such<00:10:14.720> a<00:10:14.839> DSL<00:10:15.240> in 00:10:15.430 --> 00:10:15.440 align:start position:0% then it's simple to use such a DSL in 00:10:15.440 --> 00:10:17.509 align:start position:0% then it's simple to use such a DSL in scolar<00:10:16.200> for<00:10:16.399> people<00:10:16.640> who<00:10:16.800> have<00:10:17.000> actually<00:10:17.279> no 00:10:17.509 --> 00:10:17.519 align:start position:0% scolar for people who have actually no 00:10:17.519 --> 00:10:19.630 align:start position:0% scolar for people who have actually no idea<00:10:17.959> that<00:10:18.120> they're<00:10:18.360> using<00:10:18.640> scolar<00:10:19.160> which<00:10:19.279> is 00:10:19.630 --> 00:10:19.640 align:start position:0% idea that they're using scolar which is 00:10:19.640 --> 00:10:22.190 align:start position:0% idea that they're using scolar which is a<00:10:20.079> pretty<00:10:20.399> typical<00:10:20.760> use<00:10:20.959> of<00:10:21.120> scolar<00:10:21.519> I<00:10:21.720> see<00:10:22.040> in 00:10:22.190 --> 00:10:22.200 align:start position:0% a pretty typical use of scolar I see in 00:10:22.200 --> 00:10:25.470 align:start position:0% a pretty typical use of scolar I see in the<00:10:22.320> field<00:10:22.800> and<00:10:23.079> even<00:10:23.279> in<00:10:23.640> eBay<00:10:24.640> you<00:10:24.760> would<00:10:25.040> get 00:10:25.470 --> 00:10:25.480 align:start position:0% the field and even in eBay you would get 00:10:25.480 --> 00:10:27.430 align:start position:0% the field and even in eBay you would get people<00:10:25.720> who<00:10:25.839> are<00:10:26.040> very<00:10:26.360> familiar<00:10:26.839> with<00:10:27.240> let's 00:10:27.430 --> 00:10:27.440 align:start position:0% people who are very familiar with let's 00:10:27.440 --> 00:10:31.190 align:start position:0% people who are very familiar with let's say<00:10:27.680> r<00:10:28.200> or<00:10:28.399> matlb<00:10:29.000> or<00:10:29.360> Python<00:10:30.320> and<00:10:30.519> they<00:10:30.720> get<00:10:30.959> a 00:10:31.190 --> 00:10:31.200 align:start position:0% say r or matlb or Python and they get a 00:10:31.200 --> 00:10:33.190 align:start position:0% say r or matlb or Python and they get a spark<00:10:31.839> script<00:10:32.320> program<00:10:32.720> however<00:10:32.880> you<00:10:33.000> want<00:10:33.079> to 00:10:33.190 --> 00:10:33.200 align:start position:0% spark script program however you want to 00:10:33.200 --> 00:10:35.629 align:start position:0% spark script program however you want to call<00:10:33.360> it<00:10:33.680> and<00:10:34.160> they<00:10:34.320> just<00:10:34.800> understand<00:10:35.000> it<00:10:35.440> yes 00:10:35.629 --> 00:10:35.639 align:start position:0% call it and they just understand it yes 00:10:35.639 --> 00:10:37.550 align:start position:0% call it and they just understand it yes they<00:10:35.760> don't<00:10:35.959> even<00:10:36.440> realize<00:10:36.839> it's<00:10:37.079> scar 00:10:37.550 --> 00:10:37.560 align:start position:0% they don't even realize it's scar 00:10:37.560 --> 00:10:39.069 align:start position:0% they don't even realize it's scar because<00:10:37.800> it<00:10:37.959> just<00:10:38.120> makes<00:10:38.399> sense<00:10:38.680> oh<00:10:38.839> it's<00:10:38.920> a 00:10:39.069 --> 00:10:39.079 align:start position:0% because it just makes sense oh it's a 00:10:39.079 --> 00:10:42.269 align:start position:0% because it just makes sense oh it's a filter<00:10:39.600> it's<00:10:39.720> a<00:10:39.959> group<00:10:40.959> etc<00:10:41.360> etc<00:10:41.680> ex<00:10:41.920> exactly 00:10:42.269 --> 00:10:42.279 align:start position:0% filter it's a group etc etc ex exactly 00:10:42.279 --> 00:10:43.949 align:start position:0% filter it's a group etc etc ex exactly so<00:10:42.440> I<00:10:42.519> think<00:10:42.680> you<00:10:42.800> know<00:10:43.200> if<00:10:43.440> if<00:10:43.519> you<00:10:43.639> look<00:10:43.760> at 00:10:43.949 --> 00:10:43.959 align:start position:0% so I think you know if if you look at 00:10:43.959 --> 00:10:46.470 align:start position:0% so I think you know if if you look at subset<00:10:44.320> of<00:10:44.440> Scholars<00:10:44.880> it's<00:10:45.000> us<00:10:45.720> for<00:10:45.920> spark 00:10:46.470 --> 00:10:46.480 align:start position:0% subset of Scholars it's us for spark 00:10:46.480 --> 00:10:48.150 align:start position:0% subset of Scholars it's us for spark yeah<00:10:46.680> that's<00:10:46.800> a<00:10:46.920> very<00:10:47.120> natural<00:10:47.519> way<00:10:47.680> to<00:10:47.880> write 00:10:48.150 --> 00:10:48.160 align:start position:0% yeah that's a very natural way to write 00:10:48.160 --> 00:10:51.110 align:start position:0% yeah that's a very natural way to write data<00:10:48.440> programs<00:10:49.399> right<00:10:50.399> so<00:10:50.600> but<00:10:50.720> you're<00:10:50.880> on<00:10:51.040> the 00:10:51.110 --> 00:10:51.120 align:start position:0% data programs right so but you're on the 00:10:51.120 --> 00:10:52.670 align:start position:0% data programs right so but you're on the AR<00:10:51.399> team<00:10:51.600> and<00:10:51.720> kind<00:10:51.839> of<00:10:52.079> like<00:10:52.279> let's<00:10:52.440> kind<00:10:52.560> of 00:10:52.670 --> 00:10:52.680 align:start position:0% AR team and kind of like let's kind of 00:10:52.680 --> 00:10:54.829 align:start position:0% AR team and kind of like let's kind of make<00:10:52.800> a<00:10:52.880> connection<00:10:53.279> here<00:10:53.560> right<00:10:53.720> because<00:10:54.639> uh 00:10:54.829 --> 00:10:54.839 align:start position:0% make a connection here right because uh 00:10:54.839 --> 00:10:56.430 align:start position:0% make a connection here right because uh obviously<00:10:55.360> you<00:10:55.480> know<00:10:55.760> now<00:10:55.959> more<00:10:56.120> people<00:10:56.320> are 00:10:56.430 --> 00:10:56.440 align:start position:0% obviously you know now more people are 00:10:56.440 --> 00:10:58.190 align:start position:0% obviously you know now more people are familiar<00:10:56.880> with<00:10:57.079> spark<00:10:57.399> and<00:10:57.560> maybe<00:10:57.760> with<00:10:57.880> play 00:10:58.190 --> 00:10:58.200 align:start position:0% familiar with spark and maybe with play 00:10:58.200 --> 00:11:01.829 align:start position:0% familiar with spark and maybe with play than<00:10:58.360> with<00:10:58.519> AA<00:10:59.600> as<00:10:59.680> a<00:10:59.839> part<00:11:00.079> of<00:11:00.279> of<00:11:00.440> of<00:11:00.600> play<00:11:01.560> uh 00:11:01.829 --> 00:11:01.839 align:start position:0% than with AA as a part of of of play uh 00:11:01.839 --> 00:11:03.910 align:start position:0% than with AA as a part of of of play uh so<00:11:02.639> and<00:11:02.920> this<00:11:03.160> kind<00:11:03.279> of<00:11:03.399> a<00:11:03.560> little<00:11:03.720> bit 00:11:03.910 --> 00:11:03.920 align:start position:0% so and this kind of a little bit 00:11:03.920 --> 00:11:05.509 align:start position:0% so and this kind of a little bit different<00:11:04.240> domains<00:11:04.680> right<00:11:04.800> so<00:11:04.959> we<00:11:05.160> have<00:11:05.399> kind 00:11:05.509 --> 00:11:05.519 align:start position:0% different domains right so we have kind 00:11:05.519 --> 00:11:08.110 align:start position:0% different domains right so we have kind of<00:11:06.079> you<00:11:06.200> cannot<00:11:06.600> write<00:11:07.120> an<00:11:07.279> API<00:11:07.680> supporting<00:11:08.040> a 00:11:08.110 --> 00:11:08.120 align:start position:0% of you cannot write an API supporting a 00:11:08.120 --> 00:11:11.430 align:start position:0% of you cannot write an API supporting a million<00:11:08.519> iPhones<00:11:09.040> in<00:11:09.240> spark<00:11:09.959> yeah<00:11:10.440> uh<00:11:10.760> right 00:11:11.430 --> 00:11:11.440 align:start position:0% million iPhones in spark yeah uh right 00:11:11.440 --> 00:11:12.629 align:start position:0% million iPhones in spark yeah uh right because<00:11:11.600> of<00:11:11.760> this<00:11:12.000> kind<00:11:12.079> of<00:11:12.160> widespread<00:11:12.519> ad 00:11:12.629 --> 00:11:12.639 align:start position:0% because of this kind of widespread ad 00:11:12.639 --> 00:11:13.670 align:start position:0% because of this kind of widespread ad optional<00:11:12.880> spark<00:11:13.160> some<00:11:13.320> people<00:11:13.519> actually 00:11:13.670 --> 00:11:13.680 align:start position:0% optional spark some people actually 00:11:13.680 --> 00:11:15.069 align:start position:0% optional spark some people actually don't<00:11:13.920> realize<00:11:14.240> this<00:11:14.360> I<00:11:14.480> got<00:11:14.639> this<00:11:14.800> question 00:11:15.069 --> 00:11:15.079 align:start position:0% don't realize this I got this question 00:11:15.079 --> 00:11:17.269 align:start position:0% don't realize this I got this question you<00:11:15.200> know<00:11:15.639> why<00:11:16.040> just<00:11:16.160> use<00:11:16.360> park<00:11:16.760> right<00:11:16.880> and<00:11:17.000> so 00:11:17.269 --> 00:11:17.279 align:start position:0% you know why just use park right and so 00:11:17.279 --> 00:11:21.069 align:start position:0% you know why just use park right and so are<00:11:17.399> different<00:11:17.600> use<00:11:17.880> cases<00:11:18.560> and<00:11:18.720> so<00:11:19.600> uh<00:11:20.399> What 00:11:21.069 --> 00:11:21.079 align:start position:0% are different use cases and so uh What 00:11:21.079 --> 00:11:25.190 align:start position:0% are different use cases and so uh What uh<00:11:21.880> use<00:11:22.200> cases<00:11:22.440> do<00:11:22.560> you<00:11:22.720> see<00:11:23.120> for<00:11:23.680> AA<00:11:24.680> uh<00:11:25.000> right 00:11:25.190 --> 00:11:25.200 align:start position:0% uh use cases do you see for AA uh right 00:11:25.200 --> 00:11:27.509 align:start position:0% uh use cases do you see for AA uh right now<00:11:25.440> being<00:11:25.600> a<00:11:25.800> t<00:11:26.079> save<00:11:26.480> kind<00:11:26.600> of<00:11:26.800> how<00:11:26.959> are 00:11:27.509 --> 00:11:27.519 align:start position:0% now being a t save kind of how are 00:11:27.519 --> 00:11:29.910 align:start position:0% now being a t save kind of how are customers<00:11:27.959> using<00:11:28.279> AA<00:11:28.639> what<00:11:28.720> are<00:11:28.880> the<00:11:29.000> best 00:11:29.910 --> 00:11:29.920 align:start position:0% customers using AA what are the best 00:11:29.920 --> 00:11:33.790 align:start position:0% customers using AA what are the best situations<00:11:30.920> where<00:11:31.079> AR<00:11:31.680> shines<00:11:32.680> right<00:11:33.000> so<00:11:33.639> at 00:11:33.790 --> 00:11:33.800 align:start position:0% situations where AR shines right so at 00:11:33.800 --> 00:11:37.110 align:start position:0% situations where AR shines right so at the<00:11:33.959> core<00:11:34.200> of<00:11:34.360> it<00:11:34.800> it's<00:11:35.399> a<00:11:35.680> really<00:11:35.920> a<00:11:36.120> toolkit 00:11:37.110 --> 00:11:37.120 align:start position:0% the core of it it's a really a toolkit 00:11:37.120 --> 00:11:39.310 align:start position:0% the core of it it's a really a toolkit that<00:11:37.320> you<00:11:37.480> can<00:11:37.680> use<00:11:37.920> for<00:11:38.160> building<00:11:38.639> either 00:11:39.310 --> 00:11:39.320 align:start position:0% that you can use for building either 00:11:39.320 --> 00:11:42.230 align:start position:0% that you can use for building either highly<00:11:39.800> concurrent<00:11:40.800> or<00:11:41.120> highly<00:11:41.399> scalable<00:11:42.079> in 00:11:42.230 --> 00:11:42.240 align:start position:0% highly concurrent or highly scalable in 00:11:42.240 --> 00:11:44.870 align:start position:0% highly concurrent or highly scalable in the<00:11:42.399> sense<00:11:42.680> of<00:11:42.959> multiple<00:11:43.399> nodes<00:11:44.079> or<00:11:44.639> well<00:11:44.800> if 00:11:44.870 --> 00:11:44.880 align:start position:0% the sense of multiple nodes or well if 00:11:44.880 --> 00:11:46.790 align:start position:0% the sense of multiple nodes or well if you<00:11:44.959> want<00:11:45.079> to<00:11:45.279> stay<00:11:45.399> local<00:11:45.760> multiple<00:11:46.160> threats 00:11:46.790 --> 00:11:46.800 align:start position:0% you want to stay local multiple threats 00:11:46.800 --> 00:11:48.750 align:start position:0% you want to stay local multiple threats and<00:11:46.920> the<00:11:47.079> core<00:11:47.320> thing<00:11:47.519> about<00:11:47.720> it<00:11:48.079> is<00:11:48.440> the 00:11:48.750 --> 00:11:48.760 align:start position:0% and the core thing about it is the 00:11:48.760 --> 00:11:52.110 align:start position:0% and the core thing about it is the concept<00:11:49.760> that<00:11:49.959> you<00:11:50.399> use<00:11:50.720> to<00:11:50.920> think<00:11:51.200> about<00:11:51.480> it 00:11:52.110 --> 00:11:52.120 align:start position:0% concept that you use to think about it 00:11:52.120 --> 00:11:54.069 align:start position:0% concept that you use to think about it stays<00:11:52.519> the<00:11:52.680> same<00:11:53.079> right<00:11:53.399> because<00:11:53.639> you<00:11:53.800> only 00:11:54.069 --> 00:11:54.079 align:start position:0% stays the same right because you only 00:11:54.079 --> 00:11:56.829 align:start position:0% stays the same right because you only think<00:11:54.360> about<00:11:55.040> messaging<00:11:56.040> and<00:11:56.240> once<00:11:56.480> you 00:11:56.829 --> 00:11:56.839 align:start position:0% think about messaging and once you 00:11:56.839 --> 00:11:59.509 align:start position:0% think about messaging and once you Wroten<00:11:57.320> something<00:11:57.639> using<00:11:58.040> messaging<00:11:59.040> it<00:11:59.399> it 00:11:59.509 --> 00:11:59.519 align:start position:0% Wroten something using messaging it it 00:11:59.519 --> 00:12:01.949 align:start position:0% Wroten something using messaging it it feels<00:11:59.920> native<00:12:00.399> that<00:12:00.560> it's<00:12:00.760> concurrent<00:12:01.480> and<00:12:01.639> it 00:12:01.949 --> 00:12:01.959 align:start position:0% feels native that it's concurrent and it 00:12:01.959 --> 00:12:04.829 align:start position:0% feels native that it's concurrent and it can<00:12:02.160> be<00:12:02.360> distributed<00:12:02.959> easily<00:12:03.920> so<00:12:04.120> it's<00:12:04.320> the 00:12:04.829 --> 00:12:04.839 align:start position:0% can be distributed easily so it's the 00:12:04.839 --> 00:12:08.069 align:start position:0% can be distributed easily so it's the opposite<00:12:05.320> of<00:12:05.600> people<00:12:06.600> what<00:12:06.800> people<00:12:07.040> did<00:12:07.519> in 00:12:08.069 --> 00:12:08.079 align:start position:0% opposite of people what people did in 00:12:08.079 --> 00:12:10.269 align:start position:0% opposite of people what people did in previous<00:12:08.560> attempts<00:12:09.160> to<00:12:09.320> do<00:12:09.760> distributed 00:12:10.269 --> 00:12:10.279 align:start position:0% previous attempts to do distributed 00:12:10.279 --> 00:12:12.949 align:start position:0% previous attempts to do distributed computing<00:12:11.200> where<00:12:11.480> people<00:12:11.720> would<00:12:12.079> hide<00:12:12.760> the 00:12:12.949 --> 00:12:12.959 align:start position:0% computing where people would hide the 00:12:12.959 --> 00:12:14.910 align:start position:0% computing where people would hide the complexities<00:12:13.800> and<00:12:13.959> make<00:12:14.120> it<00:12:14.320> look<00:12:14.519> like<00:12:14.639> a 00:12:14.910 --> 00:12:14.920 align:start position:0% complexities and make it look like a 00:12:14.920 --> 00:12:18.230 align:start position:0% complexities and make it look like a method<00:12:15.920> which<00:12:16.120> we<00:12:16.279> believe<00:12:16.639> is<00:12:17.079> a<00:12:17.839> well<00:12:18.120> the 00:12:18.230 --> 00:12:18.240 align:start position:0% method which we believe is a well the 00:12:18.240 --> 00:12:20.310 align:start position:0% method which we believe is a well the wrong<00:12:18.480> thing<00:12:18.639> to<00:12:18.800> go<00:12:19.040> about<00:12:19.240> it<00:12:19.519> because<00:12:20.160> well 00:12:20.310 --> 00:12:20.320 align:start position:0% wrong thing to go about it because well 00:12:20.320 --> 00:12:21.990 align:start position:0% wrong thing to go about it because well it<00:12:20.440> doesn't<00:12:20.760> behave<00:12:21.079> like<00:12:21.199> a<00:12:21.399> method<00:12:21.760> because 00:12:21.990 --> 00:12:22.000 align:start position:0% it doesn't behave like a method because 00:12:22.000 --> 00:12:24.069 align:start position:0% it doesn't behave like a method because there's<00:12:22.199> latencies<00:12:22.800> involved<00:12:23.800> however<00:12:23.959> when 00:12:24.069 --> 00:12:24.079 align:start position:0% there's latencies involved however when 00:12:24.079 --> 00:12:26.150 align:start position:0% there's latencies involved however when you<00:12:24.199> turn<00:12:24.360> it<00:12:24.560> around<00:12:25.199> and<00:12:25.600> you<00:12:25.760> make 00:12:26.150 --> 00:12:26.160 align:start position:0% you turn it around and you make 00:12:26.160 --> 00:12:28.550 align:start position:0% you turn it around and you make messaging<00:12:26.680> a<00:12:26.839> first<00:12:27.120> class<00:12:27.360> citizen<00:12:28.360> now 00:12:28.550 --> 00:12:28.560 align:start position:0% messaging a first class citizen now 00:12:28.560 --> 00:12:31.590 align:start position:0% messaging a first class citizen now suddenly<00:12:28.920> you<00:12:29.519> all<00:12:29.760> the<00:12:30.000> time<00:12:30.760> realize<00:12:31.360> well 00:12:31.590 --> 00:12:31.600 align:start position:0% suddenly you all the time realize well 00:12:31.600 --> 00:12:33.870 align:start position:0% suddenly you all the time realize well there's<00:12:31.880> going<00:12:32.079> to<00:12:32.240> be<00:12:32.399> some<00:12:32.680> latency<00:12:33.680> and 00:12:33.870 --> 00:12:33.880 align:start position:0% there's going to be some latency and 00:12:33.880 --> 00:12:35.350 align:start position:0% there's going to be some latency and when<00:12:34.040> I'm<00:12:34.279> distributed<00:12:34.880> there<00:12:35.040> may<00:12:35.160> be 00:12:35.350 --> 00:12:35.360 align:start position:0% when I'm distributed there may be 00:12:35.360 --> 00:12:38.350 align:start position:0% when I'm distributed there may be message<00:12:35.680> loss<00:12:36.480> and<00:12:36.639> now<00:12:36.760> it's<00:12:37.320> it<00:12:37.480> feels<00:12:38.000> right 00:12:38.350 --> 00:12:38.360 align:start position:0% message loss and now it's it feels right 00:12:38.360 --> 00:12:40.189 align:start position:0% message loss and now it's it feels right it<00:12:38.519> makes<00:12:38.800> sense<00:12:39.160> and<00:12:39.279> it's<00:12:39.440> not<00:12:39.639> surprising 00:12:40.189 --> 00:12:40.199 align:start position:0% it makes sense and it's not surprising 00:12:40.199 --> 00:12:43.870 align:start position:0% it makes sense and it's not surprising anymore<00:12:40.680> MH<00:12:41.399> so<00:12:41.800> what<00:12:42.000> we<00:12:42.560> see<00:12:42.959> people<00:12:43.240> use<00:12:43.480> AA 00:12:43.870 --> 00:12:43.880 align:start position:0% anymore MH so what we see people use AA 00:12:43.880 --> 00:12:46.870 align:start position:0% anymore MH so what we see people use AA for<00:12:44.399> is<00:12:45.399> um<00:12:45.600> when<00:12:45.800> they<00:12:45.920> need<00:12:46.199> High<00:12:46.360> throughput 00:12:46.870 --> 00:12:46.880 align:start position:0% for is um when they need High throughput 00:12:46.880 --> 00:12:49.430 align:start position:0% for is um when they need High throughput applications<00:12:47.760> or<00:12:47.959> they<00:12:48.120> need<00:12:48.920> really<00:12:49.160> to 00:12:49.430 --> 00:12:49.440 align:start position:0% applications or they need really to 00:12:49.440 --> 00:12:52.710 align:start position:0% applications or they need really to react<00:12:50.320> uh<00:12:50.480> very<00:12:50.800> dynamically<00:12:51.639> to<00:12:52.040> to<00:12:52.279> incoming 00:12:52.710 --> 00:12:52.720 align:start position:0% react uh very dynamically to to incoming 00:12:52.720 --> 00:12:54.750 align:start position:0% react uh very dynamically to to incoming load<00:12:53.199> like<00:12:53.399> today<00:12:53.680> we<00:12:53.800> have<00:12:53.920> a<00:12:54.079> talk<00:12:54.399> by<00:12:54.600> the 00:12:54.750 --> 00:12:54.760 align:start position:0% load like today we have a talk by the 00:12:54.760 --> 00:12:58.269 align:start position:0% load like today we have a talk by the guil<00:12:55.399> uh<00:12:55.800> no<00:12:56.000> the<00:12:56.199> zelando<00:12:56.839> guys<00:12:57.839> um<00:12:58.000> but<00:12:58.160> they 00:12:58.269 --> 00:12:58.279 align:start position:0% guil uh no the zelando guys um but they 00:12:58.279 --> 00:13:00.990 align:start position:0% guil uh no the zelando guys um but they have<00:12:58.399> a<00:12:58.560> very<00:12:58.720> similar<00:12:59.399> examp<00:13:00.120> use<00:13:00.480> case<00:13:00.680> to 00:13:00.990 --> 00:13:01.000 align:start position:0% have a very similar examp use case to 00:13:01.000 --> 00:13:03.389 align:start position:0% have a very similar examp use case to what<00:13:01.160> guilt<00:13:01.480> has<00:13:01.920> right<00:13:02.120> they<00:13:02.240> do<00:13:02.440> flash<00:13:02.800> sales 00:13:03.389 --> 00:13:03.399 align:start position:0% what guilt has right they do flash sales 00:13:03.399 --> 00:13:05.550 align:start position:0% what guilt has right they do flash sales right<00:13:03.639> yes<00:13:04.000> so<00:13:04.160> I<00:13:04.240> want<00:13:04.399> to<00:13:04.600> scale<00:13:04.920> up<00:13:05.079> to<00:13:05.240> a<00:13:05.320> few 00:13:05.550 --> 00:13:05.560 align:start position:0% right yes so I want to scale up to a few 00:13:05.560 --> 00:13:07.550 align:start position:0% right yes so I want to scale up to a few thousand<00:13:05.920> nodes<00:13:06.440> but<00:13:06.600> only<00:13:06.800> basically<00:13:07.199> for<00:13:07.399> an 00:13:07.550 --> 00:13:07.560 align:start position:0% thousand nodes but only basically for an 00:13:07.560 --> 00:13:09.590 align:start position:0% thousand nodes but only basically for an hour<00:13:08.120> and<00:13:08.240> then<00:13:08.360> I<00:13:08.440> want<00:13:08.560> to<00:13:08.680> scale<00:13:09.040> down<00:13:09.279> again 00:13:09.590 --> 00:13:09.600 align:start position:0% hour and then I want to scale down again 00:13:09.600 --> 00:13:10.910 align:start position:0% hour and then I want to scale down again that's<00:13:09.680> why<00:13:09.760> I<00:13:09.839> want<00:13:09.959> to<00:13:10.000> be<00:13:10.120> on<00:13:10.199> Amazon<00:13:10.680> so<00:13:10.800> I 00:13:10.910 --> 00:13:10.920 align:start position:0% that's why I want to be on Amazon so I 00:13:10.920 --> 00:13:13.750 align:start position:0% that's why I want to be on Amazon so I can<00:13:11.399> yeah<00:13:11.760> boom<00:13:12.120> you<00:13:12.240> just<00:13:12.399> add<00:13:12.560> the<00:13:12.680> noes<00:13:13.600> they 00:13:13.750 --> 00:13:13.760 align:start position:0% can yeah boom you just add the noes they 00:13:13.760 --> 00:13:15.990 align:start position:0% can yeah boom you just add the noes they spread<00:13:14.079> the<00:13:14.240> load<00:13:14.600> and<00:13:14.760> then<00:13:15.000> you<00:13:15.480> collapse 00:13:15.990 --> 00:13:16.000 align:start position:0% spread the load and then you collapse 00:13:16.000 --> 00:13:18.110 align:start position:0% spread the load and then you collapse again<00:13:16.720> and<00:13:16.880> these<00:13:17.040> are<00:13:17.240> exactly<00:13:17.600> the<00:13:17.720> use 00:13:18.110 --> 00:13:18.120 align:start position:0% again and these are exactly the use 00:13:18.120 --> 00:13:20.790 align:start position:0% again and these are exactly the use cases<00:13:18.600> AO<00:13:19.000> Rel<00:13:19.320> shines<00:13:19.839> because<00:13:20.040> of<00:13:20.199> the<00:13:20.440> fast 00:13:20.790 --> 00:13:20.800 align:start position:0% cases AO Rel shines because of the fast 00:13:20.800 --> 00:13:23.150 align:start position:0% cases AO Rel shines because of the fast messaging<00:13:21.600> the<00:13:21.839> fast<00:13:22.440> connection<00:13:22.839> of<00:13:22.959> the 00:13:23.150 --> 00:13:23.160 align:start position:0% messaging the fast connection of the 00:13:23.160 --> 00:13:24.990 align:start position:0% messaging the fast connection of the cluster<00:13:23.600> I<00:13:23.680> mean<00:13:23.920> the<00:13:24.079> last<00:13:24.320> time<00:13:24.480> we 00:13:24.990 --> 00:13:25.000 align:start position:0% cluster I mean the last time we 00:13:25.000 --> 00:13:27.790 align:start position:0% cluster I mean the last time we benchmarked<00:13:26.000> how<00:13:26.360> fast<00:13:26.680> a<00:13:26.880> cluster<00:13:27.440> can 00:13:27.790 --> 00:13:27.800 align:start position:0% benchmarked how fast a cluster can 00:13:27.800 --> 00:13:30.829 align:start position:0% benchmarked how fast a cluster can connect<00:13:28.240> multi<00:13:28.639> more<00:13:28.839> notes<00:13:29.440> into<00:13:29.720> it<00:13:30.560> we<00:13:30.720> did 00:13:30.829 --> 00:13:30.839 align:start position:0% connect multi more notes into it we did 00:13:30.839 --> 00:13:33.670 align:start position:0% connect multi more notes into it we did a<00:13:31.000> benchmark<00:13:31.760> on<00:13:32.480> Google's<00:13:32.880> compute<00:13:33.240> engine 00:13:33.670 --> 00:13:33.680 align:start position:0% a benchmark on Google's compute engine 00:13:33.680 --> 00:13:36.710 align:start position:0% a benchmark on Google's compute engine and<00:13:33.839> I<00:13:33.959> think<00:13:34.079> we<00:13:34.199> scaled<00:13:34.600> up<00:13:34.760> to<00:13:35.160> 5,000<00:13:35.880> noes 00:13:36.710 --> 00:13:36.720 align:start position:0% and I think we scaled up to 5,000 noes 00:13:36.720 --> 00:13:39.949 align:start position:0% and I think we scaled up to 5,000 noes in<00:13:37.279> 2<00:13:37.519> minutes<00:13:38.320> which<00:13:38.440> is<00:13:38.639> including<00:13:39.199> starting 00:13:39.949 --> 00:13:39.959 align:start position:0% in 2 minutes which is including starting 00:13:39.959 --> 00:13:42.990 align:start position:0% in 2 minutes which is including starting the<00:13:40.120> nodes<00:13:40.880> W<00:13:41.800> so<00:13:42.279> that's<00:13:42.440> pretty<00:13:42.560> impressive 00:13:42.990 --> 00:13:43.000 align:start position:0% the nodes W so that's pretty impressive 00:13:43.000 --> 00:13:44.629 align:start position:0% the nodes W so that's pretty impressive the<00:13:43.120> latency<00:13:43.600> of<00:13:43.760> joining<00:13:44.079> nodes<00:13:44.399> to<00:13:44.519> the 00:13:44.629 --> 00:13:44.639 align:start position:0% the latency of joining nodes to the 00:13:44.639 --> 00:13:46.230 align:start position:0% the latency of joining nodes to the cluster<00:13:45.000> and<00:13:45.160> they're<00:13:45.360> ready<00:13:45.600> to<00:13:45.720> serve<00:13:46.079> the 00:13:46.230 --> 00:13:46.240 align:start position:0% cluster and they're ready to serve the 00:13:46.240 --> 00:13:49.550 align:start position:0% cluster and they're ready to serve the requests<00:13:46.680> is<00:13:47.000> really<00:13:47.800> really<00:13:48.079> low 00:13:49.550 --> 00:13:49.560 align:start position:0% requests is really really low 00:13:49.560 --> 00:13:52.749 align:start position:0% requests is really really low interesting<00:13:50.560> so<00:13:51.079> uh<00:13:51.240> so<00:13:51.480> in<00:13:51.720> in<00:13:51.920> in<00:13:52.079> scard<00:13:52.639> We 00:13:52.749 --> 00:13:52.759 align:start position:0% interesting so uh so in in in scard We 00:13:52.759 --> 00:13:55.230 align:start position:0% interesting so uh so in in in scard We have<00:13:52.920> basically<00:13:53.360> two<00:13:53.720> major<00:13:54.040> Frameworks<00:13:54.600> for 00:13:55.230 --> 00:13:55.240 align:start position:0% have basically two major Frameworks for 00:13:55.240 --> 00:13:57.470 align:start position:0% have basically two major Frameworks for RPC<00:13:55.720> we<00:13:55.839> have<00:13:55.959> AR<00:13:56.199> we<00:13:56.279> have<00:13:56.399> finagle<00:13:57.079> I<00:13:57.160> don't 00:13:57.470 --> 00:13:57.480 align:start position:0% RPC we have AR we have finagle I don't 00:13:57.480 --> 00:13:58.590 align:start position:0% RPC we have AR we have finagle I don't know<00:13:57.680> how<00:13:57.800> much<00:13:57.959> experience<00:13:58.279> we<00:13:58.399> have<00:13:58.480> with 00:13:58.590 --> 00:13:58.600 align:start position:0% know how much experience we have with 00:13:58.600 --> 00:14:00.710 align:start position:0% know how much experience we have with finagle<00:13:59.199> a<00:13:59.320> little<00:13:59.519> bit<00:13:59.959> yeah<00:14:00.279> and<00:14:00.399> so<00:14:00.600> you 00:14:00.710 --> 00:14:00.720 align:start position:0% finagle a little bit yeah and so you 00:14:00.720 --> 00:14:02.389 align:start position:0% finagle a little bit yeah and so you know<00:14:00.880> in<00:14:01.000> the<00:14:01.160> summer<00:14:01.600> we<00:14:01.800> did<00:14:02.040> actually<00:14:02.279> the 00:14:02.389 --> 00:14:02.399 align:start position:0% know in the summer we did actually the 00:14:02.399 --> 00:14:04.629 align:start position:0% know in the summer we did actually the first<00:14:02.600> finagle<00:14:03.320> conference<00:14:03.759> as<00:14:03.880> a<00:14:04.279> schar<00:14:04.519> by 00:14:04.629 --> 00:14:04.639 align:start position:0% first finagle conference as a schar by 00:14:04.639 --> 00:14:05.749 align:start position:0% first finagle conference as a schar by the<00:14:04.720> way<00:14:05.000> and<00:14:05.160> kind<00:14:05.279> of<00:14:05.440> it's<00:14:05.560> very 00:14:05.749 --> 00:14:05.759 align:start position:0% the way and kind of it's very 00:14:05.759 --> 00:14:08.550 align:start position:0% the way and kind of it's very interesting<00:14:06.440> I'm<00:14:06.680> curious<00:14:07.480> uh<00:14:07.880> kind<00:14:08.040> of<00:14:08.440> this 00:14:08.550 --> 00:14:08.560 align:start position:0% interesting I'm curious uh kind of this 00:14:08.560 --> 00:14:12.550 align:start position:0% interesting I'm curious uh kind of this just<00:14:08.720> two<00:14:09.079> different<00:14:10.079> uh<00:14:10.399> ways<00:14:10.880> of<00:14:11.279> writing<00:14:12.279> uh 00:14:12.550 --> 00:14:12.560 align:start position:0% just two different uh ways of writing uh 00:14:12.560 --> 00:14:15.670 align:start position:0% just two different uh ways of writing uh programs<00:14:13.440> you<00:14:13.600> know<00:14:14.199> how<00:14:14.480> would<00:14:14.639> one<00:14:14.880> approach 00:14:15.670 --> 00:14:15.680 align:start position:0% programs you know how would one approach 00:14:15.680 --> 00:14:18.629 align:start position:0% programs you know how would one approach kind<00:14:15.839> of<00:14:16.560> picking<00:14:16.880> one<00:14:17.160> versus<00:14:17.560> the<00:14:17.759> other 00:14:18.629 --> 00:14:18.639 align:start position:0% kind of picking one versus the other 00:14:18.639 --> 00:14:20.550 align:start position:0% kind of picking one versus the other kind<00:14:18.759> of<00:14:19.240> like<00:14:19.720> not<00:14:19.880> really<00:14:20.079> seen<00:14:20.360> this 00:14:20.550 --> 00:14:20.560 align:start position:0% kind of like not really seen this 00:14:20.560 --> 00:14:22.829 align:start position:0% kind of like not really seen this communities<00:14:21.399> overlap<00:14:21.959> much<00:14:22.240> because<00:14:22.480> I<00:14:22.600> think 00:14:22.829 --> 00:14:22.839 align:start position:0% communities overlap much because I think 00:14:22.839 --> 00:14:24.670 align:start position:0% communities overlap much because I think it<00:14:23.199> finagle<00:14:23.639> in<00:14:23.800> Twitter<00:14:24.199> develops 00:14:24.670 --> 00:14:24.680 align:start position:0% it finagle in Twitter develops 00:14:24.680 --> 00:14:26.629 align:start position:0% it finagle in Twitter develops separately<00:14:25.199> but<00:14:25.600> and<00:14:25.839> now<00:14:25.959> it<00:14:26.120> gets<00:14:26.279> more<00:14:26.399> into 00:14:26.629 --> 00:14:26.639 align:start position:0% separately but and now it gets more into 00:14:26.639 --> 00:14:28.509 align:start position:0% separately but and now it gets more into mainam<00:14:27.040> there<00:14:27.120> are<00:14:27.240> some<00:14:27.360> customers<00:14:28.000> finagle 00:14:28.509 --> 00:14:28.519 align:start position:0% mainam there are some customers finagle 00:14:28.519 --> 00:14:29.870 align:start position:0% mainam there are some customers finagle how<00:14:28.600> would<00:14:28.720> you<00:14:28.800> compare<00:14:29.199> the<00:14:29.320> two<00:14:29.480> things<00:14:29.680> and 00:14:29.870 --> 00:14:29.880 align:start position:0% how would you compare the two things and 00:14:29.880 --> 00:14:31.670 align:start position:0% how would you compare the two things and kind<00:14:30.000> of<00:14:30.079> like<00:14:30.240> when<00:14:30.360> one<00:14:30.519> should<00:14:30.720> use<00:14:31.000> what<00:14:31.600> I 00:14:31.670 --> 00:14:31.680 align:start position:0% kind of like when one should use what I 00:14:31.680 --> 00:14:35.310 align:start position:0% kind of like when one should use what I think<00:14:31.920> now<00:14:32.560> uh<00:14:32.800> now<00:14:33.480> especially<00:14:34.000> it<00:14:34.160> will<00:14:34.399> be<00:14:35.120> a 00:14:35.310 --> 00:14:35.320 align:start position:0% think now uh now especially it will be a 00:14:35.320 --> 00:14:38.189 align:start position:0% think now uh now especially it will be a little<00:14:35.920> bit<00:14:36.279> closer<00:14:37.079> in<00:14:37.240> terms<00:14:37.560> of<00:14:37.759> usage 00:14:38.189 --> 00:14:38.199 align:start position:0% little bit closer in terms of usage 00:14:38.199 --> 00:14:40.269 align:start position:0% little bit closer in terms of usage patterns<00:14:38.800> especially<00:14:39.320> because<00:14:39.600> we<00:14:39.720> have<00:14:39.880> AKA 00:14:40.269 --> 00:14:40.279 align:start position:0% patterns especially because we have AKA 00:14:40.279 --> 00:14:43.990 align:start position:0% patterns especially because we have AKA streams<00:14:41.160> and<00:14:41.440> AKA<00:14:41.720> HTTP<00:14:42.320> based<00:14:42.560> on<00:14:42.680> AA<00:14:43.000> streams 00:14:43.990 --> 00:14:44.000 align:start position:0% streams and AKA HTTP based on AA streams 00:14:44.000 --> 00:14:45.590 align:start position:0% streams and AKA HTTP based on AA streams and<00:14:44.199> both<00:14:44.360> of<00:14:44.519> these<00:14:44.800> based<00:14:45.079> on<00:14:45.240> reactive 00:14:45.590 --> 00:14:45.600 align:start position:0% and both of these based on reactive 00:14:45.600 --> 00:14:48.470 align:start position:0% and both of these based on reactive streams<00:14:46.480> which<00:14:46.600> I'm<00:14:46.800> talking<00:14:47.120> about<00:14:47.320> today<00:14:47.800> M 00:14:48.470 --> 00:14:48.480 align:start position:0% streams which I'm talking about today M 00:14:48.480 --> 00:14:51.310 align:start position:0% streams which I'm talking about today M so<00:14:48.800> the<00:14:49.000> core<00:14:49.279> about<00:14:49.600> these<00:14:49.959> thing<00:14:50.320> these<00:14:50.639> apis 00:14:51.310 --> 00:14:51.320 align:start position:0% so the core about these thing these apis 00:14:51.320 --> 00:14:54.829 align:start position:0% so the core about these thing these apis is<00:14:51.639> one<00:14:52.240> they're<00:14:52.800> type<00:14:53.160> safe<00:14:53.800> as<00:14:53.959> in<00:14:54.480> you<00:14:54.639> have 00:14:54.829 --> 00:14:54.839 align:start position:0% is one they're type safe as in you have 00:14:54.839 --> 00:14:56.430 align:start position:0% is one they're type safe as in you have the<00:14:55.000> actual<00:14:55.360> types<00:14:55.560> of<00:14:55.720> messages<00:14:56.160> you<00:14:56.279> can 00:14:56.430 --> 00:14:56.440 align:start position:0% the actual types of messages you can 00:14:56.440 --> 00:14:58.590 align:start position:0% the actual types of messages you can handle<00:14:57.160> which<00:14:57.279> was<00:14:57.480> the<00:14:57.680> usual<00:14:58.120> complaint 00:14:58.590 --> 00:14:58.600 align:start position:0% handle which was the usual complaint 00:14:58.600 --> 00:14:59.550 align:start position:0% handle which was the usual complaint against 00:14:59.550 --> 00:14:59.560 align:start position:0% against 00:14:59.560 --> 00:15:02.350 align:start position:0% against yes<00:15:00.240> so<00:15:00.600> we<00:15:00.759> do<00:15:00.959> have<00:15:01.199> addressed<00:15:01.759> that<00:15:01.959> one<00:15:02.199> in 00:15:02.350 --> 00:15:02.360 align:start position:0% yes so we do have addressed that one in 00:15:02.360 --> 00:15:04.150 align:start position:0% yes so we do have addressed that one in the<00:15:02.480> new<00:15:02.680> apis<00:15:03.279> is<00:15:03.360> it<00:15:03.480> now<00:15:03.639> the<00:15:03.759> recommended 00:15:04.150 --> 00:15:04.160 align:start position:0% the new apis is it now the recommended 00:15:04.160 --> 00:15:07.030 align:start position:0% the new apis is it now the recommended API<00:15:04.519> the<00:15:04.680> mainstream<00:15:05.680> yes<00:15:05.839> and<00:15:06.079> no<00:15:06.519> so<00:15:06.759> for 00:15:07.030 --> 00:15:07.040 align:start position:0% API the mainstream yes and no so for 00:15:07.040 --> 00:15:10.150 align:start position:0% API the mainstream yes and no so for certain<00:15:07.440> patterns<00:15:07.920> if<00:15:08.040> you<00:15:08.199> have<00:15:08.959> a<00:15:09.959> a 00:15:10.150 --> 00:15:10.160 align:start position:0% certain patterns if you have a a 00:15:10.160 --> 00:15:12.310 align:start position:0% certain patterns if you have a a communication<00:15:10.920> pattern<00:15:11.480> that<00:15:11.639> looks<00:15:11.959> more<00:15:12.160> or 00:15:12.310 --> 00:15:12.320 align:start position:0% communication pattern that looks more or 00:15:12.320 --> 00:15:14.110 align:start position:0% communication pattern that looks more or less<00:15:12.560> like<00:15:12.680> a<00:15:12.880> pipeline<00:15:13.320> so<00:15:13.560> stuff<00:15:13.800> coming 00:15:14.110 --> 00:15:14.120 align:start position:0% less like a pipeline so stuff coming 00:15:14.120 --> 00:15:16.629 align:start position:0% less like a pipeline so stuff coming from<00:15:14.360> this<00:15:14.560> end<00:15:15.040> to<00:15:15.240> the<00:15:15.360> other<00:15:15.600> end<00:15:16.199> then<00:15:16.440> yeah 00:15:16.629 --> 00:15:16.639 align:start position:0% from this end to the other end then yeah 00:15:16.639 --> 00:15:18.470 align:start position:0% from this end to the other end then yeah definitely<00:15:17.240> this<00:15:17.360> is<00:15:17.480> the<00:15:17.680> thing<00:15:17.839> we<00:15:17.959> do<00:15:18.199> want 00:15:18.470 --> 00:15:18.480 align:start position:0% definitely this is the thing we do want 00:15:18.480 --> 00:15:20.710 align:start position:0% definitely this is the thing we do want people<00:15:18.720> to<00:15:18.880> use<00:15:19.199> for<00:15:19.600> these<00:15:19.839> kinds<00:15:20.040> of<00:15:20.199> things 00:15:20.710 --> 00:15:20.720 align:start position:0% people to use for these kinds of things 00:15:20.720 --> 00:15:23.389 align:start position:0% people to use for these kinds of things however<00:15:21.399> AKA<00:15:21.920> still<00:15:22.240> really<00:15:22.519> shines<00:15:23.120> if<00:15:23.240> you 00:15:23.389 --> 00:15:23.399 align:start position:0% however AKA still really shines if you 00:15:23.399 --> 00:15:26.949 align:start position:0% however AKA still really shines if you have<00:15:23.519> a<00:15:23.680> mesh<00:15:24.399> like<00:15:24.959> thing<00:15:25.920> right<00:15:26.399> for<00:15:26.600> example 00:15:26.949 --> 00:15:26.959 align:start position:0% have a mesh like thing right for example 00:15:26.959 --> 00:15:27.790 align:start position:0% have a mesh like thing right for example if<00:15:27.040> you're 00:15:27.790 --> 00:15:27.800 align:start position:0% if you're 00:15:27.800 --> 00:15:30.350 align:start position:0% if you're modeling<00:15:28.800> uh<00:15:29.199> devices<00:15:29.680> talking<00:15:30.000> to<00:15:30.199> one 00:15:30.350 --> 00:15:30.360 align:start position:0% modeling uh devices talking to one 00:15:30.360 --> 00:15:32.629 align:start position:0% modeling uh devices talking to one another<00:15:31.000> or<00:15:31.160> you're<00:15:31.360> doing<00:15:31.600> a<00:15:31.800> simulation 00:15:32.629 --> 00:15:32.639 align:start position:0% another or you're doing a simulation 00:15:32.639 --> 00:15:35.030 align:start position:0% another or you're doing a simulation that<00:15:33.120> you<00:15:33.199> know<00:15:33.480> you're<00:15:33.880> bring<00:15:34.079> up<00:15:34.279> completely 00:15:35.030 --> 00:15:35.040 align:start position:0% that you know you're bring up completely 00:15:35.040 --> 00:15:37.350 align:start position:0% that you know you're bring up completely unpredictable<00:15:35.680> device<00:15:36.279> correct<00:15:36.759> yeah<00:15:37.199> and 00:15:37.350 --> 00:15:37.360 align:start position:0% unpredictable device correct yeah and 00:15:37.360 --> 00:15:39.350 align:start position:0% unpredictable device correct yeah and it's<00:15:37.720> you<00:15:37.839> know<00:15:38.040> you<00:15:38.160> cannot<00:15:38.519> set<00:15:38.720> it<00:15:38.839> up<00:15:39.120> up 00:15:39.350 --> 00:15:39.360 align:start position:0% it's you know you cannot set it up up 00:15:39.360 --> 00:15:41.110 align:start position:0% it's you know you cannot set it up up front<00:15:39.920> because<00:15:40.160> you<00:15:40.279> don't<00:15:40.480> know<00:15:40.680> what<00:15:40.800> it<00:15:40.920> is 00:15:41.110 --> 00:15:41.120 align:start position:0% front because you don't know what it is 00:15:41.120 --> 00:15:44.110 align:start position:0% front because you don't know what it is up<00:15:41.319> front<00:15:41.839> yes<00:15:42.160> and<00:15:42.279> in<00:15:42.720> these<00:15:43.079> situations<00:15:43.759> AKA 00:15:44.110 --> 00:15:44.120 align:start position:0% up front yes and in these situations AKA 00:15:44.120 --> 00:15:45.990 align:start position:0% up front yes and in these situations AKA really<00:15:44.279> shines<00:15:44.720> because<00:15:45.000> it's<00:15:45.240> so<00:15:45.519> Dynamic 00:15:45.990 --> 00:15:46.000 align:start position:0% really shines because it's so Dynamic 00:15:46.000 --> 00:15:49.110 align:start position:0% really shines because it's so Dynamic nature<00:15:46.720> and<00:15:47.079> other<00:15:47.360> Frameworks<00:15:48.279> um<00:15:48.680> including 00:15:49.110 --> 00:15:49.120 align:start position:0% nature and other Frameworks um including 00:15:49.120 --> 00:15:51.269 align:start position:0% nature and other Frameworks um including AA<00:15:49.480> streams<00:15:49.880> and<00:15:50.040> finagle<00:15:50.720> and<00:15:50.880> stuff<00:15:51.120> like 00:15:51.269 --> 00:15:51.279 align:start position:0% AA streams and finagle and stuff like 00:15:51.279 --> 00:15:52.949 align:start position:0% AA streams and finagle and stuff like that<00:15:51.440> they're<00:15:51.920> really<00:15:52.120> not<00:15:52.279> meant<00:15:52.519> for<00:15:52.680> Pure 00:15:52.949 --> 00:15:52.959 align:start position:0% that they're really not meant for Pure 00:15:52.959 --> 00:15:56.389 align:start position:0% that they're really not meant for Pure top<00:15:53.440> stuff<00:15:54.120> it's<00:15:54.480> I<00:15:54.639> take<00:15:55.240> in<00:15:55.440> finagle<00:15:56.000> case<00:15:56.240> a 00:15:56.389 --> 00:15:56.399 align:start position:0% top stuff it's I take in finagle case a 00:15:56.399 --> 00:15:59.110 align:start position:0% top stuff it's I take in finagle case a future<00:15:57.199> and<00:15:57.319> I<00:15:57.440> transform<00:15:57.920> a<00:15:58.079> future<00:15:59.000> and 00:15:59.110 --> 00:15:59.120 align:start position:0% future and I transform a future and 00:15:59.120 --> 00:16:00.829 align:start position:0% future and I transform a future and eventually<00:15:59.440> it's<00:15:59.519> going<00:15:59.639> to<00:15:59.720> be<00:15:59.880> a<00:16:00.040> response 00:16:00.829 --> 00:16:00.839 align:start position:0% eventually it's going to be a response 00:16:00.839 --> 00:16:02.710 align:start position:0% eventually it's going to be a response yes<00:16:01.120> so<00:16:01.279> we<00:16:01.399> take<00:16:01.600> it<00:16:01.800> a<00:16:01.920> little<00:16:02.120> bit<00:16:02.279> further 00:16:02.710 --> 00:16:02.720 align:start position:0% yes so we take it a little bit further 00:16:02.720 --> 00:16:05.150 align:start position:0% yes so we take it a little bit further with<00:16:02.880> a<00:16:03.160> htdp<00:16:04.160> so<00:16:04.360> we<00:16:04.480> don't<00:16:04.680> say<00:16:04.880> it's<00:16:05.000> a 00:16:05.150 --> 00:16:05.160 align:start position:0% with a htdp so we don't say it's a 00:16:05.160 --> 00:16:08.069 align:start position:0% with a htdp so we don't say it's a future<00:16:06.120> we<00:16:06.240> say<00:16:06.480> it's<00:16:06.600> a<00:16:06.800> continuous<00:16:07.480> stream 00:16:08.069 --> 00:16:08.079 align:start position:0% future we say it's a continuous stream 00:16:08.079 --> 00:16:12.189 align:start position:0% future we say it's a continuous stream of<00:16:08.759> something<00:16:09.759> an<00:16:09.959> example<00:16:10.399> being<00:16:11.319> an<00:16:11.519> HTTP 00:16:12.189 --> 00:16:12.199 align:start position:0% of something an example being an HTTP 00:16:12.199 --> 00:16:15.790 align:start position:0% of something an example being an HTTP server<00:16:12.800> is<00:16:13.360> a<00:16:13.519> stream<00:16:13.959> of<00:16:14.160> incoming<00:16:14.959> requests 00:16:15.790 --> 00:16:15.800 align:start position:0% server is a stream of incoming requests 00:16:15.800 --> 00:16:18.749 align:start position:0% server is a stream of incoming requests and<00:16:16.000> they<00:16:16.160> stream<00:16:16.480> of<00:16:16.639> outgoing<00:16:17.319> responses<00:16:18.160> M 00:16:18.749 --> 00:16:18.759 align:start position:0% and they stream of outgoing responses M 00:16:18.759 --> 00:16:20.749 align:start position:0% and they stream of outgoing responses M and<00:16:18.959> this<00:16:19.440> really<00:16:19.720> allows<00:16:20.079> for<00:16:20.319> a<00:16:20.440> lot<00:16:20.600> of 00:16:20.749 --> 00:16:20.759 align:start position:0% and this really allows for a lot of 00:16:20.759 --> 00:16:22.550 align:start position:0% and this really allows for a lot of interesting 00:16:22.550 --> 00:16:22.560 align:start position:0% interesting 00:16:22.560 --> 00:16:24.710 align:start position:0% interesting implementation<00:16:23.560> kind<00:16:23.720> of<00:16:23.920> details<00:16:24.480> which 00:16:24.710 --> 00:16:24.720 align:start position:0% implementation kind of details which 00:16:24.720 --> 00:16:28.309 align:start position:0% implementation kind of details which affect<00:16:25.279> the<00:16:25.480> usage<00:16:26.000> of<00:16:26.480> these<00:16:26.959> tools<00:16:27.759> so 00:16:28.309 --> 00:16:28.319 align:start position:0% affect the usage of these tools so 00:16:28.319 --> 00:16:31.030 align:start position:0% affect the usage of these tools so basically<00:16:28.680> what<00:16:28.959> we<00:16:29.120> say<00:16:29.800> well<00:16:30.000> HTTP<00:16:30.639> is<00:16:30.880> such 00:16:31.030 --> 00:16:31.040 align:start position:0% basically what we say well HTTP is such 00:16:31.040 --> 00:16:33.670 align:start position:0% basically what we say well HTTP is such a<00:16:31.199> flow<00:16:31.560> of<00:16:31.759> incoming<00:16:32.519> requests<00:16:33.000> to<00:16:33.319> in 00:16:33.670 --> 00:16:33.680 align:start position:0% a flow of incoming requests to in 00:16:33.680 --> 00:16:36.550 align:start position:0% a flow of incoming requests to in outcoming<00:16:34.399> responses<00:16:35.120> yes<00:16:35.319> so<00:16:35.480> far<00:16:35.680> so<00:16:35.880> easy 00:16:36.550 --> 00:16:36.560 align:start position:0% outcoming responses yes so far so easy 00:16:36.560 --> 00:16:38.710 align:start position:0% outcoming responses yes so far so easy however<00:16:36.800> that's<00:16:37.079> basically<00:16:37.480> just<00:16:37.639> a<00:16:37.839> wrapper 00:16:38.710 --> 00:16:38.720 align:start position:0% however that's basically just a wrapper 00:16:38.720 --> 00:16:41.350 align:start position:0% however that's basically just a wrapper on<00:16:38.959> top<00:16:39.160> of<00:16:39.319> something<00:16:40.040> which<00:16:40.199> is<00:16:40.319> TCP<00:16:41.240> which 00:16:41.350 --> 00:16:41.360 align:start position:0% on top of something which is TCP which 00:16:41.360 --> 00:16:45.150 align:start position:0% on top of something which is TCP which is<00:16:41.600> incoming<00:16:42.079> bytes<00:16:42.920> outgoing<00:16:43.440> bytes<00:16:44.000> yes<00:16:44.600> so 00:16:45.150 --> 00:16:45.160 align:start position:0% is incoming bytes outgoing bytes yes so 00:16:45.160 --> 00:16:47.189 align:start position:0% is incoming bytes outgoing bytes yes so we<00:16:45.279> can<00:16:45.519> basically<00:16:46.000> exchange<00:16:46.519> the<00:16:46.639> underlying 00:16:47.189 --> 00:16:47.199 align:start position:0% we can basically exchange the underlying 00:16:47.199 --> 00:16:50.350 align:start position:0% we can basically exchange the underlying engine<00:16:48.040> at<00:16:48.279> will<00:16:48.680> because<00:16:49.000> it's<00:16:49.279> just<00:16:50.040> this 00:16:50.350 --> 00:16:50.360 align:start position:0% engine at will because it's just this 00:16:50.360 --> 00:16:51.749 align:start position:0% engine at will because it's just this this<00:16:50.560> flow<00:16:51.040> and<00:16:51.199> we<00:16:51.319> have<00:16:51.440> all<00:16:51.600> the 00:16:51.749 --> 00:16:51.759 align:start position:0% this flow and we have all the 00:16:51.759 --> 00:16:54.470 align:start position:0% this flow and we have all the infrastructure<00:16:52.440> that<00:16:52.560> we<00:16:52.680> can<00:16:53.480> dynamically 00:16:54.470 --> 00:16:54.480 align:start position:0% infrastructure that we can dynamically 00:16:54.480 --> 00:16:56.470 align:start position:0% infrastructure that we can dynamically compose<00:16:55.040> these<00:16:55.399> so<00:16:55.639> in<00:16:55.959> when<00:16:56.120> you<00:16:56.199> want<00:16:56.319> to 00:16:56.470 --> 00:16:56.480 align:start position:0% compose these so in when you want to 00:16:56.480 --> 00:16:58.269 align:start position:0% compose these so in when you want to write<00:16:56.639> a<00:16:56.839> test<00:16:57.399> you<00:16:57.519> don't<00:16:57.720> need<00:16:57.839> to<00:16:57.959> start<00:16:58.160> a 00:16:58.269 --> 00:16:58.279 align:start position:0% write a test you don't need to start a 00:16:58.279 --> 00:17:02.550 align:start position:0% write a test you don't need to start a server<00:16:59.120> because<00:16:59.399> it's<00:16:59.680> just<00:17:00.680> the<00:17:01.360> stream<00:17:02.360> and 00:17:02.550 --> 00:17:02.560 align:start position:0% server because it's just the stream and 00:17:02.560 --> 00:17:04.429 align:start position:0% server because it's just the stream and the<00:17:02.759> most<00:17:03.120> most<00:17:03.360> interesting<00:17:03.839> bit<00:17:04.079> about<00:17:04.280> it 00:17:04.429 --> 00:17:04.439 align:start position:0% the most most interesting bit about it 00:17:04.439 --> 00:17:06.710 align:start position:0% the most most interesting bit about it is<00:17:04.640> the<00:17:04.839> back<00:17:05.039> pressure<00:17:05.400> thing<00:17:06.079> so<00:17:06.520> that's 00:17:06.710 --> 00:17:06.720 align:start position:0% is the back pressure thing so that's 00:17:06.720 --> 00:17:07.710 align:start position:0% is the back pressure thing so that's actually 00:17:07.710 --> 00:17:07.720 align:start position:0% actually 00:17:07.720 --> 00:17:10.309 align:start position:0% actually something<00:17:08.720> many<00:17:09.039> of<00:17:09.319> AA<00:17:09.640> support<00:17:09.959> tickets 00:17:10.309 --> 00:17:10.319 align:start position:0% something many of AA support tickets 00:17:10.319 --> 00:17:12.470 align:start position:0% something many of AA support tickets from<00:17:10.559> customers<00:17:11.000> or<00:17:11.319> complaints<00:17:11.799> would<00:17:12.000> be 00:17:12.470 --> 00:17:12.480 align:start position:0% from customers or complaints would be 00:17:12.480 --> 00:17:17.829 align:start position:0% from customers or complaints would be about<00:17:13.959> so<00:17:15.160> sometimes<00:17:16.160> uh<00:17:16.559> customers<00:17:17.559> don't 00:17:17.829 --> 00:17:17.839 align:start position:0% about so sometimes uh customers don't 00:17:17.839 --> 00:17:19.990 align:start position:0% about so sometimes uh customers don't really<00:17:18.000> say<00:17:18.280> that<00:17:18.439> AA<00:17:18.679> is<00:17:18.799> too<00:17:18.959> slow<00:17:19.839> that 00:17:19.990 --> 00:17:20.000 align:start position:0% really say that AA is too slow that 00:17:20.000 --> 00:17:21.669 align:start position:0% really say that AA is too slow that rarely<00:17:20.319> happens<00:17:20.760> actually<00:17:21.240> and<00:17:21.360> if<00:17:21.520> it 00:17:21.669 --> 00:17:21.679 align:start position:0% rarely happens actually and if it 00:17:21.679 --> 00:17:23.949 align:start position:0% rarely happens actually and if it happens<00:17:22.039> it's<00:17:22.240> usually<00:17:22.520> some<00:17:22.679> silly<00:17:23.000> mistake 00:17:23.949 --> 00:17:23.959 align:start position:0% happens it's usually some silly mistake 00:17:23.959 --> 00:17:26.189 align:start position:0% happens it's usually some silly mistake what<00:17:24.120> more<00:17:24.319> often<00:17:24.640> happens<00:17:24.959> is<00:17:25.199> AKA<00:17:25.520> being<00:17:25.720> too 00:17:26.189 --> 00:17:26.199 align:start position:0% what more often happens is AKA being too 00:17:26.199 --> 00:17:28.590 align:start position:0% what more often happens is AKA being too fast<00:17:27.199> and<00:17:27.319> let<00:17:27.439> me<00:17:27.559> explain<00:17:27.919> what<00:17:28.039> I<00:17:28.160> mean<00:17:28.400> by 00:17:28.590 --> 00:17:28.600 align:start position:0% fast and let me explain what I mean by 00:17:28.600 --> 00:17:30.510 align:start position:0% fast and let me explain what I mean by that<00:17:29.120> sounds<00:17:29.400> like<00:17:29.559> a<00:17:29.679> good<00:17:29.880> problem<00:17:30.120> to<00:17:30.280> have 00:17:30.510 --> 00:17:30.520 align:start position:0% that sounds like a good problem to have 00:17:30.520 --> 00:17:33.750 align:start position:0% that sounds like a good problem to have but<00:17:30.720> actually<00:17:31.160> isn't<00:17:32.160> um<00:17:32.720> so<00:17:33.000> what<00:17:33.120> we<00:17:33.240> mean<00:17:33.520> by 00:17:33.750 --> 00:17:33.760 align:start position:0% but actually isn't um so what we mean by 00:17:33.760 --> 00:17:36.950 align:start position:0% but actually isn't um so what we mean by that<00:17:33.919> and<00:17:34.080> what<00:17:34.280> customers<00:17:34.960> see<00:17:35.480> is<00:17:36.240> that<00:17:36.559> well 00:17:36.950 --> 00:17:36.960 align:start position:0% that and what customers see is that well 00:17:36.960 --> 00:17:38.830 align:start position:0% that and what customers see is that well for<00:17:37.120> example<00:17:37.440> it's<00:17:37.600> very<00:17:37.880> simple<00:17:38.200> to<00:17:38.480> produce 00:17:38.830 --> 00:17:38.840 align:start position:0% for example it's very simple to produce 00:17:38.840 --> 00:17:41.310 align:start position:0% for example it's very simple to produce loads<00:17:39.160> of<00:17:39.360> data<00:17:40.360> and<00:17:40.480> I'm<00:17:40.600> just<00:17:40.760> sending<00:17:41.120> this 00:17:41.310 --> 00:17:41.320 align:start position:0% loads of data and I'm just sending this 00:17:41.320 --> 00:17:43.510 align:start position:0% loads of data and I'm just sending this data<00:17:41.559> to<00:17:41.720> this<00:17:41.880> other<00:17:42.120> note<00:17:42.400> for<00:17:42.559> it<00:17:42.720> to<00:17:43.280> work 00:17:43.510 --> 00:17:43.520 align:start position:0% data to this other note for it to work 00:17:43.520 --> 00:17:46.470 align:start position:0% data to this other note for it to work on<00:17:43.720> it<00:17:44.559> but<00:17:44.720> this<00:17:44.919> other<00:17:45.120> note<00:17:45.360> can't<00:17:45.600> keep<00:17:45.840> up 00:17:46.470 --> 00:17:46.480 align:start position:0% on it but this other note can't keep up 00:17:46.480 --> 00:17:48.950 align:start position:0% on it but this other note can't keep up so<00:17:46.679> what<00:17:46.840> ends<00:17:47.080> up<00:17:47.280> happening<00:17:47.720> is<00:17:48.400> eventually 00:17:48.950 --> 00:17:48.960 align:start position:0% so what ends up happening is eventually 00:17:48.960 --> 00:17:50.710 align:start position:0% so what ends up happening is eventually one<00:17:49.160> or<00:17:49.400> the<00:17:49.520> other<00:17:49.720> note<00:17:50.080> will<00:17:50.480> start 00:17:50.710 --> 00:17:50.720 align:start position:0% one or the other note will start 00:17:50.720 --> 00:17:52.870 align:start position:0% one or the other note will start buffering<00:17:51.200> the<00:17:51.400> data<00:17:51.720> and<00:17:51.919> eventually<00:17:52.400> either 00:17:52.870 --> 00:17:52.880 align:start position:0% buffering the data and eventually either 00:17:52.880 --> 00:17:56.070 align:start position:0% buffering the data and eventually either start<00:17:53.120> GC<00:17:53.720> like<00:17:54.039> crazy<00:17:55.039> or<00:17:55.280> it<00:17:55.440> needs<00:17:55.640> to<00:17:55.799> drop 00:17:56.070 --> 00:17:56.080 align:start position:0% start GC like crazy or it needs to drop 00:17:56.080 --> 00:17:58.830 align:start position:0% start GC like crazy or it needs to drop the<00:17:56.320> data<00:17:56.760> or<00:17:56.919> it<00:17:57.080> needs<00:17:57.559> well<00:17:57.760> or<00:17:57.960> it<00:17:58.440> blows<00:17:58.720> up 00:17:58.830 --> 00:17:58.840 align:start position:0% the data or it needs well or it blows up 00:17:58.840 --> 00:18:01.110 align:start position:0% the data or it needs well or it blows up up<00:17:59.000> with<00:17:59.120> an<00:17:59.240> out<00:17:59.360> of<00:17:59.480> memory<00:17:59.760> error<00:18:00.480> yes<00:18:00.919> and 00:18:01.110 --> 00:18:01.120 align:start position:0% up with an out of memory error yes and 00:18:01.120 --> 00:18:03.549 align:start position:0% up with an out of memory error yes and this<00:18:01.320> happens<00:18:01.600> in<00:18:01.760> all<00:18:02.000> kinds<00:18:02.200> of<00:18:02.440> systems<00:18:03.120> but 00:18:03.549 --> 00:18:03.559 align:start position:0% this happens in all kinds of systems but 00:18:03.559 --> 00:18:04.990 align:start position:0% this happens in all kinds of systems but in<00:18:03.760> distributed<00:18:04.360> systems<00:18:04.720> or<00:18:04.880> in 00:18:04.990 --> 00:18:05.000 align:start position:0% in distributed systems or in 00:18:05.000 --> 00:18:06.789 align:start position:0% in distributed systems or in asynchronous<00:18:05.600> systems<00:18:05.919> in<00:18:06.080> general<00:18:06.520> it's 00:18:06.789 --> 00:18:06.799 align:start position:0% asynchronous systems in general it's 00:18:06.799 --> 00:18:09.510 align:start position:0% asynchronous systems in general it's really<00:18:07.760> all<00:18:07.960> over<00:18:08.200> the<00:18:08.440> place<00:18:08.960> so<00:18:09.200> reactive 00:18:09.510 --> 00:18:09.520 align:start position:0% really all over the place so reactive 00:18:09.520 --> 00:18:11.110 align:start position:0% really all over the place so reactive streams<00:18:10.000> and<00:18:10.159> our<00:18:10.360> implementations 00:18:11.110 --> 00:18:11.120 align:start position:0% streams and our implementations 00:18:11.120 --> 00:18:12.950 align:start position:0% streams and our implementations basically<00:18:11.520> address<00:18:12.039> this<00:18:12.280> need<00:18:12.720> of 00:18:12.950 --> 00:18:12.960 align:start position:0% basically address this need of 00:18:12.960 --> 00:18:15.350 align:start position:0% basically address this need of communicating<00:18:13.640> back<00:18:13.960> pressure<00:18:14.679> so<00:18:15.039> if<00:18:15.200> the 00:18:15.350 --> 00:18:15.360 align:start position:0% communicating back pressure so if the 00:18:15.360 --> 00:18:17.630 align:start position:0% communicating back pressure so if the downstream<00:18:15.919> can't<00:18:16.200> keep<00:18:16.440> up<00:18:17.080> I<00:18:17.159> will<00:18:17.360> know 00:18:17.630 --> 00:18:17.640 align:start position:0% downstream can't keep up I will know 00:18:17.640 --> 00:18:19.549 align:start position:0% downstream can't keep up I will know about<00:18:17.960> that<00:18:18.440> and<00:18:18.559> I<00:18:18.679> can<00:18:18.799> do<00:18:19.000> something<00:18:19.320> about 00:18:19.549 --> 00:18:19.559 align:start position:0% about that and I can do something about 00:18:19.559 --> 00:18:22.470 align:start position:0% about that and I can do something about it<00:18:20.000> so<00:18:20.120> I<00:18:20.200> can<00:18:20.320> use<00:18:20.520> the<00:18:20.720> signal<00:18:21.480> to<00:18:22.080> from<00:18:22.280> the 00:18:22.470 --> 00:18:22.480 align:start position:0% it so I can use the signal to from the 00:18:22.480 --> 00:18:26.510 align:start position:0% it so I can use the signal to from the pipeline<00:18:23.120> maybe<00:18:23.880> add<00:18:24.559> add<00:18:24.720> more<00:18:25.000> resources<00:18:25.960> or 00:18:26.510 --> 00:18:26.520 align:start position:0% pipeline maybe add add more resources or 00:18:26.520 --> 00:18:28.950 align:start position:0% pipeline maybe add add more resources or slow<00:18:26.919> down<00:18:27.200> the<00:18:27.720> generating<00:18:28.280> of<00:18:28.400> the<00:18:28.520> data<00:18:28.799> and 00:18:28.950 --> 00:18:28.960 align:start position:0% slow down the generating of the data and 00:18:28.960 --> 00:18:30.909 align:start position:0% slow down the generating of the data and stuff<00:18:29.200> like<00:18:29.400> that<00:18:30.039> so<00:18:30.280> this<00:18:30.400> is<00:18:30.559> actually<00:18:30.760> a 00:18:30.909 --> 00:18:30.919 align:start position:0% stuff like that so this is actually a 00:18:30.919 --> 00:18:33.070 align:start position:0% stuff like that so this is actually a lesson<00:18:31.280> that<00:18:31.400> we've<00:18:31.559> learned<00:18:31.880> the<00:18:32.039> hard<00:18:32.280> way 00:18:33.070 --> 00:18:33.080 align:start position:0% lesson that we've learned the hard way 00:18:33.080 --> 00:18:35.590 align:start position:0% lesson that we've learned the hard way um<00:18:33.720> yeah<00:18:33.880> exactly<00:18:34.240> from<00:18:34.400> our<00:18:34.640> experience<00:18:35.159> with 00:18:35.590 --> 00:18:35.600 align:start position:0% um yeah exactly from our experience with 00:18:35.600 --> 00:18:38.350 align:start position:0% um yeah exactly from our experience with uh<00:18:35.840> customers<00:18:36.360> and<00:18:36.600> production<00:18:37.159> systems<00:18:38.159> and 00:18:38.350 --> 00:18:38.360 align:start position:0% uh customers and production systems and 00:18:38.360 --> 00:18:40.669 align:start position:0% uh customers and production systems and also<00:18:38.960> we've<00:18:39.200> used<00:18:39.520> that<00:18:39.840> experience<00:18:40.360> both<00:18:40.559> to 00:18:40.669 --> 00:18:40.679 align:start position:0% also we've used that experience both to 00:18:40.679 --> 00:18:42.230 align:start position:0% also we've used that experience both to build<00:18:40.919> reactive<00:18:41.280> streams<00:18:41.880> and<00:18:42.080> our 00:18:42.230 --> 00:18:42.240 align:start position:0% build reactive streams and our 00:18:42.240 --> 00:18:44.590 align:start position:0% build reactive streams and our implementations<00:18:42.919> but<00:18:43.120> also<00:18:43.480> to<00:18:43.640> help<00:18:43.919> spark 00:18:44.590 --> 00:18:44.600 align:start position:0% implementations but also to help spark 00:18:44.600 --> 00:18:47.870 align:start position:0% implementations but also to help spark actually<00:18:45.600> so<00:18:46.360> we<00:18:46.480> have<00:18:46.600> a<00:18:46.720> team<00:18:46.880> at<00:18:47.080> typ<00:18:47.400> safe 00:18:47.870 --> 00:18:47.880 align:start position:0% actually so we have a team at typ safe 00:18:47.880 --> 00:18:50.950 align:start position:0% actually so we have a team at typ safe who<00:18:48.480> which<00:18:48.640> is<00:18:49.400> basically<00:18:49.840> dedicated<00:18:50.440> to<00:18:50.679> help 00:18:50.950 --> 00:18:50.960 align:start position:0% who which is basically dedicated to help 00:18:50.960 --> 00:18:53.909 align:start position:0% who which is basically dedicated to help spark<00:18:51.440> be<00:18:51.679> better<00:18:52.200> MH<00:18:52.960> and<00:18:53.120> in<00:18:53.320> the<00:18:53.640> in<00:18:53.760> the 00:18:53.909 --> 00:18:53.919 align:start position:0% spark be better MH and in the in the 00:18:53.919 --> 00:18:57.590 align:start position:0% spark be better MH and in the in the latest<00:18:54.840> uh<00:18:55.000> spark<00:18:55.520> release<00:18:56.520> these<00:18:57.280> how<00:18:57.400> many 00:18:57.590 --> 00:18:57.600 align:start position:0% latest uh spark release these how many 00:18:57.600 --> 00:19:00.350 align:start position:0% latest uh spark release these how many is<00:18:57.720> it<00:18:57.880> now<00:18:58.240> three4<00:18:58.880> guys<00:18:59.280> basically<00:18:59.919> spent<00:19:00.240> a 00:19:00.350 --> 00:19:00.360 align:start position:0% is it now three4 guys basically spent a 00:19:00.360 --> 00:19:02.190 align:start position:0% is it now three4 guys basically spent a few<00:19:00.600> months<00:19:00.919> working<00:19:01.320> on<00:19:01.480> spark<00:19:01.960> back 00:19:02.190 --> 00:19:02.200 align:start position:0% few months working on spark back 00:19:02.200 --> 00:19:04.549 align:start position:0% few months working on spark back pressure<00:19:02.760> mechanisms<00:19:03.760> which<00:19:03.919> was<00:19:04.120> addressing 00:19:04.549 --> 00:19:04.559 align:start position:0% pressure mechanisms which was addressing 00:19:04.559 --> 00:19:07.669 align:start position:0% pressure mechanisms which was addressing the<00:19:04.760> problem<00:19:05.120> of<00:19:06.000> well<00:19:06.280> if<00:19:06.480> if<00:19:06.640> I<00:19:06.880> have<00:19:07.000> a<00:19:07.559> you 00:19:07.669 --> 00:19:07.679 align:start position:0% the problem of well if if I have a you 00:19:07.679 --> 00:19:10.870 align:start position:0% the problem of well if if I have a you know<00:19:07.960> huge<00:19:08.840> spike<00:19:09.200> in<00:19:09.360> my<00:19:09.520> load<00:19:10.159> spark<00:19:10.600> is<00:19:10.760> you 00:19:10.870 --> 00:19:10.880 align:start position:0% know huge spike in my load spark is you 00:19:10.880 --> 00:19:13.110 align:start position:0% know huge spike in my load spark is you know<00:19:11.039> failing<00:19:11.799> right<00:19:12.240> people<00:19:12.440> would<00:19:12.600> say<00:19:12.880> that 00:19:13.110 --> 00:19:13.120 align:start position:0% know failing right people would say that 00:19:13.120 --> 00:19:14.350 align:start position:0% know failing right people would say that people<00:19:13.320> would<00:19:13.480> not<00:19:13.679> realize<00:19:14.120> what's 00:19:14.350 --> 00:19:14.360 align:start position:0% people would not realize what's 00:19:14.360 --> 00:19:16.350 align:start position:0% people would not realize what's happening<00:19:15.000> what<00:19:15.159> was<00:19:15.360> happening<00:19:15.679> is<00:19:15.919> exactly 00:19:16.350 --> 00:19:16.360 align:start position:0% happening what was happening is exactly 00:19:16.360 --> 00:19:17.870 align:start position:0% happening what was happening is exactly that<00:19:16.559> that<00:19:16.720> one<00:19:16.880> note<00:19:17.120> would<00:19:17.280> be<00:19:17.360> sending<00:19:17.720> too 00:19:17.870 --> 00:19:17.880 align:start position:0% that that one note would be sending too 00:19:17.880 --> 00:19:20.230 align:start position:0% that that one note would be sending too much<00:19:18.039> to<00:19:18.280> another<00:19:18.600> Noe<00:19:18.919> in<00:19:19.039> the<00:19:19.200> spark<00:19:19.520> cluster 00:19:20.230 --> 00:19:20.240 align:start position:0% much to another Noe in the spark cluster 00:19:20.240 --> 00:19:21.950 align:start position:0% much to another Noe in the spark cluster and<00:19:20.400> they<00:19:20.559> would<00:19:20.760> you<00:19:20.880> know<00:19:21.240> oscillate<00:19:21.799> and 00:19:21.950 --> 00:19:21.960 align:start position:0% and they would you know oscillate and 00:19:21.960 --> 00:19:24.549 align:start position:0% and they would you know oscillate and start<00:19:22.240> failing<00:19:22.640> with<00:19:22.840> out<00:19:23.000> of<00:19:23.240> memory<00:19:24.240> so 00:19:24.549 --> 00:19:24.559 align:start position:0% start failing with out of memory so 00:19:24.559 --> 00:19:26.390 align:start position:0% start failing with out of memory so lessons<00:19:24.960> that<00:19:25.120> we've<00:19:25.280> learned<00:19:25.600> on<00:19:25.760> our<00:19:26.080> side 00:19:26.390 --> 00:19:26.400 align:start position:0% lessons that we've learned on our side 00:19:26.400 --> 00:19:28.990 align:start position:0% lessons that we've learned on our side we're<00:19:26.600> bringing<00:19:27.280> it<00:19:27.440> also<00:19:27.679> into<00:19:27.960> other 00:19:28.990 --> 00:19:29.000 align:start position:0% we're bringing it also into other 00:19:29.000 --> 00:19:30.950 align:start position:0% we're bringing it also into other valuable<00:19:29.520> projects<00:19:29.840> in<00:19:29.960> this<00:19:30.159> scar<00:19:30.480> ecosystem 00:19:30.950 --> 00:19:30.960 align:start position:0% valuable projects in this scar ecosystem 00:19:30.960 --> 00:19:32.789 align:start position:0% valuable projects in this scar ecosystem like<00:19:31.200> spark<00:19:31.679> right<00:19:32.159> so<00:19:32.360> that's<00:19:32.520> already 00:19:32.789 --> 00:19:32.799 align:start position:0% like spark right so that's already 00:19:32.799 --> 00:19:35.430 align:start position:0% like spark right so that's already merged<00:19:33.400> and<00:19:33.640> there's<00:19:33.880> going<00:19:33.960> to<00:19:34.120> be<00:19:35.039> more 00:19:35.430 --> 00:19:35.440 align:start position:0% merged and there's going to be more 00:19:35.440 --> 00:19:38.350 align:start position:0% merged and there's going to be more strategies<00:19:36.000> coming<00:19:36.440> right<00:19:36.679> so<00:19:36.960> in<00:19:37.360> spark 00:19:38.350 --> 00:19:38.360 align:start position:0% strategies coming right so in spark 00:19:38.360 --> 00:19:40.950 align:start position:0% strategies coming right so in spark since<00:19:38.600> you're<00:19:38.799> using<00:19:39.120> it<00:19:39.480> for<00:19:40.480> for<00:19:40.679> example 00:19:40.950 --> 00:19:40.960 align:start position:0% since you're using it for for example 00:19:40.960 --> 00:19:42.750 align:start position:0% since you're using it for for example some<00:19:41.159> analytics<00:19:41.840> right<00:19:42.000> so<00:19:42.120> a<00:19:42.280> valuable 00:19:42.750 --> 00:19:42.760 align:start position:0% some analytics right so a valuable 00:19:42.760 --> 00:19:45.990 align:start position:0% some analytics right so a valuable strategy<00:19:43.240> may<00:19:43.480> be<00:19:44.480> um<00:19:44.799> to<00:19:45.000> start<00:19:45.320> sampling<00:19:45.799> the 00:19:45.990 --> 00:19:46.000 align:start position:0% strategy may be um to start sampling the 00:19:46.000 --> 00:19:47.830 align:start position:0% strategy may be um to start sampling the data<00:19:46.400> right<00:19:46.600> to<00:19:46.760> not<00:19:47.000> collect<00:19:47.360> all<00:19:47.520> of<00:19:47.640> it 00:19:47.830 --> 00:19:47.840 align:start position:0% data right to not collect all of it 00:19:47.840 --> 00:19:50.549 align:start position:0% data right to not collect all of it because<00:19:48.039> I<00:19:48.159> can't<00:19:48.440> keep<00:19:48.679> up<00:19:49.120> so<00:19:49.280> I<00:19:49.440> can<00:19:49.640> collect 00:19:50.549 --> 00:19:50.559 align:start position:0% because I can't keep up so I can collect 00:19:50.559 --> 00:19:53.350 align:start position:0% because I can't keep up so I can collect 80<00:19:50.880> 90%<00:19:51.640> whatever<00:19:52.000> until<00:19:52.360> a<00:19:52.520> new<00:19:52.840> note<00:19:53.159> comes 00:19:53.350 --> 00:19:53.360 align:start position:0% 80 90% whatever until a new note comes 00:19:53.360 --> 00:19:55.590 align:start position:0% 80 90% whatever until a new note comes in<00:19:53.600> and<00:19:53.760> then<00:19:53.880> we<00:19:54.000> can<00:19:54.200> go<00:19:54.400> full<00:19:54.679> speed<00:19:55.080> again 00:19:55.590 --> 00:19:55.600 align:start position:0% in and then we can go full speed again 00:19:55.600 --> 00:19:58.270 align:start position:0% in and then we can go full speed again exactly<00:19:56.600> so<00:19:57.120> well<00:19:57.280> this<00:19:57.360> is<00:19:57.559> great<00:19:57.799> so<00:19:58.000> this<00:19:58.120> is 00:19:58.270 --> 00:19:58.280 align:start position:0% exactly so well this is great so this is 00:19:58.280 --> 00:20:00.510 align:start position:0% exactly so well this is great so this is actually<00:19:58.840> nice<00:19:59.120> connection<00:19:59.760> kind<00:19:59.880> of<00:20:00.120> back<00:20:00.320> to 00:20:00.510 --> 00:20:00.520 align:start position:0% actually nice connection kind of back to 00:20:00.520 --> 00:20:02.190 align:start position:0% actually nice connection kind of back to sparkk<00:20:01.000> from 00:20:02.190 --> 00:20:02.200 align:start position:0% sparkk from 00:20:02.200 --> 00:20:05.510 align:start position:0% sparkk from from<00:20:03.200> right<00:20:03.480> so<00:20:03.640> which<00:20:03.760> is<00:20:03.960> probably<00:20:04.400> kind<00:20:04.520> of 00:20:05.510 --> 00:20:05.520 align:start position:0% from right so which is probably kind of 00:20:05.520 --> 00:20:07.470 align:start position:0% from right so which is probably kind of good<00:20:05.720> point<00:20:06.000> to<00:20:06.360> to<00:20:06.679> wrap<00:20:06.880> up<00:20:07.000> and<00:20:07.120> make<00:20:07.240> a 00:20:07.470 --> 00:20:07.480 align:start position:0% good point to to wrap up and make a 00:20:07.480 --> 00:20:09.830 align:start position:0% good point to to wrap up and make a prediction<00:20:08.480> uh<00:20:08.600> as<00:20:08.679> we<00:20:08.840> like<00:20:09.000> to<00:20:09.080> do<00:20:09.360> so<00:20:09.679> so 00:20:09.830 --> 00:20:09.840 align:start position:0% prediction uh as we like to do so so 00:20:09.840 --> 00:20:11.669 align:start position:0% prediction uh as we like to do so so you're<00:20:10.000> on<00:20:10.159> thead<00:20:10.480> team<00:20:11.120> obviously<00:20:11.480> there<00:20:11.600> is 00:20:11.669 --> 00:20:11.679 align:start position:0% you're on thead team obviously there is 00:20:11.679 --> 00:20:15.630 align:start position:0% you're on thead team obviously there is a<00:20:11.880> lot<00:20:12.080> of<00:20:12.919> new<00:20:13.919> uh<00:20:14.240> uh<00:20:14.400> kind<00:20:14.520> of<00:20:14.880> progress<00:20:15.400> and 00:20:15.630 --> 00:20:15.640 align:start position:0% a lot of new uh uh kind of progress and 00:20:15.640 --> 00:20:18.909 align:start position:0% a lot of new uh uh kind of progress and kind<00:20:15.760> of<00:20:15.919> reactive<00:20:16.440> systems<00:20:17.440> is<00:20:17.679> kind<00:20:17.840> of<00:20:18.400> uh 00:20:18.909 --> 00:20:18.919 align:start position:0% kind of reactive systems is kind of uh 00:20:18.919 --> 00:20:20.669 align:start position:0% kind of reactive systems is kind of uh uh<00:20:19.039> spreading<00:20:19.679> not<00:20:19.919> I<00:20:19.960> would<00:20:20.159> say<00:20:20.440> not 00:20:20.669 --> 00:20:20.679 align:start position:0% uh spreading not I would say not 00:20:20.679 --> 00:20:22.190 align:start position:0% uh spreading not I would say not everybody<00:20:21.200> majority<00:20:21.520> of<00:20:21.600> the<00:20:21.679> world<00:20:21.919> does<00:20:22.080> not 00:20:22.190 --> 00:20:22.200 align:start position:0% everybody majority of the world does not 00:20:22.200 --> 00:20:24.070 align:start position:0% everybody majority of the world does not know<00:20:22.400> what<00:20:22.520> we<00:20:22.679> know<00:20:23.280> yet<00:20:23.720> right<00:20:23.880> like<00:20:23.960> it's 00:20:24.070 --> 00:20:24.080 align:start position:0% know what we know yet right like it's 00:20:24.080 --> 00:20:27.990 align:start position:0% know what we know yet right like it's our<00:20:24.440> job<00:20:24.760> to<00:20:25.559> to<00:20:26.320> uh<00:20:26.760> to<00:20:26.919> push<00:20:27.200> the<00:20:27.679> of<00:20:27.840> the 00:20:27.990 --> 00:20:28.000 align:start position:0% our job to to uh to push the of the 00:20:28.000 --> 00:20:30.710 align:start position:0% our job to to uh to push the of the world<00:20:28.440> right<00:20:29.000> and<00:20:29.240> and<00:20:29.480> kind<00:20:29.640> of<00:20:30.159> uh<00:20:30.520> what<00:20:30.600> do 00:20:30.710 --> 00:20:30.720 align:start position:0% world right and and kind of uh what do 00:20:30.720 --> 00:20:32.230 align:start position:0% world right and and kind of uh what do you<00:20:30.880> think<00:20:31.400> where<00:20:31.520> we're<00:20:31.679> going<00:20:31.760> to<00:20:31.880> be<00:20:31.960> in<00:20:32.039> the 00:20:32.230 --> 00:20:32.240 align:start position:0% you think where we're going to be in the 00:20:32.240 --> 00:20:33.390 align:start position:0% you think where we're going to be in the year<00:20:32.520> you<00:20:32.600> know<00:20:32.760> let's<00:20:32.960> make<00:20:33.159> like<00:20:33.240> a 00:20:33.390 --> 00:20:33.400 align:start position:0% year you know let's make like a 00:20:33.400 --> 00:20:35.710 align:start position:0% year you know let's make like a prediction<00:20:33.880> so<00:20:34.080> next<00:20:34.280> year<00:20:34.559> next<00:20:34.760> jav<00:20:35.039> one 00:20:35.710 --> 00:20:35.720 align:start position:0% prediction so next year next jav one 00:20:35.720 --> 00:20:39.830 align:start position:0% prediction so next year next jav one right<00:20:36.280> systems<00:20:36.720> AA<00:20:37.679> how<00:20:38.480> many<00:20:39.440> like<00:20:39.640> what 00:20:39.830 --> 00:20:39.840 align:start position:0% right systems AA how many like what 00:20:39.840 --> 00:20:41.149 align:start position:0% right systems AA how many like what what's<00:20:40.080> what<00:20:40.159> would<00:20:40.320> be<00:20:40.440> the<00:20:40.600> adoption<00:20:41.000> of 00:20:41.149 --> 00:20:41.159 align:start position:0% what's what would be the adoption of 00:20:41.159 --> 00:20:43.789 align:start position:0% what's what would be the adoption of reactive<00:20:41.640> systems<00:20:42.400> just<00:20:42.559> you<00:20:42.679> know<00:20:43.080> what<00:20:43.320> what 00:20:43.789 --> 00:20:43.799 align:start position:0% reactive systems just you know what what 00:20:43.799 --> 00:20:45.870 align:start position:0% reactive systems just you know what what should<00:20:44.039> we<00:20:44.159> see<00:20:45.159> you<00:20:45.280> know<00:20:45.520> what<00:20:45.640> kind<00:20:45.760> of 00:20:45.870 --> 00:20:45.880 align:start position:0% should we see you know what kind of 00:20:45.880 --> 00:20:47.789 align:start position:0% should we see you know what kind of customers<00:20:46.240> can<00:20:46.440> benefit<00:20:46.799> from<00:20:47.039> this<00:20:47.240> like<00:20:47.400> any 00:20:47.789 --> 00:20:47.799 align:start position:0% customers can benefit from this like any 00:20:47.799 --> 00:20:50.230 align:start position:0% customers can benefit from this like any wild<00:20:48.080> guesses<00:20:48.400> are<00:20:48.559> fine<00:20:48.880> right<00:20:49.720> happen<00:20:50.000> wild 00:20:50.230 --> 00:20:50.240 align:start position:0% wild guesses are fine right happen wild 00:20:50.240 --> 00:20:52.669 align:start position:0% wild guesses are fine right happen wild guesses<00:20:50.559> so<00:20:50.720> my<00:20:50.919> wild<00:20:51.200> guess<00:20:51.679> is<00:20:52.360> we're 00:20:52.669 --> 00:20:52.679 align:start position:0% guesses so my wild guess is we're 00:20:52.679 --> 00:20:54.630 align:start position:0% guesses so my wild guess is we're already<00:20:53.039> seeing<00:20:53.559> that<00:20:54.000> but<00:20:54.240> I<00:20:54.320> think<00:20:54.480> it's 00:20:54.630 --> 00:20:54.640 align:start position:0% already seeing that but I think it's 00:20:54.640 --> 00:20:56.710 align:start position:0% already seeing that but I think it's going<00:20:54.720> to<00:20:54.880> pick<00:20:55.039> up<00:20:55.240> even<00:20:55.440> more<00:20:55.760> now<00:20:56.320> um<00:20:56.480> so 00:20:56.710 --> 00:20:56.720 align:start position:0% going to pick up even more now um so 00:20:56.720 --> 00:20:59.149 align:start position:0% going to pick up even more now um so we're<00:20:56.880> seeing<00:20:57.360> lot<00:20:57.559> of<00:20:58.200> how<00:20:58.640> call<00:20:58.880> them 00:20:59.149 --> 00:20:59.159 align:start position:0% we're seeing lot of how call them 00:20:59.159 --> 00:21:01.110 align:start position:0% we're seeing lot of how call them dinosaurs<00:21:00.159> they<00:21:00.320> don't<00:21:00.480> like<00:21:00.600> to<00:21:00.720> be<00:21:00.840> called 00:21:01.110 --> 00:21:01.120 align:start position:0% dinosaurs they don't like to be called 00:21:01.120 --> 00:21:03.110 align:start position:0% dinosaurs they don't like to be called like<00:21:01.280> that<00:21:01.400> and<00:21:01.559> maybe<00:21:01.799> I<00:21:01.880> shouldn't<00:21:02.280> but<00:21:02.960> you 00:21:03.110 --> 00:21:03.120 align:start position:0% like that and maybe I shouldn't but you 00:21:03.120 --> 00:21:04.990 align:start position:0% like that and maybe I shouldn't but you know<00:21:03.320> who<00:21:03.480> I<00:21:03.559> mean<00:21:04.080> when<00:21:04.200> I<00:21:04.360> say<00:21:04.600> that<00:21:04.799> so 00:21:04.990 --> 00:21:05.000 align:start position:0% know who I mean when I say that so 00:21:05.000 --> 00:21:08.149 align:start position:0% know who I mean when I say that so they're<00:21:05.320> very<00:21:06.200> slowly<00:21:06.880> adopting<00:21:07.559> companies 00:21:08.149 --> 00:21:08.159 align:start position:0% they're very slowly adopting companies 00:21:08.159 --> 00:21:10.590 align:start position:0% they're very slowly adopting companies which<00:21:08.400> like<00:21:09.159> stuff<00:21:09.480> that<00:21:09.679> has<00:21:09.919> proven<00:21:10.320> over 00:21:10.590 --> 00:21:10.600 align:start position:0% which like stuff that has proven over 00:21:10.600 --> 00:21:13.350 align:start position:0% which like stuff that has proven over the<00:21:10.799> years<00:21:11.440> and<00:21:12.080> you<00:21:12.200> know<00:21:12.480> are<00:21:12.640> slow<00:21:12.880> to<00:21:13.039> adopt 00:21:13.350 --> 00:21:13.360 align:start position:0% the years and you know are slow to adopt 00:21:13.360 --> 00:21:16.470 align:start position:0% the years and you know are slow to adopt stuff<00:21:14.080> they<00:21:14.240> are<00:21:14.559> getting<00:21:14.840> onto<00:21:15.120> our<00:21:15.480> platform 00:21:16.470 --> 00:21:16.480 align:start position:0% stuff they are getting onto our platform 00:21:16.480 --> 00:21:19.269 align:start position:0% stuff they are getting onto our platform and<00:21:17.039> yeah<00:21:17.240> it's<00:21:17.440> stuff<00:21:17.760> like<00:21:18.360> Banks<00:21:19.039> and 00:21:19.269 --> 00:21:19.279 align:start position:0% and yeah it's stuff like Banks and 00:21:19.279 --> 00:21:22.750 align:start position:0% and yeah it's stuff like Banks and hotelier<00:21:19.919> systems<00:21:20.679> and<00:21:21.200> Airlines<00:21:22.200> these<00:21:22.559> big 00:21:22.750 --> 00:21:22.760 align:start position:0% hotelier systems and Airlines these big 00:21:22.760 --> 00:21:24.630 align:start position:0% hotelier systems and Airlines these big players<00:21:23.279> right<00:21:23.480> and<00:21:23.960> when<00:21:24.200> they<00:21:24.360> make 00:21:24.630 --> 00:21:24.640 align:start position:0% players right and when they make 00:21:24.640 --> 00:21:27.990 align:start position:0% players right and when they make decisions<00:21:25.360> it's<00:21:26.080> usually<00:21:27.080> both<00:21:27.520> they<00:21:27.679> make<00:21:27.840> it 00:21:27.990 --> 00:21:28.000 align:start position:0% decisions it's usually both they make it 00:21:28.000 --> 00:21:29.350 align:start position:0% decisions it's usually both they make it very<00:21:28.159> slowly 00:21:29.350 --> 00:21:29.360 align:start position:0% very slowly 00:21:29.360 --> 00:21:30.710 align:start position:0% very slowly and<00:21:29.559> then<00:21:29.880> they<00:21:30.039> need<00:21:30.159> to<00:21:30.320> be<00:21:30.480> really 00:21:30.710 --> 00:21:30.720 align:start position:0% and then they need to be really 00:21:30.720 --> 00:21:34.269 align:start position:0% and then they need to be really convinced<00:21:31.240> about<00:21:31.480> it<00:21:32.120> and<00:21:32.480> they<00:21:32.960> don't<00:21:33.840> just 00:21:34.269 --> 00:21:34.279 align:start position:0% convinced about it and they don't just 00:21:34.279 --> 00:21:36.230 align:start position:0% convinced about it and they don't just watch<00:21:34.559> a<00:21:34.760> presentation<00:21:35.360> and<00:21:35.559> this<00:21:35.720> idea<00:21:36.080> let's 00:21:36.230 --> 00:21:36.240 align:start position:0% watch a presentation and this idea let's 00:21:36.240 --> 00:21:39.029 align:start position:0% watch a presentation and this idea let's use<00:21:36.480> that<00:21:37.080> they<00:21:37.320> really<00:21:37.480> want<00:21:37.760> hard<00:21:38.039> numbers 00:21:39.029 --> 00:21:39.039 align:start position:0% use that they really want hard numbers 00:21:39.039 --> 00:21:40.870 align:start position:0% use that they really want hard numbers and<00:21:39.279> now<00:21:39.480> we're<00:21:39.799> pretty<00:21:40.000> much<00:21:40.159> in<00:21:40.279> a<00:21:40.520> position 00:21:40.870 --> 00:21:40.880 align:start position:0% and now we're pretty much in a position 00:21:40.880 --> 00:21:43.630 align:start position:0% and now we're pretty much in a position to<00:21:41.279> show<00:21:41.840> hard<00:21:42.120> numbers<00:21:42.559> about<00:21:43.240> you<00:21:43.360> know 00:21:43.630 --> 00:21:43.640 align:start position:0% to show hard numbers about you know 00:21:43.640 --> 00:21:45.909 align:start position:0% to show hard numbers about you know there's<00:21:43.919> been<00:21:44.120> so<00:21:44.320> many<00:21:44.799> actual<00:21:45.400> migrations 00:21:45.909 --> 00:21:45.919 align:start position:0% there's been so many actual migrations 00:21:45.919 --> 00:21:47.789 align:start position:0% there's been so many actual migrations to<00:21:46.120> our<00:21:46.400> Technologies<00:21:46.960> and<00:21:47.159> this<00:21:47.400> style<00:21:47.640> of 00:21:47.789 --> 00:21:47.799 align:start position:0% to our Technologies and this style of 00:21:47.799 --> 00:21:50.310 align:start position:0% to our Technologies and this style of development<00:21:48.360> reactive<00:21:49.080> reactive<00:21:49.520> systems 00:21:50.310 --> 00:21:50.320 align:start position:0% development reactive reactive systems 00:21:50.320 --> 00:21:51.830 align:start position:0% development reactive reactive systems and<00:21:50.480> it<00:21:50.640> has<00:21:50.799> worked<00:21:51.080> out<00:21:51.240> for<00:21:51.480> these 00:21:51.830 --> 00:21:51.840 align:start position:0% and it has worked out for these 00:21:51.840 --> 00:21:54.230 align:start position:0% and it has worked out for these companies<00:21:52.840> so<00:21:53.039> it's<00:21:53.200> finally<00:21:53.559> convincing<00:21:54.039> the 00:21:54.230 --> 00:21:54.240 align:start position:0% companies so it's finally convincing the 00:21:54.240 --> 00:21:56.470 align:start position:0% companies so it's finally convincing the big<00:21:54.440> players<00:21:54.760> to<00:21:54.919> move<00:21:55.320> along<00:21:55.679> as<00:21:55.840> well<00:21:56.360> all 00:21:56.470 --> 00:21:56.480 align:start position:0% big players to move along as well all 00:21:56.480 --> 00:21:58.669 align:start position:0% big players to move along as well all right<00:21:57.080> and<00:21:57.240> so<00:21:57.520> hopeful<00:21:57.840> it<00:21:57.960> means<00:21:58.200> that<00:21:58.400> the 00:21:58.669 --> 00:21:58.679 align:start position:0% right and so hopeful it means that the 00:21:58.679 --> 00:22:00.830 align:start position:0% right and so hopeful it means that the they<00:21:59.000> will<00:21:59.200> have<00:21:59.320> to<00:21:59.480> adopt<00:21:59.799> Scola<00:22:00.320> and<00:22:00.559> learn 00:22:00.830 --> 00:22:00.840 align:start position:0% they will have to adopt Scola and learn 00:22:00.840 --> 00:22:03.269 align:start position:0% they will have to adopt Scola and learn it<00:22:01.200> along<00:22:01.440> the<00:22:01.559> way<00:22:01.720> I<00:22:01.960> hope<00:22:02.200> so<00:22:02.840> yeah<00:22:03.120> all 00:22:03.269 --> 00:22:03.279 align:start position:0% it along the way I hope so yeah all 00:22:03.279 --> 00:22:05.149 align:start position:0% it along the way I hope so yeah all right<00:22:03.600> so<00:22:03.840> let's<00:22:04.159> hope<00:22:04.400> that<00:22:04.559> reactive<00:22:05.039> will 00:22:05.149 --> 00:22:05.159 align:start position:0% right so let's hope that reactive will 00:22:05.159 --> 00:22:07.710 align:start position:0% right so let's hope that reactive will be<00:22:05.360> as<00:22:05.640> big<00:22:05.799> a<00:22:05.919> driver<00:22:06.240> for<00:22:06.559> skull<00:22:06.840> as<00:22:07.039> spark 00:22:07.710 --> 00:22:07.720 align:start position:0% be as big a driver for skull as spark 00:22:07.720 --> 00:22:09.830 align:start position:0% be as big a driver for skull as spark and<00:22:07.960> play<00:22:08.679> before<00:22:08.919> it<00:22:09.279> exactly<00:22:09.600> all<00:22:09.720> right 00:22:09.830 --> 00:22:09.840 align:start position:0% and play before it exactly all right 00:22:09.840 --> 00:22:11.110 align:start position:0% and play before it exactly all right thanks<00:22:10.080> con<00:22:10.320> we're<00:22:10.440> looking<00:22:10.640> forward<00:22:10.880> to<00:22:10.960> your 00:22:11.110 --> 00:22:11.120 align:start position:0% thanks con we're looking forward to your 00:22:11.120 --> 00:22:12.430 align:start position:0% thanks con we're looking forward to your talk<00:22:11.279> and<00:22:11.440> thanks<00:22:11.600> for<00:22:11.760> coming<00:22:12.159> thank<00:22:12.279> you 00:22:12.430 --> 00:22:12.440 align:start position:0% talk and thanks for coming thank you 00:22:12.440 --> 00:22:24.510 align:start position:0% talk and thanks for coming thank you very<00:22:12.600> much<00:22:13.000> thanks<00:22:14.000> so 00:22:24.510 --> 00:22:24.520 align:start position:0% 00:22:24.520 --> 00:22:27.720 align:start position:0% [Music]