Hacker News Reader

It entirely depends on my use case. If I'm stringing I/O together from other applications, I'll just glue them together in Bash.

If I'm building something a bit more robust or integrated I'll use Python or Groovy or Node.

An example would be: we have a Java web app with some REST APIs for updating content. Instead of rebuilding the models, I just pulled the domain objects into a core library and wrote a Groovy CLI around it.

View on HN

I'll want something that probably communicates with web through REST calls, with authentication, so I'll need ssl.

I've done a lot with curl and jq for REST calls with bash. But if I'm doing a lot of API calls I usually go straight to Python or Node- usually Node because I feel like I'm faster with it for that type of stuff.

I tend to save Groovy for bigger projects, or take my bash scripts that get unwieldy and move them over.

Reply on news.ycombinator.com