3 ms·

- No memory management - No pointers - No cache - No branch predictor - No interrupts - No endianness - No alignment What exactly are we teaching student

• est 12y ago
  The best part is you can't forEach or map an HTMLCollection object. You have to [].forEach.call it. lol
  • bzbarsky 12y ago
    HTMLCollection is a messed-up puppy, sadly. Consider this markup: <img name="forEach"> <script> document.images.forEach.src = "something"; </script> This works, today, in all browsers. Adding "forEach" to the proto chain of HTMLCollection would make this code no longer work, so no browser is willing to add it for fear of breaking sites. The answer is to stop using HTMLCollection. What's worse is that NodeList doesn't have this named-lookup issue, but putting Array.prototype on its proto chain (the obvious simplest way to get all the array goodies) again breaks websites, because some people uses "instanceof Array" to assume things about how an object will interact with Array.prototype.concat. Long story short, making improvements to the DOM is very hard because of the two decades of weird website hacks that are supposed to not get broken in the process...
• Turing_Machine 12y ago
  Turing machines don't have any of those things either, and they are certainly computers. Universal ones, in fact