Jump to content

eSJayDee

Community Member
  • Posts

    1,763
  • Joined

  • Last visited

Posts posted by eSJayDee

  1. 1 hour ago, JMM said:

    Then you didn't watch Thurman who was an MVP  and an incredible dual threat. OJ was strictly a runner

    Actually, in '75 (the 1 yr in his tenure that we had a good/great, balanced attack) OJ caught 7 TDs & averaged like 16 yds/catch!

    • Like (+1) 1
    • Thank you (+1) 1
  2. 4 minutes ago, Einstein said:

     

    I think you’re vastly underestimating the velocity on a deep pass. The ball gets there a lot faster than you think.

     

    For example, the high arching moon-ball hail mary against KC was 3.38 seconds from the time it left Allen’s hand until it touched the first players hand in the end zone.

     

    A normal deep pass - like the 52 yard (in the air) deep ball TD from Allen to Emmanuel Sanders in the 2021 playoffs took only 2.55 seconds after it left Allen’s hand.

     

     

    You might be right, I don't think I've ever timed a pass, or at the very least, it's not something I'm familiar w/.  I'm basing that estimate on punts, which I am quite familiar w/, both my own & pros.  Though it's contrary to the typical intent, I'd think it difficult to punt a ball 50 yds in the air & have it arrive in < ~3 seconds.

    Thinking about it further, consider someone running under a "bomb".  Considering they're already at speed, they'd easily cover 30+ yds once a ball is airborne.  I don't think QBs have to lead them that much so I guess that makes this strategy more viable.

    • Agree 1
  3. 59 minutes ago, eSJayDee said:

    If it's a "short" hail mary & you've got a QB w/ a good arm, it might be barely feasible.  Although the defenders are bunched, they're still spread out for maybe 8-10 yds, and they're not on the sideline, but rather more toward the middle of the field.  So even if you set up "in the corner", you've got at most 30 yds before other sideline.  I doubt any QB can throw more than 50 yds in < ~3 seconds.  Once that ball is airborne, a DB can run almost 30 yds in ~3 seconds.  If you can somehow time a receiver receiver surreptitiously break for the other sideline just as the QB is throwing, it might be viable.  But again, I think only for a "short" hail mary.

    An added potential bonus of attempting this strategy is that it's more likely to draw a DPI penalty.  DPI isn't usually called on the melee that is typically a hail mary, but it might be (much) more likely if it's a defender hauling butt to try to defend a single receiver that's all by his lonesome, & further gives the receiver the opportunity to try to "induce" it.

  4. If it's a "short" hail mary & you've got a QB w/ a good arm, it might be barely feasible.  Although the defenders are bunched, they're still spread out for maybe 8-10 yds, and they're not on the sideline, but rather more toward the middle of the field.  So even if you set up "in the corner", you've got at most 30 yds before other sideline.  I doubt any QB can throw more than 50 yds in < ~3 seconds.  Once that ball is airborne, a DB can run almost 30 yds in ~3 seconds.  If you can somehow time a receiver receiver surreptitiously break for the other sideline just as the QB is throwing, it might be viable.  But again, I think only for a "short" hail mary.

  5. 1 hour ago, Big Turk said:

     

    What good would extra time outs do in that situation? You are working against the clock not lack of TOs

    W/ 20 seconds & TOP left, you have the opportunity of 1 play in-bounds before you have to try the FG (If it's really short, you could probably spike the ball.)  W/ 2 TOs, that means 2 plays, if each of them are ~20 yds, that puts you in FG range.

    I seem to recall the Chiefs doing it against someone in only 13 seconds. ;)

  6. 39 minutes ago, FireChans said:

    Are they more expensive that losing $5M of guaranteed income?

    I doubt it.  But... that income is not entirely guaranteed.  Also, he does still have to work for it.  Further, one could argue the $ isn't really "lost", merely delayed, or at least this is partially the case.  ie he chooses to work 4 more yrs.  Does it really matter if it's '23-'26 or '24 thru '27?

    As for what I expect the "math" to be like (this is just a hypothetical I'm basically pulling out my butt, IDK real numbers) - imagine you're a "regular" wage earning & you're presented w/ a "tenuous" opportunity to earn $1m/yr for "a few yrs".  That $1m is ~$600k after taxes.  How anxious would you be to pay $100-$200k (presumably not tax deductible) to insure said income, knowing that a) only a handful of the ~2000 players/yr end up missing out on a similar opportunity due to circumstances you want to insure against and b) collecting said payout in the event it's warranted, will possibly (likely?) involve a (costly) legal battle w/ no actual assurances that you'll indeed collect.

    Not saying no one insures themselves for such circumstances, but I suspect it's not so dumb (& likely prudent) to actually make a decision NOT to insure.

    • Like (+1) 1
  7. 1 hour ago, FireChans said:

    I don’t understand why these athletes don’t take out gigantic insurance policies for stuff like this.

     

    just seems prudent.

    Probably cuz they're gigantic expensive.  I used to work in an industry (Commodity Trading Advisor) where we're potentially liable for substantial amounts of $.  We looked into insurance & it was highly imprudent given the probability of a liability.  How often does something like this happen?  Very seldom.  Also, good luck getting a payout.  You think insurance companies will just hand out a 6 or 7 figure amount w/o some legal fight to try to weasel out of it.

    1 hour ago, FireChans said:

    I don’t understand why these athletes don’t take out gigantic insurance policies for stuff like this.

     

    just seems prudent.

    Probably cuz they're gigantic expensive.  I used to work in an industry (Commodity Trading Advisor) where we're potentially liable for substantial amounts of $.  We looked into insurance & it was highly imprudent given the probability of a liability.  How often does something like this happen?  Very seldom.  Also, good luck getting a payout.  You think insurance companies will just hand out a 6 or 7 figure amount w/o some legal fight to try to weasel out of it.

  8. HELLLLO! McFLY!  Have you heard of the salary cap?  If we trade/cut JA at this juncture, we'll literally have difficulty fielding a 53 man roster.  I think he has like a $99m dead cap.  You can't jettison high cost players like Miller, Diggs (prolly Milano) & Knox as although they cost a lot, their dead cap is more.  The roster would need to be comprised almost exclusively of minimum wage players.

    • Thank you (+1) 2
  9. 26 minutes ago, T&amp;C said:

    By "log in" do you mean just using the random person at the bottom instead? I use Chromebooks and can just plunk one down wherever.. house/yard.. and listen to albums while I do whatever. Until this...

    I believe the "full" youtube experience involves having a "user account", so you can "like, subscribe, comment"
     on videos, etc.  I don't have a "user account", so I'm just a "visitor".  When I bring up the main page, at the top right, there's a button to "sign in".  Presumably, if you're "signed in" that's how they getcha w/ the ads.  I use Firefox w/ a couple Add-on ad blockers & thus far, I'm still immune to the ads, though I'm arguably missing out on some things by being able to comment or take note of favorite content providers.  Trying "signing out" & see if the ads persist.

  10. The simple problem w/ cutting him or trading him is his cap #.  As a 1st round pick, he had a big signing bonus, which would accelerate if jettisoned.  According to Sportrac, it'd cost roughly an extra $8m in cap to dump him rather than keep him.  Easier/cheaper/more prudent to just keep him on the roster & inactive every week.

  11.  

    Quote

    Josh Allen, who averaged his longest time to throw in a game this season (3.26 sec), struggled when forced to hold onto the ball (10/24, 130 yards, INT over 2.5 sec).

    I think it's more accurate to say "forced to run around to avoid being sacked" rather than "hold onto the ball".  Big difference.

    • Agree 3
    • Thank you (+1) 2
  12. 5 hours ago, Scott7975 said:

     

    Maybe 20 years ago.  60 yard fgs are the 50/50 of todays NFL.  Bass was 3 of 3 before the Giants game this year. 11 of 15 career before Giants.

     

    This chart is 3 years old.

     

    pn1kmlkzpf9a1.png

    Where'd you get that chart?  Almost 20% from 80 yds?  For that matter, 30% from 70 when the longest FG in the NFL was only 66????

    • Haha (+1) 2
  13. Bummer.  Celeb deaths I'm usually indifferent about, but this one hurts.  I knew he had health issues recently, but he was otherwise touring until the end.  He lived one hell of a life & favorably impacted the lives of many millions.  Thank you Jimmy & RIP.

    • Like (+1) 4
  14. I think it depends on how you define "effective".  If you're referring to total yards by RBs, then yes, to some extent, a QB who runs takes yards away from them.  Also, passing also makes them less effective by this definition (when you're doing something else, a RB isn't accumulating yards).  I'll concede there is a limit to this effect, ie if you NEVER pass, the RBs will likely be less productive than if you pass occasionally as the defense will adjust accordingly.

    If you define effective as production relative to opportunity (largely akin to yds/carry, though I would contend there are some differences, then no, I don't think a running QB lessens the effectiveness of the RBs run game.  In fact, I would think that it would benefit it to some extent cuz it's just another thing the defense has to be wary of.

×
×
  • Create New...