A problem I find with typography "rules" is that a lot of them read like the ten commandments. They tell you what not to do, rather what to do and rarely talk about exceptions. For example
this table would read better with vertical rules.

Why would it read better? If you had to curve fit any of the observations you would read from top to bottom, a column a time, for example the comet distance. In general (my rule/observation), if you don't need a heading on the first column of a table, you are better off with vertical rules. Note that if you adopt such an approach the table will look better if you minimize the horizontal rules.
There are many exceptions. Any table that has information similar to a table of logarithms, trigonometric functions etc. At a point in time there was the DIN 55 301 (1978) standard that dictated vertical and horizontal rules for statistical tables with the motivation to present data clearly. According to the same standard cells in a numerical table should not be left vacant. If the cell is left empty the value of the data in that cell becomes unclear. If its value is "0" better to state it. An en-dash normally signifies an absence of data. I normally use ditto rather than "''" if the data is the same as the cell above.
Sometimes, no rules might blend with the text better,

In general though as Tufte says, it is better not to imprison your data in grids of cells. This is very common in business reports, where one picks an excel table and shows it in a similar fashion in a publication. If you are in doubt use "Firer's Rules", but it is good to be aware of the exceptions. Tables are meant to be read (otherwise don't include them). Read them aloud as you would a sentence, normally this would give you a clue as to the best way to lay them out as well as to where rules should be placed.
As an aside, the tables are from Newton's Principiae. Astronomical symbols from the package wasysym
.
booktabs
package.booktabs
package in general, I find it very sad that those statements are used by the author as justification to not support vertical lines. There are several good reasons for using vertical lines in certain use cases (like emulating existing layouts, or because you have tables meant to be read vertically), and in those cases, the very nice spacing features frombooktabs
simply cannot be used. :-(