[nebucnaut]

To be honest: We have not decided what language we will pick up next. Our first priority is to improve on our Java coverage. In a few months we should be ready to choose our next language. We are thinking about either tackling Python or implement support for a more recent language like Kotlin, Swift or Go.

[fusiongyro]

I doubt there's very much legacy-ish Kotlin or Swift code out there to be a significant selling point for your product.

[xyclos]

I spend a lot of time in clients' ios apps which were developed by other contractors long ago and then I'm asked to fix bugs and add new features. I think this would help me save a lot of time. Since it already supports C/C++ would objective-c support be relatively straightforward to add? Not sure if there are many others who would like to see it, but I know I would definitely appreciate it.

[dbcurtis]

Seems to me there is probably a huge amount of legacy Python code around that people need to explore. In fact, I've spent the entire day so far creating some so that we have enough legacy Python code around in a couple more years. Wouldn't want to run short.

[notheguyouthink]

I might buy this for Go if it was available, this looks interesting!

Note that I'm mainly interested because my current editor of choice does not have the full suite of tools I'm used to for Go. I used to use Vim, and vim-go has such an excellent suite of tools I don't think I'd buy this. However, I've since switched to Kakoune, and the tool support is quite young and I've not had time to improve it myself. So this tool (at the $100 self employment pricing) is a nice fit for a tool I'm on the fence about. At $200 I don't think I would, but at $100 I think I would.

Anyway, just providing a bit of feedback. Looks really nice!

[nebucnaut]

Thank you for sharing your opinion! This will be exactly what we will be interested in when deciding what language to tackle next :)

[3wolf]

I know it's easier said than done, but a pluggable interface for community created language support would go a long way towards gaining traction.

[devrandomguy]

A Lisp might be an easy language to target, because of its consistent syntax and "code is data" philosophy. With Clojure, you could both reuse some of your work on Java, and support Clojure's Java interop. Attempting to support Clojure would drive improvements in the Java support.

[Shank]

Seems to me like the obvious choices would be languages that have large, long standing legacy codebases. Swift code is going to be relatively tight just because it's so recent, whereas something like C# isn't.

[tylerc230]

Swift would be great. Perhaps you could leverage SourceKit.

[fspear]

Python, Scala and Go would be great additions (in that order).