I would see what the current knowledge of both languages is among your colleagues. Not just if they know Java and or Go. I would like to know how proficient they are.
As a consultant I often come to workplaces where I need to help and maintain a piece of code. They used a different language because the previous codes thought it would fit better (but you should read that as: we thought it would be fun to try out). You get code that is written without knowing all the language concepts and frameworks. It's bad and maintenance becomes hell.
Don't just go for a different language because it looks cool or it is shiny. If you still would like to try it: send all the developers to a course of a few days to make sure everybody on par.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I would see what the current knowledge of both languages is among your colleagues. Not just if they know Java and or Go. I would like to know how proficient they are.
As a consultant I often come to workplaces where I need to help and maintain a piece of code. They used a different language because the previous codes thought it would fit better (but you should read that as: we thought it would be fun to try out). You get code that is written without knowing all the language concepts and frameworks. It's bad and maintenance becomes hell.
Don't just go for a different language because it looks cool or it is shiny. If you still would like to try it: send all the developers to a course of a few days to make sure everybody on par.