@slightlylate Hey there! I’m looking for some history about javascript. Do you happen to know why user code can override native methods? Or is it possible that was accidental?
-
-
-
Replying to @slightlylate
Yes exactly! It goes without saying that being able to override these things is _super_ useful. But I'm trying to learn why the decision was made.pic.twitter.com/TQgu21N3Gp
1 reply 0 retweets 1 like -
Replying to @vazac
That's what the default behaviour of every other JS object/property is. Only rationalized in ES5 with property definition flags.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
Right, but I'm looking for the _why_. And maybe I'll never find it. But it can't be particularly common for a language to allow itself to be destroyed irreparably (for the lifetime of the page). It's one of my favorite things about javascript.pic.twitter.com/EEyU8rPeW1
2 replies 1 retweet 5 likes
C lets you do pointer math and (naively compiled) do all sorts of crazy. Java has reflection and bytecode shenanigans. Most languages let you get away with murder, they just make you work harder for it :-)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.