[Official] NFL 2010


Recommended Posts

So happy that football is BACK! The Saints Vikings game was a hard fought game, but I'll take a win over a loss.

Houston dominating Indy was a fun site to see. Typically I root for the Colts, and even though I picked them to win, I was pleased to see Texans win. Only their second time in the last nine years (17 games) they have beaten the Colts. If the Texans can continue to play that way for most of the season, winning the AFC South isn't so far fetched, much less reaching the playoffs. It's also the first time in the last seven to ten years that the Colts won't have won their first 12 or more games.

Chad Johnson's non-TD catch was a great catch, and it was only due to the technicality of the rule that it wasn't, which sucks for him and the Lions. I picked Chicago for that game, so no harm for me.

As for Kolb, he's got potential, but he's got really big shoes to fill (despite what most Eagles fans say, McNabb was a winning QB). Vick is in an ideal position with an ultimately untested QB starting. 175 yards passing, 103 yards rushing, that's what Vick so good for the Falcons. With Kolb suffering a concussion, Vick see even more playing time.

And lastly, I don't care if the Cowboys D and some of their players are among my fantasy teams. I want them crushed.

So happy that football is BACK! The Saints Vikings game was a hard fought game, but I'll take a win over a loss.

That was an awesome first game of the season, favre just couldn't get anything going with his receivers. AP is a beast though.

Houston dominating Indy was a fun site to see. Typically I root for the Colts, and even though I picked them to win, I was pleased to see Texans win. Only their second time in the last nine years (17 games) they have beaten the Colts. If the Texans can continue to play that way for most of the season, winning the AFC South isn't so far fetched, much less reaching the playoffs. It's also the first time in the last seven to ten years that the Colts won't have won their first 12 or more games.

I love watching the colts lose. It makes me happy seeing payton cry.

As for Kolb, he's got potential, but he's got really big shoes to fill (despite what most Eagles fans say, McNabb was a winning QB). Vick is in an ideal position with an ultimately untested QB starting. 175 yards passing, 103 yards rushing, that's what Vick so good for the Falcons. With Kolb suffering a concussion, Vick see even more playing time.

Vick was awesome today, my boy did well :) He had a TD on top of that too.

And lastly, I don't care if the Cowboys D and some of their players are among my fantasy teams. I want them crushed.

die cowboys die!!!!

Meh, Dallas haters.

Their O-line was horrible and the penalties killed them. Their offense couldn't get it done when they finally got within range, and they need a kicker desperately -- quit trying to save a damn roster spot by using the place kicker.

They'll still make it to the playoffs, but that was a pretty crappy loss.

Oh, and the Lions got screwed out of a victory.

Calvin Johnson's non-TD catch was a great catch, and it was only due to the technicality of the rule that it wasn't, which sucks for him and the Lions. I picked Chicago for that game, so no harm for me.

If that was a correct ruling they need to alter or get rid of that rule because their expectations of what you need to do in order for a catch in the end zone to count is rediculous. He had complete control of the ball from the second he touched it, he then put two feet down, sat down in the endzone, and then started getting up. Because the ball left his hand at that point its not a catch?

If that was a correct ruling they need to alter or get rid of that rule because their expectations of what you need to do in order for a catch in the end zone to count is rediculous. He had complete control of the ball from the second he touched it, he then put two feet down, sat down in the endzone, and then started getting up. Because the ball left his hand at that point its not a catch?

Not just because of that. It has to do with him catching the ball and "completing" whatever fall or hit happens with the possession. The argument could be made that his turning and using the ball to push himself up could be considered a second movement or act; if that were the case, it would have been ruled a complete pass, but the entire process of going up and landing, rolling, etc., the player must maintain possession. Here's a good read on the whole situation. It should have been a catch.

Yeah, I think they should just drop the whole "complete act" thing, if he has posession and comes down in bounds in the end zone why do they need anything else? It's not like he was juggling the ball or anything, if he follows through the catch rolling over, turning, or anything why should that act now be somehow bound to the catch? If that had happened in the open field and he wasn't touched and ruled down that would have been a fumble not an incompletion.

He had COMPLETE control of the ball. The only thing they seem to be bitching about is that he leg go of it when he was celebrating. Even when he had it in one hand, he had CONTROL of it. How that can be questioned is beyond me.

His feet were firmly planted, and when they were firmly planted, he had possession of the ball. Even when falling, the ball was securely in his hand. What happens after that SHOULD NOT MATTER. He caught it, was clearly in the end zone, and then fell AFTER catching it. But even WHILE falling, he had control of the ball. The issue seems to be that he let the ball touch the ground and let go of it. Why does that matter at all?

