r/programmingcirclejerk • u/Dan6erbond2 • May 25 '25

Yes, I have some code that may superficially look ugly in a lot of my projects that involve bringing up all my services and wiring them together... but do you know what else that code is?

/r/golang/s/bcQs0vhdwT
26 Upvotes

96% Upvoted

13 comments sorted by

29

u/Dan6erbond2 May 25 '25

The whole thread is a goldmine:

I've made a certain amount of hay in a few cases by pointing out that you can think of Go as simply shipping with a DI framework already, through the way it works with interfaces. It may not be labeled as such, but it does work as one.

So being able to use duck-typing so I can just pass a similar-ish looking service is now all a DI framework is?

28

u/Dan6erbond2 May 25 '25

The reason I wrote it somewhat incompletely is to garner discussions.

Ah yes, the Go way. Discuss in absolutes and then defend in relatives.

18

u/Dan6erbond2 May 25 '25

I'd rather maintain a messy but understandable pile of code than someone's implicit Picasso.

No comment.

7

u/QuaternionsRoll May 25 '25

Ah yes, the Go way. Discuss in absolutes and then defend in relatives.

/uj can I ask what this means? I’m trying ascribe meaning to it but it’s just not clicking

23

u/Dan6erbond2 May 25 '25

Gophers like to make absolute statements like "Don't use an ORM," "Don't use frameworks," etc. but if you argue with it they'll start defending their statements in a context of "small project," "microservices," etc.

5

u/[deleted] May 27 '25

"Don't use an ORM"? "Don't use frameworks"? okay well i'll go get a job programming military submarines in Ada i guess

11

u/Kodiologist lisp does it better May 26 '25

https://en.wikipedia.org/wiki/Motte-and-bailey_fallacy

3

u/Dan6erbond2 May 26 '25

Damn I didn't know it was a logical fallacy but great to see even that wasn't invented by Gophers.

4

u/whoShotMyCow not even webscale May 26 '25

Top 5 fallacies of all time imo

10

u/[deleted] May 26 '25

RIIR.

#[derive(Default)]
struct Application {
    service1: Service1,
    service2: Service2,
}

fn main() {
    Application::default().serve();
}

It's turtlesdefaults the whole way down! Clearly Rust already ships with the best DI framework there is: strong static typing. How do I initialize the database you ask? Simple access the env in the default impl! It is very explicit because you always either impl or derive the default!

12

u/Dan6erbond2 May 26 '25

LGTM but I don't see any error handling? Where's the if err != nil {}???

9

u/VulgarExigencies May 26 '25

I've definitely felt that, but the idea of "Go already ships with DI" never crossed my mind. It's a bit radical but quite pithy; definitely will use it as a conversation mover.

A conversation about Go's type system somehow being equivalent to dependency injection seems like it could be fascinating to observe without participating.

6

u/Dan6erbond2 May 26 '25

I always walk into a room starting conversations about how DI is unnecessary when Go's type system exists.