10 ms·
Good old David - he loves systemd. No wonder he does not like X11. Oldschool KDE devs were better. Today's generation of David or Nate, are just killing KDE of
by shevy-java 4mo ago
Good old David - he loves systemd. No wonder he does not like X11.
Oldschool KDE devs were better. Today's generation of David or Nate, are just killing KDE off. But no worries, on their blog they'll continue how everything is great. It is so great that they need a donation-widget to keep on pestering people to donate. So now you can pay for them ruining the legacy here.
- segbrk 4mo agoFunny, my impression of KDE in the 3 and 4 eras was “Wow, this is shiny and sleek— oh, and it crashed. Nevermind.” Nowadays there is nothing I would recommend more to the average user who just wants something normal that works. It just works. What you’re saying just sounds like a pointlessly personal and ideological attack. Against a piece of software. Why?
- ahartmetz 4mo agoI don't really like Systemd neither - but Wayland and Systemd are pretty much opposites of each other. Systemd does (too) many things, many of them badly. Wayland does well what it does, but it (still!) does too little. Wayland is adding features and is pretty close to doing "everything necessary". Systemd keeps accreting worse replacements for existing services.
- josephcsible 4mo agoThey're similar in that they're both new things that are worse than what they're meant to replace.
- chlorion 4mo agoThey are actually both much better than the things they replace, but a bunch of whiner babies can't stand the thought of anything changing and will claw and scream while being dragged into the future.
- ahartmetz 4mo agoSystemd-resolvd is a bad DNS resolver and journalctl makes logging needlessly complicated and log files slow to read. Also, socket activation is basically xinetd and we got rid of it because it's a brittle hack, also slower than starting stuff as soon as possible if you actually need it.
- l72 4mo agoI’ll agree with some parts of this as I have some big issues with parts of systemd. But writing service files with systemd is so much better and having a unified interface into logs is really really nice.
- josephcsible 4mo agoSure, there are a few things it's better at. I don't think it's entirely bad, just that the good things are way outweighed by the bad.
- account42 4mo agoIts similar in that Wayland assumes responsibility for all interactions between programs instead of providing unrestricted interfaces that can be used to implement accessibility, automation and whatever other tools people can think of. It's the systemD way or the highway and it's the wayland way or the highway. But yes the situation is also different in that there is one SystemD but many little incompatible wayland compositors.
- vkazanov 4mo agoI dont know when where these "good old days" but in 2000s KDE was superunstable. It seemed to have all the cool UI tweaks but 30% of them barely worked. Modern KDE is nothing like that, and i cannot see how this is a bad thing.
- tuna74 4mo agoMore and more Free SW will depend on Systemd (like next gen flatpak). Make something better or adapt.
- okanat 4mo agoDavid is the definition of old-school KDE developer. Do you know how far back his commits go? I remember his name from my first rodeos with KDE when I was a teenager. He was blogging about KDE in 2009 FFS: https://blog.davidedmundson.co.uk/blog/2009/09/ https://blog.davidedmundson.co.uk/blog/2009/09/
- account42 4mo ago2009 was already after KDE 4 which many agree is the point when things started going to shit.