4 ms·
When you scan, you're looking for the id or class, not its attributes. I'm a huge fan of one-line and have been doing for 5 years. It's just faster for me.
by antidaily 17y ago
When you scan, you're looking for the id or class, not its attributes. I'm a huge fan of one-line and have been doing for 5 years. It's just faster for me.
- blaix 17y agoRight. And the whole point of the article is that using any modern editor, you can easily scan to find an id or class without resorting to one-liners, which do make the attributes harder to read/write/debug/diff.
- antidaily 17y agoThe debugging argument is a joke - who doesn't have some sort of soft wrap option on their editor? what about people who don't write one-line css but tab nested classes (such as the writer of the article)?
- thedz 17y agoSoft wrapping long one-line css selectors completely defeats the purpose of putting it all on one line in the first place.
- nfnaaron 17y agoNo, it helps people who like one line. You leave soft wrap off normally, and you see your lines the way you intend. If a line extends off the end of the screen, and you don't want to scroll to see the rest, turn on soft wrap to see, then turn it off again.
- JoelSutherland 17y agoFinding isn't the problem. It's understanding the intent and structure of the document by looking at multiple selectors at once.