Welcome to PatsFans.com

Analyzing the Patriots Upcoming Free Agents

Discussion in 'PatsFans.com - Patriots Fan Forum' started by PatsFans.com Article, Feb 14, 2011.

Thread Status:
Not open for further replies.
  1. PatsFans.com Article

    PatsFans.com Article Rookie

    Joined:
    Sep 10, 2007
    Messages:
    3,203
    Likes Received:
    1
    Ratings:
    +1 / 0 / -0

    Analyzing the Patriots Upcoming Free Agents
    By: Derek Havens

    Analyzing the Patriots upcoming Free Agents for the off - season...

  2. Fencer

    Fencer Rookie

    Joined:
    Oct 2, 2006
    Messages:
    7,636
    Likes Received:
    7
    Ratings:
    +17 / 0 / -1

    BJGE -- of course he'll be back. The reasonable expectation that the Patriots will TRY to find a better player in no way undercuts his usefulness.

    Graham -- why would he come back to a situation in which he expects to not get the job? He'd be better served to go elsewhere.

    Arrington -- slot guy? Is that a fit for him? But of course he comes back, even if the roster were to be otherwise so stacked that he wouldn't project better than #6 or #7 DB.

    Mighty Quinn -- depends on how much of a logjam there is ahead of him with aging guys who've proved they can play, plus high picks.

    Page -- left his prior team for money, and doesn't have a great role locked up on the Patriots. Hmm. On the other hand, a multiyear deal for him would solidify the position past the expires-in-one-year deals other guys have.

    McGowan -- well, just let me make the general point that the two areas where there's a clear logjam, but it also might break, are safety and OL.

    G. Warren -- if enough young guys have great offseasons or come in via high picks, he might not have a job here. He might also get more money elsewhere for a more secure role. So he wouldn't be wise to stay unless the team pays him at a level that makes it likely they'll keep him around over their bottom youngsters.
Thread Status:
Not open for further replies.

Share This Page

unset ($sidebar_block_show); ?>