๐ค Go is not about IO ๐ค
I listened to an interview and to the question: "Why Go and not Python, given the expected high loads?" โ I gave myself a very interesting answer.
#go
# [ $davids.sh ] ยท message #253
๐ค Go is not about IO ๐ค
I listened to an interview and to the question: "Why Go and not Python, given the expected high loads?" โ I gave myself a very interesting answer.
#go
@ [ $davids.sh ] ยท # 1566
For me, Go isn't about high loads (though it handles them perfectly), Go is about language design.
I love frameworks and boundaries:
Firstly, they make it much easier to work with juniors/mid-levels because they have far fewer ways to write something overly complicated + everything that allows using juniors more effectively is a net positive.
Secondly, it allows us to spend much less effort understanding another developer's code.
Thirdly, as they say in art: "Constraints stimulate imagination" โ and in the case of coding, constraints stimulate the search for more concise problem-solving paths, the discovery of which brings immense joy.
Undoubtedly, languages that offer more expressive mechanisms (Rust, TS, C#, etc.) still allow for concise writing, BUT a person who hasn't imposed strict limitations on themselves simply doesn't understand that alternative paths exist.
Therefore, I can recommend writing in Go to absolutely any developer precisely so that when you switch to another language, you still have concise techniques for writing understandable code in your arsenal and can add syntactic sugar where necessary.
@ Arsen IT-K Arakelyan ยท # 1572
I'm playing around with Go right now, and Node.js is really starting to annoy me with the fact that you sit there and constantly think, "Can I do it this way? Or this way? Or maybe a mix? Then twist it like this, and you end up with a Frankenstein mess."
Maybe it's because I haven't written anything complex or large in Go yet.
No enjoyment from development, just mental masturbation of thoughts in my head, few actions, and in the end, extreme exhaustion from a completed task, with the thought, "To hell with all these best practices, just get the task done and make it work," because the goal is to solve the problem.
But on the other hand, if you constantly live within limitations, you end up with Java (any strict language) brain!