WEBVTT

00:00:00.380 --> 00:00:02.900
Speaker 0: Veet has been acquired by Cloudflare.

00:00:03.080 --> 00:00:25.460
Speaker 0: Or to be precise, the veet team or company behind it, Void Zero is joining cloudflare and as a web developer its worth closer look because obviously veet built tool and so much more in modern JavaScript and TypeScript projects.

00:00:25.840 --> 00:00:28.520
Speaker 0: And of course, the big question there for is why this happening?

00:00:28.680 --> 00:00:30.800
Speaker 0: What does it mean for web

00:00:30.860 --> 00:00:31.400
Speaker 0: developers?".

00:00:31.600 --> 00:00:34.960
Speaker 0: I guess that's two questions actually but let us take a closer look now.

00:00:35.360 --> 00:00:37.940
Speaker 0: First things first, there are three blog posts.

00:00:38.040 --> 00:00:47.440
Speaker 0: I'll link them all below which talk about this change and make it very clear that VIT remains open source under the MIT license.

00:00:50.280 --> 00:01:03.640
Speaker 0: so you will be able to deploy your VIT applications not just on Cloudflare in just right now and in the past on a multitude of providers, all to adjust on VPS if you want.

00:01:04.519 --> 00:01:08.680
Speaker 0: And the development will still be controlled by the Veet team.

00:01:08.780 --> 00:01:11.100
Speaker 0: they'll follow their existing roadmap.

00:01:12.500 --> 00:01:39.820
Speaker 0: I'm sure that it's going to stay open source for the road map Stay pretty cloudflare independent, but I would guess that it will be influenced by a cloud flare to some degree because of course if somebody's paying your bills you will want to align with their requirements.

00:01:39.940 --> 00:01:48.640
Speaker 0: That being said I'm sure it will not be cloud-free exclusive and there are many things on the roadmap that align with broader interest.

00:01:51.000 --> 00:01:59.520
Speaker 0: We had pretty much the same message there.

00:01:59.580 --> 00:02:07.320
Speaker 0: You could say it also still is open source and MIT licensed, then you can absolutely Still use bun for whatever you used to before end.

00:02:07.700 --> 00:02:11.800
Speaker 0: It's still an amazing JavaScript in TypeScript runtime no doubts about that.

00:02:12.340 --> 00:02:22.280
Speaker 0: But if you look at The features That have been shipped to bun over the last months For example the bun web view or the bun image API?

00:02:22.340 --> 00:02:36.960
Speaker 0: eight of course kind Of seems like these are features That makes sense for a tool that's used by coding agents and even runs a coding agent, namely Claude code.

00:02:37.040 --> 00:02:46.700
Speaker 0: So I would expect with Veet we also see in the tool stays amazing can be use all kinds of projects you run on any provider.

00:02:47.580 --> 00:02:58.400
Speaker 0: but i imagine some parts future roadmap will particularly help with building cloudflare applications, if that makes sense.

00:02:58.540 --> 00:03:09.540
Speaker 0: But at the same time many of things may make it easier to build and ship CloudFlare applications... ...may also make it easy to ship webapplications without our provider.

00:03:09.640 --> 00:03:11.040
Speaker 0: So thats not really negative.

00:03:11.100 --> 00:03:15.520
Speaker 0: It's just something to be aware off I would say or something I think, of course don't know.

00:03:15.960 --> 00:03:20.500
Speaker 0: But why exactly is this happening and what exactly is that white zero thing?

00:03:20.560 --> 00:03:21.320
Speaker 0: in case you missed it?

00:03:21.680 --> 00:03:30.180
Speaker 0: Well as mentioned White Zero is a company set up by Avenue the creator of Veed, The Creator of VueJS too btw!

00:03:30.820 --> 00:03:36.280
Speaker 0: And if you wonder Vuejs isn´t part of this deal... It's not part of Void Zero.

00:03:36.840 --> 00:03:49.180
Speaker 0: The Vue JS team now pretty much independent off of avenue is my understanding at least so For for many, many years view hasn't been a one-man show anymore.

00:03:49.580 --> 00:03:52.060
Speaker 0: So vue.js absolutely not related to that.

00:03:52.420 --> 00:03:54.260
Speaker 0: but white zero Is a company?

00:03:54.340 --> 00:04:00.040
Speaker 0: That was set up I think in twenty twenty two or twenty three and received venture capital funding.

