5 ms·

Interesting, I am a heavy user of vite today and the featureset is interesting but I don't really understand how it will differ from "normal" vite and why I wou

Interesting, I am a heavy user of vite today and the featureset is interesting but I don't really understand how it will differ from "normal" vite and why I would pay for it.

rk06 1y ago
On twitter, they said that there will be an announcement on monday. so we will find out then. previously (i.e. before current viteconf), Evan had said that existing OSS (vite and below) will remain OSS. only newer tooling will be monetised
- staticelf 1y ago
  Well sure, but will there be incentives to keep developing and improving vite? Since they will probably want to have subscribers they will have to do a rug pull and make vite less great than they could've since that is how every saas works.
- manniL 1y ago
  Yes, existing tools are MIT and will stay MIT. Nothing changed thre.
Muromec 1y ago
I was on the conference where it was announced. They plan to finish rewriting all the eslint/tsc/prettier/bundler/nx/minifier stuff in rust and give it single config instead of all of those tools having its own ast parser, alias rules and 5 incompatible babel versions. If anything, FE tooling starts looking like it moves to more sane place. Also Anthony Fu is cool
- staticelf 1y ago
  Yes but is it worth paying a monthly subscription in order to avoid some config files? I donno. Then you will have the problem in if things go wrong or if you do something very different it's closed source so it won't be easily fixed or prioritized since there is no community.
  - Muromec 1y ago
    I dunno really. I'm pretty sure my organization will be willing to cough up the fee. Me personally -- I would rather see it staying fully opensource and be funded through open collective or EU grants or something, like a lot of core stuff should. The fact this model doesn't work is sad. I feel that something that the whole FE community gravitates to converge on should stay that way to prevent rag pulls and license dramas, otherwise it sabotages the process of converging on the same set of tools in the first place. Then the whole work will be wasted and eventually the project will die out and we get back to the same mess. That being said, I get that the problem they are aiming to solve is a big pain point and whoever solves it -- they deserve money, but don't deserve to keep the whole community hostage to their whims indefinitely. Then again, if people can pay 20 bucks a month for oracle lottery tickets selling infinite wisdom one token at time, why not pay actually helpful people doing great tools.
  - array_key_first 1y ago
    I think for a company the answer is yes, definitely. A monthly subscription is nothing next to a salary. Not that this will eliminate a whole engineer but... It might. It'll get close, depending on how big the project is.
TiredOfLife 1y ago
It's simple. Use Vite and want bugfixes - pay.
- yencabulator 1y ago
  Translation: Stop using Vite before it's too late. This is not good news.

Interesting, I am a heavy user of vite today and the featureset is interesting but I don't really understand how it will differ from "normal" vite and why I would pay for it.

rk06 1y ago

On twitter, they said that there will be an announcement on monday. so we will find out then. previously (i.e. before current viteconf), Evan had said that existing OSS (vite and below) will remain OSS. only newer tooling will be monetised

staticelf 1y ago
Well sure, but will there be incentives to keep developing and improving vite? Since they will probably want to have subscribers they will have to do a rug pull and make vite less great than they could've since that is how every saas works.
manniL 1y ago
Yes, existing tools are MIT and will stay MIT. Nothing changed thre.

Muromec 1y ago

I was on the conference where it was announced. They plan to finish rewriting all the eslint/tsc/prettier/bundler/nx/minifier stuff in rust and give it single config instead of all of those tools having its own ast parser, alias rules and 5 incompatible babel versions. If anything, FE tooling starts looking like it moves to more sane place. Also Anthony Fu is cool

staticelf 1y ago
Yes but is it worth paying a monthly subscription in order to avoid some config files? I donno. Then you will have the problem in if things go wrong or if you do something very different it's closed source so it won't be easily fixed or prioritized since there is no community.
- Muromec 1y ago
  I dunno really. I'm pretty sure my organization will be willing to cough up the fee. Me personally -- I would rather see it staying fully opensource and be funded through open collective or EU grants or something, like a lot of core stuff should. The fact this model doesn't work is sad. I feel that something that the whole FE community gravitates to converge on should stay that way to prevent rag pulls and license dramas, otherwise it sabotages the process of converging on the same set of tools in the first place. Then the whole work will be wasted and eventually the project will die out and we get back to the same mess. That being said, I get that the problem they are aiming to solve is a big pain point and whoever solves it -- they deserve money, but don't deserve to keep the whole community hostage to their whims indefinitely. Then again, if people can pay 20 bucks a month for oracle lottery tickets selling infinite wisdom one token at time, why not pay actually helpful people doing great tools.
- array_key_first 1y ago
  I think for a company the answer is yes, definitely. A monthly subscription is nothing next to a salary. Not that this will eliminate a whole engineer but... It might. It'll get close, depending on how big the project is.

TiredOfLife 1y ago

It's simple. Use Vite and want bugfixes - pay.

yencabulator 1y ago
Translation: Stop using Vite before it's too late. This is not good news.