I envy you for never having issues with VS Code. I have to restart it far, far too often for it grinding to a halt. I'll lose my auto-complete menus completely. Forget auto-completing any paths (like for imports) when it gets to this state. I have to restart my whole computer sometimes.
I have minimal plugins, but have once again removed some more that I thought were helpful, performance got a little bit better again. But we shall see how long it holds up, as I've done this a couple times now in an attempt to gain reliable performance. This is on basically a brand new 15" i9 Intel MBP.
I'm not the only one I've talked to that has random slow-downs like this. I've literally contemplated going back to Sublime Text 2 for my sanity - I just want things to work reliably. Oh, and if you accidentally click on one of your build files, enjoy the system lock-up!
I don't need new features every month in VS Code that I won't use. I just want better performance on the basics so I can get back to being in flow, writing code, solving problems.
You are to the point where you know what CSS can do, and can work your way through building out UIs. From here it's about adopting a system, and a system that will work well with your needs.
Are you building in a react environment? Are you building WordPress websites? Are you just building simple landing pages? Are you building in a team environment? These could all have different solutions, they could also use similar solutions.
But you need to decide how you want to think about CSS. Which to me, is atomic vs component driven.
Atomic is building small reusable classes, then use those classes everywhere in your HTML. It keeps things consistent. [Tailwind CSS](https://tailwindcss.com/) is the winner of this race at the moment. Lots of people are moving to it. There are solutions for standard CSS, SCSS, or even working with it in React type environments.
Component driven is how I think of BEM, "Block Element Modifier". Break things into reusable components, keep your naming structure consistent according to BEM specs.
I personally prefer BEM type of process (break your pieces into components), but with usage of utility classes also, these can be thought of as atomic (one use, like text-align: center;).
I'm going to try Tailwind on a project soon (I've been following it for years), but I will still think of it in a BEM type structure. Things get messy in atomic when you have complex UIs that have different needs across device sizes. I personally have a hard time looking at HTML when one element could have 10+ classes on it if you go pure atomic.
I've kept things consistent without Tailwind with my own set of config (for things like colors, units, font stacks, z-index stack, etc), then various helper functions for things like keeping breakpoints consistent.
There are lots of great resources (look up atomic css and BEM css), you should browse through many of them to get a well rounded picture of how people work with CSS.
But figuring out how you want to think about CSS and putting a system around it seems like where you are. I recommend trying various methods out, and see what works best for you. Just be flexible if you are in a team environment. A team sticking to a defined standard (even if it isn't your favorite) is better than lots of competing standards.
I have minimal plugins, but have once again removed some more that I thought were helpful, performance got a little bit better again. But we shall see how long it holds up, as I've done this a couple times now in an attempt to gain reliable performance. This is on basically a brand new 15" i9 Intel MBP.
I'm not the only one I've talked to that has random slow-downs like this. I've literally contemplated going back to Sublime Text 2 for my sanity - I just want things to work reliably. Oh, and if you accidentally click on one of your build files, enjoy the system lock-up!
I don't need new features every month in VS Code that I won't use. I just want better performance on the basics so I can get back to being in flow, writing code, solving problems.