Live data from Hacker News

VanJS (Vanilla JavaScript): smallest reactive UI framework

github.com

81–90 of 214 posts

Re: VanJS (Vanilla JavaScript): smallest reactive UI framework

#81
This narrative (https://vanjs.org/about#story) about modern JS tooling being opaque, exclusive, and hard to learn is frustrating.

If all you need is HTML rendering and basic state, any modern web framework will do that extremely simply. The barrier to entry is really not that high!*

*Except maybe at Google. I hear their internal tooling is a huge pain to work with.

Re: VanJS (Vanilla JavaScript): smallest reactive UI framework

#82

If I was making this kind of mini framework instead of this a({href: "https://vanjs.org/"}, "VanJS") I would have gone with this shorter way a("VanJS").href("https://vanjs.org/") And make it chainable and allow class names as second argument as in a("About us", ".big.red").href("/about.html").target("_blank")

I think the way it's done is correct, an object passed as a parameter with key value pairs for attributes seems a lot more logical.

Re: VanJS (Vanilla JavaScript): smallest reactive UI framework

#83
post #69
post #64

Earlier quoted context omitted.

Suggestion: call it Bourbon JS. Wikipedia: > The majority of the world's vanilla is the V. planifolia species, more commonly known as Bourbon vanilla.

Wait people write JavaScript without drinking bourbon?

I prefer Scotch

Re: VanJS (Vanilla JavaScript): smallest reactive UI framework

#84
post #64

Earlier quoted context omitted.

Suggestion: call it Bourbon JS. Wikipedia: > The majority of the world's vanilla is the V. planifolia species, more commonly known as Bourbon vanilla.

Already taken. I know it's not JS but it's front end tooling. https://www.bourbon.io/

Vanilla was already taken too:

https://github.com/idevz/vanilla

Re: VanJS (Vanilla JavaScript): smallest reactive UI framework

#85
post #8

I really don't want to be that guy, but... Vanilla JavaScript already exists as a popular term for JavaScript without any framework. No jQuery, no React - just JavaScript. Calling a library VanJS (as short for "Vanilla JavaScript") is just going to cause confusion. The repo's own description uses the phrase vanilla JavaScript in this way, and even mixes both meanings within a single sentence. If the author likes the…

Yes, please be that guy. Or I'll do it. Vanilla Javascript refers indeed to "javascript without a framework". So creating a framework and calling it "vanilla javascript" is... wrong?

Suggestion 2: call it IceCreamJS or just IceJS/CreamJS

Re: VanJS (Vanilla JavaScript): smallest reactive UI framework

#86

Why is everybody so obsessed with size? 100kB means nothing these days.

Wrong. You know it never ends up being 100kb, and when it reaches 1MB (it always does) then you get the real issues.

It’s because of your thinking that we got bloated webpages.

Re: VanJS (Vanilla JavaScript): smallest reactive UI framework

#87

If I was making this kind of mini framework instead of this a({href: "https://vanjs.org/"}, "VanJS") I would have gone with this shorter way a("VanJS").href("https://vanjs.org/") And make it chainable and allow class names as second argument as in a("About us", ".big.red").href("/about.html").target("_blank")

Here's one for React:

https://github.com/jehna/nosx

Re: VanJS (Vanilla JavaScript): smallest reactive UI framework

#89
Makes me think that jquery may have missed a boat to integrate reactive elements (as there was clearly a need for them for a long time before angular, react etc took of) and retain relevance.

Maybe for projects that don't aim to replicate desktop app functionality there is a "small-is-beautiful" yet all-inclusive js library that is missing.

Re: VanJS (Vanilla JavaScript): smallest reactive UI framework

#90
post #57

If I was making this kind of mini framework instead of this a({href: "https://vanjs.org/"}, "VanJS") I would have gone with this shorter way a("VanJS").href("https://vanjs.org/") And make it chainable and allow class names as second argument as in a("About us", ".big.red").href("/about.html").target("_blank")

Chaining is very... 2010? Mainly because it's used().to().make().awful().APIs().like().this(). It got popular then seems to have died out. href() isn't a function name. One doesn't 'href()' anything.

You know what promises are right?
Post reply on HN