No post body was provided.
Vite – Next Generation Front End Tooling
301–310 of 383 posts
Re: Vite – Next Generation Front End Tooling
#302Incredible 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.
> It takes more time to type all that negativity Well, good criticism is not negativity, but I'd argue it is positivity.
I came to this discussion because I wanted good criticism of ViteJS . I genuinely wanted to see it picked apart by experts because I have been thinking about trying it for a while now.
Instead, I'm about 100 comments down and so far all I can see is endless repetition of the same nitpicking complaint that the landing page is not good. The landing page!
If you use this tool you'll spend about 5 minutes on the landing page and potentially hundreds or thousands of hours in the code, API, and docs. So who cares about the damn landing page?
I want discussion of the actual tool, that's what I come to HN for. There doesn't appear to be much of that happening here, unfortunately.
If there was a single comment thread somewhere criticizing the landing page that would be fine, it's a valid complaint. But if pretty much all the top comments are exclusively doing that, or pointing out how pointless a criticism that is (like this one) then this discussion is a failure.
EDIT: scrolling further down I appear to have hit the "oh no frontend dev is so complicated, poor me" section of the discussion. I'm gonna keep digging, wish me luck!
Re: Vite – Next Generation Front End Tooling
#303No post body was provided.
Re: Vite – Next Generation Front End Tooling
#304It 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.
Re: Vite – Next Generation Front End Tooling
#305Earlier quoted context omitted.
We both know those aren't even close to the same thing. All this grunt->gulp->webpack->vite->'the inevitable replacement for vite' are really achieving is finding slightly different ways of doing the same thing.
"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.
Re: Vite – Next Generation Front End Tooling
#306Earlier quoted context omitted.
We both know those aren't even close to the same thing. All this grunt->gulp->webpack->vite->'the inevitable replacement for vite' are really achieving is finding slightly different ways of doing the same thing.
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.
Re: Vite – Next Generation Front End Tooling
#307Working 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…
I had the exact opposite experience with Vite.
We had built a web application and had an existing rollup build process configured for all the obvious things you can think of (including SVG and JSON files, path aliases, development server with watch, typescript support, etc).
One week I got approval to try migrate to Vite and it was pretty much: delete the existing config, use the default Vite one, and remove all your rollup plugins from package.json (since Vite does all the obvious stuff out of the box).
I was using Rider and had no issues at all. It was automatically using my path aliases. It understood importing SVG and JSON files. I got intellisense for all Vite APIs. Maybe I had some plugins installed or settings enabled from when I was using rollup, but there's nothing obscure as my IDE setup is pretty vanilla.
Re: Vite – Next Generation Front End Tooling
#308Earlier quoted context omitted.
It's still not concise enough. It's a long article you have to read to figure out what you are reading about. "WTF IS IT?" is an endemic problem with marketing and startups. Marketing is a skill, that many people in marketing so often don't have, and lot of leaders fail to grasp. It's so sad. Imagine losing 1/2 of your potential uptake because of poor choice of words.
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.
Re: Vite – Next Generation Front End Tooling
#309Earlier quoted context omitted.
> ...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.
This. As someone who's hung back and not switched to the hot new thing in frontend - I've learned the "old" stuff seems to mature and tends to get better. Look at React, CRA, or Redux Toolkit - they're all so much better (performant, more concise) than the original few releases now!
Thank you, glad to hear RTK is working well for you!
Re: Vite – Next Generation Front End Tooling
#310The frontend world seems to be drowning in its own accidental complexity, with each new framework trying to solve the ecosystem's self-created problems. I've been developing complicated full stack apps for years with nearly-vanilla JS, CSS and HTML, plus a helping of basic software design skills, and I have no trouble managing complexity, delivering features fast, etc. I've never related to all these problems the fro…
Have any examples of websites or products of yours?
Edit: ok so I took a look at the website in your hackernews bio. Some cool stuff there, but honestly in terms of front end work it isn't terribly complicated. So while you might be picking the correct tools for your work, it doesn't really apply for, say, a marketplace website that wants to lazy load long lists of products, or that want to re-use those product cards across different pages, etc. This is where vanilla JS starts to be too low-level, and you start to see the benefits of the structure that frameworks provide.