• 0 Posts
  • 44 Comments
Joined 1 year ago
cake
Cake day: September 27th, 2023

help-circle
  • There are some really nice designs here. I really hope that KDE finally gets to pay attention to this. I love simplification of it.

    One thing I don’t like here is the login screen. There is too much stuff on it. I think gnome’s login screen, as it is now, is fantastic.

    And one more thing, proposal for mindset change: not everything has to be a widget. Some things (like shell) could have layouts: layout as current plasma/windows, layout as gnome, layout as Mac, layout as Win8… If things get well thought out, you can integrate this and switch layouts and not di*k around with widgets. Less moving parts, less problems.










  • Why would they put effort into changing something which works for them with the risk of breaking things?

    The sentiment is similar to climate change deniers. Why would we stop with fossil fuels when they work, people have jobs, etc. And why would we risk breaking the power grid?

    And as long as that works for them, they won’t actively change anything.

    Wayland on gnome and Ubuntu is already the default. It seems to me you have to actively change the default to x.

    It would be interesting to see in which scenario x is better than wayland. The only reason I can think of is an (old) Nvidia card. With new Nvidia’s I guess the statement would otherwise be ‘i will not use it until they fix Wayland’











  • I agree, all the apps I use run natively on Wayland, but I think there will always be some legacy X11 apps that won’t get ported. So, I think I’ll implement it, but it is definitely not a priority.

    While I understand the need for legacy, I also think at some point legacy should be left alone. If it is really needed for some old app to run, VM should do fine. I don’t think missing xorg is ever going to be an issue in 2025+ (well, Electron apps maybe). Yet added and not used features (or seldom used features) is offset with future maintenance burden and/or security issues for no good reason.

    This also applies to OpenGL comment. Every code path introduces a maintenance burden. While support of more devices is good, supported devices are super old in this case and the question is - is it worth it? Vulkan drivers should either way be in a better state.

    Looks very interesting! I wonder how it works, so I definitely will check it out.

    Is super cool, there is a presentation in one of the conferences about it. Architecture is explained somewhere in the docs. Anyway, if you do implement it - this would be a good alternative to https://guacamole.apache.org

    Who knows, maybe it would be a money opportunity.

    Why?

    It’s not Microsoft, but actually an open source community running open source forge. Also, it’s way faster to use in browser.