Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vite+ – Unified toolchain for the web

viteplus.dev

Post reply on HN
Print view View original

141–150 of 151 posts

Re: Vite+ – Unified toolchain for the web

#141

Post by rk06 »

YuukiRey wrote: post #105
Uehreka wrote: post #84

Earlier quoted context omitted.

Greybeard (35) here. When these cynical takes were crafted, Angular, AngularJS, Aurelia, Backbone, Ember, Knockout, React and Vue were all competing for mindshare, with new members joining/leaving that group every month (anyone remember OJ.js and Google FOAM?) being compiled by traceur, 6to5, the Google Closure Compiler and others from (Iced) CoffeeScript, TypeScript, ES6, Atscript, Livescript and Closurescript. We h…

Okay fair point, the various *Scripts predates my entry into the developer workforce somewhat. But just in the repos at work I deal with: yarn, npm, pnpm, bun, NextJS, biome, Prettier, ESlint, Vite, Vitest, Jest, Turbopack and esbuild. At least those are the things I remember right now. They all have their idiosyncracies and issues. They all require learning slightly different configs. Nothing is compatible with anyt…

nextjs and vite don't work together. same with non, pnpm & yarn. if your projects have different set of tools, thn your projects should have a readme file so people can manage working on them

Re: Vite+ – Unified toolchain for the web

#142

Post by rk06 »

yencabulator wrote: post #136
EvanYou wrote: post #135

Earlier quoted context omitted.

Wrong - Vite is not open core, Vite+ is. This differentiation is important because even if a feature benefits Vite+, if it needs to be shipped via Vite then it has to be open source. Companies willing to pay for Vite+ help sustain and improve the open source parts powering it, including Vite. Even if you only use Vite and not Vite+, you’d benefit from the success of Vite+, not the other way around. I don’t really fin…

The line between Vite and Vite+ exists mostly inside your head. From the outside, Vite is the open core and some set of features are only in Vite+. Best of luck with your commercial project. History has not been kind to open core projects.

it is upto vite team to decide between "open source" or "open core". from my perspective, there is no data to say otherwise, so your "from outside" translates to "In my opinion, but I take no responsibilty for it"

Re: Vite+ – Unified toolchain for the web

#143

Post by yencabulator »

rk06 wrote: post #142
yencabulator wrote: post #136

Earlier quoted context omitted.

The line between Vite and Vite+ exists mostly inside your head. From the outside, Vite is the open core and some set of features are only in Vite+. Best of luck with your commercial project. History has not been kind to open core projects.

it is upto vite team to decide between "open source" or "open core". from my perspective, there is no data to say otherwise, so your "from outside" translates to "In my opinion, but I take no responsibilty for it"

No, they don't get to define what those terms mean.

https://en.wikipedia.org/wiki/Open-core_model

Re: Vite+ – Unified toolchain for the web

#144

Post by rk06 »

yencabulator wrote: post #143
rk06 wrote: post #142

Earlier quoted context omitted.

it is upto vite team to decide between "open source" or "open core". from my perspective, there is no data to say otherwise, so your "from outside" translates to "In my opinion, but I take no responsibilty for it"

No, they don't get to define what those terms mean. https://en.wikipedia.org/wiki/Open-core_model

they certainly get to decide which label to pick for their projects (vite and vite+). you should complain if they do not act according to their choosen labels. but there is nothing done at the moment to complain about.

Re: Vite+ – Unified toolchain for the web

#145

Post by watty »

Not shocking, a lot of time goes into making Vite and they need to make money.

One approach is to setup consulting services. Looks like Void Zero's approach is to start building value-add tools and features on top of Vite that are no longer free.

The decision that users must make now is whether it's worth the risk investing in Vite, assuming that more and more functionality will move to the paid tier.

Re: Vite+ – Unified toolchain for the web

#146

Post by TheAlexLichter »

watty wrote: post #145

Not shocking, a lot of time goes into making Vite and they need to make money. One approach is to setup consulting services. Looks like Void Zero's approach is to start building value-add tools and features on top of Vite that are no longer free. The decision that users must make now is whether it's worth the risk investing in Vite, assuming that more and more functionality will move to the paid tier.

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.

Re: Vite+ – Unified toolchain for the web

#147

Post by whstl »

romanovcode wrote: post #138
whstl wrote: post #83

Earlier quoted context omitted.

If I had my way I would still be writing ASP.NET WebForms, but the market decided to move. I don't even know if it still works. Hot take but: it took 20 years for Next.js to catch up to 10% of WebForms offered. But if people want whatever Next.js offers to build their copycat SaaS with shadcn/ui, so who am I to argue.

> if people want You mean many developers want. Actual customers, the ones who pay for your work don't even know what Next.js is and are extremely happy with whatever works. The hard part is to sell the idea that - no, next.js is not the best for your SEO heavy website :)

Actually it’s what founders want, technical and non-technical ones.

I’ve been in situations where a non-technical founder asked me to use Angular just to fit in.

With technology becoming about trends, clueless founders more and more are pushing for certain technologies.

Recruitment and developers just follow.

Re: Vite+ – Unified toolchain for the web

#149

Post by TheAlexLichter »

selectnull wrote: post #148

I belong to the "small business" group and as such I would be entitled to "free" plan. But, I would actually prefer to pay and have the assurance that the team will be here to maintain it. Please list the prices.

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

Re: Vite+ – Unified toolchain for the web

#150

Post by whstl »

collingreen wrote: post #131
whstl wrote: post #125

Earlier quoted context omitted.

No, that's an answer to a cherry-picked reply. It was one package that had a version migration. I don't necessarily agree but I'm trying to move the discussion forward rather than staying at the "it's all shit" lane. And I gave three other examples, and I can give others: React itself has been around for 12 years, leading. Vue has been super stable too. Migrating versions of frameworks is several magnitudes harder th…

I'm not even against you in general but "react for 12 years" is another really bad example with the complete paradigm change from classes to hooks. I even think hooks are better, but I'm not going to sit and tell people their fatigue isn't valid when even your argument is "some of these aren't as bad as babel or webpack".

The paradigm change you mention happened once, it was piggybacked on an existing and very popular concept (functional components), and the previous paradigm was "deprecated" by the community itself.

Sure it would be better if people had gotten it right the first time, but the fatigue problem isn't really due to React.

And my argument isn't that "X is better than Y". It's that the number of new tools showing up is WAY smaller than it was when those complaints started. Today it has become a meme here in HN, often by people outside the frontend community.

Post reply on HN