A summary of the problems outlined in the email:
* Lack of options for support from Phacility
* Free/open source components of Phabricator feeling half-finished because Phacility has redirected development resources to paid features
* Issues with Harbormaster (Phabricator's half-baked CI system)
* Developer's prefer using regular Git to Phabricator's nonstandard workflow, which requires installation of the Arcanist command-line tool (written in PHP to manage patches.
I was just going to eval Phab for my team, your comment identified a deal breaker for us and you've saved me more than a few wasted hours. Thank you
Of course, there is a bit of a learning curve and most engineers already know the standard git workflow. That is a disadvantage of course, but only in the short term. If it's a short project, then I would recommend against it. However, if you're in it for the long run, arc is great.
I feel like the other points (CI, lack of support, etc.) much better show the weak points of Phabricator versus GitHub or GitLab.
The only real downside I've found with using phabricator at work is the lack of a decent built in CI system. You can integrate it with external ones fairly well but that seems like something you shouldn't have to do.
Phabricator is basically cancer.
I'm partial to Gerrit if you're looking for a git native solution with branch, draft, patch, review, iterate workflows with proper merge/rebase handling.
It is a bit different from "GitHub flow" but mostly a big improvement in an organisation context (vs FOSS.)
Media wiki has the best docs but it's a bit dense.
https://mediawiki.org/wiki/Gerrit
This page below has a decent graphic and lots of quick examples to show you how powerful it is to work with git instead of gimping it with a wrapper.
https://mediawiki.org/wiki/Special:MyLanguage/Gerrit/Advance...
I think you need a lessen in sensible writing. You don't like Phabricator, fine. It's not cancer. Not "basically" either.
Would you have preferred I used the word infection? Virus? Aids?
Which one of those metaphors crosses the "sense writing" line for you?
Why does cancer?
There are no closed-source Phabricator components. The email is complaining about development focus being on the wrong parts (the ones paying customers use), rather the ones Haskell uses.