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

>... but taken literally it suggests assinine ideas like using bubble sort instead of merge sort for a large set not because of any memory footprint constraints but because it is easier to read.

No, it doesn't suggest this at all. It means use the merge sort but implement it in a clean, understandable way.



It means use the merge sort but implement it in a clean, understandable way.

https://rosettacode.org/wiki/Sorting_algorithms/Merge_sort - which ones of these do you consider objectively "clean and understandable"?

Why should any of them (Prolog, Mercury, J, Common-Lisp, etc) be considered "not understandable" instead of "not familiar to the reader"?




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

Search: