Yup...i can confirm that

None of that is "Python". You want to learn a language and automatically know everything there is to know using Math?

A hammer is beginner friendly, but learning to use a hammer doesn't necessarily mean you're ready to build a house with it.

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 Ouroboros.
- The reason C becomes relevant to Python users isn't typically because the interpreter is written in C, but because so many important libraries (especially numpy) are implemented in C.

The mistake was choosing a language, and afterwards searching for a use to the language you just learned.

Among all of them at least python is the choice generically people learn when they don't want to learn programming, just want to program stuff as a helper tool to manage data. For those, python is just fine and the learning material around is tailored to for that.

That's how you trick people into programming. You then see people making scripts that take days to run, but it's fine, they're only going to use it twice and are busy enough to be able to wait
- You then see people making scripts that take days to run, but it's fine, they're only going to use it twice and are busy enough to be able to wait
  
  Sponsored by "terrible python code by Matt Parker"

Dynamic typing, special and unique syntax for every language feature, interpreter intrinsics

Dynamic typing is the source of very amazing errors, see JavaScript.
- I think the problems there are exacerbated a lot by over-eager type coercion and other crappy design decisions inherited from almost 30 years ago
- [object Object]
  
  !Reddit moment.!<
Operator overloads, descriptor protocol, decorators
- Operator overloads are excellent for readable code when used well - I object to their inclusion on this list.
Honestly, I've been using type hints very heavily since they became a thing. I just use IDE completion too much to do without them.

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 after a 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.
  
  Edit: aa -> after a
- I still write more Perl than Python these days.
That syntax decision is single handedly why I avoid python if possible
- For me it's dependency hell. Almost as bad as npm.
I've had very few issues with whitespace in my decade or so of using python, especially since git and IDEs do a lot to standardize it. I'm a Python simp, tho
You say that, then use a language that allows you to do this (it's not lisp)

if (foo); { bar(); }
- You can make embarrassing mistakes in virtually any programming language that's not too esoteric.
  
  When I still used Python for prototyping (today, I usually use Go for that), it happened much too often that I did this:
  
  if foo: bar() foobar() # syntax error
  
  In Lisp, however, both errors are much harder to make (not even considering GNU Emacs's superb auto-indentation - which is what most Lispers use these days, as far as I know):
  
  (when foo) ;; <- obvious! (bar))
  
  (when foo (bar) (foobar) ;; <- still valid (quux)) ;; <- also still valid
I mean, their goal was readability, and at least they're trying new things.

Was this made with AI?

we really need a proper beginner-friendly language that has no maths