I still like Svelte, but to me SvelteKit has taken up too much of its mind/devshare. Svelte itself is fantastic, especially as a Vue guy I love the "new" reactivity system/runes, but SvelteKit for me is horrible. It's just a hodgepodge of over engineered crap to cater to React/Next devs, and the Svelte team has also been hell bent on horrible decisions like the abomination that is routing[1] in SvelteKit.
To me Kit is the antithesis of what made Svelte so attractive to me originally. Svelte was dead simple and intuitive to use, Kit is anything but.
The router is really baffling, agreed. Magic file names make me so frustrated, and even more so when they all start with the same prefix so all my editor tabs look the same. I wish they’d just make a simple single file router that works the same as every other one. There are a lot of things that aren’t perfect in Vue, which I primarily work on, but the router isn’t one of the things that bothers me. It mostly just works.
Magic files are one thing (and just personally having a filenane beginning with + is just damned ugly). You also even have magic folders, which for me was a first.
Even if I could ignore that, for my super tiny hobby project that I tried Kit with, the routing ended up being strewn across a million folders and files that are called +page nested in (page) folders, and a super tiny app turned into a nightmare to navigate and find things in. I didn't even use any of the stupid SSR stuff, just SPA mode, I can't even imagine what it ends up looking like with +layout and all the server-side files
I don't understand why frameworks that offer file based routing don't provide a way to define routes using either a configuration file or some library calls.
To me Kit is the antithesis of what made Svelte so attractive to me originally. Svelte was dead simple and intuitive to use, Kit is anything but.
[1] https://svelte.dev/docs/kit/routing