3 ms·
Closing li tags is the right thing to do! I always close the kitchen drawer too after putting the scissors back. But I rarely write HTML as content anyway, it's
by exodust 4y ago
Closing li tags is the right thing to do! I always close the kitchen drawer too after putting the scissors back. But I rarely write HTML as content anyway, it's mostly templates for the CMS, where it's best to close the tags.
- recursive 4y agoI too close my kitchen drawers. But not my li tags. Unless I'm using the bastardization known as jsx. The next li closes it automatically, as it's specified to do.
- hinkley 4y ago"everybody knows" doesn't scale, because 1) not everybody knows and 2) you're relying on memorization for people to read your code, which means you're smashing the ladder rungs behind you Software on a team is a performance art. People are either watching you and copying your behavior, or watching you and getting confused. And if you've ever felt overbooked on a project while other people are idle? It's stuff like that that put you into that situation. And since you're the one who did the 'stuff like that', it's at least partly your fault you're in this situation. Stop being a ball hog, and you'll get fewer bruises.
- recursive 4y ago> "everybody knows" doesn't scale Agreed. That's why I prefer to have things written down. In this case, WHATWG and W3C already did the work for us. > And if you've ever felt overbooked on a project while other people are idle? I've seen what you're talking about, but I'm not the one getting overbooked. I'm not generally the one fighting over this stuff. If I get feedback on a PR telling me to add li close tags, I'll probably just do it. If you're using a technology on a daily basis, it will pay big dividends to spend a little time learning how it actually works.