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

Windows Technical Preview.

 

This is a discussion thread for that topic, I am voicing a legitimate concern, if you don't like it then I suggest you use the ignore feature, name calling, trolling, flame baiting, this seems to be the typical response and I am not guilty of any of it, I'm here to discuss windows 10 and its eventual failure/success.

 

Which metro apps are just as powerful and have matched, feature for feature, functionality for functionality, with modern desktop software?

You can't be so naive that expect metro app to be as powerful as the legacy app in such short amount of time which has improved for a very long time. Metro app might not have all the functionality compared to the desktop app but it provide a new way of interacting with it such as animation and more lively content. Missing feature will be slowly implement down the road.  :angry:

Not entirely true. You still can access to the old control panel and pin it to the task bar which isn't possible in previous version of windows. 

For now. It's being decommissioned though. Still people need to recognize that Windows is Metro. It's being rebuilt using the new properties of the MDL. Don't like that? Oh well. Switch to Android?

digging through the api (winrt), i noticed support for some new stuff

custom hardware devices

media casting devices

lights/lamps

serial ports

midi devices

battery reports/stats

audio devices input/output

call control(custom dialers?)

adaptive streaming

  • Like 2

There should be a Windows UI thread to put all this crap there. This thread has become a pile of stinking mess lately and is rather useless for those looking for new info.

I agree, this thread is way too long as it is, I'm thinking it's time to close it and start a new thread once we get a new build out be it a leaked one or the one released by MS on the 21st. Till then everyone try to stay on topic and quit trying to start arguments by calling others out by name.

digging through the api (winrt), i noticed support for some new stuff

custom hardware devices

media casting devices

lights/lamps

serial ports

midi devices

battery reports/stats

audio devices input/output

call control(custom dialers?)

adaptive streaming

It'll be very interesting to see just how much they can add to winrt by the time this hits RTM. One of the issues with apps is that the lack of API support for specific things holds the apps back. They need to be working double time to get winrt to feature parity with win32.

I agree, this thread is way too long as it is, I'm thinking it's time to close it and start a new thread once we get a new build out be it a leaked one or the one released by MS on the 21st. Till then everyone try to stay on topic and quit trying to start arguments by calling others out by name.

I have created a thread for the argument.

 

Members: you can post here:

https://www.neowin.net/forum/topic/1241422-the-great-modern-ui-debate-thread/?p=596699022

digging through the api (winrt), i noticed support for some new stuff

custom hardware devices

media casting devices

lights/lamps

serial ports

midi devices

battery reports/stats

audio devices input/output

call control(custom dialers?)

adaptive streaming

 

Not surprising - WInRT is being geared up as a replacement for win32 so eventually you'll see win32/win64 become an removable feature like how you can uninstall win32 on Windows Server. I wouldn't be surprised if at some point in the future we'll see Win32 completely removed from Windows RT in favour of a pure WinRT environment. 

Not surprising - WInRT is being geared up as a replacement for win32 so eventually you'll see win32/win64 become an removable feature like how you can uninstall win32 on Windows Server. I wouldn't be surprised if at some point in the future we'll see Win32 completely removed from Windows RT in favour of a pure WinRT environment. 

I would actualy expect that to happen with Windows 10 already. There is no need for the Win32 APIs on Windows RT anymore now Office is ported to WinRT and all other Desktop tools are as well (like calculator, etc).

Not surprising - WInRT is being geared up as a replacement for win32 so eventually you'll see win32/win64 become an removable feature like how you can uninstall win32 on Windows Server. I wouldn't be surprised if at some point in the future we'll see Win32 completely removed from Windows RT in favour of a pure WinRT environment.

doesn't WinRT sit on top of Win32 though?

WinRT 1.0 maybe, because apps suddenly quit when I kill explorer.exe, and also microsoft loves leave everything half-baked, no wonder why right after Windows 8 release, Sinofsky geared Windows 10 development process (suspended because development of 8.1). Paul Thurrott already said no, but I read another article contracy about that. Heck, it is even possible to call Win32 APIs from WinRT

Perhaps Order_66 posts' similar to DOS 4.0 disaster, when MSFT introduce new shell?

