[09:11] <RikMills> mamarley: looks like the kwin changes you liked have been reverted
[09:11] <RikMills> https://mail.kde.org/pipermail/kwin/2020-January/002999.html
 >I don't see a positive future for the KWin project as it is currently … organized on a fundamental level
[10:47] <mparillo> Back when it seemed to the casual observer that Martin simply did everything on KWin...
[10:54] <Tm_T> Gräßlin? yea he did a lot
[11:00] <Tm_T> ah, Flöser nowadays? so many things happened while I was away
[11:03] <mparillo> Martin is easier on my keyboard.
[11:13] <Tm_T> I was reading that mailinglist and was wondering what names I was not seeing there, Martin was it (:
[11:46] <mamarley> Well bummer.
[11:49] <mamarley> And he reverted the (unrelated) bug fix for the compositor blacking out when suspending and re-enabling compositing too. :(
[11:50] <mamarley> (when swap events were used)
[11:51] <mamarley> And I never even got to try it out to see if it would fix some of the stuff I thought it would.
[12:39] <BluesKaj> Hi folks
 https://kde.org/announcements/plasma-5.17.90.php
 uploading to staging ppa now
 Wooohooo 😁😁
[14:41] <mamarley> I'm having a very hard time getting excited about it since the kwin changes were reverted.
[14:44] <mamarley> To be honest I had gotten sick and tired of the stuttering and lag, and of the apparent stagnation of kwin development.  The Intel swap event thing helped with the stuttering and lag, but also tended to cause framerate-halving.  Other compositors seem to be able to avoid the stuttering and lag without framerate issues, so I was hoping these patches would make kwin do that too.
[14:46] <mamarley> And also the apparent inability to ever get things working properly on Wayland…
[14:58] <mamarley> I'm going to do my own build with the reverts reverted.  I at least deserve to know whether it fixes the problems I mentioned.
[14:58] <RikMills> mamarley: nice idea!
 @mamarley, Ensure to report here what you discover.
[15:00] <mamarley> Of course!
[15:00] <mamarley> And if it works well and solves any of my problems, I can at least hopefully maintain it through the 5.18 cycle…
[16:07] <blaze> One the amd side kwin doesn't work too well either
[16:08] <blaze> on*
[16:33] <mamarley> blaze: There's a decent explanation as to why at https://github.com/tildearrow/kwin-lowlatency.  If my understanding of the situation is correct, the now-reverted improvements in 5.18 were supposed to address some of those concerns.
[17:55] <mamarley> Well, here goes nothing…
[18:09] <mamarley> Oops, it seems I have jumped the gun…
 *hugs* RikMils
[20:02] <mamarley> So my initial impression is that the compositor overhaul patches don't seem to result in any noticeable change versus 5.18 beta with KWIN_USE_INTEL_SWAP_EVENT=1, besides the bugfix for toggling compositing resulting in a black screen.
[20:03] <mamarley> That specific patch is unrelated to the overhaul though and I'm not sure why it was reverted in the first place.
[20:03] <mamarley> In any case, I reserve my final judgement until I can try it on my computer with a 4K display.
[20:22] <blaze> I have a different issue, slightly annoying ghost windows, remaining on the screen forever after the application was closed
[20:24] <mamarley> Interesting, I haven't seen that.