5 ms·
We've started building Bugfender using GORM and it was good for the initial job, but we now decided to remove it completely and continue on a lower level. We'v
by znq 10y ago
We've started building Bugfender using GORM and it was good for the initial job, but we now decided to remove it completely and continue on a lower level.
We've summarized our whole experience with Go here: https://bugfender.com/one-year-using-go https://bugfender.com/one-year-using-go and we're just wrapping up another blog post with the Go pros and cons (from our point of view), which should be out soon as well.
The biggest problem with go is, that it is still a very fast and changing ecosystem. Which is great for a new language, but didn't serve us too well for building something stable.
- sagichmal 10y agoIn which universe is Go a part of a fast-changing ecosystem? It certainly isn't this one! The Go language abides a strict compatibility guarantee. Libraries, perhaps due to the poor dependency management situation, tend more than other language ecosystems to avoid breaking changes, or at least hide them behind different import paths. Go has arguably the least dynamic, most boring ecosystem among popular languages today!