>The “enterprise java” style is an unfortunate one >but it is not a necessity at all The thing is in real life you have to deal with this kind of code most of

>The “enterprise java” style is an unfortunate one >but it is not a necessity at all The thing is in real life you have to deal with this kind of code most of the time. Because most of the time you deal with the old code or people who are used to some patterns you have to use too because you are part of the team. Go enforces (kind of) a more barebones approach by default. PS: I think it's poinless to compare two languages. We should rather compare real practices and read examples.