Thanks for the comparison. A couple of things, if I may be so bold:

When comparing development experiences, make sure the results are visually identical. Basically, in this article one can see how the to-do list in Svelte is basically half the size in terms of lines of code when compared to the one in Vue JS. However, the visual result is wildly different. This takes a lot out of the comparison.

I do realize that some of these articles are based on bibliography that is external to it, and this is usually a good thing. What is not a good thing is to repeat things you read. For example, you say Svelte is not "as flexible" as Vue. If I were to ask you "what does this mean?", would you be able to answer? Can you provide a concrete example in Vue JS that cannot be achieved by Svelte due to its lack of "flexibility"? I would be very surprised if you could.

Finally, a good thing to realize is that Svelte doesn't need a lot of Svelte-specific libraries. One can use many framework-agnostic libraries in Svelte without modification. For example, I created a test project that uses @azure/msal-browser in Svelte. Did I need @azure/msal-svelte? No. The agnostic package was more than enough. Same thing goes for many others, like floating-ui, ChartJS, etc. It is common to see authors bring the smaller Svelte ecosystem as a weakness, but one should realize that Svelte is so close to plain JavaScript that there isn't much hassle in making other libraries work with it.