observable
proposal-observable
observable | proposal-observable | |
---|---|---|
9 | 12 | |
514 | 3,036 | |
1.4% | 0.2% | |
8.2 | 0.0 | |
11 days ago | over 4 years ago | |
Bikeshed | JavaScript | |
GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
observable
- Proposal: Signals as a Built-In Primitive of JavaScript
-
What We Need Instead of "Web Components"
> especially since Observables have been widely available and actively worked on for a long time, without seeing wide adoption
Take a look at "Userland libraries" section [0] of the proposal (almost certainly written by Ben). He argues that observables get reinvented in the userland in various libraries over and over again. It is a primitive, like a Promise, only better.
[0] - https://github.com/WICG/observable?tab=readme-ov-file#userla...
- Observable API Proposal
- Observable API proposal
-
You Don't Need to “Learn” Svelte: Embracing the Simplicity of JavaScript
Perhaps this falls into the repetitive boilerplate category you referred to, but if you want framework-agnostic domain objects that still work well with Svelte, create your own using the observer pattern.
Create an object with a subscribe method and whatever other methods make sense for updating its state. Svelte will treat it like one of its stores, and it will work with the $ syntax. It can be used with React via its `useSyncExternalStore` hook. It can be used with SolidJS via its `from` utility.
If you don't want to handle the set-up boilerplate, you could use another library like Effector or RxJS, but of course, that means another dependency. There is a gradual move to make something like this a part of the platform[1], but who knows when or if it will land.
[1] https://github.com/domfarolino/observable
proposal-observable
-
Proposal: Signals as a Built-In Primitive of JavaScript
https://github.com/tc39/proposal-observable
And there's the new one which seems to be getting implemented in node right now:
-
Observable API Proposal
How does it differ from <https://github.com/tc39/proposal-observable/>?
-
The Truth about Svelte
I think it is a shame that the Observable proposal [1] still seems somewhat stuck in Stage 1. It's a better idea than just raw event emitters because of composability (if no other reason). Making Observables "first class" could go a long way to unifying a lot of reactivity patterns in various frameworks, in theory at least.
To be fair, Observables and especially Observable composition has a rough learning curve and many frameworks like Svelte intentionally prefer implict reactivity and avoiding things like explicit Observables because they are seen as too complex/"too hard" for the average developer.
(Then you get awful worst of both worlds frameworks like Angular that sort of rely on Observables but yet also don't trust teaching Observables and wind up with code that isn't properly Observable and so also has all the code for implicit reactivity and is full of nasty escape hatches that cause all sorts of composition problems and unnecessary side effects.)
[1] https://github.com/tc39/proposal-observable
-
💡 Observable Mutable Wrapper Object
Uses an interface described in the TC39 observables proposal
-
Example of Asynchronous programming using Observer pattern vs Promise
JavaScript doesn't have any built-in observables (addEventListener is part of the DOM API specific to browsers) though there is an old observable proposal collecting dust. I think ReactiveX (RxJS) is pretty much the go-to for any kind of observable functionality you may want. That may be a good place to start to really see what observables can do.
-
JavaScript Evolutsiyasi Qisqa Satrlarda!
Observablelar streamlarga asoslangan reaktiv dasturlash paradigmasini olib kiradi JSga. Shaxsan menga eng yoqqan takliflardan biri. Bu haqida ham alohida maqola yozish niyat bor. RxJS (Angular) bilan ishlab ko'rganlar bo'lsa buni nimaligini juda yaxshi tushunishadi, endi bu library emas balki native 🚀 !!!
-
4 Ways to Handle Async Operations in Javascript
Observable is an object that takes a stream of data and emits events over time to react accordingly. There is a talk to add it to the ECMAScript standard and its proposal is here. Till now it is not part of the ECMAScript standard so to use it, you have to use a third-party library and the well-known Reactive Extension in Javascript is RxJs.
-
Reactive Programming
Well, the answer is surprisingly no. But, there is an active tc39 proposal going on around for a while, didn’t find it much active though, you could watch out here — https://github.com/tc39/proposal-observable
-
Why do we need rxjs library as JavaScript is reactive by default?
RxJS is an implementation of observables which do not exist natively in JavaScript. There is a proposal for adding observables to the language, but it's only stage 1 and hasn't been active for years.
- Query Engines: Push vs. Pull
What are some alternatives?
starfx - A modern approach to side-effect and state management for web apps.
duckdb - DuckDB is an in-process SQL OLAP Database Management System
proposal-async-iterator-helpers - Methods for working with async iterators in ECMAScript
fp-ts - Functional programming in TypeScript
BrightFutures - Write great asynchronous code in Swift using futures and promises
eslint-plugin-unicorn - More than 100 powerful ESLint rules
Reactor - Powering your RAC architecture
eslint-plugin-github - An opinionated collection of ESLint rules used by GitHub.
bruh - The thinnest possible layer between development and production for the modern web.
RxJS - A reactive programming library for JavaScript
cross-project-council - OpenJS Foundation Cross Project Council
proposal-pattern-matching - Pattern matching syntax for ECMAScript