He had COMPLETE control of the ball. The only thing they seem to be bitching about is that he leg go of it when he was celebrating. Even when he had it in one hand, he had CONTROL of it. How that can be questioned is beyond me.

i just watched it again about 5 times, i completely agree with the call, you have to show you have completely control, the catch doesn't stop until you are completely down or out of bounds, he was neither when the ball came loose.

He's a idiot...mostly bad luck, but still a bonehead.

The ball touching the ground wouldn't have been a problem as long as the officials could clearly see he maintained possession, which he did up to the point of getting off the ground. Had he gotten up with the ball in hand instead of letting go, this wouldn't have been an issue.

i just watched it again about 5 times, i completely agree with the call, you have to show you have completely control, the catch doesn't stop until you are completely down or out of bounds, he was neither when the ball came loose.

He's a idiot...mostly bad luck, but still a bonehead.

He was completely down, though. He maintained position through the catch, to the ground, and when he was getting back up, he let the ball go. It was a very bad call and some ref should be on the brink of losing his job.

I'm over the moon about that Cowboys loss though. The Redskins still suck, but apparently the Cowboys are even worse. :laugh:

Also, I hate Vick (because I hate what he did and I also hate his alma mater, Virginia Tech [which had an absolutely hilarious loss to JMU, an FCS team, this weekend :D]), but he really should be starting for Philly. Kolb was complete ****.

He was completely down, though. He maintained position through the catch, to the ground, and when he was getting back up, he let the ball go. It was a very bad call and some ref should be on the brink of losing his job.

...

It was NOT a bad call at all! The ref made the call as the current rule states - blame the rulebook not the ref. I am all about refs making bad calls, but it was dead on. ESPN / FOX clearly showed the rule in its entirety and it was properly called. I'm sure this will raise questions as Calvin clearly did have possession and control - just not as the league defined it in this situation.

The ball touching the ground wouldn't have been a problem as long as the officials could clearly see he maintained possession, which he did up to the point of getting off the ground. Had he gotten up with the ball in hand instead of letting go, this wouldn't have been an issue.

You just admitted the exact opposite of what you're arguing. He maintained possession of the ball through the entire process of the catch. When he hit the ground, he clearly had possession of the ball, so him getting up and letting go of the ball is a nonissue. Furthermore, they reviewed it and clearly had the opportunity to see what you just stated. The NFL for some reason has decided that the review process is a joke now based on all the televised games I saw, as they almost never reverse a call now.

You just admitted the exact opposite of what you're arguing. He maintained possession of the ball through the entire process of the catch. When he hit the ground, he clearly had possession of the ball, so him getting up and letting go of the ball is a nonissue. Furthermore, they reviewed it and clearly had the opportunity to see what you just stated. The NFL for some reason has decided that the review process is a joke now based on all the televised games I saw, as they almost never reverse a call now.

I did no such thing. Let me explain it a bit more clearly: the ball can hit the ground and the pass be completed so long as the player has possession during and after the ball makes contact with the ground. Johnson let go of the ball while it was on the ground and by rule, that's an incomplete pass. This is one of rare catches that illustrates the problem with the ruling, but in nearly all other cases, the rule properly dictates the outcome.

Like I said before, had he gotten up with the ball rather than letting it go when it was on the ground, this wouldn't have been an issue for debate.

I did no such thing. Let me explain it a bit more clearly: the ball can hit the ground and the pass be completed so long as the player has possession during and after the ball makes contact with the ground. Johnson let go of the ball while it was on the ground and by rule, that's an incomplete pass. This is one of rare catches that illustrates the problem with the ruling, but in nearly all other cases, the rule properly dictates the outcome.

Like I said before, had he gotten up with the ball rather than letting it go when it was on the ground, this wouldn't have been an issue for debate.

That is not, by rule, an incomplete pass. The ground can't cause a fumble, just like it can't cause an incomplete pass when you have control of the ball when hitting the ground. What happened after he hit the ground is relevant to the situation unless you argue he didn't have control, and it seems pretty clear to me that he did, in fact, have control. Just because he had the ball in one hand doesn't mean he didn't have control. He was down, the ball was controlled securely in his hand.

