Announcement

Collapse
No announcement yet.

Prolific Red Hat Developer Starts Up "Wayland Itches" Project

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #61
    Originally posted by DanL View Post

    I never claimed that.
    Then stop wasting others' time here, defending Nvidia's foul behavior. Back on topic - compositor developers should not clean up Nvidia's mess. And if users want Linux support, they should use hardware that has it properly.
    Last edited by shmerl; 05-16-2019, 11:25 AM.

    Comment


    • #62
      Originally posted by Weasel View Post
      If you can't trust a specific process then run it as another user. It's basic unix 101.
      Um, that is a workaround, not a real solution. Running a process as a different user has many drawbacks.

      Or: why would an OS force me to do that? Why doesn't an OS isolate user processes properly in the first place? Why are you insisting on a cubersome workaround, instead of just having process isolation work properly?

      Mind you, process isolation features are built both into hardware (page tables denying access to memory of other processes) and software (one process cannot snoop on network of another). Why do CPU and OS manufacturers go into lenghts to isolate processes, if it is so unimportant as you claim?

      It is sad to see an obviously experienced computer user like you not knowing the very basics of modern computing philosophy.
      And by not knowing these very basic issues you put yourself straight back into the league of plain amateurs.

      Untill you retract your statement, your opinions have no importance for me.

      ***
      Also, where are other knowledgeable users of this forum, who should immediately come into my defence after someone posts crap like this. Most people on this forum know that a program which uses too much memory is bad. Where are expert users who know that process isolation is important? Come here and slam down Weasels ridiculous opinions. Show your expertise!
      Last edited by xfcemint; 05-16-2019, 12:25 PM.

      Comment


      • #63
        Originally posted by mroche View Post

        Outside of the Wayland fiasco (EGL vs GBM) can you define NVIDIA’s broken drivers? I haven’t had a problem in several years using their driver for multiple cards on my workstation for computer graphics work (an industry where AMD GPU’s will not be making a surge in any time soon). If you’re referring to their choices of ending support for “older” hardware or refusing to open source the driver, that’s one thing. But it’s also their prerogative as a company to choose what they support and for how long. Doesn’t mean I like it, but I accept that’s the way things are for the time being. As it is on X, the stuff works great.

        Cheers,
        Mike
        Lets, start with xrender acceleration, it's really bad. Nvidia -needed- to redesign their 2d engine support decades ago and never did. By far the very slowest desktop performance of all modern hardware out there. Run any xrender benchmark for proof. The other thing is that twinview is horribly buggy, if you've evr used dual monitors on nVidia then you must be aware of it, everything from horrible unfixable tearing to fullscreen apps can only stretch across all screens. Their multimonitor support is an absolute fucking disaster. And then the most recent fiasco was the whole wayland support thing....It has so many bugs that are -decades- old, it's just stupid....

        Comment


        • #64
          Originally posted by miabrahams View Post

          Nvidia developers have contributed EGLStreams backends for both Mutter and KWin. In what way do they ignore Linux?
          Obviously, it's because -NOBODY- uses EGLstreams, literally it has not even -one- single opensource user. nVidia is completely alone on it. They are the -SOLE- consumer. A pre-existing and far superior solution called GBM already existed, which -literally- everyone else already uses. But using it would have required nVidia to actually implement a proper memory manager, but of course that was too much to ask from nvidia.... They would never consider -really- implementing an actual proper memory management.....
          Last edited by duby229; 05-16-2019, 12:35 PM.

          Comment


          • #65
            Originally posted by shmerl View Post
            Then stop wasting others' time here, defending Nvidia's foul behavior.
            I wasn't defending Nvidia's less than ideal driver situation. I was debunking your bullshit statement(s) that Nvidia ignores Linux and doesn't support it in any way. How about if you stop wasting peoples' time with patently false statements?

            Comment


            • #66
              Originally posted by DanL View Post

              I wasn't defending Nvidia's less than ideal driver situation. I was debunking your bullshit statement(s) that Nvidia ignores Linux and doesn't support it in any way. How about if you stop wasting peoples' time with patently false statements?
              Again, don't waste time please.

              Comment


              • #67
                Xeyes and TWM. Need I say more? Okay, XBill would be nice as well.

                Comment


                • #68
                  Originally posted by ehansin View Post
                  Xeyes and TWM. Need I say more? Okay, XBill would be nice as well.
                  Jokes aside, xeyes may be a very useful tool. Because it doesn't work over Wayland apps, you can use it to check if the selected program is running in native Wayland mode or just through XWayland.
                  This information is important when you creating flatpak packages, because you have to explicitly mark Wayland access in the manifest.
                  http://docs.flatpak.org/en/latest/sa...rd-permissions
                  Relying on the toolkit/graphics library is simple not enough. For example, wxWidgets 3.0/3.1 apps may support native Wayland when using wxGTK3 (Gtk+3), but this is not always the case, because e.g. wxGLCanvas doesn't work with Wayland yet.
                  And when we are talking about binaries, this is even less obvious. The fact that the game uses SDL2, doesn't have to mean that it will work in native Wayland mode. The same applies to the Qt5 apps.

                  Comment


                  • #69
                    Originally posted by shmerl View Post
                    Again, don't waste time please.
                    The truth is never a waste of time. Stop wasting time with lies.
                    Last edited by DanL; 05-17-2019, 05:24 AM.

                    Comment


                    • #70
                      By the way, I've been a little snarky here lately. I did find this on Xeyes, yes more than fiun and games:

                      https://unix.stackexchange.com/quest...rpose-of-xeyes

                      In the end, I am pulling for Wayland though, coming from a non-expert.

                      Comment

                      Working...
                      X