00:04:00.500 --> 00:04:01.800
Speaker 0: And they built build tools.

00:04:02.020 --> 00:04:04.200
Speaker 0: They built Many amazing bill tools.

00:04:04.340 --> 00:04:08.380
Speaker 0: They built oxland for example an Amazing alternative to eslint.

00:04:08.620 --> 00:04:15.840
Speaker 0: They also built ox Fmt ox format an amazing formatter all super fast built with rust under the hood.

00:04:15.980 --> 00:04:30.020
Speaker 0: They also build roll down Rust powered JavaScript and typescript bundler, And all these tools are part of that void zero company and Are used or usable via beat Under-the-hood?

00:04:30.380 --> 00:04:40.580
Speaker 0: um...and they build that to build a comprehensive ecosystem off tools That make your life as developer easier faster so that building javascript applications is more fun and faster.

00:04:41.420 --> 00:04:45.180
Speaker 0: That's white zero, a company that builds these build tools!

00:04:45.420 --> 00:04:47.020
Speaker 0: How does such a company earn money?

00:04:47.280 --> 00:04:49.940
Speaker 0: That exactly the big problem.

00:04:50.380 --> 00:04:53.620
Speaker 0: as mentioned they are venture capital funded or were.

00:04:54.100 --> 00:05:02.300
Speaker 0: venture capital earns some money at some point and I guess even if they weren't everybody needs to make a living.

00:05:02.780 --> 00:05:07.920
Speaker 0: So, at the end of last year in October twenty-twenty five They announced Veet Plus!

00:05:08.600 --> 00:05:14.040
Speaker 0: And The idea was To have like one tool Like A supercharged veet.

00:05:14.180 --> 00:05:15.480
Speaker 0: Veet Of course is free to use.

00:05:16.420 --> 00:05:18.580
Speaker 0: That was the idea, would not be free to use.

00:05:18.980 --> 00:05:26.180
Speaker 0: Instead it will simply one tool that has all of that linting formatting testing stuff built in and makes it particularly easy-to-use!

00:05:26.380 --> 00:05:48.180
Speaker 0: Of course you could set up on your own two in a normal VIT project... You can add vtest for testing oxformatoxlint and wireitupmall manually.. And the idea behind VIT plus is that It'll make things easier with these things builtin and be more interesting best practice enabled setup.

00:05:48.440 --> 00:06:03.220
Speaker 0: But of course charging money for something which you can also relatively easy set up on your own, probably not the simply not an idea that earns you tons of money, or it's very hard to monetize at least.

00:06:03.600 --> 00:06:10.740
Speaker 0: That's why then later they announced Void and what you could say was a framework built on top of wheat?

00:06:10.820 --> 00:06:19.040
Speaker 0: A framework that would make it far easier to build complete full stack applications And most importantly also deploy them to cloudflare.

00:06:19.120 --> 00:06:30.940
Speaker 0: It would essentially be like service built on top of Cloudflare, where you wouldn't have to worry about provisioning or setting up all the cloudflare infrastructure under the hood instead.

00:06:31.020 --> 00:06:38.240
Speaker 0: You could build your full stack application and then run a command that it would then set-up the cloud flare resources for you.

00:06:38.320 --> 00:06:42.260
Speaker 0: so what make building full stack applications and deploying them easier?

00:06:42.360 --> 00:06:45.460
Speaker 0: That was the idea behind The Void framework!

00:06:45.520 --> 00:06:59.000
Speaker 0: And the idea was that you can use with these different frontends view specific or react-specific, but instead the main kicker would be that it's easy to deploy and all these resources are set up for you.

00:06:59.100 --> 00:07:01.900
Speaker 0: And... You can already see a connection there right?

00:07:02.040 --> 00:07:03.840
Speaker 0: It will use Cloudflare under the hood.

00:07:04.240 --> 00:07:14.160
Speaker 0: back then The idea still was To do as product though not part of cloudflare But I guess made sense.

00:07:14.680 --> 00:07:17.560
Speaker 0: Then take next step actually join cloudflere.

00:07:17.780 --> 00:07:19.660
Speaker 0: That is what happened now.

00:07:20.900 --> 00:07:31.020
Speaker 0: The idea here is that Cloudflare is moving quickly towards becoming an infrastructure.

00:07:31.940 --> 00:07:39.240
Speaker 0: provider, a hosting provider that makes it particularly easy to build AI built applications.