To quote the rule, "if the regains control of the ball prior to the ball touching the ground, the pass is complete." So, even if you want to argue he lost control, he clearly had it secured in his hand before hitting the ground. At what point are you saying he lost control? Because that's the issue. His legs were clearly down, he clearly had control of the ball, and then it came out after making the catch. This isn't like the other instances where the receivers lost control of the ball or weren't properly handling it. He doesn't need two hands on the ball to have control.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Save 59% on training for a Claude AI Professional E-Degree by Steven Parker Today on offer via our Online Courses section of the Neowin Deals store, you can save 59% on the cost of training for a Claude AI Professional E-Degree. Note: Available to New users only. Master Claude AI for Productivity, Automation & AI-Powered Workflows Unlock the full potential of Claude AI with a structured, hands-on eDegree designed to help you master prompting, agentic coding, workflow automation, integrations, and AI-powered systems for real-world applications. Through four in-depth modules, you’ll learn how to use Claude beyond simple conversations and turn it into a practical tool for productivity, development, and business workflows. Whether you're a developer, entrepreneur, freelancer, creator, or working professional, this program teaches future-ready AI skills designed to help reduce repetitive work, improve efficiency, and build smarter workflows. With 100+ lectures, 8+ hours of video content, quizzes, practical projects, and a professional certificate, you'll gain hands-on experience applying Claude AI to real-world tasks. Master Claude AI from Prompting to Automation Advanced Prompt Engineering & AI Communication: Learn effective prompting techniques, context management, chain-of-thought workflows, & methods for improving Claude responses. Agentic Coding & Development: Learn AI-assisted coding workflows, debugging techniques, VS Code integrations, & Claude-powered development systems. Workflow Automation, Integrations & Plugins: Connect Claude with Gmail, Google Drive, Calendar, Chrome, MCP connectors, & productivity tools. Claude Cowork Ecosystem: Explore plugins, sub-agents, workflow systems, & practical AI automation strategies. Learn Through Real-World Projects 5 Practical Projects: Build projects focused on marketing workflows, AI websites, automation systems, educational content, virtual assistants, & AI-powered applications. 100+ Lectures & Quizzes: Reinforce learning through guided lessons & hands-on activities. Professional eDegree Certificate: Earn a certificate upon successful completion. Future-Ready AI Skills: Gain practical experience designed for productivity, development, & AI workflow applications. What You'll Get 4 Comprehensive Courses 8+ Hours of Video Content 4 Claude Tools Covered Master Claude AI from beginner to advanced level Learn powerful prompting and AI communication techniques Build real-world AI automation workflows Use Claude for agentic coding and faster development Explore plugins, integrations, and AI tools Automate repetitive business and productivity tasks Improve workflow efficiency with AI-powered systems Gain hands-on experience with practical projects Learn industry-ready AI productivity strategies Earn a professional eDegree in Claude AI mastery Good to know Length of access: Lifetime Redemption deadline: Redeem your code within 30 days of purchase Access options: Desktop or mobile Maximum number of device(s): Multi-device access Available to New users only Certificate of Completion ONLY Experience level required: All levels Updates included: Yes Closed captioning NOT available NOT downloadable for offline viewing Here's the deal Training for a Claude AI Professional E-Degree normally costs $49, but you can pick it up for just $19.99, that's a saving of $29. For terms, specs and license info, click the link below. Deal Price Get trained for just $19.99 (was $49) Although priced in U.S. dollars, this deal is available for digital purchase worldwide. Support queries If you have queries or need support for any of the Neowin Deals, please use the contact form here. Neowin Deals are managed and sold by StackCommerce who represent Neowin on an affiliate basis. Why we post these deals We post these because we earn commission on each sale so as not to rely solely on advertising, which many of our readers block. It all helps toward paying staff reporters, servers and hosting costs. So for those that keep moaning and complaining, be thankful we're still online for you to even do that. Other ways to support Neowin Whitelist Neowin by not blocking our ads Create a free member account to see fewer ads Make a donation to support our day to day running costs Subscribe to Neowin - for $14 a year, or $28 a year for an ad-free experience Disclosure: Neowin benefits from revenue of each sale made through our branded deals site powered by StackCommerce.
    • All good features. But it is not an actual Windows app. I’d rather use the PWA. Meanwhile but versions - Classic and Modern - are full of bugs and inconsistencies. Yuck.
    • Had one user who switched to new Outlook, could not send an email he sends weekly due to file size to large error, works fine in classic Outlook. Issue just today, user received a meeting invite, when she went to add the meeting to the calendar it opened up New Outlook (she has classic open) and we could not add the invite to her calendar, We had her switch to New Outlook, it crashed when we tried to add the invite. Still hot garbage.
  • Recent Achievements

    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      468
    2. 2
      PsYcHoKiLLa
      250
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      77
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!