Bracket property access gets fast, and Ask follows your timeline

More speed where real code actually lives, and Ask that respects when you read something. First, speed. Minifiers - the tools that shrink a site's code before it ships - rewrite `thing.name` into `thing['name']` wherever they can, so most of the web's JavaScript reads properties with brackets, not dots. The engine sped up the dot form long ago but left the bracket form running at plain-interpreter speed. Now a constant bracket key is recognised as the same property read and gets the same fast path: that access runs about three and a half times faster, level with the dot form. It stays exact - anything unusual behind the access (a value inherited from a prototype, a getter, a live page element) quietly takes the careful path, so nothing changes but the speed. Building an array by pushing several values at once (`list.push(a, b)`) now compiles too, about twice as fast. The whole engine gate holds at 6375 of 6375, proven equal to the plain interpreter by a differential fuzzer. Second, memory. Ask your reading now follows your timeline. When two pages you read answer a question equally well, the one you read more recently comes first - usually the thing you were just looking at is what you are asking about. It is a gentle tiebreaker, never enough to bury a genuinely better answer from an older page.