observable-slim

Observable Slim is a singleton that utilizes ES6 Proxies to observe changes made to object graphs. Originally built to assist with state management, one-way data binding, and any situation where an application must be reactive to data store changes.

Explore on GitHub Read Hacker News discussions

2Distinct people

7Mentions

0Explicit recommenders

306GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

elliotnb/nimbly · linked in 5 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 6:36:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month7 dated mentions

Observed mentions: 2018-07-07 21:11:26 UTC to 2019-09-15 16:16:26 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
Jul 2018	2018-07-01 00:00:00 UTC	2018-08-01 00:00:00 UTC	1	1	0
Aug 2018	2018-08-01 00:00:00 UTC	2018-09-01 00:00:00 UTC	0	0	0
Sep 2018	2018-09-01 00:00:00 UTC	2018-10-01 00:00:00 UTC	1	0	1
Oct 2018	2018-10-01 00:00:00 UTC	2018-11-01 00:00:00 UTC	0	0	0
Nov 2018	2018-11-01 00:00:00 UTC	2018-12-01 00:00:00 UTC	0	0	0
Dec 2018	2018-12-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	0	0	0
Jan 2019	2019-01-01 00:00:00 UTC	2019-02-01 00:00:00 UTC	0	0	0
Feb 2019	2019-02-01 00:00:00 UTC	2019-03-01 00:00:00 UTC	2	0	2
Mar 2019	2019-03-01 00:00:00 UTC	2019-04-01 00:00:00 UTC	1	0	1
Apr 2019	2019-04-01 00:00:00 UTC	2019-05-01 00:00:00 UTC	1	0	1
May 2019	2019-05-01 00:00:00 UTC	2019-06-01 00:00:00 UTC	0	0	0
Jun 2019	2019-06-01 00:00:00 UTC	2019-07-01 00:00:00 UTC	0	0	0
Jul 2019	2019-07-01 00:00:00 UTC	2019-08-01 00:00:00 UTC	0	0	0
Aug 2019	2019-08-01 00:00:00 UTC	2019-09-01 00:00:00 UTC	0	0	0
Sep 2019	2019-09-01 00:00:00 UTC	2019-10-01 00:00:00 UTC	1	0	1

What Hacker News says

2 sources

EB66·Feb 20, 2019

@omeid2 I think you've distilled the issue very well -- it's all about "what is simpler code?". I hadn't thought of the issue in terms of the three C's you've mentioned, but the criteria also seems accurate. In my opinion, the popular SPA frameworks (Angular, React, Vue, etc) all suffer from similar problems. They build abstractions on top of abstractions, they force you to learn domain-specific languages (e.g., JSX), lots of new concepts to learn before you can be productive, they are fairly opinionated about how your application should be structured, etc. If you have the time, take a look at this JS framework I put together ( https://github.com/elliotnb/nimbly ) and it's state management dependency ( https://github.com/elliotnb/observable-slim ). I built the framework so developers can take advantage of the benefits of modern frameworks

Read the rest

(templating, data binding, state management, no explicit DOM manipulations, automated unit testing, loosely coupled modular components, etc) but without the typical drawbacks of modern frameworks. The framework has far fewer abstractions than React or Vue, requires no domain specific language (i.e., you write in plain HTML, CSS and JS), and does not require compiling/transpiling. The framework embraces the DOM instead of abstracting away from it and still refreshes/re-renders components in a highly performant manner via DocumentFragments. We've used the framework fairly extensively at my work because it plays very nicely with our jQuery-heavy legacy code and allows for much easier re-factors. The observer library has gained a fair bit of interest from other developers (~2k monthly downloads via npm) and it'd be great if I could interest others in trying out the framework too. I'd love to hear feedback from anyone who takes the time to try it out. Other contributors would be fantastic.

In I love React Hooks

EB66·Feb 13, 2019

@sam0x17 If you have the time, take a look at this JS framework I put together ( https://github.com/elliotnb/nimbly ) and it's observer library dependency ( https://github.com/elliotnb/observable-slim ). I built the framework so developers can take advantage of the benefits of modern frameworks (templating, data binding, state management, no explicit DOM manipulations, automated unit testing, loosely coupled modular components, etc) but without the typical drawbacks of modern frameworks. The framework has far fewer abstractions than React or Vue, requires no domain specific language (i.e., you write in plain HTML, CSS and JS), and does not require compiling/transpiling. The framework embraces the DOM instead of abstracting away from it and still refreshes/re-renders components in a highly performant manner via DocumentFragments. We've use

Read the rest

d the framework fairly extensively at my work because it plays very nicely with our jQuery-heavy legacy code and allows for much easier re-factors. The observer library has gained a fair bit of interest from other developers (~600 downloads per week via npm) and it'd be great if I could interest others in trying out the framework too. I'd love to hear feedback from anyone who takes the time to try it out. Other contributors would be fantastic.

In Bootstrap 5 will remove jQuery as a dependency