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

Show HN: Mador – Make any DOM reactive with a tiny 80-line Proxy state tuple

github.com

Post reply on HN
Print view View original

31–37 of 37 posts

Re: Show HN: Mador – Make any DOM reactive with a tiny 80-line Proxy state tuple

#31

Post by royal_ts »

bedroom_jabroni wrote: post #12

There are many standalone plug-n-play implementations of the signal primitive in JS. To name a few: preact/signals, vue reactivity, etc, there's even a TC39 proposal for a lang feature. Is this meant to stand out by doing things differently or reinvent them?

The TC39 proposal seems pretty much dead :(; it doesn't look like much is happening. If I understand it correctly, it's really just about agreeing on a protocol, and it's ultimately up to frameworks to implement it, there isn't anything (yet?) that can run directly in JavaScript.

Re: Show HN: Mador – Make any DOM reactive with a tiny 80-line Proxy state tuple

#32

Post by bedroom_jabroni »

kevinfiol wrote: post #25
bedroom_jabroni wrote: post #16

Earlier quoted context omitted.

preact/signals-core has 0 dependencies, your project could also benefit from mentioning what primitive is being implemented for the reader's information. The size difference is negligible. The readme creates a false dilemma where there's either Mador or "having to use a framework" but it hasn't been the case for ages - as I mentioned above the major frameworks have decoupled versions of their reactivity available. Th…

It's not that weird of a presentation, just different ergonomics for the same problem. preact/signals-core is great, but since HTML elements have no way to subscribe to signals, you have to handle that yourself: import { signal, effect } from "@preact/signals-core"; const $ = (s) => document.querySelector(s); const counter = signal(0); effect(() => { $('.counter').textContent = counter.value; }); $('.increment').addE…

I wasn't referring to the ergonomics - the weirdness was from the way it was worded like "Here's one trick Big Framework doesn't want YOU to know" as if React, Vue and such were gatekeeping their reactivity while they're actively maintaining and sharing standalone versions of it.

Re: Show HN: Mador – Make any DOM reactive with a tiny 80-line Proxy state tuple

#33

Post by bedroom_jabroni »

bosmarcel wrote: post #17
bedroom_jabroni wrote: post #16

Earlier quoted context omitted.

preact/signals-core has 0 dependencies, your project could also benefit from mentioning what primitive is being implemented for the reader's information. The size difference is negligible. The readme creates a false dilemma where there's either Mador or "having to use a framework" but it hasn't been the case for ages - as I mentioned above the major frameworks have decoupled versions of their reactivity available. Th…

That's a fair distinction, but I think they solve different problems. Signals are great, but they usually require managing primitives individually and don't map directly to deep, nested JS objects the same way. Mador is specifically about dropping in a plain, nested object and working with it like normal JS without .value "boilerplate". Appreciate the feedback on the README phrasing though—I'll tweak it so it doesn't…

The .value comparison is not fair because it's a single value vs an object property. A better comparison would be against something like Vue's reactive() where it doesn't require you to add this "boilerplate".

Re: Show HN: Mador – Make any DOM reactive with a tiny 80-line Proxy state tuple

#36

Post by kevinfiol »

bedroom_jabroni wrote: post #32
kevinfiol wrote: post #25

Earlier quoted context omitted.

It's not that weird of a presentation, just different ergonomics for the same problem. preact/signals-core is great, but since HTML elements have no way to subscribe to signals, you have to handle that yourself: import { signal, effect } from "@preact/signals-core"; const $ = (s) => document.querySelector(s); const counter = signal(0); effect(() => { $('.counter').textContent = counter.value; }); $('.increment').addE…

I wasn't referring to the ergonomics - the weirdness was from the way it was worded like "Here's one trick Big Framework doesn't want YOU to know" as if React, Vue and such were gatekeeping their reactivity while they're actively maintaining and sharing standalone versions of it.

Fair, although I'm aware of preact/signals-core, what are React/Vue's standalone reactive libraries?

Re: Show HN: Mador – Make any DOM reactive with a tiny 80-line Proxy state tuple

#37

Post by phatskat »

kevinfiol wrote: post #36
bedroom_jabroni wrote: post #32

Earlier quoted context omitted.

I wasn't referring to the ergonomics - the weirdness was from the way it was worded like "Here's one trick Big Framework doesn't want YOU to know" as if React, Vue and such were gatekeeping their reactivity while they're actively maintaining and sharing standalone versions of it.

Fair, although I'm aware of preact/signals-core, what are React/Vue's standalone reactive libraries?

You're looking for `@vue/reactivity`[1] - looks like it provides ref, computed, watch, and some internals.

Honestly, this seems pretty nifty. Most projects I'd do today would likely have more value in Vue as a whole, and it's nice to see these kinds of things exposed and standalone bits

[1] https://github.com/vuejs/core/tree/main/packages/reactivity/...

Post reply on HN