Recommended Posts

Maybe it's me, but I really can't understand Microsoft's implementation of Live Services within Windows 8.

I tried to use it, before giving up and just using Windows Live Essentials 2011.

Now I'm signed in at two places on the same computer because I linked my Microsoft ID with my domain account, the metro messenger app is clunky and not intuitive at all, I prefer the WLM pane with my contacts showing on my 2nd desktop all the time with open conversations on that same desktop. Messages popup as (metro) notifications alerts long after I've already received them in WLM 2011 and to top it off I also have Skydrive installed as a virtual drive in My Computer, I fail to see how the Metro version could ever replace it?

Can anyone who's had more success with the Live services explain to me what I'm doing wrong? :p

Edit: The People app and Messenger app isn't easy to use either.

Th integrated apps aren't replacing the live suite anyway. Different uses.

Well there's almost one for every WL Essentials app. Why would anyone want two versions of Skydrive and Messenger installed among others anyway?

I've been trying to figure this out, too. Especially Photo Gallery, with batch people tagging and the photo fuse or whatever they call it. The current metro app seems like a pretty huge step backwards, so it's either FAR from done, or there will be an updated set of desktop apps.... right?

Conceptually I think people have a problem understanding the new metro apps, that and the fact they're not necessarily gonna replace the desktop versions on a desktop.

But people are used to WLM for example haing image sharing, file transfer and all that bolt into the one app, and mail replicates some of that and soon.

With metro, these apps are use a front end for the full live back end that's fully integrated into windows. That means that the people/messaging app,it only needs to do what it's supposed to, lis people and message them, or receive messages. Meanwhile image sharing or transfer is handled fully by the OS through the charm menu, which then lets ou share the image over any method you choose, WLM, mail, cloud storage.... Same with file transfer and all that other stuff. Handled like these all the apps don't need to duplicate functions, instead they share the functions through a more intelligent OS design.

This is also something any WP user will recognize and appreciate.

For a desktop user this might to make sense though and they may choose to disable the metro apps for messaging and mail and instead use the old and eventually new desktop live apps. It's not like MS going to abandon a powerful desktop app like live mail in favor of metro mail. Metro mail is good enough for a lot of things and people but is not a live mail replacement.

Maybe it's me, but I really can't understand Microsoft's implementation of Live Services within Windows 8.

I tried to use it, before giving up and just using Windows Live Essentials 2011.

Now I'm signed in at two places on the same computer because I linked my Microsoft ID with my domain account, the metro messenger app is clunky and not intuitive at all, I prefer the WLM pane with my contacts showing on my 2nd desktop all the time with open conversations on that same desktop. Messages popup as (metro) notifications alerts long after I've already received them in WLM 2011 and to top it off I also have Skydrive installed as a virtual drive in My Computer, I fail to see how the Metro version could ever replace it?

Can anyone who's had more success with the Live services explain to me what I'm doing wrong? :p

Edit: The People app and Messenger app isn't easy to use either.

Metro apps are optimized for low bandwidth usage... if you will download emails from the desktop app with a 3G connection, you can start to sell your car to pay the bill. Are you on a desktop? Don't use metro apps... easy

"Damned if they do, damned if they don't"

That pretty much summarizes everything Microsoft does/doesn't do to their most popular products.

  • Like 2

Depends on how you want to use your computer. Metro on the go, desktop at home, etc.

What about those of us who would like to use Metro at home, too? There is no way I would enjoy using the Metro experience on the go and the desktop experience at home because the two are incredibly inconsistent.

I would hope that Microsoft will update these apps with great features before release, and the "APP PREVIEW" labels seem to suggest they will.

Metro apps are optimized for low bandwidth usage... if you will download emails from the desktop app with a 3G connection, you can start to sell your car to pay the bill. Are you on a desktop? Don't use metro apps... easy

It isn't "easy" because the Metro experience was designed for use on desktop PCs, too.

Does anybody have this problem with the Messaging App.

I can only start a conversation with people that I have on messenger, not my facebook contact.

But when FB contacts start a conversation with me it picks it up.

If I just start the people app I can see all my contacts from FB and Messenger.

The included Metro apps are previews and only have incredibly basic functionality, hence why they have the disclaimer at the top - Microsoft is going out of its way to make sure users don't confuse them for the final version. In fact some of them are verging on unusable because of how limited they are, like Mail and Music. However, even though I like Windows 8 I really can't see myself using Metro apps for anything other than snapping to the side of my desktop. I have a 30" display and make extensive use of multi-tasking, so the last thing I want is for an app like Mail or Skydrive to take up the entire screen - I much prefer using the desktop with Aero Snap. The only Metro app I use in fullscreen mode is the XE.com currency converter, which is a considerable improvement over the website. Metro apps are more suited to tablets or touchscreens, though I think they should be differentiated from the Metro Start screen which is designed with high resolution desktop monitors in mind and really works well.

I hope they develop them with C++, right now it seems that they are developed with JavaScript.

The "People" application is incredibly terrible in terms of performance.

Microsoft do develop the logic in C++ - technically they use a HTML & JS frontend for the UI that call the C++ DLL's for the logic - for some reason they don't seem to want to use XAML & C++ at ALL within Microsoft, so we're only left with HTML. But yes, all the first party metro MS apps seems to use HTML (bar the Xbox team apps - I'm not sure what they use. Their performance is still pretty dire though too at the moment).

You have to use either DirectX, XAML or HTML as your UI frontend, even if you're using C++, and direct DirectX is out of the question unless you want to reimplement all the logic for all the controls.

Microsoft do develop the logic in C++ - technically they use a HTML & JS frontend for the UI that call the C++ DLL's for the logic - for some reason they don't seem to want to use XAML & C++ at ALL within Microsoft, so we're only left with HTML. But yes, all the first party metro MS apps seems to use HTML (bar the Xbox team apps - I'm not sure what they use. Their performance is still pretty dire though too at the moment).

You have to use either DirectX, XAML or HTML as your UI frontend, even if you're using C++, and direct DirectX is out of the question unless you want to reimplement all the logic for all the controls.

Wouldn't XAML + C++ give better performance than HTML + JavaScript?

Wouldn't XAML + C++ give better performance than HTML + JavaScript?

I'm not entirely sure, though I believe XAML is heavier on the RAM and takes the CPU longer to actually initially parse and create visuals from XAML than with HTML. Keep in mind the IE10 rendering and layout engine has seen WAY more optimization than the Silverlight based XAML engine in WinRT, which is probably why they're pushing it so much. In the current implementation, XAML touch events also have far more latency than touch events in HTML apps, and I'm not sure if that's be design or not (but it should be something Microsoft should easily be able to fix)

They've also gimped XAML in WinRT more than it was in Silverlight (which in turn could have been considered a step down from WPF) - gone are pixel shaders so no blurring or shadows, gone are even simple things like RadialGradientBrushes, gone is rendering visual elements to bitmaps, amongst other things. I'm sure if they put as much optimization effort into the XAML engine as they do with the IE engine things would get better, but the IE engine is a bigger priority for them, and given how much [not] effort there seems to be in actually improving XAML in WinRT, it doesn't look that bright.

Of course, I also think most developers would have a much easier and quicker time coding in XAML & C# / C++ than using HTML & JS in the first place too, and I prefer styling and animation in XAML over HTML / CSS & JS anyday.

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

    • No registered users viewing this page.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!