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

351–360 of 383 posts

Re: Vite – Next Generation Front End Tooling

#351

Post by traspler »

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…

This might be stupid and petty but the only reason why I want enough Karma on HN is to be able to downvote these kinds of comments. They make me irrationally angry. Especially if they are under a link to a release announcement or changelog link, which at least, this is not.

Re: Vite – Next Generation Front End Tooling

#352

Post by samfundev »

vultour wrote: post #239
kossTKR wrote: 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…

It's hilarious listening to my friends who do frontend rave about the the incredible framework of the month, every month there's a new one that's supposed to be the last, ultimate, final stop for developing frontends. Lately it's all about server-side rendering... they managed to reinvent PHP 25 years later with 100x the complexity.

To clear up some confusion, I believe people are using the terms SSR and hydration interchangeably. Hydration is a new technology that uses SSR and then adds reactivity: https://en.wikipedia.org/wiki/Hydration_(web_development)

The server code will use the framework to handle SSR and hydration. Meaning that all you have to do is write the frontend and you get SSR for free.

Re: Vite – Next Generation Front End Tooling

#353

Post by zmxz »

weejewel wrote: post #191
zmxz wrote: 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.

Writing an objective, clear landing page seems to be a superpower as well.

You can complain all you like, but in the end it's you who has to read and understand the text written on the landing page. No one can do it for you.

Re: Vite – Next Generation Front End Tooling

#354

Post by phist_mcgee »

cercatrova wrote: post #197
finfinfin wrote: post #136

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.

The lack of native scrolling kills it for me. It's painfully obvious using a flutter app on iOS, since the scrolling momentum is way off.

You never really think this stuff matters until you're exposed to it.

Re: Vite – Next Generation Front End Tooling

#355

Post by boobsbr »

samfundev wrote: post #352
vultour wrote: post #239

Earlier quoted context omitted.

It's hilarious listening to my friends who do frontend rave about the the incredible framework of the month, every month there's a new one that's supposed to be the last, ultimate, final stop for developing frontends. Lately it's all about server-side rendering... they managed to reinvent PHP 25 years later with 100x the complexity.

To clear up some confusion, I believe people are using the terms SSR and hydration interchangeably. Hydration is a new technology that uses SSR and then adds reactivity: https://en.wikipedia.org/wiki/Hydration_(web_development) The server code will use the framework to handle SSR and hydration. Meaning that all you have to do is write the frontend and you get SSR for free.

If I'm not mistaken, GWT did hydration way back in 2010.

Re: Vite – Next Generation Front End Tooling

#356

Post by boobsbr »

noduerme wrote: post #207
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.

aaand we're all the way back to Flash.

Adobe (now Apache) Flex.

Re: Vite – Next Generation Front End Tooling

#357

Post by andruby »

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…

The Why page imo does a better job of explaining the reason it exists:

https://vitejs.dev/guide/why.html

Re: Vite – Next Generation Front End Tooling

#358

Post by TechBro8615 »

runarberg wrote: post #336
zmxz wrote: 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.

I agree. Vite is amazing. And most of the comments here seem to be same old complaints we’ve heard and debunked over and over about the state of frontend dev tools. I do wonder if other industries act like this to their specialties. E.g. do carpenters complain about the tools that boat builders use? Do butchers complain about bakers having to many tools. Do cobblers complain about marketing materials for tools used e…

Insecure non-frontend devs continue to see frontend as an easy programming environment, and therefore assume the problems in it should instantly make sense to them and be easily solvable. Because after all it’s easy, and they’re smart, and if they were a frontend dev, they wouldn’t even need this tooling because it’s so much easier to start from first principles of an index.html page.

It’s funny because I’m a frontend dev and I can do the job of a backend dev better than most backend devs. Yet I don’t go into every thread about Python and complain about what a horrible experience it is to install and manage.

Re: Vite – Next Generation Front End Tooling

#359

Post by zmxz »

systemvoltage wrote: post #198
zmxz wrote: 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.

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

There was no criticism of the tool itself, but how landing page is not instantly clear to developers who are not even frontend-related devs.

What's positive about that? A complaint with proposed action is what can be considered positive, but most complaints here were "I am not frontend dev, I clicked the link, I don't understand anything. They need to telepathically understand what I want and make the page that's to my liking".

It's just pseudointellectuals trying to pose as experts in a field they're not even working in. And here we are, a bunch of bottom feeders arguing over a landing page in year 2022. Oh, how entitled have we become. This situation is absolutely disgusting and not positive.

Re: Vite – Next Generation Front End Tooling

#360

Post by strokirk »

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.

As a backend developer, I’d say that it is a very apt comparison to your point. The backend and infrastructure space also has a lot of new projects solving old problems being released.
Post reply on HN