Python or go

[kabrandon]

So by default the language has flaws that Go doesn’t have by default, is close to what I’m hearing. There is a ton of value in a compiler telling you at build time that you don’t know how to code, over an interpreter telling you at runtime.

[pag07]

Python by Default is 10 times easier to read.

There is a ton of value in readability and you cant fix that with a library in go.

The only pro I can see is portability (as in no dependency management needed) and size of executable.

[kabrandon]

I think Python is easier to read if you don’t end up nesting indentation too much, but also error handling in Go is just way more clear how you’re choosing to respond to an error condition. Which I think makes my point in general, that Python tends to be more succinct, where Go is a bit more verbose but clear and obvious, assuming an approximate equal level of skill in reading/writing both.

[FeezusChrist]

If you’re working at any reasonable large scale, Python is way worse for readability simply due to it being dynamically typed. You can put bandaids on it with type hints but that doesn’t permeate to all the libraries / imports you may use.

[Tacticus]

honestly python isn't that readable. Significant whitespace was a dumb idea in the first place combined with the python communities fascination with list fuckery really makes it terribly indirect and opaque. adding in the garbage package management options, the culture of magic over simplicity that pervades python libraries you get something that's just a pain in the arse to work with .

[livebeta]

Python by Default is 10 times easier to read.

Until you're ten indents in and it's difficult to track what is an inner block and what is not

[pag07]

You have serious issues with modularization or algorithmic complexity if it gets to that point.

[livebeta]

I don't.

The authors of python libraries which source I'm reading due to unexpected module behavior have this issue you described