3 ms·

For me, the biggest downside to Svelte is the lack of TypeScript support. This is a massive deal-breaker for myself as well as many other developers. I am also

For me, the biggest downside to Svelte is the lack of TypeScript support. This is a massive deal-breaker for myself as well as many other developers. I am also not a fan of the Moustache/Handlebars inspired templating, it feels outdated in the face of enhancing standard HTML or going in the direction of something more extreme like JSX. I think Svelte is refreshing, but I would not be comfortable using it on a large-scale web application just yet given the downsides, particularly an enterprise LOB application with many moving pieces. This is why frameworks like Angular, Ember and Aurelia on the front-end lend themselves better to the enterprise and React and other more component-based libraries do not. In terms of community size, I don't think that matters in 2020. You don't need a big community if you have something straightforward and easy to work with. Great read.

aarpmcgee 7y ago
I submit that any large Ember codebase is intractable without Typescript.
- mdgrech23 7y ago
  I submit that Typescript is largely overrated, adds unnecessary complexity and fails to catch a large number of issues at compile time that it should in fact catch.
  - top_kekeroni_m8 7y ago
    Like what?
  - DigitalSea 7y ago
    What are you basing this on?
overtowed 7y ago
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 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 https://twitter.com/Rich_Harris/status/1224414679021301761 2 - https://twitter.com/Rich_Harris/status/948231770725605377 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 https://news.ycombinator.com/item?id=22541100

aarpmcgee 7y ago

I submit that any large Ember codebase is intractable without Typescript.

mdgrech23 7y ago
I submit that Typescript is largely overrated, adds unnecessary complexity and fails to catch a large number of issues at compile time that it should in fact catch.
- top_kekeroni_m8 7y ago
  Like what?
- DigitalSea 7y ago
  What are you basing this on?

overtowed 7y ago

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 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 https://twitter.com/Rich_Harris/status/1224414679021301761 2 - https://twitter.com/Rich_Harris/status/948231770725605377 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 https://news.ycombinator.com/item?id=22541100