Originally posted by zexelon
View Post
KDE lead developer version of hissyfit.
1) Mandate the only party that could implement Wayland support in KDE for Nvidia had to be a Nvidia paid developer.(yes this is lead developer power)
2) Being the lead developer use that power to mandate what features the Nvidia lead developer has to implement.
3) This checkmates the Nvidia developer with a feature they cannot implement and gets Nvidia to implement what KDE lead developer wanted all along as in GBM and DMA BUF.
The reality here the KDE lead developer knew Nvidia did not have a functional solution. Its in many bug reports one is good where the KDE lead developer is asking the Nvidia lead developer how to implement compositor restart and the Nvidia funded developer end up asking for KDE lead developer to restrict KDE functionality until he can talk to the driver developer team on fixing the problem. Yes this is what leads to GBM and DMA BUF support.
KDE lead developer version of a hissyfit is being belligerent as well. KDE had enough market share that Nvidia could not ignore the hissy fit of KDE lead developer saying we are not allowing anyone other than Nvidia to implement this. Yes the KDE lead developer also said he would not waste any time implementing eglstream support.
KDE version of a hissyfit worked to get us to where we are today where Nvidia is now starting to support other Wayland compositors that have not implement eglstreams. Yes this is another part of KDE lead developer being a pain asking for third party compositor proof of Nvidia functional code.
Getting on KDE lead developers bad side long term never end up good.
Comment