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

321–330 of 383 posts

Re: Vite – Next Generation Front End Tooling

#321

Post by jollybean »

hardwaregeek wrote: post #118
darkest_ruby wrote: post #63

Despite all negative comments, I (and my team) switched to vite for create-react-app about two months ago, and never looked back. Builds take seconds, developer experience is amazing.a.m.a.

You may notice that all of the negative comments are around superficial nitpicking of the website copy or general bemoaning of the state of front end development. The first is sort of useful in a minor way; the second is pretty useless and generally tired. Vite is a great tool that I’d recommend for anyone who wants to speed up their front end build setup.

It's not superficial or nitpicking, it's just not directly related to the quality of the product.

We're now firmly in the age of complexity and thousands of new tools and projects - it's important that people provide a very simple introduction/overview to 'what something is'.

That said, I agree, it's not hugely helpful to have all our discussion be about that.

Re: Vite – Next Generation Front End Tooling

#322

Post by mikewhy »

monkey_monkey wrote: post #305
mikewhy wrote: post #277

Earlier quoted context omitted.

"all this monoliths->microservices are really achieving is finding slightly different ways of doing the same thing" "all this python->go are really achieving is finding slightly different ways of doing the same thing" "all this relational db->document stores are really achieving is finding slightly different ways of doing the same thing"

Once again, we both know those aren't even close to being the same. Your attempts at snidey mimicry just expose the poverty of the point you think you're making.

Awwww but you're so close to getting the point. Hopefully one day.

Re: Vite – Next Generation Front End Tooling

#323

Post by cercatrova »

martpie wrote: post #316
cercatrova wrote: post #197

Earlier quoted context omitted.

Yes, and that's the main reason why I like it. You can do advanced UIs and animations that would otherwise be very annoying in other frameworks like React Native. Plus, a canvas makes it easy to port to other platforms like desktop and web because all you need is the ability to draw pixels on a screen.

Until a blind person contacts your support team to tell them your website/webapp is not working with their screen reader.

Flutter has accessibility FYI. It creates a parallel accessibility tree in the DOM that screen readers can read.

https://docs.flutter.dev/development/accessibility-and-local...

Re: Vite – Next Generation Front End Tooling

#324

Post by denkmoon »

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…

Over the last few years I've noticed a new heuristic I use for determining if something is good/worth investigating or not; Can I tell what it is within 60 seconds of looking at its website.

Re: Vite – Next Generation Front End Tooling

#325

Post by systemvoltage »

mikewhy wrote: post #275
systemvoltage wrote: post #198

Earlier quoted context omitted.

> It takes more time to type all that negativity Well, good criticism is not negativity, but I'd argue it is positivity.

I'm not seeing a lot of "good criticisms" here. Just the typical HN curmudgeons complaining about things that were introduced half a decade ago being too new.

That seems pretty new actually.

Re: Vite – Next Generation Front End Tooling

#326

Post by toddmorey »

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…

Credit to them for a nice "Why Vite" button backed by a very informative page.

But for any homepage describing any product / project: If you solve a similar problem as a better know competitor, that's a huge advantage! Mention them explicitly and then state what makes you different. That's one of the fastest avenues to understanding anything "it's like [well known thing] but different in that it [differences here]".

Perhaps just having this:

Vite is a javascript bundler for web development that uses native ES modules. Projects are adopting Vite in lieu of Webpack to gain near-instant HMR and much simpler setup and configuration.

Re: Vite – Next Generation Front End Tooling

#327

Post by LAC-Tech »

So I just streamed myself taking vite for a test drive. My thoughts:

- Very fast to reload

- Seemed pretty damn simple and non-magical. Your main code doesn't get transpiled, just your dependencies.

- IMHO the scaffolding stuff was superfluous, at least for vanilla JS. I'm a minimalist and it initially turned me off, but then I discovered it was basically just a thin wrapper around the `vite` binary. Will probably just install vite as a dev dependency and go from there next time.

Over all a positive experience and might end up re-using it.

Re: Vite – Next Generation Front End Tooling

#328

Post by brailsafe »

porker wrote: post #61
jbrooksuk wrote: post #14

We (Laravel) have just switched the frontend tooling from Laravel Mix (a webpack wrapper) for Vite. https://laravel.com/docs/9.x/vite#main-content The speed gains are super impressive from Vite.

Interesting you've made the change. Does that mean that Vite source maps for TS/JS and CSS are now up to scratch?

Were they not before?

Re: Vite – Next Generation Front End Tooling

#329

Post by brailsafe »

ta-run wrote: post #235
darkest_ruby wrote: post #63

Despite all negative comments, I (and my team) switched to vite for create-react-app about two months ago, and never looked back. Builds take seconds, developer experience is amazing.a.m.a.

Not CRA related, but is it as simple to move an existing Vue2 project to Vite?

I think it depends, and it's just worth trying. My opinion from a cursory test is that it should be easy to migrate for local dev purposes if you have a single entry point for an app that us essentially one or a series of component trees.

The app I work on deoends on an angularjs bootstrapping process, and does some other things that are sort of webpack specific, so we'd need to refactor some bits first.

Vue2 should be pretty easy, at least to see the speed improvements locally which is its main pitch afaik

Re: Vite – Next Generation Front End Tooling

#330

Post by noduerme »

cercatrova wrote: post #323
martpie wrote: post #316

Earlier quoted context omitted.

Until a blind person contacts your support team to tell them your website/webapp is not working with their screen reader.

Flutter has accessibility FYI. It creates a parallel accessibility tree in the DOM that screen readers can read. https://docs.flutter.dev/development/accessibility-and-local...

hah. I remember having to build HTML-only fallback versions of fancy Flash UI sites back in... 2002 to around 2008. We marketed this as an add-on for improved SEO. Allegedly Google used to manually check if the content matched what was in the Flash version and knock you down if it wasn't. That was probably just a rumor.
Post reply on HN