[Video] Red Hat Is About To End Xorg: Is Wayland Ready?

Come the next major release of Red Hat Enterprise Linux, Red Hat is officially dropping the Xorg package, whilst it’ll still be available in RHEL 9 until 2032 the countdown has begun, Xorg is on the way out. Are you and your software going to be ready in time.

New video by: @BrodieOnLinux

yum13241,

Not until I can have my pretty screensavers. Yes, I care. When my laptops are on battery they don’t need to S3 sleep, nor s0idle. They just show pretty animations that prompt for a password and let me in, without waiting ten years for it to wake up from its slumber

lemmyvore,

There’s no Red Hat anymore, it was sold to IBM 5 years ago. All their recent shifts in FOSS strategy are a predictable result of that. IBM only cares to streamline RHEL operations not about what’s usable or appropriate for Linux in general.

SpaceCadet,
@SpaceCadet@feddit.nl avatar

Who made Red Hat the arbiter of when xorg should end?

I mean, sure they’re a major Linux vendor but their market is servers with hardly any foothold in the desktop market. It would be more interesting to see how long Debian, Ubuntu or Arch will keep xorg alive.

Unyieldingly,

Redhat does a lot of testing/patching with Xorg Server.

most of the people who was working on Xorg Server moved to Wayland a few years ago, Ubuntu and Debian have been Defaulting to Wayland, on the main Desktops, and Desktops are dropping Xorg Server support in Development, this is not just Redhat.

No Patches and No $$$,$$$,$$$ = Xorg server dead. if you want to pay 15 to 20+ Software Engineers/Testers to work on Xorg Server got for it.

FreeBSD has Wayland support to.

Even the Xorg mailing list is mostly dead, many of the Xorg Server Dev’s moved on, XWayland will be long lived.

and last i was there for all the Crying about XFree86 to I’m old.

LeFantome,

People are completely missing the point here. “Who made Red Hat the arbiter of when Xorg should end?”

I would say nobody but perhaps a better answer is all of us that have left the work of maintaining Xorg to Red Hat. All that Red Hat is deciding is when they are going to stop contributing. So little is done by others that, if Red Hat stops, Xorg is effectively done.

Others are of course free to step up. In fact, it may not be much work. Red Hat will still be doing most of the work as they will still be supporting Xwayland ( mostly the same code as Xorg ), libdrm, libinput, KMS, and other stuff that both Xorg and Wayland share. They just won’t be bundling it up, testing it, and releasing it as Xorg anymore.

We will see if anybody steps up.

SpaceCadet,
@SpaceCadet@feddit.nl avatar

So little is done by others that, if Red Hat stops, Xorg is effectively done.

Source?

As far as I know the X.org foundation is an independent non-profit organization, and while Red Hat is a sponsor and they have 1 member in the board of directors (out of 8), they don’t appear to be the main contributor.

taanegl,

Here’s the repo for xserver. It’s basically a collective effort between developers who represent certain companies, among them Oracle - and RedHat.

AMDIsOurLord,

They’re the ones who’s engineers worked on Xorg, so yes, they decide it.

edinbruh,

As the video points out, a lot of the work in xorg (and Linux in general, fwiw) is done by red hat engineers. So red hat cutting on that investment bears direct consequences for everyone else. Unless of course someone steps up and takes their place in maintenance, but it’s not gonna happen, which is literally why Wayland (and not some revamped xorg) is the future of Linux desktop.

Also, red hat’s decisions often trickle down on most other distros. E.g.: systemd, pulseaudio, pipewire, gnome, not including proprietary codecs, etc.

So, they technically don’t arbiter, but they definitely set the pace.

wmassingham,

Nobody. And it’s not like Red Hat runs the X.Org Foundation, either, at most they have one seat on the board. Development will continue.

theshatterstone54,

By whom? Red Hat is pretty much the only one supporting X.Org so that’s why. Development will not really continue because there will be nobody to do the development.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • linux@lemmy.ml
  • localhost
  • All magazines
  • 200 @ entry_single
    HTTP status 200 OK
    Route name entry_single
    Has session yes
    Stateless Check no
    Time 13102 ms
    Total time 13102 ms
    Initialization time 2407 ms
    Memory 16.0 MiB
    Peak memory usage 16.0 MiB
    PHP memory limit 128 MiB
    Cache 1
    Number of forms 1
    Number of errors 0
    Logger 87
    Errors 0
    Warnings 0
    Deprecations 87
    Cache 81 in 6874.41 ms
    Cache Calls 81
    Total time 6874.41 ms
    Cache hits 49 / 83 (59.04%)
    Cache writes 24
    641
    Default locale en
    Missing messages 641
    Fallback messages 0
    Defined messages 148
    Security n/a
    Authenticated No
    Firewall name main
    Twig 7803 ms
    Render Time 7803 ms
    Template Calls 181
    Block Calls 82
    Macro Calls 6
    130 in 6963 ms
    settings_row_switch 15
    date 14
    user_inline 13
    date_edited 12
    vote 12
    boost 12
    entry_comment 11
    user_avatar 11
    entry_comments_nested 11
    user_settings_row_switch 4
    settings_row_enum 2
    entry 1
    entries_cross 1
    editor_toolbar 1
    user_actions 1
    magazine_box 1
    magazine_sub 1
    related_magazines 1
    active_users 1
    related_categories 1
    related_posts 1
    related_entries 1
    support_us_block 1
    featured_magazines 1
    22 in 643.91 ms
    Database Queries 22
    Different statements 14
    Query time 643.91 ms
    Invalid entities 0
    Cache hits 27
    Cache misses 7
    Cache puts 7
    6.4.0
    Profiler token 17da80
    Environment dev
    Debug enabled
    PHP version 8.2.26   View phpinfo()
    PHP Extensions Xdebug ✗ APCu ✓ OPcache ✓
    PHP SAPI apache2handler