Announcement

Collapse
No announcement yet.

OBS Studio Merges Its EGL-Wayland Code To Natively Support Wayland

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

  • oiaohm
    replied
    Originally posted by 144Hz View Post
    oiaohm You had me laughing at kwin and Kwinft working together. They just spent the last week exchanging insults and fragmenting their code bases. Now I remember you are also the guy who claims KDE owns the Qt copyright. I see no reason to discuss any further. We don’t share the same reality. Talk to you next time the kwinft poopoo slinging blogs makes the news. Shouldn’t be long..
    Insulting each other and looking to fragment happens with wine mainline vs wine staging as well even when stuff is moving mainline. You need to look deeper at the commits that are making it into mainline.

    Friendly fork is a deceptive term. A fork can be friendly with mainline as in working the features of the fork up into mainline over time at the same time having public disputes with ideas in mainline.

    I told you to look at the KDE mainline patches just reading the blog and exchanging insults can horrible be part of the development process.

    Also think patches from kwinft are modified and end up in mainline Kwin of course there should be a few posts stating that X reason for using kwinft is no more why because that feature is now mainline. Take a closer look at those so call kwinft poopoo slinging blogs and the patches the lead developer of kwinft has got merged mainline kde you will notice something its exactly this. So yes there are going to be more blogs like that and should be expected when the fork is not 100 percent independent and the reasons for using kwinft is a changing thing.

    Leave a comment:


  • 144Hz
    replied
    oiaohm You had me laughing at kwin and Kwinft working together. They just spent the last week exchanging insults and fragmenting their code bases. Now I remember you are also the guy who claims KDE owns the Qt copyright. I see no reason to discuss any further. We don’t share the same reality. Talk to you next time the kwinft poopoo slinging blogs makes the news. Shouldn’t be long..

    Leave a comment:


  • oiaohm
    replied
    Originally posted by 144Hz View Post
    oiaohm KDE showing good progress? I see nothing but forks and weekly blogs about some unquantifiable “wayland improvements”.
    This is shows you have not been reading. KDE what you hear talked about is KDE mainline and 1 fork KWinFT. Thing you have missed is if you take the lead developer of KWinFT and check is name against KDE mainline patches he is there. KWinFT is very much like the Wine staging branch for the mainline KDE because the improvements that work properly in KWinFT are moving mainline.

    Quite a few of the wayland improvements are based on bugs if you get to the bugs you have the information to in fact quantify the improvements. Really 144Hz you are not putting in the effort to know how KDE is in fact going. Reporting always only part of the picture.

    Leave a comment:


  • 144Hz
    replied
    oiaohm KDE showing good progress? I see nothing but forks and weekly blogs about some unquantifiable “wayland improvements”.

    Leave a comment:


  • finalzone
    replied
    Originally posted by fafreeman View Post
    I fear this because all I want is a simple xfce / gnome 2 style DE again on wayland. I don't like tablet focus gnome which unfortunately has been the biggest funded and developed wayland and honestly x11 DE. I also don't like bloated KDE along with some keyboard focused tiling minimal thing like sway.
    GNOME Classic is the starting point.

    Leave a comment:


  • oiaohm
    replied
    Originally posted by fafreeman View Post
    I fear this because all I want is a simple xfce / gnome 2 style DE again on wayland. I don't like tablet focus gnome which unfortunately has been the biggest funded and developed wayland and honestly x11 DE. I also don't like bloated KDE along with some keyboard focused tiling minimal thing like sway.

    I wish xfce received more funding and support. It's probably going to be years before it even gets basic wayland support if it gets wayland support at all.
    This is worse. xfce will need to pick up the pace on a lot of things like GTK 4.0 support. Xfce is not only lagging in Wayland support its lagging in using current versions of libraries what means it more open to security flaws.


    Originally posted by 144Hz View Post
    fafreeman That’s not going to happen. So far only GNOME has demonstrated the willingness and capabilities to reach the post-X era.
    Sorry that is tunneled visioned on your part. KDE and sway/wlroots is showing good progress in that direction of post-X. Xfce does in fact depend on Gnome maintained and made parts and has been under resourced to keep up on that side.

    The reality here items like xfce have not been in a healthy location for development or funding for quite some time.

    Wayland change over really is just displaying existing problems that need fixing by either merging projects to increase resources in remaining projects or killing off projects or somehow finding more funding for them.

    Leave a comment:


  • 144Hz
    replied
    fafreeman That’s not going to happen. So far only GNOME has demonstrated the willingness and capabilities to reach the post-X era.

    Leave a comment:


  • fafreeman
    replied
    Originally posted by oiaohm View Post

    This is where things take a horrible turn for the worst for you arguement. Replacing old X features requires tons of developer resources is true. But you have overlooked something most of the parts you need to replace for wayland were in fact deprecated under X11 protocol almost a decade ago with a dbus interface yet there are still a lot of WM and DE under X11 not providing the new interfaces and worse as wine/Qt/Gtk.. quirk lists shows have not implemented even the deprecated X11 ones correctly.

    There is a lot of distribution hoping/DE and WM hopping that is caused by using parts that are under resourced for developers that have not even implemented the deprecated X11 parts correctly.

    So yes a lot of DE and WM really need to end of life and not make it to the post-X era. Yes due to the fact they are broken as applications update for Xwayland that are providing X11 protocol related parts correctly if it provides will result in newer versions of X11 applications tested with Xwayland working only on bare metal mostly with DE/WM for X11 that have Wayland support but having odd quirks on the DE/WM that have not done this because of the broken they have.

    144Hz X11 on bare metal is broken in many ways.

    1) X11 server on bare metal does not really have any funded developers.
    2) DE/WM that support X11 only most of them under closer inspection are broken and are causing distribution hopping and WM/DE hopping.

    Like it or not the fact that not all DE and WM will make into the post-X era is a good thing long term. Maybe some of the ones that die will pool their resources to make a Wayland compositor that has enough personal to-do the job properly?
    I fear this because all I want is a simple xfce / gnome 2 style DE again on wayland. I don't like tablet focus gnome which unfortunately has been the biggest funded and developed wayland and honestly x11 DE. I also don't like bloated KDE along with some keyboard focused tiling minimal thing like sway.

    I wish xfce received more funding and support. It's probably going to be years before it even gets basic wayland support if it gets wayland support at all.

    Leave a comment:


  • oiaohm
    replied
    Originally posted by 144Hz View Post
    oiaohm Your tunnel vision theory is spot on. Replacing old X features requires tons of developer resources. Ultimately not all DEs and WMs will make it to the post-X era.
    This is where things take a horrible turn for the worst for you arguement. Replacing old X features requires tons of developer resources is true. But you have overlooked something most of the parts you need to replace for wayland were in fact deprecated under X11 protocol almost a decade ago with a dbus interface yet there are still a lot of WM and DE under X11 not providing the new interfaces and worse as wine/Qt/Gtk.. quirk lists shows have not implemented even the deprecated X11 ones correctly.

    There is a lot of distribution hoping/DE and WM hopping that is caused by using parts that are under resourced for developers that have not even implemented the deprecated X11 parts correctly.

    So yes a lot of DE and WM really need to end of life and not make it to the post-X era. Yes due to the fact they are broken as applications update for Xwayland that are providing X11 protocol related parts correctly if it provides will result in newer versions of X11 applications tested with Xwayland working only on bare metal mostly with DE/WM for X11 that have Wayland support but having odd quirks on the DE/WM that have not done this because of the broken they have.

    144Hz X11 on bare metal is broken in many ways.

    1) X11 server on bare metal does not really have any funded developers.
    2) DE/WM that support X11 only most of them under closer inspection are broken and are causing distribution hopping and WM/DE hopping.

    Like it or not the fact that not all DE and WM will make into the post-X era is a good thing long term. Maybe some of the ones that die will pool their resources to make a Wayland compositor that has enough personal to-do the job properly?

    Leave a comment:


  • 144Hz
    replied
    oiaohm Your tunnel vision theory is spot on. Replacing old X features requires tons of developer resources. Ultimately not all DEs and WMs will make it to the post-X era.

    Leave a comment:

Working...
X