Announcement

Collapse
No announcement yet.

Following Mir 1.0, Developers Encouraged To Target Wayland Instead Of Mir Client API

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

  • Following Mir 1.0, Developers Encouraged To Target Wayland Instead Of Mir Client API

    Phoronix: Following Mir 1.0, Developers Encouraged To Target Wayland Instead Of Mir Client API

    Last week Canonical developers released Mir 1.0 for the "next-generation of graphical solutions" particularly for IoT device makers. Mir lead developer Alan Griffiths published a bit of a redux today now with the 1.0 release out the door...

    http://www.phoronix.com/scan.php?pag...r-1.0-One-Week

  • #2
    Michael This is the time where you should begin merging the "Mir" and "Wayland" sections in Phoronix forums.

    Comment


    • #3
      Originally posted by tildearrow View Post
      Michael This is the time where you should begin merging the "Mir" and "Wayland" sections in Phoronix forums.
      Good point.... I will probably do it this weekend when having a beer. As I learned when recently merging the AMD Linux forums, need to click each thread manually to move... a lot of redundant clicking without bothering to look into the vBulletin database structures and bothering with that.
      Michael Larabel
      http://www.michaellarabel.com/

      Comment


      • #4
        Originally posted by tildearrow View Post
        Michael This is the time where you should begin merging the "Mir" and "Wayland" sections in Phoronix forums.
        No he shouldn't, if only because the Mir client API still exists. Which means that there is still a kind of split between Mir: the display server with its own protocol and API vs Mir: the Wayland compositor.

        Comment


        • #5
          Good.

          Comment


          • #6
            So Mir turned into just another Wayland compositor? Or is there more to it?

            Comment


            • #7
              Originally posted by Aleksei View Post
              So Mir turned into just another Wayland compositor? Or is there more to it?
              Just typical and pathetically done vaporware by Canonical...

              Comment


              • #8
                Originally posted by Sonadow View Post

                No he shouldn't, if only because the Mir client API still exists. Which means that there is still a kind of split between Mir: the display server with its own protocol and API vs Mir: the Wayland compositor.
                Why he shouldn't? Even Mir developers recommends using Wayland API instead of Mir API. So what's the point of using Mir API now? Without this Mir isn't very different to Wayland compositors.

                Comment


                • #9
                  dragon321 also , even if there was some edge case where utilizing the mir protocol would be truly beneficial . it would not mean a whole section of a forum should be dedicated to it

                  Comment


                  • #10
                    Originally posted by timofonic View Post

                    Just typical and pathetically done vaporware by Canonical...
                    "You keep using vaporware. I do not think it means what you think it means"

                    Comment

                    Working...
                    X