signals VS solid

Putting the runic terminology aside and looking into how the signal primitive is implemented should dispel the magic. I learned a lot from examining preact's implementation: https://github.com/preactjs/signals/blob/main/packages/core/...

https://refactoring.guru/design-patterns/observer/typescript/example https://indepth.dev/posts/1269/finding-fine-grained-reactive-programming#how-it-works https://legendapp.com/open-source/legend-state/ https://legendapp.com/open-source/state/fine-grained-reactivity/ https://www.builder.io/blog/usesignal-is-the-future-of-web-frameworks https://dev.to/ryansolid/a-hands-on-introduction-to-fine-grained-reactivity-3ndf https://medium.com/hackernoon/becoming-fully-reactive-an-in-depth-explanation-of-mobservable-55995262a254 https://preactjs.com/blog/introducing-signals/ https://hygraph.com/blog/react-memo

All the frameworks are starting to adapt them. You can easily add them to react project as well. https://preactjs.com/blog/introducing-signals/

Signals are a design paradigm for reactive programming which have recently trended in the JS frontend space. For e.g., https://preactjs.com/blog/introducing-signals/

Compare Vue's reactivity system to the principles the Preact authors write about here:

Reactivity libraries are at the heart of modern web component frameworks like Solid, Qwik, Vue, and Svelte. And in some cases you can add fine-grained reactive state management to other libraries like Lit and React. Reactively comes with a decorator for adding reactive properties to any class, as well as prototype integration with Lit. Preact Signals comes with a prototype integration with React. Expect more integrations as these reactivity cores mature.

State solution should not be a framework, this is what I dislike in riverpod as well.. its a FRAMEWORK... compare to the simple useSignal hook that preact has https://preactjs.com/blog/introducing-signals/ this looks like an overkill.

Looks like it's coming from here https://preactjs.com/blog/introducing-signals

Sciter got native (built-in) Signal implementation made after PReact's Signals;

The reactivity core, which is in https://github.com/solidjs/solid This is where you'll see the reactivity runtime implementation. Take note that Solid's reactivity doesn't rely on compile-time magic

I did try this but I'm not sure what you mean with the ssrLoadFrom. Is there any documentation on this, all I could find was the examples folder in solidjs: solid-ssr?

This is very true. I really hate svelte single file components. But then I tried JSX for breaking things down. I love solid but I don't feel really good about angle brackets within C style syntax. I saw this Scala library that stick with simple statically typed function syntax than html tags. I don't understand why people still wants to stick with xml like tags. In laminar markup is written like this scala div( h1("Hello world", color := "red"), inputCaption, input(inputMods, name := "fullName"), div( ">>", button("Submit"), "<<" ) ) I wish solid team makes their HyperScript syntax as performant as JSX.

What is Solid?

import logo from './logo.svg'; import styles from './App.module.css'; import 'flowbite'; function App() { return (

Edit src/App.jsx and save to reload.

Learn Solid, Tailwind CSS and Flowbite Toggle Flowbite modal

Terms of Service

svg> Close modal

With less than a month to go before the European Union enacts new consumer privacy laws for its citizens, companies around the world are updating their terms of service agreements to comply.

The European Union’s General Data Protection Regulation (G.D.P.R.) goes into effect on May 25 and is meant to ensure a common set of data rights in the European Union. It requires organizations to notify users as soon as possible of high-risk data breaches that could personally affect them.

I accept Decline

); } export default App;

There is example of each technique in Solid's main repo: https://github.com/solidjs/solid/tree/main/packages/solid-ssr/examples

I basically came up with an idea that is much like flutter's bloc pattern, and probably waht ryansolid was referring to in his reply to this issue when he said he made his own version of redux that codifies state changes instead of immutable state.

After seeing how inactive this sub was, I took it to Github: https://github.com/solidjs/solid/discussions/1440