Announcement

Collapse
No announcement yet.

Qt5's Linux Requirements Cause Problems

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

  • All I've learned from this thread is to never have anything to do with this "developer", his friends, or any of his projects. You can be doing the greatest work mankind has ever seen but if you act like this no one will care.

    Comment


    • Originally posted by Amaranth View Post
      All I've learned from this thread is to never have anything to do with this "developer", his friends, or any of his projects. You can be doing the greatest work mankind has ever seen but if you act like this no one will care.
      Zester dared us in another post to google him to prove that he is a legitimate developer. Well, I did and found a forum post by him where he confessed that he is a bipolar schizophrenic or in a colloquial term: crazy.

      When he wrote his “essay”/rant, he was probably off his meds or whatever because it is completely beside the point. He bashes Qt because the proprietary NVidia driver is currently missing features. He rants because XCB and GLX in combination don't support accelerated rendering on NVidia.
      It is far from news that use of GLX is not recommended and developers are advised to use EGL instead. For NVidia EGL is currently only supported on Tegra but according to a comment on https://www.youtube.com/watch?v=LesAb4sTXgA (roughly around 8–10min) by the attending NVidia guy, EGL support for NVidia's desktop drivers is in the works.
      EGL works just fine on all Mesa-based drivers, including the free Radeon drivers and Nouveau.

      Comment


      • It has been around for a long time and is a better way to get to X11 compared to using Xlib.

        Comment


        • Some stupid f*ck thought he knows about X11 better than Alan Coopersmith

          So we have this bullsh*t in the web

          Comment


          • Well, he seems to actually know what he's talking about. The problem is that he's too radical about it and the problem might not be such a serious issue as he makes it out to be.

            Comment


            • Problem is that there's no issue at all. XCB is a core part of modern X11 ecosystem. Any X application uses it either through Xlib API or directly, and direct usage, exposing asynchronous nature of X11, can help to reduce latencies [1].

              he seems to actually know what he's talking about
              If he really knows, he intentionally spreads the FUD. XCB is not "crippled" neither is it "wrapper" for any "higher level API". It's true that it does not cover all Xlib functionality, but:
              1. Using XCB does NOT imply not using Xlib. They are fully interoperable and can be used together (as Qt developers do, and they do use GLX). XCB needs to be used where it can bring speed up
              2. More APIs become available in XCB with each new release of X.org

              And, of course, XCB has nothing to do with KDE and NVidia breakages.

              [1] https://blogs.oracle.com/alanc/entry...wininfo_to_xcb

              Comment

              Working...
              X