Show HN: A tiny and fast reactive observables library via functions

Couldn’t read only be replaced with wrapping an observable in a closure?

const $a = $observable(42)

const $b = () => $a()

IMO “use after dispose” should crash to make it easier to detect bugs. Also dispose should error when it texts a request to dispose something that still has a dependency. It is unlikely this is intended as it would likely lead to a “use after free” or memory leak.

Not OP, but:

- You could just use computeds instead of effects, but:

  - Effects don't have an internal observable, so they are cheaper to make and to keep in memory.

  - If OP will implement something like Suspense they'll probably want to pause the execution of effects, but not the execution of computeds.

  - OP didn't implement this, but potentially you could support returning a cleanup functions inside effects, you can't do the same for computeds.

Yes, internally it's probably just a `$computed( $observable )`. The differences are that one is just a function and the other is an observable, which is a detectable difference that may matter, but also potentially the utility function could return you always the same observable if it has already a reference to a read-only version of the one you give it, which may consume less memory (1 function to keep around rather than N), though this is a bit of an edge case.

Add me to the list of people who've made their own "tiny" observable js lib (https://github.com/kevinfiol/vyce). Albeit, this one looks more complete.

[0]: https://github.com/adamhaile/S