Recommended Posts

However, it's a relevant limitation. There isn't any practical limit to the number of applications on the Windows taskbar, yet the situation is very different when you jump into WinRT apps - it's a very low limit at that. It irritates me that Microsoft opted to implement a second taskbar just for Metro apps and to have it hidden by default, along with the aforementioned limitations. It really does seem bolted on.

Ugh ... the switcher is not really meant as a counterpoint to the taskbar, in that it's a shortcut to get to "recent" apps not "running" apps. Think of it like the little arrow next to the Back button in Windows/File Explorer, or the address bar of a web browser, showing recent history. But this gets to one of my pet peeves in that I'm not sure the switcher should even have been added at all as it just confuses things - the Start screen is a better way to switch apps most of the time. The switcher is useful as a way of snapping apps, but there should be a better way of snapping apps from the start screen anyway, so ...

Why would you need more than a couple Metro applications actually running full time? The number of programs that actually need to be running 100% of the time isn't that great and would work perfectly fine with scheduled updates/notifications. Media players, torrent clients, etc sure. But for the vast majority of Metro applications, not really.. 99% of the time they're waiting on you to do something anyway or run functions at scheduled times.. they wake up, do their thing and go back to sleep again.

They don't allow any MetroApp to run in the background and only allow scheduled tasks to do so. For them to put any limit on the desktop is a joke. I don't think my Quad Core + HyperThreading i7 with 16GB of RAM and an SSD would even feel the impact of the apps running 24/7 or the background tasks running just as long.

Those limits are fine on my cellphone where the increased activity = battery drain. No such scenario exists on my PC here at home.

They don't allow any MetroApp to run in the background and only allow scheduled tasks to do so. For them to put any limit on the desktop is a joke. I don't think my Quad Core + HyperThreading i7 with 16GB of RAM and an SSD would even feel the impact of the apps running 24/7 or the background tasks running just as long.

Those limits are fine on my cellphone where the increased activity = battery drain. No such scenario exists on my PC here at home.

Actually one of the most common performance problems people hit on desktop PCs is "runaway" apps. The new model goes a long way to preventing exactly this problem.

Actually one of the most common performance problems people hit on desktop PCs is "runaway" apps. The new model goes a long way to preventing exactly this problem.

I don't know if you're being serious or not here... You're seriously suggesting that we shouldn't be allowed to run more than one app at a time on Quad Core CPUs with HT (which effectively handle 8 threads at a time)?

You know, depending on your resolution even the taskbar has a limit on how many things it can show, just like the new metro switcher does. When people who went on about the start screen were told to just pin things they use the most to the taskbar they snapped back saying that they don't have enough space there for everything. Metro apps will work in the background on their schedule regardless of if they're added to the lock screen or show up in the switcher unless the system needs more RAM and then they get paged out or closed.

As some have said I think people are mixing things up here, the limits on what you can add to your lock screen are different from the limits of how many apps can show up in the switcher and so on. In the end the apps should all just work, in the background, regardless. The only difference is if they're running on a schedule or if you're on a desktop without battery constraints and they just run normally when they have to.

I don't know if you're being serious or not here... You're seriously suggesting that we shouldn't be allowed to run more than one app at a time on Quad Core CPUs with HT (which effectively handle 8 threads at a time)?

I never suggested anything of the sort. What makes you think I did?

  • 6 months later...

If background apps only get 1-2 CPU seconds per 15 minutes, how come there are music streaming apps that run just fine in the background? Is that enough for them, or is there something else I'm missing?

I thought metro apps could only be in focus, suspended, or not running. And suspended (background apps) only got very little CPU time allotted to them for push notifications and such.

Anyone?

If background apps only get 1-2 CPU seconds per 15 minutes, how come there are music streaming apps that run just fine in the background? Is that enough for them, or is there something else I'm missing?

I thought metro apps could only be in focus, suspended, or not running. And suspended (background apps) only got very little CPU time allotted to them for push notifications and such.

Anyone?

there are certain scenarios when background stuff is permitted and theres a part of the API for that. This includes background audio and background downloading.

I never suggested anything of the sort. What makes you think I did?

I thinks he thought you were talking about the limitation of the number of background tasks running at once to mean number of apps. To be clear, what Brandon is referring to is the new the app Lifecycle management where apps are suspended when you navigate away from them. This means apps are consuming NO resources when not present other than memory which uses the same amount of power regardless if their is meaningful data occupying it. Because of this, minimized apps will not run rampant on your system affecting battery life or performance. As memory becomes scarce, Windows will close apps as needed to reclaim memory (this is why you no longer have to close apps.) Again, Windows places no restriction on the number apps running at once.

Apps can get special permissions to run short tasks in the background in a controlled manner, as others have mentioned which allows them update live tiles, downloads, play music, notifications, and such.

