Regarding your question, I hate to say it, but out of my recommendations most of my clients are tending towards either Woo or Shopify. I actually personally prefer Magento for most reasons, and still have clients who are happily trading with M1, both OS and Enterprise, but the customers on M2 feel that they've been burnt by the constant show-stopper bugs (mostly in regards to integration with other systems).
I really hope that I'll be able to start recommending M2 to clients again, as I've worked with Magento for many years and I know the system well. I feel it gets a lot of things right, but the M2 bugs have been frankly embarrassing, and have led to uncomfortable conversations with clients where I have to explain that yes, the old M1 site worked perfectly, but the new site that they're spending money on still has 3 month old bugs that I can't provide an update on, or even an ETA for resolution.
I look forward to Magento hopefully fixing the major issues with M2 in the near future.
P.S. I realised that I didn't actually post the URL to the bug I mentioned in my previous post. It's https://github.com/magento/magento2/issues/6683 ("Products updated_at field is not updating on save") which seems related to a couple of other bugs pertaining to "updated_at" fields not being modified.
From what I can tell, it's in the high priority backlog. Hopefully that means some progress along with... lots of other things. But, let's wait until we have some demonstrated burn down before we pop champagne.
Regarding your question, I hate to say it, but out of my recommendations most of my clients are tending towards either Woo or Shopify. I actually personally prefer Magento for most reasons, and still have clients who are happily trading with M1, both OS and Enterprise, but the customers on M2 feel that they've been burnt by the constant show-stopper bugs (mostly in regards to integration with other systems).
I really hope that I'll be able to start recommending M2 to clients again, as I've worked with Magento for many years and I know the system well. I feel it gets a lot of things right, but the M2 bugs have been frankly embarrassing, and have led to uncomfortable conversations with clients where I have to explain that yes, the old M1 site worked perfectly, but the new site that they're spending money on still has 3 month old bugs that I can't provide an update on, or even an ETA for resolution.
I look forward to Magento hopefully fixing the major issues with M2 in the near future.
P.S. I realised that I didn't actually post the URL to the bug I mentioned in my previous post. It's https://github.com/magento/magento2/issues/6683 ("Products updated_at field is not updating on save") which seems related to a couple of other bugs pertaining to "updated_at" fields not being modified.