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

281–290 of 383 posts

Re: Vite – Next Generation Front End Tooling

#281

Post by frankwallis »

somenewaccount1 wrote: post #122
blowski wrote: post #69

Earlier quoted context omitted.

Devil's Advocate position here. I don't know much about carpentry, and if I look at a website selling saws, I will struggle to understand the difference between different models. Dumbing down to an extent that I understand (when I probably won't buy the product anyway) risks alienating the target market that will. Due to customer demands, end-user requirements, and device fragmentation, front-end development has genu…

I am a developer and still took a while to realize what it does. Also, that snowpack is probably just as sufficient. It's a shite landing page that communicates little, and as a front end framework, well....shouldn't we expect more?

Snowpack is no longer maintained and they recommend switching to Vite.

Re: Vite – Next Generation Front End Tooling

#282

Post by shepherdjerred »

Aisde from the typical HN comments of:

* Front-end is a mess; who needs anything other than hand written HTML and jQuery

* This site doesn't explain what this is

Vite is pretty great. It is a huge improvement on webpack and other competitors that I've used. Configuring Vite for the common use case of some front end framework + optional TypeScript + unit testing + hot reloading is something that can be done with a literally just 5 lines of configuration.

At work I switched over a 1000 line webpack script for 40 lines of Vite. Vite is superior in every way compared to webpack (at least as far as my use cases)

Re: Vite – Next Generation Front End Tooling

#284

Post by dang »

martini333 wrote: post #242
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…

Quoted post unavailable.

Whoa - we ban accounts that attack others like this, regardless of how dense other commenters are or you feel they are.

I'm afraid you've been breaking the site guidelines in other places too (e.g. with unsubstantive and/or flamebait and/or name-calling comments).

I'm not going to ban you just now but if you'd please review https://news.ycombinator.com/newsguidelines.html and stick to the rules when posting here, we'd appreciate it.

Re: Vite – Next Generation Front End Tooling

#285

Post by avgcorrection »

blowski wrote: post #69
thrdbndndn wrote: post #52

Earlier quoted context omitted.

I'm not a developer and particularly not a front-end one. I have this problem all the time. Even some of the more "obvious" ones, say, nuxtjs, I have a hard time to get what exactly it offers and why I should use it.

Devil's Advocate position here. I don't know much about carpentry, and if I look at a website selling saws, I will struggle to understand the difference between different models. Dumbing down to an extent that I understand (when I probably won't buy the product anyway) risks alienating the target market that will. Due to customer demands, end-user requirements, and device fragmentation, front-end development has genu…

Nothing like a carpentry analogy to obliterate all nuance.

The OP said:

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

We know that it is “tooling”. But what is “next gen” and “catch up with you”? Are those terms that the appropriate audience is just supposed to get?

Re: Vite – Next Generation Front End Tooling

#286

Post by redbar0n »

gedy wrote: post #186
config_yml wrote: post #21

Earlier quoted context omitted.

I think Rails should have done the same, vite_ruby is amazing. Thankfully it's easy enough to replace the current options, which feel a bit half-hearted.

It feels like DHH really doesn't want this tooling at all in Rails, but did so reluctantly because so much view tech and mindshare had moved to the client.

https://world.hey.com/dhh/rails-7-will-have-three-great-answ...

Re: Vite – Next Generation Front End Tooling

#287

Post by christoph »

QuadrupleA wrote: post #221

The 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…

I absolutely agree with you on the surface, as I’m of exactly the same mind. However, I’ve forced myself to use a few shiny new things on projects over the last couple of years and it’s been a mixed bag. Some new frameworks like Vue have absolutely shrunk development times for certain types of projects by a serious order of magnitude, as we are now worrying way less about state and writing far less code overall. Mutating certain changes just cascades down without us worrying too much and writing loads of code to handle those changes/updates. Hot reloads alone have easily saved countless development hours.

Other times, I just feel like I’ve been fighting a framework for hours to achieve something that really should have only take a few minutes.

IMO, it’s about having as many weapons in your arsenal as possible and always selecting the most appropriate for the task at hand. You can only really do this if you have a good broad working knowledge of as many tools as possible, to understand their unique strengths and limitations.

Typically I just avoid the latest shiny new thing entirely for at least a couple of years until it’s stabilised somewhat. I got burnt early adopting Swift and spending countless unbillable hours updating thousands of LOC every time Apple seemed to break the entire thing with each new release.

Re: Vite – Next Generation Front End Tooling

#288

Post by yeskia »

config_yml wrote: post #21
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.

I think Rails should have done the same, vite_ruby is amazing. Thankfully it's easy enough to replace the current options, which feel a bit half-hearted.

esbuild through jsbundling-rails is very quick too.

Re: Vite – Next Generation Front End Tooling

#289

Post by [deleted] »

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.

[deleted]
Post reply on HN