[WC2010] Game 05 - England vs. United States


Who do you think will win?  

160 members have voted

  1. 1. Who do you think will win?

    • England
      94
    • United States
      30
    • Draw
      36


Recommended Posts

Could have been worse, but could have been so much better. There was a decent spell with plenty of opportunities in the second half but they fell at the last hurdle. All in all, fairly disappointing, but it could easily have been 2-1 to USA if Green hadn't knocked that shot into the post.

So once the USA gets the ball with that many people in the box, they have to slowly pass it out of their territory?

I'll do my best to explain the offside rule since I am not as knowledgeable as some members here about football.

You asked why doesn't the US just stay back and wait for the ball to be kicked to them when England pushed that many players for defense. The offside rule dictates that the offensive player(s) cannot be more advanced (closer to the other team's goal) than the second last defensive player (we're not counting the keeper) when performing an attack.

This is why players cannot just sit at the back and wait. They would be more advanced than all the defensive players and as soon as the ball was kicked in their direction they would be offsides.

I know I probably did a horrible job explaining it. It took me a while to get it myself. There are videos on youtube that would do a better job than me.

I'The offside rule dictates that the offensive player(s) cannot be more advanced (closer to the other team's goal) than the second last defensive player (we're not counting the keeper) when performing an attack.

You said the second-last defensive player. Therefore you ARE counting the keeper.

Just listening to 5Live, and they nailed it. Everyone is on about '66, and how our first match back then was a draw. People, we need to get over oursevles. That was 44 years ago, everything has changed. Not to mention we ALL hype the crap out of England playing @ the WC.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • I was just being silly based on David Uzondu's comment ☺️
    • The unified inbox, when it arrives, will be a powerful argument for those who have > 1.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!