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

Vite – Next Generation Front End Tooling

main.vitejs.dev

Post reply on HN
Print view View original

171–180 of 383 posts

Re: Vite – Next Generation Front End Tooling

#171

Post by barkingcat »

dzogchen wrote: post #169
barkingcat wrote: post #140

I find it really funny that the word "javascript" doesn't appear anywhere on the entire first landing page. You have to click into "Why Vite" and then about 1/2 way into the first sentence, then you see "javascript" I was wondering "exactly what kind of front end?" C? C++? Swift? iOS front end? some kind of GUI framework? Windows app development? Modern day Javascript web ecosystem is a nightmare.

No it is not a nightmare. It is actually quite pleasant thanks to Vite.

You say that now, but 3 years in the future you'll be posting "Vite destroyed the Javascript ecosystem"

Re: Vite – Next Generation Front End Tooling

#172

Post by romanhn »

bladegash wrote: post #5

Really enjoy working with Vite and it works great with React (many think it’s geared towards Vue, which perhaps it was at one point). Made the switch after some frustrating behavior coming from CRA and having zero flexibility with configuration. As a side note, Vitest is fantastic as well and I highly recommend giving it a try.

Exactly same here. Scaffolded a small project with Create React App. At one point tried to organize all the config files in a subfolder and ran into the problem of CRA literally hardcoding the location. Was annoyed enough to look at alternatives and Vite was a fantastic substitute that not only provided all the configurability I wanted, but also let me remove all kinds of craft from the project (eg random React and ASP.NET proxy files generated by CRA). It was also fast and way leaner than CRA in terms of dependencies. Quite happy with the outcome.

Re: Vite – Next Generation Front End Tooling

#173

Post by unsupp0rted »

BiteCode_dev wrote: post #126
krick wrote: post #46

It gave me a pause to think about how it came that I can never really tell what am I looking at anymore. Forget the HN title, which is stupid — what does this landing page tell me? Well, that it's… next gen, and it apparently can catch up with me, which is not much, since I'm not really catching up with what's going on anyway. Also, that it's "tooling". Like IDE, or framework, or maybe a chainsaw. Can't tell. "Gettin…

Terrible landing page for an otherwise excellent tool. It sets up JS transpiling and bundling for you in an easy way, then provide a server with pretty fast hot reload. This solves 2 problems: - the complicated js project stack is now simple to setup, unlike with webpack - saving and seeing the result of your coding is now almost instant, unlike with CRA It's a joy to use, given that it's from VueJS author, and I hig…

> pretty fast hot reload

An understatement to be sure: you can set VS Code to auto-save every 1 second and that way whatever you type instantly appears via Vite's Hot Reload in your dev browser. No waiting multiple seconds for a recompile.

It's game-changing workflow (for some tasks).

Re: Vite – Next Generation Front End Tooling

#175

Post by konfusinomicon »

smt88 wrote: post #72
konfusinomicon wrote: post #64

Earlier quoted context omitted.

at this point I've come to realize that all you need to know about front end frameworks anymore is that they are not jquery

You are utterly wrong. There's a huge difference between even Next.js and create-react-app, even though they're both based on React. The JS framework space is huge, messy, complex, and endlessly frustrating, but you can't wave that all away just because you can't keep up with it. I can't keep up either, but I do employ people who do, and they recently moved all our build tooling to Vite, which dramatically improved o…

I agree! my comment was in jest and was just poking fun at the madness that is the JS ecosystem and it's often overly complex, and ever growing list of solutions to problems that could be probably be solved with a few lines of jQuery.

in the words of Jack Borrough, Senior JS Developer, "JQuery, what are you, five? We use JJQuery." https://jjquery.io/

Re: Vite – Next Generation Front End Tooling

#176

Post by mrwnmonm »

maigret wrote: post #151
mrwnmonm wrote: post #144

Earlier quoted context omitted.

So, this is not a framework like React, right?

It’s more like Webpack, the software that processes your React code into JavaScript bundles that are optimized for the browser. ie puts together what belongs together, removes the unused code, provides a test server to develop and get instant refresh.

Got it, thanks

Re: Vite – Next Generation Front End Tooling

#177

Post by shepherdjerred »

SCLeo wrote: post #135
BiteCode_dev wrote: post #126

Earlier quoted context omitted.

Terrible landing page for an otherwise excellent tool. It sets up JS transpiling and bundling for you in an easy way, then provide a server with pretty fast hot reload. This solves 2 problems: - the complicated js project stack is now simple to setup, unlike with webpack - saving and seeing the result of your coding is now almost instant, unlike with CRA It's a joy to use, given that it's from VueJS author, and I hig…

I have been using parcel for web development because I thought webpack is very difficult to use. However, for my latest personal project, I tried webpack. To my surprise, I found webpack 5 much simpler to use then I thought it is (significantly easier than make or gradle, the complexity is not even on the same level). Everything pretty much worked out of box now. All I had to do was to copy the starting template for…

Vite is just a few lines, and it’s a much better experience than webpack

Re: Vite – Next Generation Front End Tooling

#178

Post by athammer »

brundolf wrote: post #167
Volundr wrote: post #125

Earlier quoted context omitted.

Isn't it? I use it and it's not clear to me what's incorrect about it.

It's too imprecise: - People might interpret that as "drop-in replacement for webpack", which is definitely not true - Even as just "a replacement for webpack"; Webpack and Vite have a lot of overlap, and it makes sense to compare them, but I think there are too many asterisks and nuances to say they're equivalent, in official materials, unqualified

Rather imprecise then have people confused of what it does - especially when the confusion could be fixed by a sentence.

Just have a hyper link that directions to a comparison page explaining the nuance. Even without the hyperlink I wouldn’t assume people would think it’s a 1:1 clone drop in replacement. People don’t just drop in a new tool without research and comparing it against their new tool.

Re: Vite – Next Generation Front End Tooling

#179

Post by zmxz »

Incredible amount of negative comments. It takes more time to type all that negativity out than it takes to read about what Vite is and what it does.

Frontend dev here. Vite is amazing. It doesn't take long to get what it does if you try it out (you can avoid reading about it that way).

I won't bother summarizing what it does, the website literally covers it. Reading really became superpower in this day and age.

Post reply on HN