Live data from Hacker News

Vite – Next Generation Front End Tooling

main.vitejs.dev

151–160 of 383 posts

Re: Vite – Next Generation Front End Tooling

#151

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…

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.

Re: Vite – Next Generation Front End Tooling

#152
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…

One question .. Is the main goal to make development process easy or does it also have an impact on production performance as well ?

Re: Vite – Next Generation Front End Tooling

#153
post #59

Working with front end for 5+ years have nearly made me switch careers. There's an absolute onslaught of languages, frameworks, patterns and now also "tools" that never really work in you editor, and you never really grasp before moving on to the next thing. I think me and my team have spent 90% of our time working with tooling, and all creativity and joy has gone out the window - because you never become a master, a…

> ...and you never really grasp before moving on to the next thing. Then why do you move on to the next thing? Not a frontend dev, but I notice that a lot of frontend devs seem to be really eager to jump to the next hot thing when it becomes available, even though the thing they are using is still well maintained.

>> even though the thing they are using is still well maintained.

I think you mean "even IF the thing is still maintained". This is a big IF. Something as ubiquitous as a React app may still work fine after a few years, but try updating or fixing something and you're in for a world of hurt.

Re: Vite – Next Generation Front End Tooling

#155

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…

Would this replace parcel or be adjacent to it?

Replace it.

Re: Vite – Next Generation Front End Tooling

#156
post #69

Earlier quoted context omitted.

Devil's Advocate position here. I don't know much about carpentry, and if I look at a website selling saws, I will struggle to understand the difference between different models. Dumbing down to an extent that I understand (when I probably won't buy the product anyway) risks alienating the target market that will. Due to customer demands, end-user requirements, and device fragmentation, front-end development has genu…

This is a good point if we were selling physical goods and limited by the amount of information we can convey on a screen but we aren't. I'd honestly include things like the what and why as critical to documentation. Most libraries, tools, and tech in general are bad at documentation. It's an active choice to omit discussing these things when they should obviously be included but writing good copy is hard. IDK seems…

Different way of thinking about this - maybe the devs aren't even the target user of the homepage. If the first time a front end dev hears of Vite is via the homepage, their marketing has a problem. (I first heard of Vite maybe 18 months ago in a discussion on the upcoming Nuxt v3.)

Instead, this homepage is trying to convince some CxO this is a serious tool worth adopting.

Either way, I'd assume there's a good reason you find the homepages of so many popular projects homepages rather vacuous. I doubt it's incompetence.

Re: Vite – Next Generation Front End Tooling

#157
post #2

The constant iteration and revolution of basic front-end web dev makes me happy to be a mobile dev.

Are you sticking with the tired old 2019 tech, or have you rewritten everything with Kotlin, Compose, Swift, and SwiftUI?

We're still writing iOS apps in Objective-C(++).

Re: Vite – Next Generation Front End Tooling

#158
post #17

Earlier quoted context omitted.

Yeah, and it's a pleasure to use. Really the only issue I ran into was not realising SvelteKit doesn't support all Svelte functionalities, and you have to vet plugins at times.

Could you elaborate on which functionality? I've been using SK in production since early beta, I've not run into this (yet)

To be honest I'm not a front end developer, just learned that a few things on GitHub had issues outstanding about SK issues, and avoided them after the first run-in. Massive props to Svelte to allow me to finish my project while actually, somehow, enjoying the front end development portions though!

The one I ran into: https://github.com/BulatDashiev/svelte-slider

Re: Vite – Next Generation Front End Tooling

#159

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…

One question .. Is the main goal to make development process easy or does it also have an impact on production performance as well ?

It’s mainly for dev rebuild performance. I also use vite and it’s a pretty nice build tool that’s relatively easy to configure and quite fast.

It might also affect your production build times, but prod builds are far less frequent and performance isn’t important here

Re: Vite – Next Generation Front End Tooling

#160

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…

One question .. Is the main goal to make development process easy or does it also have an impact on production performance as well ?

From https://main.vitejs.dev/guide/

"Vite (French word for "quick", pronounced /vit/, like "veet") is a build tool that aims to provide a faster and leaner development experience for modern web projects."

Ultimately it makes the dev process more productive because builds are generally much faster than most other build tools.

https://main.vitejs.dev/guide/why.html might also be worth a read

Post reply on HN