Wayne Rooney @ The World Cup


  

36 members have voted

  1. 1. Should Wayne Rooney give up his place to a fully fit player, or go to the World Cup?

    • Stay
      15
    • Go
      21


Recommended Posts

Well, it looks like young master Rooney won't be fit to play until the quarter finals at the earliest. Is it a waste of time him going?

In my opinion, Wayne should stay in England and one of the other fully fit players should be taken in his place. It's not that I don't want to see him play, but having only a half fit Rooney could be a disaster. Look at Beckham in Euro 2004.

He should stay at home and concentrate on getting fully fit for the new English season. The last thing he would want was to go to the World Cup and get an even worse injury through not being fit, that could possibly ruin his career and any further World Cup appearances.

Pete

Link to comment
https://www.neowin.net/forum/topic/464510-wayne-rooney-the-world-cup/
Share on other sites

  • 2 weeks later...

yeah i think he should go but i dont think he should push himself. i mean he doesn't have to be fully healed, suck it up a little bit, but dont go right in there when u kno u wont be of any good cuse other wise it hurts the team and whos knows he could hurt himself worse.

go!!! Just act as a sub for the first round of matches :) as he can already play football and sprint etc now, it was on gmtv news this morning. Although the players on the opposite team will probably try and catch his foot cos it will probably be still weak :(

would be better if we had him, the whole team would be more confident, however i think we are concentrating on one player too much, there are other very talented players and they arent in the light :/

Only problem though is, if he plays a game he will become the victim of stamping and bad tackles as he has a well advertised problem and he is a stronger link in the team.

You must remember what the Portugese did to him, they made sure he was knocked off the pitch.

That apart from a stupid ref costing us the game.

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!