4 ms·
Optimizing for readers definitely excludes lists like: 2. 3. 5. 6. 1.
by hyperpape 6y ago
Optimizing for readers definitely excludes lists like:
2.
3.
5.
6.
1.
- setr 6y agoTbf it’d be trivial to have a button/flag to fix it in the source, and a warning to notify the user. It’d might be debatable to do so automatically, but on demand there’s no issue (like words table of content update/warning). But the current definition of “its always sequential, that’s it” means you could do it automatically without changing meaning. Whereas do-as-I-say is stuck with being unsafe, always