About every project at my last job. Impossible to like any project with a boss that legitimately thinks frames and tables are a better option than learning css.

But why not, attribute styling on html-elements are the future indeed.

"They do it all the time in normal XML" nnngh inline styles make me want to punch things.

Had a senior developer at Zynga Games and formerly of the GTA game series tell me that inline styles are okay on a PHP project we're collaborating on. My response:

"No they're not. Not now. Not ever. You put a fucking class or ID in there right the fuck now. I don't give a shit who you've worked for or what you've done in the past. I may be a shoeless hillbilly from Arkansas, but I've got better sense than that shit."

He tried to pull seniority and some old ass late 90's lingo on me, then called me a diva front end guy that knows nothing about development. I responded:

"I may not know a lot about development, but at least I know better than to put online styles on markup."

That shut him up.

@lquessenberry never style to an ID

@Nexion agreed, but anything in this case was better than inline.

@Nexion plus it was a single use unique tag in the markup, but yeah I only style on classes. Especially with SASS. It just blew my mind that he was writing the styles inline instead of stubbing them out with classes so I could do my work. Now I'm having to change PHP code just to style the markup properly.

Wanna hear something scary? If you wanna use CSS in an HTML email that will be read from the Gmail website, you only can use the style attribute

@CombustLemons Email styling is a special level of hell.

@CombustLemons inline styling for email makes sense, and its one of the only places where inline styling is acceptable imo