I like how at the start of the line it explicitly says “out of memory” but we’re just pretending this is some satanic bullshit.

She obviously read the error to find “kill process” and “sacrifice child” but still ignored the memory error

I didn’t know we even had dynamic compiled languages but a quick google search tells me Lisp counts. Wonder if Musk actually knew that or if this screenshot is taken mid dunning-kruger.

If you think this is more structured than traditional SQL, I really disagree. Is this a select * query, it’s ambiguous. Also what table is being queried here there’s no from or other table identifier.

When I went rooting around to find it. I figured it was some QA process that starts 5 seconds after the video loads (the timer seems to be async and the code sends a promise off while it waits). Of course, it’s all minified JS so it’s a huge pain to read.

Yes but no. Modern PHP lets you put types in function signatures and it will then attempt to convert your inputs to those types at runtime.

JS/TS and Python don’t do this. They have optional type annotations that’s treated as syntactic sugar. You can use static checkers against this but if you get an error like “expected string got int” you can still run the code. It won’t behave any differently because you have annotations.

Ahh yes memoization, the complicated way to say “remember this, I might need it again”