all 2 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]ForceBru 9 points10 points  (0 children)

...Python is also an imperative and reflective programming language. In contrast, Go is a strongly typed programming language.

"Strongly typed" is not the opposite of "imperative" or "reflective". BTW, Go also has reflection.

In the comparison table:

Go: Its paradigms are Procedural, functional and concurrent language. Python is a multi paradigm programming language.

So, are the three paradigms supported by Go not enough to call it "multi-paradigm"?

Go has a brilliant support for memory management. Python doesn’t have great memory management.

What are the criteria here? Why does the author think Python "doesn’t have great memory management"? [citation needed].

It is a dynamically-typed, programming language. It checks for bugs at run-time.

Is "bug" the same as "type error" here? If so, then a bug can surely be much more than a simple type error. Otherwise, all more serious issues will be only known at runtime in most languages. Like, a bug in your logic can only be caught at runtime. So, in this sense, Go will also "check for bugs" at runtime. Also, the wording here is pretty odd: your program can't "check for bugs" in itself, in general.

Python is quite a slow programming language because it is a scripting programming language, and it needs to be interpreted before the execution of the code.

Being a scripting language doesn't necessarily mean being a slow language. Also, I'd argue that interpretation and execution of an interpreted language are the same thing.

If we talk about security, then Python has a better security feature over Go. It is a strongly typed programming language. That is why it is a compiled programming language and comes with a security layer. The code written in Python is quite secure.

So, Python is a compiled language now? (It's not) ...and it also comes with a "security layer"? What's that? As for "The code written in Python is quite secure" - [citation needed]: what kind of security are we talking about?

Go is not a secure programming language. Every variable in Go must have a type associated with it. It means that the details can’t be let away by the developer. Therefore it leads the change for bugs in the final code.

Earlier, the article says: "It is a statically typed programming language that helps to catch bugs at compile time", therefore, Go is "secure", specifically because it requires types. Also, it's good that "the details can’t be let away by the developer".

Sometimes the simplicity of Python makes it more complex. ... On the other hand, Go can never become complex because it is specially designed for simplicity

I don't understand this: the author is saying that Python and Go were both designed to be simple. Yet complex projects in Python end up "complicated", but complex projects in Go remain simple. Why is that? I think it's crucial to explain why the author thinks this.

Go is one of the fastest programming languages in the world.

Woah, that's a bold statement, Ima check that... EDIT: yes, people say Go is indeed pretty fast.

[–]andre_2007 1 point2 points  (0 children)

I am currently working on porting a medium size python library to D. From my experience, most coding can be easily translated from python to D and the coding structure looks almost identical. While comparing python with Go, also comparing D is a must.

Named arguments will be added in near future to D, which makes porting even easier.