Svelte 3: Rethinking Reactivity • Hacker News Board

Re: Svelte 3: Rethinking Reactivity

#181

Post by carlosperate » Wed, Apr 24, 2019, 9:55 AM UTC

mlazowik wrote: post #175

carlosperate wrote: post #174

Is the frustration meter shown in the talk video part of that original benchmark? Or is it something we could run on top of any page? I had a search around, but didn't find anything.

https://github.com/sw-yx/async-render-toolbox https://github.com/facebook/react/tree/master/fixtures/unsta...

Thank you so much!

Re: Svelte 3: Rethinking Reactivity

#182

Post by danabramov » Wed, Apr 24, 2019, 10:02 AM UTC

This is a great talk. During its discussion, I've seen some misconceptions about what Concurrent React is. I hope this thread will be helpful to someone who's wondering why we're continuing work on that approach: https://twitter.com/dan_abramov/status/1120971795425832961

Re: Svelte 3: Rethinking Reactivity

#183

Post by simplify » Wed, Apr 24, 2019, 2:55 PM UTC

Looking at the talk, how is this different from markojs?

Re: Svelte 3: Rethinking Reactivity

#184

Post by [deleted] » Sun, Apr 28, 2019, 3:22 AM UTC

wontoncc wrote: post #33

I'm wondering how good Typescript support is. Can I use Typescript in the component script?

[deleted]

Re: Svelte 3: Rethinking Reactivity

#185

Post by ryansolid » Fri, May 03, 2019, 9:44 AM UTC

machiaweliczny wrote: post #42

Nice handling of reactivity - I think this should already be in language as well. I'm not sure I like this single components approach and embedding JS in HTML. The problem with this is that it's too frameworkish. The big benefit of JSX/React rendering is that it's composable and declarative (as it's just functions), but it's also simple to get - render just returns wanted structure, given the state and you can use si…

Check out my library DOM Expressions(https://github.com/ryansolid/dom-expressions#readme) It's almost exactly what you are talking about. The libraries I've written on top (Solid.js, MobX JSX, and KO JSX) are among the fastest on the JS Frameworks Benchmark(https://krausest.github.io/js-framework-benchmark/current.ht...). The future is already here.

Re: Svelte 3: Rethinking Reactivity

#186

Post by ryansolid » Fri, May 03, 2019, 9:53 AM UTC

rich_harris wrote: post #90

Vinnl wrote: post #88

Earlier quoted context omitted.

Funny: problems I think are important are "ship less code" and "read less code" (and perhaps "require reading less code to understand what's going on"). The writing part is not something I've considered to be especially problematic, thus far.

Allow me to try and convince you of its importance :) https://svelte.dev/blog/write-less-code

Yeah I don't know. More noise sure but I fear Svelte just misses the point. I'd write a rebuttal but I sort of already have: https://medium.com/@ryansolid/what-every-javascript-framewor...