2 ms·
Perhaps another factor for minor popularity of Fossil SCM is a lack of plugins for major IDEs. I don't believe this should be such an obstacle, as most plugins
by nomadbyte 10y ago
Perhaps another factor for minor popularity of Fossil SCM is a lack of plugins for major IDEs.
I don't believe this should be such an obstacle, as most plugins implement only a part of SCM client features, thus asking you to resort to command-line for certain functions. Still, for a lot of developers the expected interaction with "everything" is through IDE. There seems to be a Git or SVN plugin for every possible IDE, yet Fossil lags in that department.
JetBrains has a nice Fossil plugin (for IDEA); that's about it, nothing for VisualStudio, eclipse, Xcode etc. Catch 22 -- no demand, no plugin.
We faced this with our Qt projects, and went on to develop a Fossil SCM plugin for QtCreator:
https://github.com/nomadbyte/qtcreator-plugin-fossil https://github.com/nomadbyte/qtcreator-plugin-fossil
Not that availability of plugins has to be such a big deal for a SCM adoption, but sure this helps a lot to increase any SCM's visibility and accessibility. In case of Fossil this probably will have to be another community effort.