Announcement

Collapse
No announcement yet.

Mir 0.28 Arrives As A Late Addition To Ubuntu 17.10

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

  • Mir 0.28 Arrives As A Late Addition To Ubuntu 17.10

    Phoronix: Mir 0.28 Arrives As A Late Addition To Ubuntu 17.10

    There's one week to go until the official Ubuntu 17.10 "Artful Aardvark" release and it looks like Mir 0.28 will land in the nick of time...

    http://www.phoronix.com/scan.php?pag...ir-0.28-Artful

  • #2
    exporing -> exploring

    Comment


    • #3
      Originally posted by arnaudv6 View Post
      exporing -> exploring
      Thanks.
      Michael Larabel
      http://www.michaellarabel.com/

      Comment


      • #4
        Wayland was supposed to "replace xorg" 5-10 years ago ?! So much for the speed of development in OSS.

        With the graphical clients implementing most of the GUI artifacts and compositing and kernel drm talking to hardware, why do we even NEED a graphics "server" ? With X11, it was for distribution across network which is no longer of importance, apparently because ALL computing has become distributed across n/w anyway.

        What linux needs is more along the lines of a windows API like MFC (only as analogy)- a system level API that has a default implementation which will render only the text components to the system console by the kernel. The clients , gnome or KDE or whatever, will implement these APIs. Third party apps will target the system level APIs and so work in any DE without rewrite and not have to worry about the DE being used !

        no more xorg, no more wayland, better performance, stability and application feedback. In fact, the kernel can sense a non responsive API call and can take an action such as rebooting the system. Windows 10 now does that when BSOD occurs.

        Comment


        • #5
          Originally posted by mvaar View Post
          Wayland was supposed to "replace xorg" 5-10 years ago ?! So much for the speed of development in OSS.
          According to who? Wayland didn't even exist 10 years ago, and the initial stable release, the point at which real development could even start on toolkits and DEs, was only 5 years ago. No one who knew anything about software development thought that porting away from a system that had been the core of GUI development on the platform for a third of a century would happen quickly.

          Originally posted by mvaar View Post
          With the graphical clients implementing most of the GUI artifacts and compositing and kernel drm talking to hardware, why do we even NEED a graphics "server" ? With X11, it was for distribution across network which is no longer of importance, apparently because ALL computing has become distributed across n/w anyway.

          What linux needs is more along the lines of a windows API like MFC (only as analogy)- a system level API that has a default implementation which will render only the text components to the system console by the kernel. The clients , gnome or KDE or whatever, will implement these APIs. Third party apps will target the system level APIs and so work in any DE without rewrite and not have to worry about the DE being used !
          How, exactly, is what you are describing different from Wayland? Keep in mind that the toolkits need to know the size of the area they can display, and they need to receive mouse and text events, and they need to be able to request minimization, maximization, new sub-windows, etc, and the DE needs to be able to get back the graphics the toolkit wants to render so they can send it to the video card (possibly with modification).
          Last edited by TheBlackCat; 10-12-2017, 12:20 PM.

          Comment


          • #6
            Originally posted by mvaar View Post
            Wayland was supposed to "replace xorg" 5-10 years ago ?! So much for the speed of development in OSS.

            With the graphical clients implementing most of the GUI artifacts and compositing and kernel drm talking to hardware, why do we even NEED a graphics "server" ? With X11, it was for distribution across network which is no longer of importance, apparently because ALL computing has become distributed across n/w anyway.

            What linux needs is more along the lines of a windows API like MFC (only as analogy)- a system level API that has a default implementation which will render only the text components to the system console by the kernel. The clients , gnome or KDE or whatever, will implement these APIs. Third party apps will target the system level APIs and so work in any DE without rewrite and not have to worry about the DE being used !

            no more xorg, no more wayland, better performance, stability and application feedback. In fact, the kernel can sense a non responsive API call and can take an action such as rebooting the system. Windows 10 now does that when BSOD occurs.
            *facepalm* /smh

            When will people start to realize that Wayland is NOT a display server?

            Comment


            • #7
              Originally posted by mvaar View Post
              ... take an action such as rebooting the system. Windows 10 now does that when BSOD occurs.
              That must be an invaluable feature for software conforming to MS' design ethos! https://www.theregister.co.uk/2017/10/12/microsoft_windows_bsod_patch_tuesday/
              ;o)

              Comment

              Working...
              X