js-proposal-algebraic-effects
proposal-signals
js-proposal-algebraic-effects | proposal-signals | |
---|---|---|
3 | 5 | |
174 | 2,379 | |
- | - | |
0.0 | 8.5 | |
about 3 years ago | 2 months ago | |
JavaScript | TypeScript | |
- | MIT 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.
js-proposal-algebraic-effects
-
Proposal: Signals as a Built-In Primitive of JavaScript
I have to admit: you're perfectly right here. React of course always relied on mutable state in it's implementation – just so we don't have to. I derailed a lot here to keep this funny thread going ;) I'm still not with you on your definition of "functional", since you treated it synonymously with "purely functional". Functional means just made by applying and composing functions, and react UI is created exactly like that. There is an awesome algebraic effects proposal[1], which will hopefully will be added to JavaScript one day, then react will make use of it to become purely functional.
1: https://github.com/macabeus/js-proposal-algebraic-effects
-
Letlang, a programming language targetting Rust - Road to v0.1
Super interesting, there is a proposal to add this to JavaScript and several languages that use this, unison, koka & eff. I had no idea this was even a thing!
-
Go Replaces Interface{} with 'Any'
Ok I was wrongly assuming that panic was expecting an error type, in fact it's an interface{}.
> Your use of exceptions for flow control (i.e. goto) is considered harmful
Exceptions are a way to delegate error handling to the caller by giving them informations about the unexpected behavior. It implies that the expected behavior is the "happy path" (everything went well) and any deviations (errors) is unexpected.
This is far from a goto because you can have `try/finally` blocks without catch (or defer in golang).
Also, exceptions are just a kind of algebraic effects that do not resume. There was a proposal to JS for this: https://github.com/macabeus/js-proposal-algebraic-effects
This is also easier to test. assertRaises(ErrorType, func() { code... })
Almost every Go library I've seen just return an error (which is just a string), you'd need to parse it to assert that the correct error is returned in special conditions.
proposal-signals
-
This Month in Solid #2: Welcome to ClownTown, Start docs, and more 😎
🤩 JavaScript TC39 Signals standard proposal
-
🤯 Keep Up With these 50 Articles
A proposal to add signals to JavaScript (https://github.com/proposal-signals/proposal-signals) by Rob Eisenberg and Daniel Ehrenberg Personally, I like the addition, but I'd prefer some refinement on the proposal first.
-
HTML Streaming Over the Wire 🥳: A Deep Dive
Regarding the first point, Brisa obviates the need to pass data for stateful components, as client components utilize real DOM elements, namely web components. When attributes are modified, they react to changes using signals, updating their content while preserving the state. Hence, use native constructs—web components, signals (currently as a proposal in TC39 with stage 0), and HyperText Markup Language—made more sense.
-
Episode 24/13: Native Signals, Details on Angular/Wiz, Alan Agius on the Angular CLI
View on GitHub
- Proposal: Signals as a Built-In Primitive of JavaScript
What are some alternatives?
mux - A powerful HTTP router and URL matcher for building Go web servers with 🦍
exhaustive - Check exhaustiveness of switch statements of enum-like constants in Go source code.
errors - Simple error handling primitives
rustic_result - Result monad for Elixir inspired by Rust Result type