"Yup, I've been there too. I think the biggest mistake newbies make is trying to learn React, Angular, and Svelte at the same time. Focus on one framework at a time, and you'll avoid the confusion and frustration"
"Yooo, been there done that with Svelte. I used to struggle with understanding the component lifecycle, thought it was super complex at first, but once I got the hang of it, things became way smoother. Would recommend checking out the official Svelte tutorial for some clarity."
Yooo, just wanna throw in my two cents - I think a lot of newbies get overwhelmed by the reactive nature of Svelte and try to force imperative code in. Don't do that, just let Svelte handle the state management for you and you'll be golden.
I feel you, learning Svelte can be a wild ride. One common mistake I made was trying to apply too much logic to the markup, Svelte's whole point is to simplify your components, so don't overcomplicate things.
I totally get where you're coming from. I struggled with setting up my project structure back in the day, but a friend turned me on to the Svelte Starter package which helped a ton. Definitely recommend checking it out if you're just starting out.
"Dude, don't even get me started on the whole 'not importing Svelte stores properly' thing lol. I swear, it took me hours to figure out why my app wasn't updating. Anyways, always double-check your imports, fam."
"Yea, I can attest to the common mistake of not using lazy loading for Svelte components. It's a game-changer for performance, and it's easy to overlook, especially for smaller projects. Anyone else struggle with optimizing component load times?"