<video id="#player">
....

It took me way to long to realize why the queryselector failed

document.querySelectorAll('.foo')[0]

Because querySelector was too efficient

Ok I love JavaScript but this is enough.
I know selectors like these shouldn't exist, but double escaping? Hell no! I didn't even know it was a thing! I wonder what's the highest level of n escaping there is out there.

I never understood the programming language discussion thing. In modern programming, all you do is gluing APIs together, no matter if they're third party or built-in. My JS code is literally 95% fetch() followed by querySelector.

All built-in APIs that do something useful are just linking C++ modules. If you're not doing stupid shit, Python is exactly as fast as C++ or Rust.

The only scenario where speed matters is algos. Guess what? You should write your algos in C and link them to your Node/Python/Go/whatever code. And don't even get me started on reinventing algos. Do you really think you can write an algo in one evening that will be more efficient than what the guy whose PhD thesis it was a part of?

Just because some engine parts require the precision only a million-dollar CNC machine can provide, doesn't matter you have to cut the whole car out of a solid block of high-performance engine block alloy.

Remember kids, sorting array in Python is always faster than sorting array in C, because Python's sort was written by someone else who's smarter than you, went through years of scrutiny and iteration, and doesn't have stupid novice algo complexity errors.

Grow up.