Earlier quoted context omitted.
Then there's "I've been writing frontends since Javascript was a thing and I think developing for the frontend with anything but Typescript is more effort than its worth and a little bit ridiculous, but maybe I'll give something with WASM a try when it's more mature"
If you're a Rust programmer Leptos looks pretty intriguing. It uses Signals like SolidJS.
Thoughts on Svelte(Kit), one year and 3B requests later
171–180 of 222 posts
Re: Thoughts on Svelte(Kit), one year and 3B requests later
#172We have recently moved our website[1] to SvelteKit. Previously we were on Sapper. Previous to that we used a custom Webpack + React setup to output a static site. Our desktop app builder is also built on Svelte (not SvelteKit). I agree with pretty much everything in this article. I wouldn't put "Reactive declarations and statements" in the "Ugly" section though. They are definitely a bit tougher to fully grok than th…
Now I always keep my reactive statements below my regular js statements, to remember.
Also I think it would have been clearer to call onMount, afterMount
Re: Thoughts on Svelte(Kit), one year and 3B requests later
#173Earlier quoted context omitted.
Could you please give a heads up what makes Seveltkit difficult in a larger code base?
I have tried to use sveltekit once and turned around in 20 minutes as routing is severely limited. All I wanted to do was to route based on domain, with a different set of routes for one of the domains. Not exactly complicated or uncommon, but not something you can do with the sveltekit router.
Re: Thoughts on Svelte(Kit), one year and 3B requests later
#174Earlier quoted context omitted.
> you can't code anything without async I'd like to understand what you mean by this. As soon as you introduce network requests in a system, don't you need to deal with asynchrony?
You can just wait for the network request to finish before continuing. Many actions require it anyway. Asynchronous code should be intentional and deliberate in my opinion, but in modern JS/Node it is the default which leads to all kinds of crazy workarounds, callback hell and race conditions. Node has the same issue PHP had now, where green devs will crank out code without realising they need to be watching out for…
Callback hell? When was the last time you gave an honest effort into JavaScript?
Re: Thoughts on Svelte(Kit), one year and 3B requests later
#175Earlier quoted context omitted.
I like Svelte but I’m not sure I’d describe it as “minimalist”. It’s a new language with its own compiler and reactivity system.
Yeah, I did a project in sveltekit + go and then one in htmx, alpinejs + golang. Sveltekit is quite big and not low maintenance. Not sure what exact use case sveltekit would be good for, that can't be solved with htmx + alpinejs.
Re: Thoughts on Svelte(Kit), one year and 3B requests later
#176Earlier quoted context omitted.
What does that mean?
It means that library maintainers are having to make changes to their libraries to get them to work on the serverside, and a lot of them aren't not really doing that very quickly.Consequently moving to RSC reduces the number of libraries that work with your React code. It's a short term problem because most popular libraries will get updated eventually, but some won't and they'll only ever work on the client side. In…
Re: Thoughts on Svelte(Kit), one year and 3B requests later
#177I like the fact minimalist approaches, like svelte, htmx and alpine.js are getting more and more traction. I felt like fighting this fight alone for years in the golden years of node, webpack and react where everybody was creating crazy stacks and adding GraphQL and so on, to basically get what Django + jquery did 10 years ago in a tenth of the time and code. So far I also survived: - xml is the future - let's use no…
Re: Thoughts on Svelte(Kit), one year and 3B requests later
#178I like the fact minimalist approaches, like svelte, htmx and alpine.js are getting more and more traction. I felt like fighting this fight alone for years in the golden years of node, webpack and react where everybody was creating crazy stacks and adding GraphQL and so on, to basically get what Django + jquery did 10 years ago in a tenth of the time and code. So far I also survived: - xml is the future - let's use no…
Honest question: how is htmx/svelte/alpine any different than other trends? Could it just be that you prefer this particular spot in the trend cycle?
Re: Thoughts on Svelte(Kit), one year and 3B requests later
#179Re: Thoughts on Svelte(Kit), one year and 3B requests later
#180I've used Next.js quite a bit, but once I tried SvelteKit, I never looked back. One of the things I built with it is https://landing.gallery/
Please change the heading font at landing gallery. I thought something was wrong with my glasses as the font characters distorted.