Announcement

Collapse
No announcement yet.

Ubuntu Allegedly To Have Its Own X, Wayland Alternative

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

  • #91
    Originally posted by Ericg View Post
    We may finally get Windows RDP quality
    That bad, eh? Shit.

    Comment


    • #92
      Originally posted by KellyClowers View Post
      That bad, eh? Shit.
      Compared to what? VNC? No, I'll take RDP over VNC any day.
      All opinions are my own not those of my employer if you know who they are.

      Comment


      • #93
        Originally posted by Ericg View Post
        Compared to what? VNC? No, I'll take RDP over VNC any day.
        The worst was whatever Citrix ICA used. I think they rolled their own scheme. That thing was unusable.

        Comment


        • #94
          Originally posted by johnc View Post
          The worst was whatever Citrix ICA used. I think they rolled their own scheme. That thing was unusable.
          Never used it, probably for the better lol
          All opinions are my own not those of my employer if you know who they are.

          Comment


          • #95
            Originally posted by uid313 View Post
            Then so be it.
            Just strip out everything that can be stripped out, and if all GTK and Qt applications still work, and almost nothing of X is left, then that is just good, right?

            Then the codebase will be smaller, it will be easier to maintain, quicker to compile, easier to fix bugs, and everything will be great.
            There's one big impediment to X11-Light that does shout back to my issue of design it out, spec it out, write it out. And Daniel hit on it during the talk, X has 3 API's for input...and they are all inter-dependent on eachother. It frightens me to think about other spots in the Xorg stack where we have a similar issue where API's are inter-dependent on eachother AND redundant of eachother. So just "taking out the old stuff" does not necessarily work. Certain parts of the stack WOULD have to be redesigned and rewritten to make sure the code is clean at the end.
            All opinions are my own not those of my employer if you know who they are.

            Comment


            • #96
              Originally posted by Ericg View Post
              <...> So just "taking out the old stuff" does not necessarily work. Certain parts of the stack WOULD have to be redesigned and rewritten to make sure the code is clean at the end.
              exactly

              it wouldnt work nor be enough, when looking at the at the "X12" proposal (or the "Why X is not our ideal window system" paper), you realize that certain aspects of X are "less than ideal" (when not straight out broken) at the core protocol level (like the 16 bit unsigned dimension / 16 bit signed coordinate model allowing for 32K x 32K pixmaps with 3/4 of their surface unaddressable - or the drag and drop and clipboard model..)
              and that if you want a sane and modern infrastructure (especially, one accomodating GPU's as first class citizens) what remains after taking parts away also need to undergo significant rethinking ( at which point it becomes something which is not X any more...)

              Comment


              • #97
                I got this thread when looking for Xorg & Wayland alternatives (first page of Google). I'm guessing this turned out to be a dead end?

                Comment


                • #98
                  Originally posted by make_adobe_on_Linux! View Post
                  I got this thread when looking for Xorg & Wayland alternatives (first page of Google). I'm guessing this turned out to be a dead end?
                  In the early times there was the XFree86 project which implemented the X11 window protocol. It was used on many Unixes, it was used on Linux, BSD, and such, I think AIX, Solaris, HP-UX, etc. Due to licensing changing, XFree86 got forked and replaced by the X.Org Window System, main part being called the X.org Server which also implements the X11 window protocol.
                  It was and is extensively used, and X11 have been around for decades.
                  The X11 protocol was designed in old times when different things were expected from computers, as such it manages much more than just displaying pixels, it also deals with fonts, drawing shapes, and much more.
                  There also existed some used proprietary implementations of the X11 protocol, some claiming better performance by forgoing the client/server architecture.

                  Over 20 years ago, Sun also tried their own stuff with SunView and NeWS. NeWS was on PostScript. I think maybe Apple might have gone with the PostScript approach too.

                  X is still popular today, and the most widely used even today. Wayland is gaining traction. Wayland uses a different approach and treats everything as frames. It is a much simpler design and touts security benefits.

                  Canonical was pushing for their own thing called Mir, but they eventually abandoned that approach and rewrite Mir as a Wayland compositor instead.

                  There have been some small scales at putting up alternatives against the X Window System such as the Y Window System, but nothing have gained much traction. Some embedded devices used DirectFB instead of X.Org Server.

                  Here is a very good article about alternatives to X and Wayland.

                  Comment

                  Working...
                  X