On a personal level, I would argue that moving code around isn't refactoring either (when I say 'refactor' I mean something like replacing a bunch of ifs with a pattern). Sure, it's an incredibly useful tool in an IDE, but to say that refactor is as simple as that ... well ... it's not. You click and it's extracted and now your refactoring work begins. But in this case, that's a personal level, I also know people who consider the above refactoring :)
About Svelte:
The DX has improved since May, for sure, but I wouldn't call it on par with React. But then again 90% of Svelte is vanilla JS code so is JS DX in Vscode ok? If so, then Svelte's is pretty great. Thing is, classic frameworks did twist a bit the notion of DX in that people have come to expect IDE support . So you've got your snippets and autocompletion for framework specific stuff. But refactor/reformat/etc, that's the JS experience. React adds on top a lot of stuff so you would need more specific abilities in the IDE.
The ecosystem definitely isn't and I wouldn't expect it to catch up. I do wonder what do you mean by mature ecosystem (I sort of got the idea that you mean "production-ready stuff"). If so, a newer technology's ecosystem never catches up with an older one's unless the older one (as a technology) starts to fade in itself. Of course, at some point, through production use, you can say there will be a number of battle tested community stuff out there (and there are) but there are two observations:
again, Svelte si about vanilla JS. There's a lot going on out there and has been since JS came to be. Once I got into Svelte, I never found stuff missing.
personally, I value much more the size and quality of community rather than ecosystem since my experience (I'm mostly a backend developer) has been that for any given ready-made component there will be customer needs that require a degree of customization which will twist your brain. And for that it's good to have general community support and Svelte's, while way smaller than React's, is better in that it's more homogenous and so you get more reliable guidance (eg: with React, you may get suggestions that used to work great yay back in the day, but missing better approaches that would apply now and you might not be able to tell until it's too late)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi,
On a personal level, I would argue that moving code around isn't refactoring either (when I say 'refactor' I mean something like replacing a bunch of ifs with a pattern). Sure, it's an incredibly useful tool in an IDE, but to say that refactor is as simple as that ... well ... it's not. You click and it's extracted and now your refactoring work begins. But in this case, that's a personal level, I also know people who consider the above refactoring :)
About Svelte:
The DX has improved since May, for sure, but I wouldn't call it on par with React. But then again 90% of Svelte is vanilla JS code so is JS DX in Vscode ok? If so, then Svelte's is pretty great. Thing is, classic frameworks did twist a bit the notion of DX in that people have come to expect IDE support . So you've got your snippets and autocompletion for framework specific stuff. But refactor/reformat/etc, that's the JS experience. React adds on top a lot of stuff so you would need more specific abilities in the IDE.
The ecosystem definitely isn't and I wouldn't expect it to catch up. I do wonder what do you mean by mature ecosystem (I sort of got the idea that you mean "production-ready stuff"). If so, a newer technology's ecosystem never catches up with an older one's unless the older one (as a technology) starts to fade in itself. Of course, at some point, through production use, you can say there will be a number of battle tested community stuff out there (and there are) but there are two observations:
again, Svelte si about vanilla JS. There's a lot going on out there and has been since JS came to be. Once I got into Svelte, I never found stuff missing.
personally, I value much more the size and quality of community rather than ecosystem since my experience (I'm mostly a backend developer) has been that for any given ready-made component there will be customer needs that require a degree of customization which will twist your brain. And for that it's good to have general community support and Svelte's, while way smaller than React's, is better in that it's more homogenous and so you get more reliable guidance (eg: with React, you may get suggestions that used to work great yay back in the day, but missing better approaches that would apply now and you might not be able to tell until it's too late)