Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
DjSall15837yThat's fine with me if you don't reuse the stuff later on, but if you write the same shit on two separate places I'll gladly murder your family, because you could have saved yourself and myself time if you put it into CSS.
The guy I hate the most uses style tags on top of the page. Get a css file, fucking Dumbo's. -
Tawzer15117y@DjSall that is my biggest pet peeve. I worked on a group project in college last year and i had to go back and rewrite all of the css and a ton of the HTML because one guy told the group that it was more efficient to do style tags because you have to have an individual css file for each page :/ he also gave classes to EVERYTHING as in <footer class=“footer”> and <p class=“paragraph”> for NO REASON.
-
nikmanG15387y@Tawzer it’s funny that in the class I’m TAing that sort of stuff loses you points. Not a lot but enough to kinda annoy you for doing unnecessary stuff and inline styling.
-
Tawzer15117y@nikmanG it loses you points in the class I took as well, which is why I went back and rewrote everything. I’m considering posting the before and afters on github just for a laugh 😂
-
inline css is are like lambda functions. Good in situations when we ain't got no time for separate functions.
-
I do it with the display property to quickly hide and show items to work on them.I also use it to quickly test small things, like background color. Inline style would never make it to production code, however.
-
Lyniven45597yOh i can't? Ok then..
Inspect element, right click, copy selector for each style.
Create a css file for each part of the page (header.css, section.css..)
— my dear coworker
Sometimes I write inline CSS because I'm a lazy piece of shit.
rant