<@U3W8YSSSV> a lot of features aren't going to be ...
# serverd
dave
10/02/2017, 3:52 PM@tipsy a lot of features aren't going to be simple tickboxes, so the columns could get very wide with explanation. For instance - interceptors/filters are a feature, but are they portable? Can they be composed into stacks that can be reused across applications? Or testing - how much infrastructure is required? How coupled are tests to the framework? Out of container? What is the effort to ditch your framework and port the test to a wire-test to be used for your new implementation? Essays could be written! :) hence, can I suggest that it's inverted so the features are rows :)
Is a matrix even the right solution? One of the nice things about the todo-backend site for example is that there are consistent requirements.. something like that, whilst a shedload more work, at least gives an idea of what your code (could) look like.