The mix of functional and imperative styles is odd, but not bad.
The mix of functional and imperative styles is odd, but not bad.
For a CRUD app server, its an overkill, though.
Even COBOL is not completely phased out by now, and runs in production, but it has been largely replaced by other languages.
But in one month with Go, I've gone from "barely remembers his teenage QBasic days and dabbles in VBA at work" to "writing genuinely useful utilities with minimal time investment". I'm sure the language has limitations, but I've yet to run into any that are personal showstoppers.
What GC does in practice is open up new domains. There are object-management patterns that simply can't be written feasibly without something like a GC runtime under the hood. (Hence Greenspun's tenth rule of programming, of course.)