We could transpose the tables: I.e. right now, rows are feature, and columns are implementations. This could be swapped. Either way has pros and cons... Start by listing these pros and cons, so that they can evaluated and weighted
There could even be an option to dynamically switch rows/columns, but that might be overkill... The real question is: What kind of information do people want from these tables, and how can we arrange things to best provide it to them?
We could transpose the tables: I.e. right now, rows are feature, and columns are implementations. This could be swapped. Either way has pros and cons... Start by listing these pros and cons, so that they can evaluated and weighted
There could even be an option to dynamically switch rows/columns, but that might be overkill... The real question is: What kind of information do people want from these tables, and how can we arrange things to best provide it to them?