Programmer Humor @programming.dev GregorTacTac @lemm.ee 2mo ago

Average CSS

I am not allowed to credit the site that has this disaster. Its owner said "Nobody should see that"

Programmer Humor @lemmy.ml GregorTacTac @lemm.ee 2mo ago

Average CSS

161 4

Programming Horror @programming.dev GregorTacTac @lemm.ee 2mo ago

Average CSS

52 2

80 comments

The author should be killed for indentation alone.
- I know, right? Needs more tab.
- We are witnessing a hate crime.
Client: "Can you switch these two colours, you have 1 minute to fix it or you're fired!"

Result:
- my eyes
color: lime !important; z-index: 1000000;
- I love the superstitious z-index just in case it does something to help.
  
  At least that's actually easy and quick to do and is the only way of doing it. Centering a div however has 81639393 ways and it seems the one that works is different every time
  
  It's a good indicator that someone is desperate and/or doesn't know what they're doing.
Not allowed to credit the site in your text editor?

Is the owner in the room with you now?
- This screenshot is not mine, it was sent to me via Matrix
  
  You get used to it. I don't even see the code
  
  …it was sent to me via Matrix
  
  That’s how they do pull requests there
Well, that's what you get for using classes like "white" and "lime".
- Exactly this. Bootstrap killed the css star.
People learning CSS through shitty frameworks:
At first I only noticed the indent. Wtf
I'm appalled that classes representing visual styles are still a thing. I thought everyone already figured that it was a bad idea back in bootstrap days. But then I recently had an opportunity to work on project that uses Vuetify and saw quite long poems about flexboxes in class names...
- And then came Tailwind…
  
  I know! What a mistake of a framework. Glad my colleagues drummed it out of me.
- Aren't classes in CSS supposed to represent visual styles? What else could they be for?
  
  Pretty sure they're referring to class names describing the visual style being applied, rather than what that class represents semantically.
  
  E.g. .red-bold vs. .error-text
- Well, there's not exactly a ~~class~~ training you have to take before writing CSS, so everyone starting out with it gets to make all those same mistakes for themselves before they know how to use classes sensibly. I myself am some backend guy, who has to write CSS far too often.
  
  It certainly also does not help that various CSS frameworks out there do exactly that...
  
  It certainly also does not help that various CSS frameworks out there do exactly that…
  
  Bootstrap (as of v5) being one of them. div class="d-flex gap-2 my-3 align-items-center flex-nowrap justify-content-between
  
  I was annoyed at this at first, but I’ve since noticed that I write hardly any CSS any more, because most rules really are “just add some space, vertically align, be red”.
- "Figured it was a bad idea" actually means that some people were against it because they believed semantic class names were the solution, I was one of them. This was purely ideological, it wasn't based on practical experience because everyone knew maintaining CSS was a bitch. Heck, starting a new project with the semantic CSS approach was a bitch because if you didn't spend 2 months planning ahead you'd end up with soup that was turning sour before it ever left the stove.
  
  Bootstrap and the likes were born out of the issues the semantic approach had, and their success and numbers are a testimony to how real the issue was, and I say this as someone who never used and despised bootstrap. Maintaining semantic CSS was hard, starting was hard, the only thing that approach had going for it was this idea that you were using CSS the way it was meant to be used, it had nothing to do with the practicality. Sure, your html becomes prettier to look at, but what good is that when your clean html is just hiding the monstrosity of your CSS file? Your clean html was supposed to be beneficial to the developer experience, but it never succeeded in doing that.
  
  There's nothing hard about semantic naming. Especially when you're separating your elements into components and use SCSS or some other pre-processor.
"Some coders just want to watch the word ~~burn~~ get colored white and/or lime."

And if you delete one or the other, or condense the code into a single command, the whole site breaks.
Worse.
- Isn't cascading styles the whole point of Cascading Style Sheets?
  
  You absolute fool. You must never utter its full name, lest you summon its wrath!
- I don't get it, isn't this a pretty normal way of using media queries. Granted you're more likely to see the widths defined in px.
  
  Shhh... The poster doesn't understand CSS and we shouldn't embarrass them in a community with memes
  
  Nowadays we do responsive webdesign instead of micromanaging widths.
I am very, very surprised about the competence of the commenters here. I have had many discussions on reddit about the advantages of meaningful instead of presentational class-naming and you're normally met with great resistance, especially with users of frameworks like Bootstrap and Tailwind.

Here, everyone seems to either 'get it' or is willing to hear why classes like .lime are bad. Very cool.
- People that advocate for presentation naming haven't endured a major company rebrand.
  
  This guy has PTSD from working at "X".
- Frameworks like bootstrap are a cancer.
  
  good for quick and dirty small projects tho...
- It's not too surprising. Consider the sort of person who would have abandoned reddit for Lemmy during the APIcolypse last year.
the userstyle experience:
- Yeah, userstyles are wild. You learn so many ways how to not use CSS. Everything is !important and rather than adjusting the HTML to change the structure, you get to do it all in CSS. 🫠
  
  flex-direction:row-reverse; my beloved
No! I wanted orange!
I hate all webdev beyond using raw HTML, CSS and Javascript to make your own crappy website
- https://motherfuckingwebsite.com/

80 comments