Announcement

Collapse
No announcement yet.

Sadly, Two X.Org GSoC Projects Already Failed

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

  • Sadly, Two X.Org GSoC Projects Already Failed

    Phoronix: Sadly, Two X.Org GSoC Projects Already Failed

    Two Google Summer of Code projects for the X.Org Foundation have already failed...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    I guess most of us miss new X.org features like outgoing farts.

    Comment


    • #3
      Outgoing farts?

      Comment


      • #4
        Originally posted by Filiprino View Post
        Outgoing farts?
        Better outgoing than incoming.

        Comment


        • #5
          Originally posted by Filiprino View Post
          Outgoing farts?
          Like this, but with farts.

          Comment


          • #6
            One of the projects that failed was the the lightweight Qt Quick compositing window manager effort.
            Good. Worthless projects deserve to die.

            Comment


            • #7
              Maybe i'm in the minority but I think what X needs is aggressive refactoring and code cleanup in the name of maintainability. Backwards compatibility and network transparency are its strongest assets I think. Or at least, any X replacement should make those features first class citizens. We use network forwarding every day in particular, and on relatively old hardware too. It's usable even on a crappy 100 megabit network...

              Comment


              • #8
                Which was the other one that failed?

                Comment


                • #9
                  Originally posted by 89c51 View Post
                  Which was the other one that failed?
                  Probably tesselation support in mesa, i think i heard that guy went missing without giving notice. Another volunteer has asked to start working on it, hopefully he makes better progress.

                  Comment


                  • #10
                    Originally posted by BradN View Post
                    Maybe i'm in the minority but I think what X needs is aggressive refactoring and code cleanup in the name of maintainability. Backwards compatibility and network transparency are its strongest assets I think. Or at least, any X replacement should make those features first class citizens. We use network forwarding every day in particular, and on relatively old hardware too. It's usable even on a crappy 100 megabit network...
                    Wayland. XWayland will handle backwards compatibility, Wayland can also do networking better than X.
                    All opinions are my own not those of my employer if you know who they are.

                    Comment

                    Working...
                    X