Why We Switched from Python to Go (2021)
softwareengineeringdaily.com
Why We Switched from Python to Go (2021)
1–10 of 301 posts
Re: Why We Switched from Python to Go (2021)
#2Something is odd about the timing.
This article is dated "Wednesday, March 3 2021" but appears to be identical to https://getstream.io/blog/switched-python-go/ dated Oct 17, 2017 and updated either May 14th 2019 or Sep 15, 2020.
Both say "Early this year, we switched Stream’s primary programming language from Python to Go", and there was HN discussion about it on Oct 17, 2017 at https://news.ycombinator.com/item?id=15495562 (397 comments).
Re: Why We Switched from Python to Go (2021)
#3Nim 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
Re: Why We Switched from Python to Go (2021)
#4Something is odd about the timing. This article is dated "Wednesday, March 3 2021" but appears to be identical to https://getstream.io/blog/switched-python-go/ dated Oct 17, 2017 and updated either May 14th 2019 or Sep 15, 2020. Both say "Early this year, we switched Stream’s primary programming language from Python to Go", and there was HN discussion about it on Oct 17, 2017 at https://news.ycombinator.com/item?id=1…
The author of the Software Engineering Daily post is credited as Thierry Schellenbach, CEO of Stream, so I'm guessing it's just a cross-post.
Re: Why We Switched from Python to Go (2021)
#5So 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 (?)
Re: Why We Switched from Python to Go (2021)
#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 are a mess, or if you have no discipline elsewhere, it doesn't matter what language you use - you will blow right past the "superfast" baseline.
Re: Why We Switched from Python to Go (2021)
#7Something is odd about the timing. This article is dated "Wednesday, March 3 2021" but appears to be identical to https://getstream.io/blog/switched-python-go/ dated Oct 17, 2017 and updated either May 14th 2019 or Sep 15, 2020. Both say "Early this year, we switched Stream’s primary programming language from Python to Go", and there was HN discussion about it on Oct 17, 2017 at https://news.ycombinator.com/item?id=1…
The Internet is awash with fake dates - old material 'up-dated' to make it appear current - but I wouldn't expect that sort of thing from SED which I have a decent amount of respect for.
Perhaps the author took something he had written before, and really did update it before republishing?
Re: Why We Switched from Python to Go (2021)
#8[deleted]
Re: Why We Switched from Python to Go (2021)
#9So 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 (?)
You really don't need frameworks on go. You go and pick whatever tools you need like ORMS, http routers or loggers.
It is only a disadvantage if you want to have a framework.
Re: Why We Switched from Python to Go (2021)
#10Something is odd about the timing. This article is dated "Wednesday, March 3 2021" but appears to be identical to https://getstream.io/blog/switched-python-go/ dated Oct 17, 2017 and updated either May 14th 2019 or Sep 15, 2020. Both say "Early this year, we switched Stream’s primary programming language from Python to Go", and there was HN discussion about it on Oct 17, 2017 at https://news.ycombinator.com/item?id=1…
The author of the Software Engineering Daily post is credited as Thierry Schellenbach, CEO of Stream, so I'm guessing it's just a cross-post.
Sure, but why do a cross-post years later without saying the information might be dated?
For example, you cannot now "Swap out True and False". That was changed in Python 3, and while many were still using Python 2 in 2019, it wasn't so true in 2021.
I also wonder how numba does with the "simple_gauss(time)*popularity" expression.