Hacker News Reader

Comment by wruza | Hacker News Reader

Vite is a “bundler”, a dev/build tool. You can vanilla js with it as usual. It takes your index.html and sucks in a whole dependency tree to shake it and either produce a production bundle or run a dev server. Being aware of ts, vue, react, sass, etc out of box is its bonus points.

Vite vs React vs Next is crates vs oranges vs boxed oranges.

I know react but never touch it. React, vue, svelte are “state management”. I’m using mithril.js with POJOs for my frontends.

Vanilla everything gets messy in interactive apps, and I come up with a poor man’s mithril usually, then rewrite for it.

View on HN

Oh, so you're developing a bit differently from the current trends. Interesting. As you mentioned, when developing with vanilla JavaScript, it can become difficult to maintain as more features are added or the service grows. However, if you plan carefully, it’s not necessarily a big issue, though many might find it challenging. Do you have any ongoing projects by any chance? Perhaps a project where you're utilizing Vite and Mithril effectively?

I understand trends, but don’t understand why I’d need them. It’s extra work for nothing. But updating dynamic ui requires thought that aligns with m() ideas for me. That’s it, my whole reasoning.

Made numerous projects with m(), inhouse dashboards/forms, crypto/stock trading tools, RC buggy debug interface. Currently a set of crypto-related db views again. Not sure if I want to share the code though.

Just read mithril guide if interested, it’s very short. I don’t do anything funny with it. If it clicks, it clicks. If not, ignore it.

It’s quite similar to the reason why I insist on developing with vanilla JavaScript. It’s hard to shake off the feeling that many libraries or frameworks stray away from the essence, and that’s one of the reasons. Since these are things I’ve felt through actual experience in the field, I’d like to take a look at it as well. Thanks for the good information!

Reply on news.ycombinator.com