Svelte caught my attention when they initially released it, but honestly it has become another JS front-end framework to add to the lengthy list of existing ones. I honestly don't see it as a real challenger anymore, especially after I read where svelte kit is going to. To me, I am on the team back to SSR, where thinks like alpine looks way more appealing an easy to integrate with blazor SSR components with the added benefit of removing the convoluted building process of a fully fledge JS framework
I just checked out alpine and I like what I see - I think I might be with you on this! I see people use htmx alongside alpine what are your thoughts on that?
@@Coding_with_Tom As a matter of fact, itis exactly what I am using in my pet project! To me the main benefit is you are forced to use the (web) platform, which is something that usually hides frameworks behind custom abstractions. The pain is the fact you must "rollback" your mindset to the old days of scripting, which can be perceived as going backwards by the "great public". However, modern tooling is better than 15+ years back and the plataform is way more powerful.
@@khalilayari3230 they are going from a simpler alternative to just do what everyone else is doing (SSR + hydration, hooks, signals...) It is just a bunch of complications that makes no sense in a lot of applications. If you are going to be doing what everybody else is doing, chances are better going to a consolidated tool if you are considering going through the rabbit hole of modern JS frameworks
How could we setup sveltekit in such a way to use the routes feature, both static and dynamic routes, the layout feature, and the load function that run before the page loads
I just cloned your repo and it built and ran immediately with no problem. What kind of witchcraft is this?
I am curious how did you deal with the linting errors for the .svelte files? Mine have squiggly lines all over
Svelte caught my attention when they initially released it, but honestly it has become another JS front-end framework to add to the lengthy list of existing ones. I honestly don't see it as a real challenger anymore, especially after I read where svelte kit is going to. To me, I am on the team back to SSR, where thinks like alpine looks way more appealing an easy to integrate with blazor SSR components with the added benefit of removing the convoluted building process of a fully fledge JS framework
I just checked out alpine and I like what I see - I think I might be with you on this! I see people use htmx alongside alpine what are your thoughts on that?
@@Coding_with_Tom As a matter of fact, itis exactly what I am using in my pet project! To me the main benefit is you are forced to use the (web) platform, which is something that usually hides frameworks behind custom abstractions. The pain is the fact you must "rollback" your mindset to the old days of scripting, which can be perceived as going backwards by the "great public". However, modern tooling is better than 15+ years back and the plataform is way more powerful.
I just start learning Svelte. Can you elaborate on what you mean by " after i read where sveltekit is going to" ?
@@khalilayari3230 they are going from a simpler alternative to just do what everyone else is doing (SSR + hydration, hooks, signals...) It is just a bunch of complications that makes no sense in a lot of applications. If you are going to be doing what everybody else is doing, chances are better going to a consolidated tool if you are considering going through the rabbit hole of modern JS frameworks
How could we setup sveltekit in such a way to use the routes feature, both static and dynamic routes, the layout feature, and the load function that run before the page loads