promises-spec
proposal-explicit-resource-management
promises-spec | proposal-explicit-resource-management | |
---|---|---|
22 | 22 | |
1,831 | 703 | |
0.2% | 4.0% | |
0.0 | 6.5 | |
9 months ago | 23 days ago | |
JavaScript | ||
Creative Commons Zero v1.0 Universal | 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.
promises-spec
-
Implement Promises/A+ from scratch
Today, I tried implementing Promises/A+ from scratch to test my coding skill. In the process, I’ve crafted this guide to share my insights and experiences with those who share a similar interest. Without further ado, let’s dive in.
-
Using XPath in 2023
That made me chuckle.
For those not familiar with the promise design controversy:
http://brianmckenna.org/blog/category_theory_promisesaplus
https://github.com/promises-aplus/constructor-spec/issues/24
https://github.com/promises-aplus/promises-spec/issues/94
-
Why is JavaScript so hated?
If you really want to go down the rabbit hole on this one, start here
-
What the imperative shell of an Functional Core/Imperative Shell language looks like
Advantage 1, nesting, is the most important here, and it's often the most-overlooked advantage. Overlooking nesting is how Promises in Javascript got to be fundamentally broken.
-
[AskJS] Is JavaScript missing some built-in methods?
Have you read the infamous GitHub thread where people tried to fix this before it got finalized? It's quite a trip
-
This typo lasted several pomodoro sessions.
1.) JS implementation of Promise is not a monad. See this StackOverflow answer or this GitHub discussion for more details
-
How to implement Promise in a FAANG interview
In this article, we will go over how to implement a basic version of a promise during a FAANG interview. The standard for promise implementation is called A+, but it includes a huge amount of details, making it almost impossible to implement all of them during a one-hour coding interview. Therefore, we will focus on implementing a basic variation that should be enough to show the interviewer your solving skills.
- what object
-
Oopsy Poopsy ahahaha *sharts uncontrollably*
Hey, at least you weren't these guys: https://github.com/promises-aplus/promises-spec/issues/94
-
Haskell is the greatest programming language of all time ... the rational adult in a room full of children ... When I program in Haskell, I am in utopia. I am in a different world than 99.9% of what I see posted on Reddit.
Total carnage
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?
proposal-symbol-thenable
librope - UTF-8 rope library for C
q - A promise library for JavaScript
caniuse - Raw browser/feature support data from caniuse.com
zx - A tool for writing better scripts
pidove
proposal-set-methods - Proposal for new Set methods in JS
proposal-class-method-parameter-decorators - Decorators for ECMAScript class method and constructor parameters
cats-effect - The pure asynchronous runtime for Scala
search-benchmark-game - Search engine benchmark (Tantivy, Lucene, PISA, ...)
purescript - A strongly-typed language that compiles to JavaScript
proposal-iterator-helpers - Methods for working with iterators in ECMAScript