KDE moved because Phabricator is practically abandoned and KDE can't take it over.
Furthermore, all KDE development is based on git and Phabricator abstracts the versioning systems, making the naming of things weird. They require weird cli integration (arcanist) not to rely on git semantics.
Most contributors expect gitlab/github kind of workflows on the other hand. It's really not great to make newcomers learn how to use arc (which is really not that good and barely used elsewhere) when they can learn proper git commands that will be useful for them in many aspects of their professional life, or just reuse the knowledge if they're already familiar.
I understand whoever wrote the article didn't want to be complaining about Phabricator as much as talking about how good gitlab is.
Did facebook stop using it internally? I'm personally in the phabricator camp, but if it lost the backing of facebook I'd be seeing the writing on the wall.
The GNOME Editor is hardly a good place from which to cast such criticism, though. Gedit pulls in a whole load of entire external Desktop Bus services in order to work, and indeed a second Desktop Bus, not only some shared libraries inside the editor process. Moreover, that editor process isn't the one that one might naïvely think it to be.
Furthermore, all KDE development is based on git and Phabricator abstracts the versioning systems, making the naming of things weird. They require weird cli integration (arcanist) not to rely on git semantics.
Most contributors expect gitlab/github kind of workflows on the other hand. It's really not great to make newcomers learn how to use arc (which is really not that good and barely used elsewhere) when they can learn proper git commands that will be useful for them in many aspects of their professional life, or just reuse the knowledge if they're already familiar.
I understand whoever wrote the article didn't want to be complaining about Phabricator as much as talking about how good gitlab is.