Live data from Hacker News

Vite – Next Generation Front End Tooling

main.vitejs.dev

231–240 of 383 posts

Re: Vite – Next Generation Front End Tooling

#231
Sorry but if it requires NPM then I am not interested. I have been burnt too many times to want to use anything related to NPM.

I would hope that a next generation framework would not have hard dependencies on the cess pit that is NPM :(. Please give us something fresh and interesting.

This is why I am so excited by deno on the backend - finally no more NPM!

Re: Vite – Next Generation Front End Tooling

#232
I find it funny that, as usual, half the comments are complaints about "why are frontend developers always reinventing the wheel"... Meanwhile the 1st post on the front page [1] is about a new "modern" scheduling package for Python. What's wrong with just using Celery, APScheduler, Huey or even cron? Why do we need a new scheduling library? Yet I don't see any "reinventing the wheel" critic in the comments. Double standard I guess.

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

Re: Vite – Next Generation Front End Tooling

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

I can't wait for deno.js to really skyrocket. It solves all of this garbage packaging dependency nonsense.

No, it doesn't. All Deno does by ignoring dependency management is creating a breeding ground for worse dependency management.

Re: Vite – Next Generation Front End Tooling

#234

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.

To be fair web content can also be ported easily pretty much everywhere because browsers run almost everywhere.

Re: Vite – Next Generation Front End Tooling

#235

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?

Re: Vite – Next Generation Front End Tooling

#237
I know everyone is here to complain about the mess that is "modern" frontend work. But I have to say, I started using Vite a week ago to bootstrap a new project using Typescript, Preact, and Tailwind, and I'm loving it. There is one weird quirk in where it insists the index.html file should be. But if you can live with that, Vite takes care of the details for me and gets out of my way. It also bundles everything exactly how I would have set it up by hand. I think it's weird that it insists its mostly a dev server. It does that well. But it's also a very good bundler with good defaults. I'd recommended it to anyone who just wants to get started, and wants a good middle ground between esbuild and parcel.

Re: Vite – Next Generation Front End Tooling

#238
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.

Because being “behind” on front end technologies is a sure fire way of ending up jobless and irrelevant.

Re: Vite – Next Generation Front End Tooling

#239
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.

Re: Vite – Next Generation Front End Tooling

#240

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.

How big is your application? What level of legacy are you dealing with? Do you also have broccoli as part of your build process? What did you switch from? How are you consuming your build? Do you do server side rendering? Do you build for UI testing? What’s it like building for Jest? Have you had to write any custom plugins?
Post reply on HN