Live data from Hacker News

Why We Switched from Python to Go (2021)

softwareengineeringdaily.com

61–70 of 301 posts

Re: Why We Switched from Python to Go (2021)

#61
post #23

Earlier quoted context omitted.

#7 given Go can't compare to Python on ecosystem breadth and depth, its a curious choice of "reason to switch"

It's been a while since I wanted something in Go that wasn't available, other than the obvious big-ticket items like NumPy which are ecosystems unto themselves. (Or, to put it another way, yeah, Go doesn't have NumPy, but neither does anybody else other than Python at this point.) YMMV, of course, but it's certainly not a routine occurrence.

[deleted]

Re: Why We Switched from Python to Go (2021)

#62

So they switched to Go from Python, because of following advantages: #1 Performance #2 Performance (to make the list longer I guess?) #5 Fast compile time... which is an advantage over Python how exactly? #7 Strong ecosystem... which brings us to disadvantage #1 - lack of frameworks (?)

[deleted]

Re: Why We Switched from Python to Go (2021)

#63
I always wondered why Stream was using Python instead of Go. Glad to hear they are able to make the change now. There is no comparison between Go and my Python or Node.js services when it comes to data processing or pipelines.

> Revel, Iris, Echo, Macaron and Buffalo seem to be the leading contenders.

If you're talking about MVC-era frameworks these are fine. However a lot of companies are using Go for microservices so I would highly recommend looking at https://goa.design/ and https://gokit.io/

Re: Why We Switched from Python to Go (2021)

#65
post #44

I read somewhere on HackerNews that Python is kinda like a default language and rest such as Go, C, C++, Java are just for Optimization, once you figure out your solution.

On first startup we used Tcl, and C code for performance, similar to what is fashionable with Python nowadays. I had enough of the rewrite in C experience that since then, if the language doesn't come with a compiler on the box, either JIT or AOT, I only see it as scripting language for sysadmin work or learning purposes.

AOLServer had a lot of defaults that would magnify the performance issues of TCL. The documentation did not cover all of the necessary configuration options to get a system to scale and you had to dig into driver.c to understand how to tune the system. I think the two big undocumented bottlenecks were maxsok and backlog. I bet if you were writing the same applications today, using modern hardware and Naviserver you would not have to write C modules anymore.

Re: Why We Switched from Python to Go (2021)

#66
post #14

>[Go] is almost as fast as languages like C++ and Java. It seems like only a couple of years ago when Java's speed was the butt of many a joke. The JVM has come a long way. As someone who doesn't work in Java and doesn't have a horse in this race, I find their turnaround impressive.

Java has been fast for a long time. Its reputation is slow to recover.

Re: Why We Switched from Python to Go (2021)

#68
post #3

Nim is another option if you're wanting a language faster than Python, but with high productivity. The ecosystem is not quite there yet though. Nexus dev framework should help somewhat: https://nexusdev.tools

THe ecosystem alone is putting me off comitting to Nim over Python. Although that attitude is a bit chicken and egg

I'm nearly ready to commit the first code for Nexus. Your comment gave me extra motivation to get it done!

I've actually written a lot of code and have used it for my own projects for some time, just need to get the release out now.

Re: Why We Switched from Python to Go (2021)

#69
post #6

"Developer productivity and not getting too creative" is NOT a point in favor of Go. Go does not have a lot of batteries included. Things like error handling, logging, test bootstrapping, etc, require consensus on the team and tight coordination. Every project is basically its own framework. Most teams are not that well-oiled. They are going to find this out the hard way. And fast? Please. If your database queries ar…

> If your database queries are a mess

This is a "wut?" moment for me. Why add this external factor, when it's totally irrelevant and the article doesn't even mention it?

Re: Why We Switched from Python to Go (2021)

#70
post #52

I think Go and Angular should have died, and would already be footnotes in programming history if they had not been introduced by Google. Let's make procedural programming great again? I get it, you can compile it and it has concurrency, but there's better alternatives in my mind, unfortunately not as popular.

For a lot of people like me, Go was something of a better scripting language.

It wasn't as hard to grok as C or Rust, it wasn't as slow as Ruby, Python or PHP. most of all, it it was designed to make use of multiple cores. Surprisingly, having testing and formatting built into the tooling is also a huge win after spending years debating and changing choices in scripting land.

Go is the new PHP/Node.js and Rust is the replacement for everything else. I know this is technically wrong, but that's how it feels.

Post reply on HN