4 ms·
The further problem is the resulting community. Interviewing for Go devs is going to become a pain.
by hordeallergy 10y ago
The further problem is the resulting community. Interviewing for Go devs is going to become a pain.
- thewhitetulip 10y ago> Interviewing for Go devs is going to become a pain Might I ask why?
- hordeallergy 10y agoWheat from chaff.
- thewhitetulip 10y agoI am sorry, I still didn't get your concern. It is easy in my opinion to identify the person writing Go code. Look at their Github profile! (I am not a recruiter, so I don't know how effective that really is, but Github profile does reflect a person's contributions to FOSS and if the person is a FOSS contributors, look at their repos or their other PRs or their projects)
- grey-area 10y agoI think most devs would have the flexibility of mind to adjust to whatever framework (or whatever ad-hoc, informally-specified implementation of half a framework) you use in-house. Many of the frameworks are not very different and lean heavily on the stdlib anyway, this is not rocket science, frameworks have different uses and strong points and the community does not have to be divided in religious war between different frameworks or framework advocates and the church of the one pure stdlib. These are tools, not competing world-views.