wire VS purescript-native

code generation is a mostly disjoint topic from DI. Granted, some solutions like https://github.com/google/wire use code generation, but you're exactly right about their pitfalls. If your dev environment doesn't have good support for generated code, it is a nightmare. If you can goto-definition the generated code, then it is suddenly feasible, but perhaps still a bad choice.

We use https://github.com/google/wire for every bigger project, take a look at it, it beautifully solves initialisation and also gives you a guideline on how to do it.

Im by no means a "purist" in such things, I love my magic and QoL-features/libs, but havent seen something that is so easy to use in go, that I immediately wanted to add it. And to be fair, I only looked closely at https://github.com/google/wire , others I have just skipped - and I will be looking into uber-fx as mentioned in the other comment.

If you have such a complex and deep dependency graph, and you don't want to manually maintain it, you could use some DI library to handle that for you. Something like https://github.com/google/wire for small-medium size stuff, or https://github.com/uber-go/fx for larger scale, more enterprise projects.

Try https://github.com/google/wire. Compile time generated like dagger 2 in java.

Most people probably do it by hand (I do). But otherwise, probably https://github.com/google/wire is the most popular, maybe followed by https://github.com/uber-go/fx.

For larger object graphs do you roll everything by hand or encourage something like https://github.com/google/wire

The other thing is that I'm lazy, so I don't construct all dependencies in main.go manually but use wire to generate the construction of my dependency tree.

There was also purescript: https://github.com/andyarvanitis/purescript-native

Before 2012, all of my websites were made using HTML, CSS and a sprinkling of JS. Then, I went all-in on AngularJS, followed by React. I started using Typescript and then PureScript and learned more frameworks like Halogen and Concur. I even wrote my own UI framework called purescript-deku.

PureScript native back-ends manage memory by reference counting too https://github.com/andyarvanitis/purescript-native/blob/cpp/README-cpp.md

I hope you get a chance to try PureScript out in your JS projects! For more learning resources, you can check out PureScript website.

Did you look into purescript-native, the purescript-to-c++ transpiler? Just curious what your reasons were to avoid that option.

Typeclasses are the big one I'd say. User defined operators are missing. Direct foreign function access is missing as well - for js stuff you have to communicate through "ports", you can't call js functions striaght from elm code. Also its not a general purpose language, you can't write a commandline tool with it or compile it to native code.

Another I thought of: Purescript (a haskell-like language that compiles to Javascript) has a native backend that compiles to either C++ or Go.

Purescript. A Haskell like language that is translate to Javascript. You can run it in NodeJS. There is also native versions that translate to Go or C++.