This is incredibly, incredibly sad: admin.phacility.com/phame/post/vie
introduced Phabricator to me 6 years ago, and we implemented it at my company after a month-long test. It was life-changing software.
Conversation
Phab saved our asses a ton of times.
My boss would ask: "Why did we decide not to implement this feature? A customer is asking." And within 5 mins I could go from git blame to the specific task documenting why we chose not to implement something. Everything was linked.
1
More importantly, Phab's code review workflow encouraged every change to be squashed into a single commit, to be rebased on top of master. It made deployments and rollbacks trivially simple: secure.phabricator.com/book/phabflavo
(This was how tasks were ALWAYS associated with one commit.)
2
The interface was also incredible for tracking development across many devs. I remember an intern sitting on a couch, writing his internship report simply by going through his Phab activity.
And I remember saving Fridays for reviewing the activity of EVERY dev in my org.
1
1
The only knock against Phab was the lack of good CI support. And I think Gitlab and Github may have finally caught up.
Phabricator was truly incredible software. I'm very sorry to see it go.
2
1
Replying to
Back in ~2015, having to install PHP to use arcanist was something that people at my side didn't really didn't like too.
Had trouble convincing the rest of the engs that it was worth the trouble, despite the fact that they agree that Differential was really good.
1
1
Replying to
Yeah our side bit the bullet (also circa 2015!) and never looked back. I think installing PHP on one's dev machine was a small price to pay — or at least, that was how we looked at it back then!