Recommended Posts

I HATE the phrase "less is more" with a vengeance ... and anymore that uses it I'll always dismiss as pretentious prats.

Less is less, not more. A more appropriate term for this stupid trend of gratuitously hiding/removing important GUI

elements is "dumbing down". Google started it with Chrome, why others are copying it, I cannot understand.

OK ... those of you with these browser layouts with certain elements missing, can you tell me what size your display

is and what resolution you have it set as? Since standard computer displays and screen resolutions are gradually

getting larger, the argument about simplified GUI's saving screen space is a very poor argument.

If we were all stuck at resolutions no higher than 800x600, it would be understandable to want to hide elements

of the GUI until we need them, but if for example, you have a decent sized monitor set to a high resolution,

there is really no need whatsoever to hide any part of your browser GUI.

Even at a fairly bog standard resolution of 1024x768, over-simplified browser GUI layouts are a complete folly.

If these cutdown GUI layouts were only optional, and not the default, I'd have far less of an issue with them.

  • Like 2

Going from the previous post,

If anything the Firefox4 button menu is a really bad idea.

I cannot find anything that way.

It is like the Chrome wrench button.

FF4 Button // Chrome Wrench: Click Button -> Slowly Find Option -> (Optional) Find Sub-Option -> Click on Option

Office 2k7+ / W7 WordPad: Click Button -> Quickly Find Option -> (Optional) Quickly Find Sub-Option -> Click on Option

Classic: Medium (or slow with Open-Source stuff like LibreOffice) Speed Find Option -> (Optional) Find Sub-Option -> Click on Option

Going from the previous post,

If anything the Firefox4 button menu is a really bad idea.

I cannot find anything that way.

It is like the Chrome wrench button.

FF4 Button // Chrome Wrench: Click Button -> Slowly Find Option -> (Optional) Find Sub-Option -> Click on Option

Office 2k7+ / W7 WordPad: Click Button -> Quickly Find Option -> (Optional) Quickly Find Sub-Option -> Click on Option

Classic: Medium (or slow with Open-Source stuff like LibreOffice) Speed Find Option -> (Optional) Find Sub-Option -> Click on Option

That is why you can customize it anyway you want. :)

Enough already of these browser layouts that look best suited for public internet kiosks and/or mobile internet devices!

Too many redundant buttons.

Menu stuff goes under the Firefox menu (or press ALT to unhide the menu bar that I rarely access).

Bookmarks are on my context menu.

Tools are under a tool menu on my context menu.

I HATE the phrase "less is more" with a vengeance ... and anymore that uses it I'll always dismiss as pretentious prats.

Less is less, not more. A more appropriate term for this stupid trend of gratuitously hiding/removing important GUI

elements is "dumbing down". Google started it with Chrome, why others are copying it, I cannot understand.

Agreed, less is not more. However, more is not more either. The goal is to remove bloat from the interface. For example, you have four buttons for DownThemAll, when the single button "DownThemAll!..." combines the function of all four of those buttons into a single dropdown menu.

It all comes down to personal preference. There is no right or "default" way of doing things. If you like your browser like that, that's fine. But the best way of doing things is simply your own opinion.

I also HATE the fad of hiding the url on the bottom it's very stupid how some people want to completely disable it at all time (even while hovering or loading) makes it sooo easy to get infected. there's tons of people that did this and regret it. LOL.

here's an example:

[user1]

I'm having a problem with windows 7 [insert problem description here]

[user2]

click on this link from microsoft's site to download this update that should fix your problem

user 1 get's infected becuase they trusted that user2 would give them a legit MS Update link and they get infected becuase they weren't aware of the true URL of the site. They trusted that it came from microsoft's site.

and what's really bad is some people want the browser to be shipped with that URL on the bottom to be completely disabled and no hover URL by default. and guess who doesn't customize stuff right away? the same people who click those links.

stupid stupid fad.

Stupid people will recklessly click links whether it is displayed or not.

I HATE the phrase "less is more" with a vengeance ... and anymore that uses it I'll always dismiss as pretentious prats.

Less is less, not more. A more appropriate term for this stupid trend of gratuitously hiding/removing important GUI

elements is "dumbing down". Google started it with Chrome, why others are copying it, I cannot understand.

OK ... those of you with these browser layouts with certain elements missing, can you tell me what size your display

is and what resolution you have it set as? Since standard computer displays and screen resolutions are gradually

getting larger, the argument about simplified GUI's saving screen space is a very poor argument.

If we were all stuck at resolutions no higher than 800x600, it would be understandable to want to hide elements

of the GUI until we need them, but if for example, you have a decent sized monitor set to a high resolution,

there is really no need whatsoever to hide any part of your browser GUI.

Even at a fairly bog standard resolution of 1024x768, over-simplified browser GUI layouts are a complete folly.

If these cutdown GUI layouts were only optional, and not the default, I'd have far less of an issue with them.

