For years, KDE users had to use Virtual Machine Managers outside the KDE ecosystem, like GNOME Boxes. Now that's changing with a new native VMM in development for KDE.
KDE development isn’t limited to a fixed number of developers. Lots of the things that go into it are contributed by regular users who want to see something improved.
It is true we are always complaining how understaffed project X and app Y are, but we are not a company, but an association run by volunteers.
In that context, if someone comes in and decides to work on a new project Z, there is no-one with the authority to tell them to go and work on X or Y instead.
That is not how we solve understaffing in KDE. Instead we have to recruit people directly into the understaffed projects. We cannot take them away from whatever their pet projects are.
Also, Karton, does not worsen the understaffing of Plasma in any way. On the contrary: we now have a new developer contributing to the overall KDE software stack that will possibly later tackle stuff in other areas of Plasma, as projects tend to overlap with each other.
I don’t agree with your assessment really as I don’t see the core experience declining.
But also, it’s a free project and people are putting in their time wherever they want; I don’t think the project would reject a submission for something based on “we’re doing too much” if it’s within the scope of a desktop environment.
That’s a valid concern; however, there is a clear benefit to making a full ecosystem. End consumers love it and stay with it, and this might contribute to increased adoption of Linux as a whole. At the same time, plenty of people don’t like ecosystems, myself included, and for us the choice is not going away.
KDE, in my eyes, is in the best shape it’s ever been, and they really can afford to spread development efforts. Besides, new applications bring new developers, which may contribute back to the core.
That’s a valid concern; however, there is a clear benefit to making a full ecosystem. End consumers love it and stay with it, and this might contribute to increased adoption of Linux as a whole. At the same time, plenty of people don’t like ecosystems, myself included, and for us the choice is not going away.
KDE, in my eyes, is in the best shape it’s ever been, and they really can afford to spread development efforts. Besides, new applications bring new developers, which may contribute back to the core.
I feel like KDE really spread themselves too thin.
KDE development isn’t limited to a fixed number of developers. Lots of the things that go into it are contributed by regular users who want to see something improved.
It is true we are always complaining how understaffed project X and app Y are, but we are not a company, but an association run by volunteers.
In that context, if someone comes in and decides to work on a new project Z, there is no-one with the authority to tell them to go and work on X or Y instead.
That is not how we solve understaffing in KDE. Instead we have to recruit people directly into the understaffed projects. We cannot take them away from whatever their pet projects are.
Also, Karton, does not worsen the understaffing of Plasma in any way. On the contrary: we now have a new developer contributing to the overall KDE software stack that will possibly later tackle stuff in other areas of Plasma, as projects tend to overlap with each other.
I don’t agree with your assessment really as I don’t see the core experience declining.
But also, it’s a free project and people are putting in their time wherever they want; I don’t think the project would reject a submission for something based on “we’re doing too much” if it’s within the scope of a desktop environment.
That’s a valid concern; however, there is a clear benefit to making a full ecosystem. End consumers love it and stay with it, and this might contribute to increased adoption of Linux as a whole. At the same time, plenty of people don’t like ecosystems, myself included, and for us the choice is not going away.
KDE, in my eyes, is in the best shape it’s ever been, and they really can afford to spread development efforts. Besides, new applications bring new developers, which may contribute back to the core.
That’s a valid concern; however, there is a clear benefit to making a full ecosystem. End consumers love it and stay with it, and this might contribute to increased adoption of Linux as a whole. At the same time, plenty of people don’t like ecosystems, myself included, and for us the choice is not going away.
KDE, in my eyes, is in the best shape it’s ever been, and they really can afford to spread development efforts. Besides, new applications bring new developers, which may contribute back to the core.