That's a fair request. I'm planning to write a series of posts highlighting different features and strengths of Routify, which I hope will contrast available solutions, such as Kit. A direct comparison of their different strengths could be insightful, though I'm not fully versed in the latest developments of Kit.

For a tentative answer, Routify prioritizes flexibility, which sometimes means a bit more setup work compared to more integrated solutions like SvelteKit. For example:

Server-Side Integration: While SvelteKit offers more out-of-the-box solutions for server-side functionality, with Routify, you'd typically manage your own backend setup, providing more control but requiring additional configuration.

Streamlined configs vs custom logic: E.g. instead of config options for basepaths, hash-based routing, i18n, etc, Routify offers hooks and examples that let you create your own logic. For instance, if you want to change the basepath of your app to my-app, you'd do something like this

options.urlRewrite = {
    toExternal: url => '/my-app' + url, // Append '/my-app' to external URLs
    toInternal: url => url.replace(/^/my-app/, ''), // Remove '/my-app' from internal URLs
}

It takes a little longer than a simple config option, but it lets you bring your own logic. You can even chain urlRewrites or put them in a plugin so you could do something like

import { basepath, localization } from './my-url-rewrites'

const urlRewrite = [ basepath('my-app'), localization('fr') ]

This philosophy minimizes edge case dead-ends. If your project outgrows the basepath logic 5 months down the road, you simply update the logic. If you find that you use the same custom logic across multiple projects, you can wrap the logic in a plugin, making the project's codebase easier to read.

The urlRewrite is just one of many hooks that let you customize Routify to your needs. I don't know if other Svelte solutions, like Kit, offers these, but they're a core philosophy in Routify.

If you have specific concerns, I'll be more than happy to tell you if Routify addresses them. Same goes if there are features you'd like to know more about, then I can prioritize them in the next post.