If you are using Firefox and Opera (and maybe IE9 too, but I haven't really tried bringing it back to the old UI), then these are optional. As others said, it is redundant:

A user may disable the bookmarks bar and simply use the bookmarks button (with dropdown arrow) for Fx.

dTa has its buttons, but it's present on the context menu and under tools options as well. The same goes for most addons.

The hidden menu bar can easily be activated by pressing Alt key.

Just because you have a place for everything does not mean you have to show everything, including stuffs that are redundant and buttons you do not use. It's about how you use those options, not how you chose to show (or hide) it.

For Chrome, you all guys can correct me here, but I think they just created a browser used simply for...browsing. User opens up Chrome, browses, closes it. Bookmarks bar is present and addon buttons are in its place. They focus more on the speed and simplicity of the browser resulting to a simpler UI.

I HATE the phrase "less is more" with a vengeance ... and anymore that uses it I'll always dismiss as pretentious prats.

Less is less, not more. A more appropriate term for this stupid trend of gratuitously hiding/removing important GUI

elements is "dumbing down". Google started it with Chrome, why others are copying it, I cannot understand.

OK ... those of you with these browser layouts with certain elements missing, can you tell me what size your display

is and what resolution you have it set as? Since standard computer displays and screen resolutions are gradually

getting larger, the argument about simplified GUI's saving screen space is a very poor argument.

If we were all stuck at resolutions no higher than 800x600, it would be understandable to want to hide elements

of the GUI until we need them, but if for example, you have a decent sized monitor set to a high resolution,

there is really no need whatsoever to hide any part of your browser GUI.

Even at a fairly bog standard resolution of 1024x768, over-simplified browser GUI layouts are a complete folly.

If these cutdown GUI layouts were only optional, and not the default, I'd have far less of an issue with them.

And no one is forcing you to use your browser like that. It all comes down to personal preference.

You don't like the minimalistic look? That's fantastic! I do, however.

Doesn't mean I'm right and you're wrong and it doesn't mean you're right and I'm wrong. Where we differ is I don't come on here telling everyone who does like a certain aesthetic that they're choice is wrong like you did.

My initial reply was a quick reaction to you stating that anyone who likes the minimalistic approach is wrong, which again, is just an opinion.

Too many redundant buttons.

A place for everything, and everything in it's place.

Menu stuff goes under the Firefox menu (or press ALT to unhide the menu bar that I rarely access).

Bookmarks are on my context menu.

Tools are under a tool menu on my context menu.

In other words, needlessly hiding stuff behind obscure buttons and dropdowns. I like to have everything within easy

reach, including any menu items that I might not use as often as others. If anything, I'm a browser traditionalist,

with a strong preference towards having as close to maximum functionality as realistically possible.

Having bookmarks hidden behind a context menu causes unnecessary extra mouse clicks and navigation, whereas

all of my most frequently accessed Bookmarks are right there in front of me ready and waiting within neatly titled

folders along my Bookmarks bar. Any other bookmarks I don't access so often, are either relegated to the folder

titled "misc", or are discarded altogether when they've become no longer relevant, or effectively dead links.

Tools are under the appropriately titled Tools menu where it should be ... on the Menu bar.

All of these over simplified browser GUI layouts that have suddenly become so freakishly popular over the last

year or so, seem to be little more than style over functionality. At least Firefox 4.x, Opera 11.x and Safari 5.x,

although dumbed down by default, are easily customisable to restore gratuitously hidden elements.

Some say having fewer GUI elements help the novice users, but that isn't necessarily the case. Recently, a friend

who I'd previously set up Firefox 3.x, and is very much a novice user, asked me why "a load of stuff has gone

from my Firefox" ... he'd been auto upgraded to Firefox 4, and he hated the new default cutdown GUI.

As for GUI bloat, lest we forget ... NeoPlanet ... a seriously horrific 3rd party front-end for Internet Explorer . . .

NeoPlanet.png

:no: :blink: :o :( :cry:

:x

also the "mystery meat" navigation trend just makes stuff harder, not easier for n00bs.

and also I can compare the same to media players. I hate going back and using windows media player when I'm on another person's system. I feel like so much stuff is missing compared to media jukebox.

the new WMP interface is actually harder, not easier to use and it has less features. it's harder for users to adjust EQ settings. it takes 5 steps vs the 3 in prev. versions. "all in the name of minimalism"

when you go from a powerful Firefox 4 or 3.6.x install then use IE9 it feels like going from a ferrari to a vw beetle.

In other words, needlessly hiding stuff behind obscure buttons and dropdowns. I like to have everything within easy

reach, including any menu items that I might not use as often as others.

How is it obscure? I customized the interface so I know where everything is at. The bookmarks are more convenient than some bar with buttons because I can access my bookmarks (which are very organized) without having to move my mouse cursor across the screen. I right-click anywhere and I have access to my bookmarks. Beyond bookmarks, URL entry, page history (controlled by mouse), and tabs, there is nothing else that I do often enough to warrant a dedicated button.

unledrr.png

This is exactly what I mean. That looks like it's been taken from a very high resolution screen, so there is absolutely no need or

excuse whatsover to have dumbed down the browser so much, you're left with is what amounts to a nearly non existant GUI!

Why not go the whole hog ... get rid of the Back/Forward buttons, and the Location Bar, so you have a browser with no GUI

at all?!? That extreme lack of GUI elements really should only ever be used on a device with a low res display of 800x600

or less, such as a smartphone or similar, not on a high resolution desktop display or a decent sized laptop.

Oh well ... if a smart, well organised, professional browser layout, for true power users, with all standard GUI elements intact,

such as my SeaMonkey layout shown earlier, is quite obviously too much for some people to handle ... who am I to argue?

To partially quote cork1958 in the comments for the Neowin article on SeaMonkey 2.1 RC2 . . .

Straight forward and gets the job done.

[/quote']

Really can't argue with that, personally ... although I'm sure some other people around here would.

If these cutdown GUI layouts were only optional, and not the default, I'd have far less of an issue with them.

As your screenshot clearly shows they're optional, personally I don't see a reason to have a menu bar always present, since I can't even remember the last time I required access to it ,so I can't see a reason for it to steal screen space from the main focus of browsing - the websites. With mouse gestures in Opera I barely even use the back / forward buttons. And please stop calling simplifying GUIs "dumb" just makes you sound ignorant.

Oh well ... if a smart, well organised, professional browser layout, for true power users, with all standard GUI elements intact,

such as my SeaMonkey layout shown earlier, is quite obviously too much for some people to handle ... who am I to argue?

Yeah, yeah we get it, you're smart and everyone else is dumb :no:

Anyway here's mine ;) :

225219645.jpg

Everyone has his own "Standards". The great advantage Fx gives you is that you've the ability/options to do whatever you want.

These are my "Standards". I don't need more, I don't need less:

icVeOW.png

Fx 7?1 - 24 Inches Monitor 1920x1080. I don't give a damn about more space ( space stealing etc crappy thoughts don't count on me ). It's just what I like to see when I open my browser and of course the convenience which gives me depending on what I need.

This is exactly what I mean. That looks like it's been taken from a very high resolution screen, so there is absolutely no need or

excuse whatsover to have dumbed down the browser so much, you're left with is what amounts to a nearly non existant GUI!

Why not go the whole hog ... get rid of the Back/Forward buttons, and the Location Bar, so you have a browser with no GUI

at all?!? That extreme lack of GUI elements really should only ever be used on a device with a low res display of 800x600

or less, such as a smartphone or similar, not on a high resolution desktop display or a decent sized laptop.

Oh well ... if a smart, well organised, professional browser layout, for true power users, with all standard GUI elements intact,

such as my SeaMonkey layout shown earlier, is quite obviously too much for some people to handle ... who am I to argue?

A true power user would know the kind of layout that will suit his needs. He'll know which bars or buttons to remove and how it affects how he uses his browser. Again, just because you can, doesn't mean you should and just because everything has a place, does not mean you need to place everything.

Why not go the whole hog ... get rid of the Back/Forward buttons, and the Location Bar, so you have a browser with no GUI

at all?!?

Well if you're going to that kind of logic, then why not:

ie-toolbar-bloat.jpg

And I'm off. The topic about whether you'll go with the old school layout or the new 'dumbed down' layout should not reach more than one page unless it is on its own thread. :)

Edit: The picture above was taken from the Google Toolbar 7 thread

This is exactly what I mean. That looks like it's been taken from a very high resolution screen, so there is absolutely no need or

excuse whatsover to have dumbed down the browser so much, you're left with is what amounts to a nearly non existant GUI!

Why not go the whole hog ... get rid of the Back/Forward buttons, and the Location Bar, so you have a browser with no GUI

at all?!? That extreme lack of GUI elements really should only ever be used on a device with a low res display of 800x600

or less, such as a smartphone or similar, not on a high resolution desktop display or a decent sized laptop.

Oh well ... if a smart, well organised, professional browser layout, for true power users, with all standard GUI elements intact,

such as my SeaMonkey layout shown earlier, is quite obviously too much for some people to handle ... who am I to argue?

To partially quote cork1958 in the comments for the Neowin article on SeaMonkey 2.1 RC2 . . .

Really can't argue with that, personally ... although I'm sure some other people around here would.

If we don't use those elements regularly what's the point in them being there? Simplified is not dumbed down. I don't use the menu bar so I don't need it taking up vertical screen space, although it's there if/when I ever need to be. I don't use the bookmarks bar so I don't need it taking up vertical screen space. It doesn't matter how big my monitor is (what a silly argument) I want to see as much of a webpage as I can and I don't need anyone telling me I'm stupid for preferring it this way. After all everything you said is your opinion on your personal preferences.

Anyways... you seem to be completely ignoring all the valid points every one is making so I won't continue.

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

    • No registered users viewing this page.
  • 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!