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

To be specific, it's the lack of typing that makes large code bases in Python, Ruby, and especially JavaScript a huge pain compared to Java. It makes debugging much more difficult. Thankfully this is being fixed with stuff like Typescript and similar projects for both Python and Ruby.

Some people may argue, "but documentation would make this an non-issue". Guarantees built-in to the platform itself are more reliable than human aspirations, or automatic memory management as a feature wouldn't have gotten popular.



I actually found it was untraceable side effects from imports and ability to monkey patch that was worse. Related to the typing, but not totally the same. I would pick something like Clojure or F# now to control that. Side effects and coupling.


You can patch by linking a different library in C. What's the difference? I suppose it's easier in Python to patch. Seems like a good thing to me.


Didn't realize that monkey patching wasn't only limited to Ruby.


It tends to be frowned on in Python. Mostly because some fairly popular projects did it first, and if you monkey patch over them, you break them.

Consequently, there was a big disincentive to monkeypatching.




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

Search: