Don't take it wrong.
If I want to see hardware specs I need to scroll a screen to the right by using friggin keyboard arrows (slow clap for the web designer).
By the time I got to the hardware specs I have lost sight of the router name. If I need to look at things I need to order them and then remember how many records it goes down, scroll to the left a screen, and see the names.
Is that a readable table for you? Do you program only in assembler perhaps? Have you never ever seen a table in a website or paper or whatever? Have you seen the dd-wrt one?
I don't see why I need to know what index number is a specific router in the table/database. Table maintainers do. What about making a "maintainer view"?
We don't like abbreviations which need to be explained.
Then use abbreviations that don't need to be explained. Like making "Available" column and setting a X for the available ones, nothing for the unavailable/unknown ones.
Reason: Those are quite different information.
Supported since Rev + Supported since Rel are redundant.
You either list the trunk rev if it isn't already supported by official release OR the release.
Still, leaving both link to trunk rev and release version in the same cell is fine too.
Because if it is supported by a official release the "Supported since Rev" becomes wasted space in the table, if one needs to compile old trunk versions can go fetch the very-less-used info from the specific router's page or something.
The links I see in your screenshot do not waste any space.
Yes they do, and for no good reason. leave a link icon and save the space occupied by the url.
It' something you don't see that wastes space. Scroll to the right.
Do you realize that to see the info I need you force me to scroll for at least a screen's worth for no reason?
That table has to be readable by humans, not by machines. Please keep in mind usual human limitations when designing it.