I use this tool every day at FB and it's awesome. I highly encourage you to try it and see if it fits into your workflow!
Open-sourcing Sonar, a new extensible debugging tool
11–20 of 47 posts
Re: Open-sourcing Sonar, a new extensible debugging tool
#12I use this tool every day at FB and it's awesome. I highly encourage you to try it and see if it fits into your workflow!
Glad to hear the tool works well for FB employee's. As always the contribution to the community is much appreciated. But as others have pointed out, the tool name could use a rebranding. The popular SonarCube is just one example where confusion can arise.
Re: Open-sourcing Sonar, a new extensible debugging tool
#13I agree unique naming is one of the fundamental pillars of modern coding , or else we would have chaos with stupid generic completely unrelated names like
Python, C, Java, Go, Swift, Ruby, Assembly, Basic, JavaScript ...
It would have been chaos. Obviously none would like that, would they ?
Re: Open-sourcing Sonar, a new extensible debugging tool
#14I use this tool every day at FB and it's awesome. I highly encourage you to try it and see if it fits into your workflow!
Glad to hear the tool works well for FB employee's. As always the contribution to the community is much appreciated. But as others have pointed out, the tool name could use a rebranding. The popular SonarCube is just one example where confusion can arise.
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?
Re: Open-sourcing Sonar, a new extensible debugging tool
#15Congrats, Emil and team! I'm most excited for this as an extensible platform for further desktop tools, built on FB's robust stack of front-end tech.
Although I must admit, I'm disappointed that they didn't use react-native-web to build this app in a cross-platform way. I agree Electron is a good choice for the current landscape, but I'm hopeful that we will be able to move past it. If Sonar was implemented with React Native's layout API, it would be easily portable to projects like react-native-macos, React Native on Windows, or projects like Proton Native, once it matures and stabilizes.
Of course Emil knows this, because he is one of the primary maintainers of Yoga, the cross-platform flexbox implementation in React Native. This is one of the primary technologies that will allow us to move away from Electron one day, if people would just stop using CSS!
Re: Open-sourcing Sonar, a new extensible debugging tool
#16I rarely comment on name ambiguity because there is rarely overlap, but this does overlap a bit with the Sonar CI analysis tool IMO. Reading this post, I can create a Sonar plugin with Java? OK, let me Google "Sonar Java plugin"...
Hey People from SonarSource: https://www.sonarsource.com/company/history/
please file a lawsuit against Facebook. It looks like it is necessary to prevent them to use these confusing names.
Re: Open-sourcing Sonar, a new extensible debugging tool
#17I rarely comment on name ambiguity because there is rarely overlap, but this does overlap a bit with the Sonar CI analysis tool IMO. Reading this post, I can create a Sonar plugin with Java? OK, let me Google "Sonar Java plugin"...
FB developers couldn't possibly not know that they would be polluting the test tool namespace with this one...
Let's release a face recognition and database application called Facebook.
Re: Open-sourcing Sonar, a new extensible debugging tool
#18I agree unique naming is one of the fundamental pillars of modern coding , or else we would have chaos with stupid generic completely unrelated names like Python, C, Java, Go, Swift, Ruby, Assembly, Basic, JavaScript ... It would have been chaos. Obviously none would like that, would they ?
To be fair, most of those pre-date an era where the name collision would be a known significant problem. I remember when Starcraft was released and being frustrated that the young web at the time only gave me info on camping trailers, but even that is much later than half your examples.
Also, many of those you name collide with words that have no particular collision within the industry, so while you and I might think "Swift" is a non-ideal choice, it's not the same as the problem people are speaking of here.
JavaScript gets a pass because it was intentional. Not wise, as recruiting emails point out to me painfully regularly, but nonetheless intentional.
Go is the major and blink-tag-in-neon exception. I have no idea how naming something that is not only one of the english words with the most definitions but ALSO a game that has a higher-than-average overlap with people in the industry AND one that has been a significant target of the industry survived. I can only assume that someone underestimated the concern or I'm overestimating the actual pain.
Nowadays, however, there's no reason to repeat the Firebird debacle and fail to do a simple web search within your industry. Particularly if you're with a large company. Doing so earlier in your process is better, but even a last-minute name change can avoid generating a lot of ill will and confusion.
Re: Open-sourcing Sonar, a new extensible debugging tool
#19Earlier quoted context omitted.
Glad to hear the tool works well for FB employee's. As always the contribution to the community is much appreciated. But as others have pointed out, the tool name could use a rebranding. The popular SonarCube is just one example where confusion can arise.
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?
It can and has been done multiple times in the past - AsyncDisplayKit -> Texture is the one that immediately comes to mind as it happened after open-sourcing.
Re: Open-sourcing Sonar, a new extensible debugging tool
#20Earlier quoted context omitted.
Glad to hear the tool works well for FB employee's. As always the contribution to the community is much appreciated. But as others have pointed out, the tool name could use a rebranding. The popular SonarCube is just one example where confusion can arise.
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?
Actually, it makes perfect sense to rename it.