Re:Key differences between Python 2.7.x and Python 3.x (2014)
by numerlo on Sunday May 07, 2017 @01:21PM
(#14286407)
While an unpopular opinion, I believe Python has lost its way too. "There should be one-- and preferably only one --obvious way to do it." - yeah I don't see it and that used to be one of the reasons I loved Python. They used to at least try for that to hold true, not it's like they try for the opposite. I much prefer Go these days.
[ Parent
| on HN ]
Re:Key differences between Python 2.7.x and Python 3.x (2014)
by goatlover on Sunday May 07, 2017 @01:48PM
(#14286538)
I understand preferring Go for static typing or performance, but not because a dynamic language gives you more than one way to do things. If don't like that Python has gained too many features, why not use something like Lua? Why jump into a more restricted language that's going to require you to write more code?
I get the argument if a programmer doesn't like dynamic languages in general, but not because one dynamic language has become too flexible.
Re:Key differences between Python 2.7.x and Python 3.x (2014)
by woah on Sunday May 07, 2017 @09:13PM
(#14288613)
I looked at Lua briefly instead of Go, but it looks like the concurrency story is lacking. Go also has an enormous standard library which helps for quick tasks.
Re:Key differences between Python 2.7.x and Python 3.x (2014)
by mixmastamyk on Sunday May 07, 2017 @03:01PM
(#14286952)
Go will probably be a mess in 20 years as well.
Re:Key differences between Python 2.7.x and Python 3.x (2014)
by poooogles on Sunday May 07, 2017 @04:48PM
(#14287573)
Yet still no generics.
Python even has limited generics now through mypy and pep 484.
Re:Key differences between Python 2.7.x and Python 3.x (2014)
by stefantalpalaru on Sunday May 07, 2017 @08:16PM
(#14288436)
> Yet still no generics.
You can use the gccgo runtime from Nim and get your goroutines and channels working with generics, macros and everything else Nim has to offer: https://github.com/stefantalpalaru/golib-nim