Who else has or wants to move from Java to Go because of the Java culture and bike shedding?

I swear, if I had a penny for every time I've had/seen PR comments saying "Why not x way?", to perfectly good code, I'd retire just to get away from Java developers.

More often than not, what's really being said is "I would have done it this way and I want it that way, and maybe I want to point things out to make myself look good as im contributing and noticing things you didnt". Now you're wasting time replying to the comment and waiting, or waiting for your colleage to respond on Slack so you can waste time talking about trivial shit.

IMO as a rule, you should refactor it yourself if you care so much to hold up a PR using an if else while you prefer Optional.of(...).orElse(...). Mind you, if you make the change, you have to wait for the CI, which costs in CI minutes and dev time (lets be real, your manager may say you shouldnt be waiting during CI, but you work on one ticket at a time for the most part? And we all hate context switching. Oh and the 20-30 min CI's typical in "Enterprise" Java codebases don't help), and then you have to wait for the reviewer again... the amount of times they've went MIA is also a pain point.

Holy shit. Java as a language is fine, but the "Enterprise Java Programmer"s you work with make me want to flip my laptop and look after sheep in the mountains. All this talk about shipping fast, then PR's being held up over trivial things because there's a 100 ways to do the same thing and a reviewer thinks he's actually adding value and coming across as a good dev because he caught a potential change. F*ck your preference, the work has been done, is done well, and works. Approve the damn thing or change it yourself. The amount of times I've seen sprints not being completed in time because collectivley a day or two has been lost in the review process. Baffling.

There's often talk about Spring Boot, and how much you get out the box. I'd bet my house you save time using Go when you calculate all the bike shedding comapred to Java teams.

Rant over.

I'm reading Learning Go and Let's Go, then moving on to Let's Go Further and Concurrency in Go. Time for a change, it'll be tough as there arent many remote Go jobs in the UK but you gotta have some hope eh.

Edit: Fully agree, this is a IC/team issue, not a language issue. But I feel its especially prevalant in Java teams, and Go challenges a lot of things Java devs are used to, and the simpler language also helps.

submitted by /u/theonlywayisupwards
[link] [comments]