The main point behind it is assuring that the best frameworks are being used. It's both relevant for both sides of any project.

I would like to read that article which talks about feature parity and support. This felt more like a hit piece. I didn't see a lot of evidence of 'best' other than broad generalizations. Would love to hear your followup in a year. I truly hope node.js can become as mature a choice as Rails, but even Ryan Dahl doesn't seem to be convinced that will happen.

We're on the verge of baselining a reference architecture in JavaScript for all our projects. We did the research with parity of features that already exist in Rails (Rails Admin, Devise, Sidekiq, etc).

You might not need a year to, at least, get my thoughts on that.

Do you mind sharing what back office solution you guys found?

Did somewhat the same kind of research for our projects, but unfortunately didn't find anything decent that could really compete with ActiveAdmin/Rails Admin/Trestle in terms of features and maintenance…

Here: https://www.imaginarycloud.com/blog/node-js-admin-panels-str...

Ah, didn't realise there is a blog article about it. Thanks!