Cool. All valid points. I have a question, do you think builds in Go for a large web app will remain fast? I ask from the experience of working in Java with several minute build/deploy times...
From my experience, defintely yes. I use the Revel framework for creating my APIs to be consumed client side (Angular).
When I make changes, refreshing the browser results in a re-compile which takes less than a second (assuming I have modified several files) on my 2012 Macbook pro.
With Go, unit testing is also blazing fast. My entire test suite (around 30+ tests) takes around 0.2 seconds.
Just for comparision, I used Play 2 (Scala) for a short while before that. Re-compilation would take in the region of 10 seconds. Startup costs are high in the Java/.NET world :(
I assume this will be less of a problem in Go, because rapid compilation for large projects with complicated dependencies is one of the main design goals of Go.
Comments
Cool. All valid points. I have a question, do you think builds in Go for a large web app will remain fast? I ask from the experience of working in Java with several minute build/deploy times...
From my experience, defintely yes. I use the Revel framework for creating my APIs to be consumed client side (Angular).
When I make changes, refreshing the browser results in a re-compile which takes less than a second (assuming I have modified several files) on my 2012 Macbook pro.
With Go, unit testing is also blazing fast. My entire test suite (around 30+ tests) takes around 0.2 seconds.
Just for comparision, I used Play 2 (Scala) for a short while before that. Re-compilation would take in the region of 10 seconds. Startup costs are high in the Java/.NET world :(
Thanks for the information. It sounds like you've got some experience that I can relate to. I might actually check GO out for some API work.
I assume this will be less of a problem in Go, because rapid compilation for large projects with complicated dependencies is one of the main design goals of Go.