"if you're working on a project if you're a web developer you have a job most web developers don't really care that much about things with that much passion so at the end of the day all of these things are just tools go is a language it is just a tool to build something and if you like using go you should use it" 👏👏👏👏👏 Bravo.
It's all very well saying "we should use the right tool for the job" when discussing language choices. It grew to suggest we should not get so emotional about it and that the endless "language wars" are silly. But, most of us don't get the choice. We often find ourselves working in teams and companies and therefore using the language they use that may be subjectively to our dislike or may well be objectively not the best tool for the job for all kind of measurable reasons. This situation can be miserable. Like hiring a master craftsman and then dictating he can use the tools he likes and knows do a better job. As such I think "language wars" are important. As the "master crafts men" of software we should point out problems in languages and language choices.
Pointing out the pros and cons in languages is good, I agree. "Language wars" not so much. It's one thing for me to say "Rust is good at x or y, Go is bad at x or y", it's another to say "if you use Go you don't know anything about programming, Rust is the best language". Those type of statements are not productive and bring absolutely nothing positive to the community. That was what I was referring to.
Whenever I need to build a web service, I’m reaching for Go. For system programming or games there are better tools, but for API or server development, or small CLI apps, go is simply unbeatable
"if you're working on a project if you're a web developer you have a job most web developers don't really care that much about things with that much passion so at the end of the day all of these things are just tools go is a language it is just a tool to build something and if you like using go you should use it"
👏👏👏👏👏
Bravo.
It's all very well saying "we should use the right tool for the job" when discussing language choices. It grew to suggest we should not get so emotional about it and that the endless "language wars" are silly. But, most of us don't get the choice. We often find ourselves working in teams and companies and therefore using the language they use that may be subjectively to our dislike or may well be objectively not the best tool for the job for all kind of measurable reasons. This situation can be miserable. Like hiring a master craftsman and then dictating he can use the tools he likes and knows do a better job. As such I think "language wars" are important. As the "master crafts men" of software we should point out problems in languages and language choices.
Pointing out the pros and cons in languages is good, I agree. "Language wars" not so much. It's one thing for me to say "Rust is good at x or y, Go is bad at x or y", it's another to say "if you use Go you don't know anything about programming, Rust is the best language". Those type of statements are not productive and bring absolutely nothing positive to the community. That was what I was referring to.
@@webdevfuel I agree.
Whenever I need to build a web service, I’m reaching for Go. For system programming or games there are better tools, but for API or server development, or small CLI apps, go is simply unbeatable
Missed you bro😢
Thanks my friend, it's good to be back!
I think Go let's you get things done real quick.