I read few posts regarding ORMs in golang & realized, few peoples are not happy with it.
They mentioned to use raw queries with our own wrapper if want to make few things reusable. I was actually using Gorm, which was super slow, then I started research regarding performance efficient ORMs, and found *Bun* which was indeed faster compared to Gorm. But then I explored documentation more and realized it doesn't provide enough function to make life easier, this ORM even doesn't have community I felt. 1. I want to know readers view regarding ORMs in Go. Let me tell you something, my project is a huge project, and I decided to use Golang for better performance. But now I feel I've to write a lot of code and slow/less-featured ORMs here making me irritated. 2. What do you guys suggest is go really good for large projects? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/49c377fb-bc86-4c24-bff9-1a51b453a86dn%40googlegroups.com.
