Vite: The Documentary https://www.youtube.com/watch?v=bmWQqAKLgT4
Vite+ – Unified toolchain for the web
111–120 of 151 posts
Re: Vite+ – Unified toolchain for the web
#112Interesting, 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.
Re: Vite+ – Unified toolchain for the web
#113Earlier quoted context omitted.
Sure, but a large part of why they never managed to produce anything useful is because SWC/ESBuild basically made the whole Rome architecture obsolete and killed all momentum around the project before they got anywhere.
what has SWC has to do with thier success or failure for Rome? Rome was VC funded, afaik, turbopack still persists despite it being effectively obsolete with vite
But when SWC/Esbuild came around to prove how much faster and efficient the compilation can be when written in a more performant language like Rust or Go, all hype around Rome died because no one wanted another Javascript toolchain.
Turbopack is backed by Vercel who obviously have a lot more capital behind them, but it's also built on Rust and at least has the potential to compete.
Re: Vite+ – Unified toolchain for the web
#114Interesting, 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.
It's simple. Use Vite and want bugfixes - pay.
This is not good news.
Re: Vite+ – Unified toolchain for the web
#1151. This is a Vite rugpull, right?
2. What the hell do I migrate to to avoid the rugpull, now?
Lots of stuff builds on top of Vite, and this is an incredibly bad move from the Vite people.
Re: Vite+ – Unified toolchain for the web
#116Earlier quoted context omitted.
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
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.
Re: Vite+ – Unified toolchain for the web
#117> Built for growing teams tired of configuring, patching, and replacing their JavaScript tooling stack. Ah, great, another Javascript tooling stack! Let's jump on board! I'll get straight to configuring, replacing and patching as soon as possible. Or maybe let's just don't. I'm tired, Boss.
Re: Vite+ – Unified toolchain for the web
#118Two questions: 1. This is a Vite rugpull, right? 2. What the hell do I migrate to to avoid the rugpull, now? Lots of stuff builds on top of Vite, and this is an incredibly bad move from the Vite people.
Re: Vite+ – Unified toolchain for the web
#119Two questions: 1. This is a Vite rugpull, right? 2. What the hell do I migrate to to avoid the rugpull, now? Lots of stuff builds on top of Vite, and this is an incredibly bad move from the Vite people.
It‘s not by the vite team.
Voidzero Inc owns the Vite trademark:
https://tsdr.uspto.gov/#caseNumber=98845059&caseSearchType=U...
Re: Vite+ – Unified toolchain for the web
#120Earlier quoted context omitted.
It‘s not by the vite team.
Looks like the same people to me: https://vite.dev/team.html https://voidzero.dev/team Voidzero Inc owns the Vite trademark: https://tsdr.uspto.gov/#caseNumber=98845059&caseSearchType=U...