WEBVTT Kind: captions Language: en 00:00:00.080 --> 00:00:02.629 align:start position:0% I'm<00:00:00.320> Alexi<00:00:00.719> Kraov,<00:00:01.280> the<00:00:01.600> organizer<00:00:02.080> of<00:00:02.240> Rust 00:00:02.629 --> 00:00:02.639 align:start position:0% I'm Alexi Kraov, the organizer of Rust 00:00:02.639 --> 00:00:05.110 align:start position:0% I'm Alexi Kraov, the organizer of Rust AI<00:00:03.040> community.<00:00:03.439> We<00:00:03.600> just<00:00:03.760> held<00:00:04.000> our<00:00:04.319> first 00:00:05.110 --> 00:00:05.120 align:start position:0% AI community. We just held our first 00:00:05.120 --> 00:00:07.670 align:start position:0% AI community. We just held our first meet<00:00:05.359> up<00:00:05.680> in<00:00:05.920> Amsterdam<00:00:06.560> before<00:00:06.799> the<00:00:06.960> PI<00:00:07.200> data 00:00:07.670 --> 00:00:07.680 align:start position:0% meet up in Amsterdam before the PI data 00:00:07.680 --> 00:00:10.950 align:start position:0% meet up in Amsterdam before the PI data Amsterdam<00:00:08.480> Italian<00:00:09.120> office<00:00:09.920> and<00:00:10.639> we<00:00:10.800> have 00:00:10.950 --> 00:00:10.960 align:start position:0% Amsterdam Italian office and we have 00:00:10.960 --> 00:00:14.390 align:start position:0% Amsterdam Italian office and we have with<00:00:11.120> us<00:00:11.440> Richie<00:00:12.160> the<00:00:12.719> founder<00:00:13.120> of<00:00:13.679> Polers. 00:00:14.390 --> 00:00:14.400 align:start position:0% with us Richie the founder of Polers. 00:00:14.400 --> 00:00:15.030 align:start position:0% with us Richie the founder of Polers. Yes. 00:00:15.030 --> 00:00:15.040 align:start position:0% Yes. 00:00:15.040 --> 00:00:17.670 align:start position:0% Yes. And<00:00:15.360> you<00:00:15.599> guys<00:00:15.759> chose<00:00:16.080> Rust<00:00:16.720> for<00:00:16.960> the 00:00:17.670 --> 00:00:17.680 align:start position:0% And you guys chose Rust for the 00:00:17.680 --> 00:00:20.870 align:start position:0% And you guys chose Rust for the implementation<00:00:18.720> of<00:00:18.960> Polers.<00:00:19.359> So<00:00:19.600> tell<00:00:19.760> us<00:00:20.320> why 00:00:20.870 --> 00:00:20.880 align:start position:0% implementation of Polers. So tell us why 00:00:20.880 --> 00:00:23.029 align:start position:0% implementation of Polers. So tell us why you<00:00:21.039> selected<00:00:21.439> Rust?<00:00:22.240> How<00:00:22.400> does<00:00:22.560> it<00:00:22.720> help<00:00:22.880> to 00:00:23.029 --> 00:00:23.039 align:start position:0% you selected Rust? How does it help to 00:00:23.039 --> 00:00:25.830 align:start position:0% you selected Rust? How does it help to build<00:00:23.279> the<00:00:23.760> AI<00:00:24.160> infra<00:00:25.119> structure<00:00:25.519> of 00:00:25.830 --> 00:00:25.840 align:start position:0% build the AI infra structure of 00:00:25.840 --> 00:00:27.109 align:start position:0% build the AI infra structure of tomorrow? 00:00:27.109 --> 00:00:27.119 align:start position:0% tomorrow? 00:00:27.119 --> 00:00:28.870 align:start position:0% tomorrow? Well,<00:00:27.279> when<00:00:27.439> I<00:00:27.519> started<00:00:27.840> a<00:00:27.920> polar,<00:00:28.480> it<00:00:28.720> was 00:00:28.870 --> 00:00:28.880 align:start position:0% Well, when I started a polar, it was 00:00:28.880 --> 00:00:30.630 align:start position:0% Well, when I started a polar, it was mostly<00:00:29.279> because<00:00:29.519> I<00:00:29.679> was<00:00:29.840> interested<00:00:30.080> in<00:00:30.320> ROS. 00:00:30.630 --> 00:00:30.640 align:start position:0% mostly because I was interested in ROS. 00:00:30.640 --> 00:00:32.310 align:start position:0% mostly because I was interested in ROS. I<00:00:30.800> was<00:00:30.880> just<00:00:31.039> very<00:00:31.279> excited<00:00:31.519> about<00:00:31.760> the<00:00:31.920> tech, 00:00:32.310 --> 00:00:32.320 align:start position:0% I was just very excited about the tech, 00:00:32.320 --> 00:00:34.229 align:start position:0% I was just very excited about the tech, about<00:00:32.800> going<00:00:33.120> into<00:00:33.440> more<00:00:33.760> low-level 00:00:34.229 --> 00:00:34.239 align:start position:0% about going into more low-level 00:00:34.239 --> 00:00:36.150 align:start position:0% about going into more low-level languages,<00:00:35.120> uh,<00:00:35.200> but<00:00:35.440> also<00:00:35.600> in<00:00:35.760> a<00:00:35.920> modern 00:00:36.150 --> 00:00:36.160 align:start position:0% languages, uh, but also in a modern 00:00:36.160 --> 00:00:39.430 align:start position:0% languages, uh, but also in a modern language.<00:00:37.200> Uh,<00:00:37.520> that<00:00:37.680> was<00:00:37.840> 6<00:00:38.000> years<00:00:38.239> ago. 00:00:39.430 --> 00:00:39.440 align:start position:0% language. Uh, that was 6 years ago. 00:00:39.440 --> 00:00:41.990 align:start position:0% language. Uh, that was 6 years ago. Nowadays,<00:00:40.000> it's<00:00:40.320> also<00:00:40.960> proven<00:00:41.280> to<00:00:41.520> be<00:00:41.600> a<00:00:41.760> very 00:00:41.990 --> 00:00:42.000 align:start position:0% Nowadays, it's also proven to be a very 00:00:42.000 --> 00:00:45.190 align:start position:0% Nowadays, it's also proven to be a very good<00:00:42.559> language<00:00:42.960> for<00:00:43.200> AI.<00:00:43.760> And,<00:00:44.239> um,<00:00:44.879> yeah, 00:00:45.190 --> 00:00:45.200 align:start position:0% good language for AI. And, um, yeah, 00:00:45.200 --> 00:00:48.069 align:start position:0% good language for AI. And, um, yeah, that's<00:00:45.520> mostly<00:00:46.160> a<00:00:46.879> lucky<00:00:47.280> coincidence,<00:00:47.840> I 00:00:48.069 --> 00:00:48.079 align:start position:0% that's mostly a lucky coincidence, I 00:00:48.079 --> 00:00:49.430 align:start position:0% that's mostly a lucky coincidence, I would<00:00:48.239> say. 00:00:49.430 --> 00:00:49.440 align:start position:0% would say. 00:00:49.440 --> 00:00:51.510 align:start position:0% would say. uh<00:00:49.600> for<00:00:49.840> a<00:00:50.000> lot<00:00:50.079> of<00:00:50.160> people<00:00:50.559> rusts<00:00:50.960> were<00:00:51.200> seen 00:00:51.510 --> 00:00:51.520 align:start position:0% uh for a lot of people rusts were seen 00:00:51.520 --> 00:00:54.150 align:start position:0% uh for a lot of people rusts were seen as<00:00:51.840> the<00:00:52.239> the<00:00:52.559> complicated<00:00:53.120> language<00:00:53.600> the<00:00:53.760> the 00:00:54.150 --> 00:00:54.160 align:start position:0% as the the complicated language the the 00:00:54.160 --> 00:00:56.869 align:start position:0% as the the complicated language the the hard<00:00:54.399> language<00:00:54.879> and<00:00:55.680> now<00:00:56.320> this<00:00:56.559> whole 00:00:56.869 --> 00:00:56.879 align:start position:0% hard language and now this whole 00:00:56.879 --> 00:00:58.709 align:start position:0% hard language and now this whole strictness<00:00:57.520> this<00:00:57.680> whole<00:00:57.840> borrow<00:00:58.239> checker<00:00:58.480> is 00:00:58.709 --> 00:00:58.719 align:start position:0% strictness this whole borrow checker is 00:00:58.719 --> 00:01:00.470 align:start position:0% strictness this whole borrow checker is actually<00:00:58.960> very<00:00:59.280> powerful 00:01:00.470 --> 00:01:00.480 align:start position:0% actually very powerful 00:01:00.480 --> 00:01:03.110 align:start position:0% actually very powerful at<00:01:00.719> compile<00:01:01.120> time<00:01:01.359> you<00:01:01.520> can<00:01:01.680> prove<00:01:02.480> uh<00:01:02.800> a<00:01:02.960> lot 00:01:03.110 --> 00:01:03.120 align:start position:0% at compile time you can prove uh a lot 00:01:03.120 --> 00:01:05.350 align:start position:0% at compile time you can prove uh a lot of<00:01:03.199> invariance<00:01:04.159> uh<00:01:04.239> that<00:01:04.479> your<00:01:04.640> thread<00:01:05.040> safe 00:01:05.350 --> 00:01:05.360 align:start position:0% of invariance uh that your thread safe 00:01:05.360 --> 00:01:09.510 align:start position:0% of invariance uh that your thread safe that<00:01:05.600> your<00:01:06.479> uh<00:01:06.640> memor<00:01:06.799> is<00:01:07.119> safe<00:01:07.920> um<00:01:08.640> so<00:01:08.960> you<00:01:09.200> can 00:01:09.510 --> 00:01:09.520 align:start position:0% that your uh memor is safe um so you can 00:01:09.520 --> 00:01:12.870 align:start position:0% that your uh memor is safe um so you can yeah<00:01:10.400> you<00:01:10.640> can<00:01:11.040> uh<00:01:11.520> let<00:01:11.760> an<00:01:11.920> agent<00:01:12.240> code<00:01:12.720> with 00:01:12.870 --> 00:01:12.880 align:start position:0% yeah you can uh let an agent code with 00:01:12.880 --> 00:01:14.149 align:start position:0% yeah you can uh let an agent code with much<00:01:13.040> more<00:01:13.280> confidence 00:01:14.149 --> 00:01:14.159 align:start position:0% much more confidence 00:01:14.159 --> 00:01:15.910 align:start position:0% much more confidence so<00:01:14.400> basically<00:01:14.799> now<00:01:15.119> people<00:01:15.360> do<00:01:15.520> not<00:01:15.680> really 00:01:15.910 --> 00:01:15.920 align:start position:0% so basically now people do not really 00:01:15.920 --> 00:01:18.789 align:start position:0% so basically now people do not really have<00:01:16.080> to<00:01:16.720> fully<00:01:17.040> understand<00:01:18.080> what's<00:01:18.400> going<00:01:18.560> on 00:01:18.789 --> 00:01:18.799 align:start position:0% have to fully understand what's going on 00:01:18.799 --> 00:01:20.310 align:start position:0% have to fully understand what's going on because<00:01:19.040> if<00:01:19.200> you<00:01:19.360> have<00:01:19.439> a<00:01:19.600> general<00:01:19.759> idea<00:01:20.080> for<00:01:20.159> a 00:01:20.310 --> 00:01:20.320 align:start position:0% because if you have a general idea for a 00:01:20.320 --> 00:01:22.070 align:start position:0% because if you have a general idea for a good<00:01:20.479> engineer<00:01:21.280> and<00:01:21.439> you<00:01:21.600> can<00:01:21.680> unleash<00:01:21.920> your 00:01:22.070 --> 00:01:22.080 align:start position:0% good engineer and you can unleash your 00:01:22.080 --> 00:01:23.030 align:start position:0% good engineer and you can unleash your agent<00:01:22.400> on<00:01:22.560> Rust, 00:01:23.030 --> 00:01:23.040 align:start position:0% agent on Rust, 00:01:23.040 --> 00:01:23.429 align:start position:0% agent on Rust, yeah, 00:01:23.429 --> 00:01:23.439 align:start position:0% yeah, 00:01:23.439 --> 00:01:27.429 align:start position:0% yeah, it<00:01:23.759> will<00:01:23.920> be<00:01:24.080> better<00:01:25.200> than<00:01:26.320> equivalent<00:01:27.200> blob 00:01:27.429 --> 00:01:27.439 align:start position:0% it will be better than equivalent blob 00:01:27.439 --> 00:01:28.710 align:start position:0% it will be better than equivalent blob of<00:01:27.600> Python. 00:01:28.710 --> 00:01:28.720 align:start position:0% of Python. 00:01:28.720 --> 00:01:30.710 align:start position:0% of Python. Yeah,<00:01:28.960> in<00:01:29.119> Rust<00:01:29.520> I<00:01:29.759> found<00:01:29.920> it<00:01:30.159> to<00:01:30.320> be<00:01:30.400> a<00:01:30.560> lot 00:01:30.710 --> 00:01:30.720 align:start position:0% Yeah, in Rust I found it to be a lot 00:01:30.720 --> 00:01:32.550 align:start position:0% Yeah, in Rust I found it to be a lot better<00:01:30.880> than<00:01:31.040> it<00:01:31.200> is<00:01:31.360> in<00:01:31.520> Python.<00:01:32.079> The<00:01:32.159> the 00:01:32.550 --> 00:01:32.560 align:start position:0% better than it is in Python. The the 00:01:32.560 --> 00:01:34.710 align:start position:0% better than it is in Python. The the agent<00:01:33.040> has<00:01:33.200> much<00:01:33.360> more<00:01:33.520> information<00:01:34.240> uh<00:01:34.400> given 00:01:34.710 --> 00:01:34.720 align:start position:0% agent has much more information uh given 00:01:34.720 --> 00:01:36.870 align:start position:0% agent has much more information uh given back<00:01:34.880> from<00:01:35.119> the<00:01:35.439> compiler.<00:01:36.079> I<00:01:36.320> would<00:01:36.479> still 00:01:36.870 --> 00:01:36.880 align:start position:0% back from the compiler. I would still 00:01:36.880 --> 00:01:39.510 align:start position:0% back from the compiler. I would still say<00:01:37.680> you<00:01:37.920> need<00:01:38.000> to<00:01:38.159> be<00:01:38.240> a<00:01:38.400> good<00:01:38.640> engineer<00:01:39.200> to 00:01:39.510 --> 00:01:39.520 align:start position:0% say you need to be a good engineer to 00:01:39.520 --> 00:01:41.510 align:start position:0% say you need to be a good engineer to get<00:01:39.759> them<00:01:39.840> the<00:01:40.000> best<00:01:40.240> out<00:01:40.400> of<00:01:40.479> it<00:01:41.119> and<00:01:41.280> getting 00:01:41.510 --> 00:01:41.520 align:start position:0% get them the best out of it and getting 00:01:41.520 --> 00:01:44.390 align:start position:0% get them the best out of it and getting in<00:01:41.600> the<00:01:41.759> loop<00:01:41.920> is<00:01:42.159> still<00:01:42.320> very<00:01:42.560> important 00:01:44.390 --> 00:01:44.400 align:start position:0% in the loop is still very important 00:01:44.400 --> 00:01:48.389 align:start position:0% in the loop is still very important in<00:01:44.640> my<00:01:44.880> opinion.<00:01:45.200> But<00:01:45.680> uh<00:01:46.720> yeah<00:01:47.200> it<00:01:47.520> was<00:01:47.680> a<00:01:48.240> a 00:01:48.389 --> 00:01:48.399 align:start position:0% in my opinion. But uh yeah it was a a 00:01:48.399 --> 00:01:49.990 align:start position:0% in my opinion. But uh yeah it was a a lucky<00:01:48.720> shot<00:01:48.960> in<00:01:49.119> that<00:01:49.280> sense. 00:01:49.990 --> 00:01:50.000 align:start position:0% lucky shot in that sense. 00:01:50.000 --> 00:01:51.990 align:start position:0% lucky shot in that sense. So<00:01:50.399> uh<00:01:50.560> polars<00:01:51.040> right?<00:01:51.280> So<00:01:51.439> basically<00:01:51.759> like 00:01:51.990 --> 00:01:52.000 align:start position:0% So uh polars right? So basically like 00:01:52.000 --> 00:01:53.749 align:start position:0% So uh polars right? So basically like there<00:01:52.240> is<00:01:52.320> pandas<00:01:52.880> there<00:01:52.960> is<00:01:53.119> polars<00:01:53.600> there 00:01:53.749 --> 00:01:53.759 align:start position:0% there is pandas there is polars there 00:01:53.759 --> 00:01:55.030 align:start position:0% there is pandas there is polars there are<00:01:53.920> data<00:01:54.159> frames 00:01:55.030 --> 00:01:55.040 align:start position:0% are data frames 00:01:55.040 --> 00:01:57.590 align:start position:0% are data frames in<00:01:55.680> spark.<00:01:56.399> How<00:01:56.640> did<00:01:56.880> you<00:01:57.040> come<00:01:57.200> up<00:01:57.360> with<00:01:57.520> the 00:01:57.590 --> 00:01:57.600 align:start position:0% in spark. How did you come up with the 00:01:57.600 --> 00:02:00.069 align:start position:0% in spark. How did you come up with the idea<00:01:57.840> of<00:01:58.000> polars?<00:01:58.640> What<00:01:58.880> makes<00:01:59.040> it<00:01:59.280> special? 00:02:00.069 --> 00:02:00.079 align:start position:0% idea of polars? What makes it special? 00:02:00.079 --> 00:02:02.389 align:start position:0% idea of polars? What makes it special? Uh<00:02:00.320> you<00:02:00.560> have<00:02:00.719> a<00:02:00.880> growing<00:02:01.280> community 00:02:02.389 --> 00:02:02.399 align:start position:0% Uh you have a growing community 00:02:02.399 --> 00:02:05.429 align:start position:0% Uh you have a growing community like<00:02:03.040> what's<00:02:03.680> what's<00:02:04.479> special<00:02:04.719> about<00:02:04.960> polars 00:02:05.429 --> 00:02:05.439 align:start position:0% like what's what's special about polars 00:02:05.439 --> 00:02:07.830 align:start position:0% like what's what's special about polars which<00:02:05.680> makes<00:02:05.840> it<00:02:06.640> a<00:02:06.799> good<00:02:07.119> choice<00:02:07.360> for<00:02:07.520> data 00:02:07.830 --> 00:02:07.840 align:start position:0% which makes it a good choice for data 00:02:07.840 --> 00:02:09.029 align:start position:0% which makes it a good choice for data frames? 00:02:09.029 --> 00:02:09.039 align:start position:0% frames? 00:02:09.039 --> 00:02:11.830 align:start position:0% frames? Well<00:02:09.280> when<00:02:09.440> I<00:02:09.599> started<00:02:09.840> polars<00:02:10.399> you<00:02:11.360> you<00:02:11.680> only 00:02:11.830 --> 00:02:11.840 align:start position:0% Well when I started polars you you only 00:02:11.840 --> 00:02:13.910 align:start position:0% Well when I started polars you you only had<00:02:12.000> pondos<00:02:12.400> it's<00:02:12.560> a<00:02:12.720> def<00:02:12.800> facto<00:02:13.360> dataf<00:02:13.680> frame 00:02:13.910 --> 00:02:13.920 align:start position:0% had pondos it's a def facto dataf frame 00:02:13.920 --> 00:02:17.750 align:start position:0% had pondos it's a def facto dataf frame library.<00:02:14.480> Um<00:02:15.040> and<00:02:15.280> pandas<00:02:16.000> was<00:02:16.319> very<00:02:17.280> uh 00:02:17.750 --> 00:02:17.760 align:start position:0% library. Um and pandas was very uh 00:02:17.760 --> 00:02:19.670 align:start position:0% library. Um and pandas was very uh powerful<00:02:18.080> in<00:02:18.319> a<00:02:18.480> sense<00:02:18.720> with<00:02:18.879> a<00:02:19.120> very<00:02:19.360> rich 00:02:19.670 --> 00:02:19.680 align:start position:0% powerful in a sense with a very rich 00:02:19.680 --> 00:02:21.190 align:start position:0% powerful in a sense with a very rich API.<00:02:20.160> You<00:02:20.319> could<00:02:20.400> do<00:02:20.480> a<00:02:20.640> lot<00:02:20.720> of<00:02:20.800> stuff<00:02:20.959> but<00:02:21.120> it 00:02:21.190 --> 00:02:21.200 align:start position:0% API. You could do a lot of stuff but it 00:02:21.200 --> 00:02:23.270 align:start position:0% API. You could do a lot of stuff but it was<00:02:21.360> not<00:02:21.440> very<00:02:21.680> predictable<00:02:22.000> in<00:02:22.239> the<00:02:22.319> API. 00:02:23.270 --> 00:02:23.280 align:start position:0% was not very predictable in the API. 00:02:23.280 --> 00:02:25.589 align:start position:0% was not very predictable in the API. Um<00:02:23.920> everything<00:02:24.160> was<00:02:24.400> quite<00:02:24.640> local<00:02:24.959> and<00:02:25.120> API 00:02:25.589 --> 00:02:25.599 align:start position:0% Um everything was quite local and API 00:02:25.599 --> 00:02:26.630 align:start position:0% Um everything was quite local and API could 00:02:26.630 --> 00:02:26.640 align:start position:0% could 00:02:26.640 --> 00:02:28.790 align:start position:0% could there<00:02:26.800> was<00:02:26.959> no<00:02:27.200> consistent<00:02:27.599> data<00:02:27.920> model<00:02:28.560> but 00:02:28.790 --> 00:02:28.800 align:start position:0% there was no consistent data model but 00:02:28.800 --> 00:02:30.790 align:start position:0% there was no consistent data model but that<00:02:29.520> never<00:02:29.760> made<00:02:29.920> a<00:02:30.080> lot<00:02:30.160> of<00:02:30.239> sense<00:02:30.400> to<00:02:30.560> me. 00:02:30.790 --> 00:02:30.800 align:start position:0% that never made a lot of sense to me. 00:02:30.800 --> 00:02:32.790 align:start position:0% that never made a lot of sense to me. But<00:02:30.879> also<00:02:31.200> pandas 00:02:32.790 --> 00:02:32.800 align:start position:0% But also pandas 00:02:32.800 --> 00:02:35.750 align:start position:0% But also pandas is<00:02:33.120> in<00:02:33.360> the<00:02:33.599> business<00:02:33.920> of<00:02:34.480> of<00:02:35.200> data 00:02:35.750 --> 00:02:35.760 align:start position:0% is in the business of of data 00:02:35.760 --> 00:02:38.229 align:start position:0% is in the business of of data processing.<00:02:36.800> However, 00:02:38.229 --> 00:02:38.239 align:start position:0% processing. However, 00:02:38.239 --> 00:02:41.670 align:start position:0% processing. However, it<00:02:38.879> didn't<00:02:39.360> look<00:02:39.599> as<00:02:39.840> much<00:02:40.480> to<00:02:40.879> databases<00:02:41.440> or 00:02:41.670 --> 00:02:41.680 align:start position:0% it didn't look as much to databases or 00:02:41.680 --> 00:02:43.910 align:start position:0% it didn't look as much to databases or query<00:02:42.000> engines<00:02:42.879> in<00:02:43.040> general.<00:02:43.519> It<00:02:43.680> didn't<00:02:43.840> make 00:02:43.910 --> 00:02:43.920 align:start position:0% query engines in general. It didn't make 00:02:43.920 --> 00:02:46.390 align:start position:0% query engines in general. It didn't make a<00:02:44.160> query<00:02:44.400> plan,<00:02:44.800> didn't<00:02:45.040> make<00:02:45.760> didn't<00:02:46.080> do<00:02:46.160> any 00:02:46.390 --> 00:02:46.400 align:start position:0% a query plan, didn't make didn't do any 00:02:46.400 --> 00:02:49.830 align:start position:0% a query plan, didn't make didn't do any query<00:02:46.640> optimization.<00:02:48.000> Uh<00:02:48.319> it<00:02:48.640> utilized<00:02:49.120> NumPy 00:02:49.830 --> 00:02:49.840 align:start position:0% query optimization. Uh it utilized NumPy 00:02:49.840 --> 00:02:53.030 align:start position:0% query optimization. Uh it utilized NumPy or<00:02:50.160> Python<00:02:50.640> itself<00:02:51.120> for<00:02:51.440> its<00:02:51.680> data<00:02:52.560> uh 00:02:53.030 --> 00:02:53.040 align:start position:0% or Python itself for its data uh 00:02:53.040 --> 00:02:57.509 align:start position:0% or Python itself for its data uh storage.<00:02:54.239> Uh<00:02:54.640> whereas<00:02:55.040> there's<00:02:55.280> a<00:02:56.720> my<00:02:57.360> there 00:02:57.509 --> 00:02:57.519 align:start position:0% storage. Uh whereas there's a my there 00:02:57.519 --> 00:03:01.589 align:start position:0% storage. Uh whereas there's a my there were<00:02:57.760> sort<00:02:58.000> of<00:02:58.319> uh<00:02:59.040> decades<00:02:59.599> of<00:03:00.160> of<00:03:00.560> research 00:03:01.589 --> 00:03:01.599 align:start position:0% were sort of uh decades of of research 00:03:01.599 --> 00:03:03.750 align:start position:0% were sort of uh decades of of research uh<00:03:01.680> within<00:03:02.080> databases<00:03:02.640> that<00:03:02.800> was<00:03:03.360> sort<00:03:03.519> of 00:03:03.750 --> 00:03:03.760 align:start position:0% uh within databases that was sort of 00:03:03.760 --> 00:03:07.430 align:start position:0% uh within databases that was sort of ignored.<00:03:04.480> Uh<00:03:04.879> I<00:03:05.120> think<00:03:05.280> it<00:03:05.440> was<00:03:06.239> Dundas<00:03:07.200> was 00:03:07.430 --> 00:03:07.440 align:start position:0% ignored. Uh I think it was Dundas was 00:03:07.440 --> 00:03:11.910 align:start position:0% ignored. Uh I think it was Dundas was mostly<00:03:08.879> uh<00:03:10.159> originated.<00:03:11.040> It<00:03:11.200> feels<00:03:11.440> like<00:03:11.680> it 00:03:11.910 --> 00:03:11.920 align:start position:0% mostly uh originated. It feels like it 00:03:11.920 --> 00:03:15.110 align:start position:0% mostly uh originated. It feels like it just<00:03:12.400> came<00:03:12.640> to<00:03:12.879> be<00:03:13.040> and<00:03:13.360> whatever<00:03:14.640> was<00:03:14.959> out 00:03:15.110 --> 00:03:15.120 align:start position:0% just came to be and whatever was out 00:03:15.120 --> 00:03:18.630 align:start position:0% just came to be and whatever was out there<00:03:15.599> was<00:03:15.920> used<00:03:16.400> but<00:03:17.360> it<00:03:17.599> wasn't<00:03:18.400> uh 00:03:18.630 --> 00:03:18.640 align:start position:0% there was used but it wasn't uh 00:03:18.640 --> 00:03:21.430 align:start position:0% there was used but it wasn't uh connected<00:03:19.200> to<00:03:19.519> database<00:03:20.000> research<00:03:21.040> and<00:03:21.200> when 00:03:21.430 --> 00:03:21.440 align:start position:0% connected to database research and when 00:03:21.440 --> 00:03:24.470 align:start position:0% connected to database research and when I<00:03:21.680> started<00:03:22.239> writing<00:03:22.959> I<00:03:23.120> wanted<00:03:23.360> to<00:03:23.519> be<00:03:24.159> to<00:03:24.319> be 00:03:24.470 --> 00:03:24.480 align:start position:0% I started writing I wanted to be to be 00:03:24.480 --> 00:03:27.030 align:start position:0% I started writing I wanted to be to be multi-threaded<00:03:25.360> I<00:03:25.599> wanted<00:03:25.920> to<00:03:26.080> be<00:03:26.319> lazy<00:03:26.720> and<00:03:26.879> I 00:03:27.030 --> 00:03:27.040 align:start position:0% multi-threaded I wanted to be lazy and I 00:03:27.040 --> 00:03:29.750 align:start position:0% multi-threaded I wanted to be lazy and I wanted<00:03:27.280> to<00:03:27.680> have<00:03:28.000> very<00:03:28.239> optimizer 00:03:29.750 --> 00:03:29.760 align:start position:0% wanted to have very optimizer 00:03:29.760 --> 00:03:31.589 align:start position:0% wanted to have very optimizer um<00:03:30.000> and<00:03:30.159> the<00:03:30.319> more<00:03:30.480> I<00:03:30.640> learned<00:03:30.879> about<00:03:31.040> it<00:03:31.440> the 00:03:31.589 --> 00:03:31.599 align:start position:0% um and the more I learned about it the 00:03:31.599 --> 00:03:33.589 align:start position:0% um and the more I learned about it the more<00:03:31.760> I<00:03:32.000> felt<00:03:32.319> like<00:03:32.560> this<00:03:32.799> should<00:03:33.040> exist<00:03:33.280> for<00:03:33.440> a 00:03:33.589 --> 00:03:33.599 align:start position:0% more I felt like this should exist for a 00:03:33.599 --> 00:03:34.789 align:start position:0% more I felt like this should exist for a single<00:03:33.840> node 00:03:34.789 --> 00:03:34.799 align:start position:0% single node 00:03:34.799 --> 00:03:36.390 align:start position:0% single node I<00:03:35.040> want<00:03:35.120> to<00:03:35.200> get<00:03:35.360> maximum<00:03:35.760> performance<00:03:36.159> out<00:03:36.319> of 00:03:36.390 --> 00:03:36.400 align:start position:0% I want to get maximum performance out of 00:03:36.400 --> 00:03:36.949 align:start position:0% I want to get maximum performance out of my<00:03:36.480> laptop 00:03:36.949 --> 00:03:36.959 align:start position:0% my laptop 00:03:36.959 --> 00:03:38.630 align:start position:0% my laptop because<00:03:37.120> pend<00:03:37.519> was<00:03:37.599> kind<00:03:37.760> of<00:03:37.920> the<00:03:38.000> design<00:03:38.480> way 00:03:38.630 --> 00:03:38.640 align:start position:0% because pend was kind of the design way 00:03:38.640 --> 00:03:40.630 align:start position:0% because pend was kind of the design way to<00:03:38.799> slice<00:03:39.040> and<00:03:39.200> dice<00:03:39.599> tables<00:03:40.080> right<00:03:40.319> so<00:03:40.480> it 00:03:40.630 --> 00:03:40.640 align:start position:0% to slice and dice tables right so it 00:03:40.640 --> 00:03:42.470 align:start position:0% to slice and dice tables right so it came<00:03:40.879> from<00:03:40.959> the<00:03:41.120> need<00:03:41.280> of<00:03:41.440> data<00:03:41.680> scientists 00:03:42.470 --> 00:03:42.480 align:start position:0% came from the need of data scientists 00:03:42.480 --> 00:03:45.589 align:start position:0% came from the need of data scientists not<00:03:43.280> uh<00:03:43.760> from<00:03:44.000> the<00:03:44.159> background<00:03:44.560> of<00:03:45.040> database 00:03:45.589 --> 00:03:45.599 align:start position:0% not uh from the background of database 00:03:45.599 --> 00:03:47.430 align:start position:0% not uh from the background of database engineers<00:03:46.000> who<00:03:46.319> properly<00:03:46.720> can<00:03:46.879> populate<00:03:47.280> the 00:03:47.430 --> 00:03:47.440 align:start position:0% engineers who properly can populate the 00:03:47.440 --> 00:03:49.110 align:start position:0% engineers who properly can populate the tables.<00:03:47.840> Yeah,<00:03:48.080> but<00:03:48.239> there's<00:03:48.480> a<00:03:48.640> in<00:03:48.879> the<00:03:48.959> vend 00:03:49.110 --> 00:03:49.120 align:start position:0% tables. Yeah, but there's a in the vend 00:03:49.120 --> 00:03:51.589 align:start position:0% tables. Yeah, but there's a in the vend diagram<00:03:49.680> you<00:03:49.920> need<00:03:50.319> both.<00:03:50.879> Also,<00:03:51.200> a<00:03:51.360> data 00:03:51.589 --> 00:03:51.599 align:start position:0% diagram you need both. Also, a data 00:03:51.599 --> 00:03:54.149 align:start position:0% diagram you need both. Also, a data scientist<00:03:52.000> was<00:03:52.239> waiting<00:03:52.640> for<00:03:53.360> it<00:03:53.599> was<00:03:53.920> pretty 00:03:54.149 --> 00:03:54.159 align:start position:0% scientist was waiting for it was pretty 00:03:54.159 --> 00:03:56.550 align:start position:0% scientist was waiting for it was pretty common<00:03:54.400> to<00:03:55.360> be<00:03:55.599> waiting<00:03:55.840> for<00:03:56.000> a<00:03:56.159> join<00:03:56.400> in 00:03:56.550 --> 00:03:56.560 align:start position:0% common to be waiting for a join in 00:03:56.560 --> 00:03:58.710 align:start position:0% common to be waiting for a join in pandas<00:03:57.040> and<00:03:57.120> you<00:03:57.280> you<00:03:57.599> just<00:03:57.760> saw<00:03:58.000> one<00:03:58.239> core<00:03:58.560> in 00:03:58.710 --> 00:03:58.720 align:start position:0% pandas and you you just saw one core in 00:03:58.720 --> 00:04:02.229 align:start position:0% pandas and you you just saw one core in your<00:03:59.200> your<00:04:00.239> uh<00:04:00.400> system<00:04:00.720> monitor<00:04:01.519> uh<00:04:01.840> chugging 00:04:02.229 --> 00:04:02.239 align:start position:0% your your uh system monitor uh chugging 00:04:02.239 --> 00:04:03.910 align:start position:0% your your uh system monitor uh chugging away<00:04:02.480> for<00:04:02.799> 10<00:04:03.040> minutes. 00:04:03.910 --> 00:04:03.920 align:start position:0% away for 10 minutes. 00:04:03.920 --> 00:04:05.110 align:start position:0% away for 10 minutes. Why<00:04:04.080> not<00:04:04.239> use<00:04:04.400> all<00:04:04.560> the<00:04:04.640> cores? 00:04:05.110 --> 00:04:05.120 align:start position:0% Why not use all the cores? 00:04:05.120 --> 00:04:07.350 align:start position:0% Why not use all the cores? Right.<00:04:05.680> Right.<00:04:05.920> Right. 00:04:07.350 --> 00:04:07.360 align:start position:0% Right. Right. Right. 00:04:07.360 --> 00:04:09.350 align:start position:0% Right. Right. Right. I'm<00:04:07.680> very<00:04:07.920> curious<00:04:08.159> that<00:04:08.400> you<00:04:08.560> said<00:04:08.799> about<00:04:09.120> not 00:04:09.350 --> 00:04:09.360 align:start position:0% I'm very curious that you said about not 00:04:09.360 --> 00:04:12.149 align:start position:0% I'm very curious that you said about not predictable<00:04:10.239> because<00:04:10.959> I've<00:04:11.280> been<00:04:11.519> you<00:04:11.760> know 00:04:12.149 --> 00:04:12.159 align:start position:0% predictable because I've been you know 00:04:12.159 --> 00:04:14.309 align:start position:0% predictable because I've been you know early<00:04:12.720> organizer<00:04:13.280> of<00:04:13.439> scala<00:04:13.760> communities<00:04:14.239> and 00:04:14.309 --> 00:04:14.319 align:start position:0% early organizer of scala communities and 00:04:14.319 --> 00:04:16.870 align:start position:0% early organizer of scala communities and spark.<00:04:14.560> So<00:04:14.799> spark<00:04:15.200> is<00:04:15.360> effectively<00:04:16.479> in<00:04:16.720> my 00:04:16.870 --> 00:04:16.880 align:start position:0% spark. So spark is effectively in my 00:04:16.880 --> 00:04:19.509 align:start position:0% spark. So spark is effectively in my view<00:04:17.120> and<00:04:17.359> marski<00:04:18.400> had<00:04:18.639> a<00:04:18.799> talk<00:04:18.880> at<00:04:19.280> my 00:04:19.509 --> 00:04:19.519 align:start position:0% view and marski had a talk at my 00:04:19.519 --> 00:04:21.590 align:start position:0% view and marski had a talk at my conference<00:04:20.239> scale<00:04:20.560> by<00:04:20.799> way<00:04:21.040> that<00:04:21.280> basically 00:04:21.590 --> 00:04:21.600 align:start position:0% conference scale by way that basically 00:04:21.600 --> 00:04:24.710 align:start position:0% conference scale by way that basically spark<00:04:21.919> is<00:04:22.160> distributed<00:04:23.199> scola.<00:04:24.000> So<00:04:24.320> scola 00:04:24.710 --> 00:04:24.720 align:start position:0% spark is distributed scola. So scola 00:04:24.720 --> 00:04:26.950 align:start position:0% spark is distributed scola. So scola collection<00:04:25.520> was<00:04:25.680> the<00:04:25.919> thing<00:04:26.320> which<00:04:26.639> gave 00:04:26.950 --> 00:04:26.960 align:start position:0% collection was the thing which gave 00:04:26.960 --> 00:04:29.510 align:start position:0% collection was the thing which gave birth<00:04:27.280> to<00:04:27.600> this<00:04:27.919> modern<00:04:28.800> data<00:04:29.120> processing 00:04:29.510 --> 00:04:29.520 align:start position:0% birth to this modern data processing 00:04:29.520 --> 00:04:30.710 align:start position:0% birth to this modern data processing where<00:04:29.680> you<00:04:29.840> treat<00:04:30.080> everything<00:04:30.320> as<00:04:30.560> a 00:04:30.710 --> 00:04:30.720 align:start position:0% where you treat everything as a 00:04:30.720 --> 00:04:33.590 align:start position:0% where you treat everything as a collection<00:04:31.199> and<00:04:31.440> so<00:04:31.600> the<00:04:31.759> the<00:04:32.160> winning<00:04:33.199> uh<00:04:33.360> of 00:04:33.590 --> 00:04:33.600 align:start position:0% collection and so the the winning uh of 00:04:33.600 --> 00:04:35.830 align:start position:0% collection and so the the winning uh of spark<00:04:34.560> it<00:04:34.800> you<00:04:34.880> know<00:04:35.120> had<00:04:35.280> this<00:04:35.520> moment 00:04:35.830 --> 00:04:35.840 align:start position:0% spark it you know had this moment 00:04:35.840 --> 00:04:37.670 align:start position:0% spark it you know had this moment because<00:04:36.560> everything<00:04:36.880> you<00:04:37.040> would<00:04:37.199> think<00:04:37.440> about 00:04:37.670 --> 00:04:37.680 align:start position:0% because everything you would think about 00:04:37.680 --> 00:04:40.469 align:start position:0% because everything you would think about in<00:04:37.919> the<00:04:38.000> API<00:04:38.800> map<00:04:39.199> filter<00:04:39.600> reduce<00:04:40.240> you<00:04:40.400> know 00:04:40.469 --> 00:04:40.479 align:start position:0% in the API map filter reduce you know 00:04:40.479 --> 00:04:42.629 align:start position:0% in the API map filter reduce you know it's<00:04:40.639> object-oriented<00:04:41.280> so<00:04:41.600> something<00:04:42.160> map 00:04:42.629 --> 00:04:42.639 align:start position:0% it's object-oriented so something map 00:04:42.639 --> 00:04:44.870 align:start position:0% it's object-oriented so something map would<00:04:42.880> map<00:04:43.280> something<00:04:43.759> filter<00:04:44.080> would<00:04:44.320> filter 00:04:44.870 --> 00:04:44.880 align:start position:0% would map something filter would filter 00:04:44.880 --> 00:04:46.550 align:start position:0% would map something filter would filter so<00:04:45.120> do<00:04:45.280> you<00:04:45.440> mean<00:04:45.680> predictability<00:04:46.240> in<00:04:46.400> that 00:04:46.550 --> 00:04:46.560 align:start position:0% so do you mean predictability in that 00:04:46.560 --> 00:04:48.230 align:start position:0% so do you mean predictability in that sense<00:04:46.800> like<00:04:46.960> you<00:04:47.120> think<00:04:47.199> of<00:04:47.360> the<00:04:47.520> method<00:04:48.080> it 00:04:48.230 --> 00:04:48.240 align:start position:0% sense like you think of the method it 00:04:48.240 --> 00:04:50.150 align:start position:0% sense like you think of the method it should<00:04:48.400> exist<00:04:48.639> on<00:04:48.880> data<00:04:49.199> frame<00:04:49.600> and<00:04:49.840> it<00:04:50.000> should 00:04:50.150 --> 00:04:50.160 align:start position:0% should exist on data frame and it should 00:04:50.160 --> 00:04:51.670 align:start position:0% should exist on data frame and it should be<00:04:50.240> there<00:04:50.400> with<00:04:50.639> a<00:04:50.800> proper<00:04:51.040> name 00:04:51.670 --> 00:04:51.680 align:start position:0% be there with a proper name 00:04:51.680 --> 00:04:55.590 align:start position:0% be there with a proper name yes<00:04:52.080> but<00:04:52.880> um<00:04:53.360> because<00:04:53.759> we<00:04:54.240> make<00:04:54.720> a<00:04:55.120> logical 00:04:55.590 --> 00:04:55.600 align:start position:0% yes but um because we make a logical 00:04:55.600 --> 00:04:58.710 align:start position:0% yes but um because we make a logical plan.<00:04:56.400> Um<00:04:57.280> we<00:04:57.600> had<00:04:57.759> to<00:04:58.000> come<00:04:58.080> up<00:04:58.240> with<00:04:58.320> a<00:04:58.560> data 00:04:58.710 --> 00:04:58.720 align:start position:0% plan. Um we had to come up with a data 00:04:58.720 --> 00:05:00.870 align:start position:0% plan. Um we had to come up with a data model<00:04:58.960> and<00:04:59.120> it<00:04:59.280> should<00:04:59.759> like<00:05:00.320> relational 00:05:00.870 --> 00:05:00.880 align:start position:0% model and it should like relational 00:05:00.880 --> 00:05:04.230 align:start position:0% model and it should like relational model.<00:05:01.280> The<00:05:01.440> relational<00:05:01.840> data<00:05:02.160> is<00:05:02.320> a<00:05:02.560> logical 00:05:04.230 --> 00:05:04.240 align:start position:0% model. The relational data is a logical 00:05:04.240 --> 00:05:06.629 align:start position:0% model. The relational data is a logical uh<00:05:04.800> if<00:05:05.040> you<00:05:05.360> if<00:05:05.600> you<00:05:05.759> have<00:05:05.840> an<00:05:06.000> API<00:05:06.320> and<00:05:06.479> you 00:05:06.629 --> 00:05:06.639 align:start position:0% uh if you if you have an API and you 00:05:06.639 --> 00:05:08.310 align:start position:0% uh if you if you have an API and you make<00:05:06.800> a<00:05:06.960> method<00:05:07.280> on<00:05:07.520> top<00:05:07.680> of<00:05:07.759> a<00:05:08.000> data 00:05:08.310 --> 00:05:08.320 align:start position:0% make a method on top of a data 00:05:08.320 --> 00:05:09.430 align:start position:0% make a method on top of a data container, 00:05:09.430 --> 00:05:09.440 align:start position:0% container, 00:05:09.440 --> 00:05:11.110 align:start position:0% container, but<00:05:09.680> that<00:05:10.080> method 00:05:11.110 --> 00:05:11.120 align:start position:0% but that method 00:05:11.120 --> 00:05:13.430 align:start position:0% but that method can<00:05:11.360> just<00:05:11.600> do<00:05:11.919> local<00:05:12.320> implementations<00:05:13.199> and 00:05:13.430 --> 00:05:13.440 align:start position:0% can just do local implementations and 00:05:13.440 --> 00:05:17.990 align:start position:0% can just do local implementations and doesn't<00:05:13.759> go<00:05:14.000> through<00:05:14.639> a<00:05:16.000> a<00:05:16.160> a 00:05:17.990 --> 00:05:18.000 align:start position:0% doesn't go through a a a 00:05:18.000 --> 00:05:19.350 align:start position:0% doesn't go through a a a engine. 00:05:19.350 --> 00:05:19.360 align:start position:0% engine. 00:05:19.360 --> 00:05:21.830 align:start position:0% engine. It's<00:05:19.680> very<00:05:20.240> hard<00:05:20.479> to<00:05:20.720> make<00:05:20.800> that<00:05:21.120> consistently 00:05:21.830 --> 00:05:21.840 align:start position:0% It's very hard to make that consistently 00:05:21.840 --> 00:05:24.230 align:start position:0% It's very hard to make that consistently behaving.<00:05:22.880> But<00:05:23.039> if<00:05:23.199> it<00:05:23.520> is<00:05:23.680> forced<00:05:23.919> to<00:05:24.160> go 00:05:24.230 --> 00:05:24.240 align:start position:0% behaving. But if it is forced to go 00:05:24.240 --> 00:05:26.230 align:start position:0% behaving. But if it is forced to go through<00:05:24.479> the<00:05:24.639> engine<00:05:25.360> through<00:05:25.600> a<00:05:25.840> virtual 00:05:26.230 --> 00:05:26.240 align:start position:0% through the engine through a virtual 00:05:26.240 --> 00:05:29.110 align:start position:0% through the engine through a virtual machine<00:05:27.360> then<00:05:28.000> you<00:05:28.240> have<00:05:28.400> to<00:05:28.560> come<00:05:28.720> up<00:05:28.800> with<00:05:28.960> a 00:05:29.110 --> 00:05:29.120 align:start position:0% machine then you have to come up with a 00:05:29.120 --> 00:05:30.310 align:start position:0% machine then you have to come up with a data<00:05:29.280> model.<00:05:29.600> You<00:05:29.759> have<00:05:29.840> to<00:05:29.919> come<00:05:30.000> up<00:05:30.160> with 00:05:30.310 --> 00:05:30.320 align:start position:0% data model. You have to come up with 00:05:30.320 --> 00:05:31.590 align:start position:0% data model. You have to come up with something<00:05:30.560> consistent<00:05:31.039> otherwise 00:05:31.590 --> 00:05:31.600 align:start position:0% something consistent otherwise 00:05:31.600 --> 00:05:31.909 align:start position:0% something consistent otherwise right 00:05:31.909 --> 00:05:31.919 align:start position:0% right 00:05:31.919 --> 00:05:32.710 align:start position:0% right it<00:05:32.080> will<00:05:32.240> not<00:05:32.400> work. 00:05:32.710 --> 00:05:32.720 align:start position:0% it will not work. 00:05:32.720 --> 00:05:34.629 align:start position:0% it will not work. So<00:05:32.960> you<00:05:33.199> so<00:05:33.440> you<00:05:33.600> mean<00:05:33.759> predictability<00:05:34.400> in 00:05:34.629 --> 00:05:34.639 align:start position:0% So you so you mean predictability in 00:05:34.639 --> 00:05:36.070 align:start position:0% So you so you mean predictability in terms<00:05:34.800> of<00:05:34.960> consistent<00:05:35.520> performance 00:05:36.070 --> 00:05:36.080 align:start position:0% terms of consistent performance 00:05:36.080 --> 00:05:37.189 align:start position:0% terms of consistent performance consistent<00:05:36.479> performance<00:05:36.800> but<00:05:36.960> also 00:05:37.189 --> 00:05:37.199 align:start position:0% consistent performance but also 00:05:37.199 --> 00:05:39.350 align:start position:0% consistent performance but also consistent<00:05:37.600> behavior<00:05:38.080> consistent<00:05:38.720> types. 00:05:39.350 --> 00:05:39.360 align:start position:0% consistent behavior consistent types. 00:05:39.360 --> 00:05:39.909 align:start position:0% consistent behavior consistent types. Yeah. 00:05:39.909 --> 00:05:39.919 align:start position:0% Yeah. 00:05:39.919 --> 00:05:42.950 align:start position:0% Yeah. Um<00:05:41.280> what 00:05:42.950 --> 00:05:42.960 align:start position:0% Um what 00:05:42.960 --> 00:05:46.230 align:start position:0% Um what um<00:05:43.440> pandas<00:05:44.160> was<00:05:44.400> non<00:05:44.720> strict.<00:05:45.440> So<00:05:45.680> it<00:05:45.919> used<00:05:46.080> to 00:05:46.230 --> 00:05:46.240 align:start position:0% um pandas was non strict. So it used to 00:05:46.240 --> 00:05:51.350 align:start position:0% um pandas was non strict. So it used to be<00:05:46.400> that<00:05:46.880> if<00:05:47.199> you<00:05:48.400> uh<00:05:48.720> parsed<00:05:49.199> a 00:05:51.350 --> 00:05:51.360 align:start position:0% be that if you uh parsed a 00:05:51.360 --> 00:05:53.510 align:start position:0% be that if you uh parsed a an<00:05:51.600> example<00:05:52.000> it<00:05:52.160> had<00:05:52.320> a<00:05:52.479> column<00:05:52.639> of<00:05:52.800> strings 00:05:53.510 --> 00:05:53.520 align:start position:0% an example it had a column of strings 00:05:53.520 --> 00:05:56.710 align:start position:0% an example it had a column of strings and<00:05:54.400> it<00:05:54.720> had<00:05:54.880> to<00:05:55.039> parse<00:05:55.360> a<00:05:55.520> date<00:05:56.160> column<00:05:56.479> out<00:05:56.639> of 00:05:56.710 --> 00:05:56.720 align:start position:0% and it had to parse a date column out of 00:05:56.720 --> 00:05:58.070 align:start position:0% and it had to parse a date column out of that<00:05:56.960> you<00:05:57.039> had<00:05:57.120> to<00:05:57.280> parse<00:05:57.440> that<00:05:57.600> as<00:05:57.759> a<00:05:57.840> date 00:05:58.070 --> 00:05:58.080 align:start position:0% that you had to parse that as a date 00:05:58.080 --> 00:05:58.710 align:start position:0% that you had to parse that as a date column. 00:05:58.710 --> 00:05:58.720 align:start position:0% column. 00:05:58.720 --> 00:06:01.029 align:start position:0% column. What<00:05:58.880> it<00:05:59.039> used<00:05:59.199> to<00:05:59.360> do<00:05:59.520> was<00:06:00.160> run<00:06:00.479> Python 00:06:01.029 --> 00:06:01.039 align:start position:0% What it used to do was run Python 00:06:01.039 --> 00:06:03.990 align:start position:0% What it used to do was run Python daytime<00:06:01.520> parsing<00:06:02.320> on<00:06:02.639> every<00:06:03.360> element 00:06:03.990 --> 00:06:04.000 align:start position:0% daytime parsing on every element 00:06:04.000 --> 00:06:04.870 align:start position:0% daytime parsing on every element sequentially. 00:06:04.870 --> 00:06:04.880 align:start position:0% sequentially. 00:06:04.880 --> 00:06:05.430 align:start position:0% sequentially. Uhhuh. 00:06:05.430 --> 00:06:05.440 align:start position:0% Uhhuh. 00:06:05.440 --> 00:06:07.990 align:start position:0% Uhhuh. But<00:06:05.600> if<00:06:05.840> the<00:06:06.080> first<00:06:06.479> one<00:06:06.800> was<00:06:07.280> date<00:06:07.680> month 00:06:07.990 --> 00:06:08.000 align:start position:0% But if the first one was date month 00:06:08.000 --> 00:06:11.110 align:start position:0% But if the first one was date month years<00:06:08.319> and<00:06:08.479> the<00:06:08.560> other<00:06:08.800> was<00:06:09.360> years<00:06:10.319> uh<00:06:10.560> month 00:06:11.110 --> 00:06:11.120 align:start position:0% years and the other was years uh month 00:06:11.120 --> 00:06:11.590 align:start position:0% years and the other was years uh month day. 00:06:11.590 --> 00:06:11.600 align:start position:0% day. 00:06:11.600 --> 00:06:13.830 align:start position:0% day. Yeah.<00:06:12.479> It<00:06:12.720> just<00:06:12.960> swapped<00:06:13.199> them<00:06:13.440> around<00:06:13.680> and 00:06:13.830 --> 00:06:13.840 align:start position:0% Yeah. It just swapped them around and 00:06:13.840 --> 00:06:14.790 align:start position:0% Yeah. It just swapped them around and you<00:06:14.000> had 00:06:14.790 --> 00:06:14.800 align:start position:0% you had 00:06:14.800 --> 00:06:17.110 align:start position:0% you had or<00:06:15.039> the<00:06:15.280> first<00:06:15.919> one<00:06:16.160> was<00:06:16.400> milliseconds,<00:06:16.960> the 00:06:17.110 --> 00:06:17.120 align:start position:0% or the first one was milliseconds, the 00:06:17.120 --> 00:06:19.029 align:start position:0% or the first one was milliseconds, the second<00:06:17.280> was<00:06:17.440> seconds.<00:06:17.759> You<00:06:17.919> had<00:06:18.080> not<00:06:18.160> a<00:06:18.400> un<00:06:18.800> you 00:06:19.029 --> 00:06:19.039 align:start position:0% second was seconds. You had not a un you 00:06:19.039 --> 00:06:20.790 align:start position:0% second was seconds. You had not a un you did<00:06:19.199> not<00:06:19.360> have<00:06:19.440> a<00:06:19.600> unified 00:06:20.790 --> 00:06:20.800 align:start position:0% did not have a unified 00:06:20.800 --> 00:06:22.150 align:start position:0% did not have a unified data<00:06:21.120> type<00:06:21.280> on<00:06:21.520> a<00:06:21.680> column. 00:06:22.150 --> 00:06:22.160 align:start position:0% data type on a column. 00:06:22.160 --> 00:06:22.629 align:start position:0% data type on a column. Mhm. 00:06:22.629 --> 00:06:22.639 align:start position:0% Mhm. 00:06:22.639 --> 00:06:24.710 align:start position:0% Mhm. Uh<00:06:22.880> you<00:06:23.120> would<00:06:23.280> have<00:06:23.520> different<00:06:24.080> data<00:06:24.400> types 00:06:24.710 --> 00:06:24.720 align:start position:0% Uh you would have different data types 00:06:24.720 --> 00:06:25.350 align:start position:0% Uh you would have different data types within. 00:06:25.350 --> 00:06:25.360 align:start position:0% within. 00:06:25.360 --> 00:06:26.710 align:start position:0% within. So<00:06:25.520> you<00:06:25.759> didn't<00:06:25.840> really<00:06:26.080> type<00:06:26.319> the<00:06:26.479> column 00:06:26.710 --> 00:06:26.720 align:start position:0% So you didn't really type the column 00:06:26.720 --> 00:06:27.350 align:start position:0% So you didn't really type the column properly. 00:06:27.350 --> 00:06:27.360 align:start position:0% properly. 00:06:27.360 --> 00:06:29.510 align:start position:0% properly. No,<00:06:27.840> it<00:06:28.080> was<00:06:28.160> not<00:06:28.400> consistent<00:06:28.800> in<00:06:29.039> its<00:06:29.280> type 00:06:29.510 --> 00:06:29.520 align:start position:0% No, it was not consistent in its type 00:06:29.520 --> 00:06:29.909 align:start position:0% No, it was not consistent in its type model 00:06:29.909 --> 00:06:29.919 align:start position:0% model 00:06:29.919 --> 00:06:31.749 align:start position:0% model because<00:06:30.160> Python<00:06:30.639> is<00:06:30.880> not<00:06:31.039> really<00:06:31.280> a<00:06:31.440> type 00:06:31.749 --> 00:06:31.759 align:start position:0% because Python is not really a type 00:06:31.759 --> 00:06:33.510 align:start position:0% because Python is not really a type language<00:06:32.240> and<00:06:32.400> so<00:06:32.639> people<00:06:32.960> don't<00:06:33.199> think<00:06:33.360> in 00:06:33.510 --> 00:06:33.520 align:start position:0% language and so people don't think in 00:06:33.520 --> 00:06:34.469 align:start position:0% language and so people don't think in terms<00:06:33.759> of<00:06:33.840> types. 00:06:34.469 --> 00:06:34.479 align:start position:0% terms of types. 00:06:34.479 --> 00:06:36.150 align:start position:0% terms of types. Yes.<00:06:34.800> But<00:06:34.880> it<00:06:35.039> could<00:06:35.120> have<00:06:35.280> been<00:06:35.360> in<00:06:35.520> pandas. 00:06:36.150 --> 00:06:36.160 align:start position:0% Yes. But it could have been in pandas. 00:06:36.160 --> 00:06:37.270 align:start position:0% Yes. But it could have been in pandas. That's<00:06:36.319> right.<00:06:36.560> That's<00:06:36.800> right. 00:06:37.270 --> 00:06:37.280 align:start position:0% That's right. That's right. 00:06:37.280 --> 00:06:39.830 align:start position:0% That's right. That's right. I<00:06:37.440> mean<00:06:37.759> Python<00:06:38.160> is<00:06:38.400> just<00:06:38.960> the<00:06:39.199> host<00:06:39.440> language. 00:06:39.830 --> 00:06:39.840 align:start position:0% I mean Python is just the host language. 00:06:39.840 --> 00:06:41.110 align:start position:0% I mean Python is just the host language. Correct.<00:06:40.080> You<00:06:40.160> can<00:06:40.319> make<00:06:40.479> anything<00:06:40.800> out. 00:06:41.110 --> 00:06:41.120 align:start position:0% Correct. You can make anything out. 00:06:41.120 --> 00:06:42.710 align:start position:0% Correct. You can make anything out. Correct.<00:06:41.520> But<00:06:41.759> because<00:06:41.919> it<00:06:42.160> comes<00:06:42.319> from<00:06:42.479> that 00:06:42.710 --> 00:06:42.720 align:start position:0% Correct. But because it comes from that 00:06:42.720 --> 00:06:44.629 align:start position:0% Correct. But because it comes from that background,<00:06:43.120> people<00:06:43.440> who<00:06:43.680> did<00:06:43.919> this<00:06:44.160> did<00:06:44.479> not 00:06:44.629 --> 00:06:44.639 align:start position:0% background, people who did this did not 00:06:44.639 --> 00:06:47.510 align:start position:0% background, people who did this did not really<00:06:44.960> think<00:06:45.199> of<00:06:45.440> imposing<00:06:46.400> a<00:06:46.560> column<00:06:46.880> type. 00:06:47.510 --> 00:06:47.520 align:start position:0% really think of imposing a column type. 00:06:47.520 --> 00:06:52.550 align:start position:0% really think of imposing a column type. Yeah.<00:06:48.000> And<00:06:48.720> um<00:06:50.160> my<00:06:50.479> experience<00:06:51.120> was<00:06:51.520> also<00:06:51.919> that 00:06:52.550 --> 00:06:52.560 align:start position:0% Yeah. And um my experience was also that 00:06:52.560 --> 00:06:55.430 align:start position:0% Yeah. And um my experience was also that my<00:06:52.800> types<00:06:53.120> could<00:06:53.360> change<00:06:53.919> in<00:06:54.960> production 00:06:55.430 --> 00:06:55.440 align:start position:0% my types could change in production 00:06:55.440 --> 00:06:57.830 align:start position:0% my types could change in production workloads<00:06:56.080> depending<00:06:56.400> on<00:06:56.639> what<00:06:56.880> kind<00:06:57.039> of<00:06:57.199> data 00:06:57.830 --> 00:06:57.840 align:start position:0% workloads depending on what kind of data 00:06:57.840 --> 00:06:58.710 align:start position:0% workloads depending on what kind of data went<00:06:58.080> in<00:06:58.319> there. 00:06:58.710 --> 00:06:58.720 align:start position:0% went in there. 00:06:58.720 --> 00:06:59.029 align:start position:0% went in there. Okay, 00:06:59.029 --> 00:06:59.039 align:start position:0% Okay, 00:06:59.039 --> 00:07:00.469 align:start position:0% Okay, I<00:06:59.199> had<00:06:59.280> the<00:06:59.440> same<00:06:59.599> query,<00:06:59.919> but<00:07:00.080> I<00:07:00.160> had<00:07:00.240> a 00:07:00.469 --> 00:07:00.479 align:start position:0% I had the same query, but I had a 00:07:00.479 --> 00:07:02.550 align:start position:0% I had the same query, but I had a rolling<00:07:01.199> window<00:07:01.440> of<00:07:01.680> data.<00:07:02.000> And<00:07:02.160> all<00:07:02.319> of<00:07:02.400> a 00:07:02.550 --> 00:07:02.560 align:start position:0% rolling window of data. And all of a 00:07:02.560 --> 00:07:04.629 align:start position:0% rolling window of data. And all of a sudden,<00:07:03.280> I<00:07:03.520> was<00:07:03.599> not<00:07:03.759> indexing<00:07:04.240> with<00:07:04.400> a 00:07:04.629 --> 00:07:04.639 align:start position:0% sudden, I was not indexing with a 00:07:04.639 --> 00:07:06.390 align:start position:0% sudden, I was not indexing with a integer,<00:07:05.039> but<00:07:05.199> I<00:07:05.360> was<00:07:05.599> indexing<00:07:06.080> with<00:07:06.240> a 00:07:06.390 --> 00:07:06.400 align:start position:0% integer, but I was indexing with a 00:07:06.400 --> 00:07:09.270 align:start position:0% integer, but I was indexing with a float.<00:07:06.800> And<00:07:06.960> my<00:07:07.520> production<00:07:07.919> pipeline<00:07:08.400> broke 00:07:09.270 --> 00:07:09.280 align:start position:0% float. And my production pipeline broke 00:07:09.280 --> 00:07:11.350 align:start position:0% float. And my production pipeline broke uh<00:07:09.520> 40<00:07:09.840> minutes.<00:07:10.080> I<00:07:10.319> will<00:07:10.400> be<00:07:10.560> terrified<00:07:11.039> as<00:07:11.199> a 00:07:11.350 --> 00:07:11.360 align:start position:0% uh 40 minutes. I will be terrified as a 00:07:11.360 --> 00:07:12.790 align:start position:0% uh 40 minutes. I will be terrified as a strongly<00:07:11.759> typed<00:07:12.080> person.<00:07:12.560> Yes, 00:07:12.790 --> 00:07:12.800 align:start position:0% strongly typed person. Yes, 00:07:12.800 --> 00:07:14.230 align:start position:0% strongly typed person. Yes, I<00:07:13.039> will<00:07:13.120> be<00:07:13.280> terrified<00:07:13.680> of<00:07:13.840> this. 00:07:14.230 --> 00:07:14.240 align:start position:0% I will be terrified of this. 00:07:14.240 --> 00:07:16.870 align:start position:0% I will be terrified of this. So<00:07:14.400> these<00:07:14.800> things,<00:07:15.840> yeah,<00:07:16.080> these<00:07:16.400> are<00:07:16.560> paper 00:07:16.870 --> 00:07:16.880 align:start position:0% So these things, yeah, these are paper 00:07:16.880 --> 00:07:19.749 align:start position:0% So these things, yeah, these are paper cuts<00:07:17.199> that<00:07:17.360> hurt<00:07:17.599> me<00:07:17.759> and<00:07:18.000> I<00:07:18.160> wanted<00:07:18.479> that<00:07:19.440> uh 00:07:19.749 --> 00:07:19.759 align:start position:0% cuts that hurt me and I wanted that uh 00:07:19.759 --> 00:07:21.270 align:start position:0% cuts that hurt me and I wanted that uh fixed<00:07:20.000> in<00:07:20.160> a<00:07:20.319> data<00:07:20.479> frame<00:07:20.720> library. 00:07:21.270 --> 00:07:21.280 align:start position:0% fixed in a data frame library. 00:07:21.280 --> 00:07:24.309 align:start position:0% fixed in a data frame library. Interesting.<00:07:22.000> Interesting.<00:07:23.039> So<00:07:23.680> basically, 00:07:24.309 --> 00:07:24.319 align:start position:0% Interesting. Interesting. So basically, 00:07:24.319 --> 00:07:26.070 align:start position:0% Interesting. Interesting. So basically, did<00:07:24.479> you<00:07:24.639> start<00:07:24.880> with<00:07:25.039> Rust<00:07:25.440> right<00:07:25.680> away<00:07:25.919> out 00:07:26.070 --> 00:07:26.080 align:start position:0% did you start with Rust right away out 00:07:26.080 --> 00:07:26.790 align:start position:0% did you start with Rust right away out of<00:07:26.160> the<00:07:26.319> gate? 00:07:26.790 --> 00:07:26.800 align:start position:0% of the gate? 00:07:26.800 --> 00:07:27.189 align:start position:0% of the gate? Yeah. 00:07:27.189 --> 00:07:27.199 align:start position:0% Yeah. 00:07:27.199 --> 00:07:27.670 align:start position:0% Yeah. Okay. 00:07:27.670 --> 00:07:27.680 align:start position:0% Okay. 00:07:27.680 --> 00:07:30.710 align:start position:0% Okay. Yeah.<00:07:28.000> The<00:07:28.240> initial<00:07:28.560> goal,<00:07:29.280> so<00:07:29.840> Paul's<00:07:30.479> story 00:07:30.710 --> 00:07:30.720 align:start position:0% Yeah. The initial goal, so Paul's story 00:07:30.720 --> 00:07:32.710 align:start position:0% Yeah. The initial goal, so Paul's story of<00:07:30.960> just<00:07:31.280> moving<00:07:31.680> goalpost.<00:07:32.240> The<00:07:32.400> initial 00:07:32.710 --> 00:07:32.720 align:start position:0% of just moving goalpost. The initial 00:07:32.720 --> 00:07:35.110 align:start position:0% of just moving goalpost. The initial goal<00:07:32.960> was,<00:07:33.680> oh,<00:07:33.919> I<00:07:34.160> really<00:07:34.319> like<00:07:34.560> this<00:07:34.800> this 00:07:35.110 --> 00:07:35.120 align:start position:0% goal was, oh, I really like this this 00:07:35.120 --> 00:07:37.270 align:start position:0% goal was, oh, I really like this this library<00:07:35.759> or<00:07:36.000> I<00:07:36.160> really<00:07:36.400> like<00:07:36.639> this<00:07:36.880> this 00:07:37.270 --> 00:07:37.280 align:start position:0% library or I really like this this 00:07:37.280 --> 00:07:39.430 align:start position:0% library or I really like this this language<00:07:37.599> in<00:07:37.840> Rust.<00:07:38.639> It<00:07:38.880> doesn't<00:07:38.960> have<00:07:39.039> a<00:07:39.199> data 00:07:39.430 --> 00:07:39.440 align:start position:0% language in Rust. It doesn't have a data 00:07:39.440 --> 00:07:42.870 align:start position:0% language in Rust. It doesn't have a data frame<00:07:39.599> library.<00:07:40.160> Let's<00:07:40.800> make<00:07:41.120> one.<00:07:41.680> Uh<00:07:42.639> I 00:07:42.870 --> 00:07:42.880 align:start position:0% frame library. Let's make one. Uh I 00:07:42.880 --> 00:07:46.469 align:start position:0% frame library. Let's make one. Uh I worked<00:07:43.120> my<00:07:43.360> first<00:07:43.599> join.<00:07:44.880> Uh 00:07:46.469 --> 00:07:46.479 align:start position:0% worked my first join. Uh 00:07:46.479 --> 00:07:49.029 align:start position:0% worked my first join. Uh did<00:07:46.720> a<00:07:46.800> benchmark<00:07:47.120> with<00:07:47.280> pondas<00:07:47.840> and<00:07:48.400> my<00:07:48.720> join 00:07:49.029 --> 00:07:49.039 align:start position:0% did a benchmark with pondas and my join 00:07:49.039 --> 00:07:51.350 align:start position:0% did a benchmark with pondas and my join was<00:07:49.199> super<00:07:49.520> slow.<00:07:49.919> So<00:07:50.080> the<00:07:50.400> the<00:07:50.720> next<00:07:50.880> goal<00:07:51.120> was 00:07:51.350 --> 00:07:51.360 align:start position:0% was super slow. So the the next goal was 00:07:51.360 --> 00:07:52.710 align:start position:0% was super slow. So the the next goal was make<00:07:51.520> it<00:07:51.680> faster<00:07:51.919> than<00:07:52.080> pondas. 00:07:52.710 --> 00:07:52.720 align:start position:0% make it faster than pondas. 00:07:52.720 --> 00:07:53.110 align:start position:0% make it faster than pondas. Mhm. 00:07:53.110 --> 00:07:53.120 align:start position:0% Mhm. 00:07:53.120 --> 00:07:55.029 align:start position:0% Mhm. Then<00:07:53.360> the<00:07:53.599> next<00:07:53.759> goal<00:07:54.080> was<00:07:54.479> okay<00:07:54.720> make<00:07:54.879> a 00:07:55.029 --> 00:07:55.039 align:start position:0% Then the next goal was okay make a 00:07:55.039 --> 00:07:58.150 align:start position:0% Then the next goal was okay make a python<00:07:55.440> API.<00:07:56.639> Then<00:07:57.199> initially<00:07:57.599> I<00:07:57.840> wanted<00:07:58.000> to 00:07:58.150 --> 00:07:58.160 align:start position:0% python API. Then initially I wanted to 00:07:58.160 --> 00:08:01.510 align:start position:0% python API. Then initially I wanted to copy<00:07:58.319> the<00:07:58.479> pom<00:07:59.039> API<00:07:59.599> and<00:07:59.759> then<00:07:59.919> I<00:08:00.080> learned 00:08:01.510 --> 00:08:01.520 align:start position:0% copy the pom API and then I learned 00:08:01.520 --> 00:08:04.309 align:start position:0% copy the pom API and then I learned what<00:08:02.160> what's<00:08:02.639> the<00:08:02.879> consistence<00:08:03.599> behavior?<00:08:04.160> I 00:08:04.309 --> 00:08:04.319 align:start position:0% what what's the consistence behavior? I 00:08:04.319 --> 00:08:05.270 align:start position:0% what what's the consistence behavior? I could<00:08:04.479> not<00:08:04.639> find<00:08:04.879> it. 00:08:05.270 --> 00:08:05.280 align:start position:0% could not find it. 00:08:05.280 --> 00:08:07.430 align:start position:0% could not find it. Mhm.<00:08:05.680> Uh<00:08:06.479> and<00:08:06.639> then<00:08:06.800> I<00:08:07.039> learned<00:08:07.199> about 00:08:07.430 --> 00:08:07.440 align:start position:0% Mhm. Uh and then I learned about 00:08:07.440 --> 00:08:09.909 align:start position:0% Mhm. Uh and then I learned about databases<00:08:07.919> and<00:08:08.080> about<00:08:08.240> lazy<00:08:09.039> programming<00:08:09.599> and 00:08:09.909 --> 00:08:09.919 align:start position:0% databases and about lazy programming and 00:08:09.919 --> 00:08:12.469 align:start position:0% databases and about lazy programming and then<00:08:10.400> at<00:08:10.639> that<00:08:10.879> point<00:08:11.120> I<00:08:11.680> learned<00:08:12.000> about<00:08:12.240> the 00:08:12.469 --> 00:08:12.479 align:start position:0% then at that point I learned about the 00:08:12.479 --> 00:08:14.070 align:start position:0% then at that point I learned about the optimizer<00:08:12.960> and<00:08:13.120> I<00:08:13.280> thought<00:08:13.440> okay<00:08:13.680> this<00:08:13.919> should 00:08:14.070 --> 00:08:14.080 align:start position:0% optimizer and I thought okay this should 00:08:14.080 --> 00:08:14.790 align:start position:0% optimizer and I thought okay this should exist. 00:08:14.790 --> 00:08:14.800 align:start position:0% exist. 00:08:14.800 --> 00:08:14.950 align:start position:0% exist. Mh. 00:08:14.950 --> 00:08:14.960 align:start position:0% Mh. 00:08:14.960 --> 00:08:16.950 align:start position:0% Mh. Uh<00:08:15.199> but<00:08:15.360> it<00:08:15.599> was<00:08:15.759> constantly<00:08:16.400> moving 00:08:16.950 --> 00:08:16.960 align:start position:0% Uh but it was constantly moving 00:08:16.960 --> 00:08:19.510 align:start position:0% Uh but it was constantly moving goalpost.<00:08:17.680> So<00:08:18.400> the<00:08:18.560> initial<00:08:18.879> goal<00:08:19.120> was<00:08:19.280> just 00:08:19.510 --> 00:08:19.520 align:start position:0% goalpost. So the initial goal was just 00:08:19.520 --> 00:08:21.749 align:start position:0% goalpost. So the initial goal was just to<00:08:19.680> across<00:08:20.080> the<00:08:20.400> library. 00:08:21.749 --> 00:08:21.759 align:start position:0% to across the library. 00:08:21.759 --> 00:08:24.550 align:start position:0% to across the library. Currently<00:08:22.560> I<00:08:22.800> want<00:08:23.280> polars<00:08:23.840> to<00:08:24.080> be<00:08:24.240> the 00:08:24.550 --> 00:08:24.560 align:start position:0% Currently I want polars to be the 00:08:24.560 --> 00:08:26.309 align:start position:0% Currently I want polars to be the fastest<00:08:24.879> engine<00:08:25.199> for<00:08:25.440> any<00:08:25.680> scale.<00:08:25.919> I<00:08:26.160> also 00:08:26.309 --> 00:08:26.319 align:start position:0% fastest engine for any scale. I also 00:08:26.319 --> 00:08:28.150 align:start position:0% fastest engine for any scale. I also wanted<00:08:26.560> to<00:08:26.720> be<00:08:26.800> the<00:08:26.960> fastest<00:08:27.199> on<00:08:27.440> distributed. 00:08:28.150 --> 00:08:28.160 align:start position:0% wanted to be the fastest on distributed. 00:08:28.160 --> 00:08:28.550 align:start position:0% wanted to be the fastest on distributed. Mhm. 00:08:28.550 --> 00:08:28.560 align:start position:0% Mhm. 00:08:28.560 --> 00:08:30.390 align:start position:0% Mhm. When<00:08:28.720> I<00:08:28.879> started<00:08:29.280> this<00:08:29.440> was<00:08:29.599> never<00:08:29.759> my<00:08:29.919> goal.<00:08:30.240> I 00:08:30.390 --> 00:08:30.400 align:start position:0% When I started this was never my goal. I 00:08:30.400 --> 00:08:32.070 align:start position:0% When I started this was never my goal. I would<00:08:30.479> have<00:08:30.639> laughed<00:08:31.199> in<00:08:31.440> your<00:08:31.599> face<00:08:31.759> if<00:08:31.919> you 00:08:32.070 --> 00:08:32.080 align:start position:0% would have laughed in your face if you 00:08:32.080 --> 00:08:34.389 align:start position:0% would have laughed in your face if you said<00:08:32.240> we<00:08:32.399> would<00:08:32.560> be<00:08:32.719> doing<00:08:32.880> this.<00:08:33.200> So<00:08:33.599> um 00:08:34.389 --> 00:08:34.399 align:start position:0% said we would be doing this. So um 00:08:34.399 --> 00:08:36.550 align:start position:0% said we would be doing this. So um yeah.<00:08:35.039> you<00:08:35.279> are<00:08:35.440> basically<00:08:35.760> growing<00:08:36.159> with<00:08:36.399> the 00:08:36.550 --> 00:08:36.560 align:start position:0% yeah. you are basically growing with the 00:08:36.560 --> 00:08:38.070 align:start position:0% yeah. you are basically growing with the community<00:08:37.120> and<00:08:37.519> we're<00:08:37.680> here<00:08:37.839> at<00:08:37.919> the 00:08:38.070 --> 00:08:38.080 align:start position:0% community and we're here at the 00:08:38.080 --> 00:08:39.670 align:start position:0% community and we're here at the community<00:08:38.399> conference.<00:08:38.800> I'm<00:08:38.959> super<00:08:39.200> curious. 00:08:39.670 --> 00:08:39.680 align:start position:0% community conference. I'm super curious. 00:08:39.680 --> 00:08:41.750 align:start position:0% community conference. I'm super curious. It's<00:08:39.919> PI<00:08:40.240> data.<00:08:40.479> It's<00:08:40.640> Python.<00:08:41.279> We're<00:08:41.440> in<00:08:41.599> the 00:08:41.750 --> 00:08:41.760 align:start position:0% It's PI data. It's Python. We're in the 00:08:41.760 --> 00:08:43.909 align:start position:0% It's PI data. It's Python. We're in the same<00:08:41.839> boat<00:08:42.080> at<00:08:42.240> lake<00:08:42.479> sale.<00:08:42.880> We<00:08:43.120> have<00:08:43.680> you<00:08:43.839> know 00:08:43.909 --> 00:08:43.919 align:start position:0% same boat at lake sale. We have you know 00:08:43.919 --> 00:08:46.550 align:start position:0% same boat at lake sale. We have you know rust<00:08:44.320> engine<00:08:44.720> but<00:08:45.040> we<00:08:45.680> uh<00:08:45.920> most<00:08:46.240> of<00:08:46.399> the 00:08:46.550 --> 00:08:46.560 align:start position:0% rust engine but we uh most of the 00:08:46.560 --> 00:08:48.230 align:start position:0% rust engine but we uh most of the customers<00:08:46.959> talk<00:08:47.200> with<00:08:47.279> through<00:08:47.440> pi<00:08:47.760> spark 00:08:48.230 --> 00:08:48.240 align:start position:0% customers talk with through pi spark 00:08:48.240 --> 00:08:49.910 align:start position:0% customers talk with through pi spark because<00:08:48.640> support<00:08:48.959> spark<00:08:49.200> connect<00:08:49.600> right.<00:08:49.760> So 00:08:49.910 --> 00:08:49.920 align:start position:0% because support spark connect right. So 00:08:49.920 --> 00:08:52.150 align:start position:0% because support spark connect right. So this<00:08:50.080> is<00:08:50.160> kind<00:08:50.399> of<00:08:50.640> so<00:08:50.800> we<00:08:51.040> say<00:08:51.279> pip<00:08:51.519> install<00:08:51.839> pi 00:08:52.150 --> 00:08:52.160 align:start position:0% this is kind of so we say pip install pi 00:08:52.160 --> 00:08:54.870 align:start position:0% this is kind of so we say pip install pi sale.<00:08:52.560> So<00:08:52.720> how<00:08:52.959> do<00:08:53.200> you<00:08:54.000> interact<00:08:54.480> with<00:08:54.720> the 00:08:54.870 --> 00:08:54.880 align:start position:0% sale. So how do you interact with the 00:08:54.880 --> 00:08:57.509 align:start position:0% sale. So how do you interact with the python<00:08:55.200> ecosystem?<00:08:56.560> uh<00:08:56.720> and<00:08:56.959> like<00:08:57.200> I<00:08:57.440> think 00:08:57.509 --> 00:08:57.519 align:start position:0% python ecosystem? uh and like I think 00:08:57.519 --> 00:09:00.389 align:start position:0% python ecosystem? uh and like I think now<00:08:57.839> a<00:08:58.080> lot<00:08:58.240> of<00:08:58.399> folks<00:08:59.120> you<00:08:59.360> know<00:08:59.600> in<00:08:59.839> in<00:09:00.160> Bay 00:09:00.389 --> 00:09:00.399 align:start position:0% now a lot of folks you know in in Bay 00:09:00.399 --> 00:09:02.550 align:start position:0% now a lot of folks you know in in Bay Area<00:09:00.640> where<00:09:01.200> you<00:09:01.360> know<00:09:01.440> I'm<00:09:01.680> from<00:09:02.080> basically 00:09:02.550 --> 00:09:02.560 align:start position:0% Area where you know I'm from basically 00:09:02.560 --> 00:09:05.190 align:start position:0% Area where you know I'm from basically solentic<00:09:03.279> and<00:09:03.519> so<00:09:03.920> like<00:09:04.080> they<00:09:04.480> all<00:09:04.720> agents<00:09:05.040> are 00:09:05.190 --> 00:09:05.200 align:start position:0% solentic and so like they all agents are 00:09:05.200 --> 00:09:08.790 align:start position:0% solentic and so like they all agents are in<00:09:05.360> Python.<00:09:06.080> How<00:09:06.240> how<00:09:06.560> do<00:09:06.720> you<00:09:07.120> see<00:09:08.160> uh<00:09:08.320> polar 00:09:08.790 --> 00:09:08.800 align:start position:0% in Python. How how do you see uh polar 00:09:08.800 --> 00:09:11.110 align:start position:0% in Python. How how do you see uh polar kind<00:09:08.959> of<00:09:09.120> being<00:09:09.440> in<00:09:09.680> this<00:09:10.320> Python<00:09:10.720> ecosystem 00:09:11.110 --> 00:09:11.120 align:start position:0% kind of being in this Python ecosystem 00:09:11.120 --> 00:09:12.790 align:start position:0% kind of being in this Python ecosystem and<00:09:11.360> specifically<00:09:11.760> in<00:09:11.920> the<00:09:12.240> ecosystem<00:09:12.640> which 00:09:12.790 --> 00:09:12.800 align:start position:0% and specifically in the ecosystem which 00:09:12.800 --> 00:09:13.829 align:start position:0% and specifically in the ecosystem which is<00:09:13.040> all<00:09:13.200> Python<00:09:13.519> now? 00:09:13.829 --> 00:09:13.839 align:start position:0% is all Python now? 00:09:13.839 --> 00:09:16.389 align:start position:0% is all Python now? Yeah.<00:09:14.480> Yeah.<00:09:14.640> So<00:09:14.800> Polar<00:09:15.279> is<00:09:15.440> a<00:09:15.519> Python<00:09:16.000> first 00:09:16.389 --> 00:09:16.399 align:start position:0% Yeah. Yeah. So Polar is a Python first 00:09:16.399 --> 00:09:18.230 align:start position:0% Yeah. Yeah. So Polar is a Python first library.<00:09:16.880> We<00:09:17.040> focus<00:09:17.279> mostly<00:09:17.600> on<00:09:17.760> our<00:09:17.920> Python 00:09:18.230 --> 00:09:18.240 align:start position:0% library. We focus mostly on our Python 00:09:18.240 --> 00:09:22.550 align:start position:0% library. We focus mostly on our Python API.<00:09:18.720> It's<00:09:18.959> a<00:09:19.519> Python<00:09:20.399> data<00:09:20.720> frame<00:09:21.120> API. 00:09:22.550 --> 00:09:22.560 align:start position:0% API. It's a Python data frame API. 00:09:22.560 --> 00:09:25.190 align:start position:0% API. It's a Python data frame API. Um<00:09:23.279> so<00:09:23.440> in<00:09:23.600> that<00:09:23.760> sense<00:09:24.000> we're<00:09:24.240> good.<00:09:24.880> uh<00:09:25.040> we're 00:09:25.190 --> 00:09:25.200 align:start position:0% Um so in that sense we're good. uh we're 00:09:25.200 --> 00:09:28.470 align:start position:0% Um so in that sense we're good. uh we're in<00:09:25.360> the<00:09:25.440> corpus<00:09:26.160> of<00:09:26.880> all<00:09:27.120> the<00:09:27.600> big<00:09:28.000> the<00:09:28.320> big 00:09:28.470 --> 00:09:28.480 align:start position:0% in the corpus of all the big the big 00:09:28.480 --> 00:09:30.230 align:start position:0% in the corpus of all the big the big models.<00:09:28.880> So<00:09:29.360> models<00:09:29.680> know<00:09:29.839> how<00:09:29.920> to<00:09:30.080> write 00:09:30.230 --> 00:09:30.240 align:start position:0% models. So models know how to write 00:09:30.240 --> 00:09:31.430 align:start position:0% models. So models know how to write polars. 00:09:31.430 --> 00:09:31.440 align:start position:0% polars. 00:09:31.440 --> 00:09:34.790 align:start position:0% polars. Uh<00:09:31.760> a<00:09:32.000> benefit<00:09:32.480> is<00:09:32.800> that<00:09:33.279> at<00:09:34.160> before<00:09:34.480> we<00:09:34.640> run 00:09:34.790 --> 00:09:34.800 align:start position:0% Uh a benefit is that at before we run 00:09:34.800 --> 00:09:36.310 align:start position:0% Uh a benefit is that at before we run the<00:09:34.959> query<00:09:35.200> you<00:09:35.440> can<00:09:35.519> also<00:09:35.680> do<00:09:35.839> we<00:09:36.000> can<00:09:36.160> already 00:09:36.310 --> 00:09:36.320 align:start position:0% the query you can also do we can already 00:09:36.320 --> 00:09:37.990 align:start position:0% the query you can also do we can already do<00:09:36.480> a<00:09:36.640> lot<00:09:36.720> of<00:09:36.800> type<00:09:37.040> check.<00:09:37.279> So<00:09:37.440> we 00:09:37.990 --> 00:09:38.000 align:start position:0% do a lot of type check. So we 00:09:38.000 --> 00:09:41.190 align:start position:0% do a lot of type check. So we so<00:09:38.240> you<00:09:38.399> write<00:09:38.560> a<00:09:38.720> query<00:09:39.360> you<00:09:39.839> the<00:09:40.080> agent<00:09:40.399> gets 00:09:41.190 --> 00:09:41.200 align:start position:0% so you write a query you the agent gets 00:09:41.200 --> 00:09:43.910 align:start position:0% so you write a query you the agent gets feedback<00:09:41.839> on<00:09:42.080> the<00:09:42.240> types<00:09:42.800> or<00:09:43.279> errors<00:09:43.680> before 00:09:43.910 --> 00:09:43.920 align:start position:0% feedback on the types or errors before 00:09:43.920 --> 00:09:45.670 align:start position:0% feedback on the types or errors before it<00:09:44.080> runs<00:09:44.320> a<00:09:44.480> query.<00:09:44.720> So<00:09:44.880> the<00:09:44.959> wrong<00:09:45.120> query<00:09:45.519> will 00:09:45.670 --> 00:09:45.680 align:start position:0% it runs a query. So the wrong query will 00:09:45.680 --> 00:09:47.509 align:start position:0% it runs a query. So the wrong query will not<00:09:45.839> go<00:09:46.080> and<00:09:46.320> reach<00:09:46.800> the 00:09:47.509 --> 00:09:47.519 align:start position:0% not go and reach the 00:09:47.519 --> 00:09:49.670 align:start position:0% not go and reach the Yeah,<00:09:47.680> there<00:09:47.839> are<00:09:48.240> still<00:09:48.640> of<00:09:48.880> course<00:09:49.200> some 00:09:49.670 --> 00:09:49.680 align:start position:0% Yeah, there are still of course some 00:09:49.680 --> 00:09:52.310 align:start position:0% Yeah, there are still of course some runtime<00:09:50.399> checks<00:09:50.800> still<00:09:51.040> but<00:09:51.360> we<00:09:51.600> try<00:09:51.760> to<00:09:52.000> catch 00:09:52.310 --> 00:09:52.320 align:start position:0% runtime checks still but we try to catch 00:09:52.320 --> 00:09:55.190 align:start position:0% runtime checks still but we try to catch as<00:09:52.560> many<00:09:52.800> errors<00:09:53.040> as<00:09:53.600> possible<00:09:54.080> up<00:09:54.240> front. 00:09:55.190 --> 00:09:55.200 align:start position:0% as many errors as possible up front. 00:09:55.200 --> 00:09:57.590 align:start position:0% as many errors as possible up front. Um<00:09:55.600> so<00:09:55.839> that's<00:09:56.080> really<00:09:56.399> beneficial<00:09:57.120> compared 00:09:57.590 --> 00:09:57.600 align:start position:0% Um so that's really beneficial compared 00:09:57.600 --> 00:09:59.910 align:start position:0% Um so that's really beneficial compared to<00:09:58.320> um 00:09:59.910 --> 00:09:59.920 align:start position:0% to um 00:09:59.920 --> 00:10:04.310 align:start position:0% to um uh<00:10:00.640> compared<00:10:00.959> to<00:10:01.200> something<00:10:01.600> like<00:10:01.760> pandas.<00:10:02.640> Um 00:10:04.310 --> 00:10:04.320 align:start position:0% uh compared to something like pandas. Um 00:10:04.320 --> 00:10:06.310 align:start position:0% uh compared to something like pandas. Um we're<00:10:04.560> also<00:10:04.800> focusing<00:10:05.040> more<00:10:05.279> on<00:10:05.440> SQL<00:10:05.839> now 00:10:06.310 --> 00:10:06.320 align:start position:0% we're also focusing more on SQL now 00:10:06.320 --> 00:10:09.590 align:start position:0% we're also focusing more on SQL now because<00:10:07.279> agents<00:10:08.320> took<00:10:08.640> that<00:10:08.800> friction<00:10:09.200> away. 00:10:09.590 --> 00:10:09.600 align:start position:0% because agents took that friction away. 00:10:09.600 --> 00:10:11.509 align:start position:0% because agents took that friction away. Humans 00:10:11.509 --> 00:10:11.519 align:start position:0% Humans 00:10:11.519 --> 00:10:15.030 align:start position:0% Humans I<00:10:11.760> mean<00:10:12.800> humans<00:10:13.760> don't<00:10:14.079> like<00:10:14.240> to<00:10:14.480> write<00:10:14.720> very 00:10:15.030 --> 00:10:15.040 align:start position:0% I mean humans don't like to write very 00:10:15.040 --> 00:10:17.670 align:start position:0% I mean humans don't like to write very complicated<00:10:15.680> SQL<00:10:16.079> strings<00:10:16.959> on<00:10:17.200> typed<00:10:17.519> an 00:10:17.670 --> 00:10:17.680 align:start position:0% complicated SQL strings on typed an 00:10:17.680 --> 00:10:19.509 align:start position:0% complicated SQL strings on typed an agent<00:10:18.000> doesn't<00:10:18.240> care. 00:10:19.509 --> 00:10:19.519 align:start position:0% agent doesn't care. 00:10:19.519 --> 00:10:22.630 align:start position:0% agent doesn't care. So<00:10:20.079> um<00:10:20.320> yeah<00:10:20.480> the<00:10:20.720> world<00:10:20.880> is<00:10:21.040> changing<00:10:21.839> so<00:10:22.320> uh 00:10:22.630 --> 00:10:22.640 align:start position:0% So um yeah the world is changing so uh 00:10:22.640 --> 00:10:24.710 align:start position:0% So um yeah the world is changing so uh looking<00:10:22.959> into<00:10:23.200> that<00:10:23.440> as<00:10:23.680> well<00:10:23.839> but<00:10:24.320> uh<00:10:24.399> I<00:10:24.640> think 00:10:24.710 --> 00:10:24.720 align:start position:0% looking into that as well but uh I think 00:10:24.720 --> 00:10:27.269 align:start position:0% looking into that as well but uh I think there's<00:10:25.040> still<00:10:25.200> merit<00:10:25.519> in<00:10:26.240> in<00:10:26.560> a<00:10:26.800> API 00:10:27.269 --> 00:10:27.279 align:start position:0% there's still merit in in a API 00:10:27.279 --> 00:10:29.269 align:start position:0% there's still merit in in a API especially<00:10:27.839> with<00:10:28.000> regard<00:10:28.240> to<00:10:28.480> composability. 00:10:29.269 --> 00:10:29.279 align:start position:0% especially with regard to composability. 00:10:29.279 --> 00:10:31.350 align:start position:0% especially with regard to composability. You<00:10:29.440> can<00:10:29.839> pass<00:10:30.160> expressions<00:10:30.560> to<00:10:30.800> functions 00:10:31.350 --> 00:10:31.360 align:start position:0% You can pass expressions to functions 00:10:31.360 --> 00:10:33.350 align:start position:0% You can pass expressions to functions let<00:10:31.519> them<00:10:31.680> generate<00:10:32.079> stuff.<00:10:32.720> So<00:10:32.800> the<00:10:33.040> meta 00:10:33.350 --> 00:10:33.360 align:start position:0% let them generate stuff. So the meta 00:10:33.360 --> 00:10:35.509 align:start position:0% let them generate stuff. So the meta programming<00:10:34.000> you<00:10:34.240> can<00:10:34.320> do<00:10:34.399> in<00:10:34.560> polars<00:10:35.040> is<00:10:35.200> very 00:10:35.509 --> 00:10:35.519 align:start position:0% programming you can do in polars is very 00:10:35.519 --> 00:10:37.190 align:start position:0% programming you can do in polars is very powerful 00:10:37.190 --> 00:10:37.200 align:start position:0% powerful 00:10:37.200 --> 00:10:38.949 align:start position:0% powerful and<00:10:37.440> it's<00:10:37.600> all<00:10:37.839> typed.<00:10:38.480> Yeah, 00:10:38.949 --> 00:10:38.959 align:start position:0% and it's all typed. Yeah, 00:10:38.959 --> 00:10:40.630 align:start position:0% and it's all typed. Yeah, very<00:10:39.279> cool.<00:10:39.519> And<00:10:39.760> so<00:10:39.920> the<00:10:40.000> last<00:10:40.240> question<00:10:40.399> over 00:10:40.630 --> 00:10:40.640 align:start position:0% very cool. And so the last question over 00:10:40.640 --> 00:10:42.389 align:start position:0% very cool. And so the last question over here<00:10:40.800> at<00:10:41.040> you<00:10:41.200> know<00:10:41.440> it's<00:10:41.680> your<00:10:41.839> hometown 00:10:42.389 --> 00:10:42.399 align:start position:0% here at you know it's your hometown 00:10:42.399 --> 00:10:44.949 align:start position:0% here at you know it's your hometown Amsterdam<00:10:43.360> right<00:10:43.600> where<00:10:43.839> Polaro<00:10:44.240> started 00:10:44.949 --> 00:10:44.959 align:start position:0% Amsterdam right where Polaro started 00:10:44.959 --> 00:10:46.790 align:start position:0% Amsterdam right where Polaro started this<00:10:45.200> is<00:10:45.360> one<00:10:45.600> of<00:10:45.680> my<00:10:45.839> favorite<00:10:46.240> conferences 00:10:46.790 --> 00:10:46.800 align:start position:0% this is one of my favorite conferences 00:10:46.800 --> 00:10:49.430 align:start position:0% this is one of my favorite conferences PI<00:10:47.040> data<00:10:47.600> I'm<00:10:47.760> coming<00:10:48.000> like<00:10:48.160> year<00:10:48.320> on<00:10:48.560> year<00:10:49.279> uh 00:10:49.430 --> 00:10:49.440 align:start position:0% PI data I'm coming like year on year uh 00:10:49.440 --> 00:10:52.550 align:start position:0% PI data I'm coming like year on year uh what's<00:10:49.839> special<00:10:50.160> about<00:10:50.720> Amsterdam<00:10:52.000> data 00:10:52.550 --> 00:10:52.560 align:start position:0% what's special about Amsterdam data 00:10:52.560 --> 00:10:55.350 align:start position:0% what's special about Amsterdam data community<00:10:53.279> like<00:10:53.519> what's<00:10:53.920> kind<00:10:54.160> of<00:10:54.640> you<00:10:54.880> know 00:10:55.350 --> 00:10:55.360 align:start position:0% community like what's kind of you know 00:10:55.360 --> 00:10:57.750 align:start position:0% community like what's kind of you know makes<00:10:55.600> this<00:10:55.839> conference<00:10:56.880> you<00:10:57.040> know<00:10:57.360> good<00:10:57.600> for 00:10:57.750 --> 00:10:57.760 align:start position:0% makes this conference you know good for 00:10:57.760 --> 00:11:00.230 align:start position:0% makes this conference you know good for you<00:10:58.399> and<00:10:58.640> page<00:10:59.440> in<00:10:59.600> general 00:11:00.230 --> 00:11:00.240 align:start position:0% you and page in general 00:11:00.240 --> 00:11:01.910 align:start position:0% you and page in general well<00:11:00.480> it's<00:11:00.720> a<00:11:00.880> it's<00:11:01.120> a<00:11:01.279> home<00:11:01.440> game<00:11:01.680> of<00:11:01.839> course 00:11:01.910 --> 00:11:01.920 align:start position:0% well it's a it's a home game of course 00:11:01.920 --> 00:11:04.470 align:start position:0% well it's a it's a home game of course so<00:11:02.160> that's<00:11:02.399> very<00:11:02.640> easy 00:11:04.470 --> 00:11:04.480 align:start position:0% so that's very easy 00:11:04.480 --> 00:11:06.310 align:start position:0% so that's very easy I<00:11:04.720> think<00:11:04.880> Amsterdam<00:11:05.440> is<00:11:05.600> great<00:11:05.839> because<00:11:06.079> of 00:11:06.310 --> 00:11:06.320 align:start position:0% I think Amsterdam is great because of 00:11:06.320 --> 00:11:09.110 align:start position:0% I think Amsterdam is great because of all<00:11:06.560> the<00:11:06.800> the<00:11:07.200> international<00:11:08.320> And<00:11:08.800> it's<00:11:08.959> a 00:11:09.110 --> 00:11:09.120 align:start position:0% all the the international And it's a 00:11:09.120 --> 00:11:11.190 align:start position:0% all the the international And it's a very<00:11:09.360> it's<00:11:09.600> one<00:11:09.760> of<00:11:09.839> the<00:11:10.000> largest<00:11:10.320> pas<00:11:10.959> I've 00:11:11.190 --> 00:11:11.200 align:start position:0% very it's one of the largest pas I've 00:11:11.200 --> 00:11:12.470 align:start position:0% very it's one of the largest pas I've been<00:11:11.279> to.<00:11:11.519> I've<00:11:11.760> been 00:11:12.470 --> 00:11:12.480 align:start position:0% been to. I've been 00:11:12.480 --> 00:11:16.310 align:start position:0% been to. I've been to<00:11:13.040> multiple<00:11:14.000> padas<00:11:14.640> across<00:11:14.959> the<00:11:15.360> globe.<00:11:15.920> But 00:11:16.310 --> 00:11:16.320 align:start position:0% to multiple padas across the globe. But 00:11:16.320 --> 00:11:16.790 align:start position:0% to multiple padas across the globe. But um 00:11:16.790 --> 00:11:16.800 align:start position:0% um 00:11:16.800 --> 00:11:18.870 align:start position:0% um yeah,<00:11:17.040> it's<00:11:17.279> always<00:11:17.440> a<00:11:17.680> big<00:11:18.000> a<00:11:18.240> big 00:11:18.870 --> 00:11:18.880 align:start position:0% yeah, it's always a big a big 00:11:18.880 --> 00:11:20.310 align:start position:0% yeah, it's always a big a big It's<00:11:18.959> a<00:11:19.120> big<00:11:19.200> one<00:11:19.360> and<00:11:19.600> one<00:11:19.760> of<00:11:19.839> my<00:11:20.000> favorites 00:11:20.310 --> 00:11:20.320 align:start position:0% It's a big one and one of my favorites 00:11:20.320 --> 00:11:20.550 align:start position:0% It's a big one and one of my favorites too. 00:11:20.550 --> 00:11:20.560 align:start position:0% too. 00:11:20.560 --> 00:11:23.670 align:start position:0% too. Yeah.<00:11:20.880> Yeah.<00:11:21.279> And<00:11:21.680> uh<00:11:21.920> just<00:11:22.160> a<00:11:22.399> lot<00:11:22.480> of<00:11:22.880> uh<00:11:23.360> I 00:11:23.670 --> 00:11:23.680 align:start position:0% Yeah. Yeah. And uh just a lot of uh I 00:11:23.680 --> 00:11:25.509 align:start position:0% Yeah. Yeah. And uh just a lot of uh I think<00:11:23.920> different 00:11:25.509 --> 00:11:25.519 align:start position:0% think different 00:11:25.519 --> 00:11:28.949 align:start position:0% think different uh<00:11:26.880> business<00:11:27.279> areas,<00:11:28.399> different<00:11:28.720> different 00:11:28.949 --> 00:11:28.959 align:start position:0% uh business areas, different different 00:11:28.959 --> 00:11:30.470 align:start position:0% uh business areas, different different fields.<00:11:29.279> So 00:11:30.470 --> 00:11:30.480 align:start position:0% fields. So 00:11:30.480 --> 00:11:32.550 align:start position:0% fields. So not<00:11:30.720> all<00:11:30.880> agents<00:11:31.680> like<00:11:31.839> they're<00:11:32.079> actual 00:11:32.550 --> 00:11:32.560 align:start position:0% not all agents like they're actual 00:11:32.560 --> 00:11:35.350 align:start position:0% not all agents like they're actual businesses<00:11:33.120> using<00:11:34.000> data<00:11:34.320> for<00:11:34.560> something, 00:11:35.350 --> 00:11:35.360 align:start position:0% businesses using data for something, 00:11:35.360 --> 00:11:36.069 align:start position:0% businesses using data for something, right?<00:11:35.680> which<00:11:35.839> is 00:11:36.069 --> 00:11:36.079 align:start position:0% right? which is 00:11:36.079 --> 00:11:38.870 align:start position:0% right? which is and<00:11:36.320> uh<00:11:36.640> them<00:11:37.120> uh<00:11:37.360> in<00:11:37.680> the<00:11:38.160> Amsterdam<00:11:38.640> is<00:11:38.800> a 00:11:38.870 --> 00:11:38.880 align:start position:0% and uh them uh in the Amsterdam is a 00:11:38.880 --> 00:11:41.829 align:start position:0% and uh them uh in the Amsterdam is a great<00:11:39.040> city<00:11:39.200> to<00:11:39.680> uh<00:11:40.399> to<00:11:40.640> have<00:11:40.800> fun.<00:11:41.200> So<00:11:41.519> uh 00:11:41.829 --> 00:11:41.839 align:start position:0% great city to uh to have fun. So uh 00:11:41.839 --> 00:11:43.670 align:start position:0% great city to uh to have fun. So uh one<00:11:42.079> of<00:11:42.160> the<00:11:42.240> best<00:11:42.560> one<00:11:42.720> of<00:11:42.800> the<00:11:42.880> best<00:11:43.279> and<00:11:43.440> is 00:11:43.670 --> 00:11:43.680 align:start position:0% one of the best one of the best and is 00:11:43.680 --> 00:11:45.590 align:start position:0% one of the best one of the best and is there<00:11:43.839> like<00:11:44.000> a<00:11:44.160> lot<00:11:44.240> of<00:11:44.399> customers<00:11:45.120> local 00:11:45.590 --> 00:11:45.600 align:start position:0% there like a lot of customers local 00:11:45.600 --> 00:11:48.230 align:start position:0% there like a lot of customers local Netherlands<00:11:46.240> customers<00:11:46.720> who<00:11:47.120> you<00:11:47.360> see 00:11:48.230 --> 00:11:48.240 align:start position:0% Netherlands customers who you see 00:11:48.240 --> 00:11:48.790 align:start position:0% Netherlands customers who you see bowlers? 00:11:48.790 --> 00:11:48.800 align:start position:0% bowlers? 00:11:48.800 --> 00:11:51.110 align:start position:0% bowlers? Uh<00:11:49.120> definitely<00:11:49.600> definitely<00:11:50.320> a<00:11:50.560> bit<00:11:50.640> less<00:11:50.880> than 00:11:51.110 --> 00:11:51.120 align:start position:0% Uh definitely definitely a bit less than 00:11:51.120 --> 00:11:55.190 align:start position:0% Uh definitely definitely a bit less than in<00:11:51.279> the<00:11:51.360> US.<00:11:51.839> They<00:11:52.800> our<00:11:53.040> market<00:11:54.160> adoption<00:11:54.800> is 00:11:55.190 --> 00:11:55.200 align:start position:0% in the US. They our market adoption is 00:11:55.200 --> 00:11:57.350 align:start position:0% in the US. They our market adoption is biggest<00:11:55.600> in<00:11:55.760> the<00:11:55.920> US.<00:11:56.240> I<00:11:56.480> think<00:11:56.640> the<00:11:56.800> US<00:11:57.040> is 00:11:57.350 --> 00:11:57.360 align:start position:0% biggest in the US. I think the US is 00:11:57.360 --> 00:11:58.389 align:start position:0% biggest in the US. I think the US is just 00:11:58.389 --> 00:11:58.399 align:start position:0% just 00:11:58.399 --> 00:12:00.310 align:start position:0% just Europe<00:11:58.720> is<00:11:58.880> always<00:11:59.120> a<00:11:59.279> bit<00:11:59.519> slower<00:12:00.000> in 00:12:00.310 --> 00:12:00.320 align:start position:0% Europe is always a bit slower in 00:12:00.320 --> 00:12:03.110 align:start position:0% Europe is always a bit slower in adoption.<00:12:01.120> they<00:12:01.440> look<00:12:01.600> at<00:12:01.920> okay<00:12:02.240> what's 00:12:03.110 --> 00:12:03.120 align:start position:0% adoption. they look at okay what's 00:12:03.120 --> 00:12:04.790 align:start position:0% adoption. they look at okay what's what's<00:12:03.360> big<00:12:03.600> in<00:12:03.760> the<00:12:03.839> US<00:12:04.079> and<00:12:04.240> then<00:12:04.399> 10<00:12:04.560> years 00:12:04.790 --> 00:12:04.800 align:start position:0% what's big in the US and then 10 years 00:12:04.800 --> 00:12:06.710 align:start position:0% what's big in the US and then 10 years later<00:12:05.120> it<00:12:05.519> sort<00:12:05.680> of 00:12:06.710 --> 00:12:06.720 align:start position:0% later it sort of 00:12:06.720 --> 00:12:07.670 align:start position:0% later it sort of moves<00:12:06.959> over 00:12:07.670 --> 00:12:07.680 align:start position:0% moves over 00:12:07.680 --> 00:12:11.350 align:start position:0% moves over but<00:12:07.920> we<00:12:08.160> have<00:12:08.240> a<00:12:08.399> lot<00:12:08.480> of<00:12:08.800> photo<00:12:09.200> users<00:12:09.920> uh 00:12:11.350 --> 00:12:11.360 align:start position:0% but we have a lot of photo users uh 00:12:11.360 --> 00:12:14.230 align:start position:0% but we have a lot of photo users uh uh<00:12:11.680> in<00:12:11.920> Europe<00:12:12.160> as<00:12:12.399> well<00:12:13.040> um<00:12:13.279> nowadays<00:12:13.920> luckily 00:12:14.230 --> 00:12:14.240 align:start position:0% uh in Europe as well um nowadays luckily 00:12:14.240 --> 00:12:16.550 align:start position:0% uh in Europe as well um nowadays luckily in<00:12:14.399> the<00:12:14.560> beginning<00:12:14.720> it<00:12:14.959> was<00:12:15.040> always<00:12:16.160> uh<00:12:16.320> we 00:12:16.550 --> 00:12:16.560 align:start position:0% in the beginning it was always uh we 00:12:16.560 --> 00:12:20.150 align:start position:0% in the beginning it was always uh we were<00:12:16.720> much<00:12:17.040> more<00:12:17.680> uh<00:12:18.880> well<00:12:19.120> known<00:12:19.440> in<00:12:19.760> US 00:12:20.150 --> 00:12:20.160 align:start position:0% were much more uh well known in US 00:12:20.160 --> 00:12:21.910 align:start position:0% were much more uh well known in US currently<00:12:20.560> it's<00:12:21.040> uh 00:12:21.910 --> 00:12:21.920 align:start position:0% currently it's uh 00:12:21.920 --> 00:12:23.910 align:start position:0% currently it's uh uh 00:12:23.910 --> 00:12:23.920 align:start position:0% uh 00:12:23.920 --> 00:12:26.230 align:start position:0% uh we're<00:12:24.240> also<00:12:24.800> big<00:12:25.040> in<00:12:25.200> Europe<00:12:25.680> but 00:12:26.230 --> 00:12:26.240 align:start position:0% we're also big in Europe but 00:12:26.240 --> 00:12:27.829 align:start position:0% we're also big in Europe but yeah yeah<00:12:26.639> it's<00:12:26.720> spread<00:12:26.959> in<00:12:27.040> the<00:12:27.200> world 00:12:27.829 --> 00:12:27.839 align:start position:0% yeah yeah it's spread in the world 00:12:27.839 --> 00:12:29.430 align:start position:0% yeah yeah it's spread in the world and<00:12:28.000> you're<00:12:28.240> one<00:12:28.399> of<00:12:28.480> the<00:12:28.639> few<00:12:28.800> remaining 00:12:29.430 --> 00:12:29.440 align:start position:0% and you're one of the few remaining 00:12:29.440 --> 00:12:31.509 align:start position:0% and you're one of the few remaining European<00:12:30.000> companies<00:12:30.399> doing 00:12:31.509 --> 00:12:31.519 align:start position:0% European companies doing 00:12:31.519 --> 00:12:35.590 align:start position:0% European companies doing Yeah.<00:12:31.920> Yeah.<00:12:32.240> Yeah.<00:12:33.120> Um<00:12:34.000> Yeah.<00:12:34.399> So,<00:12:34.959> um<00:12:35.279> I 00:12:35.590 --> 00:12:35.600 align:start position:0% Yeah. Yeah. Yeah. Um Yeah. So, um I 00:12:35.600 --> 00:12:38.150 align:start position:0% Yeah. Yeah. Yeah. Um Yeah. So, um I think<00:12:36.320> after<00:12:36.720> the 00:12:38.150 --> 00:12:38.160 align:start position:0% think after the 00:12:38.160 --> 00:12:40.710 align:start position:0% think after the the<00:12:38.399> DB<00:12:38.959> acquisition,<00:12:39.519> now<00:12:39.760> we're<00:12:40.160> uh 00:12:40.710 --> 00:12:40.720 align:start position:0% the DB acquisition, now we're uh 00:12:40.720 --> 00:12:42.470 align:start position:0% the DB acquisition, now we're uh yeah,<00:12:41.120> we're<00:12:41.360> the<00:12:41.600> European<00:12:42.000> tech<00:12:42.240> company. 00:12:42.470 --> 00:12:42.480 align:start position:0% yeah, we're the European tech company. 00:12:42.480 --> 00:12:44.310 align:start position:0% yeah, we're the European tech company. Yeah.<00:12:42.720> The<00:12:42.880> independent<00:12:43.440> Amsterdam 00:12:44.310 --> 00:12:44.320 align:start position:0% Yeah. The independent Amsterdam 00:12:44.320 --> 00:12:45.509 align:start position:0% Yeah. The independent Amsterdam different<00:12:44.639> company. 00:12:45.509 --> 00:12:45.519 align:start position:0% different company. 00:12:45.519 --> 00:12:47.110 align:start position:0% different company. All right.<00:12:45.839> Well,<00:12:46.079> thank<00:12:46.160> you<00:12:46.320> so<00:12:46.399> much. 00:12:47.110 --> 00:12:47.120 align:start position:0% All right. Well, thank you so much. 00:12:47.120 --> 00:12:49.030 align:start position:0% All right. Well, thank you so much. We're<00:12:47.360> looking<00:12:47.519> forward<00:12:47.839> to<00:12:48.399> hosting<00:12:48.800> you<00:12:48.959> at 00:12:49.030 --> 00:12:49.040 align:start position:0% We're looking forward to hosting you at 00:12:49.040 --> 00:12:51.670 align:start position:0% We're looking forward to hosting you at the<00:12:49.200> Rust<00:12:49.519> AI<00:12:49.920> events<00:12:50.399> in<00:12:50.720> Bay<00:12:50.880> Area.<00:12:51.440> Cool. 00:12:51.670 --> 00:12:51.680 align:start position:0% the Rust AI events in Bay Area. Cool. 00:12:51.680 --> 00:12:53.269 align:start position:0% the Rust AI events in Bay Area. Cool. And<00:12:51.839> I<00:12:52.000> think<00:12:52.160> like,<00:12:52.480> you<00:12:52.639> know,<00:12:52.800> we'll<00:12:53.040> have, 00:12:53.269 --> 00:12:53.279 align:start position:0% And I think like, you know, we'll have, 00:12:53.279 --> 00:12:55.030 align:start position:0% And I think like, you know, we'll have, you<00:12:53.440> know,<00:12:53.600> like<00:12:53.760> a<00:12:53.920> system<00:12:54.160> of<00:12:54.480> people<00:12:54.800> doing 00:12:55.030 --> 00:12:55.040 align:start position:0% you know, like a system of people doing 00:12:55.040 --> 00:12:57.670 align:start position:0% you know, like a system of people doing basically<00:12:55.279> what<00:12:55.360> they<00:12:55.519> call<00:12:55.680> AI<00:12:56.000> infra<00:12:56.560> 2.0<00:12:56.880> Z 00:12:57.670 --> 00:12:57.680 align:start position:0% basically what they call AI infra 2.0 Z 00:12:57.680 --> 00:13:00.470 align:start position:0% basically what they call AI infra 2.0 Z where<00:12:57.920> we<00:12:58.160> power<00:12:58.480> the<00:12:58.720> fast,<00:12:59.600> you<00:12:59.760> know,<00:12:59.920> AI<00:13:00.320> of 00:13:00.470 --> 00:13:00.480 align:start position:0% where we power the fast, you know, AI of 00:13:00.480 --> 00:13:02.550 align:start position:0% where we power the fast, you know, AI of tomorrow<00:13:00.880> with<00:13:01.200> all<00:13:01.360> this<00:13:01.680> wonderful<00:13:02.160> Rust 00:13:02.550 --> 00:13:02.560 align:start position:0% tomorrow with all this wonderful Rust 00:13:02.560 --> 00:13:03.509 align:start position:0% tomorrow with all this wonderful Rust engineering. 00:13:03.509 --> 00:13:03.519 align:start position:0% engineering. 00:13:03.519 --> 00:13:05.829 align:start position:0% engineering. Yeah.<00:13:03.839> Yeah.<00:13:04.320> It<00:13:04.480> would<00:13:04.639> be<00:13:04.880> great<00:13:05.040> to<00:13:05.440> uh<00:13:05.680> to 00:13:05.829 --> 00:13:05.839 align:start position:0% Yeah. Yeah. It would be great to uh to 00:13:05.839 --> 00:13:08.310 align:start position:0% Yeah. Yeah. It would be great to uh to be<00:13:06.000> there<00:13:06.240> and<00:13:07.120> and<00:13:07.360> be<00:13:07.440> in<00:13:07.600> the<00:13:07.680> Bay<00:13:07.839> Area.<00:13:08.160> I 00:13:08.310 --> 00:13:08.320 align:start position:0% be there and and be in the Bay Area. I 00:13:08.320 --> 00:13:11.430 align:start position:0% be there and and be in the Bay Area. I always<00:13:08.560> like<00:13:08.800> to<00:13:09.040> have<00:13:09.200> this<00:13:09.440> whole<00:13:10.639> um 00:13:11.430 --> 00:13:11.440 align:start position:0% always like to have this whole um 00:13:11.440 --> 00:13:12.870 align:start position:0% always like to have this whole um vibrant<00:13:11.920> culture. 00:13:12.870 --> 00:13:12.880 align:start position:0% vibrant culture. 00:13:12.880 --> 00:13:14.629 align:start position:0% vibrant culture. Looking<00:13:13.120> forward.<00:13:13.680> Cheers.<00:13:14.160> Thank<00:13:14.320> you. 00:13:14.629 --> 00:13:14.639 align:start position:0% Looking forward. Cheers. Thank you. 00:13:14.639 --> 00:13:18.000 align:start position:0% Looking forward. Cheers. Thank you. Bye,<00:13:14.959> guys.<00:13:15.680> All<00:13:15.760> right.