3 ms·

This is just a personal opinion. No offense intended if you disagree. I started go 6 months a go and while I like the language I hate the team. There's so much

This is just a personal opinion. No offense intended if you disagree. I started go 6 months a go and while I like the language I hate the team. There's so much emphasis on making everything elegant perfect, organized and clean and the way go is designed just doesn't fit well with that. I feel like I'm working with a giant java program. Looking at the libraries I feel this is the go culture. Elegance over simplicity seems to be the philosophy and that leads to java like programs rather than c like programs. I personally liked the language but the ecosystem and the culture around it I'm not particularly a fan of because it's so at odds with the design of the language. Funnily enough many years back before generics I didn't feel this way about the language. Now I do, so it might be that?

mseepgood 3y ago
> I hate the team Can you link to where you have interacted with them personally, so that we can judge whether your hatred is justified?
- ninetyninenine 3y ago
  By team I mean team culture and general go culture. And I don't mean attitudes or treatment. I mean design philosophy. Just to be clear. No links just look at some go libraries. Many libraries feel like it's designed for java.
  - kjksf 3y ago
    I have used lots of Go libraries. I even wrote some. Your opinion here is just bizarre because typical Go code is as far away from typical (bad) Java code as you can get. Your typical Go library doesn't have FactoryFactory classes, doesn't overuse interfaces, doesn't have dependency injection, doesn't have callstacks 20 frames deep etc. So yeah, I would like to know which Go libraries specifically you're referring to because I just don't see that in the popular Go packages.
    - hkpack 3y ago
      To be honest, I saw a plenty of factory of factories in go on top of dependency injection systems with everything is an interfaces nightmares for simple libraries. Some people need to justify their salaries with the complexity for nothing.
  - hkpack 3y ago
    A lot of go developers are coming from Java and so write in Java style. That’s a problem of itself. To understand idiomatic go, it is better to look at its own standard library source codes.
- dijit 3y ago
  Maybe hate the team is strong, but there's excellent tools that have a really offputting team around them. I feel this way about Rust. Great language, fantastic tools, but the surrounding culture is really off-putting. You can disagree with the parent (and I do), but it's not like you need to directly interact with a team to dislike them if you disagree with their public statements, actions or controversies.
  - ninetyninenine 3y ago
    Yeah I meant I hate my teams design philosophy and I feel most teams that are go centric are like this. Hate was too strong of a word and that was my mistake.
    - Mawr 3y ago
      It wasn't, you're just being hit with the standard obnoxiously disingenuous HN responses. It's very clear what you meant by 'hate' in your post.
silisili 3y ago
Your comment makes it look as if you're saying you hate the Go development team, but it seems that isn't the case. I get a little of what you're saying, I wouldn't say I hate anyone, but I strongly dislike how a lot of projects are organized. I think a lot stems from https://github.com/golang-standards/project-layout https://github.com/golang-standards/project-layout , which pretended to be standard and was so (ab)used one of the creators opened an issue about it. If you look at the actual Go src, it's much, much cleaner.

mseepgood 3y ago

> I hate the team Can you link to where you have interacted with them personally, so that we can judge whether your hatred is justified?

ninetyninenine 3y ago
By team I mean team culture and general go culture. And I don't mean attitudes or treatment. I mean design philosophy. Just to be clear. No links just look at some go libraries. Many libraries feel like it's designed for java.
- kjksf 3y ago
  I have used lots of Go libraries. I even wrote some. Your opinion here is just bizarre because typical Go code is as far away from typical (bad) Java code as you can get. Your typical Go library doesn't have FactoryFactory classes, doesn't overuse interfaces, doesn't have dependency injection, doesn't have callstacks 20 frames deep etc. So yeah, I would like to know which Go libraries specifically you're referring to because I just don't see that in the popular Go packages.
  - hkpack 3y ago
    To be honest, I saw a plenty of factory of factories in go on top of dependency injection systems with everything is an interfaces nightmares for simple libraries. Some people need to justify their salaries with the complexity for nothing.
- hkpack 3y ago
  A lot of go developers are coming from Java and so write in Java style. That’s a problem of itself. To understand idiomatic go, it is better to look at its own standard library source codes.
dijit 3y ago
Maybe hate the team is strong, but there's excellent tools that have a really offputting team around them. I feel this way about Rust. Great language, fantastic tools, but the surrounding culture is really off-putting. You can disagree with the parent (and I do), but it's not like you need to directly interact with a team to dislike them if you disagree with their public statements, actions or controversies.
- ninetyninenine 3y ago
  Yeah I meant I hate my teams design philosophy and I feel most teams that are go centric are like this. Hate was too strong of a word and that was my mistake.
  - Mawr 3y ago
    It wasn't, you're just being hit with the standard obnoxiously disingenuous HN responses. It's very clear what you meant by 'hate' in your post.

silisili 3y ago

Your comment makes it look as if you're saying you hate the Go development team, but it seems that isn't the case. I get a little of what you're saying, I wouldn't say I hate anyone, but I strongly dislike how a lot of projects are organized. I think a lot stems from https://github.com/golang-standards/project-layout https://github.com/golang-standards/project-layout , which pretended to be standard and was so (ab)used one of the creators opened an issue about it. If you look at the actual Go src, it's much, much cleaner.