svelte

- Svelte seems to have a bit of a problem with large bundle sizes: https://github.com/sveltejs/svelte/issues/2546#issuecomment-... - Svelte might feel (it does to me at least; although I haven't really worked much with it) a bit too magical. In React, you are explicit about the fact that you want to change your variables and how exactly you want to change them (Rich Harris seems to think that such explicitness is excessive verbosity); while in Svelte you just change a value inline, then boom magic happens. It may be a leap forward, like JSX once was; but it also has an uncomfortable feel to it.

I think it's a good idea to include ones that stands out from rest of the pack. https://github.com/sveltejs/svelte and https://github.com/ryansolid/solid stands out by being the only 2 that are compiled to standard js, so no framework is loaded at runtime. Speed is important too and https://github.com/infernojs/inferno (and solid above) is well known for speed and is backed by benchmarks. Not sure if you want to add more beyond this point since a few more will push the boundary to just include everything which is over 100 nowadays.

Looking at the Github commits I’d say neither statement is true? Seems to be plenty of contributors that have contributed recently: https://github.com/sveltejs/svelte/commits/master

Slots are currently an unwieldy band-aid. https://github.com/sveltejs/svelte/issues/1037 (open since 2017) https://github.com/sveltejs/svelte/issues/2079 The simple usage of passing a component to a component, which almost every decently-sized project will make use of, has no convenient syntax, only workarounds: // parent.svelte <script> import Nested from './nested.svelte' import Child from './child.svelte'; </script> <Child> <div slot="bar"> <-- Extra wrapper DOM node <Nested foo="Foo"/> </div> </Child> // child.svelte <slot name="bar" {...data}/> Passing down an element as a prop requires separating the component constructor and its data and manually re-conciliating the two in the child component every time, since components can't be rendered from functions. It wo

Thanks for sharing! On point 1, this issue is the one to watch. https://github.com/sveltejs/svelte/issues/4518 Language server support will work for both JavaScript and TypeScript and error/type checking and editor support should be pretty comprehensive when it's ready. Svelte 3 was written with TypeScript in mind, so the idioms are fairly compatible with type checking. (a nice pit of success for design!) This should also fix reassigning to a const mentioned in point 2.

It's buried in the article, but TypeScript support is being worked on by one of the TypeScript team members in collaboration with the Svelte devs - https://github.com/sveltejs/svelte/issues/4518 The template language's restrictions compared to JavaScript/JSX-built views are part of Svelte's performance story. It's able to optimize things ahead of time that are impossible with dynamic code because of the constraints. Here's a couple tweets from the author about that - 1 - https://twitter.com/Rich_Harris/status/1224414679021301761 2 - https://twitter.com/Rich_Harris/status/948231770725605377 The Svelte template language is quite small, and compositional features like slots and <svelte:component> are powerful. There are currently some unwanted edge-case restrictions as this comment points out - https://news.ycombinator.com/item?id=22541100

Since you've been using Svelte for a few months after using React, haven't you been hit by the lack of composability in Svelte? Passing around components as variables is such a common pattern in React, and there's no good replacement in Svelte. The lack of dynamism in components and styles makes theming and crafting reusable components (outside of simple widgets) very tedious [1][2]. I'm genuinely curious how someone can come from React and not be bothered by it. [1]: https://github.com/sveltejs/svelte/issues/2106 [2]: https://github.com/sveltejs/svelte/issues/1550