[jcadam]

I wish the Clojure compiler was half as fast as Go's :(

I'm not much of a fan of using Go for anything 'big', but I have taken to using it in places where I would have previously used Python (tiny/simple services, housekeeping/utility scripts fired by cron, etc.)

I'd love to use Go at work (amongst many other things), but my employer already gives me a hard time for writing small utilities in Python rather than Java (I refuse to wait for a JVM to spin up just to convert a single file from csv to xml. I simply will not do it, and apparently my employer doesn't consider it worth firing me over).

[zigzigzag]

Spinup of the JVM is 50 msec or so, for a hello world. Perhaps it's been a while since you tried running a small program on it? I can see why you might think the JVM starts slowly if you only ever run huge programs on it.

[infinotize]

What makes you choose Go over Python for simple services and utility scripts? (I'm just learning Go but would heavily lean towards Python for those things)

[jcadam]

Off the top of my head:

- Ease of deployment. It's a standalone binary - I don't have to ensure python and all needed libraries are installed/configured.

- I like Go's standard library - it usually has everything I need to whip up a basic network service easily.

- Better/easier concurrency support.

- It's faster than Python (though that's usually not incredibly important most of the time).