Advertisement
Guest User

KDE4 Very Slow

a guest
Oct 17th, 2015
115
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.35 KB | None | 0 0
  1. Date: Fri, 16 Oct 2015 22:54:35 +0100
  2. From: Roger Leigh <rleigh@codelibre.net>
  3. To: dng@lists.dyne.org
  4. Subject: Re: [DNG] Detailed technical treatise of systemd
  5.  
  6. On 16/10/2015 20:39, Rainer Weikusat wrote:
  7. > Neo Futur <dng@ww7.be> writes:
  8. >>> I pretty much stopped reading after the following line in the
  9. >>> composition:
  10. >>> ======================================================
  11. >>> Fourthly, I will only be dealing with systemd the service manager (of
  12. >>> which the init is an intracomponent subset, and also contains several
  13. >>> other internal subsystems and characteristics which will prove of
  14. >>> paramount importance to the analysis), and to a lesser extent journald.
  15. >>> ======================================================
  16. >> Same here, if systemd was just an init system, i d probably still
  17. >> avoid it and fight it, but the main problem is that its much more than
  18. >> that, eating everything around it (
  19. >> http://neofutur.net/local/cache-vignettes/L200xH133/arton19-b28db.gif
  20. >> ), and that is the main problem, for sure.
  21. >
  22. > In case you like a nice piece of irony: Both GNOME and KDE perform like
  23. > shit. According to the opinion of both the GNOME and the KDE developers,
  24. > the reason for this must be somewhere in all the code they didn't
  25. > write. Hence, it has to be replaced. Especially considering that it's
  26. > all "But that's not how Microsoft does it!" stuff --- and you can't get
  27. > more fishy than that, can you?
  28.  
  29. The performance of GNOME3, KDE4 and Unity are all terrible. Too much
  30. shiny bling and too little care for *real* usability.
  31.  
  32. A couple days back, I was playing with Trinity on a PCLinuxOS live CD.
  33. Starting the applications **from the CD** was faster than doing the
  34. same from a KDE4 desktop *from an SSD*. At the time, I recall GNOME2
  35. and KDE3 being slower than their earlier incarnations, but the sheer
  36. bloat and inefficiency of the current forms of all these desktops is
  37. incredible. In Trinity, I was shocked that I could click on
  38. System->Konsole and get a terminal... not in a second or two, or even
  39. half a second, but right there and then. That's how bad the current
  40. desktops are. I shouldn't have been surprised at being reminded how
  41. snappy a user interface could be--it should be a standard expectation.
  42. I'm not even using low-end hardware; it's an 8-core 4GHz CPU with 16GB
  43. RAM and a 4GB GPU! Using a current KDE system, I found the amount of
  44. sliding-fading-semi-tranparent bling really got in the way of using
  45. the thing. When every hovering popup on the taskbar slides in from
  46. random directions as you moved the mouse around, I found this
  47. massively distracting, and that's only the start of it. The other
  48. major flaw is the use of animations and transitions; they typically
  49. only start after you initiate an action, leading you to wait until
  50. they complete to avoid getting confused as to what will happen;
  51. previously such actions were immediate. The most jarring example I
  52. can think of is the alt-tab switching animation where you have to wait
  53. while there's visible movement of the selection, but the modern
  54. kickoff menu is also victim to this, and it's seen in many other
  55. places. These little details all make the system less efficient and
  56. less predictable--they make you second guess what action will take
  57. since you're unsure of what will happen due to waiting on the
  58. animations/transitions to catch up with your input.
  59.  
  60. Roger
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement