Sean McDermott announced Monday afternoon … well, nothing regarding the quarterback position.

Despite a woeful performance by Nathan Peterman Sunday in the Bills' 47-3 loss to Baltimore, McDermott said at his day-after press conference that no decision on the starter has been made for Sunday’s home opener against the Los Angeles Chargers.

“Still going to evaluate where we are, dotting the I’s, crossing the T’s,” he said. “When you look at the tape, I’ve been through it a couple times already, we all have to do our job better. You can go around the team, in all three phases we didn’t play well enough to win the football game.”

The Bills suffered the second-worst loss in the 59-year history of the franchise, and as McDermott admitted, Peterman was far from the only problem, but he was a big piece of the disaster.

More:Khalil Mack is already looking like a $141 million steal for Bears

More:32 things we learned from Week 1 of the 2018 NFL season

More:NFL Week 1 winners, losers: Cowboys offense looks stuck

Peterman struggled from the outset, completing 5 of 18 passes for 24 yards and two interceptions. He did not lead the Bills to a first down in the first half. He was relieved by Josh Allen early in the third quarter after two more possessions led to nothing, with his last pass of the day being intercepted to set up a Baltimore touchdown that gave the Ravens a 40-0 lead.

Allen, the seventh overall pick in April’s NFL draft, completed 6 of 15 passes for 74 yards and he directed the Bills’ only scoring drive of the day, a 12-play, 46-yard series late in the third quarter.

Meanwhile, as Bills fans were watching Peterman put forth a historically inept performance in posting a 0.0 passer rating, they were surely following along on Red Zone channel or the Sunday Ticket as former Bills’ quarterback Ryan Fitzpatrick was putting together an epic performance down in New Orleans.

By now you’ve heard the story about how Fitzpatrick’s 11-year-old son wasn’t going to play his father on his fantasy team in Week 1, but his 9-year-old son talked his big brother into it.

“I guess it was a good decision,” Fitzpatrick told Peter King of NBC Sports. Considering Fitzpatrick threw for a career-high 417 yards and touchdowns and rushed for another in Tampa Bay’s 48-40 upset over the Saints, yes, it sure was.

Naturally, as Fitz was lighting up the Bayou, Twitter was aflame with comments about how the Bills should never have never let him go, and some wondered how the Bills would have fared in Baltimore had Fitzpatrick been the quarterback.

However, before we start pining for the days of the bearded one, let’s pump the brakes a bit here. Fitz was one of my all-time favorite Bills, and while he would certainly be an upgrade over Peterman and Allen at this point, are we seriously going to forget that Fitz is the very definition of a journeyman who has bounced around to seven different teams across 14 seasons?

Come on, people. He had a great game Sunday, but is he really capable of doing that week after week? For that matter, is he even going to be the Bucs starter once Jameis Winston returns from his three-game suspension? I don’t think so.

Fitz is the ideal NFL backup at this point in his career because he can do something like what he did on Sunday, occasionally. But as a regular starter, there’s more than enough evidence to show that Fitz doesn’t stand up for the long haul of 16 games, as his 49-70-1 record as a starter would indicate.

The highest passer rating he ever produced in his four years with the Bills was 83.3. He threw 64 interceptions as a Bill, including a league-high 23 in 2011, the year the team gave him a whopping contract extension that blew up in its face the following season which ultimately led Buddy Nix and Doug Whaley to release him and draft EJ Manuel in the first round.

Had Fitz been above average, perhaps the Bills never let him go and make that mindless reach for Manuel, a decision that also blew up in their face. Folks, it was six years ago, let’s move on.

The other quarterback Bills fans were paying attention to Sunday was the previous Buffalo starter, Tyrod Taylor, who now operates out of Cleveland. The Browns managed a 21-21 tie at home against the Steelers, which means they can’t finish 0-16 again.

Taylor’s role in that? Yes, he threw a game-tying touchdown pass to Josh Gordon with 1:58 left, and he also had a 20-yard TD run, but the rest of his day was Tyrod being Tyrod. The Browns’ defense forced six turnovers, and still Cleveland couldn’t win. Taylor completed 15 of 40 passes for 197 yards with the one TD and one pick, a passer rating of 51.8.

We saw that act for three years in Buffalo, so no, as I watched Peterman making a mockery of playing the quarterback position, I wasn’t wishing for a Tyrod return.

Like Fitz, of course Taylor would have played better than Peterman against the Ravens. Then again, Fitz’s fantasy football-playing son might have played better than Peterman.

When you haven’t had a true franchise quarterback for more than 20 years, it’s pretty tough to practice patience, but Bills fans have to do it because the team believes it has its franchise quarterback in Allen, and it’s only a matter of time before McDermott breaks the seal and gives the kid his first regular-season start.

But will that happen Sunday when the Bills host the Chargers at New Era Field? As of Monday, probably not, though the week is still early.

MAIORANA@Gannett.com