[demetris]

I love Vite, when I don’t forget it exists in my projects. It took things that made you feel mentally deficient and made them almost zero-config.

This news does not make me happy.

Same with the news about Astro earlier this year.

I know it must be good for the people how have made the projects (why else would they chose to do it?) but there is something in those acquisitions that makes me uneasy.

[embedding-shape]

> I know it must be good for the people how have made the projects (why else would they chose to do it?) but there is something in those acquisitions that makes me uneasy.

Same, kind of conflicting. Happy for the individuals involved, they've probably more than earned it. Slightly sad about what comes next, as I'm guessing both you and me seen this happen so many times before, and we've learned to read past the always-reiterated "Nothing will change, everything keeps on being great forever".

[nobleach]

I've loved Vite from the moment it was public. I also tried Snowpack back in the day. (fun story that Fred "fks" went on to create Astro after Snowpack didn't gain traction). The fact that we can "just forget it exists" is a major win in my case. Webpack - while maybe a win over Grunt/Gulp, was MASSIVELY complex.

I too am a bit uneasy. It's not always the case but, corporate ingestion is often where cool projects go to die. The good news about open source is that we have enough Terraform->OpenTofu & Redis->Valkey stories out there.

[pier25]

> Webpack - while maybe a win over Grunt/Gulp, was MASSIVELY complex.

and slow

[abustamam]

Having used Webpack since 2016... Vite was amazing. Few years ago I migrated a rather complex project (monorepo with a Rust wasm binding) from Webpack to Vite (before the LLM days!) and dev builds and real builds went from minutes to seconds. I never looked twice at Webpack ever again.

I don't know what to feel about this news, especially since migrating to from vite 7 to vite 8 broke my project in ways that were not documented, but I'm remaining cautiously optimistic.

Happy for Evan regardless.

[avdwrks]

This one is particularly interesting given that Vercel products (Nuxt) now rely on a competitor's tooling (Vite).

[Mitochondriac]

Next* the framework for React. Nuxt is the framework for Vue.

[brennopost]

Nuxt is also on Vercel

https://vercel.com/blog/nuxtlabs-joins-vercel

[ZiiS]

Both are more reliant on V8 derivatives hence Google which they very much compete with.

[trollbridge]

Yeah. I don't want to sound selfish, but now I need to make plans to eventually migrate off of vite.

[adzm]

Migrate off vite to what exactly? I just migrated a personal project to vite and it simplified the existing webpack thing drastically, I was very impressed.

[shimman]

IDK, I've been purposely limiting the scope of work I can provide by only working with js, html, css. It's extremely limiting but when it comes to basically making one-off splash pages it's nice to not worry about tooling and just deploy what I made instantly. Modern CSS is amazing, there's no need to use sass or postcss. The modern web APIs are amazing as well. You can get a lot done with new base standard across browsers. The only libraries I really pull in nowadays are anime.js + umami for analytics.

I don't even need TS and can get away with js doc annotations + a functional LSP allows me to be slightly more dangerous (think running with scissors in chain mail).

Maybe if you need a specific web app you can reach for the complex tooling but even then I still wonder if it's necessary? The most popular political tool I've shared was a simple HTML page that just fetched the census API for specific codes in a tabular format. Sure I could have used react which would have enabled me to unlock some future value I couldn't foresee at the time but the working alternative is that I have a single html page with minimal JS (around ~2k LOC) that a surprising amount of nontypical devs (think carpenter that is interested in cybersecurity or union negotiators) are able to extend by themselves for their own needs (think adding census codes about snap or public transit).

There is a tremendous amount of value in telling my users how they can modify the source code and see the immediate impact of doing as much.

If this was a project that would have necessitated vite the first thing I would tell them is to install nodeJS and that's where I would lose 99.9999999999% of my users being able.

These projects will never go beyond 500,000 visitors and a CDN is more than sufficient for 90% of the work I do. So that obviously plays a major role but if this is a solo project there are much better choices to make if you want it to be sustainable + low upkeep. Those two qualities are something we as an industry should always value as it makes all our jobs collectively easier.

[bossyTeacher]

> This news does not make me happy.

It shouldn't. Big corpo buying small companies harms us all long term.

[ericyd]

What alternative ending do you prefer? Personally I think acquisition is preferable to dev burnout due to lack of funding and/or extractive practices from other companies.

[chrisandchris]

Last time I checked, VueJs was "quite ok funded" [1]. Sure it's no FAANG income, but it will get you quite far in most parts of this world.

[1] https://opencollective.com/vuejs

[ambicapter]

> It took things that made you feel mentally deficient and made them almost zero-config.

What kind of things?

[chrisweekly]

I'm not the one you replied to, but a typical config & plugins stack for (webpack + eslint + prettier) is nearly impossible to reason about. VoidZero's tools (Vite + oxcfmt + oxclint) are radically simpler and more performant.

[azangru]

> a typical config & plugins stack for (webpack + eslint + prettier) is nearly impossible to reason about.

I think people just don't want to bother. They don't want to read the docs, or maybe watch a video or two (back when webpack was popular, Sean Larkin, webpack evangelist, made a number of popular courses about setting it up). Also, webpack config became easier compared to 2014/2015; I think they got to practically a zero-config by default.

I can understand that people don't want to care; but "impossible to reason about" is not it. It isn't rust, for crying out loud; nor lisp; nor haskell.

[demetris]

What chrisweekly said:

Configuring webpack, mostly. :-D

That’s not a dig at webpack: Those tools are super complex, and hiding complexity from the user is not easy. But it seems that with Vite we finally got there.