Recommended Posts

it will look a little different when windows 8 RTMs.

You can see how most pro apps don't use glass. They have their own UI. Now they can actually simplify it to make it more attractive and consistent with the rest of the system.

I am already seeing some apps go the Zune UI way.

I'm still seeing folks going on and on about the tutorial coming in Windows 8. Apparently, they've forgotten about this guy:

and don't forget the tutorial/interactive video thing that XP had

It was pretty much exactly like that (using the available tech at the time of course). However it did force developers to immediately start developing for OS X rather than letting "Classic" linger for ages, something I'm afraid will happen with the desktop on Windows. OS X Cheetah was released in 2001, the same year Microsoft made an Office version for it available.

I was using safari in full screen today and had to switch back-forth once (felt exactly same as switching between metro apps/desktop on Win8) and that got me thinking that the Classic or Legacy windows apps are not going anywhere. Microsoft will just make them run full screen in Windows 8+ (either a service pack or in 9 etc.) without additional features that WinRT apps enjoy.

It's amazing how much similar the full screen mode on OS X Lion feels like Windows 8.

I was using safari in full screen today and had to switch back-forth once (felt exactly same as switching between metro apps/desktop on Win8) and that got me thinking that the Classic or Legacy windows apps are not going anywhere. Microsoft will just make them run full screen in Windows 8+ (either a service pack or in 9 etc.) without additional features that WinRT apps enjoy.

It's amazing how much similar the full screen mode on OS X Lion feels like Windows 8.

Difference is you're not confronted with apps that have a radically different interface and window behavior. I'm also not being forced to use full-screen with a certain set of apps.

Personally I hardly ever use full-screen on OS X Lion simply because it serves no real purpose on a 27-inch screen. QuickTime X and VLC being the obvious exceptions of course. ;)

and don't forget the tutorial/interactive video thing that XP had

hated it from the bottom of my heart every time I had to install XP or create a new user on a box WHERE I HAD ALREADY DISMISSED THE DAMN TUTORIAL! :angry: :laugh: That stupid thing wouldn't go away unless I opened and closed it once!

(Somebody will no come by and point out an easier way to dismiss it after all these years!)

Difference is you're not confronted with apps that have a radically different interface and window behavior.

true. It does share at least one aspect though - hiding UI controls :p (like exiting out of full screen button in the menu bar).

I agree with this. Literally, all of the older generation and people who aren't really technophobes who I've shown Windows 8 too - as soon I've showed it too them and told them that's the new Windows, they've literally said "okay" and got on with it. They don't care and they've not questioned it, and they've all seemed fine. As long as their stuff works, boom. :p

Same here. Out of the eight :D people I have shown it to and let them use it, none, not one, has complained about any of the things that I see people here griping about all the time.

Not one of them said "what happened to the start thingy?"

or "why does it take x clicks to do y".

They sat down, looked at the screen, clicked on their desired tile, and got going.

Geeks see their control of the dark arts slipping away from them, and go into hissy fits over things the average user doesn't give two figs about.

true. It does share at least one aspect though - hiding UI controls :p (like exiting out of full screen button in the menu bar).

Yeah of course, they wouldn't make much sense when a window is full-screen. You do on the other hand still have access to the same universal Menu Bar, Dock and Mission Control. It's not like they're used for windowed apps only. My point is there isn't a split-up between full-screen apps and windowed ones and you're not forced to use something full-screen only. It's still all and the same Aqua interface. :)

I get it, but I'm not digging it. I've always been fond of the glass look. Switching to this is probably going to make me wonder what's wrong with my video driver for the first few days, since it looks like Aero Lite.

Got a chuckle out of that one, nice.

Seems that MS is just guessing at what to do, and it's kind a late in the dev cycle for that if you ask me. However, removing Aero makes sense in one area ... VDI. The GPU resources for Aero (RemoteFX) add up. Simply removing it and settling on a somewhat bland simple to render Gem OS-like color scheme removes this resource requirement. To be honest, it is needed in that environment as we won't be stacking Quadro GPUs at a minimum of $400 pop for 5-10 desktops each card. It's much easier to tell users the Aero themes are no longer in Windows as it is to tell them you can's have that nice transparency, etc. because we're not gonna buy the resources to do it. All users will do is demand a desktop which we don't want anymore. We're moving to VDI and Windows 7 seven ASAP. Windows 8 will be a support and end user nightmare and its going to be a helluva lot easier to deal with in a Virtual Desktop World.

