I've played 3D games just fine under X, run VR with the Valve Index while X was up, can generally work fine with international text and image pasting, etc, etc. I deeply value the ability to swap out to different window managers, although fvwm has worked well for me for a good while (after having gone through about 10 others). I value this because anyone designing how the window environment should work is very, very likely to break something fundamental, and often utterly fail to understand why it's a problem. I use remote X windows over TCP ** ALL THE TIME ** even just between computers at home. I even use features like Emacs's ability to open windows on multiple X servers at once.

X does have its flaws, but the only one that's every blocked me is the fact that the library and protocol make it seemingly impossible to cleanly forward non-faked X events to a specific X window including the pointer coördinates without involving the entire bloody X display structure - meaning that managing a bunch of interactive textures texturing 3D objects requires screwing around with a hidden X display and popping a specific window to the top of the stack to map coörds display-wide, which is mind-bogglingly inelegant. Hopefully I just missed something...

(For this paragraph, my information is from a few years back, so let me know if Wayland has solved any of these below...) However, Wayland's pretty useless for many things given its:
* general lack of any way to run X programs (individuals windows) on the same host,
* a way emulate at least an X server for X programs to use (something I've written myself before, although I modified my X server to use an OpenGL texture format for the X server display buffer so I could map a display onto any object)
* a way to run a program on one host that displays its windows to a different host - this ability is CRUCIAL in many applications
* (rare) a way to run a program that can display windows on several hosts simultaneously (like I said, even Emacs supports this... though the emacs proc will die if any of the X servers it's connected to do, which is a bit fragile)

X's core win is that it is fundamentally a network protocol, while gamers want the supposedly opposed core win of optimized local hardware use. But this don't have to conflict - you can see how OpenGL was aiding the joint effort with display lists, which allows your vector info to be pushed to a local OR remote display (using GLX) and then call it on either by the list's identifier. Still, this doesn't scale well on slow networks with scenes with lots of dynamic objects.

What would be ideal is to have full local hardware support, and for the remote display to be able to use *either* a high-level protocol (as was GLX for OpenGL) **or** some per-window VNC-style fallback, depending on the bandwidth. And the graphics-level protocol can be faster than one thinks - remote X in many applications was slow because Xlib was based on serialized events, where the xc library parallelized event handling, making them shockingly faster.

There is a deeper problem though, that both Wayland and X fail at: I want to be able to keep up sets of 2D (for example) windows for *all* of the stuff I work on, spread across all my hosts at home and whatever I'm using for work, in one big, shared environment - and I want that set up to be be resilient in the face of any host crashing, so that I can connect to that environment from any host, or reconnect if the one in front of me died, and still have most of it reappear when I log back in. Until we have something that gives that level of ease of use, we're still basically just using toys, regardless of how good the hardware acceleration is.

You *can* disable Firefox updates at the system level via root access, but a user doesn't have control, and the update process with all the problems combined is just as much of a blocker as waiting for some Microsoft box doing an update for 20 minutes before letting you start a presentation, or insisting on updating when you want to shut down before a power outage, despite telling you not to interrupt power. The attitude, and its effects, are both serious problems.

I use several independent Firefoxes with different plugins and objectives, especially to segregate my wander-the-web usage from my financial-institution usage. I'm also a heavy virtual desktop user, with a 3x3 grid of virtual screens, and scores of Firefox windows with about 700 tabs total on a typical day.

It used to be, back when Session Manager still worked (before the Firefox API changed), that in the rare case of a crash (every few weeks), and when I still used *one* Firefox with a couple hundred open tabs and windows offscreen and all, that I could just restart, and *poof*, everthing ended up back on the right virtual (off)screen, and life continued with barely a pause.

No longer. Firefox has turned into garbage despite still outperforming Chrome when tons of tabs and windows are involved..

Firefox now:
* has separate processes for content that crash once or more daily, and often have to killed manually just to cope with the massive memory they consume
* switching tabs often forces one to watch a spinner while waiting for a rerender
* wastes fantastic amounts of bandwidth in disk I/O even when the user is away
* wastes huge amounts of CPU time, even when the screen is locked - and setting your lockscreen to pause Firefox while screenlocked causes a new problem
* resuming a suspended Firefox makes it do ALL of the stupid I/O wasting updates it missed at once - easily locking up a Threadripper for 15 to 20 minutes. The only workaround is to kill Firefox and restart to skip that intervals I/O binge
* of course, now when I restart Firefox, none of the windows put themselves back on the offscreen virtual desktops anymore - so more time is lost replacing them
* Firefox now forces upgrades, usually forcing the user to suicide the session, if Firefox doesn't just outright implode
* Frequently, in every window where the upgrade-notice overrides the visible tab, the state of that tab is lost - so when you restart, every webpage you were actually looking at is gone
* Firefox's replacement for the lost Session Manager is garbage, storing only one session back and forcing arcane file operations to get to an earlier one - if you don't careful restore the prior session, the current empty one becomes the checkpoint for restore
* New windows often grab text input, even when not under the mouse, still keystrokes from wherever you were actually typing
* Randomly decides it wants to "refresh" your experience, creating new profiles with modified names, and often failing to copy anything from the profile that had history and so on
* Usually fails to restart itself when it says it will
* For ages, "file:///" -prefixed URLs would crash it, but this *might* have been fixed
* None of the "about:config" items are documented in the browser, a congenital design defect
* Per-bookmark notes were ripped out of the database for absolutely no reason

And lastly, one STILL can't get any information on which tab is eating all the CPU time, although *today*, for the first time, Firefox popped up a notice about high load from a *named* tab, so perhaps this will finally improve.

Chrome is still useless to me, but I have been pleased with the Vivaldi browser, which I just discovered a few weeks ago.

Let's see, my experience with Firefox currently is basically

* Sleep firefox when I screenlock to keep JavaScript from eating my CPU cores all night
* When I resume it later, Firefox ties up the entire computer in disk I/O for up to 20 minutes updating files on disk (seriously, it can just write the LAST state to disk, instead of the thousands of intermediate ones) - revealing how much it thrashes the disk all the time (and killing SSDs) when it isn't asleep
* After decades, I still can't pinpoint *which* tab is eating up all the CPU and RAM, so I can't kill the offending tab (out of a 100+). But that's okay if I managed to kill the right Content proc before the next thing happens...
* Firefox will, without warning (including when RAM isn't full) have a Content proc die, replace all the affected, visible tabs with some noise about Reloading (in 20+ windows), then often fail to reload and insist "Sorry. We just need to do one small thing to keep going." THIS IS A HARD CRASH, and claim it'll restart, which is fails to do (under linux at least), and then when restarted, 90% of the tabs that the Sorry appeared in failed to reload - so the majority of the most important tabs are unrecoverable other than by grovelling through the history.
* Part of this is an offensive determination to do background updates despite that sessions will be impacted

Plus other braindamage like:

* 100% of the about:config options have near zero documentation. All of them should be documented
* I can't rearrange the toolbars without hacking the chrome css
* Per-bookmarks notes were ripped out for no sane reason
* The ability to set the default URL for new tabs was torn out
* file:/// ... URLs often fail
* It used to randomly decide it had to create a new profile and then copy nothing from the old one into it
* Thinking Firefox's replacement for the brilliant Session Manager addon is even remotely comparable. Seriously, if you had a bunch of tabs, FF dies, and you restart and mistakenly quit before reloading the last session - the only way to get to the last (okay, now pre-last) session is to move session files around in some arcane way. Otherwise all your 100+ tabs and those windows are just... gone. Probably because of some spontaneous crash caused by an update.

And sure, there are other issues. Crashing the browser is especially bad on a virtual window manager (fvwm, tvwm, etc), where I get to watch all the windows reappear in the right places in the overview widget, then get yanked forcibly onto the current screen from the eight others. That might not be FF's fault though.

Firefox currently has (just barely) enough going for it that I STILL USE IT DESPITE EVERYTHING, like:

* The ability to control the number of content procs used lets me keep my 5 running profiles (partly to deal with the inability to put windows back in the right virtual desktop areas) running with about 100 tabs each WITHOUT melting my computer in heat death. Chrome utterly fails here.
* The bookmark sharing is super useful, although I'd like to be able to host the server-side of this on one of my own servers for privacy reasons
* With the toolbars all on and the Ubuntu Unity toolbar braindamage disabled, the UI is very nice on a large screen (having to go to the top of the monitory to hit menus on a 65" monitor would be stupid).
* I like the developer tools menu and what it provides
* Outside of the issues above, Firefox does what it should 99% of the time (for me). Which is impressive considering the complexity of browsers.

But with all this, they want a UI refresh? *facepalm*

I know, I should be including all the related tickets for all the issues above, but this seems a lot more like a philosophical problem in the heads of some subset of the devs than just an issue in reporting.

I use this:
        browser.fixup.alternate.enabled: False (default is True)
        keyword.enabled: False (default is True)

There's an Elvengear /dev/girl T-shirt I'd been thinking of giving a girlfriend (who hated being objectified and wasn't a big Linux fan) - but NOW, the perfect excuse! Literally true! ... assuming you can run LInux on her. :-)

"Welcometo the future. A pity you are too late to stop it. No one can stop me now!"

Well... optically would probably could make it focussing at a far distance while looking at a converging at a nearer distance (flipped from above), but the point is that no accomodation (focus change) is required for for 3D screens, and that could impact kids' brains learning how to integrate focus into the set of cues used for depth perception.

Othewise said, Anses is an idiot in this area and has no idea what the real issue is, though there might be one: "three-dimensional effect requires the eyes to look at images in two different places at the same time before the brain translates it as one image" is flawed in almost every respect except for "three-dimensional" and "eyes". He shouldn't be involved in policy in this area.

The key point is whether the end user can install a signature for his *own* operating system in his own hardware, and then secure boot linux. Nothing in the document suggests this is possible (and MS slams linux as an older operating system for "enthusiasts", but that isn't really the point)

Geez, use metric already:

labrat@yggdrasil:~$ units
2411 units, 71 prefixes, 33 nonlinear units
You have: 498438559990 kilograms
You want: petagrams
        * 0.49843856
        / 2.0062653

1/2 petagram. Easy.

Newflash^2: Lag is explicitly network lag for any online game unless otherwise specified, since online lag completely overshadows almost all other types of local-to-host delays. If you're talking about a solo, unnetworked game, sure, "lag" might mean something else.

Now, of course, if you're talking to complete duffers, who will complain that their computer's slow when a remote webserver is slow to respond, and that the Internet is slow while their disk drive I/O light is solid on, and in almost all other ways have no idea what causes delays, then sure, "lag" could mean anything.