Angry Jesus writes:
We all know that python is slower than compiled languages like C. But what can you do about it? Jake VanderPlas, director of research in the physical sciences for the university of Washington's eScience institute, digs into python's internals to explain how it works and what program design choices you can make to use python efficiently.
I have Pythonista friends who tell me that Python is a transformable dialect of LISP. I ask them why they don't transform it to LISP and run it through the well-proven LISP to C compilers (to juice their runtime performance).
They don't answer then question and we eat pizza instead; wait about three months and they tell me that Python is a dialect of LISP.
I have no idea whether your friends are right, but even if they are, actually writing a Python-to-Lisp translator would still be a lot of work. Probably more work than justified by the gain it would give them. Especially if their programs just don't need that runtime optimization. For example, speeding up code that spends most of its time waiting for I/O is generally useless.
I have Pythonista friends who tell me that Python is a transformable dialect of LISP.
I've never heard this claim (but I don't know many proper Python fans).
There's a lot of good stuff in Python, but transformability? No. LISP-dialect? No, of course not.
Next time they try it, point them at the failed Unladen Swallow project.