I'm not saying it's a bad thing man i understand the situation in fact i'm pretty excited to see what Trails has to offer, I was even hoping to make waterlock trails compatible or work on something for Trails. I'm just saying it's important to keep these things upfront, i commend you and your company for taking on this task and like you said before (somewhere i forget) it's refreshing to be transparent about the motivations and issues at hand.
HN user
duhruh
[ my public key: https://keybase.io/duhruh; my proof: https://keybase.io/duhruh/sigs/x6mYpd7aBZVK-Wq21RAaYpy9yxBvDoXtA5cpxf8rNss ]
Yea I've noticed this too, mostly because Travis threw up a comment on multiple GH issues on my Sails library e.g. https://github.com/waterlock/waterlock/issues/99#issuecommen...
I've looked over these issues and noticed Travis is just copy/pasting the same message stating "Sails.js is no longer actively maintained". It seems like this guy has a real vendetta against Mike (the creator of Sails) and is dead set on getting all current developers of Sails libraries to either make their library trails compatible or die. This guy really doesn't like Mike and even though he has some good points on making a new framework it seems there might also be some personal issues driving this decision.
A better alternative to your simple a/b test would be the multi-armed bandit algorithm. This will give you your answer the fastest, though it's slightly harder to wrap your head around check it out here: http://stevehanov.ca/blog/index.php?id=132
So really, any form of financing a company would be considered debt.