Comparing Go to Rust is like comparing apples to oranges IMSO.
Also, I’d be careful comparing it to Python as well because the latter has an enormous amount of libraries for everything including but not limited to ML/NLP which is very trendy nowadays. What Go brings to the table is cheap concurrency, but hey, Erlang can do it better for 30 years already and Elixir leverages Erlang’s VM if one wants a modern fancy syntax.
Capitalization for publics is not as bad OTOH as it could seem at the first glance; once one gets accustomed, it somewhat simplifies reading the code. Many languages do that or similar, including but not limited to Ruby, Erlang, Elixir etc. The idea is not as random, it’s originated to FORTRAN where you named integer variables starting with one of i, j, k, l, m, n letter.
Oh, thank you for the clarification. What I meant comparing it to python was that for me, it filled the same role. I often use python to quickly whip out web servers, but I have been using go for this more since I learned it. (and yes node may be slightly faster but I don't want to deal with call back hell and I already know python).
I honestly doubt Node is any faster than Go. Actually I am pretty sure it’s vice versa.
Well, the best language to quickly whip out web servers is the language you like most :)
When it comes to extensive development of business logic behind, syntax and “effectiveness” come to the scene because syntax increases developer’s performance and “effectiveness” increases the computer’s performance. I do not see Go fitting any of the above.
I meant node is faster than python, I should have made that more clear.
BTW no one uses callbacks in 2018 (or 2019?) anymore, async/await is the standard in Node now ;)
Looks like I'm behind the times. Thanks for the heads up!
You're welcome ;)
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.