Hi HN, I'm the tech-lead for the State Tool, here to hopefully get some useful feedback!

Our aim with the State Tool is to provide a tool that solves common dev tasks in a universal way. Think of how we tend to abuse the Makefile to just contain some aliases, or how we might use Gulp when using JavaScript and setupfiles when using Python. There is a large amount of tool abuse and inconsistency that makes jumping between projects hard and onboarding new people to a project harder. The State Tool aims to be the one stop shop to address these issues.

Currently we're still in beta. This mainly means features are still in flux and the general user experience is still forming. What we really need is feedback from developers on what they like, dislike and would like to see from the tool.

Happy to answer any questions you might have.

I couldn't readily tell how much value this is for non-Python users coming from a name I strongly associate with Python.

Right now we only support Python and Perl, so if you don't wish to use those languages for writing common dev tasks scripts I agree there isn't much value here -- yet.

The language portion of this is powered by the ActiveState Platform which is quickly ramping up. We're working hard on adding support for other open source languages so the relevancy for users of those languages will come into play soon.

In case we have any Arch users, I took this opportunity to learn more about AUR and created a Komodo-IDE package for it

https://aur.archlinux.org/packages/komodo-ide/

So installing on Arch should be as simple as `pacaur -S komodo-ide`

Hi guys, I'm the lead developer for Komodo IDE. Excited to share our hard work with you. Happy to answer any questions you might have.

Do you support code refactoring yet?

Eg, rename a symbol and have all usage of it updated (could be a local scope variable could be a class name used project wide)

I previously used Komodo IDE but for the last few years I've found IntelliJ IDEA to be more robust/full featured.

I'd love to be able to switch back, because the jvm definitely makes idea seem "heavier" somehow.

I believe this was introduced in version 9. So yes, we do support code refactoring.

One major difference between IDEA and Komodo that you may not be aware of is Komodo is based on Mozilla (XUL) and does not use Java.

I did know about it being xul actually (I used it for my day job back in 2006-8) - that's the big draw for me, not being java.

The simpler licensing is nice too. I'll have to check this out in a few days (laptops don't work well without fans).

I'm the product lead for Komodo IDE and the author of the new unit testing feature, happy to answer any questions.

Komodo does not use any Java what so ever. The only traces of Java you could find is syntax highlighting support and in the name of JavaScript. We're not a Java IDE.

It does not have native Puppet integration at the moment. You could add your vote here: https://github.com/Komodo/KomodoEdit/issues/803

Komodo has remote debugging for pretty much all of its major languages.

Not to take the magic away but I bought it from AudioJungle:

http://audiojungle.net/item/dynamic-world-background/3940097

It's quite good, I was also surprised it was "just a jingle".

Doesn't bother me in the slightest - thanks!

Hi there, I'm the lead dev for Komodo. Just wanted to point out that Komodo IDE is $147 for individuals. The individuals price is below the fold on the pricing page, so you might not see it at first glance.

What is the problem with those for you? Komodo supports refactoring.

I actually had to download and try it, to remember the specifics. For this example I just opened up a PHP project.

With refactoring specifically: Komodo supports just "rename class member" and "rename variable" (and "Extract method..." which was constantly unavailable for me).

IntelliJ IDE's support simple renames of members/variables, but more importantly, push/pulling members up/down in a class hierarchy, changing method signatures, moving entire classes into different namespaces.

On top of this, it's little things e.g. the Komodo codeintel doesn't auto-suggest class names if they aren't already imported - you have to import the class (using "use"), and then you can go use it. This is exactly the kind of thing an IDE is supposed to improve - manual steps that can absolutely be automated.

Those are all very good points :) Please consider sharing your ideas on our bug tracker: https://github.com/Komodo/KomodoEdit/issues

The API isn't documented yet, but you can infer from the existing tools and integrations how things work:

http://kopy.io/about.md

(scroll down to "Tools & Integrations")