Announcement

Collapse
No announcement yet.

Wayland 1.18 Alpha Released With Meson Support, Connection Sharing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
    uid313
    Senior Member

  • uid313
    replied
    Originally posted by Britoid View Post

    Rust would make no difference here.

    You know what happens if X.org crashes? Your applications go down. And with X being X, you'll probably get a frozen display and input.

    Wayland display servers are much simpler than the X servers they're replacing, so the area for potential bugs is reduced.
    But Rust eliminates entire classes of bugs. No more null references, no more race conditions, concurrency issues, etc.

    Yes, if X.Org crashes then applications go down, but if only the compositor or window manager running on X crashes then nothing everything is lost, but with Wayland then the compositor is the window manager which is the display manager so if that crashes, it all does down.

    Leave a comment:

  • Britoid
    Senior Member

  • Britoid
    replied
    Originally posted by uid313 View Post

    I just don't want my compositor to crash because unlike X.Org Server where when the compositor or window manager crashed it would just gracefully restart with all applications intact, when a Wayland compositor crashes everything goes down. I think.
    Rust would make no difference here.

    You know what happens if X.org crashes? Your applications go down. And with X being X, you'll probably get a frozen display and input.

    Wayland display servers are much simpler than the X servers they're replacing, so the area for potential bugs is reduced.

    Leave a comment:

  • uid313
    Senior Member

  • uid313
    replied
    Originally posted by Britoid View Post
    Rewriting the compositors in Rust would bring very little (if any) gain for an extreme amount of work, just because something is written in Rust doesn't make it better. C is perfectly fine for a compositor.
    I just don't want my compositor to crash because unlike X.Org Server where when the compositor or window manager crashed it would just gracefully restart with all applications intact, when a Wayland compositor crashes everything goes down. I think.

    Leave a comment:

  • Britoid
    Senior Member

  • Britoid
    replied
    Originally posted by uid313 View Post

    But does Weston or GNOME Shell support Vulkan?
    Yeah, maybe the low level library should be in C because it has bindings for many languages, but maybe the compositors ought to be written in Rust.
    GNOME Shell does not support using Vulkan as a renderer, GTK4 does though so if GNOME Shell does get rewritten in GTK4 it could use it.

    Rewriting the compositors in Rust would bring very little (if any) gain for an extreme amount of work, just because something is written in Rust doesn't make it better. C is perfectly fine for a compositor.

    Leave a comment:

  • uid313
    Senior Member

  • uid313
    replied
    Originally posted by ascent12 View Post

    This is talking about libwayland, the library which handles the low level wire protocol. It actually has nothing to do with graphics.
    Vulkan clients have always worked, and Vulkan support in Wayland compositors are entirely a compositor issue, and has nothing to do with Wayland itself.

    Why on earth would a C library suddenly stop wanting to be a C library? It's written in C for a very good reason, and just rewriting code for literally no reason is just an opportunity to introduce new bugs.
    But does Weston or GNOME Shell support Vulkan?
    Yeah, maybe the low level library should be in C because it has bindings for many languages, but maybe the compositors ought to be written in Rust.

    Leave a comment:

  • theriddick
    Senior Member

  • theriddick
    replied
    Well this all sounds nice, shame NVIDIA is still not working well with Wayland, but if AMD releases that super GPU big navi and its not a flop, I won't need to worry about that for long

    Leave a comment:

  • ascent12
    Junior Member

  • ascent12
    replied
    Originally posted by uid313 View Post
    But no support for Vulkan, and no code in Rust.
    This is talking about libwayland, the library which handles the low level wire protocol. It actually has nothing to do with graphics.
    Vulkan clients have always worked, and Vulkan support in Wayland compositors are entirely a compositor issue, and has nothing to do with Wayland itself.

    Why on earth would a C library suddenly stop wanting to be a C library? It's written in C for a very good reason, and just rewriting code for literally no reason is just an opportunity to introduce new bugs.

    Leave a comment:

  • lu_tze
    Phoronix Member

  • lu_tze
    replied
    Originally posted by uid313 View Post
    But no support for Vulkan, and no code in Rust.
    Wayland shouldn't have any GPU API-specific APIs. In case of Vulkan, it is Vulkan that has WSI (window system integration) layer on it's side of the fence. For Wayland, in the form of VK_KHR_wayland_surface.

    Leave a comment:

  • uid313
    Senior Member

  • uid313
    replied
    But no support for Vulkan, and no code in Rust.

    Leave a comment:

  • tildearrow
    Senior Member

  • tildearrow
    replied
    Originally posted by 144Hz View Post
    Meson or bust.
    Or CMake.

    Leave a comment:

Working...
X