3 ms·
Just trying go for some real project, and frankly i wouldn't use it for anything else but network-related middleware ( or low level services), which is what i'm
by bsaul 12y ago
Just trying go for some real project, and frankly i wouldn't use it for anything else but network-related middleware ( or low level services), which is what i'm using it for, and almost every tutorial i've read about this language mentions.
As long as you're building something very technical, everything's fine. But once you go out of this path, you can see the walls getting dangerously closer.
For example, i was surprised to see how many runtime errors i got while coding, for a statically typed language.
Surprised as well to see that error checking made me wish for a goto statement again ( what's the pattern for handlings all errors in a block with the same code ? Please tell me..)
Then i started to code against a sql db, and boy did it bring me old memories back. Manual transaction scope handling ( annotation where are thou ?), manually counting bound variables in a statement, finding mismatched types between nullable ones and regular ones....
What a mess...
Now it may only be a matter of waiting for advanced librairies to mature, but somehow i doubt it.
- andrewchambers 12y agoGo is good at two things. Simple portable command line utilities with no dependencies - and network services.
- howeman 12y agoGo does have a goto statement, and one of its good uses is to transfer to an error handling block (from what I've seen). There are also type annotations (tags), though I don't know how/if they relate to sql