
-
I have briefly looked into this and leaning towards GraphQL Go but don't yet know how it'll all come together. I'd prefer to stick with GraphQL if I can without it getting messy.
-
Nutrient
Nutrient - The #1 PDF SDK Library. Bad PDFs = bad UX. Slow load times, broken annotations, clunky UX frustrates users. Nutrient’s PDF SDKs gives seamless document experiences, fast rendering, annotations, real-time collaboration, 100+ features. Used by 10K+ devs, serving ~half a billion users worldwide. Explore the SDK for free.
-
Better look into this one: https://github.com/99designs/gqlgen for GraphQL powered by Go. It's spec first approach and requires the least boilerplate code to write. It also incorporates seamlessly with Apollo Federation.
-
I know somebody is going to rush to defend Go's performance and in many cases you may be right, but web dev is not one of them. Even Go regexes are among the slowest of any language, far behind JavaScript and PHP. The regexp performance issue has been open since 2015. Despite rsc himself being the former Google RE2 open source maintainer, and Google in general having several regex experts and obviously Go experts, nobody has cared enough to make Go's regexes even passably average.
-
I do see that point of view, didn't think of that, there are some aspects of go which are a bit weird if you never touched lower abstraction languages, yet once you learn what they are, you are all set and you can code in anything. go has the least amount of gotchas I have seen in any programming language. compare it with loads of the weird stuff javascript does https://github.com/denysdovhan/wtfjs and go is like heavenly lol