Why We switched from Python To Go
medium.com
Why We switched from Python To Go
1–10 of 79 posts
Re: Why We switched from Python To Go
#2Next up from The Author:
5 Reasons Why We Switched from MySQL to Postgres
Why We Switched from Postgres to Oracle
11 Reasons For Switching From Oracle To KDB
7 Reasons Why We Switched from Go to Fortran-77
Grammar errors are provided for free by The Author.
Re: Why We switched from Python To Go
#3As with all "why we changed from technology X to technology Y", the story is that there was this or that perceived shortcoming in technology X and technology Y will be our savior and fix all our problems, or conform to our software ideology/dogma.
I used to read these things but given that I've read one, I've read em all.
The only reason people keep writing these things is blog filler to promote their company or do indirect recruiting. Surely cannot be cause anyone cares why you use a blue pen instead of a black pen.
Re: Why We switched from Python To Go
#4> #2 Static Type System
It's really weird to see one of the reasons for their switch to Go was because it's a statically typed language. If you want static typing, you don't choose Python in the first place. You know it beforehand and it shouldn't come as a surprise for you.
> For example it has http, json, html templating built in language natively
So does Python with urllib and json modules. I don't know if it has HTML templating in the standard library, but you can always use jinja2.
> Great IDE support and debugging
Not even a mention for the excellent PyCharm or so many of the useful Python vim plugins?
Re: Why We switched from Python To Go
#5That's a dumb article.
Take point 5 for instance: You can code in Go with Jetbrain's IDE. Well guess what, Python has a dedicated IDE made by JetBrain: PyCharm. How is this an advantage ?
Re: Why We switched from Python To Go
#6From the HN guidelines:
If the original title begins with a number or number + gratuitous adjective, we'd appreciate it if you'd crop it. E.g. translate "10 Ways To Do X" to "How To Do X," and "14 Amazing Ys" to "Ys."
Re: Why We switched from Python To Go
#7Point 3
Goroutines are more performant than python threads if you don't understand the difference between a thread and a routine.
Re: Why We switched from Python To Go
#8Next up from The Author: 5 Reasons Why We Switched from MySQL to Postgres Why We Switched from Postgres to Oracle 11 Reasons For Switching From Oracle To KDB 7 Reasons Why We Switched from Go to Fortran-77 Grammar errors are provided for free by The Author.
Lol!
Re: Why We switched from Python To Go
#9Point 3 Goroutines are more performant than python threads if you don't understand the difference between a thread and a routine.
How about asyncio in python 3 and gevent etc. in python 2?
Re: Why We switched from Python To Go
#10As an aside, the greatest thing about Python is StackOverflow one-liner solutions to common problems. How do you find your developer productivity fares in Go? To take a simple example, I was experimenting with C++ and had the simple task of "reading in a CSV". This simple C++ task does not have a nicely formatted, pre-approved, community rubber-stamped, best practice 500 green ticks StackOverflow top accepted answer (sometimes by Core Python / prominent PyCon developers) that I can just copy and paste.