Can we perhaps now have EGLStreams compatibility on KWin?
Not that I ever intend to use the proprietary Nvidia driver (I'm saving for a GT 1030 to use with Nouveau, because I only need it to draw my desktop, so the locked clockspeeds do not affect me significantly), but it's really nice to have the option there in case I would ever need to resort to the proprietary driver.
Announcement
Collapse
No announcement yet.
Martin Flöser Steps Down As Maintainer Of KDE's KWin
Collapse
X
-
ngraham I learned about it only through some links posted here, and I dearly hope the decision to allow root user access for Kate and Dolphin will be revisited again at some point.
Most users (even some devs) don't have the technical knowledge to understand that what they are doing when they run GUI apps as root is really bad. Quoting Emmanuele Bassi from Gnome, where there has been a similar discussion:there are no *real*, substantiated, technological reasons why anybody should run a GUI application as root. By running GUI applications as an admin user you're literally running millions of lines of code that have not been audited properly to run under elevated privileges; you're also running code that will touch files inside your $HOME and may change their ownership on the file system; connect, via IPC, to even more running code, etc. You're opening up a massive, gaping security hole
(the changes in question are unrelated to sudo, it's really only about root user)
- Likes 2
Leave a comment:
-
Guest repliedOriginally posted by nuetzel View Post
We had ages of UI (lab) research.
Originally posted by nuetzel View PostKonsole without 'status bar'. - Horror.
Originally posted by nuetzel View PostWe have knobs. - Like knives & forks. Generations of people have learned how to use them...
Originally posted by nuetzel View PostI want to decide myself. - Or leave.
Leave a comment:
-
Originally posted by ngraham View PostIn no way, shape, or form are we unaware of the criticisms or ignoring the issues.
You ignore anything against it and push things forward against criticism and maintainers, this is what happened here, this is what drove and will drive people away.
And then, later on, you might notice that it wasn't the best idea but then you can't go back.
That's the picture I get by only reading a few of the tickets linked or mentioned.
So in addition to the comments already made on what specifically you should change: how the VDG works. Maybe reflect, sit back and wait a bit more, and be more open minded and accepting to arguments that do not fit your current view of the issue at hand.
And to answer your previous question (got eaten by forum filters, so I reply to it rather late): Hi Nate, I'm Daniel, I am "only" a concerned user and I don't think we met or know each other, no.
- Likes 2
Leave a comment:
-
Well, seems as he's just giving up Maintainership, but he'll stick around coding and with no doubt his vast knowledge about KWin and the decisions made. I'm sure David and/or Roman can take over Maintainership (if they choose to). Though, I'm pretty sure there'll have to be a transition phase, a maintainer with the knowledge of Martin isn't easily replaced.
Seems he's getting rid of some paint point (maintainership, the discussions with VDG/usability groups, reviewing) to drive on KDE/KWin from a technical point of view (he always stated that his passion goes for the technical implementation and challange, so maybe that's good for him and the project).
His step down also shows his passion for the project, actually. He couldn't take it any longer. Martin was always one to have a strong opinion on things, which is part of being maintainer. He obviously got upset fighting pitch-battles for the right solution, which is part of maintainership. Maybe they're right (later in the mails) that splitting maintainership of KWin in several parts is a good idea. It's a beast of a project, and splitting the review and fight responsibility is something to think of, though, that would require a release manager, but they'll manage. It's not as if this guys work together since yesterday.
KWin was in a worse state (developer whise) a not so long while ago, while there were contributions by others, the vast amount of work was done by Martin only. That obviously changed which is a positive thing (not following KDE development closely any longer, not a KDE user anymore for very much reasons Martin stated, it's getting feature crowded again as it was in KDE3, and I don't like that, but KWin is a gem, and I am looking to other Desktops to run on top of KWin, lxqt in example).Last edited by STiAT; 05 June 2018, 04:23 AM.
Leave a comment:
-
Originally posted by TemplarGR View Post
Haha, KWIN is EASILY the WORST part of KDE pal... I don't think you know what you are talking about... He is the reason i am so conflicted with major DEs: I want to use KDE for my workflow, but Kwin is trash, Gnome works so much better. And don't get me started on the 4.x days, ok?
- Likes 1
Leave a comment:
-
Originally posted by TemplarGR View Post
Haha, KWIN is EASILY the WORST part of KDE pal... I don't think you know what you are talking about... He is the reason i am so conflicted with major DEs: I want to use KDE for my workflow, but Kwin is trash, Gnome works so much better. And don't get me started on the 4.x days, ok?
I really don't think KWin is the worst part of KDE. I could understand if someone said that Plasma is, though I wouldn't say so. Of course you can have your own opinion, whatever that is, but I hope it is based on something.
Maybe I'm feeding a troll, which I probably shouldn't be doing...
Leave a comment:
-
Originally posted by msotirov View PostWell, I for one read his explanation as "I don't like it that I'm not a dictator and I have to debate my decisions with designers".
I'm grateful for his work but I strongly disagree with him on multiple points:
- client side decorations
- his thinking that the focus should be on new features instead of bug fixing and usability fixes
Well, it's the UI of the operating system. It gets designed before it's implemented.
What a drama queen!
Leave a comment:
-
Originally posted by ngraham View Postdarclide, you have a level of knowledge about these internal projects that makes me think that you're a KDE person I already know. Is that so? I'm Nate Graham BTW.
In the KCM redesign project, we have consciously avoided removing features. That was not the goal at all. It's a visual and UX overhaul, not a feature removal party. The only feature I'm aware of us removing is the tinting feature from the Icons KCM, because in the porting process it was discovered that the feature was actually broken and would be difficult to fix, and a lack of bug reports indicated that nobody was actually using it. We discussed the matter, and reasoned that users could get the same functionality in other ways already through custom icons and custom icon themes. Again I'm not aware of any other lost features off the top of my head. Can you enlighten me?
Again, we do NOT want to remove features and customizability. The goal isn't to turn Plasma into GNOME. What we're trying to do is get the best of both worlds: good defaults, attractive presentation, and high usability, all the while keeping the advanced features that our users love. Sometimes this does mean hiding them a bit, but we are NOT removing them. Making our KCMs simpler by default doesn't mean that we've actually removed any features, just that we're trying to make them easier to use.
I would still appreciate a specific list of gripes because that's actionable for me; I can try to help fix them. I can't do anything with generalities.
There is a subset of OCD people who think that unless every single pop up window has 5 submenus, 15 toolboxes, and throw some combo lists for fun, then it is "casual" and has "removed features". Those people should just fork KDE and add buttons lists and menus to their hearts content.
Granted, i was previously a Gnome user, and would still be using Gnome if it handled multiple applications' workflow better for me, but KDE's strength was never this kitchen sink approach of old. I am glad that some sane people like you stepped up and made changes. Keep up the good work!
Leave a comment:
-
Originally posted by nll_aThanks Martin for all your great work. Kwin is the best part of KDE for me and you are such a huge part of it. I hope everything works out for and that we'll still have you around with your crucial expertise.
I think KDE is only getting better and I have no personal opinion on this matter. I just want to thank the KDE community for such a fine work and hope your dynamics keeps improving.
Leave a comment:
Leave a comment: