@AmyShackles
They are! <i>, <b>, along with <em>, <strong> all have their own semantics, albeit slightly different.

@AmyShackles
Two problems:
1. <i> is still semantically incorrect
2. There is no text for accessibility

Two solutions:
1. Use a <span> instead, or use a pseudo element
2. Provide text

@Codex404
Still doesn't make it right.

@alexbrooklyn

That is absolutely not how one should implement a button. That is what the <button> element is for.

And Font Awesome does suggest using <i>, but later concedes that it is semantically incorrect and to use <span> instead.

Font Awesome is using <i> just because most folks are doing it... that is just wrong.

@M1sf3t
React originally had a `createClass` method when it launched, yes. But we"re talking about `class`.

@volttide

Well, this is coming from a "Tech Lead", so I'm like: ...

@Jilano
Unfortunately, it comes from a developer, not a project manager. It's super sad.

There are definitely valid situations for the develop branch to have a different role than development; the problem is that there is not consistent git flow from project to project with this person.

Wow....

I see this ALL the time in job descriptions. And lo and behold, that position still hasn't been filled 6 months later...