Any comparison of a feature list is going to be skewed in favor of SD, just because it has so many more features.
If you had a table comparing SD7, SD7 Lite, and SE, how would it be different from the existing table?
How would it be less skewed in favor of SD?
I suppose having two tables makes sense from the perspective of different target audiences: existing SD6 users vs non-SD users (SE users). Those that see clutter everywhere would argue that having SD6 in the table adds unnecessary clutter. Perhaps. But for those who like data to make informed decisions, having the SD6 in the table shows the SD is alive and growing, a key feature IMO.
One option to consider is to have two tables, but organized differently:
- Comparison of Major Features
- Make this as short as possible
- This addresses the “clutter” issue, and arguably makes decision-making easier.
- Comparison of All Features
- But highlight the Major features and/or list them first
- For those that want to see everything.
- As an alternative to a separate table, just have a “more. . .” button at the bottom of table #1.
You could also consider showing a small popup on the page on mouseover that defines the feature and provides a link (open on new tab) for details/demo. Personally, I really like this style because it allows me to quickly understand a feature, and get details if I want.
Just my 2¢.