Announcement

Collapse
No announcement yet.

Mir 2.18 Released With Wayland Server-Side Decorations

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

  • #21
    Originally posted by robojerk View Post
    Gnome devs forced the issue on NO SSD in the main Wayland protocol with a NAK.
    That makes no sense. The core Wayland protocol was created without SSD long before GNOME was involved in any way. And if NAK was used against the decoration protocol extension, it couldn't exist in the XDG namespace.

    Meanwhile on every compositor meant to be daily driven SSD is present.
    Except one of the most popular ones.

    Anyway, this is irrelevant. The fact is that Wayland doesn't support SSD without the decoration protocol, which is optional. Therefore a general-purpose Wayland client can't rely on SSD.

    Originally posted by Mez' View Post
    You absolutely nailed what is wrong with people like Mr. Cooper, their closed-mindedness and their will to force everything onto users that are not in demand of those.
    I'm just describing reality, not forcing anything on anybody — I wasn't involved in any of the decisions resulting in this reality. Everybody is free to ignore reality, it tends not to care though.

    Comment


    • #22
      Originally posted by robojerk View Post
      This attitude really bugs me. You're literally saying every developer who currently or wishes to write applications for Linux now needs to accommodate a decision by a single radical group ( Gnome ).
      To come back to this, those unilateral decisions made by Red Hat and derivatives (Gnome being one of them) is slowly driving a lot of companies, developers and distributions away. Finally, and hopefully more and more get away from the locked self-feeding fake community around Red Hat.

      We can think of Unity back then (even though it circled back), and other obvious ones such as System76 or Budgie. And now I just read an article about Wind River eLxr Pro, what their CEO says is another example of Linux actors being fed up with the Red Hat control attempt over the Linux world and their unilateral decisions:

      “We took a hard look at the market and the open source community and we decided to move StarlingX to a Debian-based operating system, and we did that to really align to a more pure open source methodology, so that frankly, our business couldn’t be controlled by another enterprise’s desires.” (the enterprise being Red Hat here)

      “We generally feel, after spending a lot of time studying that part of the industry and the open source community, that continuing down any type of RHEL path inevitably ties you to the whims of Red Hat”

      You can read the whole article here:

      Comment

      Working...
      X