For what it’s worth, the origin of the inotify limit seems to have been a desire to be conservative when using unswappable kernel memory - if anyone reading this is interested in learning more about that feature, here are a couple links I found helpful (including suggested upper limits for that value):
And for what it’s worth… @ExXfceUser , if I can offer a thought, in my humble and ignorant user opinion, having no basis in actual development knowledge…the highlight of the Debian project is their Stable release. That release’s philosophy is curating specific releases of software that will fit together into a “whole that is more than the sum of the parts”, and that swapping out those parts for newer ones is a “FrankenDebian”, not recommended.
My observation of the KDE philosophy is one of more rapid and iterative improvements - over my five months or so of running openSUSE Tumbleweed daily, I’ve seen multiple releases of different KDE packages (Plasma Desktop, Gear apps, Frameworks, etc.), not all at the same time, and not all in one massive “this is the culmination of two years’ worth of work” push (although that no doubt does happen with things like the upcoming Plasma 6).
Take this for what it is, but I don’t feel like the “find a collection that works and stay with it for two years” approach from Debian meshes that well with the “fast iterative feature development, releasing and fixing” approach from KDE. Debian’s approach would seem to fit better with projects like (ironically, I assume, given your username) Xfce that value long-term availability of an unchanging feature set. Personally, I had a better experience using KDE products on Kubuntu with the Backports PPA, and am having an even better one on Tumbleweed, and I suspect that’s because they’re more naturally aligned with the upstream KDE model.
Take all that with many grains of salt, but just a few thoughts as I was thinking about this thread and several others.