Svelt > Sapper anyone?
Hey everyone,
I'm looking into new tech for fun (and for a future project) and Svelte seems refreshing and very easy to get started with (my background is in Angular).
I want it for a server-rendered app, and I see that Sapper is under development. Has anyone tried it in a production service?
I don't think I'll use it in prod but wanted to know how much of a headache I'd get if I start using it even for a side project.
Thanks!
I've started a project with svelte,
Honestly i was amazed with it.
By its simplicity It reminded me of angularjs/ruby, it has an easy to pick up learning curve. Would definitely recommend it for any kind of new side project.
I've tried sapper but honestly for a small-ish side project think ssr is overkill.
In my opinion i prefer to go with templating like mustache or hugo, ror or just ditch the whole ssr and add a loader until data is loaded.
Thank you! The loader won't really be optimal for SEO - ideally we'd have static content that's super fast to render.
I've used Sapper for a couple of small sites. It's very competent and really quick to develop. Routing is an issue, since you have to make that choice yourself. 😅 But otherwise, it's a really nice stable platform. Nextjs has a lot more community support, but if you like and know web fundamentals it's a great choice.
Thank you - I still need to get to know React (and then NextJS). From the crash courses I took so far, I see that it's not difficult but it can be easy to make mistakes since React is an unopinionated library. I have the feeling that many things can go wrong without me noticing, and when I notice errors may not be indicative of the actual issue. I hope I'm wrong..
I don't see this with Svelte. It seems better structured and makes more sense especially with messaging and state management.
Anyway, I can't ignore NextJS so I'll be looking more into it next. Thank you!
This comment was deleted 6 years ago
Thank you - Routify and Strapi look promising. However, I wanted an SSR solution. Strapi doesn't seem to solve that for me (headless CMS). Thanks anyway - useful tools to know about.
This comment was deleted 6 years ago
Thank you! Hmm GraphQL is something I've been trying to avoid, it's yet another learning curve to do something I've already been doing with standard boring REST apis. I do see the huge value GraphQL brings, but I don't think it's worth my limited time yet. Thanks for the useful links!