Forum Replies Created
-
AuthorPosts
-
znModeratorSo what can we expect now,
from a team that was struggling on defense,
and that has now lost three starters
on the OLine ? And maybe Quick as well.
Not to mention Hayes on defense.Nine more games.
O dear.
Two more wins?
w
vThis is 2011 redux.
BTW it Hayes is hurt, so is Westbrooks. That means they have 3 injured left DEs.
They have lost or currently have injured:
1 WR
2 QBs
3 OL
3 left DEs
2 free safeties
3 CBs, including one on IRBecause of shifts and replacements, that has an effect on:
CB1, CB2, FS, left DE, LOT, LOG, OC, ROG, WR, & QB.
10 positions.
I don’t know how many of the injured come back when so who knows about how long this will last.
3-4 positions with replacements? That’s just the NFL. Beyond that? It’s not the same team.
October 27, 2014 at 1:22 am in reply to: the media post-mortem on the KC game … Gordon, Wagoner, Thomas, etc. #10550znModeratorRams notes: J. Long could be done for year
By Jim Thomas
KANSAS CITY • Remember the Cleveland preseason game, when the Rams lost five starters in the first half?
Well, Sunday’s 34-7 shellacking to Kansas City was that nightmare revisited.
Early in the second quarter — just two plays apart — the Rams lost wide receiver Brian Quick (arm) and right guard Rodger Saffold (shoulder) to injuries. Quick’s left arm was in a sling after the game; he said he didn’t know the extent of the injury.
Late in the third quarter, left tackle Jake Long left with a knee injury. Two sources confirmed to the Post-Dispatch after the game that it looks like Long is done for the year with a torn ACL (anterior cruciate ligament). That’s the same injury that sidelined Long in the Tampa Bay game late last season.
Before the second half was over, center Scott Wells (elbow), free safety Rodney McLeod (knee) and backup free safety Cody Davis (concussion symptoms) had been sidelined with injuries. McLeod apparently has an MCL (medial collateral ligament) injury, which is not nearly as serious as an ACL injury.
And although there was no in-game announcement regarding William Hayes, the veteran defensive end left the locker room on crutches with a foot injury.
It all added up to six starters, and a backup, going down with injuries Sunday afternoon.
“I’ll assess our injury situation over the next 24 hours,” coach Jeff Fisher said at his postgame news conference. “We’re gonna have some players that are gonna miss some time. I don’t know how much and whom, but they’re gonna miss some time.”
The Rams finished the game with only two of their original five offensive line starters on the field — Greg Robinson and Joe Barksdale. And Barksdale, the team’s right tackle, was the only one playing his original position.
After Long’s injury, Robinson moved from left guard to left tackle. Mike Person, who had played only four snaps previously all season on the offensive line, came off the bench to play left guard. Barrett Jones, who played in his first game of the season last week against Seattle following back surgery, replaced Wells at center. It was Jones’ first action in the NFL on offense after being drafted in the fourth round out of Alabama in 2013.
Davin Joseph, who started the first four games of this season at right guard, replaced Saffold there.
“It’s always a setback, especially when you start losing key players,” Hayes said. “Hopefully we can get ‘em healthy this week and they’ll be ready to go for San Fran. But it just (stinks). Guys work hard and then you see ‘em go down. It’s always tough.”
SITTING IT OUT
Rams inactives Sunday were CB Janoris Jenkins (knee), CB Trumaine Johnson (knee), C Tim Barnes (shoulder), DE Ethan Westbrooks (hand), TE Alex Bayer, S Maurice Alexander and QB Case Keenum.
On Saturday, the Rams placed second-year CB Brandon McGee on the season-ending injured reserve list because of a foot injury that he aggravated in practice last week. He was replaced on the active roster by CB Jemea Thomas, who was promoted from the practice squad.
Thomas’ Rams debut included an unnecessary roughness penalty after the last Kansas City kickoff of the day.
RAM-BLINGS
• The Rams had only 200 yards of offense Sunday, easily their lowest total of the year. Between their game-opening touchdown on their first possession to some garbage-time yards on their final two possessions late in the fourth quarter, they managed only 65 yards of offense over a span equivalent to three quarters.
• After giving up zero sacks last week against Seattle, the Rams allowed seven sacks Sunday against the Chiefs.
• LB Marshall McFadden, promoted to the active roster from the practice squad following the release of WR Austin Pettis, made two special teams tackles in his Rams debut, according to unofficial press box stats.
October 27, 2014 at 12:11 am in reply to: the media post-mortem on the KC game … Gordon, Wagoner, Thomas, etc. #10545znModeratorBernie: Sing it again … same old Rams
Bernie Miklasz
KANSAS CITY • Chiefs 34, Rams 7 … and the beat goes on.
And by now, I don’t know what to say. I could throw a tantrum and demand firings to appease the understandably angry mob of Rams fans. But telling the owner to sack the GM and head coach and a coordinator or two is nothing more than a cheap grandstand play. And it has no chance of happening. None.
After using a satchel of magic tricks to upset the Seattle Seahawks last Sunday, the Rams had a chance to come to Arrowhead Stadium and get a little something going. Just a two-game winning streak to signify that things were on the upswing. You know, a little serving of hope for the people.
The day began promisingly enough for the visitors, with an opening drive of six plays, 65 yards and a touchdown for a 7-0 lead.
That’s it.
There’s your highlight.
The Chiefs outscored the Rams 34-0 the rest of the way.
That little slice of hope was shredded by the Chiefs.
“It’s disappointing,” Rams coach Jeff Fisher said. “We had a great week, a short-lived bit of momentum, and weren’t able to put two in a row together.”
And now the Rams and their overpopulated list of wounded players go on the road for games at San Francisco and Arizona.
Good luck with that.
The bullet points on a 27-point loss:
• More Rams players limped off the field with broken bodies — six guys were injured in this one including three starting offensive lineman.
• The Rams allowed a 99-yard kickoff return to start the second half, and the Chiefs were suddenly up 17-7 and well on their way to a systematic rout.
• Kicker Greg Zuerlein shanked that kickoff to set up the runback. In the second quarter he missed a 38-yard field goal that would have given the Rams a 10-7 edge.
• QB Austin Davis threw a terrible interception to kill the early momentum. And on at least a couple of occasions Davis failed to throw the ball away to avoid being sacked. The Chiefs sacked him seven times. Davis is a young quarterback who hasn’t always played like a young QB. He played young Sunday.
• After grabbing that early 7-0 lead, here’s what the Rams did on their next eight possessions: 33 plays, 51 yards, five first downs, six punts, the interception, and the missed field goal.
• The Rams’ young, injury-torn secondary was shredded by KC quarterback Alex Smith for 24 completions in 28 attempts and a 100.3 passer rating. Defensive coordinator Gregg Williams’ pass defense remains vulnerable.
• The Rams defense stopped Chiefs RB Jamaal Charles for as long as they could; he had only 14 yards on eight first-half carries. But with the Rams offense unable to stay on the field, the overexposed Rams defense eventually gave way. In the second half Charles galloped for 96 combined rushing-receiving yards and had two touchdowns including a 36-yard breakaway.
• The Rams actually did a solid job of running the ball — but sort of moved away from the run while this game was within plausible (if not realistic) reach.
• I’m not sure why offensive coordinator Brian Schottenheimer thinks it’s so clever to use the mini-receiver Tavon Austin on runs between the tackles. Defensive players must chortle when they see Austin lined up in the backfield.
• And of course there were eight Rams penalties for 68 yards.
• Faulty preparation was apparently an issue. A quote from tight end Lance Kendricks on the Rams’ sputtering offense: “We struggled all across the board. It was loud out there. We couldn’t get the signals out. We couldn’t get the personnel out. So the game wasn’t really flowing for us as it may have for them. But that’s on us. We’re professionals. We play ball, too. We have to be ready for that type of stuff. I just don’t think we were ready for everything they threw at us.”
I’m sorry to disappoint you, but I just can’t lather myself up with rage after this one. My supply of rage is running low. After a while, these smackdowns of the Rams just leave me shrugging. I don’t know if I’m just numb to it by now. Or if I’ve just accepted the reality. The Rams lose. And lose. And lose. So why would we expect a different outcome except for the odd Sunday here and there?
Fisher and the staff and the players are working hard. (I know; no one cares about that. That’s what they’re supposed to do. True.) The Rams aren’t good enough to win consistently when healthy. They sure as heck have no chance to win when they aren’t healthy.
The Rams are 2-5 on the season.
They’re 45-105-1 since the start of the 2005 campaign.
Pardon the mixing of sports, but that’s 151 games … nearly enough to add up to a full major-league baseball season.
So basically, the Rams are the 1962 New York Mets (40-120), or maybe the 2003 Detroit Tigers (43-119.)
Sometimes, a team is so bad it becomes comical. I’m not suggesting laughter here … but please don’t have a heart attack over this team. It isn’t worth it.
I suppose there’s always hope.
I know this because I’m looking across the parking lot at Kauffman Stadium, and World Series Game 6 will be played there Tuesday night, the San Francisco Giants at the Kansas Royals.
As you know, the Royals failed to make the MLB playoffs for 29 consecutive seasons, 1986 through 2013. And now the Royals have a chance to win a World Series a few hundred yards from the patch of ground where the Rams curled up to absorb another hideous loss.
Yeah, so there’s always hope of a Rams turnaround.
In theory, anyway.
Just don’t ask me to predict if it’ll happen during your lifetime.
October 27, 2014 at 12:08 am in reply to: the media post-mortem on the KC game … Gordon, Wagoner, Thomas, etc. #10544znModerator
Rams’ missed chances become Chiefs’ blowoutBy Nick Wagoner
http://espn.go.com/blog/st-louis-rams/post/_/id/13019/rams-missed-chances-become-chiefs-blowout
KANSAS CITY, Mo. — The St. Louis Rams have made a habit of starting as the hare and ending as the tortoise in 2014, but for all of those slow finishes, many of them can be directly linked to a series of missed opportunities.
After the Rams’ 34-7 blowout loss to the Kansas City Chiefs on Sunday afternoon, the 2-5 Rams appear headed down the path to another disastrous season.
And there will be no sequence of plays that better sums up this year’s team so far than what happened midway through the second quarter of Sunday’s loss.
In a 7-7 game with the ball at Kansas City’s 8-yard line after a fumble recovery by defensive end William Hayes, the Rams somehow managed to come away with no points. Not a touchdown, not a field goal, nothing. Instead of at least a 3-point Rams’ lead, Kansas City got the ball back and promptly drove for a field goal of its own.
It was a six-point swing that turned more painful as the Chiefs rattled off the next 27 points of the game. They scored all 34 of their points after the Rams’ opening touchdown.
“We clearly got outplayed the second half of this game in all three phases,” Rams coach Jeff Fisher said. “It probably started before half when we had the turnover, got sacked, got no points and then gave up points. So this team is going to have to learn to play consistent through 60 minutes.”
Really, the most consistent thing about this Rams team is the repeated use of that final sentence. Talk of finishing a game, playing a full 60 minutes and other such cliches are staples around the St. Louis locker room and yet nothing seems to change — with rare exceptions like last week’s win against Seattle mixed in.
Sunday’s failure came at all levels, but the steamroller didn’t really fire up until after the missed second quarter chance.
The Rams offense had put together an impressive opening drive for a touchdown, and though it hadn’t scored since, had at least moved the ball. On first down from the Chiefs’ 8, running back Tre Mason ran up the middle for 1 yard. On second down, the Chiefs blanketed a Rams receiver corps as pressure came through the Rams’ struggling offensive line and forced quarterback Austin Davis to scramble for a yard.
Third down is when things really took a turn for the worse as Davis felt pressure, escaped the pocket to the right and instead of throwing the ball away or hanging in the pocket to find receiver Chris Givens in the back of the end zone, took a 14-yard sack.
“That was a big point in the game,” Davis said. “Obviously you get the big turnover. At minimum, you’ve got to come away with three but really you need to score a touchdown. I’ve got to throw it away. We’re even closer and it would have been more of a chip shot for Greg so I have got to do a better job of throwing the football away and managing the situation. You get the field goal and everyone feels a little bit better. Those types of plays are critical in a close game as it was at that point.”
In fairness, Davis had thrown a touchdown earlier in the game on a similar play when he rolled out and found tight end Lance Kendricks in the back of the end zone. Taking a sack isn’t a good play but it still left kicker Greg Zuerlein a 38-yard chip shot. Or so it seemed.
Zuerlein, who has developed a knack for missing kicks at crucial times, said he rushed the kick and didn’t set his plant foot properly.
“Anytime you go out there they expect you to make the field goal, obviously you should, being that close,” Zuerlein said.
Once again, there are a lot of simple enough things the Rams should be able to do to help them win games. They’re the things that winning teams do and losing teams don’t. And for as long as the Rams don’t do them, they’ll continue to get the same result.
October 27, 2014 at 12:06 am in reply to: the media post-mortem on the KC game … Gordon, Wagoner, Thomas, etc. #10543znModeratorRams crushed in Kansas City 34-7
By Jim Thomas
http://www.stltoday.com/sports/foot…cle_c3d8917b-dbf9-50f6-8297-121f30f833df.html
KANSAS CITY • After a promising start, the Kansas City nightmare continued for the Rams. A 34-7 loss to the Chiefs made the Rams 0-3 against their NFL cousins on the western edge of the state since the move to St. Louis in 1995.
The composite score in those three contests: Kansas City 137, Rams 51.
Since that buzz-kill of a season-opening 34-6 loss to Minnesota, the Rams had played everyone tough over the next five games. But not this Sunday.
While the Chiefs were piling up points in the second half, the Rams were piling up penalties, missed tackles, and injuries. It was an embarrassing afternoon to say the least.
Injuries to center Scott Wells (elbow), left tackle Jake Long (knee), right guard Rodger Saffold (shoulder), wide receiver Brian Quick (arm), cornerback Rodney McLeod (knee), and safety Cody Davis (concussion symptoms) added injury to insult.
There couldn’t have been a better start for the Rams in the Sea of Red. For starters there was a 41-yard kickoff return by Benny Cunningham, who entered the day as the NFL’s leader in kickoff return average.
On third-and-1 from the St. Louis 44, Austin Davis found Kenny Britt open deep down the left sideline for a 43-yard gain to the Kansas City 1. Three plays later, a patient Davis found tight end Lance Kendricks open in the middle of the end zone for a 1-yard touchdown.
It marked the third game in a row that Kendricks has hauled in a TD catch, with two of the grabs coming in the red zone.
End of highlight reel. Things went downhill from there on out for the Rams, who dropped to 2-5 on the season and face road games at NFC West rivals San Francisco and Arizona in the next two Sundays.
On the Rams’ second possession, Davis forced a deep ball into double coverage that was intended for Britt. Fourth-year defensive back Ron Parker hauled in the overthrown pass for a Kansas City interception.
Starting late in the first quarter, the Chiefs (4-3) took advantage of good field position to even the score on a 53-yard touchdown drive. It was a tough drive for Rams rookie cornerback E.J. Gaines, the Missouri product playing in his hometown.
First off, he tried to pick up an Alex Smith fumble forced by Robert Quinn instead of falling on the ball. It rolled out of bounds and the Chiefs retained possession. On third-and-7, an illegal contact penalty on Gaines gave KC a first down.
Then, on third-and-6 from the St. Louis 18, Gaines missed a tackle near the line of scrimmage on a quick sideline toss to tight end Travis Kelce. Kelce wasn’t brought down until he reached the 1-yard line. On the next play, Jamaal Charles was in the end zone running off left guard to tie the score 7-7 early in the second quarter.
Later in the quarter, the Rams missed a golden opportunity to take the lead when a botched handoff to Charles from Smith resulted in a fumble deep in Kansas City territory. Defensive end William Hayes recovered the loose ball and returned it six yards to the Kansas City 8. But two running plays produced no gain, and then Davis foolishly held onto the ball instead of throwing it away and was sacked for a 14-yard loss.
Wait — it gets worse. Out trotted Greg Zuerlein, who promptly missed a 38-yard field goal, wide right.
The Chiefs took over at their 28 and even with back-to-back sacks by Quinn in the final 80 seconds of the half, they were able to tack on a Cairo Santos 53-yard field goal with 1 second left.
It took Kansas City only 12 seconds to tack onto the lead to start the second half. For some reason, Zuerlein sent a line-drive kick that bounced to Knile Davis at the 1. Davis returned the ball 99 yards for a TD, with only Zuerlein having any kind of a shot at a tackle. Zuerlein whiffed.
That play seemed to break the Rams’ back. They were never the same afterward.
It became 20-7 Kansas City on the Chiefs’ next possession on a 28-yard field goal by Santos. The drive started at the KC 6, but the Rams helped the Chiefs downfield with a late hit by linebacker Alec Ogletree and a spearing penalty by Rodney McLeod that led to 30 yards in penalties.
Also, a missed tackle near the first-marker by Jo-Lonn Dunbar helped Charles turn a short reception into a 30-yard gain to the St. Louis 14 on third-and-6.
Charles hammered the nail into the coffin early in the fourth quarter with a 36-yard TD run to give the Chiefs a 27-7 lead.
October 27, 2014 at 12:05 am in reply to: the media post-mortem on the KC game … Gordon, Wagoner, Thomas, etc. #10542znModeratorRapid Reaction: St. Louis Rams
By Nick Wagoner
http://espn.go.com/blog/st-louis-rams/post/_/id/12996/rapid-reaction-st-louis-rams-19
KANSAS CITY, Mo. — A few thoughts on the St. Louis Rams’ 34-7 loss to the Kansas City Chiefs at Arrowhead Stadium:
What it means: The Rams’ victory over Seattle last week offered a short respite to forget about all that ails the Rams. But it only took a week for many of those problems to come bubbling to the surface again. The Rams had plenty of chances to jump out to an early lead and make Kansas City work for this one, but instead reverted to their usual M.O. of self-destruction. Never was that more evident than a second-quarter sequence in which the Rams recovered a fumble at Kansas City’s 8 and came away with zero points. The Chiefs scored 34 unanswered points and that was that. At 2-5 with road trips to San Francisco and Arizona the next two weeks, things such as silly penalties, missed tackles and shoddy pass protection remain at the forefront for this team. Until those things change, the results will remain the same.
Stock watch: Down — The offense, all of it. After an impressive opening drive, the Rams were wholly ineffective with the ball, with plenty of blame to be spread. Start with ineffective play calling that offered little in the way of creativity or adjustments, then go to an offensive line that was leaking from nearly every position to a quarterback who forced a bad interception in the first quarter to receivers failing to create separation. You name it, the Rams did (or didn’t) do all of it. All told, the Rams mustered 200 yards of offense, including just 20 in an atrocious third quarter.
Injuries pile up: Speaking of the offensive line, a group that has mostly held up on the injury front so far finally had the issues that seemed imminent from the start of the season. Guard Rodger Saffold, center Scott Wells and left tackle Jake Long have been injury-prone in the past few years and it seemed to be a matter of time before it happened again. It happened all at once against Kansas City as Saffold (shoulder), Wells (elbow) and Long (knee) left the game and did not return. Receiver Brian Quick left with an arm injury and also did not come back. The Rams also took major hits at safety, where Rodney McLeod (knee) and Cody Davis (concussion) departed and did not return.
Game ball: Defensive end Robert Quinn. In an ongoing theme this season, there wasn’t much to choose from here, but Quinn had his best day of the season, posting back-to-back sacks in the second quarter and forcing an Alex Smith fumble from behind in the opening quarter. After going without a sack in the season’s first five games, Quinn has three in the past two weeks and seems to be coming to life.
What’s next: The Rams head to San Francisco to take on the 49ers for the second time in four weeks. It will be the second game in a three-game road trip.
znModeratorHe’s 49 for 59 with a 60 yarder that’s 83%
Adam Vinatiri is 83%
Check out other kickers %
83% is pretty good plus Greg the Leg has the capability kick 60 yarders.
Today’s loss was not because of that miss.
Reality is, …..in the spirit of Denny Green’s famous meltdown. Austin Davis is who we thought he was…
This year so far though I think he is around 73%.
znModeratori missed the last quarter. how did barrett jones look filling in at center?
greg robinson at left tackle?
The whole offense was a train wreck at that point so it was hard to tell. For me it was anyway.
October 26, 2014 at 10:17 pm in reply to: Who is more responsible for the wasted draft picks? #10537znModeratorLets face it, the Snisher record in the draft is not looking good. Should the Rams be looking for a good talent evaluator for the draft. Obviously Snead is not very good.
I would say of any position they draft Offensive line is most important. Then Linebackers.
Grits
I think their draft record looks good. I have done this experiment where I go back and look at older drafts by good drafting teams. You want to go back before 2011, so you know how picks turned out. I counted a “hit” as a starter or important contributing role player on offense or defense.
What I found was that on avg. 4 hits a year is GOOD to VERY GOOD drafting.
(Anything beyond 4-5 a yr. on avg. = exceptional).2.5-3 a year = avg. drafting.
2 a year = below avg.
Less than 2 = bad.
According to that model, although it’s way too soon to judge the Rams drafts, they certainly look like they are averaging 4 a year at least.
The Rams draft well.
I also found out that all good drafting teams have a 1st or 2nd round bust in there somewhere.
To me, what we saw today was mostly due to multiple injuries.
znModeratorYou know of course that Rams OLs have been eaten up with extensive injuries before.
But let’s assume that Jones and Robinson can play. Maybe full of young mistakes, but can still play.
You know–never in the multi-year history of Rams OL injuries have they had a Jones and a Robinson on the bench before.
This is different.
HOW different? Jeesh, I dunno.
My old formula was this–any OL has injury replacements, and so on. But if you have to replace as many as 3 guys including the OC and LOT, then teams just can’t play. The offense suffers.(I’ve been repeating that formula practically word for word for years now.)
But it may not be THAT level of bad if the depth at 2 key positions was your future anyway.
Ironically, though, I also remember the old Bulger debates. I don’t know if anyone here got into them, but back then, in 2007 and 2008, some of us kept saying that if the OL suffers massive injuries, the qb can’t play. On the old huddle, there were people who denied that. They put it all on Bulger. Today, some of the same people out on the net are claiming that the issue today was not Davis, it was the OL injuries. A complete about face.
And I agree, Davis suffered cause of the OL injuries. But then in 2007, so did Bulger. In the first half of 2012, so did Bradford.
I have even seen someone say this is the worst they have seen a Rams OL play. Well…no. It ranks right there with some of the worst OL games of 2007, 2008, and 2009 though.
znModeratorI do not see improvement. You can try and blame it on injuries
I won’t blame it on injuries if you can name a team that won with injuries like this. So far that’s the #1 and #2 qb and 6 other regular starters. I will settle for 1 qb and 6 other starters.
If you can’t name a team that won with injuries like that, then, strongly consider the possibility that dismissing EXTENSIVE injuries as an explanation of a game like today is short-sighted and unrealistic.
znModeratorZn my old friend I said minor annoyance,not anything to make a big deal I just thought I should tell you know about it. Thank’s for the apology but really no apology is necessary
You do get that I ended up stupidly deleting your “Barnes” post. That’s the 2nd mistake I was trying to explain. If it were just a moved thread that needed to be un-moved, I would think, okay, zn, take your time and be more selective combining threads next time. But I glitched every step of the process and ended up with an improperly deleted post.
So I don’t know if I am apologizing so much as just confessing to being “guilty on account of temporary dumbassery.”
znModeratorNot sure how it all works. I know they can’t cut him right now–but next year when he’s healthy again. How does it work? Do they save his cap money by releasing him or do they take a big hit? Honestly, I don’t know what the situation is regarding all of that. Just curious if anyone knows.
Someone will come along who knows this better than I do. But, my limited understanding is, once he is under contract, any football related injury means he’s part of the team. I don’t know how it works to cut him while re-habbing…I think after the season, they have to reach an injury settlement.
znModeratorSo I guess Robinson takes over the LT duties now.
As for Long? I don’t know the cap issues with cutting him at this point. We’ll have to see.
I don;t know if Robinson moves to LOT, but if so, damm lucky thing he practiced there.
You can’t cut an injured player. Not like you’re thinking.
znModeratorcgsuddeath wrote:
Looks like long is out for the season again.So ends the Jake Long experimentWhat’s wrong with Long? What happened?
Got it.
—
Per league source, Rams fear LT Jake Long suffered torn ACL today.
— ProFootballTalk (@ProFootballTalk) October 26, 2014—
Rams, Jake Long believe he has re-torn ACL
by Mike Florio
Two key members of the Rams’ offense tore ACLs last year. Now, both have re-torn the same ligaments this year.
During the preseason, quarterback Sam Bradford suffered the same season-ending injury as he suffered a year ago. On Sunday, the Rams and left tackle Jake Long believe he tore the same ACL that was torn last season.
An MRI is expected to confirm the ACL tear on Sunday night. It would be a surprise at this point if the MRI shows anything but the ACL being torn.
znModeratorThey’re the Washington Generals of the NFL.
Is that a silver lining?
kidding.
This is 2011 all over again.
.
znModeratorLooks like long is out for the season again.So ends the Jake Long experiment
What’s wrong with Long? What happened?
znModeratorWell actually ER it’s worse than you said.
I got a brain glitch and thought you had started the OL injuries thread. I thought you were complaining that your follow-up post was then orphaned. I fixed it, I thought, by combining your 2 posts and then deleting the orphan.
And I double-checked. You didn’t start the OL thread. CG did. So … I didn’t combine YOUR 2 posts. What can I say, I F’ed up, and am embarassed. You’re important regular poster and I hope I didn’t offend you.
So that’s a double screw-up. One, yeah, the OL injuries thread did not belong in the post-game thread. That was a little insensitive on my part.
Then when I thought I fixed the orphan thing, I made it worse.
So, my sincere apologies.
It was just a brain glitch day. I can only apologize again. It wasn’t just bad judgement, it was ordinary dumbassery.
Unless people think otherwise, I think that combining threads on the same topic–particularly when we have multiple news articles on the same thing–is a good idea.
Sometimes combining conversation threads is a good idea.
But from now on, I will be much slower to do it and more selective. Time for a little more anarchy (that’s said with fun sincerity, it’s not ironic.)
Fair enough?
If you don’t think it’s not fair enough–speak up. This thread is about honesty.
znModeratorzn wrote:
Have at it.Who has a silver lining?
<ZN I am not liking having my posts micro managed. The comment “and Barnes” makes even less sense than usual when you move it to from the OL thread and lump it in with the post game venting stuff.The silver lining is this minor annoyance got my mind off the 2 hour abomination I just watched.
Well, we combine threads that are on the same topic. If it’s time to re-think that, then, that;s fair. In this case, your complaint about “and Barnes”–I fixed that with an edit. I didn’t notice that before.
There’s 2 ways this works. One is, all threads just stay. If someone starts a thread, it just has its own life and lifespan. But then threads go off the page faster, and you see 1-2 at best reply threads on page 2 no one looks for, with new 1-2 response threads on the same topic on page 1. If you combine threads that are posted close together on the same topic–like reactions to the KC game on game day, for example–more participate and there’s more action and conversation, and things don’t move off the 1st page as fast. The danger there, of course, is that someone may think they’re just being pushed around, plus it gets down to the judgement of the combiner.
OR if you would prefer I move your post back out as a separate thread about OL injuries, just ask. That’s easy.
So is this a one-time thing? Or is it a genuinely a board issue? I can set us up to discuss it as a board if that’s how you feel.
Let me know. That’s sincere.
October 26, 2014 at 12:54 pm in reply to: what challenges do the Rams face with KC? Can they win? #10473znModeratorLots of questions for this game. Same as the other games but in a new framework. Are they progressing or was Seattle one of those “every 21st game the Rams beat someone” games.
* can they play with a rookie secondary
* have they re-wired Ogletree
* this game ought to let the DL do some damage
* can they contain the edge or will Charles set a world’s record for yards per carry
* the Rams OL + Mason and the other backs could be a strong suit.
* who is Austin Davis
* can they neutralize the KC pass rushznModeratorfrom off the net
—
thehammer
meet Marcus roberson
Lean, athletic, finesse cornerback who is best deployed in off-man or zone coverage, and has potential to develop into a No. 2 or No. 3 corner if he regains his sophomore form. However, he lacks desirable instincts and tackling ability, and did not elevate his game in 2013 when injuries, suspension and inconsistency marred his junior season. …pretty good summary by nfl.com
mine was shorter..covers like Tarzan tackles like Jane also 4 missed tackles in 135 snaps in preseason..
what I saw at camp/film really dislikes contact..think KC will run to Quinn/Roberson side? BUT very solid cover cb…looked like a solid 2 or 3 cb in coverage both at camp and in college….6’0 with long arms did well on deep balls even without great speed. Rams will be slidely help to his side
znModeratorJenkins and Johnson out. McGee on IR.
2 rookie corners.
A rookie nickel.
A rookie back-up (Thomas).
This is like a much more modest, much less destructive repeat of 2011.
Like, having gone through a war, now, it’s a bar brawl. Same thing…smaller scale.
znModeratorAnnouncers said “we checked and Stacy is healthy.” Interesting.
I agree with those who say it does not matter what they’re telling people about Stacy, if you watched him the last coupla games, he’s running hurt. Not the same physically. They dress him, I think, cause they want a vet on the sideline in case he has to go in and that a banged up Stacy is better than no depth.
I think if all 3 backs were healthy we would see a dose of all 3.
The Fisher team medical reports are a tangled web of misdirections. IMO.
znModeratorfrom off the net
—
thehammer
2012 (junior): Started all 14 games… ranked second on the team in total tackles (86) and led the team in solo tackles (61)… led the team in interceptions (4)…
2013 played and started in all 13 games… led the team in solo tackles (73), total tackles (88) and pass break-ups (8
Was one of the most talented and versatile defensive backs in the ACC… played in 54 career games, tying for the most in Georgia Tech history… played every position in the secondary… was the Yellow Jackets’ top cover corner but moved to safety because of injuries to teammates… was also a solid kick and punt returner… has a love for the game… was one of the hardest hitters on the team and a great open-field tackler… recorded 234 career tackles… had nine interceptions over the last three seasons…
very similar to Joyner as a player…1 inch taller 10 lbs heavier better short times..if Gaines, Joyner and Thomas are on the field together rams would have the best tackling secondary in the nfl
.
znModeratorJamea Thomas from practice squad
Jemea I. Thomas (born April 7, 1990) is an American football cornerback for the St. Louis Rams. He was drafted by the New England Patriots in the sixth round of the 2014 NFL Draft. He played college football at Georgia Tech.
Professional career
2014 NFL Draft
He was drafted by the New England Patriots in the sixth round (206th overall) of the 2014 NFL Draft.
On May 18, 2014 the Patriots signed Thomas to a four-year deal. On August 26, 2014, he was released by the Patriots.
Dallas Cowboys
On August 27, 2014, Thomas was claimed off waivers by the Dallas Cowboys. He was released by the Dallas Cowboys on September 1, 2014
——-
5’9″ 192 LBS
Analysis
Strengths
Has large hands and is strong for his size. Sacrifices his body and supports the run willingly; he likes contact. Takes good angles and understands run-game fits. Quietly confident. Mentally and physically tough. Good short-area zone awareness; reacting to throws in front of him is a strength. Tough and durable, will play hurt. Highly respected. Hardworking and accountable. Experienced four-year starter.
Weaknesses
Lacks ideal height and has short arms. Frame is nearly maxed out. Stiff hips. Gives up some ground and allows separation in man coverage vs. quickness. Easily mismatched by size vs. tight ends. Average range — lacks desirable length and fluidity to patrol the back end. Hands are iffy.
Bottom Line
Strong, tough, durable, downhill box safety whose hip tightness is limiting, but he brings desirable grit, physicality and competitiveness and could latch on as a situational nickel-safety and special-teams player.
znModeratorWhy displace Barksdale??? Seems he’s the only guy who’s really doing his job at the highest level…
Well this is just me speculator-atizing.
Just going through the options. I know a lot of this is obvious.
But, I don’t see them keeping 4 big contract linemen. So if they sign Barksdale, then, they have to let someone else go. One hang-up…apparently, Boudreau linemen get market attention and money. So he could cost.
They could keep Barksdale and then let Long or Wells go or both. IF Jones comes through then Wells is not an issue. If Jones can’t cut it…they either have to keep Wells, or find someone, or both (draft or free agency).
Long is an amazing run-blocker, better than Barksdale. I just don’t want him pass-blocking on the left next year unless he just improves this year and can carry it over. So a Robinson left, Long right combo makes sense. Then again…so does a Robinson left, Barksdale right combo. Then again (again), if Long improves—and he just had a shakey start—another combo that makes sense is Long left, Robinson right.
Saffold is in place.
Looks like the only thing up for grabs is guard. Unless they keep Barksdale and Long both, which could happen too if they like Jones and can part with Wells. Under those circumstances, they keep GR at guard for another year.
I don’t think that’s even all the options.
Short answer:
I dunno.
znModeratorfrom off the net
—
alyoshamucci
So . . . I’m not going to talk about the fumble. Honestly in my heart I feel like we lost the game . . which doesn’t change much, because we’re pretty snakebit at finding ways to lose games. Hopefully we won’t keep finding new ways and trying harder in that department.
We have been a part of a record setting game every single game this season. That’s pretty unreal.
1) CP’s 100 yards by WR
2) Bobby Rainey’s career day
3) Largest regular season no OT COWBOY comeback.
4) Eagles string of on offensive TDs goes to 5, 2 in our game . . thought there may have been another.
5) Kap’s longest ever TD pass for himself.
6) NFL’s first 300 yard passer/100 yard rushing QB.We are 2-4, and not out of it.
The Great
1) Aaron Donald. I was going to say, before I saw PFF’s chart, that he was outplaying most every DT I’ve seen this year. He has legit pro bowl and DROY chances. He is also the most disruptive force Ive seen on our interior D line . . ever.
2) Special Teams play . . . way to go Fassel.
The Good
3) RB for an NFL team. Mason’s burst. He is getting the playbook down. We now have 4 RBs, three of which can run you over, 2 that can run away from you, and all that move slightly differently so you cannot get used to how you tackle them. And Im not even counting Austin being back there.
4) Sacks. Thanks guys. Let’s keep that going yeah?
5) Davis’ passing accuracy? highest ever vs. the Seahawks.
6) Where was Marshawn Lynch? Oh yeah our run D showed up.
7) Playcalling. Shotty finally seems to have enough different “styles” of games to call that he can switch mid-game. Even if he sometimes still makes a mistake or two on calls/personnel.
8) Low penalties. Certainly looks like it matters.
9) Barksdale rated as 2nd best OT. Resign and let them man play. If there’s any spot to have cohesion its the O line.
10 Having two rookie CBs in the game on the ten yard line, and not giving up a TD. not to mention they were a UDFA and 6th rounder. Wow. Way to go Roberson . .living up to your talent rather than what we saw from you at UF in the postseason.
11) FINISHING THE GAME.
The Bad
12) Tackling overall.
13) When Shotty calls ‘stop and turn” routes, Tavon Austin has to not be in the game.
14) Bummed about Stacy’s calf, which is obviously hurting him, but glad we have other backs. Prior game, saw him in pain, don’t care what Fisher said. Wincing while trying to get up is wincing. Not worth arguing about though, as I saw it. if you didn’t see it then you didn’t.
15) Saffold’s never ending injuries.
16) Hayes has lost a step, needs to be replaced. Also, he’s too vet to not hit the upfield shoulder on a free shot at Wilson.
17) How does no one tell Mason “hey, after you get the first down, just go down, we can’t risk a fumble” . .?
The Ugly
18) Ogletree. Not only his worst game, but maybe THE WORST GAME IVE EVER SEEN BY ANY LB EVER. WOW. This is his gimme . . he must have had brain damage or been drugged or something.
znModeratorOr maybe they move Long to the right side.
znModeratorHow can Jeff Fisher game plan against Andy Reid? Brian Billick tells The Fast Lane.
znModeratorzn wrote:
The way I see it? This team dominates at times. If it were a more inherently stable team (and I think circumstances led to the instabilities) it would dominate more of the time. If it were a bad team OR a badly coached team, it would never dominate, whether for stretches or not.This is exactly correct.
And that is precisely a definition of a poorly coached team. I think that, by consensus and across the spectrum of most sports, a team that is “inherently unstable” is understood to reflect poor coaching. Especially in American football, which is pre-eminently a coach’s sport.
So, I view your comment–with which I agree–as an indictment of Fisher and his staff.
One example. You mention ’11 and McDaniels. Well, that was a coaching disaster. McD. utterly failed to adapt to and coach that unit to its potential. And Spags hired him and let him run wild. It was precisely a coaching staff catastrophe.
Well, this year, Fisher hires a wild DC and lets him leaqd the league in blitzes while recording a league record for pass rush futility through 5 games … all with a superb DL. Insofar as this season is like ’11, it is a coaching failure.
ZN, you keep saying you see things differently. But your description of what is happening is pretty much what I see … except that you keep avoiding a harsh judgment of Fisher’s staff. Frankly, I don’t really get what you are trying to argue.
Let’s just hope they turn things around and we can all be happy.
I just see it so differently. I don’t think this is a poorly coached team. I think it’s a team with bad growing pains and confidence issues. I see execution issues, but it’s not like it’s a vet team that does all the wrong things…it’s a struggling to be consistent, younger team, and I put that on players. As I said, what I see on the defense is something I think I have seen before–in early 2011, for example, when the offense was out of sync and just not comfortable with what they were doing. I put that down to them not really having a handle on the McD offense. That’s what I see with the Wms defense.
The fact that Fisher keeps saying “you stay the course” meaning stressing the same things tells me (to my ears anyway) that players are having problems adapting and executing and you react to that by continuing to do what you are doing. One day that will even out.
I can’t imagine a team BOTH changing a coordinator and starting its 3rd qb and being seamless and smooth. Toss in the youngest secondary in the league. That’s a recipe for “a team that struggles out the gate.”
So I just see units struggling to adjust. To me that’s experience.
I don’t get down on coaches unless they’re guys like Linehan who clearly lost the team. Previous Fisher teams have long stretches where they are tops. Same with Wms defenses. So I look at execution above all. I also think everyone would look better if the team were winning, and I think they lost games because of multiple bad errors, and to me those errors go to execution.
I mean clearly you make good points in your as usual articulate way, but I am just into my own way of seeing it right now.
-
AuthorPosts
