The sea should be marked as C considering that’s what you’ll discover when you get deep into it.
https://en.m.wikipedia.org/wiki/PyPy
Their greatest mistake was not naming it Uroboros.
A hammer is beginner friendly, but learning to use a hammer doesn’t necessarily mean you’re ready to build a house with it.
For all of those, Lisp is the more logical choice. Plus, whitespace as syntax is the worst possible design decision.
Ok, but what if an entire programming language is made of whitespace?
https://en.wikipedia.org/wiki/Whitespace_(programming_language)
Still easier to refactor than Python. ;-)
Lisp is the more logical choice.
Relevant XKCD. Python has replaced Perl, but things have otherwise changed quite little.
Perl is the only language that looks just as incomprehensible before and aa rot13 transformation.
Python on the other hand is the only language that will cause your application to stop working because you mixed up tabs and spaces, even though it looks perfectly fine on your scr.
And lisp is hard to say if you have one.
Perl is the only language that looks just as incomprehensible before and aa rot13 transformation.
Lol. You’re not wrong.
It is absolutely fine to mix tabs and spaces in Python, as long as you are consistent about it. It’s not recommended though, as it’s easy to mess up if you’re not paying attention. Most IDE’s will convert tabs to spaces anyway so it’s a bit of a non-issue.
I still write more Perl than Python these days.
I’m kinda jealous. I don’t miss maintaining production Perl code, but Perl was more fun to code in.
Feel free, it’s still out there!
That syntax decision is single handedly why I avoid python if possible
The mistake was choosing a language, and afterwards searching for a use to the language you just learned.
Dynamic typing, special and unique syntax for every language feature, interpreter intrinsics
