Earlier quoted context omitted.
You will get slightly better people but still the wrong people. JS is almost never the right tool for the job, Go is occasionally the right tool for the job, mainly if you need to write something that moves bytes from one fd to another without much in the way of business logic. TBH if you are building something boring you should just use Spring w/Java or Kotlin. This will attract pragmatists that ship code that works…
Go doesn’t attract mediocrity it attracts pragmatism. I worked on a Scala team for a couple years, had a lot of devs that were “smart”, problem was they wrote really fancy code no one could understand. I then switched to a Go team and it was night and day. I was wildly more productive and the people in the community were not lacking intelligence. Go prioritizes community, it believes that “us” is more impactful than…
It attracts "pragmatism" and "simplicity" in my experience, but in the prescence of cheap optimal solutions the worse alternative is chosen to preserve that pragmatic image.