If that's their justification it's a pretty pathetic one. With Windows 7 they have already designed it so that it disables Aero whenever resources are needed elsewhere, or when an application runs that isn't compatible with it. And it's not exactly as if Aero takes up much of a resource footprint, $30 bargain bin graphics cards are capable of running it these days with few issues so it just strikes me as being a very questionable design choice, especially given that with the introduction of Vista, Aero was one of the most popular features.

If that's their justification it's a pretty pathetic one. With Windows 7 they have already designed it so that it disables Aero whenever resources are needed elsewhere, or when an application runs that isn't compatible with it. And it's not exactly as if Aero takes up much of a resource footprint, $30 bargain bin graphics cards are capable of running it these days with few issues so it just strikes me as being a very questionable design choice, especially given that with the introduction of Vista, Aero was one of the most popular features.

Don't trust a randumb advice on the internet who makes such assumption based on a screenshot.

So far, MS didn't announce that they are giving up on GPU/2D acceleration to draw component on the Desktop. The funny part about that is that all Metro apps are GPU accelerated;hence the "fast & fluid" experience.

Because the glass effect is being replaced by a solid color doesn't makes it using less resources than before.

I invite you to test it by yourself or to wait for reviews that compare GPU usage on Windows 7 and Windows 8. For now you can download any software that shows GPU usage (ex: process explorer) and see how low Aero uses your GPU. My current GPU usage is around 1% as I'm writing this post. Will Windows 8 uses 0%? I highly doubt it. Also it won't be using my CPU because that would makes it really heavy on the CPU usage, and it will kill any laptop battery.

If that's their justification it's a pretty pathetic one. With Windows 7 they have already designed it so that it disables Aero whenever resources are needed elsewhere, or when an application runs that isn't compatible with it. And it's not exactly as if Aero takes up much of a resource footprint, $30 bargain bin graphics cards are capable of running it these days with few issues so it just strikes me as being a very questionable design choice, especially given that with the introduction of Vista, Aero was one of the most popular features.

I'm not going to get into RemoteFX and VDI, but removing aero was not required to alleviate the overhead, simply making classic the default theme would suffice. When you take away desktops, users want the same experience or they will complain and demand that they should be allowed to spend their budgets how they see fit and not accept a lesser remote session.

I think MS' justification is trying to wean everyone away from Windows 7. Remember, Windows 7 is the best desktop OS out there and there's really no good reason to change other than MS' furthering their Phone and Tablet efforts and leveraging their desktop dominance to do so. That's my personal feeling on the matter. Windows 7 isn't going down easy so the more different they can make 8, the more they can give the appearance they are offering so much more. MS Shareholders do not need nor want Windows 7 living as long as XP, and given it's superioirity, it can last twice as long.

There's also a bit of MS has never had much style. Look at Windows icons and the customization market. Look at gadgets, then look at Widgets, Konfabulator, and X-widgets. Aero is the most stylish thing MS ever did, lol.

Looking at the metro frameworks we have, it'd be voodoo for them to get a decent performing version of Office running in Metro, and I really can't seem them ever porting over the full applications - not with the current frameworks anyway. Maybe smaller, bite sized, metro-optimised versions, but not the full prowess of the suite. And to be fair, the full programs aren't suited for Metro anyway with the amount of options they have at their disposal.

Going with what we have now then yes, but I doubt the APIs will stay at the level they are now. I fully believe WinRT is the next step and Win32 will slowly work it's way off of the OS over time. I don't see why the apps wouldn't work in metro, we're just talking full screen versions of them. They all have the ribbon and that covers what you need really. I'm sure it's doable, UI wise there really isn't anything to hold them back, it's just like you said the frameworks aren't there yet. This is also why right now they haven't allowed metro apps to even run on the desktop but I expect that to change at some point.

The blog only states that rendering realistic glass with all the required effects necessary to sustain that illusion looks, "Dated and Cheesy". This I could agree with. I don't, but I could. The glass effects in Vista and Win7 are not very realistic anyway.

I think a translucent window frame achieves the design goal of reducing the visual weight of the chrome better than solid white borders. A clear frame simply is not there. A white frame is there no matter how pristine the white is.

Sorry for the double post:

