I've been around webdev for a while now and I've learnt to approach each day as a newbie. First day using react and i was so astonished at how wonderful it was, from being stuck at the React default src web page to creating components and importing them into your App.js folder. it's marvelous I tell you!!! well I'm still learning; I haven't completed a website yet but I'm working on it plus this is my first post and I'm super excited!! P.S tell me what you think, thank you!!!
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (6)
I can relate to your feeling right now. However, as you move along getting better and better, you start to feel a burden. One day you decide to "see what's out there", and realize that you can do better. Personally, I think Svelte has already beaten all competition. Its simplicity is just brilliant.
thank you for your words of encouragement. I've never heard of Svelte, but I'll be sure to look it up btw what do you consider best practice? writing all your css in the App.css file or each component having their own css file ? cus I've found it difficult debugging the App.css file since it contains a whole lot of css I'm looking for an easier approach
I am probably not the guy to ask this, as I am a back end developer. I am just honing my skills up in the frontend area recently because, as tech team leader of my group, I must decide on the future of my application as a whole.
I will, however, volunteer my opinion based on my tech team leader standpoint: There are 2 important aspects to consider:
The latter is simple to explain: At some point you must learn the rules of CSS. How the browser works. At some point you must realize that you cannot escape this task if you want to master frond-end building.
The former has to do with understanding how modern frontend projects work. It is generally advantageous to import files. This puts them inside the processing pipeline of your build process. If you ever want to master something like single-spa, which is what I'm doing right now, you'll learn that this is your friend, more often than not. Why? Because in single-spa, we want CSS scoped to components. So having CSS per-component is good.
I don't know. I feel like I made a mess of that explanation. Still, there it is.
lol thank you so much it was crystal clear i could see the picture you painted. I'll definitely take what I can from your lesson. thank you once again and just so you know I leave here better than I came
Hi José it's been a while and I've made steady progress since we last spoke looking back at your explanations, they make a whole lot more sense than when I first read them I've improved both my frontend and backend skills favouring backend development. I want to tell you thank you for your kind words and if there's anyway I could be of help I'd gladly avail myself for your service
Hello. Good to hear you're doing well and I thank you for the kind offer.
Since we're catching up, I'll tell you that I mastered
single-spaand even created the only plug-in in the world to createsingle-spaapplications out of Vite-powered projects: vite-plugin-single-spaIt works without a single issue and is now approaching the 13,000 downloads per week.
I have also been drafting a new micro-frontend library, hoping to release before the year's end.