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

1–10 of 178 posts

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

#4

Post by codebeaker »

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?

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

#5

Post by __s »

This doesn't look too bad for pushing down minimal dom manipulation, since it includes reactivity

Looking at my own use of solid, things this is missing are:

- jsx

- stores (having some way to hook into van's reactivity would address this, maybe digging into van.state internals there's a way)

- onMount/onCleanup

- For/Index/Show which helps handle efficient reuse, this could probably be built as a layer on top of vanjs

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

#6

Post by thinkingkong »

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.

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

#8

Post by pulse7 »

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?

The problem is not size. The problem is installation, configuration, dependencies, transpilation, IDE setup, etc. And here you have the plain old notepad with browser - nothing else...

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

#9

Post by robin_reala »

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?

The amount of code matters when the lowest-performing Androids on the market have an order of magnitude less single core performance than a modern iOS device. V8 parse times have got much better over the last few years (they used to be a big bottleneck) but you’ve still got major execution cost leading to bad user experience.

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

#10

Post by bovermyer »

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?

Size does still matter. Just because we _can_ serve huge amounts of data over the pipe quickly doesn't mean we _should_.
Post reply on HN