it's so refreshing reading your comment, I believe the same, looks like some people enjoy a hidden satisfaction doing that, on my opinion is the sensation of power to decide what's right or not (basically playing God)
and as we know power corrupts people.
I have this idea, be honest and but firm, and do a proposition to him: you'll allow him to stay and continue working but he has to accept taking a serious psychological treatment, that person needs mental attention immediately. He sounds like a reasonable/intelligent person, try to negotiate something that helps him and you.
the key is simplicity, you're complaining about language features that allow you to write "fun" code, but remember that we spend around 80% of the time reading or debugging code, the main focus of Go is about writing code that's easy to read which will allow you to scale a project or source code with more people, also remember that easy doesn't mean simple, I think these 2 talks will make you understand my idea a little bit better:
And I'd disagree. Numerous engineers of differing skill levels (what I deal with day to day), struggle significantly when map/filter are added into the mix. And we may say "get better engineers", but we don't have that ability. We have to write code that is maintainable for the engineers we have and can get (and the ones coming in the future).
Not really. They require a basic understanding of higher order functions and often heavily use closures. Those moderately advanced concepts. It’s also sometimes harder to write efficiently to avoid multiple iterations over the same collection. I think many many people are way more comfortable with loops than people are with map/filter.
Correctness isn't about fun, although fun is definitely a side effect. I agree Go is easier to read if you're primarily familiar with C style imperative programming, but once you've strayed from that a bit, a PR in Typescript is no more difficult to review than one in Go. The big benefit of languages with more expressive type systems is the confidence you get that your code will work as expected if it compiles - I felt this in Swift more than in TS, and very little in Go.
I love go but the OP is completely right. Lack of basic collection functions is incredibly aggravating and slows down productivity substantially. At least it's not as bad as Java.
I'm not sure how you can have that opinion of Java when Go is basically Java pre-generics. Especially in the context of collection functions. Java's stream API is simply amazing.
Yeah sorry, the Java collections API is pretty great. I meant in terms of raw boilerplate the language requires you to type to get anything done. This is definitely improving, and you can use things like Project Lombok to generate a lot of it.
I'm so tired of those fake problems, when Silicon Valley started was majority white, one day the victimhood mindset will end and everybody will not find excuses to do things.
I simply said they were not the same. You and another commenter have incorrectly inferred that I was talking about their victims. Says a lot more about you than it does about me.
