Pastebins make me nostalgic. I’m told they existed well before the web in the IRC days. The first notable one I remember, Pastebin.com, was created in 2002 by Paul Dixon, introducing features like syntax highlighting and private pastes. Believe it or not, it’s still going strong today. The latest incarnation I remember using recently was PostBin (clever: Pastebin for Webhooks). It made testing “web callbacks”... - Source: dev.to / about 2 years ago

When you get something started feel free to put your code on pastebin.com or gist.github.com and share a link for feedback/help. Source: over 2 years ago

Either use pastebin or Github for formatting and paste a link. Source: over 2 years ago

You'll have to use a site like https://pastebin.com/ so I can see it too. My guess is that you did not install the mod I linked or that you haven't succesfully followed my steps. Start again from the beginning. Source: over 2 years ago

Pastebin.com was still reliable last time I tried it. Source: over 2 years ago

Anecdotal, but I have built from scratch a fairly large OpenAPI-compliant service using the Goa dsl (https://goa.design) and a coding agent and I've suspected for a while that the reason I've been as productive as I have with few blind alleys is that Goa kept the mistake surface pretty constrained. I also like not having the model generate boilerplate, as Goa's tooling does all that so much more cheaply. YMMV. - Source: Hacker News / 4 days ago

My experience of Golang is that dependency injection doesn't really have much benefit. It felt like a square peg in a round hole exercise when my team considered it. The team was almost exclusively Java/Typescript Devs so it was something that we thought we needed but I don't believe we actually missed once we decided to not pursue it. If you are looking at OpenAPI in Golang I can recommend having a look at... - Source: Hacker News / about 2 years ago

See https://goa.design/. It automates all the comms stuff, so you just write: 1) a design file showing your functions, 2) an implantation of those functions, and 3) a very generic "main.go" (basically the same for all your services) that decides "how is this exposed over gRPC or REST or other comms?". The rest of the code is generated. Source: over 2 years ago

If you really need a framework, you can take a look at Echo or, for a contract-first approach, https://goa.design/. Source: about 3 years ago

Few folks in here are (rightly) frustrated with the code generation story and broader tooling support around the OpenAPI standard. I've found a few alternative approaches quite nice to work with: - Use a DSL to describe your service and have it spit out the OpenAPI spec as well as server stubs. In other words, I wouldn't bother writing OpenAPI directly - it's an artifact that is generated at build time. As a Go... - Source: Hacker News / about 3 years ago