Announcement

Collapse
No announcement yet.

Blue Systems Seeks To Speed Up KF5 Development

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

  • Blue Systems Seeks To Speed Up KF5 Development

    Phoronix: Blue Systems Seeks To Speed Up KF5 Development

    For speeding up the development of KDE Frameworks 5, developers at Blue Systems are near exclusively focusing upon the development of these frameworks for the next three months...

    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
    wasnt that the plan right before the KDE guys did rush into wayland because MIR was announced?

    Comment


    • #3
      Originally posted by k1l_ View Post
      wasnt that the plan right before the KDE guys did rush into wayland because MIR was announced?
      No one "rushed into wayland" because mir was announced. The main difference is news coverage on anything relating to wayland and mir has increased because the "wayland vs mir" drama generates drama and pagehits.

      And there's also lots of development work going on in other parts of the stack (like egl support in mesa) that makes wayland and mir possible. Gnome and KDE have been able to start ramping up their wayland desktop development because these parts of the stack have started maturing enough, not because of anything to do with mir.

      Comment


      • #4
        what always amaze me of this flame wars with mir is that the stupidiest further from the truth crazy pulled of an troll ass arguments reach everyone at lightspeed but actual facts require a bazillion posts to reach ppl, well if you reached this post for some reason before post watch this

        http://www.youtube.com/watch?v=RIctzAQOe44 (is from daniel stone an Xorg developer and works with wayland)

        Comment


        • #5
          Originally posted by k1l_ View Post
          wasnt that the plan right before the KDE guys did rush into wayland because MIR was announced?
          No, KDE (at least Martin for KWin), has been working on Wayland support for awhile before Mir was even announced. It was always planned for KDE 5, too.

          Comment


          • #6
            Originally posted by jrch2k8 View Post
            but actual facts require a bazillion posts to reach ppl, well if you reached this post for some reason before post watch this

            http://www.youtube.com/watch?v=RIctzAQOe44 (is from daniel stone an Xorg developer and works with wayland)
            Thank you for sharing this!
            May I wonder why opensource developers kept this X compatibility for so long, despite all of X did badly?

            Comment


            • #7
              Originally posted by ulenrich View Post
              Thank you for sharing this!
              May I wonder why opensource developers kept this X compatibility for so long, despite all of X did badly?
              Politics thats why Wayland was Developed and is not called X12 (or is it going to be?)

              Comment


              • #8
                Originally posted by LinuxGamer View Post
                Politics thats why Wayland was Developed and is not called X12 (or is it going to be?)

                http://www.x.org/wiki/Development/X12/
                It isn't called X12 because it has essentially nothing in common with X.

                Comment


                • #9
                  Originally posted by LinuxGamer View Post
                  Politics thats why Wayland was Developed and is not called X12 (or is it going to be?)

                  http://www.x.org/wiki/Development/X12/
                  X12 assumes you still have SOMETHING in common with the X API.... Wayland doesn't. Wayland throws the entire book and the bookshelf out the window and says "Okay, Start from scratch. No legacy crap, no assumed backwards compatibility, clean break. Lets get this right this time. No stopgap-measures."

                  Also, X12 was never really coming to pass... That X12 page was basically a whiteboard of ideas of "If we had to do it all over again, knowing what we know now, what would we change from X11?"

                  A lot of those ideas got merged into Wayland, and if some other company wants to make X12 they sure can...but i won't be the X.org devs.
                  All opinions are my own not those of my employer if you know who they are.

                  Comment


                  • #10
                    Originally posted by bakgwailo View Post
                    No, KDE (at least Martin for KWin), has been working on Wayland support for awhile before Mir was even announced.
                    Indeed. Initial steps were taken as early as 2010: http://blog.martin-graesslin.com/blo...#comment-20435
                    Back then KWin was just Martin?s hobby which is one reason why progress was slow (the other was still changing Wayland API).

                    In October 2012 he was hired by Blue Systems to work on KWin full time beginning January 2013. His main goal was to get the Wayland port done: http://blog.martin-graesslin.com/blo.../kwin-hacking/
                    All that happened way before Mir was announced.

                    Btw, I got all that info by simply opening the Wayland Wikipedia article: https://en.wikipedia.org/wiki/Waylan...ol%29#Adoption

                    Comment

                    Working...
                    X