by Andrew Lang
by Andrew Lang
When the Nationals needed a win from Tanner Roark, he delivered with a 1-run performance in 7.0 innings as Ryan Madson and Kelvin Herrera closed out this game with no drama. The Nationals RBIs came from Matt Wieters with a solo home run, and Bryce Harper hit an opposite RBI double. Continue reading
When the Nationals lost the first game of the doubleheader yesterday, it pushed the Nationals back to a 6.0 game deficit in the NL East behind the Phillies. Fortunately, the offense that could not score runs Saturday afternoon — exploded for a half-dozen runs in the nightcap of the doubleheader. Anthony Rendon who was hit-less in the afternoon knocked in 2-runs on 3-hits in the evening. It was like two different teams from afternoon to evening. Juan Soto was consistent in both ends of the doubleheader with 2-hits in each game which tied a teenager record, but the difference is that he scored 3-runs in the nightcap. Continue reading
Photo by Sol Tucker for TalkNats
After dropping the matinée to the Cincinnati Reds in a game in which they could push across only one score, the Washington Nationals badly needed a win in the evening game, and that’s what they got.
An offensive unit that was almost completely inept in the first game of the day-night doubleheader roared back to life this evening, plating at least one run in each of the first five innings. The Nats won this one 6-2, with starter Jeremy Hellickson netting his fifth win of the year and Juan Soto, Anthony Rendon, and Matt Adams furnishing some sock in the lineup.
Photo By Andrew Lang for TalkNats
The second game of doubleheaders have added pressure for the team that lost the first game of the doubleheader, and it is the Nationals in just that spot as the team that lost the front end of the doubleheader. The added pressure comes from losing ground in the pennant race. Another game off of the calendar and it feels like the Nats keep digging a hole for themselves. Continue reading
Past performance usually is a good indicator of what you will see in the future, and sure enough it did again today with Gio Gonzalez. In this game, it looked bad from the start as Gonzalez was missing his spots and loaded the bases in the first inning. While the inning ended with giving up just one run, the damage seemed to have been done. The stadium went quiet as did the Nationals bats. They barely put together anything and continued this history of losing their 7th game in Gio’s last 8 starts. The run support behind Gio continued in those starts to be less than a run per game. Something is not clicking with this team when Gio starts. This is the same Nats offense that just scored an average of 13.33 runs per game in the previous 3-games. Continue reading
With yesterday’s rain-out, today is a day/night doubleheader with separate admission. Manager Dave Martinez will stay with the same line-up as yesterday for Game #1. The Nationals had a choice to use a spot starter as their 26th man to reseed the rotation to strategically match-up in the Braves series which begins with a doubleheader on Tuesday. Continue reading
We’ve all seen that look on Gio Gonzalez‘s face and so have his teammates. Frustration has been too commonplace with Gonzalez lately. Trends since mid-June for Gio have translated to little run support while he is on the mound. The Nats have been shutout 3-times in Gio’s last seven games plus two more games they have only scored 1-run in support. Saturday in Miami was one of those games, Gio exited the game with a 1-0 deficit, and the Nationals tied the game in the 9th inning only to lose 2-1. Gonzalez has received 0.86 runs while he is in the game over that 7-game span. The team’s record in Gio’s last 8-games is 1-7. Continue reading
With a 6-run second inning, the Nationals cruised to a 10-4 victory behind the arm and bat of Max Scherzer and powered by Trea Turner and friends. Scherzer earned his MLB best 15th win.
"Opening Day should be a National holiday"
We recently upgraded our comment system to improve reliability, performance, and long-term control, and we’re currently running both systems during the transition. This shift moves us away from an external service to a system we run and control directly—meaning we own the content and can continue improving it over time. We’ve also reduced the comment refresh delay from about 30 seconds to 10 seconds, making it much closer to real-time.
We understand there have been frustrations and increased feedback, and we’re actively working to improve things. What we ask is simple: use the system and give it a fair shot. If you run into issues, please submit them through the support form so we can track and fix them properly. Repeated complaints without details don’t help us solve problems—we appreciate your patience as we continue refining the experience.
If you’d like a full side-by-side comparison of the platforms and the reasons behind this decision, please refer to the chart below. This change is being made with the long-term benefit of the entire community in mind.