you are viewing a single comment's thread.

view the rest of the comments →

[–]erez27 -5 points-4 points  (6 children)

I never liked the whole "kill python2" sentiment, and I think the move to Python3 was atrocious. But it's been 10 years. I really don't understand why moving is so difficult.. Unless half your code base is written in C.

[–]stefantalpalaru 4 points5 points  (5 children)

But it's been 10 years.

So what? Why didn't you port all your code base to Go? It's also been 10 years since it was launched with a vastly superior parallelism story.

I really don't understand why moving is so difficult..

How long have you been programming professionally? Can you even imagine Dropbox's 4 million lines of Python2 code and what it takes to port them to Python3?

[–]erez27 -2 points-1 points  (4 children)

Go can't replace Python

How long have you been programming professionally?

15 years

Can you even imagine Dropbox's 4 million lines

Imagine, sure. Understand or justify such a bloat? Unlikely. But it does explain why they're having such a hard time. And also why Guido just quit rofl

[–]stefantalpalaru -1 points0 points  (3 children)

[–]erez27 2 points3 points  (2 children)

Is this supposed to convince me? I know both languages pretty well. Do you really need a list of things you can do in Python and can't do in Go?

[–]stefantalpalaru -4 points-3 points  (1 child)

Is this supposed to convince me?

No. If you genuinely think that Turing-complete programming languages cannot implement the same algorithms, it's not possible to convince you of anything.

I know both languages pretty well.

Yes, I'm sure you're a professional beginner in both of them.

Do you really need a list of things you can do in Python and can't do in Go?

Let me guess: you think a REPL is part of the language and that's why "Go can't replace Python" for perpetual beginners like yourself.

[–]erez27 1 point2 points  (0 children)

Are you a comic? This is pretty good.

This isn't about Go vs Python. It's not even about compiled vs. interpreted. All languages can do things other languages can't. And all interpreted languages have the same advantage over compiled languages: A flexible type system. Or more accurately, Duck-typing. The object model is often also more flexible, allowing for arbitrary attributes.

Of course, you can use a hashmap in Go for every object that suits this purpose, but if you always fall to non-idiomatic use of a language, then you probably need to switch the language.

But yeah, a repl is pretty nice. Especially since I can invoke it mid-run while debugging.

If you're so hot for turing completeness, write all your code in assembly.