there are certain scenarios when background stuff is permitted and theres a part of the API for that. This includes background audio and background downloading.

Also, while 2 seconds doesn't seem like a lot, it actually is a lot of time to a really fast CPU. The seconds don't have to be continuous, but can be spread out as needed. Most of the time the app just needs short bursts (say 10 milliseconds) and then goes dormant for a bit, another short burst, then dormant...and so on.

Playing audio is a special case. Usually CPUs or GPUs have hardware decoders anyway which are extremely efficient so the extra time needed won't affect battery life much.

This topic is now closed to further replies.
  • Posts

    • Exactly. They won't go 100 because current gen consoles are simply too old for any groundbreaking graphics or gaming experience otherwise. They will go with standard (console) price 70 or go with 80 if they really want to go premium. Of course they will have more expensive options too with some useless cosmetics as always.
    • Doesn’t surprise me at all. God is light & He gave us life so it sounds almost logical that we would therefore emit a certain amount of light.
    • This is what I want. Hey Gemini, how do I remove you from all my google products permanently?
    • I would never install install this build before rtm process. only 3 months to go. never install on your daily devices. just wait 3 months.
    • Motrix Next 3.9.6 by Razvan Serea Motrix Next is a modern, open-source cross-platform download manager built as the official next-generation successor to the original Motrix project. It has been completely rewritten using Tauri 2, Vue 3, TypeScript, and Rust, while still relying on the powerful Aria2 download engine for high-speed multi-protocol transfers. The app supports HTTP, HTTPS, FTP, BitTorrent, ED2K and magnet links, offering advanced features like multi-connection acceleration, task scheduling, bandwidth control, and batch download management. With a significantly reduced install size (around 20MB), it focuses on being lightweight, fast, and resource-efficient compared to traditional Electron-based download tools. Designed for Windows, macOS, and Linux, Motrix Next delivers a clean, modern UI inspired by Material Design 3 principles, with smooth animations and a minimal workflow. It improves usability through better download organization, system tray integration, and enhanced torrent handling including selective file downloads and tracker management. Motrix Next features: Multi-protocol downloads — HTTP, FTP, BitTorrent, Magnet, .torrent, ED2K, and Metalink tasks BitTorrent — Selective file download, DHT, peer exchange, encryption controls, metadata caching, GeoIP peer flags, and tracker probing Browser extension integration — Embedded Extension API with independent authentication, download confirmation, smart auto-submit, filename hints, referer/cookie forwarding, and real-time controls (Chrome Web Store · Edge Add-ons) Safe filename handling — Content-Disposition, RFC 2047, non-UTF-8, percent-encoded, and extensionless URL resolution with path traversal sanitization Download organization — Favorite and recent folders, optional file-type categorization, stale-record cleanup, and completed history backed by SQLite Concurrent downloads — Independent controls for active tasks, HTTP connections per server, segments per file, and BT peer limits Speed control — Global and per-task upload/download limits with day-of-week and time-of-day scheduling System integration — Tray operation, optional tray speed display, macOS Dock badge/progress, protocol handlers for magnet://, thunder://, and motrixnext:// Lightweight mode — Destroys the WebView on minimize-to-tray while Rust keeps the engine, task monitor, notifications, history, and extension routing alive Notifications and power options — Native task start/complete/failure notifications, keep-awake during downloads, and optional shutdown after completion Network controls — Scoped proxy support for downloads, app updates, and tracker updates, plus system proxy detection Auto-update channels — Stable, Beta, and Latest Across Channels policies with separate download and install phases Diagnostics — Structured logs, exportable diagnostic ZIPs, database integrity checks, automatic DB rebuild, and Linux GPU rendering fallback Personalization — Light/dark/system theme, 10 color schemes, 26 languages, and first-launch system language detection Motrix Next 3.9.6 changelog: New Features Clipboard management — App-owned copy actions no longer trigger the Add Task auto-detect popup. aria2 input compatibility — Multi-line aria2-style task input is supported for URLs with per-task options such as out=. BitTorrent IPv6 DHT — Added IPv6 DHT support and related configuration. File category URL patterns — File category rules can match URL patterns with validation and localized hints. Task status tags — Added clearer waiting and sharing states for task cards. Download event bridge — Added an aria2 WebSocket event bridge for faster download notifications. Improvements Improved task list transitions and preserved task state during tab switches. Kept RPC origin access enabled for local integrations. Restored AppImage stripping in release builds after beta validation. Added localized preference guidance across supported languages. Download: Motrix Next 64-bit | ARM64 | macOS ~20.0 MB (Open Source) Links: Website | macOS / Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      +Edouard
      181
    3. 3
      PsYcHoKiLLa
      86
    4. 4
      Michael Scrip
      78
    5. 5
      Steven P.
      75
  • Tell a friend

    Love Neowin? Tell a friend!