Those kind of tables improve readability right until someone hits a length constraint and had to either touch every line in order to fix the alignment, causing weird conflicts in VCS, or ignore the alignment and it's slow decay into a mess begins.

▲

Cthulhu_ 4 days ago | parent | next [-]

It's not an either/or though. Tables are readable and this looks very much like tabular data. Length constraints should not be fixed if you have code like this, and it won't be "a slow decay into a mess" if escaping the line length rules is limited to data tables like these.

	▲	VBprogrammer 4 days ago \| parent [-]
		By length constraint I meant that one of the fields grows longer than originally planned rather than bypassing the linter.

▲

DemocracyFTW2 3 days ago | parent | prev [-]

so you're basically saying "look this is neat and I like it, but since we cannot prevent some future chap come along and make a mess of it, let's stop this nonsense, now, and throw our hands up in the air—thoughts and prayers is what I say!"?

	▲	VBprogrammer 3 days ago \| parent [-]
		At best I'd say it's ok to use it sparingly, in places where it really does make an improvement in readability. I've seen people use it just to align the right hand side of a list of assignments, even when there is no tabular nature to what they are assigning.