captcha VS fx

captcha

We haven't tracked posts mentioning captcha yet.
Tracking mentions began in Dec 2020.

fx

• How do you do dependency injection in go?
  2 projects | reddit.com/r/golang | 6 May 2022
• Thoughts on DI containers?
  1 project | reddit.com/r/golang | 30 Mar 2022

  Also why use dig directly? I really prefer using FX who is recommended by Uber

• Dependency injection in Go with Uber-go/fx
  2 projects | news.ycombinator.com | 27 Feb 2022

  That's a very fair perspective, and build-time verification of your dependency graph is great. That said, fx's approach allows for a more dynamic dependency graph. (For example, fx.Replace[0].)

  The documentation for Fx, along with nearly all the applications I saw internally, use the dependency injection container only in main - once the application starts successfully, there's no more interaction with the container. For Uber at the time, this struck a useful balance between safety and the difficulty of distributing yet another versioned code gen tool to thousands of repositories.

  [0]: https://github.com/uber-go/fx/pull/837

• How do you deal with dependency injection?
  2 projects | reddit.com/r/golang | 26 Dec 2021

  You can try Fx, it works pretty well. You can opt out of a lot of features if you just want DI.

• fx: useful functional programming helpers without using interface{}, based on Go 1.18 generics
  4 projects | reddit.com/r/golang | 19 Dec 2021

  Will advise you to change the library name as there is another popular library with same name. https://github.com/uber-go/fx

• Implementing Graceful Shutdown in Golang
  2 projects | reddit.com/r/golang | 17 Nov 2021
• [Question] How to split main.go into separate packages/files whilst maintaining Dependency Injection?
  8 projects | reddit.com/r/golang | 26 Aug 2021

  Try fx https://github.com/uber-go/fx. I separate my code into packages in exactly the same way that you want to do and fx takes care of the DI.

• Any workflow with dependent functions?
  2 projects | reddit.com/r/golang | 10 Aug 2021
• Gracefully shutting down multiple servers in a single prorgam
  2 projects | reddit.com/r/golang | 13 Jul 2021

  I really like use fx as a dependency and lifecycle manager (https://github.com/uber-go/fx) here’s an example of how it can gracefully handle multiple server startups and shutdowns (https://github.com/brandenc40/green-mountain-grill/blob/master/server/server/server.go#L37)

• Show HN: We wrote a book about building business applications in Go
  7 projects | news.ycombinator.com | 13 May 2021

  Take a look at the major DI frameworks for Go, Wire [0] and FX [1]. They just plumb the gaps between methods that return types and methods that want them. Although technically they work for concrete types, 99% of the time it's going to be an interface, so that you can substitute a mock for testing.

  Prior to DI frameworks we used global variables, often initialized in a package's init() method.

  >The desire to do this reflects a misunderstanding of interfaces.

  Generally you have a few layers: gRPC/HTTP/Kafka handler, business logic, and database or external service access. Layers are unit tested individually against mocks of the layers below. Because you're going to inject a mock, you can't depend on a concrete type, so you depend on an interface. Often when you're developing you want to know what the concrete implementation of a lower layer does, so it's useful to have "go-to-definition" see through the interface declaration to its implementations.

  I think the implicit satisfaction of interfaces is very cool and I wish I had it in every language. I wouldn't give it up just to simplify the IDE's job. But the IDE having this functionality does matter.

  [0] https://github.com/google/wire

  [1] https://github.com/uber-go/fx