00:07:39.320 --> 00:07:42.100
Speaker 0: So you know your got all these AIA agents going around.

00:07:42.140 --> 00:07:50.560
Speaker 0: You've got all this wipe coded apps or these agenting engineered apps and many of these web apps then at some point need To be deployed in.

00:07:50.660 --> 00:07:51.540
Speaker 0: Many of them meet.

00:07:51.880 --> 00:07:58.200
Speaker 0: features like queues Or databases are file systems files storage And cloudflare offers All the services.

00:07:58.280 --> 00:08:33.440
Speaker 0: but In the past and to some degree still right now, you have to wire up all of this stuff manually so that Experience also that agent ready deployment experience where you got an agent build a web application for, probably with your input or maybe also entirely wipe coded and then.

00:08:33.620 --> 00:08:41.220
Speaker 0: You give the agent Also as CLI which is very agent friendly to use get lots of explanations in there Which the agent can than used too?

00:08:41.679 --> 00:08:43.340
Speaker 0: quickly deployed to the cloud.

00:08:43.539 --> 00:08:51.480
Speaker 0: Cloudflare wants to become a provider for these kinds of applications and they plan on building it all on top of Veet!

00:08:51.940 --> 00:09:02.680
Speaker 0: So in the official Cloudflayer blog post, they talk about this mission more, show some impressive numbers about their Veet plugin which existed before that deal.

00:09:04.480 --> 00:09:17.800
Speaker 0: because AI agents use Veet as the established standard JavaScript ecosystem build tool, bundler whatever you want to call it and cloudflare is pretty popular amongst agents already.

00:09:18.160 --> 00:09:20.600
Speaker 0: so they got a pretty strong adoption for that weed plug-in.

00:09:20.760 --> 00:09:45.140
Speaker 0: They now wanna take the next level so that your agents, of course also you but the main idea is your agents can use that tool to quickly build full stack applications and then also easily deploy them.

00:09:45.180 --> 00:09:47.800
Speaker 0: And all these resources are provisioned for you behind-the-scenes.

00:09:48.240 --> 00:10:00.280
Speaker 0: So kind of going back to that vision off The Void framework But now agent first and fully integrated with Cloudflare With the official cloudflare support Also monetary support Of course.

00:10:02.040 --> 00:10:03.340
Speaker 0: what's going to happen there.

00:10:03.560 --> 00:10:21.580
Speaker 0: Now, the good news of course for us developers is that the features that already make wheat great all these different tools I mentioned before for formatic linting and wheat itself That all benefits this cloudflare future vision too.

00:10:22.000 --> 00:10:40.120
Speaker 0: And therefore, as mentioned initially I have no doubt that it will stay open and you'll be able to use with other vendors also because there is no way around VIT right now especially since these agents has strong opinions on which tools they want used by default – which matters for wipecoded apps of course!

00:10:44.360 --> 00:10:50.300
Speaker 0: hosting providers, pushing towards that age and first easy deployment vision.

00:10:50.620 --> 00:10:57.220
Speaker 0: And they will probably also embrace VIT for that or at least the chances are pretty high for that I would say.

00:10:57.400 --> 00:11:01.740
Speaker 0: but of course Cloudflare now got kind of priority access you could say!

00:11:02.000 --> 00:11:17.380
Speaker 0: Of course ALSA as mentioned initially can influence the roadmap a bit to make sure this own CLI This cloud layer CLI, which I mentioned that this really works well together with the beat under the hood.

00:11:17.440 --> 00:11:20.920
Speaker 0: So to say anyways That's the plan there.

00:11:21.100 --> 00:11:25.520
Speaker 0: that are some interesting changes and i also want To make it very clear.

00:11:25.620 --> 00:11:33.740
Speaker 0: not just that i have no doubts about Beat staying open sourcing so on And uh...i don't see that as a negative thing at all.

00:11:33.860 --> 00:11:43.280
Speaker 0: instead It's crucial That open source maintainers can make a living off that, earn money and continue working on the tools we use every day.

00:11:43.860 --> 00:11:53.940
Speaker 0: And it's not something to frown or see as bad things because ultimately like you everybody needs to make money.

00:11:55.080 --> 00:12:09.500
Speaker 0: so I think its great for popular projects being backed by companies even if they then influence their development a bit, as long it's not totally shifting away from being flexible open ecosystem.

00:12:13.260 --> 00:12:16.480
Speaker 0: But of course let me know what you think about this deal!