I don’t know much about programming, but I’m somewhat confident in the fact that 343 wasn’t just leaning on a switch labelled “make the menus lag like a fat kid at a 5K”. What changes were made behind the scenes so that the menu would work better?
They only made it load faster and lag less.
> 2533274823519895;1:
> I don’t know much about programming, but I’m somewhat confident in the fact that 343 wasn’t just leaning on a switch labelled “make the menus lag like a fat kid at a 5K”. What changes were made behind the scenes so that the menu would work better?
Do we really have to know? Does it matter that much on how they did it?
All we should care about is that it loads faster now. Maybe through optimization, maybe through removing a bottleneck that caused this issue.
All that matters to me at the end of the day is that it loads faster.
EDIT: Though, on consideration, they probably rewrote parts of how the menu loaded up. It seems to load the menu well before the images do, and the behind-the-scenes explanation is that they worked hard on it. The issues are probably incredibly technical.
> 2533274823519895;1:
> I don’t know much about programming, but I’m somewhat confident in the fact that 343 wasn’t just leaning on a switch labelled “make the menus lag like a fat kid at a 5K”. What changes were made behind the scenes so that the menu would work better?
No, you’re wrong. There is a switch for that, lol 
I only know some basic vba and C++ and from my experience the main focus is to make stuff work. Doesn’t mean the code is as efficient as it can be but it works. They would have gone in and rewritten sections of code, reordered some of the subroutines and possibly cut bits that are considered unnecessary now.