preslavrachev / preslav.me-comments

0 stars 0 forks source link

scratchpad/2023/12/why-golang-over-rust-java-python/ #27

Open utterances-bot opened 9 months ago

utterances-bot commented 9 months ago

Why should I use Go over Rust, Java, or Python? · Preslav Rachev

I am a software engineer with a decade-long experience developing software in Python, Go, and Java.

https://preslav.me/scratchpad/2023/12/why-golang-over-rust-java-python/

zaid-kamil commented 9 months ago

You did not convince me with anything.

was this article generated using chatgpt? P.S. the author helped me edit my poorly written comment

preslavrachev commented 9 months ago

was this article generated using chatgpt?

@zaid-kamil Nope, it's entirely my creation. But i guess, that does not make any difference to you, does it? Anyway, thanks for stopping by.

P.S. You can edit your comment by clicking on its link, which will take you to the related Github issue.

Cheers, Preslav

zaid-kamil commented 9 months ago

was this article generated using chatgpt?

@zaid-kamil Nope, it's entirely my creation. But i guess, that does not make any difference to you, does it? Anyway, thanks for stopping by.

P.S. You can edit your comment by clicking on its link, which will take you to the related Github issue.

Cheers, Preslav

expectation vs reality

Here is the story of what happened before. I came home, sat at the couch and started scrolling through Google news. Suddenly an article titled "Why should I use Go over Rust, Java, or Python?" Appeared in the feed and got me intrigued, as I was already looking at rust to learn, with golang being in the back of my mind as a backlog. I thought, whoa an interesting article title that will give me an idea about golang, cool cool cool. I started reading and liked the first 2 paragraphs, and with interest i scrolled and read more and then that's it, there was no example, no code, just a very simple explanation. As a person who rarely comments on articles was enraged by the author's choice of words asking me to follow, while I got nothing in the article, and also it was so small, it looked like something generated by a chatGPT prompt. And i just wrote a negative comment in a very bad markdown syntax on my mobile, which after submission, had the option to edit. The end of the story.

I will wait for the next article on golang, not for the purpose of commenting but learning and if it's good I will share it with my students and peers.

P.S. you can check my GitHub profile to understand me better

Cheers,

Zaid

preslavrachev commented 9 months ago

@zaid-kamil I understand perfectly where you are coming from. In fact, I wrote this (I won't even call it a blog post) scratch halfway as a joke, halfway to explain the diagram. In fact, if you look at the categorization in the URL, it's coming from my scratchpad - it's not even considered a regular blog post of mine. And yet, somehow Google picked it up, so I now live with the consequence of thousands of people coming by and not finding what they expected to find.

As you have figured out, I am in Team Go (for the reasons I outlined in the text). I have tried to like Rust, but th econgnitive burden is just too much for me to make anything useful with it. I am a practical person - I like frameworks like Java's Spring, Rails, and Django. I enjoy building products without having to sit down and fit the compiler for days. While i understand Rust's entire premise, it's just too unproductive for me at this point to find it a useful option.

SnowDrift80 commented 9 months ago

Go is great, but I think Python is unstoppable. And Mojo Lang will combine the advantages Python, like easy to read code (because based on Python), lots of libraries and the efficiency of Golang, like memory usage and performance.

dilantha111 commented 9 months ago

I can say I was convinced to give it a go for Go. I like the idea that it's being a language of 80%. I expect this is being you need to install lot's of libraries and lot's of setups before you do some actual coding.

PS : Not sure why @zaid-kamil was expecting some codes for this article. It's just stating some suggestions.