MS makes it possible to call win32 from inside metro to help with porting legacy apps. They know you can't just port year old apps to want right away so for now it's a halfway measure, they're also not stopping with WPF. I think going forward you'll see the ability to call/use winrt through WPF apps on the desktop, something developers are asking for.

I would actualy expect that to happen with Windows 10 already. There is no need for the Win32 APIs on Windows RT anymore now Office is ported to WinRT and all other Desktop tools are as well (like calculator, etc).

 

Not gonna happen. WinRT is built on top of Win32.

WinRT 1.0 maybe, because apps suddenly quit when I kill explorer.exe, and also microsoft loves leave everything half-baked, no wonder why right after Windows 8 release, Sinofsky geared Windows 10 development process (suspended because development of 8.1). Paul Thurrott already said no, but I read another article contracy about that. Heck, it is even possible to call Win32 APIs from WinRT

Perhaps Order_66 posts' similar to DOS 4.0 disaster, when MSFT introduce new shell?

Actually, no - Microsoft does NOT like to have a half-baked API.  However, developers (and users) want to keep that legacy base around, because they are used to it being there.  How much cruft was in the original Start menu, because it had not had a cleanout in eighteen years?  The Start menu had become like a wallet after a few years - chockablock full of crud and cruft; one thing that two-OS gap between the Start menu's canning and the replacement (with mini-Start) did was enable a complete clean-out of the cruft and crud.

 

That's the REAL issue with not just new features, but improvement and advancement of existing features - it may not be doable without a complete reset.  (Linux has had to deal with the same thing in terms of desktop environments - GNOME and KDE come to mind.)  But will your userbase let you?

digging through the api (winrt), i noticed support for some new stuff

custom hardware devices

media casting devices

lights/lamps

serial ports

midi devices

battery reports/stats

audio devices input/output

call control(custom dialers?)

adaptive streaming

And support for most of it (if not all of it) is coming (or there already) in the Technical Preview (some of it has been present since prior to 9870 - 9901 exposed addition of a few more such features); other features are improvements due to additions to Device Manager itself going back to Windows 8 (the audio I/O is the biggest example).  Device Manager - starting with Windows 8 (and even Server 2012) is MUCH finer-grained at picking up new devices than previous versions of Windows - desktop or server.  The problem that Windows has is that - until the Technical Preview - adjustability didn't match up with the detection.  9901 is a major step toward fixing that - and the next major build will be another step in the same direction.

digging through the api (winrt), i noticed support for some new stuff

custom hardware devices

media casting devices

lights/lamps

serial ports

midi devices

battery reports/stats

audio devices input/output

call control(custom dialers?)

adaptive streaming

Windows IoT edition?

Windows IoT edition?

Nope - most of those features are becoming commonplace in all hardware (the MIDI/audio features already are); it's about greater control and adjustability of those features on a user-specific basis.

 

It's basically about making the User Experience more personal - and not only is it NOT a bad thing, it has been a cornerstone of Windows in particular nearly from the beginning.

Why are you (in particular) insisting on "do not advance"?

 

Primarily because I'm not stupid enough to think that new = advanced. WMP works just fine as it is, butchering it's functionality and turning it into another watered down piece of metro crap would not be an advancement.

QuoteFor now. It's being decommissioned though. Still people need to recognize that Windows is Metro. It's being rebuilt using the new properties of the MDL. Don't like that? Oh well. Switch to Android?

 

Huh? Is Android a desktop OS? I think not...

I suppose you meant "switch to mac", in that case, well, we have other alternatives, we can stick to older versions of windows like XP, Vista and 7... not everyone needs to have the latest piece of software all the time... Windows 8 (with some tweaks and with 8.1 update 1 installed) works great for me but I really really miss the start menu.

For now. It's being decommissioned though. Still people need to recognize that Windows is Metro. It's being rebuilt using the new properties of the MDL. Don't like that? Oh well. Switch to Android?

i'm confused. what does Android have to do with Windows 10 TP? So you're saying users who don't all agree that windows is metro now, should switch to android? One is a mobile OS and the other is a desktop OS.  :/  Being a bit rude... hey

