What dif­fer­enti­ates front-end frame­works

Post by svieira » Thu, Jul 20, 2023, 3:20 AM UTC

nwienert wrote: post #164

aluminum96 wrote: post #131

> To overcome the shortcomings of the default change detection paradigm, the Angular team is working on a new approach called Signals. Conceptually, signals are similar to Svelte stores (which we’ll get to later), and fundamentally, they solve the change detection problem the same way as React; the framework is taking control over the application’s state so that changes can be easily monitored and re-renders can be a…

Signals have their own shortcomings as well. Once you leave the "re-run the render function on state change" you suddenly are dealing with implicit dependencies, stale closures, cyclical updating, and all sorts of weirdness in debugging things, figuring out what triggered what, etc. Signals as a concept existed well before React and I think part of the genius of React is actually not using them. In a way a signal is…

Post by em-bee » Thu, Jul 20, 2023, 3:34 AM UTC

onsclom wrote: post #155

rubymamis wrote: post #6

QML wins with bindings and signal and slots! (In this example the the text property of the Text componenet is binded to count , so whenever count changes the text changes). ``` property int count: 0 Button { onClicked: { count--; } } Text { text: count.toString(); } Button { onClicked: { count--; } } Button { onClicked: { incrementLater.start(); } } Timer { id:incrementLater interval: 1000 onTriggered: { count++; } }…

Having used both QML and Svelte, I enjoy Svelte a lot more. The reactive APIs are very similar, just declare variables, mutate them, and use them. But Svelte is much nicer for many reasons: 1. It uses modern JavaScript and not some limited custom ES5-like JavaScript 2. Svelte can be used with TypeScript so your UI code can be statically typed 3. The integration with Svelte and VSCode is much better than QML and Qt Cr…

Post by nwienert » Thu, Jul 20, 2023, 3:47 AM UTC

svieira wrote: post #171

nwienert wrote: post #164

Earlier quoted context omitted.

Signals have their own shortcomings as well. Once you leave the "re-run the render function on state change" you suddenly are dealing with implicit dependencies, stale closures, cyclical updating, and all sorts of weirdness in debugging things, figuring out what triggered what, etc. Signals as a concept existed well before React and I think part of the genius of React is actually not using them. In a way a signal is…

> I think part of the genius of React is actually not using [signals] Except that with the introduction of hooks (aka "OCaml 5.0 effects, but in JS, as a UI framework") you get some of the same interesting issues cropping up in React codebases as well, just spelled differently (stale closures, implicit dependencies, weird debugging issues)

Post by onsclom » Thu, Jul 20, 2023, 4:13 AM UTC

em-bee wrote: post #173

onsclom wrote: post #155

Earlier quoted context omitted.

Having used both QML and Svelte, I enjoy Svelte a lot more. The reactive APIs are very similar, just declare variables, mutate them, and use them. But Svelte is much nicer for many reasons: 1. It uses modern JavaScript and not some limited custom ES5-like JavaScript 2. Svelte can be used with TypeScript so your UI code can be statically typed 3. The integration with Svelte and VSCode is much better than QML and Qt Cr…

how would the above QML example be implemented in svelte?

  
   let count = 0
  
  
  count--}>decrement
  {count}
  count++}>increment
  setTimeout(()=>count++, 1000)}>
   increment later
  

Post by whartung » Thu, Jul 20, 2023, 4:21 AM UTC