Vite – Next Generation Front End Tooling

Re:Vite – Next Generation Front End Tooling by thr0wawayf00 on Sunday July 03, 2022 @01:48PM (#31969527)

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 expert in all of the different ways you can bundle and deploy a JS app in order for the jargon associated with these tools to make any sense.

[ Parent | on HN ]

Re:Vite – Next Generation Front End Tooling by jollybean on Sunday July 03, 2022 @02:47PM (#31969980)

You're right that JS is a mess, but this is not a JS problem, it's a tech problem.

I see it over, over and over again.

I see young people pitching their tech and I have no f*ing clue what they are talking about.

I would say >50% of web sites don't do a very good job of explaining anything.

Vercel is one of the worst offenders.

[ Parent | on HN ]

Re:Vite – Next Generation Front End Tooling by woojoo666 on Sunday July 03, 2022 @07:27PM (#31971897)

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/

[ Parent | on HN ]

Re:Vite – Next Generation Front End Tooling by jollybean on Sunday July 03, 2022 @08:02PM (#31972084)

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.

[ Parent | on HN ]