i'm confused. what does Android have to do with Windows 10 TP? So you're saying users who don't all agree that windows is metro now, should switch to android? One is a mobile OS and the other is a desktop OS.  :/  Being a bit rude... hey

The other is  a mobile OS, a desktop OS, a tablet OS, and a Game Console OS.  Android is a Mobile OS and Tablet OS.

 

:)

i'm confused. what does Android have to do with Windows 10 TP? So you're saying users who don't all agree that windows is metro now, should switch to android? One is a mobile OS and the other is a desktop OS.  :/  Being a bit rude... hey

There are those here who are under the impression Android will replace Windows.

doesn't WinRT sit on top of Win32 though?

 

It really depends on what one defines as win32 given that it appears that gradually what Microsoft has defined as Win32 has either been spun off and categorised as its own or it has been relabelled as a 'low level library' that sits as an low level library for WinRT. When I'm thinking of Win32 I probably should be more accurate - removing dependency on GDI/GDI+, Common Control and Dialogues along with other legacy technologies. I guess in the case of Microsoft they're gradually, piece by piece, replacing legacy code whilst ensuring that a move forward has as minimal disruption as possible. Eventually WinRT once 'complete' will include parts of what used to be part of win32, the re-classification of some win32 parts as low level (which pushes them down the stack and shared between Windows Phone, Windows RT and Windows x86/x64).

This topic is now closed to further replies.
  • Posts

    • Microsoft launches Godot Sample to streamline Xbox PC game development on the engine by Pulasthi Ariyasinghe Microsoft today announced a new endeavor that aims to make it simpler for Godot developers to get their products into the Xbox PC ecosystem. Dubbed the "XBOX Godot Sample," this is a new public reference for developers using the open-source engine. This is set to serve as an example of how Microsoft GDK, Xbox Services, and PlayFab can be integrated into their projects. The sample is available now on GitHub as a working example. This covers key features in gaming projects that developers may need to release their projects on Xbox PC, with everything from matchmaking and game sign-in to gamepad compatibility with Godot being covered. This release is being called the first step in giving Godot developers the tools to bring their games over to Xbox PC, with more changes to come based on feedback and issue reports. However, the company was clear that this is not related to bringing Godot projects to Xbox consoles. The engine's open development model stops it from accessing console SDKs due to the requirement of NDAs and legal contracts. Here's how it explained this Godot sample project's focus: This is a source-only sample, not a product. It's MIT-licensed at the wrapper layer; the GDK and PlayFab dependencies still require their own installs and license acceptance, consistent with our other XBOX samples. There is no set update cadence for support or maintenance. We’ll watch the repo, monitor issues, and iterate where it makes sense, but this isn't a commercial release. That said, we’re excited to hear your feedback and see any community PRs, as we evolve this together. This is the first step in bringing Godot for XBOX on PC. We plan to evolve it over time based on what the community tells us is most valuable. This sample is built specifically for XBOX on PC. It doesn’t include support for XBOX Series X|S or XBOX One. If you’re already building for XBOX Series X|S or XBOX One, please talk with your XBOX representative. If not, you can get started by signing up here. Game developers can find the XBOX Godot Sample by heading to GitHub over here. Documentation on how to get started with Godot for building an Xbox PC project can be seen here.
    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • It is notable that around 70% of web browser users choose Google Chrome. However, it is puzzling why anyone on Windows would opt for Chrome when Microsoft Edge is often superior in many aspects and comes pre-installed. Edge collects less data, uses less RAM, and is more optimized for Windows as a native Microsoft product. While some may point to bloat in Edge, much of it can be removed with simple tools, requiring no more effort than installing Chrome. Meanwhile, Chrome reportedly downloads large amounts of AI data (4 GB) without explicit consent. I'm sure you Chrome users love that, or? Here is one example of a tool that doesn't even need to be installed to be able to use: https://github.com/TheBobPony/MSEdgeTweaker Although Microsoft’s aggressive promotion of Edge may be questionable, the browser’s current advantages make it a preferable choice over Chrome today, even if Chrome may have been better in the past.
    • 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.
  • 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!