I think React gives you more specially-crafted tools than you suggest and Svelte gives you fewer than you suggest. Even in this case, bind:group is just a shortcut -- Svelte also provides the tools to "do it yourself"…
bind:group is not a "special string" but simply part of the API, in the same way useEffect is part of the React API. bind:group is no more "magical" than useEffect (both are ultimately going to "invoke some arbitrary…
bind:group is explained in the docs (https://svelte.dev/tutorial/group-inputs). I don't think React would be particularly easy to grok without first having read its docs (or some kind of instructional material) either.…
> If code knows which updates to make, it essentially embeds a particular form of the diff algorithm. Having an alternative means of identifying where to make targeted updates on data changes (i.e., via static analysis…
I'm not sure you understood the article. The Svelte compiler does in fact generate code that performs "carefully crafted direct DOM mutations," though it is not hard to maintain, because the compiler handles it. Given…
> Sure, you do a bit of it, and then you're often better doing something else, like enhancing developer experience for example. Aside from its performance optimizations, arguably one of the biggest selling points of…
> However, I've seen the types of transformations the Svelte compiler does and they tend to hide complexity, making it harder to trace and debug code at runtime. Are you saying the original source code hides complexity…
> There's a lot of what I'd consider to be non-trivial transformation going on between the code you pass to the Svelte compiler and what comes out of it and runs in the browser. Personally, I'm less comfortable with…
> I'm saying that OP could do this without crapping all over React's contribution What are some specific quotes from the article that you feel are "crapping all over React's contribution"? Genuinely curious, because I…
> To readers considering Aurelia I would suggest trying Vue as well... And if interested in Vue, check out Quasar [0], a UX framework for Vue (recently made compatible with Vue 2.0) that seems to have a lot of the same…
Use of the GPL doesn't merely prevent commercial developers from creating non-compatible formats -- it prevents them from using Concord at all. Let's say I want to build a commercial app that happens to use Concord, and…
I think React gives you more specially-crafted tools than you suggest and Svelte gives you fewer than you suggest. Even in this case, bind:group is just a shortcut -- Svelte also provides the tools to "do it yourself"…
bind:group is not a "special string" but simply part of the API, in the same way useEffect is part of the React API. bind:group is no more "magical" than useEffect (both are ultimately going to "invoke some arbitrary…
bind:group is explained in the docs (https://svelte.dev/tutorial/group-inputs). I don't think React would be particularly easy to grok without first having read its docs (or some kind of instructional material) either.…
> If code knows which updates to make, it essentially embeds a particular form of the diff algorithm. Having an alternative means of identifying where to make targeted updates on data changes (i.e., via static analysis…
I'm not sure you understood the article. The Svelte compiler does in fact generate code that performs "carefully crafted direct DOM mutations," though it is not hard to maintain, because the compiler handles it. Given…
> Sure, you do a bit of it, and then you're often better doing something else, like enhancing developer experience for example. Aside from its performance optimizations, arguably one of the biggest selling points of…
> However, I've seen the types of transformations the Svelte compiler does and they tend to hide complexity, making it harder to trace and debug code at runtime. Are you saying the original source code hides complexity…
> There's a lot of what I'd consider to be non-trivial transformation going on between the code you pass to the Svelte compiler and what comes out of it and runs in the browser. Personally, I'm less comfortable with…
> I'm saying that OP could do this without crapping all over React's contribution What are some specific quotes from the article that you feel are "crapping all over React's contribution"? Genuinely curious, because I…
> To readers considering Aurelia I would suggest trying Vue as well... And if interested in Vue, check out Quasar [0], a UX framework for Vue (recently made compatible with Vue 2.0) that seems to have a lot of the same…
Use of the GPL doesn't merely prevent commercial developers from creating non-compatible formats -- it prevents them from using Concord at all. Let's say I want to build a commercial app that happens to use Concord, and…