You hate math? Get out, just get out.havokeff wrote:38-18 on the year.
48-22 if you count week 3 which I didn't post here.
Can anyone figure out the winning %? I hate math.
.679 on the first, .686 on the second. (I rounded up)
Moderator: Edi
You hate math? Get out, just get out.havokeff wrote:38-18 on the year.
48-22 if you count week 3 which I didn't post here.
Can anyone figure out the winning %? I hate math.
Sweet. Thanks. And it's not so much a hatred as just a complete fundamental non-understanding of itDarth Quorthon wrote:You hate math? Get out, just get out.havokeff wrote:38-18 on the year.
48-22 if you count week 3 which I didn't post here.
Can anyone figure out the winning %? I hate math.
.679 on the first, .686 on the second. (I rounded up)
If one part of the foot initially hits the ground in bounds (like the toes or the ball of the foot), but the rest of the foot touches out of bounds (like the heel) in the same motion, then the whole foot is considered out of bounds. In other words, having one part of your foot land in bounds a spilt second before the rest of the foot hits out of bounds in the same move does not give you a catch. Floyd's toes landed in bounds when he caught the ball and the rest of his feet were off the ground until the defender pushed him out. Touchdown, San Diego.Jason von Evil wrote:Texans? Wtf? That's the first time I've ever heard of them.
Anyways, question about the Chargers/Steelers game about a week or two back. The commentators were talking about the Chargers first TD of the game and why the ref had to rewatch a replay of whoever it was catching the ball. One of them mentioned some little known rule that said something to the effect that if a player jumps, catches the ball and lands either ball heel or heel ball first near the boundary line, the TD didn't count. Supposedly that was the reason the ref had to watch the replay (which didn't happen, because the machine refs use broke).
The hell kind of rule is that? Who gives a shit what part of the foot touches the ground first?
EAGLES DEFENSE: "Coach I swear we all counted 11 guys!"RedImperator wrote:ATTN. EAGLES DEFENSE:
If have counted all your fingers, and your pecker, and there are still extra players on the field, you have too many and somebody has to leave.
Jesus Christ.
They picked quite possibly the worst time to do it too.RedImperator wrote:ATTN. EAGLES DEFENSE:
If have counted all your fingers, and your pecker, and there are still extra players on the field, you have too many and somebody has to leave.
Jesus Christ.
How does that happen? Do they not have someone among the 173 people on the sidelines who can keep a simple count?RedImperator wrote:ATTN. EAGLES DEFENSE:
If have counted all your fingers, and your pecker, and there are still extra players on the field, you have too many and somebody has to leave.
Jesus Christ.
Jamie Dukes on the NFL Network said this is the worst team since the Jets under Rich Kotite. Kotite was known as Rich Kotex on the grounds that his team played like bloated pussies. They went 1-15. I don't see any team the Raitards have on their schedule that they have a good chance of beating. The game earlier tonight was about as good a chance as they could hope for: a division rival looking ahead to the next opponent and playing like shit -and they still lost by 10 points. Maybe they can get it up against a floundering Chiefs team, but I doubt it. Just as no soldier or Marine in 1971-73 wanted to be the last man to die in Vietnam, no professional team wants to be the one to give the Raitards their only win this season.thejester wrote:Dude. Oakland suck.
Players are substituted in groups, not individuals. So the extra guy probably thought he was supposed to be out there in the defense called. He realized he wasn't supposed to be out there until it was too late and couldn't get off the field before the ball was snapped. He got an earfull from DC Jim Johnson on the sideline. That fuckup pretty much cost them the game.FSTargetDrone wrote:How does that happen? Do they not have someone among the 173 people on the sidelines who can keep a simple count?
Oh, and one other thing: Clock management.
What's wrong with them - specific departments (QB seemed pretty awful) or just shit across the board?Elfdart wrote:Jamie Dukes on the NFL Network said this is the worst team since the Jets under Rich Kotite. Kotite was known as Rich Kotex on the grounds that his team played like bloated pussies. They went 1-15. I don't see any team the Raitards have on their schedule that they have a good chance of beating. The game earlier tonight was about as good a chance as they could hope for: a division rival looking ahead to the next opponent and playing like shit -and they still lost by 10 points. Maybe they can get it up against a floundering Chiefs team, but I doubt it. Just as no soldier or Marine in 1971-73 wanted to be the last man to die in Vietnam, no professional team wants to be the one to give the Raitards their only win this season.thejester wrote:Dude. Oakland suck.
Barely. Did you see that catch? It almost didn't count. If it weren't for the whole Reply Review thing, it wouldn't have.phongn wrote:The Bucs won?
The Raiders are actually a reasonably talented bunch. They're deep, especially at receiver, but they don't play like a team at all. They're like Detroit last year, after most of the Lions had quit on the season, except that unlike the Lions, NONE of the Raiders have decided to step up and try even harder just for themselves. The Raiders' have a bad linebacking corps, and their offensive and defensive lines are soft. At QB, they're pretty deficient, especially with Brooks on the sidelines injured--and he's not real good, himself.thejester wrote:What's wrong with them - specific departments (QB seemed pretty awful) or just shit across the board?
It's hard to say that the Radiers have a soft D-line and bad linebackers. They get ZERO support from their offense and are forced onto the field constantly. Talk to Warren Sapp about how that feels as I'm sure he is having flashbacks of the shitty Bucks offense. The problem is thie defense isn't NEAR as good as that one was.Master of Ossus wrote:The Raiders are actually a reasonably talented bunch. They're deep, especially at receiver, but they don't play like a team at all. They're like Detroit last year, after most of the Lions had quit on the season, except that unlike the Lions, NONE of the Raiders have decided to step up and try even harder just for themselves. The Raiders' have a bad linebacking corps, and their offensive and defensive lines are soft. At QB, they're pretty deficient, especially with Brooks on the sidelines injured--and he's not real good, himself.thejester wrote:What's wrong with them - specific departments (QB seemed pretty awful) or just shit across the board?
All-in-all, the Raiders have a better chance of going 0-for-2006 than the Bears or the Colts have of running the table the other way.