Replies: 1 comment 3 replies
-
The main reason is just my preference, because it is the only modern reactive framework that I have learnt. Also there were a lot of things and code from my another project Uptime Kuma that I could reuse, so that I could kick-start very very fast. Indeed I just used around 3 weeks to build Dockge 1.0.0.
I think we have no choice with Vue? But thanks for introducing SvelteKit, I always thought SvelteKit is just another SPA framework and I never get into it. Didn't know it also doing backend things. It is interesting. I am planning to create Dockge's simple website. I think it is a chance to try SvelteKit. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Don't get me wrong, I love Vue. But I left Vue last year for SvleteKit.
I see that you have a separate backend and front-end. Was there a specific reason for keeping the backend and front-end code separate?
What I really enjoy about SvelteKit is that my server side and client side code live in the same project space. I feel like this provides some key advantages over other systems.
I hope I am not sounding rude, as people love the frameworks they use. TypeScript and Vue are good. I'm curious about people's thoughts on this.
Beta Was this translation helpful? Give feedback.
All reactions