

13·
6 days agoFeels like it would be quicker and easier just to write the code myself at that point…
Feels like it would be quicker and easier just to write the code myself at that point…
Sure but who’s got time for all that aggravation? Especially if it’s not part of the codebase I have to work with personally. LGTM and let it be someone else’s problem.
TL;DR: For historical reasons stacks growing down is defined in hardware on some CPUs (notably x86). On other CPUs like some ARM chips for example you (or more likely your compiler’s developer) can technically choose which direction stacks go but not conforming to the historical standard is the choice of a madman.
Time for the UK government to make good on all that money we spent rescuing OneWeb…