I do agree. My concern is about the future of the project. If they do a great job, I do think they should support others languages, perhaps having a ecosystem like jetbrains. I think it's inviable survive supporting only one language.
I’m not in their beta, but the following statement doesn’t give me a lot of faith in a native Jetbrains-like alternative:
> Our whole philosophy is fewer features, built with more polish. Attention to detail and thoughful design is what Chime is all about.
They seem to be pretty focused on editor usage, not tooling and ecosystem. That could definitely change over time, but I’m not currently interpreting this application as a pluggable IDE-like scenario.
They also have barely any information on their site, so it’s hard to form an opinion on this. It’s something to keep an eye on, though.
Even without that, I still think it's a niche worth pursuing. They'll be able to sell this if it really works well. All the Go developers I know use macOS as their primary development platform.
The last thing the world needs is another proprietary, payware IDE (that most likely involves all sorts of phone-home telemetry to benefit them and not you).
Chime has in-process crash reporting. Which is both open source (on our Github page) and you can opt-out via prefs. No other telemetry of any kind. To be honest, I'm not even sure how telemetry like that could even be used to be benefit us. But, perhaps we're just not in that mindset.
Regardless, there's nothing like this in Chime and there never will be. But I get that not everyone wants a closed-source tool. There are many open source options, including a number of high-quality macOS native ones.
Many parts of the system are open, and more are coming. We're just not savvy enough to be able to open source the whole thing and also continue to afford to work on it.
Sounds like you work on exclusively open source software. You're lucky!