It has good performance and also small in size; but limited in docs. Gatsby and Next.js are built on react; it is easy to create blog and website. But in svelte, creating dynamic pages for blog post is quite difficult task.
where's the lack of docs on svelte? it has plenty of docs in many different forms. also, you're not supposed to create dynamic pages for a blog. Use Jekyll, ffs.
well, after using graphql a lot, I hate the ecosystem. it's not flexible at all. I'm talking about the official Apollo things. the docs suck. and about typescript, it's a valid point although I don't use it.
GraphQL can be useful when you don’t have a solid backend service but otherwise just create an endpoint with what you need to request and that’s it ... you can even choose the language for the backend API server: Javascript, PHP, C#, Rust, Scala, whatever you like the most
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It has good performance and also small in size; but limited in docs. Gatsby and Next.js are built on react; it is easy to create blog and website. But in svelte, creating dynamic pages for blog post is quite difficult task.
where's the lack of docs on svelte? it has plenty of docs in many different forms. also, you're not supposed to create dynamic pages for a blog. Use Jekyll, ffs.
Svelte Docs is good; I mean the stuff like Graphql, typescript is the future improvement of svelte.
well, after using graphql a lot, I hate the ecosystem. it's not flexible at all. I'm talking about the official Apollo things. the docs suck. and about typescript, it's a valid point although I don't use it.
Svelte supports TypeScripts since months already.
GraphQL can be useful when you don’t have a solid backend service but otherwise just create an endpoint with what you need to request and that’s it ... you can even choose the language for the backend API server: Javascript, PHP, C#, Rust, Scala, whatever you like the most