Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

VanJS – A no-JSX framework based on vanilla JavaScript

vanjs.org

Post reply on HN
Print view View original

11–20 of 178 posts

Re: VanJS – A no-JSX framework based on vanilla JavaScript

#11

Post by pard68 »

codebeaker wrote: post #4

Why do people even reinvent this wheel every few months? Does the Anyone can build a "reactive" type framework by following tutorials online now, they're super in vogue. Is my cynicism here warranted, or am I just jaded from 20 years of watching pendulums swing left and right and watching the wheel be reinvented over and over?

I think your cynicism is warranted for you. Like if you're not looking for a new framework and you are interested in the new, shiny JS refactor, don't bother. I live a happy life, using the same framework and never looking at all the other stuff.

But at one point our big contenders were also shiny and new, and I am glad someone less cynical than me was willing to put them to the test.

Re: VanJS – A no-JSX framework based on vanilla JavaScript

#12

Post by nwoli »

thinkingkong wrote: post #6

The whole “small footprint” thing is always weird to me. I understand that lots of people really want to squeeze efficiency out of every single kb but Im struggling to see where this is helpful. A single image, a single pixel from the marketing team, the actual application code, the page, etc are all going to dwarf the framework.

Not necessarily. Lots of jpegs go below the 1 mb mark (and tons of framework are bloated like crazy)

Re: VanJS – A no-JSX framework based on vanilla JavaScript

#13

Post by terpimost »

codebeaker wrote: post #4

Why do people even reinvent this wheel every few months? Does the Anyone can build a "reactive" type framework by following tutorials online now, they're super in vogue. Is my cynicism here warranted, or am I just jaded from 20 years of watching pendulums swing left and right and watching the wheel be reinvented over and over?

People feel unsolved problem for them and want a better solution for them individually. As you said “anyone can” so “anyone will”. Just ignore posts like this ;). After 20 years of experience just pay attention to v1 of anything :)

Re: VanJS – A no-JSX framework based on vanilla JavaScript

#14

Post by postalrat »

codebeaker wrote: post #4

Why do people even reinvent this wheel every few months? Does the Anyone can build a "reactive" type framework by following tutorials online now, they're super in vogue. Is my cynicism here warranted, or am I just jaded from 20 years of watching pendulums swing left and right and watching the wheel be reinvented over and over?

You should also be mad at all the people making game engines, compilers, llm's, and container hosts.

Re: VanJS – A no-JSX framework based on vanilla JavaScript

#15

Post by n2d4 »

codebeaker wrote: post #4

Why do people even reinvent this wheel every few months? Does the Anyone can build a "reactive" type framework by following tutorials online now, they're super in vogue. Is my cynicism here warranted, or am I just jaded from 20 years of watching pendulums swing left and right and watching the wheel be reinvented over and over?

For privacy reasons, resources are no longer cached across origins, so the size does matter (though arguably 1KB more or less makes absolutely no difference on any webpage that has a medium-sized image, especially if you have SSR for the first paint).

But the better reason why these projects exist is for experimentation and iteration. It's not like everyone who uses React will switch to this over the holidays, but maybe in five years some of the ideas in here will become more mainstream, and a future version of React (or a different framework) may adopt them.

Re: VanJS – A no-JSX framework based on vanilla JavaScript

#16

Post by __s »

codebeaker wrote: post #4

Why do people even reinvent this wheel every few months? Does the Anyone can build a "reactive" type framework by following tutorials online now, they're super in vogue. Is my cynicism here warranted, or am I just jaded from 20 years of watching pendulums swing left and right and watching the wheel be reinvented over and over?

You're jaded. Look at this as someone completing the exercise to understand reactive frameworks by implementing a toy implementation. Like when someone implements yet another lisp. Maybe you disagree with it getting to front page, but then don't upvote & move on. There'll always be some amount of front page content someone considers crap & it's best if we don't collectively fill every comment thread disparaging about it

Re: VanJS – A no-JSX framework based on vanilla JavaScript

#17

Post by robin_reala »

thinkingkong wrote: post #6

The whole “small footprint” thing is always weird to me. I understand that lots of people really want to squeeze efficiency out of every single kb but Im struggling to see where this is helpful. A single image, a single pixel from the marketing team, the actual application code, the page, etc are all going to dwarf the framework.

It’s about execution cost, not size over the network.

Re: VanJS – A no-JSX framework based on vanilla JavaScript

#19

Post by pritambarhate »

codebeaker wrote: post #4

Why do people even reinvent this wheel every few months? Does the Anyone can build a "reactive" type framework by following tutorials online now, they're super in vogue. Is my cynicism here warranted, or am I just jaded from 20 years of watching pendulums swing left and right and watching the wheel be reinvented over and over?

Let them reinvent it. You are not required to learn it right now. If it really manages to become widely used you can learn it then. If not well the guy is spending his own time on doing something he likes.

Re: VanJS – A no-JSX framework based on vanilla JavaScript

#20

Post by xiphias2 »

This is where most libraries are going.

Svelte 5 builds upon these signals / derivations as well, and I guess a bunch of other libraries.

It would be time for them to get together and standardize on a signals library at this point that could be adopted to be a web standard and help interoperability between web components built with different frameworks.

Post reply on HN