Live data from Hacker News

Vite – Next Generation Front End Tooling

main.vitejs.dev

311–320 of 383 posts

Re: Vite – Next Generation Front End Tooling

#311
post #298

Earlier quoted context omitted.

All this make->ant->maven->gradle->'the inevitable replacement for gradle' are really achieving is finding slightly different ways of doing the same thing.

I'm glad you agree with me.

As another commenter pointed out [1], backend "reinventions" don't seem to receive the same criticisms, so in general there really does seem to be a double standard

[1]: https://news.ycombinator.com/item?id=31970112

Re: Vite – Next Generation Front End Tooling

#312

Earlier quoted context omitted.

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.

How would one use it together with a backend that already serves the frontend code? As a compiler only?

I don't think Webpack is designed for that use case, it is pretty apples and oranges

Re: Vite – Next Generation Front End Tooling

#313
post #179

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.

> to read about what Vite is and what it does.

This is actually my main complaint. I read everything on the landing page and Getting Started page and still have literally zero idea what Vite does.

Re: Vite – Next Generation Front End Tooling

#314

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

An 80% true statement that sets the tone followed by a deeper explanation is fine. What is currently there tells us 0% about what Vite does.

Re: Vite – Next Generation Front End Tooling

#315

Earlier quoted context omitted.

I think is more of an indictment on the javascript ecosystem generally, because there's so much more to building an app that runs JS than just your standard MVC/MVVM/pick-your-pattern web frameworks. You have to deal with various layers of transpilation on your JS, styles and assets and that all needs to be flexible enough to fit a wide set of use cases for the community. It's gotten to the point you need to be an ex…

I see the same issue with libraries and frameworks in any language. For example, I came across Dark Lang [1] yesterday, and the front page is similarly cryptic if you aren't familiar with back end work. [1]: https://darklang.com/

Hilariously I came across that one as well as a good 'WTF' example.

That said - I feel for some of these dudes just wanting to make a framework, struggling a bit with the 'communication' part.

Re: Vite – Next Generation Front End Tooling

#316

Earlier quoted context omitted.

Does Flutter still render everything in a canvas? This has been a huge turn off for me.

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.

Re: Vite – Next Generation Front End Tooling

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

The first sentence of the "Getting started" page tells you the following: > 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. But of course it's easier to keep ranting and ignore the second part of the sentence you referenced because it doesn't match your narrative.

That's still very generic so as to be almost no information.

Imagine if python's homepage had no code samples at all, and the getting started page said "Python is a programming language for high productivity".

Re: Vite – Next Generation Front End Tooling

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

Ah, the age old HN pass-time of feeling like everything needs to fit your niche, leaving a comment about how a website didn't fill in your blind spot for you rather than googling what something is with the time.

If the official homepage of something doesn't tell you what it is, where are you supposed to obtain that inforation?

Re: Vite – Next Generation Front End Tooling

#319
post #179

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.

> to read about what Vite is and what it does. This is actually my main complaint. I read everything on the landing page and Getting Started page and still have literally zero idea what Vite does.

Secondary call-to-action is literally "Learn more" [0] and explains in details all the problems it solves

[0] https://vitejs.dev/guide/why

Re: Vite – Next Generation Front End Tooling

#320

F*king hell the ecosystem just never stops growing. Vite, Rollup, HMR? What the f*k is all this? Why does building a frontend have to be a titanic project involving a hundred tools including build systems and tree shakers and compilers and whatever else is going on. Web development is an embarrassment and a blight on computing.

No post body was provided.
Post reply on HN