2 ms·
Because we're all using Go for other projects (even if piecemeal) and would like to build the entire project in a single language.
by rcarmo 9y ago
Because we're all using Go for other projects (even if piecemeal) and would like to build the entire project in a single language.
- bsaul 9y agoi personaly only would use go for very technical, low-level middlewares (as in, just above the OS layer) involving networks. The good side to it being simple to understand and maintain is that you won't pay a lot of debt if you're adding it to your stack. There isn't a single language that fits all use case perfectly anyway, so we'd have to just go to the "best tool for the job" approach in the meantime.
- sd8dgf8ds8g8dsg 9y ago> i personaly only would use go for very technical, low-level middlewares. Care to extend upon why you don't feel go is a good fit for other programming?