kalpolintrol

beautiful reminiscence - my question is: where do people influenced by this stuff collect? I suppose its everywhere - you get those once in a blue moon encounters (hello to chap I met in Bulgaria who was travelling around the MIddle East learning the Oud and would regail tales of late 80s / early 90s san francisco). I'm in Europe - a bit dissatisfied - but buzzing.

theyre really not mucking about - just a cursory play in the live preview and it promises to solve basically 99% of the weirdness I encounter in my projects. it makes sense that automatic reactivity for any let was always overkill, and the use of $: in complex scenarios got stringy. $state / $derived / $effect seems elegant and I'm sure will make everyday grokking + maintenance easier ("ergonomics"). bigup

What works for one person might not work for another. It's not one-size-fits all.

Same. Although I've migrated all of my projects to a single SvelteKit monorepo. This is a really disparate mix of things: creative coding sketches, webview GUIs, personal sites.

I find the problem isn't necessarily the opinionated layout of Kit - I respect that they are trying to establish a sane pattern for frontenders to use. The problem is that this is locked down and enforced in the config and adaptors. Perhaps too much influence via way of the zeroconf web hosting services contributors work at.

Most problems I encounter, in particular of the SPA / making-a-quick-sketch kind, could be solved by more hackable control of the build system. Sometimes I'd like my routes in a single file, sometimes excluding some routes, sometimes a different pattern than +page.

If this breaks something, so what? You have the means to fix it or find a way. As it stands I find myself plugging away at an obtuse JSON object, or must make a my-weird-way-of-doing-things fork. Appeal to the maintainers and it reinforces a papa-knows-best attitude.

Just open it up, make the build system hackable - then see how people decide to use it.