Going with what we have now then yes, but I doubt the APIs will stay at the level they are now. I fully believe WinRT is the next step and Win32 will slowly work it's way off of the OS over time. I don't see why the apps wouldn't work in metro, we're just talking full screen versions of them. They all have the ribbon and that covers what you need really. I'm sure it's doable, UI wise there really isn't anything to hold them back, it's just like you said the frameworks aren't there yet. This is also why right now they haven't allowed metro apps to even run on the desktop but I expect that to change at some point.

What about comparing multiple documents side by side? Snapping allows two different applications to be used simultaneously. However, a user writing a report can easily have several documents open at once, along with a few web pages for reference. Expecting the user to swipe to the right to switch between all of these windows is extremely cumbersome and a bit slow.

Yes, currently the traditional desktop is there to support the existing Office and this usage case but that only supports accusations that Metro is unsuited for getting any "real" work done.

Sorry for the double post:

What about comparing multiple documents side by side? Snapping allows two different applications to be used simultaneously. However, a user writing a report can easily have several documents open at once, along with a few web pages for reference. Expecting the user to swipe to the right to switch between all of these windows is extremely cumbersome and a bit slow.

Yes, currently the traditional desktop is there to support the existing Office and this usage case but that only supports accusations that Metro is unsuited for getting any "real" work done.

If you read carefully the long blog post, you'll see that Metro isn't made to replace the Desktop. Both are going to live side by side for a very long time.

Don't trust a randumb advice on the internet who makes such assumption based on a screenshot.

So far, MS didn't announce that they are giving up on GPU/2D acceleration to draw component on the Desktop. The funny part about that is that all Metro apps are GPU accelerated;hence the "fast & fluid" experience.

Because the glass effect is being replaced by a solid color doesn't makes it using less resources than before.

I invite you to test it by yourself or to wait for reviews that compare GPU usage on Windows 7 and Windows 8. For now you can download any software that shows GPU usage (ex: process explorer) and see how low Aero uses your GPU. My current GPU usage is around 1% as I'm writing this post. Will Windows 8 uses 0%? I highly doubt it. Also it won't be using my CPU because that would makes it really heavy on the CPU usage, and it will kill any laptop battery.

Yes, that was precisely my point. The footprint is so low there's simply no justification I can see for removing it. Having the UI GPU accelerated is great but I personally think this new design just looks horrible. I liked Aero because it was a break from the traditional dull gradients that were traditional for so many years. I just feel as if Microsoft have taken a big step backwards here.

If you read carefully the long blog post, you'll see that Metro isn't made to replace the Desktop. Both are going to live side by side for a very long time.

That doesn't address my point. Office does not work well in Metro, how can this be fixed?

Yes, it does. Since Office isn't a Metro app, there isn't anything that needs fixed at the moment.

I really hope you realize you're completely talking out of your ass. Apple had to support legacy apps all the same back in May 2001 when they first released OS X. Why exactly do you think they incorporated "Classic" into the OS and continued to support it until OS X Leopard (2007)? The main difference is that Apple released their important new apps for OS X from the get-go instead of letting then run only within the old Classic environment. Microsoft on the other hand is actively sustaining the desktop for the years to come by not releasing something like Office 15 for Metro, which in my opinion is a huge mistake. If a suite like Office is truly better off running within the desktop environment - as some have brought up in defense - you know there's something fundamentally wrong with Metro.

My original point however is you can't really speak of a "uniform" situation when you're dealing with two completely different interfaces that each run their own separate set of apps within the same OS, which isn't just there for legacy purposes.

The point is that unlike classic, the desktop in Windows 8 is just an app and not an entire OS like classic was, that, as you said, was dropped in Leopard. That shows that Apple don't need to maintain backwards compatibility for the userbase it has.

Microsoft however, need to maintain backwards compatibility for the sake of applications that have no Metro version e.g. Office 2010 or lower or even custom applications that are used by businesses, there's no Metro version available and I don't think businesses will spend the money rewriting any custom applications they use, this means that the "two interfaces" have to co-exist. Office could run quite happily in a Metro environment but it would have to use WinRT APIs, which older versions of Office don't use.

Yes, that was precisely my point. The footprint is so low there's simply no justification I can see for removing it.

Actually delivering the full Aero experience to 100s, 1000s of remote clients is not low. I'm not saying that's why they did it, I'm saying that's one positive. Though I am sure this would be on anyone's top 5 reasons to drop Aero.

I love Aero and think what's in the screenshot is fugly. Would prefer it stayed. But no Aero will save a ton of money and resources and gig to the desktop may not be as necessary as it is now for large VDI environments.

