Ah! I was taking a look at Coracle’s code some time ago and thinking “maybe I should learn this Svelte thing” 😅
Call me old fashioned, but my go to is still react + redux + redux-saga. Yes it’s boilerplaty, but isolates UI code from state management, from side effects, which makes debugging much faster (no magic). That said, if I was optimizing for performance I’d maybe have to reconsider.
If you're going to be stuck in the past, you could do worse than redux! I actually really like that approach still.
What are you looking into, post svelte?
Too many options, I don't know. I'm interested in learning more about rimmeljs or some other observable thing, stencil for making web components tractable, rust (dioxus?)
Hadn’t heard about rimmeljs 👀
Used stencil a bit and it was quite enjoyable. In rust I played with yew and a bit of leptos, but you end up having to write a lot more stuff yourself.
My question is, what the "Ol Reliable" of frontend development that just works, no frills?
Vanilla JS?
I think it’s all a question of which kind of problems you want to have…
A complex app will have lots of state to manage no matter what. With vanilla JS you’ll have to find a structure for it yourself. Frameworks bring you a structure and a bunch of tradeoffs.
This is basically what I understand about the options out there. I was just holding out some hope that maybe there was something like that.
For me the “old reliable” is react/redux in part due to familiarity, in part cause it solves the problem I value the most - decoupling logic and making it easy to locate where some state update is going wrong.
Something I learned was to not try new tech when building a product I don’t understand yet - and since I spend more time prototyping, I go for the boring stack I’m most productive in.
