1 00:00:00,160 --> 00:00:03,840 Today it's 5%. It's two and a half times greater. 2 00:00:03,920 --> 00:00:07,760 And I think that we're reaching a tipping point. So 3 00:00:08,320 --> 00:00:11,920 to meet that tipping point, we also need to match the 4 00:00:11,920 --> 00:00:15,600 expectations of people who are coming from commercial software and 5 00:00:15,600 --> 00:00:18,400 quite frankly, up the game and up the support 6 00:00:18,640 --> 00:00:22,480 mechanisms and provide the capabilities the proprietary users 7 00:00:22,720 --> 00:00:26,320 are really looking for. And that is stability and reliability 8 00:00:26,320 --> 00:00:30,110 and validation. Hey, Frank here. I just want to give a little bit of 9 00:00:30,110 --> 00:00:33,950 context for today's episode. It's basically not really a 10 00:00:33,950 --> 00:00:37,590 data or AI talk per se, but it is something 11 00:00:37,590 --> 00:00:41,110 that I think that the community in general needs to start thinking 12 00:00:41,110 --> 00:00:44,030 about. The Windows that we know and love 13 00:00:44,590 --> 00:00:48,350 isn't really a thing anymore. And increasingly I'm seeing 14 00:00:48,350 --> 00:00:52,030 a lot of workloads and developers and AI 15 00:00:52,030 --> 00:00:55,570 engineers shift away from Windows into 16 00:00:56,290 --> 00:00:59,810 the Mac or Linux ecosystems. 17 00:00:59,970 --> 00:01:03,810 Now, what this means for you practically is. I get it, Linux can 18 00:01:03,810 --> 00:01:07,650 be a little intimidating at first, particularly on the desktop, but 19 00:01:07,810 --> 00:01:10,850 we have the opportunity to speak with someone who is 20 00:01:11,330 --> 00:01:15,170 really alleviating that. So listen with an open mind and keep 21 00:01:15,170 --> 00:01:18,550 in mind that the future may not have a start menu on it. 22 00:01:28,540 --> 00:01:32,340 Hello and welcome back to Data Driven, the podcast. We explore the emerging field of 23 00:01:32,340 --> 00:01:36,060 data, AI and data engineering. Now, 24 00:01:36,620 --> 00:01:39,820 Andy couldn't make it today, so with me, I have the most 25 00:01:40,620 --> 00:01:44,300 quantum curious person I know. But today we'll be talking about AI and data 26 00:01:44,540 --> 00:01:47,990 and hardware. So who do we have talking to us today? Candace? 27 00:01:48,550 --> 00:01:52,150 Today we're going to be speaking with Michael Makowski, and 28 00:01:52,550 --> 00:01:55,990 he is a really fascinating guest because he sits at the 29 00:01:55,990 --> 00:01:59,630 intersection of user experience, open 30 00:01:59,630 --> 00:02:03,110 source development, Linux and the evolution of web 31 00:02:03,110 --> 00:02:06,870 applications. He is an author of single web 32 00:02:06,870 --> 00:02:10,190 applications and a longtime advocate for SPA 33 00:02:10,190 --> 00:02:14,040 architecture. And I'm really, really excited to dig in 34 00:02:14,040 --> 00:02:17,760 deep about what he's doing now. Very cool. Well, welcome to the 35 00:02:17,760 --> 00:02:21,520 show, Mike. Hey, thanks. I appreciate it. No problem. 36 00:02:22,480 --> 00:02:26,200 Spa. So you like to spend time at the spa? Well, 37 00:02:26,200 --> 00:02:29,520 I did back in the day, although recently 38 00:02:29,760 --> 00:02:33,120 with the introduction of AI exploitation 39 00:02:33,600 --> 00:02:37,120 tools. They're very popular in Hollywood, from what I understand, 40 00:02:37,910 --> 00:02:41,750 although maybe they're applied a different way there. But as far 41 00:02:41,750 --> 00:02:45,510 as websites are concerned, the more active your website 42 00:02:45,590 --> 00:02:48,950 is today, the more likely it is to get 43 00:02:48,950 --> 00:02:52,670 exploited, especially if you're using something like WordPress. I 44 00:02:52,670 --> 00:02:56,230 spent some time in the security space, 45 00:02:56,390 --> 00:02:59,830 actually about four years in Silicon Valley, and 46 00:03:00,310 --> 00:03:04,150 the number one attack vector for a 47 00:03:04,150 --> 00:03:07,400 lot of companies was WordPress. 48 00:03:08,600 --> 00:03:12,200 So our website actually is all static these 49 00:03:12,200 --> 00:03:15,720 days. So after writing an spa book, and there are great 50 00:03:15,880 --> 00:03:19,560 things you can do with an spa, basically Having a web application as 51 00:03:19,560 --> 00:03:22,600 opposed to a website. But for 52 00:03:23,240 --> 00:03:26,680 what we're doing today, which is selling validated 53 00:03:26,920 --> 00:03:30,520 Linux systems with a fully fleshed out 54 00:03:30,520 --> 00:03:33,690 web infrastructure, we don't have a need 55 00:03:34,090 --> 00:03:37,610 for having a web application. So 56 00:03:37,690 --> 00:03:40,330 you don't have a need for it and you value 57 00:03:41,450 --> 00:03:45,050 privacy and security then. I'm a big fan of 58 00:03:45,050 --> 00:03:48,170 doing static web pages, which is what we're doing now. 59 00:03:48,490 --> 00:03:51,930 Interesting. So you, you make and ship 60 00:03:52,090 --> 00:03:55,810 Linux laptops. Is that high performance Linux laptops? Is that a 61 00:03:55,810 --> 00:03:59,540 correct statement? Yes, we actually do arrange. 62 00:03:59,860 --> 00:04:03,540 We're launching this week. Hopefully we'll get everything 63 00:04:04,100 --> 00:04:07,740 pulled together. Major initiative which we've 64 00:04:07,740 --> 00:04:11,300 actually had under the way. We're now going into our second month on that 65 00:04:11,700 --> 00:04:15,460 and then we're launching, at least depending on 66 00:04:15,460 --> 00:04:19,060 how you want to count it, six new or refresh 67 00:04:19,060 --> 00:04:21,860 models. So with the latest 68 00:04:22,100 --> 00:04:23,950 2.26.04 69 00:04:25,310 --> 00:04:28,910 Kubuntu operating system, which we 70 00:04:29,230 --> 00:04:32,910 provided stipends for the developers and then directly help 71 00:04:32,910 --> 00:04:36,590 develop and also we provide hardware and then 72 00:04:36,750 --> 00:04:40,590 we're a patron for kde, so we get to pay a lot of 73 00:04:40,590 --> 00:04:44,030 different ways to help make sure that we've got a really 74 00:04:44,350 --> 00:04:47,870 reliable system. And then the 75 00:04:49,280 --> 00:04:52,640 other way that we are moving the needle forward 76 00:04:52,960 --> 00:04:56,400 for validated Linux systems is by 77 00:04:56,720 --> 00:05:00,480 announcing a bulletproof KDE 78 00:05:01,440 --> 00:05:05,240 initiative. That's our working title. We don't know exactly if that's 79 00:05:05,240 --> 00:05:09,040 going to be what sticks for the actual press releases, but 80 00:05:09,040 --> 00:05:12,760 that's a $100,000 plus commitment 81 00:05:12,760 --> 00:05:16,460 to KDE for the next three years to ensure that we 82 00:05:16,460 --> 00:05:20,220 have a stable long term support release on 83 00:05:20,220 --> 00:05:23,660 KDE the desktop. And this is going to 84 00:05:23,660 --> 00:05:27,300 benefit lots of companies and organizations that 85 00:05:27,300 --> 00:05:30,980 use kde. A great example. You'll see that if 86 00:05:30,980 --> 00:05:34,780 you look around NASA that the desktop they offer now running is KDE. 87 00:05:35,660 --> 00:05:39,260 And of course we have Fortune 500 companies 88 00:05:39,340 --> 00:05:41,980 that use our systems and AI companies 89 00:05:43,030 --> 00:05:46,870 and all those folks are going to benefit. But basically anybody 90 00:05:46,870 --> 00:05:49,670 that uses KDE and wants to use the LTS 91 00:05:50,390 --> 00:05:53,750 release will get a big boost. And then of course 92 00:05:53,990 --> 00:05:57,710 we do have a little, what is it, enlightened self 93 00:05:57,710 --> 00:06:01,430 interest involved with this because you know, we're funding that. So hopefully it's going to 94 00:06:01,430 --> 00:06:04,470 drive interest to the systems we produce 95 00:06:05,350 --> 00:06:09,130 and so that we can build a virtuous cycle so that 96 00:06:09,130 --> 00:06:12,770 we can continue to build an ecosystem that 97 00:06:13,570 --> 00:06:17,370 meets or exceeds the best proprietary systems 98 00:06:17,370 --> 00:06:20,930 available, but without all the spyware and without 99 00:06:20,930 --> 00:06:24,610 all the surveillance and all the phoning home and 100 00:06:24,610 --> 00:06:28,210 the age verification APIs that are basically 101 00:06:28,210 --> 00:06:31,810 a thinly veiled attempt to have a 102 00:06:31,810 --> 00:06:35,380 national ID system in place. You know, a lot of people 103 00:06:35,460 --> 00:06:39,260 are really recoiling against all the Big Brother activities 104 00:06:39,260 --> 00:06:42,900 that are occurring currently. And we 105 00:06:43,300 --> 00:06:47,020 have recoiled against that for a long time. But 106 00:06:47,020 --> 00:06:50,500 it's getting so overbearing these days that we're seeing 107 00:06:50,980 --> 00:06:54,780 an extreme amount of interest. Linux usage just a few years 108 00:06:54,780 --> 00:06:57,540 ago was 2% on the desktop, today it's 5%, 109 00:06:58,340 --> 00:07:02,060 it's two and a half times greater. And I think that we're reaching 110 00:07:02,060 --> 00:07:05,780 a tipping point. So to meet 111 00:07:05,780 --> 00:07:09,540 that tipping point, we also need to match the expectations of people 112 00:07:09,540 --> 00:07:13,180 who are coming from commercial software and quite frankly up the 113 00:07:13,180 --> 00:07:16,900 game and up the support mechanisms and provide the 114 00:07:16,900 --> 00:07:20,500 capabilities the proprietary users are really looking for. 115 00:07:20,580 --> 00:07:23,700 And that is stability and reliability and validation. 116 00:07:24,180 --> 00:07:27,900 And so Candice has been involved with me on this for a 117 00:07:27,900 --> 00:07:31,650 seven year journey and she knows that we've been beating that drum 118 00:07:31,650 --> 00:07:35,410 for a long time. But I think that sometimes you just keep on doing 119 00:07:35,410 --> 00:07:39,090 what you're doing and then, you know, the whole world shifts 120 00:07:39,170 --> 00:07:42,970 and you're there to take advantage of it. So I get a 121 00:07:42,970 --> 00:07:46,610 feeling that we're around that zone right now. No, 100%. 122 00:07:46,610 --> 00:07:50,210 And I think that, you know, the privacy story as you look at, you know, 123 00:07:50,210 --> 00:07:53,850 and most of our listeners are Windows users, I would say 124 00:07:53,850 --> 00:07:57,410 with some Linux experience. So KDE is the desktop environment, 125 00:07:57,570 --> 00:08:01,340 is that. Yes, that runs on top of any distro 126 00:08:01,340 --> 00:08:04,260 Linux or just Ubuntu or just certain ones. 127 00:08:05,300 --> 00:08:08,980 It runs on virtually any build 128 00:08:09,060 --> 00:08:11,540 of Linux. Okay. But the. 129 00:08:12,980 --> 00:08:16,340 It's one of those things that's in a certain extent like 130 00:08:16,340 --> 00:08:19,700 Windows in that it doesn't like to 131 00:08:20,420 --> 00:08:23,940 share the OS with other desktops. 132 00:08:24,300 --> 00:08:27,900 Right. Actually, that's kind of the wrong term. It's more like the other way around. 133 00:08:27,980 --> 00:08:31,620 Certain desktops don't play well with other desktops. So like certain 134 00:08:31,620 --> 00:08:34,820 kernels don't play along with certain desktop 135 00:08:34,820 --> 00:08:38,420 experiences. No, kernel is very lower 136 00:08:38,420 --> 00:08:42,220 level. Yeah, well, not lower level. It's. But it 137 00:08:42,220 --> 00:08:43,100 is very 138 00:08:45,660 --> 00:08:49,420 generic in the respect that it's a component 139 00:08:49,420 --> 00:08:53,120 that everybody works with. What you run into trouble with 140 00:08:53,360 --> 00:08:56,720 is, you'll remember back in the day when they had 141 00:08:56,720 --> 00:09:00,160 ZR dos, you know, I'm going way back here, so 142 00:09:00,320 --> 00:09:04,120 that's a lot goes way back. Yeah, yeah. We're losing about three quarters of your 143 00:09:04,120 --> 00:09:07,680 audience right now. But bear with me, back in the day, 144 00:09:07,760 --> 00:09:11,600 Gary Kildall from Digital Research created 145 00:09:11,600 --> 00:09:14,960 ZR dos, which was dos but with stability 146 00:09:15,360 --> 00:09:19,060 and performance. And it was better than 147 00:09:19,220 --> 00:09:22,900 Ms. DOS by almost any 148 00:09:22,980 --> 00:09:26,340 measurable factor. And it gained a lot of 149 00:09:26,580 --> 00:09:30,140 popularity. The problem was that Microsoft 150 00:09:30,140 --> 00:09:33,660 didn't like it. So what Billy and his friends did 151 00:09:33,660 --> 00:09:36,740 was they decided to make it incompatible 152 00:09:37,380 --> 00:09:40,660 for their Windows program. Windows 95 153 00:09:41,220 --> 00:09:44,660 ran perfect on it until they decided to make it not run perfect. 154 00:09:45,800 --> 00:09:49,520 And so it's. Now, not everybody 155 00:09:49,520 --> 00:09:53,240 is so nefarious as that. But if 156 00:09:53,240 --> 00:09:56,920 you don't build your desktop system to work with 157 00:09:56,920 --> 00:10:00,759 the underlying layers, you're going to have problems or if 158 00:10:00,759 --> 00:10:04,520 you create like services that conflict. And 159 00:10:05,000 --> 00:10:08,440 that's what indeed can happen with 160 00:10:09,400 --> 00:10:12,120 certain other desktop systems in Linux. 161 00:10:13,290 --> 00:10:16,570 So the most notorious one, and I'm not saying that this is 162 00:10:16,890 --> 00:10:20,650 an example of any sort of 163 00:10:20,650 --> 00:10:24,410 malfeasance, it's just that the GNOME 164 00:10:24,410 --> 00:10:27,610 desktop environment has a lot of services 165 00:10:28,650 --> 00:10:32,490 that are required by GNOME that 166 00:10:32,490 --> 00:10:35,290 don't play well with other desktop systems. 167 00:10:36,010 --> 00:10:39,690 And I'm certain it goes with other ways as 168 00:10:39,690 --> 00:10:43,400 well. But. So that's the reason why you see distributions that, that only 169 00:10:43,720 --> 00:10:47,520 ship one or two desktop environments. Instead of 170 00:10:47,520 --> 00:10:50,920 giving you 20 to choose from if you want to like go out and play 171 00:10:50,920 --> 00:10:54,680 with a bunch of them, it's because they conflict. And 172 00:10:54,680 --> 00:10:58,480 again not because people have malfeasance in their heart, but 173 00:10:58,480 --> 00:11:02,280 because of the fact that nobody actually tests to make 174 00:11:02,280 --> 00:11:06,000 sure that the interplay actually is going to 175 00:11:06,000 --> 00:11:09,750 work out the way you want it to. I think we've probably done 176 00:11:10,390 --> 00:11:14,030 a lot more than the average bear in that respect where we've actually identified 177 00:11:14,030 --> 00:11:17,790 the conflicting services, but nobody's paying us, 178 00:11:17,790 --> 00:11:21,230 quite frankly, to make those 179 00:11:21,230 --> 00:11:24,749 conflicts go away. Or nobody's paying Gnome or 180 00:11:24,749 --> 00:11:28,470 KDE to make sure those conflicts go away. There's really not 181 00:11:28,470 --> 00:11:32,270 much of an incentive to change that because people who 182 00:11:32,270 --> 00:11:35,870 use a certain desktop tend to stick with it. It's kind of like they 183 00:11:35,870 --> 00:11:39,470 choose a type of cigarette and they stick with it too. Maybe not, maybe not. 184 00:11:39,470 --> 00:11:43,110 The best example, they picked a favorite type of soda. How about 185 00:11:43,110 --> 00:11:46,870 that? Yeah, there we go. Exactly. Pepsi or Coke? There we go. Pepsi or 186 00:11:46,870 --> 00:11:50,430 Coke or Dr. Pepper. Yeah, so 187 00:11:51,470 --> 00:11:54,350 what? I think you're absolutely right. I think there's a. 188 00:11:55,390 --> 00:11:58,870 Something is rotten in the state of Windows land. We have a lot of folks 189 00:11:58,870 --> 00:12:02,270 here who are Microsoft centric, who do listen. And 190 00:12:03,060 --> 00:12:06,660 if they've been following me, they know that I've kind of gone. I've gone 191 00:12:06,660 --> 00:12:10,300 rogue, right? Because Windows 11 192 00:12:10,300 --> 00:12:13,460 has really pushed me over the edge in terms of the decisions that were made, 193 00:12:13,860 --> 00:12:17,660 the usability and when you start peeling back the 194 00:12:17,660 --> 00:12:21,460 curtain behind the privacy story on Windows 11, certainly the home version 195 00:12:21,860 --> 00:12:25,660 Pro is not as bad. Enterprise is a little bit less bad. It's 196 00:12:25,660 --> 00:12:29,340 painting a picture. I really don't like. Right. My, my beef was, you 197 00:12:29,340 --> 00:12:32,340 know, if you look at my office, I got a lot of equipment and 198 00:12:33,140 --> 00:12:36,580 you know, because of an arbitrary decision made in Redmond, 199 00:12:37,060 --> 00:12:40,260 most of this will not run Windows 11. And 200 00:12:41,220 --> 00:12:44,500 that really made me mad. I was going to use other words, but 201 00:12:46,020 --> 00:12:49,860 I think Windows 11. And again, I used to be a Microsoft 202 00:12:49,860 --> 00:12:52,660 MVP. I used to be a Microsoft employee twice 203 00:12:53,460 --> 00:12:56,980 and I doubt that I'll be reinvited for the MVP program 204 00:12:57,870 --> 00:13:01,590 anytime soon. But I just take issues with 205 00:13:01,590 --> 00:13:05,390 some of the decisions that were made with Windows. Now I haven't seen what 206 00:13:05,390 --> 00:13:08,750 they announced at build this week but or last week, 207 00:13:09,070 --> 00:13:12,910 but I'm just very much annoyed and 208 00:13:12,910 --> 00:13:16,030 I think that Windows choices, 209 00:13:17,310 --> 00:13:21,110 be they what they are, I think has really driven Linux 210 00:13:21,110 --> 00:13:24,710 adoption. You mentioned Linux on the desktop has 211 00:13:24,710 --> 00:13:28,150 doubled. I don't think it's a coincidence that Windows 11 has drove 212 00:13:28,310 --> 00:13:31,670 away a lot of hardcore Windows users like me. Right. Like, I mean I, 213 00:13:32,470 --> 00:13:35,510 for me to, you know, obviously I, you know, my day job is at Red 214 00:13:35,510 --> 00:13:38,270 Hat now. You can see the fedora there. Right. But you know, for the longest 215 00:13:38,270 --> 00:13:41,510 time I was the only person on my team that had a Windows laptop. 216 00:13:41,910 --> 00:13:45,470 Right. But with the rise of AI development tools 217 00:13:45,470 --> 00:13:49,070 being fairly agnostic in terms of what 218 00:13:49,070 --> 00:13:52,690 platform they're on, almost to the point now where they're, they recommend 219 00:13:52,690 --> 00:13:56,250 Mac or Linux and if you have a Windows device they 220 00:13:56,330 --> 00:14:00,130 actually say you probably should run this inside WSL or Windows subsystem for 221 00:14:00,130 --> 00:14:03,810 Linux. I think that you're right. I think we are on the cusp 222 00:14:03,810 --> 00:14:07,370 of an inflection point of Windows. 223 00:14:07,530 --> 00:14:10,970 Certainly in the AI field, if you're an AI developer, it's almost 224 00:14:11,050 --> 00:14:14,690 exclusively Macintosh, I would say. 225 00:14:14,690 --> 00:14:18,070 Well, we have a lot of companies 226 00:14:18,230 --> 00:14:21,910 that develop for AI that use our systems. 227 00:14:22,310 --> 00:14:25,910 Right. There's a saying in Silicon Valley 228 00:14:25,910 --> 00:14:28,390 which is nobody deploys to Mac. 229 00:14:29,910 --> 00:14:32,790 So when you really think about it, the 230 00:14:33,430 --> 00:14:37,110 tools have to first and foremost be 231 00:14:37,110 --> 00:14:40,790 Linux compatible and Linux proven and 232 00:14:40,790 --> 00:14:44,470 Linux battle tested. Right. Mac is popular because 233 00:14:45,390 --> 00:14:48,950 got a trophy status and they also are 234 00:14:48,950 --> 00:14:52,710 popular now because of the unified memory mechanism. They 235 00:14:52,710 --> 00:14:56,470 have relatively weak GPUs compared to the 236 00:14:56,470 --> 00:15:00,310 top end Nvidia GPUs obviously. But because 237 00:15:00,310 --> 00:15:03,950 they have unified memory that can overcome that 238 00:15:03,950 --> 00:15:06,830 disadvantage and for certain models can actually run faster. 239 00:15:07,550 --> 00:15:11,230 Now with the advent of AMD processors as 240 00:15:11,230 --> 00:15:14,530 well as now the latest Panther Lake intel 241 00:15:14,530 --> 00:15:18,130 processors, Those now have BPIGPUs in them as 242 00:15:18,130 --> 00:15:21,810 well. Again, they don't touch the Nvidia in 243 00:15:21,810 --> 00:15:25,290 terms of the level of performance 244 00:15:25,450 --> 00:15:29,130 available. But again for certain models, say 245 00:15:29,130 --> 00:15:32,850 running llama from my understanding, and I'm not an expert here, so if 246 00:15:32,850 --> 00:15:35,610 I sound foolish, it's because I am. 247 00:15:36,410 --> 00:15:40,260 But the. For certain 248 00:15:40,260 --> 00:15:44,100 models, Llama, for example, will work better because you can 249 00:15:44,100 --> 00:15:47,900 have a memory window of 128 250 00:15:47,900 --> 00:15:51,580 gigabytes, for example, instead of being limited to 16 or 24 251 00:15:51,580 --> 00:15:55,180 gigabytes on an Nvidia system. On the other hand, you know when you got a 252 00:15:55,180 --> 00:15:59,020 5090 and you want to start swapping stuff out, if your model is 253 00:15:59,020 --> 00:16:02,580 the right structure, that 59 is going to decimate anything 254 00:16:02,580 --> 00:16:06,180 else. But I think the reason why you're seeing people developing 255 00:16:06,260 --> 00:16:09,990 on Mac for models that will eventually be 256 00:16:09,990 --> 00:16:13,550 deployed, typically on Linux Nvidia 257 00:16:13,550 --> 00:16:17,110 systems, is because of the fact that they, 258 00:16:17,750 --> 00:16:19,190 they can have a 259 00:16:21,110 --> 00:16:24,070 proprietary quality, 260 00:16:24,470 --> 00:16:27,990 user experience and reliability and 261 00:16:28,390 --> 00:16:31,950 then also have reasonable performance when working with their 262 00:16:31,950 --> 00:16:35,590 model. Sometimes better performance working with their model, 263 00:16:35,830 --> 00:16:39,670 although again, I don't think that tends to be deployed. But I'm 264 00:16:39,670 --> 00:16:43,470 not an expert in the deployment arena. I just know what our customers 265 00:16:43,470 --> 00:16:47,190 buy and what they tell me. Well, no, I mean, 266 00:16:47,430 --> 00:16:50,990 so as someone who is in AI space, I will say that 267 00:16:50,990 --> 00:16:54,630 unified memory, I think is what makes the Apple Silicon really appealing. 268 00:16:55,030 --> 00:16:58,830 And I also have a DGX Spark, which that's also. It's kind of claim to 269 00:16:58,830 --> 00:17:02,520 fame is that it's unified memory, right? Oh yeah. And you're right, like depending on 270 00:17:02,520 --> 00:17:06,040 the actual chip you can get more done, 271 00:17:06,760 --> 00:17:10,560 but very often the VRAM that's 272 00:17:10,560 --> 00:17:13,480 available to you or the RAM that's available to the video card 273 00:17:14,600 --> 00:17:18,040 is also a blocker too. Right. So the fact that you can have a unified 274 00:17:18,920 --> 00:17:22,520 memory space I think is a huge deal. And you're even seeing Microsoft follow 275 00:17:22,520 --> 00:17:25,760 suit with this with their new I think RTX Spark. I think that's what it's 276 00:17:25,760 --> 00:17:29,569 called. Yeah, I think that's kind of the future. 277 00:17:30,289 --> 00:17:34,089 But yeah. So tell me about some of the AI specific hardware. 278 00:17:34,089 --> 00:17:37,689 You have me curious. Well, I can show you what we have that 279 00:17:37,689 --> 00:17:41,409 people. Yeah. And then we'll let Candace ask, ask questions because I'm hogging away. We 280 00:17:41,409 --> 00:17:45,009 have lots of companies that buy hardware 281 00:17:45,409 --> 00:17:48,689 that. And I'll show you the heavyweight stuff. 282 00:17:48,929 --> 00:17:51,969 Let's see. Yeah, we're actually, like I said, 283 00:17:52,769 --> 00:17:55,729 going to be launching new versions of these systems. But 284 00:17:56,420 --> 00:18:00,260 I'll, I'll see if I can share a. 285 00:18:00,820 --> 00:18:04,660 Let's go to our website, be able to share your screen and I'll, 286 00:18:04,660 --> 00:18:07,460 I'll talk through it for those that are listening. 287 00:18:08,100 --> 00:18:11,819 Yeah, you just go, ooh, wow, you can do 288 00:18:11,819 --> 00:18:15,220 that. Take my money. Yeah, that's my recommendation. 289 00:18:15,380 --> 00:18:18,980 Yeah, take my money. Yeah, you can keep doing that. 290 00:18:19,460 --> 00:18:22,990 Let's see. Share and let's try 291 00:18:23,150 --> 00:18:26,030 a home tab. There we go. And there we go. 292 00:18:27,310 --> 00:18:30,590 If those who are listening and they want to see this, we are on YouTube. 293 00:18:30,590 --> 00:18:34,270 Just check the show notes. I always link the YouTube version. Sorry, cut you 294 00:18:34,270 --> 00:18:37,950 off. That's it. No, no, you didn't cut me off. Interesting thing about doing 295 00:18:37,950 --> 00:18:41,710 these web pages, by the way, is that I 296 00:18:41,710 --> 00:18:45,310 think it's a pretty fascinating thing here. But if you look at these 297 00:18:45,870 --> 00:18:49,680 graphics here, right? And then I'm going to change this to a 298 00:18:49,680 --> 00:18:53,160 dark theme right now. So the OS is changing to the dark theme 299 00:18:53,800 --> 00:18:57,160 and. Oh, that's on a local host. Let's do it. Let's go to the actual. 300 00:18:58,200 --> 00:19:01,320 I was showing the development model. That's the reason why that broke. 301 00:19:02,280 --> 00:19:05,800 So here's the actual production site. But what's pretty 302 00:19:05,800 --> 00:19:09,280 fascinating about this that you never think about is that these are 303 00:19:09,280 --> 00:19:12,920 mostly black, you know, very dark machines, right. But 304 00:19:12,920 --> 00:19:16,760 if you now switch over to a light view, you 305 00:19:16,760 --> 00:19:20,480 may not notice it. But these, the chassis here just bumped up 306 00:19:20,480 --> 00:19:23,760 about two levels of lightness in the gray area. 307 00:19:24,560 --> 00:19:28,240 And it's a kind of funny thing because the, you 308 00:19:28,240 --> 00:19:31,920 put something in a white room and it makes the whole thing lighter. 309 00:19:32,000 --> 00:19:35,800 Those things you don't just run into unless you're, I 310 00:19:35,800 --> 00:19:39,600 guess, selling black computers on the Internet. So let's take a 311 00:19:39,600 --> 00:19:42,480 look at a couple of the products that we have and the ones that are 312 00:19:42,560 --> 00:19:46,390 popular for AI. So this is the, this is 313 00:19:46,390 --> 00:19:50,110 the beast. And it is a 5090 314 00:19:50,110 --> 00:19:53,550 with 24 gigabytes of video RAM. Oh, wow. 315 00:19:54,110 --> 00:19:57,790 Yeah. And then it's got up to 192 gigabytes of 316 00:19:57,870 --> 00:20:01,550 RAM. So I guess 2000, $2500 of RAM 317 00:20:01,550 --> 00:20:05,230 at wholesale these days that you put into that. It's got an 18 inch 318 00:20:05,230 --> 00:20:08,790 screen, 2560 by 1600, which is a beautiful 319 00:20:08,790 --> 00:20:12,180 screen. It's DCIP3, 100% and 320 00:20:12,820 --> 00:20:16,500 it's just a beast. It's got a subwoofer in it for, you know. Oh, wow. 321 00:20:16,660 --> 00:20:19,620 Crying out loud. There we go. I almost slipped up there. 322 00:20:20,180 --> 00:20:23,620 So. And the, the subwoofer does sound good. So 323 00:20:23,780 --> 00:20:27,620 you can get your jam on when you're loading up 324 00:20:27,620 --> 00:20:31,300 your, oh, I don't know what 30 billion 325 00:20:31,540 --> 00:20:35,140 parameter model. See, I might be sounding ignorant here now too, 326 00:20:35,140 --> 00:20:38,660 but yeah, while you're loading up your model and this one's real popular 327 00:20:38,740 --> 00:20:41,820 with ML. What's the, 328 00:20:42,300 --> 00:20:44,860 what's the 5090 vram? 329 00:20:45,900 --> 00:20:49,620 24 gigabytes. Oh yeah, you can do, you can do some serious damage with 330 00:20:49,620 --> 00:20:51,500 that. Yeah. So. 331 00:20:53,100 --> 00:20:56,660 And it's got the 24 core. The new version coming 332 00:20:56,660 --> 00:21:00,340 out is the. And this was actually recommended 333 00:21:00,340 --> 00:21:03,980 by Wired magazine as the best Linux 334 00:21:03,980 --> 00:21:07,670 laptop for performance. And the next generation is 335 00:21:07,670 --> 00:21:11,070 the 2090 HX which gets it about a 6 to 336 00:21:11,070 --> 00:21:14,870 15% bump in single and multi core 337 00:21:14,950 --> 00:21:18,710 performance. The GPU remains the same, 338 00:21:19,670 --> 00:21:23,470 but that gives incredible performance as well. So pardon 339 00:21:23,470 --> 00:21:27,230 my ignorance, but one of the, one of the screenshots that kind of cycled 340 00:21:27,230 --> 00:21:30,070 through was a game. Yes, obviously, 341 00:21:31,440 --> 00:21:35,160 obviously anyone buying this would buy it for serious business purposes. But what 342 00:21:35,160 --> 00:21:38,760 is the state of gaming on Linux these days? I've 343 00:21:38,760 --> 00:21:42,560 heard things kind of mixed and is Kubuntu also what is 344 00:21:42,560 --> 00:21:46,160 based on the Stream Deck or Steam Deck is 345 00:21:46,160 --> 00:21:50,000 not what the Steam deck is based on. Steam Deck is 346 00:21:50,000 --> 00:21:53,600 a custom version of Arch 347 00:21:53,600 --> 00:21:57,390 Linux that uses a non 348 00:21:57,390 --> 00:22:01,030 mutable version. It's designed to be 349 00:22:01,510 --> 00:22:04,470 an appliance, not a general purpose computer. 350 00:22:05,190 --> 00:22:08,550 And there are some alluring aspects of that. 351 00:22:09,910 --> 00:22:13,630 Obviously if it's designed to be an appliance, that means that the end user 352 00:22:13,630 --> 00:22:17,350 is unable to easily break it. The 353 00:22:17,350 --> 00:22:20,950 downside to that is that the end user is 354 00:22:21,030 --> 00:22:24,390 unable to easily add system level services 355 00:22:24,710 --> 00:22:28,380 to the system. So. So if you want to run a database for example, 356 00:22:28,860 --> 00:22:32,660 and have a multi user system, well, you're probably kind of out of luck. But 357 00:22:32,660 --> 00:22:35,740 then again you're running a Steam Deck. You're not. It's something that you hold in 358 00:22:35,740 --> 00:22:39,220 your hands. Well, it's like an Xbox, right? Like a PlayStation. 359 00:22:39,220 --> 00:22:42,780 Yeah. They by the way run KDE Linux and 360 00:22:43,420 --> 00:22:46,900 I'm sorry, KDE Linux, they're running the KDE desktop on that as well. 361 00:22:46,900 --> 00:22:50,300 Gotcha. Okay. That's where I saw it because in case people are wondering what's Frank 362 00:22:50,300 --> 00:22:54,070 talking about? And again I'm not a Linux guru. I, one of my 363 00:22:54,070 --> 00:22:57,870 co workers said I speak Linux with a Windows accent. The. When you 364 00:22:57,870 --> 00:23:01,630 go to kde.org, one of the devices on there is. You're, you're on that 365 00:23:01,630 --> 00:23:04,590 page and. But next to your logo, 366 00:23:05,230 --> 00:23:08,710 a couple of items down is, is the Steam deck. So I 367 00:23:08,710 --> 00:23:12,510 noticed that like. And I noticed that Linux gaming has really taken 368 00:23:12,510 --> 00:23:15,950 off. Right. It used to be like good luck with that. 369 00:23:16,670 --> 00:23:20,310 I think it used to be. Now it's. Now I would say again this is 370 00:23:20,310 --> 00:23:23,220 just based on conjecture and I may sound like an idiot now, but I would 371 00:23:23,220 --> 00:23:26,580 say if you want to play a triple A game, it's probably a 372 00:23:26,580 --> 00:23:30,220 5050 shot that it will run on Linux. I 373 00:23:30,220 --> 00:23:33,900 think it's better than that even really. At least if it's a. If 374 00:23:33,900 --> 00:23:36,660 it's a triple. If it's a triple a game 375 00:23:37,700 --> 00:23:41,340 like if you want to run something like Grand 376 00:23:41,340 --> 00:23:43,860 Theft Auto, one of my favorite Grand Theft Auto 5. 377 00:23:44,900 --> 00:23:48,180 So almost certainly you can run that. 378 00:23:48,660 --> 00:23:51,860 Okay. The biggest challenge right now with 379 00:23:53,300 --> 00:23:56,740 gaming on Linux is not a technical issue 380 00:23:57,300 --> 00:24:01,140 because because 381 00:24:01,140 --> 00:24:04,100 of Steam's investment 382 00:24:04,900 --> 00:24:08,500 in that aspect, they've created a 383 00:24:08,500 --> 00:24:11,620 runtime environment that is not a 384 00:24:11,620 --> 00:24:15,210 translator, but is an 385 00:24:15,210 --> 00:24:18,730 API layer that Windows programs can run 386 00:24:19,370 --> 00:24:23,090 and say, I want to make this video call. And it 387 00:24:23,090 --> 00:24:26,490 works the same on the Linux system as it does on 388 00:24:26,490 --> 00:24:30,090 Windows. So it's not running through a 389 00:24:30,809 --> 00:24:34,250 like Rosetta Stone translation layer. It's 390 00:24:34,730 --> 00:24:37,690 running in a virtual environment that then makes 391 00:24:38,810 --> 00:24:41,690 calls out to local 392 00:24:43,610 --> 00:24:47,210 resources and they just work. So 393 00:24:47,690 --> 00:24:51,530 if you can imagine you in Windows, and 394 00:24:51,530 --> 00:24:55,290 this is a very simple example of this, and if any 395 00:24:55,290 --> 00:24:59,050 of your readers want to pick apart my explanation, have at it. But 396 00:24:59,770 --> 00:25:02,730 I think in a grand sense this is correct. 397 00:25:04,010 --> 00:25:07,780 When you're on Windows and you want 398 00:25:07,780 --> 00:25:11,540 to list the files in a directory, you type in dir. Correct. 399 00:25:11,540 --> 00:25:15,220 And when you're on Linux and you want to type or list files in a 400 00:25:15,220 --> 00:25:18,740 directory, you use ls. And the layer 401 00:25:19,540 --> 00:25:23,380 which is called WINE that is used by 402 00:25:23,380 --> 00:25:26,180 Steam, it basically aliases 403 00:25:27,620 --> 00:25:31,260 LS for dir. And so. So that's what WINE is. 404 00:25:31,260 --> 00:25:34,990 Okay. In fact, WINE is something along like 405 00:25:35,230 --> 00:25:37,870 Wine is not an emulator. It's one of those recursive 406 00:25:38,750 --> 00:25:42,190 acronyms, I believe, that plague us to this day. 407 00:25:42,590 --> 00:25:45,470 Find is not elm. Yeah, yeah, stuff like that. 408 00:25:47,390 --> 00:25:50,990 The whole point is that it's a layer that instead of 409 00:25:51,230 --> 00:25:54,830 creating a whole new emulation environment and having to recompile 410 00:25:54,830 --> 00:25:58,510 stuff, it just takes the executable and allows it to run. 411 00:25:58,590 --> 00:26:02,440 And then when it asks for a DirectX call, there 412 00:26:02,440 --> 00:26:06,240 is a. Actually a repointer that occurs 413 00:26:06,320 --> 00:26:10,080 that allows that to work. I think DirectX 414 00:26:10,080 --> 00:26:13,880 has fallen out of favor in for a lot of 415 00:26:13,880 --> 00:26:17,400 games they just go right to Vulcan. And Vulcan is native to 416 00:26:17,400 --> 00:26:21,240 Linux, so there doesn't even have to be a translation. There are 417 00:26:21,240 --> 00:26:24,760 a number of AAA games that actually run faster on Linux than they do on 418 00:26:24,760 --> 00:26:28,520 Windows. Especially now that you have all those background services running 419 00:26:28,520 --> 00:26:32,220 on Windows 11 to take snapshots and send them to Lord knows 420 00:26:32,220 --> 00:26:35,940 where or to drive, you know, you have to have that background service so that 421 00:26:35,940 --> 00:26:39,380 you can get advertisements in your system settings 422 00:26:39,540 --> 00:26:43,180 configuration or get advertisements in your Start menu 423 00:26:43,180 --> 00:26:46,900 and you know those are important. So you can't turn Those off. No, 424 00:26:47,780 --> 00:26:51,620 yeah, yeah, people. And that's actually driving 425 00:26:52,180 --> 00:26:56,020 Linux to be more power efficient. We're able to get longer 426 00:26:56,020 --> 00:26:59,650 battery lives on Linux, then you are able to get on 427 00:26:59,650 --> 00:27:03,130 Windows, even though Windows has such 428 00:27:03,130 --> 00:27:06,850 fantastic cross device driver support. 429 00:27:08,930 --> 00:27:12,650 You can't bring the CPU necessarily 430 00:27:12,650 --> 00:27:16,050 down to the sleep level that you want it to if it's 431 00:27:16,050 --> 00:27:19,810 constantly calling all these background services. So 432 00:27:20,370 --> 00:27:24,130 through some tweaks we're able to be competitive or even better than 433 00:27:24,130 --> 00:27:27,760 Windows as far as battery usage and battery life on 434 00:27:27,920 --> 00:27:31,360 a number of our systems. So you've already 435 00:27:31,360 --> 00:27:34,640 listed a couple of the truly competitive advantages 436 00:27:36,240 --> 00:27:39,760 for someone who's considering gaming the gaming 437 00:27:39,760 --> 00:27:43,480 platform they want to use. That's exciting. It's 438 00:27:43,480 --> 00:27:47,320 actually very exciting. What else do you think would surprise people the most 439 00:27:47,320 --> 00:27:50,840 about the current state of game compatibility, performance and 440 00:27:50,840 --> 00:27:54,130 overall user experience when considering 441 00:27:54,130 --> 00:27:57,810 Linux as their primary gaming platform? Well, I do want 442 00:27:57,810 --> 00:28:01,210 to answer one thing that is a negative 443 00:28:01,610 --> 00:28:05,370 for Linux and it's not because of Linux, it's because of the game companies 444 00:28:05,610 --> 00:28:09,210 and the Sweeneys of the world. And that is 445 00:28:10,090 --> 00:28:12,890 what's a Sweeney? Sweeney runs 446 00:28:13,610 --> 00:28:17,210 the company, I believe, that creates Fortnite. 447 00:28:17,530 --> 00:28:21,320 Oh, okay, okay. So you've got on one hand 448 00:28:21,640 --> 00:28:24,920 the Steam team that 449 00:28:25,240 --> 00:28:28,920 wants to get out from under the yoke of Microsoft and they 450 00:28:29,080 --> 00:28:31,560 went and did something amazingly 451 00:28:32,440 --> 00:28:36,080 proactive with releasing their Steam deck running Linux, 452 00:28:36,080 --> 00:28:39,840 not Windows, you have 453 00:28:39,840 --> 00:28:43,440 that side of it and then the other side you have game companies that want 454 00:28:43,440 --> 00:28:46,520 to make sure that their intellectual property 455 00:28:47,550 --> 00:28:51,390 locked down and the weather locking that down is by using 456 00:28:51,950 --> 00:28:55,150 kernel level anti cheat mechanisms. 457 00:28:55,870 --> 00:28:59,070 And from my understanding what that means is that 458 00:28:59,310 --> 00:29:02,030 they're actually running in kernel space 459 00:29:03,070 --> 00:29:06,670 code that is meant to prevent people from 460 00:29:06,670 --> 00:29:09,870 cheating on massively multiplayer 461 00:29:10,910 --> 00:29:13,870 games. So mm pgs, 462 00:29:14,590 --> 00:29:18,070 you can tell I'm a real gamer, but that is a downside that 463 00:29:18,070 --> 00:29:21,430 MMPGs are not always as well 464 00:29:21,430 --> 00:29:25,150 supported or not supported officially by the game studios. 465 00:29:26,110 --> 00:29:29,790 And the on the flip side, 466 00:29:30,670 --> 00:29:34,310 the fact that you're running code at the kernel level on 467 00:29:34,310 --> 00:29:37,670 your Windows system is going to be an 468 00:29:37,670 --> 00:29:41,380 incredible vector for somebody probably real 469 00:29:41,380 --> 00:29:44,900 soon to own a lot 470 00:29:44,980 --> 00:29:48,340 of Windows systems. Right? Because 471 00:29:48,820 --> 00:29:52,540 people who just want a game are going to download whatever, they're not 472 00:29:52,540 --> 00:29:56,380 going to go and review the source code 473 00:29:56,380 --> 00:29:59,620 for the kernel code that's running in Windows. And 474 00:29:59,940 --> 00:30:03,700 Lord knows you probably couldn't do that if you wanted to because it's certainly 475 00:30:03,700 --> 00:30:07,460 protected under 3 NDAs and a couple of 476 00:30:07,460 --> 00:30:10,840 licenses that have been created for that 477 00:30:10,840 --> 00:30:13,960 purpose. And so you're just 478 00:30:14,200 --> 00:30:17,800 basically adding mystery code on top of a system 479 00:30:17,960 --> 00:30:21,600 that is built for surveillance. And so now 480 00:30:21,600 --> 00:30:25,240 what's going to happen when you get into that and then what's going to happen 481 00:30:25,320 --> 00:30:29,040 when commercial OSes are going to be 482 00:30:29,040 --> 00:30:32,440 required to effectively tap into a national 483 00:30:32,680 --> 00:30:36,460 ID database for the save the Children 484 00:30:37,020 --> 00:30:40,380 effort for age verification? That's their vector. 485 00:30:40,780 --> 00:30:44,420 Now you're going to have somebody running so they can play their 486 00:30:44,420 --> 00:30:48,100 favorite mmpg. They're going to have running kernel level 487 00:30:48,100 --> 00:30:51,740 code that somebody with Claude code is going 488 00:30:51,740 --> 00:30:55,500 to be able to dissect and find a backdoor for. 489 00:30:56,140 --> 00:30:59,940 Once they get into the kernel level they own the system. Now 490 00:30:59,940 --> 00:31:03,620 you have all these wonderful tools and APIs available at 491 00:31:03,620 --> 00:31:07,240 the the kernel level and the user space level that allow 492 00:31:07,240 --> 00:31:10,360 you to go in and basically docs anybody 493 00:31:11,080 --> 00:31:14,920 And I don't want to be part of that. So I guess the 494 00:31:14,920 --> 00:31:18,520 short or the long answer because I've made this long 495 00:31:18,520 --> 00:31:22,040 is that you can't game everything because 496 00:31:22,200 --> 00:31:26,040 of these kernel level anti cheat as well as other anti 497 00:31:26,040 --> 00:31:29,880 cheat mechanisms that you can't get anything but Windows. 498 00:31:30,540 --> 00:31:34,180 But you have to ask yourself do you really want to be 499 00:31:34,180 --> 00:31:37,260 putting those things on your system because of the security 500 00:31:37,420 --> 00:31:40,620 implementation. Sorry, 501 00:31:41,740 --> 00:31:45,540 implications, Implications. There we go. My 502 00:31:45,540 --> 00:31:48,940 mind was trying to throw in an extra syllable there but the security 503 00:31:49,020 --> 00:31:52,740 implications that you're exposing 504 00:31:52,740 --> 00:31:56,300 yourself to so sounds dangerous. 505 00:31:57,250 --> 00:31:59,890 Yeah, you're right. 506 00:32:02,210 --> 00:32:05,970 I think the whole national ID thing is a 507 00:32:05,970 --> 00:32:09,250 whole other can of fish can of worms to open. 508 00:32:10,130 --> 00:32:13,970 But you're right just from an operational security point of view, if these 509 00:32:13,970 --> 00:32:17,610 things are running in kernel mode. For those who don't know kernel mode an error 510 00:32:17,610 --> 00:32:21,330 in kernel node is what caused the crowdstrike issue. That was 511 00:32:21,490 --> 00:32:25,230 two summers ago and there are very good reasons 512 00:32:25,230 --> 00:32:28,950 to run things in kernel mode. But I have a hard time thinking that the 513 00:32:28,950 --> 00:32:29,590 risk of 514 00:32:32,950 --> 00:32:36,390 cheat prevention. I don't know if it raises to that level in my 515 00:32:36,390 --> 00:32:38,790 opinion. Right. And I think. 516 00:32:40,070 --> 00:32:43,190 Do gamers. Are gamers aware of this or. And I know I don't want to 517 00:32:43,190 --> 00:32:46,710 make this all about gamers because even though it's cool but these are high performance 518 00:32:46,870 --> 00:32:50,490 systems. Right. But so sorry about that but do gamers 519 00:32:50,490 --> 00:32:53,970 know the risks involved? I 520 00:32:53,970 --> 00:32:57,250 don't think all of them do. Certainly some do. 521 00:32:57,970 --> 00:33:01,530 Right. I would say that people that have 522 00:33:01,530 --> 00:33:05,330 been ardent Windows users 523 00:33:05,330 --> 00:33:09,090 for a long time like Linus Text tips. Right, right. Right 524 00:33:09,090 --> 00:33:12,850 out of Canada they just did their Linux challenge which seems to 525 00:33:12,850 --> 00:33:16,450 be like a yearly thing for them now or once every few years anyway. 526 00:33:16,890 --> 00:33:20,610 I've done a few of them now and maybe 527 00:33:20,610 --> 00:33:23,530 three. I don't follow that closely but 528 00:33:24,170 --> 00:33:27,930 this last Time around, you know, he had his typical, I'm 529 00:33:27,930 --> 00:33:31,610 moving to a different platform problems. And 530 00:33:32,170 --> 00:33:35,930 in previous challenges, if 531 00:33:35,930 --> 00:33:39,730 he ran to a wall, he was. And he's actually on the record saying this. 532 00:33:39,730 --> 00:33:42,210 He said, when I ran to the wall, I just threw my hands up and 533 00:33:42,210 --> 00:33:45,400 said, well, I'm just going back to Windows. He said, but now with all the 534 00:33:45,400 --> 00:33:49,240 trouble that I'm having with Windows right now with security and 535 00:33:49,800 --> 00:33:53,480 root level anti cheat and stuff like that, he knows what's going 536 00:33:53,480 --> 00:33:56,920 on there. And he's like, now I am 537 00:33:56,920 --> 00:34:00,640 motivated to put in the effort to migrate 538 00:34:00,640 --> 00:34:03,560 to something else because this is. 539 00:34:04,360 --> 00:34:08,200 This is just getting to be too much of a pain point. So. 540 00:34:08,520 --> 00:34:12,190 Yeah, interesting. Yeah, here's, by the way, the page that you mentioned 541 00:34:12,190 --> 00:34:15,990 on kde. So they do ship these around to be fair to people. 542 00:34:16,150 --> 00:34:19,950 So sometimes we're at the very top, sometimes we're near the bottom 543 00:34:19,950 --> 00:34:23,670 here. So I guess we. I mean, next time around 544 00:34:23,670 --> 00:34:25,910 we'll be at the top again. So we'll see. 545 00:34:27,510 --> 00:34:29,990 Maybe they're just trying to get more money from you. Who knows? 546 00:34:33,030 --> 00:34:36,810 We're a big contributor. I think we're one of the. I 547 00:34:36,810 --> 00:34:40,490 wouldn't say we're the largest contributor to kde, but I think we're 548 00:34:40,490 --> 00:34:44,130 now moving towards the upper echelon because. Okay, we're a patreon. I'm just 549 00:34:44,130 --> 00:34:47,090 joking. I'm just joking. I don't want to. I don't want to start any fights. 550 00:34:47,090 --> 00:34:50,570 I don't want to start any trouble. Oh, no, no, no. The initiative that I 551 00:34:50,570 --> 00:34:53,930 was talking about, though, is the bulletproof KDE initiative that. 552 00:34:54,010 --> 00:34:57,250 Yeah, working title. That's where we're basically 553 00:34:57,250 --> 00:35:00,810 freezing KDE at a specific version and then 554 00:35:01,210 --> 00:35:04,550 we are pro providing them. And I won't get into all the 555 00:35:04,550 --> 00:35:07,910 details, but we're setting up a continuous 556 00:35:07,910 --> 00:35:11,670 integration environment and where we're able to 557 00:35:11,670 --> 00:35:15,390 do automated tests within the data center. It's in 558 00:35:15,390 --> 00:35:19,030 Finland. And then we work with an international team 559 00:35:19,510 --> 00:35:23,110 for identifying. We manage the list 560 00:35:23,110 --> 00:35:26,950 of key paper cuts and. And then 561 00:35:27,110 --> 00:35:30,470 we pay them to help shepherd getting 562 00:35:30,790 --> 00:35:34,270 those things fixed. And we work with a Kubuntu team, which we also provide 563 00:35:34,270 --> 00:35:38,110 stipends for, to make sure that those get backported to 564 00:35:38,110 --> 00:35:41,950 the release. So if you buy one of our systems, not only do we continually 565 00:35:41,950 --> 00:35:45,670 test things like kernels and drivers before you 566 00:35:45,670 --> 00:35:49,510 ever see it, to make sure that it always works. So we're kind of 567 00:35:49,510 --> 00:35:53,110 like your remote IT department. Right? You know how, like, with your IT 568 00:35:53,110 --> 00:35:56,690 department, you don't get an image until they verified it? Well, we 569 00:35:56,690 --> 00:35:59,730 verify that we. Oh, that's pretty cool. 570 00:36:00,050 --> 00:36:03,650 Yeah. So we actually, if you want to take a look at 571 00:36:03,650 --> 00:36:07,170 what we verify, I'll share this tab instead. If you get a. 572 00:36:08,370 --> 00:36:11,770 This is probably a good way to put it, but here let's just go to 573 00:36:11,770 --> 00:36:15,570 support and you can look at the 574 00:36:16,450 --> 00:36:20,250 system support and it walks 575 00:36:20,250 --> 00:36:24,090 through everything that we do from hardware selection to 576 00:36:24,090 --> 00:36:27,930 making sure. Like making sure that the dual ethernet 577 00:36:27,930 --> 00:36:31,170 on the ZR Gen 2 which is coming up, 578 00:36:31,410 --> 00:36:35,170 or the big beast we just looked at, making sure those work, 579 00:36:35,250 --> 00:36:38,570 making sure three monitors work on sleep and 580 00:36:38,570 --> 00:36:42,290 resume etc, we make sure that's there. We make sure the 581 00:36:42,290 --> 00:36:45,890 kernel updates always work and that we have about 150 582 00:36:45,890 --> 00:36:49,660 major KPCs that we go through. We make sure 583 00:36:49,660 --> 00:36:53,500 that the Nvidia machine learning language, sorry, 584 00:36:53,500 --> 00:36:56,620 machine learning libraries are available 585 00:36:58,540 --> 00:37:01,940 and all these, which for non Linux people that's a 586 00:37:01,940 --> 00:37:05,740 massive pain point. I will say making sure you get that 587 00:37:05,740 --> 00:37:09,340 working like. No, that part of the reason why I 588 00:37:09,340 --> 00:37:13,100 chose to get the Nvidia, the gtx, the DGX Spark. 589 00:37:13,660 --> 00:37:16,620 Yep. Was that it was made by Nvidia and Nvidia 590 00:37:17,500 --> 00:37:20,620 would be on the hook to supply those drivers. 591 00:37:21,180 --> 00:37:24,220 So hold that thought because I want to. I want to come back to Nvidia 592 00:37:24,220 --> 00:37:27,980 and Linux in a few minutes, but go ahead. Sorry. Well, it's all right. We 593 00:37:27,980 --> 00:37:31,580 just. We spent the last. On the ZR Gen 1 594 00:37:31,580 --> 00:37:35,420 and the M2 Gen 7. We 595 00:37:35,420 --> 00:37:39,100 spent about 150 hours of development time on 596 00:37:39,100 --> 00:37:42,710 creating and packaging everything for those 597 00:37:43,430 --> 00:37:46,390 Nvidia drivers and the machine learning libraries. 598 00:37:47,030 --> 00:37:50,630 It was a. That. That is not normally the amount that we 599 00:37:50,630 --> 00:37:54,230 spend, but because we do support the machine 600 00:37:54,230 --> 00:37:57,830 learning libraries and this was with Ubuntu 601 00:37:57,830 --> 00:38:01,550 24.04. There were a lot of challenges 602 00:38:01,550 --> 00:38:05,390 this time around. I think it's partially due to the newness 603 00:38:05,390 --> 00:38:09,120 of the hardware and also due to the fact that there's more of an 604 00:38:09,120 --> 00:38:12,960 emphasis on commercial hardware than they 605 00:38:12,960 --> 00:38:16,280 used to have versus consumer hardware. 606 00:38:16,840 --> 00:38:20,480 But in any event, setting all those things up, adding the 607 00:38:20,480 --> 00:38:24,040 right repositories from Nvidia and then pinning to the right 608 00:38:24,920 --> 00:38:28,360 machine learning and inference libraries is 609 00:38:28,600 --> 00:38:32,400 a lot of work. And if you buy from us, you 610 00:38:32,400 --> 00:38:36,000 outsource that. So we test that 611 00:38:36,000 --> 00:38:39,680 before every kernel upgrade and we test that for every major 612 00:38:40,400 --> 00:38:43,800 upgrade. For the Nvidias we actually have an 613 00:38:43,800 --> 00:38:47,400 Nvidia meta package that we create that's validated for your 614 00:38:47,400 --> 00:38:51,120 hardware. We also have a kernel which is spun 615 00:38:51,120 --> 00:38:54,640 off of the mainline Ubuntu kernel, but 616 00:38:54,640 --> 00:38:58,440 we will advance patch stuff that 617 00:38:58,440 --> 00:39:02,080 we then upstream to the mainline kernel or to the Ubuntu 618 00:39:02,080 --> 00:39:05,850 kernel that allows say proper hardware 619 00:39:05,850 --> 00:39:09,570 integration or sound routing and stuff like that. So when you get 620 00:39:09,570 --> 00:39:13,410 the system, you open it up, you turn it on 621 00:39:13,410 --> 00:39:16,890 and everything works. And then it continues to work for the 622 00:39:16,890 --> 00:39:20,450 entire support window. And the standard support window is three years. 623 00:39:20,610 --> 00:39:24,130 So we keep bench models and we validate every 624 00:39:24,130 --> 00:39:27,970 single model that's been released and last sold in the last three 625 00:39:27,970 --> 00:39:31,740 years. So when you buy a system, you typically get three and a 626 00:39:31,740 --> 00:39:34,940 half to four years of support 627 00:39:35,660 --> 00:39:39,340 in basically IT team support for your system. 628 00:39:40,060 --> 00:39:43,860 And then by the time you go off of that support, generally 629 00:39:43,860 --> 00:39:47,020 everything is upstreamed anyway. So. But 630 00:39:47,180 --> 00:39:50,940 it's. That's the reason why companies buy from us for 631 00:39:51,180 --> 00:39:54,820 this purpose. So the other thing we do here, 632 00:39:54,820 --> 00:39:58,260 and I'll change the sharing here because you'll. Is there's a lot of 633 00:39:58,260 --> 00:40:02,100 integration that we do that is 634 00:40:03,380 --> 00:40:06,740 people ask us are we a hardware company or a software company? 635 00:40:07,060 --> 00:40:10,660 We're really a software company that does hardware because we have 636 00:40:10,660 --> 00:40:13,460 to. Interesting. 637 00:40:14,500 --> 00:40:18,260 Yeah. The best way to describe that, I would say is that when you buy 638 00:40:18,260 --> 00:40:21,700 a Mac you get a full ecosystem 639 00:40:22,020 --> 00:40:25,780 and you have a few key pieces of hardware 640 00:40:25,780 --> 00:40:29,570 that they continuously integrate for. And so I 641 00:40:29,570 --> 00:40:33,330 don't think anyone's going to argue that Macs are more reliable than Windows 642 00:40:33,330 --> 00:40:37,090 systems because of the. And it's because of the limited hardware 643 00:40:37,090 --> 00:40:40,130 and the fact that Apple does continue 644 00:40:40,850 --> 00:40:44,410 for a number of years to do basically what we're doing, which 645 00:40:44,410 --> 00:40:48,170 is they have a limited amount of hardware and they have 646 00:40:48,170 --> 00:40:51,970 a limited amount of software. It's a vast support 647 00:40:52,050 --> 00:40:55,770 surface, but it's manageable. And we're 648 00:40:55,770 --> 00:40:59,530 doing the same thing for Linux is that that Apple is doing for their 649 00:40:59,530 --> 00:41:03,370 proprietary os. But we have the advantage of being Linux native. 650 00:41:04,170 --> 00:41:07,970 That is very valuable if you're deploying to Linux 651 00:41:07,970 --> 00:41:11,730 as opposed to deploying to macOS. Yeah, that's 652 00:41:11,730 --> 00:41:15,530 our philosophy. The other thing that you'll see and we're in 653 00:41:15,530 --> 00:41:19,210 kind of transition here, so. And I'm actually gonna. This is the 26 654 00:41:19,210 --> 00:41:22,840 out of 4 development. I'm in an alpha system. So if something 655 00:41:22,840 --> 00:41:26,680 breaks here, don't go around and point say, hey look, they're 656 00:41:26,680 --> 00:41:30,400 shipping broken stuff. This stuff isn't shipping for another. We're planning on 657 00:41:30,720 --> 00:41:34,560 two to three weeks. Two weeks would be the very minimum. Probably three 658 00:41:34,560 --> 00:41:38,399 weeks we'll be shipping once all the bugs are worked out. But 659 00:41:38,399 --> 00:41:42,240 here's an example though of if you go to like support here, 660 00:41:42,400 --> 00:41:46,120 we have all of these. Pretty much anything that you want to do 661 00:41:46,120 --> 00:41:48,810 that's a workflow, but. And 662 00:41:49,610 --> 00:41:52,970 so if you look at like Linux help, you can go to Chat 663 00:41:52,970 --> 00:41:56,730 GDP and have it lie to you for six or seven iterations 664 00:41:56,730 --> 00:42:00,330 on a question, or you can go to a forum 665 00:42:00,490 --> 00:42:03,610 or a bug report and try to figure out how to get something done. 666 00:42:04,250 --> 00:42:07,730 And we've all had the experience where it's kind of similar to Chat 667 00:42:07,730 --> 00:42:11,050 gdp where it'll lie to you numerous times and hallucinate 668 00:42:11,210 --> 00:42:14,770 until you kind of have to know where you're going to get the correct 669 00:42:14,770 --> 00:42:18,510 answer. Or you could just go here and get a correct answer right off 670 00:42:18,510 --> 00:42:22,270 the bat. Because it's tested for your system, so 671 00:42:22,270 --> 00:42:25,150 it's tested for the OS for your system. So if you want to connect to 672 00:42:25,150 --> 00:42:28,830 a phone, you can see that this is tested for a 673 00:42:28,830 --> 00:42:32,550 previous operating system that's still supported. It's also verified 674 00:42:32,550 --> 00:42:36,150 on the current one because we actually have people to go and test the 675 00:42:36,150 --> 00:42:39,430 entire procedure on the OS 676 00:42:39,750 --> 00:42:43,310 with the drivers that are in place. So 677 00:42:43,310 --> 00:42:46,790 interesting. You can, you know, let's say I want to set up a 678 00:42:46,790 --> 00:42:50,430 vpn. So you just go here, press VPN and 679 00:42:50,430 --> 00:42:53,870 oh, look, I can connect to a VPN. And there you are, 680 00:42:54,430 --> 00:42:58,190 VPNs everywhere. There's Taylor Swift. I was wondering when she was going 681 00:42:58,190 --> 00:43:01,990 to show up. And this will actually walk you through setting 682 00:43:01,990 --> 00:43:05,830 up a VPN completely for your system. And this 683 00:43:05,830 --> 00:43:08,030 is a amalgamation of 684 00:43:09,780 --> 00:43:13,540 over here running a Wireguard server 685 00:43:13,540 --> 00:43:17,300 or installing OpenVPN and configuring everything 686 00:43:17,380 --> 00:43:19,380 in an optimal fashion for your system 687 00:43:20,980 --> 00:43:24,340 if you want to know how to do things right. And it's a 688 00:43:24,500 --> 00:43:28,140 common workflow, we probably already have it here and 689 00:43:28,140 --> 00:43:31,860 it's been tested for you. One of the things 690 00:43:31,860 --> 00:43:35,300 that we do that our customers really like 691 00:43:36,090 --> 00:43:39,770 is we make sure that they don't have Franken systems. 692 00:43:41,290 --> 00:43:44,570 So you see that with a lot of people that are using Chat GDP 693 00:43:44,810 --> 00:43:48,050 or using forms and stuff like that, they end up finding 694 00:43:48,050 --> 00:43:51,450 suboptimal solutions after 695 00:43:51,610 --> 00:43:55,290 maybe breaking their system a couple of times. Then they copy and 696 00:43:55,290 --> 00:43:58,970 paste something to a configuration file somewhere and it works kind 697 00:43:58,970 --> 00:44:02,290 of well enough and they limp along with it and they're afraid to touch it 698 00:44:02,290 --> 00:44:06,000 because I might break it again. And then they have to reinstall the OS 699 00:44:06,000 --> 00:44:08,920 for one reason or another or move to a different machine and they have no 700 00:44:08,920 --> 00:44:12,720 idea what they did. If you contrast that to what we 701 00:44:12,720 --> 00:44:16,080 do is that we end up finding those solutions 702 00:44:16,480 --> 00:44:20,320 and we'll create them into this documentation. But 703 00:44:20,560 --> 00:44:24,000 the way that we run the company is we actually push those 704 00:44:24,000 --> 00:44:27,200 changes up into software so that you just 705 00:44:27,440 --> 00:44:31,090 update your packages and. And those configurations are 706 00:44:31,090 --> 00:44:34,890 done for you in a repeatable fashion, again, like an IT 707 00:44:34,890 --> 00:44:37,690 department. So we even have 708 00:44:38,650 --> 00:44:42,170 a pitch deck that actually shows how we do that. And 709 00:44:42,410 --> 00:44:46,090 so our goal is always to move everything up the stack. Because 710 00:44:46,810 --> 00:44:50,450 if you look at compliance, people doing the 711 00:44:50,450 --> 00:44:53,690 right thing, if you put the stuff into the packages 712 00:44:54,250 --> 00:44:56,970 that people update, their compliance is 100%. 713 00:44:58,070 --> 00:45:01,750 If you put it in documentation, if you're lucky, 714 00:45:01,750 --> 00:45:05,190 you might get 50% compliance or 30% compliance. 715 00:45:05,990 --> 00:45:09,350 Right? And we're always pushing to get 716 00:45:09,350 --> 00:45:12,710 100% compliance so that people don't have to worry about that. 717 00:45:13,750 --> 00:45:17,550 One thing that's also interesting here is like, if you look at. Let's take 718 00:45:17,550 --> 00:45:21,230 a look at image editing, for example, and we have a whole 719 00:45:21,230 --> 00:45:23,350 subsystem that's in place here for, 720 00:45:25,280 --> 00:45:28,880 we call Curated Apps. And this allows you to 721 00:45:28,960 --> 00:45:32,480 like, say, start an application directly from the 722 00:45:32,480 --> 00:45:36,160 documentation. And if the application isn't installed, 723 00:45:36,160 --> 00:45:39,960 it'll actually add the cryptographic keys and 724 00:45:39,960 --> 00:45:43,520 then add the repository and then download the program 725 00:45:43,520 --> 00:45:47,120 and then install the program if necessary. 726 00:45:47,600 --> 00:45:51,080 So you don't have to step out and do five or six different steps and 727 00:45:51,080 --> 00:45:54,780 say, what was I doing? You just click on something and if 728 00:45:54,780 --> 00:45:57,780 it's installed, it'll launch it like you see here. 729 00:45:58,660 --> 00:46:02,420 And if it's not installed, it'll go all the way back as necessary. 730 00:46:02,820 --> 00:46:05,460 It'll even encourage you to 731 00:46:06,420 --> 00:46:09,060 even step you through, for example, installing, 732 00:46:10,580 --> 00:46:13,940 say, Docker, which 733 00:46:14,100 --> 00:46:17,940 requires service setups and adding 734 00:46:17,940 --> 00:46:21,220 yourself to groups so that you can run as a regular user and stuff like 735 00:46:21,220 --> 00:46:23,820 that. It'll actually walk you right through that. 736 00:46:25,020 --> 00:46:28,820 So if I go to support, let's say, let's go to Curated 737 00:46:28,820 --> 00:46:32,500 Apps right here. Now, I haven't checked this out on here. 738 00:46:32,500 --> 00:46:36,300 We're still in alpha, but I believe this is actually already in 739 00:46:36,300 --> 00:46:40,020 place. So let's take a look for Docker. So click 740 00:46:40,020 --> 00:46:43,820 on Docker and there it's not installed. So do I want to 741 00:46:43,820 --> 00:46:46,460 install it? Yes. Now I'm asked for my password 742 00:46:49,110 --> 00:46:52,710 and away we go. And now it's actually downloading the system. It's 743 00:46:52,790 --> 00:46:56,310 added the repository for the official Docker release. 744 00:46:56,790 --> 00:46:59,990 It's added the cryptographic keys for the actual Docker release. 745 00:47:00,390 --> 00:47:03,910 It's installing it right now. And then it's going to guide me through changing 746 00:47:03,910 --> 00:47:07,630 the groups again. We're just really 747 00:47:07,630 --> 00:47:11,190 focused on making sure that people are 748 00:47:11,190 --> 00:47:14,960 prepped for success. Here you go. It 749 00:47:14,960 --> 00:47:18,760 says Dockers installed, but the user dev must be added to the Docker group to 750 00:47:18,760 --> 00:47:22,560 run as normal user. Do you want to add to the group. Now 751 00:47:22,640 --> 00:47:26,320 say yes, now I have to do that as 752 00:47:26,320 --> 00:47:29,920 root. Now it's been added, 753 00:47:31,520 --> 00:47:35,360 Docker's installed. But you got to log out and log back in if you want 754 00:47:35,360 --> 00:47:36,480 to use it as a user. 755 00:47:38,960 --> 00:47:42,760 It's fantastic. That's amazing because this does. I know a lot of people that 756 00:47:42,760 --> 00:47:46,320 are very, very lost right now in terms 757 00:47:46,320 --> 00:47:49,400 of Windows isn't what it used to be. And 758 00:47:51,240 --> 00:47:54,600 there's a lot of people that are looking for a new place to land with 759 00:47:54,760 --> 00:47:58,600 high performance hardware. And I can only assume that you 760 00:47:58,600 --> 00:48:02,080 could probably run this as the base operating system and kick off as many 761 00:48:02,080 --> 00:48:05,920 VMs, particularly if you have enough RAM, kick off as many VMs as 762 00:48:05,920 --> 00:48:09,730 you need for Windows. Right. If you really absolutely needed a Windows like 763 00:48:09,730 --> 00:48:13,450 a pure Windows machine. Oh, absolutely. In fact, if you. 764 00:48:13,690 --> 00:48:16,930 That sounds like a common workflow. Let's see if we have something that fits that 765 00:48:16,930 --> 00:48:20,650 category. Oh, here's how you stall 766 00:48:21,290 --> 00:48:24,930 virtual 11. Right. And by the way, all of these right 767 00:48:24,930 --> 00:48:27,850 here have, are available 768 00:48:28,570 --> 00:48:31,370 in blow up format, if you will. 769 00:48:32,410 --> 00:48:35,690 So we can just walk right through these and it'll just go through all the 770 00:48:35,690 --> 00:48:39,380 steps for you. This has been validated for Windows 11 771 00:48:39,540 --> 00:48:43,300 on the latest OS. You can see over here that it's already applied 772 00:48:43,300 --> 00:48:46,820 to this os. I mean this is brilliant because 773 00:48:47,460 --> 00:48:50,900 there's so many times when there's no instruction manual, there's no 774 00:48:50,900 --> 00:48:54,260 instructions anywhere. You kind of have to just, 775 00:48:54,500 --> 00:48:58,260 you know, Svengali it yourself. But to have these guided solutions 776 00:48:58,420 --> 00:49:01,860 is just. Is really, I think 777 00:49:01,860 --> 00:49:05,490 reduce anxiety. Especially with Linux. 778 00:49:05,890 --> 00:49:09,450 Right? Linux, you're kind of, you know, good luck 779 00:49:09,450 --> 00:49:13,210 is kind of like the. You're kind of 780 00:49:13,210 --> 00:49:17,010 left to your own devices and your own skills, which for some people is perfectly 781 00:49:17,010 --> 00:49:20,690 fine. But not for everyone. Oh yeah, and even 782 00:49:20,690 --> 00:49:24,210 the people that. There's a bit of a dunning Kruger effect out there. 783 00:49:24,610 --> 00:49:28,370 Yes, smidgen of that. Especially people that get behind 784 00:49:28,370 --> 00:49:32,210 chat gtp. Right. And you know, I used it just the other day and 785 00:49:32,210 --> 00:49:35,930 I was trying to solve a problem where I knew already what the answer was. 786 00:49:38,010 --> 00:49:41,610 It was actually the answer was 787 00:49:41,610 --> 00:49:44,970 looking to pull down the latest Jetbrains toolbox 788 00:49:45,450 --> 00:49:49,250 and install it. So one of the curated apps here that 789 00:49:49,250 --> 00:49:52,890 is not finished for this version of the release is 790 00:49:52,890 --> 00:49:56,490 installing the Jetbrains toolbox. So I knew that I had to go out and 791 00:49:56,490 --> 00:50:00,270 pull a web API and make a request to 792 00:50:00,270 --> 00:50:03,830 get the current version and then build a 793 00:50:03,830 --> 00:50:06,270 URL to create a download poll. 794 00:50:08,270 --> 00:50:11,910 Being a developer for three or four years at 795 00:50:11,910 --> 00:50:15,670 least. Yeah, multiply that by a 796 00:50:15,670 --> 00:50:18,830 bit. But I knew that that's where we needed to be. Right. 797 00:50:19,870 --> 00:50:23,230 And so I went and used GTP and asked, 798 00:50:24,040 --> 00:50:27,400 how do I do this? And I had to ask literally six times. 799 00:50:29,720 --> 00:50:33,040 And it kept giving me the wrong URL to go and make the request on 800 00:50:33,040 --> 00:50:35,800 it. And I was like, you know, I could have just looked up for the 801 00:50:37,080 --> 00:50:40,760 Jetbrains API and I would have gotten there in 802 00:50:40,760 --> 00:50:44,600 a search and then a quick query. But the 803 00:50:44,600 --> 00:50:47,640 problem with those answers were they were all 804 00:50:48,120 --> 00:50:51,860 extremely confident. Oh, yeah, you just need to 805 00:50:51,860 --> 00:50:54,940 do this and this and this here, cut and paste this. It won't hurt. 806 00:50:56,220 --> 00:50:59,940 We're seeing an uptick in people breaking their systems because they're using chat 807 00:50:59,940 --> 00:51:03,180 gdp. Why doesn't that surprise me? Yeah, 808 00:51:04,220 --> 00:51:07,500 we're actually been talking about creating a local 809 00:51:07,580 --> 00:51:11,340 LLM that will basically consume all of these 810 00:51:11,660 --> 00:51:15,020 documents that you see and use these as the primary source 811 00:51:15,830 --> 00:51:19,350 instead of going out to the web and scraping that. And 812 00:51:19,670 --> 00:51:22,870 that way people will have an interface that will be available 813 00:51:23,030 --> 00:51:26,390 directly from their toolbar and 814 00:51:26,630 --> 00:51:29,990 that they're. They will be just as confident. But 815 00:51:30,070 --> 00:51:33,870 unlike the confidence of chat gdp, most 816 00:51:33,870 --> 00:51:36,390 of the time, in my experience, it'll be right. 817 00:51:37,430 --> 00:51:41,230 Bonus. Another thing here is you 818 00:51:41,230 --> 00:51:44,150 can see that we have service guides for all of our systems that. 819 00:51:45,160 --> 00:51:48,280 And we have the same structure for every one of them, including what the bio 820 00:51:48,280 --> 00:51:50,760 settings should be for any one of the systems, 821 00:51:52,200 --> 00:51:56,000 so. Oh, very cool. Yeah, you click on the show you how to swap out 822 00:51:56,000 --> 00:51:59,520 your ram and we don't void the 823 00:51:59,520 --> 00:52:02,960 warranty if somebody opens up their case, so. 824 00:52:02,960 --> 00:52:05,960 Interesting. Yeah, I. 825 00:52:06,600 --> 00:52:09,600 Where can folks find out more and get their hands on one of these sweet 826 00:52:09,600 --> 00:52:13,400 systems? Well, I just go to our website, which is 827 00:52:13,640 --> 00:52:16,600 the. There's our. That's the. 828 00:52:18,600 --> 00:52:22,280 That's the new interface you're seeing there. I shouldn't say 829 00:52:22,280 --> 00:52:25,880 new. That's an overview. So we have different 830 00:52:27,000 --> 00:52:30,680 things here. Oh, very cool. Yeah, so 831 00:52:30,920 --> 00:52:34,120 it's a beautiful interface. It's just. 832 00:52:34,120 --> 00:52:37,590 Kfocus.org is our website. Okay. We used to have 833 00:52:37,590 --> 00:52:41,350 kfocus. Com, but we had somebody steal it 834 00:52:41,350 --> 00:52:45,030 from us and to give it back. Yeah, I 835 00:52:45,030 --> 00:52:48,110 won't go into all the details on that one, but watch your backs, people. 836 00:52:48,670 --> 00:52:51,550 Yeah, just go here. And I think it's pretty straightforward. 837 00:52:52,189 --> 00:52:55,830 And yeah, we'll be. I 838 00:52:55,830 --> 00:52:59,230 wouldn't recommend buying it right now because in the next couple of days. 839 00:52:59,470 --> 00:53:02,690 So if you're watching this in the next couple of days, then yeah, buy right 840 00:53:02,690 --> 00:53:06,130 now. But we'll be updating all these 841 00:53:06,130 --> 00:53:09,850 models to 26.04 and we don't expect to 842 00:53:09,850 --> 00:53:13,450 release any or ship any other models with the 843 00:53:14,570 --> 00:53:17,970 earlier version of the os. So we're basically on a little bit of a 844 00:53:17,970 --> 00:53:21,810 pause as we finalize that and finalize the validation 845 00:53:21,810 --> 00:53:25,610 for all the new hardware. It's a big hard push right now that we're 846 00:53:25,610 --> 00:53:28,970 going through, but it's going to be pretty awesome. 847 00:53:29,130 --> 00:53:32,580 It's our again, Candace was there at the 848 00:53:32,580 --> 00:53:35,740 beginning from 2019 and 849 00:53:36,140 --> 00:53:39,820 this will be our fourth major or 850 00:53:39,820 --> 00:53:43,500 fifth major OS upgrade. And fourth actually. 851 00:53:43,740 --> 00:53:45,420 Fourth and 852 00:53:47,500 --> 00:53:50,580 yeah, it's better than ever. Well, there's one thing that I do want to show 853 00:53:50,580 --> 00:53:53,820 you that I think that you would very much appreciate 854 00:53:54,140 --> 00:53:57,590 and let me put it here. One of the things you run into 855 00:53:57,830 --> 00:54:01,030 with immutable systems. Immutable systems are great 856 00:54:01,350 --> 00:54:04,870 until you don't want them to be immutable anymore and then you're stuck. 857 00:54:06,950 --> 00:54:10,470 We put about 1200 engineering hours 858 00:54:10,950 --> 00:54:14,310 into a thing called 859 00:54:15,670 --> 00:54:19,270 rollback. Oh, very 860 00:54:19,270 --> 00:54:22,880 cool. So you can, it's. That could be very 861 00:54:22,880 --> 00:54:26,600 useful. What system rollback 862 00:54:26,600 --> 00:54:30,240 does is it takes a snapshot of your root system and 863 00:54:30,240 --> 00:54:33,840 boot system and then it is immutable. 864 00:54:36,960 --> 00:54:40,520 People that are creating immutable file systems or immutable 865 00:54:40,520 --> 00:54:44,000 systems are basically doing the same sort of thing. 866 00:54:45,600 --> 00:54:48,990 But here you're doing it at your 867 00:54:49,150 --> 00:54:52,950 leisure or you can have it done automatically. You 868 00:54:52,950 --> 00:54:56,790 can see up here we have automatic snapshots on here and I'd give you 869 00:54:56,790 --> 00:54:59,870 a demo on it, but it's not on this system because it's a development system. 870 00:55:00,350 --> 00:55:04,110 But there's people that you'll see post recently there was 871 00:55:04,110 --> 00:55:07,790 on Twitter where one of the guys said the best system you can get is 872 00:55:07,790 --> 00:55:10,910 Kubuntu Focus because they're amazing rollback system. 873 00:55:11,710 --> 00:55:15,280 And this is what he was referring to. This allows you to take 874 00:55:15,280 --> 00:55:19,000 snapshots, roll them back and every time you upgrade your system 875 00:55:19,000 --> 00:55:22,720 it takes a snapshot before the upgrade. So it 876 00:55:22,720 --> 00:55:26,080 causes problems. You can roll back. So not only are we pre 877 00:55:26,080 --> 00:55:29,879 checking all the major updates, like all the kernel updates etc and all 878 00:55:29,879 --> 00:55:33,720 the Nvidia driver updates, but even if a minor 879 00:55:33,720 --> 00:55:37,400 update causes a problem, let's say an app update, you can just go 880 00:55:37,400 --> 00:55:40,910 over here and roll back to the previous one version. That's 881 00:55:40,910 --> 00:55:44,630 fantastic. We also wrote an event driven 882 00:55:44,790 --> 00:55:47,990 monitor. It's a throttled and 883 00:55:48,230 --> 00:55:51,750 debounced event driven system. 884 00:55:51,830 --> 00:55:54,870 So it doesn't have a major 885 00:55:55,349 --> 00:55:58,390 impact in performance. It's a very tiny impact of performance. 886 00:55:59,030 --> 00:56:02,670 But if you end up pushing this copy on 887 00:56:02,670 --> 00:56:06,420 write file system to the point where you don't have enough space, 888 00:56:06,740 --> 00:56:10,260 it will actually pop up and warn you immediately and 889 00:56:10,340 --> 00:56:14,140 it will also turn off the automatic snapshots until you 890 00:56:14,140 --> 00:56:17,580 fix it. And it also guides you on how does turn off the 891 00:56:17,580 --> 00:56:21,379 snapshots until it's fixed. Interesting. Yeah, that was a 892 00:56:21,379 --> 00:56:24,900 part of the reason why it was 1200 hours is because we have the 893 00:56:24,900 --> 00:56:28,420 whole solution. Also, unlike a lot of 894 00:56:28,420 --> 00:56:32,220 software, this was accelerated tested. I come from 895 00:56:32,220 --> 00:56:35,980 automotive design background so like when if we screwed up, 896 00:56:35,980 --> 00:56:38,980 people died and you lose your job. We use a lot of 897 00:56:39,780 --> 00:56:43,300 spec driven development techniques that have been around 898 00:56:43,620 --> 00:56:47,420 for probably 50 years or longer in automotive that have been 899 00:56:47,420 --> 00:56:51,140 proven out. And so we use design for 900 00:56:51,700 --> 00:56:55,380 design failure mode effect analysis with RPMs 901 00:56:55,540 --> 00:56:59,340 and KPCs and then we also use accelerated 902 00:56:59,340 --> 00:57:02,960 testing. So we actually had laptops set up for this where 903 00:57:02,960 --> 00:57:06,480 they ran through multiple three year cycles 904 00:57:06,960 --> 00:57:10,600 of taking snapshots, installing packages, rolling 905 00:57:10,600 --> 00:57:14,160 back, taking more snapshots and that was all automated. So we just had 906 00:57:14,160 --> 00:57:18,000 systems that were like 125 watt light bulbs burning up 907 00:57:18,880 --> 00:57:22,680 constantly doing all of that. But we wanted to make sure that it 908 00:57:22,680 --> 00:57:26,400 was reliable for users. And so. And then we 909 00:57:26,400 --> 00:57:30,100 also did the same thing like with. Or we do a 910 00:57:30,100 --> 00:57:33,940 related thing which is make sure the BTRFS file system that 911 00:57:33,940 --> 00:57:37,700 this is based on has appropriate performance and we tune that 912 00:57:37,700 --> 00:57:41,500 as well. Basically it's like again it's like you're going into a big 913 00:57:41,500 --> 00:57:45,100 company, you've got an IT department that looks after you 914 00:57:45,420 --> 00:57:49,020 and make sure that everything just works and keeps working. 915 00:57:49,740 --> 00:57:53,020 That's cool. Yeah. All you got to do is update. Awesome. 916 00:57:53,500 --> 00:57:57,020 We'll make sure that we put the shit linked here and you got me, 917 00:57:57,810 --> 00:58:01,570 got me. You got my attention. Good. So very 918 00:58:01,570 --> 00:58:05,010 cool. And I think it's a good alternative for people that. 919 00:58:05,730 --> 00:58:08,410 I think it's a great alternative for people who want to get into Linux but 920 00:58:08,410 --> 00:58:11,330 maybe don't are afraid of it. And all these things you put in in place, 921 00:58:11,330 --> 00:58:14,290 I think remove a lot of that fear and I think that's great.