VDI and App-V's time has come.

This topic is now closed to further replies.
  • Posts

    • AMD RX 9070 GRE AI, Blender benchmarks vs 9070 XT, 7800XT, Nvidia RTX 5070, 4070 by Sayan Sen Earlier this week, we shared the first part of our review of AMD's new RX 9070 GRE. It was about the gaming performance of the GPU, and we gave it an 8 out of 10. As a follow-up, similar to how we did with the 9070 XT and non-XT, we are doing a dedicated productivity review for the RX 9070 GRE as well, where we compare it against the 9070 XT, 9070, 7800 XT, as well as Nvidia's 5070 and 4070. This will include AI, rendering, compute, and more benchmarks. AI performance, especially, is a very important metric in today's world, and AMD also promised big improvements thanks to its underlying architectural improvements. We will be pitching it against the data we already have for the RX 9070, and RX 9070 XT, but also the Nvidia 5070 FE, MSI GeForce RTX 4070 VENTUS 2X 12G, and Gigabyte Radeon RX 7800 XT GAMING OC 16G as they are in a similar price class, but also because we do not have a comparable 5060 Ti card lying around here that we can compare it against. Before we get underway, this is a collaboration between Sayan Sen and Steven Parker, who lent me his test bed. Also, there was no editorial input from AMD. First up, the specs of the RX 9070, 9070 XT, and 9070 GRE, which were given to us by AMD: Radeon RX 9070 GRE Radeon RX 9070 Radeon RX 9070 XT Boost Clock: Game Clock: up to 2.79GHz up to 2.20GHz up to 2.52GHz up to 2.07GHz up to 2.97GHz up to 2.40GHz Stream Processors 3,072 (48 CU) 3,584 (56 CU) 4,096 (64 CU) Ray Accelerator 48 56 64 AI Accelerator 96 112 128 ROPs 96 128 Texture Mapping Units 192 224 256 Memory 12 GB GDDR6, 18Gbps Clock, 192-bit Bus 432 GB/s 16 GB GDDR6, 20Gbps Clock, 256-bit Bus Effective Memory Bandwidth: 640 GB/s Infinity Cache 48 MB (3rd Gen) 64 MB (3rd Gen) Card Bus PCI-E 5.0 X16 Output 2x HDMI 2.1b 2x DisplayPort 2.1a Power consumption 220W 304W Recommended PSU 650W 750W Slot width 2x 3x Price (SEP) $549 $599 As you can see from the specs above, it is less than the standard RX 9070 in every way that counts, except for slightly higher Boost and Game clock speed. Design Moving on, the RX 9070 GRE we were given is an XFX Swift triple-fan, dual-slot design with two 8-pin connectors. At 30cm (self-measured), it will fit in most systems easily. There is no RGB either. The AMD Radeon RX 9070 GRE by XFX from all angles. Test system Our test system consists of the following: Lian Li O11 Dynamic Mini V2 Flow (Amazon|Newegg) ASUS Z890 ProArt Creator WiFi (Amazon|Newegg) Intel Core Ultra 7 270K Plus (Amazon|Newegg) Thermal Grizzly KryoSheet - 44x37 (Amazon|Newegg) 2x 16GB G.Skill Trident Z5 RGB (7200 MT/s in XMP) (Amazon|Newegg) Sabrent Rocket4 Plus 2TB SSD (Amazon) Windows 11 25H2 (Build 26200.8246) AMD shared a press driver based on the recently released Adrenaline 26.5.2 that we were required to use. We now move on to our benchmarks. First up, we have Geekbench AI running on ONNX. For some reason, the 9070 GRE does exceptionally well here in both half-precision (FP16) and single-precision (FP32). It manages to beat the RTX 5070 and RX 9070 non-XT, and is only behind the 9070 XT. Since Geekbench runs in short bursts instead of continuously hammering the graphics card, it seems the GRE's faster boost clocks are helping here. Next up, we move to the UL Procyon AI test suite, starting with the image generation benchmark. We chose the Stable Diffusion XL FP16 test since it is the most intense workload available on Procyon. The Nvidia cards do very well here, as even the 4070 out-muscles AMD's best fairy easily. The positive thing about the GRE is that it gets quite close to the 9070 non-XT in this test; this indicates that the VRAM does not play a very big role here, as SD XL relies on float16 (FP16). So this is something to keep in mind again. If you wish to work with float32 AI workloads, graphics cards with larger than 12 GB buffers would likely emerge as victors. Regardless, the gains are still massive on AMD's 9000 series compared to the 7000 series. Following image generation, we move to the text generation benchmark. This is one test where the 9070 GRE struggled, quite a lot. It seems that the 12 GB VRAM and lower memory bandwidth of the new Radeon 9070 GRE are hurting it quite a bit; the split is massive, especially in a test like Llama2, which packs 13 billion parameters. As such, in all the tests, the 9070 GRE is the slowest of the lot. Next, we tried Blender, and here the AMD GPUs were beaten by Nvidia. Rendering is something the Green team has always had a lead over the Red side, and it has not changed so far. On the positive side, though, the 9070 GRE shows significantly better results than the 7800 XT, which means AMD is on the right path. Catching up to Nvidia, though, will require a lot more effort. And we hope HIP and ROCm can keep improving. Wrapping up AI testing, we measured OpenCL throughput in the Geekbench compute benchmark. The RX 9070 GRE alongside the 9070 did not fare well here at all, even falling behind the 7800 XT. Interestingly, even the RTX 5070 could not beat the 4070 on OpenCL, so perhaps this suggests that OpenCL optimization may not have been a priority for either AMD or Nvidia in the modern era. Conclusion We reached the end of our productivity performance review of the 9070 GRE, and we have to say it's a mixed bag. Unlike the 9070 and 9070 XT, the GRE excels in some areas while losing ground fairly easily in others. Similar to how it happened in gaming, any time the card's memory subsystem gets hammered, it tends to fall behind the others. This was the case with text generation, wherein we saw the VRAM sometimes hit its maximum available 12 GB of usage with larger model sizes. So what do we make of the RX 9070 as a productivity hardware? It can certainly be used, but you have to know it has its limitations. For those looking for a GPU that can deal with more, AMD recently unveiled the Radeon AI PRO R9700, which is essentially a 32 GB refresh of the 9070 XT with some additional workstation-based optimizations. On a similar note, the new Ryzen AI Halo platform is something you can consider if you want to set up a local AI processing station. Considering everything, we rate AMD's Radeon RX 9070 GRE a 7.5 out of 10 for its productivity performance. Price is less of a factor for those looking at productivity cases compared to those considering the GPU for gaming, and as such, we felt it did quite decently on many occasions and can be handy if you need a 12 GB GPU and, for some reason, don't want to get Nvidia. Purchase links: RX 9070 / XT / GRE (Amazon US) As an Amazon Associate, we earn from qualifying purchases.
    • Does anyone here know if these updates are integrated into the UUP dump isos?
    • Motrix Next 3.9.4 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.4 changelog: Motrix Next 3.9.4 promotes the 3.9.4 beta cycle to stable. This release refreshes bundled engine binaries, improves task detail readability and copy actions, expands link handling for magnet and ED2K workflows, polishes responsive navigation and text wrapping, updates browser extension documentation, and refines network preference controls. New Features Task Detail copy actions — Added copyable values for task metadata and reusable render functions for long text fields. Magnet and ED2K lifecycle support — Added task lifecycle handling for magnet and ED2K links. History cleanup for deleted tasks — Deleted tasks can now remove matching history records. User-Agent management — Added user-agent management and improved related network preference controls. Browser extension documentation — Added the Firefox Add-ons link for the Motrix Next extension. Improvements Engine binaries — Updated bundled binaries for supported architectures. Task Detail readability — Long task names, URLs, tracker values, and copyable metadata now render more clearly. Deletion messaging — Refined localized task deletion text for clarity and consistency. Text wrapping — Improved URI input wrapping and task name multiline display. Navigation layout — Improved sub-navigation responsiveness. Disk allocation default — Changed the default file allocation method to trunc. Proxy controls — Improved proxy button styling in network preferences. 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
    • NVIDIA officially supports Ubuntu, as linked above with the GeForce NOW Hands on I did in collaboration with Paul Hill.
    • TO be clear I am not running linux today, however I keep thinking about it. And I want to make sure there are minimal obstacles if I decide to make that switch in the coming months.
  • Recent Achievements

    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      479
    2. 2
      PsYcHoKiLLa
      244
    3. 3
      Steven P.
      72
    4. 4
      FloatingFatMan
      66
    5. 5
      +Edouard
      66
  • Tell a friend

    Love Neowin? Tell a friend!