Originally posted by bug77
View Post
It does seem that its KWin specifically thats having these tensions which is not too surprising considering that KDE is reliant on KWin to do anything (it is afterall the main compositing engine). Such software commonly permeates an ultra conservative attitude out of fear of breaking things and considering its age and how Linux is not that mature when it comes to dealing with graphics/compositing/X11 there are a huge amount of workarounds/hacks and without having lots of hardware to test regressions there is a lot of fear of not breaking things.
In these kinds of cases I can see why a fork is necessary for such large refactoring especially if you want to revisit things from first principles however I would tone down the language, it isn't fair to brush all of KDE software with the same brush.
Comment