A lot of problems have arisen over in Drupal Land where people have been forced to use things like Composer in order to just test modules out... Take the Commerce Guys "Address" module as a perfect example: To try it out, one must first download and install Git, then download and configure Composer, then issue commands to download Address whereby you're then expected to log into the D8 site to enable the module... That's an awful tech debt just to test something out and because of this, it's acting as incentive for many people to jump from the Drupal ship once and for all.
Does Backdrop have similar workflows and if not, are you guys intended to force users into things like that? I get the value of version control systems and dependency managers but they shouldn't act as prerequisites for using something like Drupal (or Backdrop) as they represent tools some view as necessary while others may not.
I'd love to read your guys' thoughts on this (which I'm sure you've covered already but being new to Backdrop, I've been out of your guys' loop).
Thanks in advance and keep up the great work.
I was excited about D8 but all that went out the window when it would not install on a shared hosting account with out shell access and some convoluted way of installing things. That was it for me for Drupal and have built lot of sites using Drupal since D5.