Recommended Posts

good god, not another one of these "Good god. Not another one of these Metro whine threads."

Good god. Not another one of these "good god, not another one of these "Good god. Not another one of these Metro whine threads.""

Personally i think Metro should have been like Windows Media Center, if you wish it can start full screen when Windows starts. The end user doesn't need to know Windows is running behind it, that's certainly the experience the family get with the Media Center in the front room.

Same with Metro, if you want it to have it start when the user logs on. If not just give the user the desktop environment, there's nothing wrong with choice is there? Metro doesn't need to interfere with the desktop environment at all.

Power users are happy, and your basic computer user can use Metro and never know there's a desktop behind it.

Windows 8 would be received so much better by just allowing users some basic choices.

Good god. Not another one of these "good god, not another one of these "Good god. Not another one of these Metro whine threads.""

Good god, Not another one of these "Good god. Not another one of these "good god, not another one of these "Good god. Not another one of these Metro whine threads."""

Good god, Not another one of these "Good god. Not another one of these "good god, not another one of these "Good god. Not another one of these Metro whine threads."""

Good god, Not another one of these "Good god, Not another one of these "Good god. Not another one of these "good god, not another one of these "Good god. Not another one of these Metro whine threads.""""

This has probably been said already, but if we're going to be stuck with metro, at least allow the Start screen to be displayed on the left side, kind of like the charms menu, rather then go full screen and cover up the desktop and everything I was working on. That is VERY distracting and the number 1 issue for me.

I think people will quickly get used to the new gestures and gimmicks like moving your mouse in one of the corners, using the charms etc. It's sad some people won't give it a chance. Some of the OPs suggestions ruin the whole Metro idea, this is what I'd love to see;

- Desktop apps appearing in the app switcher at the top left. Now there are essentially two types of apps (Metro and classic) and two ways to switch (taskbar and left switching pane)

- Remove the taskbar, it's obsolete with desktop icons. Certainly DON'T dare to bring back the ominous start button, it's as obsolete as hell. Remove window chrome and let them close using the "drag down" paradigm that Metro apps have.

- Improve the App Preview apps dramatically (really, the CP versions are for kids --')

- Shut down/Restart/Control Panel option in the user flyout menu.

I still can't see why the desktop can't be the default environment on laptops and desktops, and metro on tablets and phones. It makes no sense to force everyone into one paradigm. Honestly I think this will just push more people toward GNU/Linux, which gives users actual choices instead of forcing it down their throats.

that Dot Matrix guy probably has too much time in his work to defend Windows 8 like mad... or MS is paying him. Anyway, what everyone that is protouch interface is failing to see is shown next:

it is NOT ACCURATE and does NOT ALLOW SEE below the fingers.

Because of this simple fail the mouse will reign supreme AND because of this, when anybody solves the two problems above will come with another way to interact the pcs that isn't touch, when that happens even the keyboard will render obsolete and then a change for the sake of the better will be executed.

With this said, such interface will remove all this touch BS that removes accuracy and renders GUIs pretty much less efficient than their mouse keyboard counterpart... The mind that is, once we're able to read and press our thoughts into a pc this madness will end. Patiently awaiting for it... if ever.

This topic is now closed to further replies.
  • Posts

    • Thank god they got rid of the disgusting looking sidebars, and the corner radius looks much better, too. Two things I hated on day one, and never got used to.
    • JetBrains launches Rider 2026.2 EAP 5, bringing several AI improvements by David Uzondu JetBrains has released the fifth EAP version of Rider 2026.2, bringing a faster startup flow with the new non-modal startup screen and quality-check hooks for Claude Code and Codex. In the latest EAP release, Rider now has newly bundled "quality-check" hooks that run background tests on code edits before the external agent proceeds. For example, after Claude Code rewrites a class, Rider immediately triggers a PostToolUse hook that analyzes the code for syntax errors and formatting warnings. It then passes those findings back to the model as feedback, allowing the agent to fix its own output before finalizing the task. If Rider detects compilation errors, the IDE prevents the agent from treating the task as complete, while minor formatting warnings simply help guide the model toward better output. The "Explain with AI" feature can now tackle tricky build errors directly from the console, helping .NET developers who frequently wrestle with multi-targeting failures and MSBuild errors. JetBrains introduced Explain with AI back in the 2024.1 release cycle. With this feature, instead of forcing developers to copy long diagnostics into a separate chat window, Rider now lets you trigger these explanations directly from the error source. In similar EAP news, JetBrains recently opened the first EAP for IntelliJ IDEA 2026.2, with features that appeal to both those who are into AI-assisted coding and those who prefer "classic" manual development. For manual developers, the release adds revamped dependency completion for Maven and Gradle build scripts, which pulls data directly from the local cache to suggest relevant versions. It also brings the Spring Debugger update, displaying security indicators next to endpoints to visualize secured routes during runtime. In addition to database migration tools for Flyway and Liquibase, this build introduces a Hibernate debugger that shows the exact SQL or HQL queries that the framework plans to execute, letting developers jump directly to the Java code that triggered them.
  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
  • Popular Contributors

    1. 1
      +primortal
      502
    2. 2
      PsYcHoKiLLa
      222
    3. 3
      ATLien_0
      87
    4. 4
      Steven P.
      80
    5. 5
      +Edouard
      80
  • Tell a friend

    Love Neowin? Tell a friend!