A Junior's perspective on crafting styles
First off, Hello world! my name is Luana Eva and i am a 18 years old software developer, my first ever experience with typing things for a computer was making an html-only website using window's 7 notebook and it shaped a lot of my view on coding;
I found out this platform from a site called ossium and I absolutely love it here, i feel like that's the stuff i should be doing on linked-in, so expect me to treat here as a mainpage for my posts.
So, why is the title of this post "I love Less, Sorry?", I have read two awesome posts about tailwind, one of them being I Don't Like Tailwind. Sorry Not Sorry and I Love Tailwind. Sorry Not Sorry , I love these texts because they both serve to show my problems with supersets and the experience of writing CSS, as someone since day 1 has been an absolute sucker for making things look pretty (since before becoming a programmer I was guiding my life to be an artist) I have a special relationship with CSS.
The fact that CSS doesn't behave like a proper programming language bother me and a lot of it comes from the time i spent learning programming logic, things like variables and while these things are an awesome QOL improvements i can see why they are not in vanilla css.
To be honest, I dont like tailwind either, the writing is messy and I feel less in control over the styling, but for things like an MVP i don't deny how useful Tailwind can be and is on projects, but i think that the author of the original post describes some problems that are incredibly valid for example the fact that a lot of junior and beginners are just speed running the fundamentals of writing code.
From my own experience, if you want a quality of life improvement in CSS and want to still have control and learn you styling, use less, it is incredibly easy and it makes working with CSS so much more pleasant, I think that less does not get the respect and love it deserves.
-Xoxo, Lua
Top comments (0)