Using node taking the following into consideration
Can be fully GPL
Will be a server based tool
>>Yes, actually it'll run on a desktop - if you want to configure it like that. This was one of the considerations in the Matrix compiled by Dennis.
Low barrier to adoption
>> Using npm we could publish the Adapt editor as a package and users could run a bunch of npm commands to get the Adapt node app installed
Able to achieve mass adoption
>> We will only achieve mass adoption if the tool/framework is useful.
Originally I'd have liked to have used a framework/CMS (like Drupal) where we'd get some functions for free (user maintenance) plus the ability to get plugins already developed by others (Single Sign On).
As we progressed through the requirements, with multi-tenant, being a big must have it was pretty clear that whatever existing framework/CMS we picked there was always going to be a fair bit of core-hacking involved, which from experience is painfully difficult to maintain, upgrades become difficult and so on.