Skip to content
View in the app

A better way to browse. Learn more.

Morning Big Blue

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

wbbfan

Members
  • Joined

  • Last visited

Everything posted by wbbfan

  1. Call that room Semi Pro. Time to start printing ticat logos on paper bags and make a fortune.
  2. I think they made a temporary stopgap based on bad options. A few weeks of tre ford may change their minds. Though I don't think we'd really trade Zach. I would, but I don't think Walters has it in him. I think it'd be Brown. Zach was throwing the same depth; TE had 2 shots; it wasn't the QB; that was the game plan. I was impressed by TE's poise in that position as well. He was clearly mentally ready to go in and run the install from the week, which isn't at all easy for a true rookie in the very limited backup reps. He's further along as a fresh rookie than Rourke was as a rookie. He has a hell of a long way to go to get close to Rourke now, but he's on track.
  3. You're right, they are. The thing is, we have maybe a 2-year window with this core, including this year. We can keep both QBs, but a 30/31 year old Brown isn't a rebuilding QB. The Question is do you sit on both and hope to turn things around fast when the old guard is gone in a year or two, or do you move one now and try to win a GC this year or next? For me, if you can become a legit GC contender, I pull the trigger. Extreme QB depth (3 guys) is a tremendous luxury, but not one worth being a bottom-half team for. The thing about Browns familiarity is its double layered. We are doing a lot of Condell stuff, but we also have brought back various Zach favorites from Buck and Lapo. After TC, when you should get run out of every play several times, the week-to-week prep is about the current install. A vet like Brown who is dually familiar with what we do and many of our pieces will do a better job of picking that up than a true rookie. I think the biggest obstacle for Brown will be comfort with the Wrs. This equally applies to TE, and Zach struggled with that as well, honestly. None of the 4 QBs had enough live-fire reps with the first-team WRs. It's a great position to be in, though. Choosing between brown and TE for an injury replacement. Brown is clearly the pick imo, but either way you have a guy who can, at worst, not lose you the game. We didn't consistently have that from Zach the previous 2 years. I agree that Brown should be the default pick. I don't think we actually traded for him for this situation. I think this is the last year for Zach, and Dru was brought in for next year. This is purely gut and speculation on my part, but I think Zach has decided not to play next year and told to club as such.
  4. I don't think they would TBH. They love Brown.
  5. right? he’s played the best we’ve seen in a long ass time. That plus his pedigree is more than enough for a team needing a qb to gamble on. I mean the options are tre ford, dig up masoli whose been toast for a very long time or it only gets worse. We’ve also eaten up a decent chunk of zachs salary already so it’s much easier to trade for. Our roster isn’t built around youth or gradual improvement, if it’s a trade we need to add immediate active roster value.
  6. Round here, anything is possible. Boy, that would be stupid, though. If they really think Brown is behind TE, they should move brown to hamilton for more then we paid.
  7. No doubt, anything can happen in the CFL.
  8. qbs in the cfl, never seem to run out of time. How much he has? who knows.
  9. We got the run game going really late for the most part. The last drive was a huge hunk of our production
  10. Throwing for 5.7 yards per attempt is not a recipe for success. Neither is 5.9. The offense was a real issue in terms of play call and design.
  11. I mean, I would consider that if Hamilton was indeed willing to trade starters/AR. Not draft capital. It would have to be extremely expensive on Hamilton's end. I would do the same for any player on the roster; if we got a lopsided value back, no one is untradeable. If we can fix the 2nd DE, defensive backfield, and WR while getting Canadian depth? Sure. Hamilton isn't likely to do that, but if they are, go for it. Talking something like howsare, Stubbelfield, Stavros, Gittens etc. Not for some pack of 1 player and picks or less. Otherwise, I'm very happy to be sitting on the QBs we have. Having Brown + Elgersma for the post-Zach era is going to be key.
  12. That's true, but we also see statistical reasons to believe that it is an aberration. Going into this week, we have been middle of the pack in yards given up, 2nd most first downs given up, middle of the pack in TDs given up, and fewest FGs given up. That says the place we are saving points is mostly long drives from other teams leading to FGs, but that we still give up more TDs than average. most rushing yards given up, 3rd most YPC, 2nd worst opponent average field position, 2nd worst opp TOP, 2nd worst TD per drive rate; this, like below, shows that other teams are able to get what they want and keep drives going. Fewest pass yards/completions/attempts but closer to the bottom in % against, 2nd highest pass eff against, 3rd most YAC given up, 3rd most 30+ plays given up. That says the bye week, and that other teams are wasting time when not finishing drives. Not that we are preventing them from finishing drives. Opponent TD drives are 2nd worst in the league, with such a low offensive snap count against and all the big plays, with few FGs given up; this all points to teams not being stopped by our D. This isn't bend but don't break; this is breaking so frequently that opposing offences haven't optimized playing against us. But If we don't change things soon, they will.
  13. Kramdi is not the answer at S, that is for sure. A big part of the coverage problem is that, instead of bringing in an IMP dime off the bench and putting him in front of the half over a slot, we are bringing in Kelly and running him and Kramdi both as shallow Safteys. Neither has the ability to pick up a deep man worth a damn, and both are shoddy at best in one-on-one coverage. Thats leaving a wr to run past a lber and be open for close to a first down a lot, and leaving us extremely vulnerable along the hash marks deep down field. Idk if Allen is injured for real or being hidden on the IR. We either need him back, or another imp S in a hurry. Then we need to stop subbing Kelly in on D. Put Kramdi back at Sam, and Griffin at Wil. Or better yet, Kramdi straight to wil. He never should've made it out of camp. I get everyone loves the guy; he's the goat. If you want, keep him on the IR or even the reserve roster as a player-coach or something. Cutting Randolph for him was a massive mistake. Teams are beginning to focus on him too, what we saw last night will only get worse unless change happens soon.
  14. no chance over brown tbh that’s what zach was doing too. I think te took two deeper shots which is more than zach. same idea but worse honestly
  15. the ugliest win in recent history
  16. flag?
  17. full marks to brady and every ol not wearing 66 on that drive on the bright side we are well practiced at playing prevent coverage
  18. eli destroyed the guy on the play side edge
  19. big stan again
  20. de yes. dl, sayles/stove etc at dt since then
  21. te looks deep and decides his 4.7 speed through no gap is the best look. that says a lot
  22. he got the ball off in time, wasted the to
  23. gotta cash in now
  24. front just got punched in the mouth
  25. if he was qb2 today, we’d be winning imo

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.