5 ms·
I've been building a medium-scale web application that works as a configurator for 3D models (swapping objects/changing materials) and parsing/storing/syncing t
by h4ch1 4y ago
I've been building a medium-scale web application that works as a configurator for 3D models (swapping objects/changing materials) and parsing/storing/syncing those configurations in real-time along with images, and a lot of metadata that needs real-time updates.
To be honest, it's a breeze until it's not, my single file gets very long, lots of declarations, $: reactive = another reactive variable, derived stores, the dependency graph can get really deep really quickly and it's very important to maintain a sort of heading, and plan ahead, because you can really lose yourself building with Svelte because of how little boilerplate there is.
Even then, 100% recommend it, documentation, and existing issues are sometimes lacking and information is hard to come by, but the Discord is helpful, even though it takes a lot of searching their "forums". Have great hopes for its' future, and it's really fun to build tools in Svelte, I remember giving all my Network Security assignments (transposition cipher, DES/AES, KDC) a nice, clean reactive front-end showing intermediate states of the data being passed around even though a simple cpp file would've sufficed, just because of how fun it's to use Svelte.
- can_center_divs 4y agoMaybe your case is different, as your app is solving a completely different problem. We have been building a somewhat complex CMS system with Svelte the last two years and haven't had any issues, that couldn't be solved because of the lack of information you are mentioning. After this time, literally every other framework seems unnecessarily overcomplicated for me lol. It is a BREEZE compared to writing React imo.
- vaughan 4y agoI wonder if this is a visualization problem. Imagine if you could see the dependency graph visually.
- deleted 4y ago[deleted]
- jazzypants 4y agoIn my opinion, this is yet another area where SolidJS is clearly the better option. The dev tools give you a full visual reactive graph. I like Svelte, but people like to pretend that it's easier than it is.
- mekeor 4y agowhich solid-dev-tool shows are graph?
- jazzypants 4y agoI wasn't aware there were multiple. This one has Ryan Carniato's seal of approval. He talks about it on stream often. Here you go: https://github.com/thetarnav/solid-devtools https://github.com/thetarnav/solid-devtools
- h4ch1 4y agoI think this is what you're talking about ? https://chrome.google.com/webstore/detail/solid-devtools/kmcfjchnmmaeeagadbhoofajiopoceel https://chrome.google.com/webstore/detail/solid-devtools/kmc...
- jazzypants 4y agoYep, that's it. It's in early development, and you have to install an additional library. But, it works wonderfully.
- dmix 4y agoIs there something similar for Vue?
- rk06 4y agoI don’t think vue devtools have this capability. But if you are facing issues with large Vue components, then you should split it into smaller components. And use composables(vue hooks) to split js logic. That will get you quite far
- marcelr 4y agoI wouldnt say this is a problem unique to svelte Ive designed svg based editor systems in svelte & the crucial piece was xstate. I had editors with 7+ states, that is copy line, edit point of line, split line, draw line, etc.. and with xstate, no matter how much i added features each file would be 25-50 lines with some outliers at 80. Id highly recommend it.
- h4ch1 4y agoXstate looks very interesting, certainly going to take a look, thanks!
- dsego 4y agoIs xstate something like redux or mobx?
- phpnode 4y agoit's like a much more structured, and observable version of redux. observable in the sense that not only can you tell what has happened, you can also tell (and visualise) what can happen next
- johtso 4y agoYeah, the first time you realise you can set the disabled state of a button using `state.can('submit')` it feels like magic!