Talk:Modular inverse: Difference between revisions
→Removed Paddy's message requiring normalisation to 'good Python style'
Line 23:
Now that Python has matured, and outgrown its BDFL infancy, that scar tissue can begin to heal (`reduce` will in time emerge from the purdah of `functools`, to which the dictator truculently relegated it when the Python developer community would not let him trash it) and the huge community of Python library users can begin to be better served by a genuinely multi-paradigm and less damagingly limping corpus of Python use.
Functional code optimises more for correctness, speed of assembly, degree of code reuse, and ease of refactoring, than for compression of time and space. That may well make it 'bad' for some contexts and projects, but it also makes it excellent, and clearly preferable, for others. 'Pythonic' and good are *very* far from being natural synonyms, and there is room on Rosetta Code for Python code which explores both main areas of the multi-paradigm space, and is optimised for various different contexts. 'Good' code above all returns correct results, and is well optimised for a particular organisational context. Bad code, and incorrect results, are not *in any way* redeemed by being loyally 'Pythonic' or 'Guidonic'. That mould has now broken. The young Python has broken its shell and emerged from its egg. A cause for celebration. Don't try to sellotape it back into the fragments. [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 22:21, 25 October 2018 (UTC)
| |||