I used Svelte daily as my main framework between 2020 and 2024. Took me a couple of years to realize Svelte's biggest strength is also its biggest issue. Having a custom language means so much effort is needed to build and maintain custom tooling to support it. And not only from the small Svelte team and its community. Eg: Even to this day, the Svelte plugin by JetBrains is trash [2]. If you want to do Svelte you're basically trapped into using their VSCode extension.
Ultimately I ended up moving away to Solid primarily because I can write vanilla TS/TSX. Like it or not, TS/TSX is a standard these days and most editors or IDEs support it out of the box.
Ironically, given the chatter in this thread, I'd say this is a problem very solvable by LLMs. The Svelte language is well defined, the JetBrains API is well defined. No reason why a plugin couldn't be LLM generated.
Seems like a separate issue? I also wouldn't assume that. Svelte is faster and smaller than React, even with all the training data in the world there are still non-negotiables.
pier25 · · focus · HN ↗
Ultimately I ended up moving away to Solid primarily because I can write vanilla TS/TSX. Like it or not, TS/TSX is a standard these days and most editors or IDEs support it out of the box.
[1] <a href="https://plugins.jetbrains.com/plugin/12375-svelte" rel="nofollow">https://plugins.jetbrains.com/plugin/12375-svelte
philipthetenth · · focus · HN ↗
pier25 · · focus · HN ↗
philipthetenth · · focus · HN ↗
afavour · · focus · HN ↗
pier25 · · focus · HN ↗
afavour · · focus · HN ↗