Borderlands and Halo have completely different engines. Halo button glitches are related to the way the animation and animation cancel works with the rest of the systems. It's intrinsic. The two games simply aren't comparable. May as well compare it with Street Fighter.
That said, controls, button glitches, animation and lots of other systems are stuff we're obviously set on improving in the future.
OK, I'm likely going to get heat for this from you or someone else here, but I have to comment as this annoys me every time it's brought up.
@thebold: SO WHAT? What on earth does the action that cancels the animation/causes the glitch have to do with the button on the controller that maps to that action? This does not now nor has it ever made sense to me.
An example of why this seems ludicrous: When people talk about button glitches and Halo, the most recent obvious topic is Halo 2 (although 3/Reach/4 have all had some, however minor or impactful). In Halo 2, there's the infamous "BXR" glitch, where one presses B to melee, X to cancel the animation early, and right trigger to fire their weapon. This is using the default button layout. I have a friend who used Green Thumb, mostly because he's crazy. For him, melee is performed by clicking the thumbstick. I guess that means he can't perform the BXR glitch, right?
WRONG! It works just fine, even though the buttons are completely different. So what's the difference between using B, the bumpers, thumbsticks, whatever, to perform the actions required in game (aiming aside)? Is there an *actual* reason Halo games can't do this?
If the reason is honestly as simple as "It wasn't a priority and we couldn't get to it" (because there is work involved in making the interface), I would be just fine with that. But dodging the question by saying that 2 FPS's aren't comparable just because they use a different engine (which, again, has nothing to do with the buttons you press and how that info is fed to the 360), or saying "glitches bad" doesn't cut it.
I'm not coming out in favor of more button glitches. I'm not even taking a side in that debate because I lean both ways and that's a legitimate discussion. My issue is, since we can demonstrably show that the button itself has nothing to do with the action performed, what's the problem? As a technically proficient person with experience with systems with many more inputs than a simple 360 controller, I almost feel insulted by this logic that you present on the subject.
EDIT: To clarify, my question is regarding custom controls, not the current glitch debate.