TheAlexLichter

That did happen! https://github.com/oxc-project/oxc-css-parser/issues/92#issu...

I am using Vite+ for CLIs as well, yes. You don't use Vite as dev server then but lint, format, task running and caching is still there!

Not really. The claim is that nothing will change regarding the OSS projects.

Vite is a multi stakeholder team. How would that happen?

IMO perfect for Vue (and similar for Vite). All the talented folks working together.

Just use Vite Plus (viteplus.dev)

1) The blog post mentions "acquisition" multiple times. 2) VoidZero joins Cloudflare is still correct. Nobody forced anyone to accept a deal and do so

Vite 8 is in beta, so you can try it out already. See https://voidzero.dev/posts/announcing-vite-8-beta

Rolldown is in RC, meaning no more breaking changes (except for experimental features). See https://voidzero.dev/posts/announcing-rolldown-rc

There will be more

I personally met a lot of folks who care about both quite a bit.

But to be fair, besides the usual patterns like tree-shaking and DCE, "runtime performance" is really tricky to measure or optimize for

For a couple of reasons:

* You need have a clean architecture, so starting "almost from scratch" * Knowledge about performance (for Rust and for build tools in general) is necessary * Enough reason to do so, lack of perf in competition and users feeling friction * Time and money (still have to pay bills, right?)

Love that fact that you don't need anything ts-node/tsx like if you have erasable syntax only. Other than that, there is https://github.com/oxc-project/oxc-node too.

As said in another comment: Curious to see what you are coming up! Talk is cheap

> That still leaves you admitting that only a small fraction of the served community can really contribute.

Not really (see above).

> You'll need to keep all the best benefits of your work for the Plus users or else there would be no reason to buy Plus and no way to keep paying the few to do all the work for the many.

No, won't happen that way.

> You're stuck telling people what they can't have (and shouldn't want) while I'm now in a position to just give people what they want.

Didn't see any software of yours yet, only big talk so far sadly! Besides that, VoidZero will also be in a position to just give people what they want

That is correct, every rule with a custom parser (e.g. vue/svelte/astro tempaltes) and also type-aware rules can't be used as JS plugin.

Type-aware rule are indeed not marked as stable but work like a charm. tsgolint is indeed tsgo + shims + some works, but that won't change soon as tsgo won't have a JS API for a while.

Not really.

1) This is not what I said, no

2) With AI, languages and syntax matters even less nowadays.

3) There have been a good amount of contributors (e.g. for Oxc) that came out the JS world, so it isn't impossible

4) Realistically, the avg. web dev does not contribute to tooling internals, maximum custom rules or similar. The concepts are a bigger "hurdle" than the lang.

Yeah, no. Real human here.

Oxlint does support core rules out of the box but has support for JS plugins[0] as mentioned. If you don't rely on a custom parser (so svelte or vue component for example) things just work. Even react compiler rules[1].

[0] https://oxc.rs/docs/guide/usage/linter/js-plugins.html [1] https://github.com/TheAlexLichter/oxlint-react-compiler-rule...

The good part is that the new tools do replace the old ones, while being compatible. The pattern is:

* Rolldown is compatible to Rollup's API and can use most Rollup plugins

* Oxlint supports JS plugins and is ESLint compatibel (can run ESLint rules easily)

* Oxfmt plans to support Prettier plugins, in turn using the power of the ecosystem

* and so on...

So you get better performance and can still work with your favorite plugins and extend tools "as before".

Regarding the "mix of technology" or tooling fatigue: I get that. We have to install a lot of tools, even for a simple application. This is where Vite+[0] will shine, bringing the modern and powerful tools together, making them even easier to adopt and reducing the divide in the ecosystem.

[0] https://viteplus.dev/

Mentioning SWC and ESBuild but missing Rolldown (https://rolldown.rs/) here seems like a miss.

Take a look at workspace mode for that! See e.g. https://github.com/vue-macros/vue-macros/blob/main/tsdown.co... for reference.

Good point! Will improve this.

Think of it as in opinionated Rolldown-"preset" for libraries. It will be used as the foundation of Vite's lib mode revamp.

Appreciate that! Prices and details will be known closer to launch, so stay tuned

Consulting doesn't scale though and draws resources from development itself, harming both the OSS and the business side.

All functionality as part of OSS projects will stay there. OSS projects such as Vite, Vitest, Rolldown and Oxc will stay open source.

Eventually, the (financial) success of Vite+ is directly tied to the health, stability, and adoption of the free, open-source Vite ecosystem, so the incentive is rather low.

Take a look at the formatter RFC https://github.com/oxc-project/oxc/discussions/13608

+ Adding a task runner with fine-grained caching (which isn't open source). All in a single dependency.

And that is on purpose!

Selling access isn't really helpful there. The target group (companies) have to care about licenses at some point, while it will be free for OSS, individuals and the community.