r/javascript • u/manniL • Jun 04 '26

VoidZero is Joining Cloudflare

https://voidzero.dev/posts/voidzero-cloudflare
137 Upvotes

97% Upvoted

37 comments sorted by

11

u/ProCodeSoftware Jun 04 '26

I don't really like acquisitions because after a company buys something, they usually make it worse. I love Vite, and I don't want it turning into an AI service I don't want.

But this is a BIG SLAP to the triangle company!!

5

u/manniL Jun 04 '26

That’s why everywhere is clearly Written: Vite will stay open source and vendor neutral

6

u/kitkatas Jun 04 '26

But what's the point of buying it then

2

u/manniL Jun 06 '26

There is more in VoidZero than just the OSS projects

2

u/ProCodeSoftware Jun 04 '26

Does that still mean "well-maintained"?

2

u/manniL Jun 06 '26

Yeah, CF puts 1M$ in a Vite ecosystem fund. That + having some of the maintainers on the payroll should help

10

u/captain_obvious_here void(null) Jun 04 '26 edited Jun 04 '26

That's honestly a move that I didn't expect, from the Vue team. I can't say if it's good or bad.

I have nothing against Cloudflare, I just hope they don't fuck things up, as the Vue stack Vue ecosystem is something I really don't want to move away from anytime soon.

12

u/manniL Jun 04 '26

Vue !== void. Vue is independent

6

u/captain_obvious_here void(null) Jun 04 '26

Meant to say "the Vue ecosystem".

25

u/jessepence Jun 04 '26 edited Jun 04 '26

First Astro, now this? Cloudflare is getting all the good JS talent.

The monetization story never really made sense to me. It seems really hard to carve out a space in the managed hosting world. Are the Vercel and Laravel teams the only ones who are able to make Private Equity work?

2

u/theguymatter Jun 05 '26

Feels less like managed hosting competition and more like Cloudflare building the runtime layer under it. Different game, different economics.

1

u/SolidOdd4889 25d ago

cloudflare is trying to do the usual vendor lock-in strategy, with astro for example you basically have to rewrite everything for cf since it doesnt support standard nodejs utilities

17

u/kitsunekyo Jun 04 '26

i trust this team to make the right choice more than any other. so no notes from me

2

u/kitkatas Jun 06 '26

Business intentions might be completely different

3

u/RevolutionaryPen4661 Jun 04 '26

Some guy on X suggested that Cloudflare should acquire TanStack too.

7

u/mrgrafix Jun 04 '26

Probably working on it, but Tanner probably doesn’t need it, yet.

2

u/HelloXhale Jun 04 '26

Cloudflare is already a big sponsor / partner of tanstack as far as I’m aware

1

u/boneskull Jun 06 '26

developer-tooling-to-sales-funnel pipeline strikes again

2

u/Salkinator Jun 04 '26

Ugh... please I beg all tech founders: don't just go for the exit. Build something that can endure. We need more competition, not less!

7

u/Charuru Jun 04 '26

easier said than done? like how though? monetizing open source often just means enshittification so if they can monetize some other unrelated business but support their work as a pure cost center that's a better outcome imo

1

u/ultrathink-art Jun 05 '26

Worth watching what this means for Rolldown and Vite's neutrality long-term. Evan You positioned VoidZero as infrastructure for the whole ecosystem specifically to avoid one company controlling the toolchain. Cloudflare has obvious incentives to optimize for Workers and Pages — if Vite starts shipping defaults that favor edge deployment, that's not necessarily bad but it changes what 'neutral build tooling' means for teams not on Cloudflare.

1

u/manniL Jun 05 '26

Vite remains vendor-agnostic, applications built with vite are meant to run anywhere.

Source

1

u/SolidOdd4889 25d ago

astro is based on vite, and if you change the adapter to cloudflare you also need to rewrite your codebase unless it’s a simple static site with no logic, so definitely not vendor agnostic

1

u/manniL 25d ago

That is not a Vite issue though but based on how Astro works.

Nuxt is also based on Vite can do it all zero config

1

u/SolidOdd4889 25d ago

same problem with nuxt, you can’t use nodejs or bun utilities/packages, you have to rewrite everything

1

u/manniL 25d ago

Well, if you want to migrate away from a database/library/... then usually yes, you have to change the code for these specific features.

Same for Bun. That does not change that Vite is vendor agnostic.

If you build a Vite application you can deploy it anywhere by default. If you make choices on your own to change that, like locking into Bun for example, that is not Vite's fault.

1

u/SolidOdd4889 25d ago

i’ve never had to change a single thing across railway, fly.io, vercel, netlify and the other mainstream platforms…

1

u/manniL 25d ago

Okay, so this speaks for Vite then. Not sure I get your point here?

1

u/SolidOdd4889 25d ago

the point is that cloudflare is trying the usual vendor lock-in strategy

1

u/manniL 25d ago

And how do they do that in your opinion?

Nothing changed about Vite (or Astro) since these acquisitions that "favors Cloudflare". And I don't think it will, otherwise CF would lose a big chunk of reputation in the dev community

0

u/boneskull Jun 06 '26

until corporate decides differently, of course.

1

u/yolomoonie Jun 07 '26

True, but Cloudflare workers are open source. Basically any hosting provider could implement a "Cloudflare compatible" hosting.

0

u/egorf Jun 04 '26

A great day for the team and a truly sad day for the rest of the developers community.

I certainly hope that a new package builder will emerge once vite fades.

0

u/manniL Jun 05 '26

Why would you assume that Vite goes anywhere?

-6

u/[deleted] Jun 05 '26

[deleted]