3 ms·
Amusingly, in his "Why I love Go" [0] linked from that article he discusses using the right tool for the job: > Instead, this about the right tool for the job.
by mcintyre1994 11y ago
Amusingly, in his "Why I love Go" [0] linked from that article he discusses using the right tool for the job:
> Instead, this about the right tool for the job. (Could you imagine woodworkers getting into heated arguments about whether a screwdriver or hammer was better?)
That would be about as insane as a woodworker writing a blog post about 'leaving the screwdriver' :)
[0] http://blog.jonathanoliver.com/why-i-love-go/ http://blog.jonathanoliver.com/why-i-love-go/
- deleted 11y ago[deleted]
- jonathanoliver 11y agoOP here. Most of my work is server-side APIs where Go fits very, very well.
- Retra 11y agoYou do realize that computer programs and languages are not screwdrivers and hammers, right? We're talking about a world where screwdrivers and hammers both claim to allow you to efficiently drive nails and screw screws. It is very possible for one to be strictly better than the other, and not even unlikely that one is better in most common situations. I know "the right tool for the job" is some sort of unchallengeable divine hacker slogan, but I've never seen that slogan solve a problem. So maybe it isn't the right tool for this job.