Re:Open-sourcing Sonar, a new extensible debugging tool
by avarun on Monday June 11, 2018 @01:18PM
(#17286356)
Facebook has been using it internally for a long time. It would make no sense for them to rename the tool for open-source release just because a naming conflict exists, unless you'd prefer they just not release it at all?
[ Parent
| on HN ]
Re:Open-sourcing Sonar, a new extensible debugging tool
by krschultz on Monday June 11, 2018 @02:31PM
(#17287005)
We typically do rename before open sourcing and intend to avoid namespace collisions. E.g. Litho was not the original name of that framework either.
I am familiar with most of the other tools mentioned here (e.g. SonarJava) from my time doing Java development outside of Facebook and never had a collision in my head because this project is not actually a library or tool for Java. It's a standalone Electron app that works on iOS and Android for debugging purposes, the only Java part is incidental in the Android app (and could be Kotlin or C++ or whatever you want).
Re:Open-sourcing Sonar, a new extensible debugging tool
by batbomb on Monday June 11, 2018 @02:57PM
(#17287317)
SonarQube isn’t just Java, it’s a generic framework for reporting from any language
Re:Open-sourcing Sonar, a new extensible debugging tool
by qznc on Monday June 11, 2018 @01:48PM
(#17286606)
Why not? Google renames every internal tool they release as well. E.g. Blaze -> Bazel and Rietveld -> Gerrit.
Re:Open-sourcing Sonar, a new extensible debugging tool
by cjhopman on Monday June 11, 2018 @02:09PM
(#17286790)
> Rietveld -> Gerrit
That's a bad example. Gerrit is not a new name for Reitveld, it's a totally new implementation (with similar inspiration). And both of those were publicly released under those names.
Your underlying point is quite true, though.