Live data from Hacker News

Vite+ – Unified toolchain for the web

viteplus.dev

111–120 of 151 posts

Re: Vite+ – Unified toolchain for the web

#113
post #109
post #99

Earlier 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

Rome was going to be a whole toolchain built completely in Javascript. That was why they started with linting and formatting because they first had to implement the Javascript language parser and AST that was going to be the core of Rome. Linting and formatting was two easy things to start with while the ironed out the parser and AST implementation.

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

#114

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.

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

Translation: Stop using Vite before it's too late.

This is not good news.

Re: Vite+ – Unified toolchain for the web

#116
post #78

Earlier 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.

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.

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.

Vite works fairly well. Most config for other tools can (should?) be left at the defaults. Jest is falling apart but Vitest works very well. We've come a long way. Now let's freeze the web for some years!

Re: Vite+ – Unified toolchain for the web

#119
post #118

Two 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.

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...

Re: Vite+ – Unified toolchain for the web

#120
post #118

Earlier 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...

Oh my… thanks for the research and sorry for my lazy assumption!
Post reply on HN