Windows Technical Preview  

1031 members have voted

  1. 1. On a scale of 1-5, 1 being worst, 5 being best. What do you think of Windows 10 from the leaks so far?

    • 5.Great, best OS ever
      156
    • 4. Pretty Good, needs a lot of minor tweaks
      409
    • 3. OK, Needs a few major improvements, some minor ones
      168
    • 2. Fine, Needs a lot of major improvements
      79
    • 1.Poor, Needs too many improvements, all hope is lost, never going to use it
      41
  2. 2. Based on the recent leaks by Neowin and Winfuture.de, my next OS upgrade will be?

    • Windows 10
      720
    • Windows 8
      20
    • Windows 7
      48
    • Sticking with XP
      3
    • OSX Yosemite
      35
    • Linux
      24
    • Sticking with OSX Mavericks
      3
  3. 3. Should Microsoft give away Windows 10 for free?

    • Yes for Windows 8.1 Users
      305
    • Yes for Windows 7 and above users
      227
    • Yes for Vista and above users
      31
    • Yes for XP and above users
      27
    • Yes for all Windows users
      192
    • No
      71


Recommended Posts

Yeah, the fact that the current marketing numbering of the OS doesn't follow the actual kernel numbering kinda bugs me.

 

It's no different than all the Linux distros and maybe even OSX itself?     None of those follow the kernel version for anything, besides a OS is more than just it's kernel.   Lots of things that make up Windows have different versions to them.

I really hope Windows 9 is the official name. I don't want Microsoft going back to yearly product names (9x releases) or "cute" names (XP, Vista).

 

Frankly, in a perfect world, we'd be looking at Windows NT 6.4...

 

Frankly if improves on win 7 & 8 then the name is irrelevant . :rofl:

Yeah, the fact that the current marketing numbering of the OS doesn't follow the actual kernel numbering kinda bugs me.

It was kind of the norm for Microsoft back in the day. Windows 3, Windows 3.1, MS-DOS 6, MS-DOS 6.22, etc.

 

They may be boring but at the end of the day, it's the simplest, most honest way to name your product.

It was kind of the norm for Microsoft back in the day. Windows 3, Windows 3.1, MS-DOS 6, MS-DOS 6.22, etc.

 

They may be boring but at the end of the day, it's the simplest, most honest way to name your product.

 

Yeah but you can't keep trying to sell a "major" new version of your OS and have it be labeled as 6.2 or 6.3 compared to 7 and 8.   It's the business side of things coming into play.  Back when those version of Windows and MS-DOS were being sold it was a different market, it was smaller and it was mostly techies who liked to know the version numbers and model numbers of things they were buying/using.   Now things have changed, heck things changed with Windows 95.

It was kind of the norm for Microsoft back in the day. Windows 3, Windows 3.1, MS-DOS 6, MS-DOS 6.22, etc.

 

They may be boring but at the end of the day, it's the simplest, most honest way to name your product.

 

honest yes but simplest? That not always true.

Myerson: "but the world in which Windows has grown up has changed", "Our new Windows must be built from the group up for a mobile first cloud first world."

 

 

I like this guy. He's speaking a lot of sense. :)

This topic is now closed to further replies.
  • 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!