5 ms·
I don't care about past tense. If you had to write every day in Go, would you still be happy about it? (I sure wouldn't)
by snotrockets 4y ago
I don't care about past tense.
If you had to write every day in Go, would you still be happy about it? (I sure wouldn't)
- Cthulhu_ 4y agoI write Go every day, and have done so for the past two years or so (along Typescript, JS and PHP, the latter two for a 'legacy' application), and I'm happy with the language. If I were to criticise it, there's a few things that come to mind: - Struct tags don't feel right; it's string-based annotations and some libraries design whole DSLs in them. - The community seems to push towards using hexagonal or clean design, but unless I'm getting it wrong, this leads to a lot of really tedious conversion / adapter code. - There's not many good tools out there (yet?) to make things easier, e.g. database abstraction layers. Writing lower level SQL and some utilities to help with that is still better, but it's tedious and voluminous (like using raw JDBC and iterating over ResultSets). I've used ent (which required manual mapping between every struct field and every column, unless I got it wrong) and gorm (which breaks down when you nest deeper than one level), currently have about 40 tables. But these are issues that show up, I think, in any larger application.