4 ms·
LISP to Python (and therefore a job) is really just moving the left hand parenthesis after the function name, replacing spaces with commas, discarding everythi
by yawpitch 3y ago
LISP to Python (and therefore a job) is really just moving the left hand parenthesis after the function name, replacing spaces with commas, discarding everything good and right about homoiconicity, and embracing a nigh sickening amount of syntactic sugar around OOP.
Give me a decent LISP programmer who is willing to compromise and I can get you a job.
- skydhash 3y agoMacro is the name of the game and where you go from programming the business rules using a language to directly stating the rules themselves. Something like (def-action name ..) and it generates the whole routing handling, response generating code for you in a web application. Kinda like, but more powerful than the decorators you find in Flask.
- pjmlp 3y agoUnfortunately it also means throwing away compiled code, in JIT and AOT form. Still looking forward to the day Python ecosystem fully embraces it, without going through using C and calling it Python, or reaching to implementations that are 80% there and are largely ignored by the community. Thankfully the whole AI stuff is putting pressure into making JITs part of the standard Python workflow and I am looking forward to that Python 3.13 release.