Hacker NewsRip language. Compiles to ES2022. Built-in reactivity
https://github.com/shreeve/rip-lang
#HackerNews #RipLang #ES2022 #Reactivity #Programming #Language
Jan 
Reactive programming in #Rust - Observability - by Ivan Enderlin (@hywan)
https://mnt.io/series/reactive-programming-in-rust/observability/
eyeball - Add observability to your Rust types! - by @hywan and @jplatte
Sycamore – next gen Rust UI library powered by fine-grained reactivity
#HackerNews #Sycamore #Rust #UI #library #reactivity #nextgen
N-gated Hacker News🥴 Ah, the age-old dilemma: to push or to pull 🤔. Our brave author embarks on an epic quest of #overexplaining the obvious, inventing a mythical "push-pull" combo like it’s the Fusion Cuisine of #Reactivity. 🧙♂️ Because who doesn't love wading through #algorithmic #soup to solve a problem no one had? 🍜
https://jonathan-frere.com/posts/reactivity-algorithms/ #pushpull #FusionCuisine #HackerNews #ngated
https://jonathan-frere.com/posts/reactivity-algorithms/ #pushpull #FusionCuisine #HackerNews #ngated
Pushing and Pulling: Three Reactivity Algorithms | Jonathan's Blog
It’s looking like I’m going to need to build a reactive engine for work, so I’m going to prepare for that by writing down what I know about them. I want to look at three ways of building reactive engines: push reactivity, pull reactivity, and the hybrid push/pull combination that is used in a bunch of web frameworks. The Problem Statement The simplest way to visualise reactivity, in my opinion, is as a spreadsheet. You have a series of input cells, containing your initial data, and a series of output cells containing the final results. In between are many more cells containing intermediate computations that need to be done to figure out the final results.
Pushing and Pulling: Three reactivity algorithms
https://jonathan-frere.com/posts/reactivity-algorithms/
#HackerNews #Pushing #Pulling #reactivity #algorithms #tech #blog #programming
Pushing and Pulling: Three Reactivity Algorithms | Jonathan's Blog
It’s looking like I’m going to need to build a reactive engine for work, so I’m going to prepare for that by writing down what I know about them. I want to look at three ways of building reactive engines: push reactivity, pull reactivity, and the hybrid push/pull combination that is used in a bunch of web frameworks. The Problem Statement The simplest way to visualise reactivity, in my opinion, is as a spreadsheet. You have a series of input cells, containing your initial data, and a series of output cells containing the final results. In between are many more cells containing intermediate computations that need to be done to figure out the final results.
RetroBetchReactivity will continue to be a bit of a bitch until we figure out how to just use quantum entanglement.
Robin MilletteDepuis longtemps, j'ai choisi SolidJS au lieu de React (ou Vue, Svelte, Angular...). Un de ces jours, je me pencherai peut-être sur qwik mais entre-temps, voici enfin la version 2-beta de Solid!
westbrook#signals friends.
#reactivity friends.
#webDev friends.
Thoughts on https://github.com/proposal-signals/signal-utils/issues/100 and being able to both depend on and change a value in a `reaction()`?
Leveraging `reaction()` with dependencies in the effect. · Issue #100 · proposal-signals/signal-utils
I'm looking at using a reaction like this: https://codepen.io/Westbrook/pen/QwNJdBK?editors=0010 import { Signal } from 'https://unpkg.com/signal-polyfill?module'; import { SignalSet } from 'https:...
FACCTsFukui functions provide an effective way to estimate molecular reactivity and pinpoint reactive sites. With #WEASEL, you can visualize these functions and compute all associated indices easily using just one command!
Learn more about WEASEL and its workflows at www.faccts.de/weasel
#FACCTs #CompChem #QuantumChem #Fukui #Reactivity #WorkflowAutomation
Frontend DogmaBeyond Signals, by Ryan Carniato, by @ryansolid.bsky.social (@jetbrains.com):
