proposal-observable
proposal-explicit-resource-management
proposal-observable | proposal-explicit-resource-management | |
---|---|---|
12 | 22 | |
3,036 | 703 | |
0.2% | 4.0% | |
0.0 | 6.5 | |
over 4 years ago | 23 days ago | |
JavaScript | JavaScript | |
- | BSD 3-clause "New" or "Revised" License |
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.
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
proposal-explicit-resource-management
- Cooperation between Cloudflare Workers has become amazing thanks to RPC support
-
Proposal: Signals as a Built-In Primitive of JavaScript
The standard doesn't have anything to do with TypeScript, not sure where you got that from? https://github.com/tc39/proposal-explicit-resource-managemen...
-
How does TypeScript's explicit resource management work?
The explicit resource management proposal tries to make it a bit easier for us, by allowing the resource to declare how it should be managed, rather than expecting us to clean everything up when we use the resource. We get a new keyword using to define a variable (rather than const or let), which tells the runtime to clean up the resource at the end of the function.
-
Using using in TypeScript for resource management
Enter the explicit resource management proposal, which describes — among many other things — a new using operator that was introduced in TypeScript 5.2 and is making its way into JavaScript. From the top of the README file, here’s what this proposal aims to do:
-
OpenTelemetry in 2023
In addition to this, is the new (stage 3 even!)explicit resource management proposal[0], supported by TypeScript version >= 5.2[1]
Though I agree that async context is better fit for this generally, the RMP should be good for telemetry around objects that have defined lifetime semantics, which is a step in the right direction you can use today
[0]: https://github.com/tc39/proposal-explicit-resource-managemen...
[1]: https://www.totaltypescript.com/typescript-5-2-new-keyword-u...
- ECMAScript Explicit Resource Management Proposal
-
Why is JavaScript so hated?
It's too early for that, https://github.com/tc39/proposal-explicit-resource-management
-
TypeScript 5.2's New Keyword: 'using'
[3]: https://github.com/tc39/proposal-explicit-resource-managemen...
-
Douglas Crockford: “We should stop using JavaScript”
I'm not _entirely_ sure which RAII you mean, but if you mean something like C#'s `using` or Java's `try-with-resources` or Python's `with`, then https://github.com/tc39/proposal-explicit-resource-managemen... and https://github.com/tc39/proposal-async-explicit-resource-man... are in stage 3 (of 4 stages) in ECMAScript's language proposal lifecycle and will be coming to a JS engine near you behind a flag soon-ish.
What are some alternatives?
duckdb - DuckDB is an in-process SQL OLAP Database Management System
librope - UTF-8 rope library for C
fp-ts - Functional programming in TypeScript
caniuse - Raw browser/feature support data from caniuse.com
eslint-plugin-unicorn - More than 100 powerful ESLint rules
pidove
eslint-plugin-github - An opinionated collection of ESLint rules used by GitHub.
proposal-class-method-parameter-decorators - Decorators for ECMAScript class method and constructor parameters
RxJS - A reactive programming library for JavaScript
search-benchmark-game - Search engine benchmark (Tantivy, Lucene, PISA, ...)
cross-project-council - OpenJS Foundation Cross Project Council
proposal-iterator-helpers - Methods for working with iterators in ECMAScript