Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This is rewriting history. It was a serious goal at the time, and the language was all the better for it; the fact that it wasn't applied to tooling is the language's gravest mistake.


Maybe, but I have trouble thinking of a Python language decision that was made (or not made) because there should be a single way to do things. Can you think of one?


Pushing map/reduce/filter behind an import was done on the grounds that list comprehensions were the preferred way to express the same things.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: