4 ms·
I tend to downvote jokes or non-substantive comments about systemd (although I haven't downvoted any of the comments on this post). Like any other software sys
by skissane 5y ago
I tend to downvote jokes or non-substantive comments about systemd (although I haven't downvoted any of the comments on this post).
Like any other software system, anyone is welcome to question or doubt or disagree with systemd's design decisions. But some people seem to have an almost irrational hatred for it, far beyond what a mere software package calls for. Even if a person making a joke about systemd isn't themselves like that, being reminded of it all makes me want to reach for that downvote button. And the topic gets tiring after a while anyway, it has been done to death already.
- mlang23 5y agoFinally, cancel culture has a firm grip on Free Software, achievement unlocked!
- bayindirh 5y agoFlamewars of 90s have called, and reminded that it's way older than the cancel culture.
- mlang23 5y agoHowever, back then, killfiles were not shared amongst users. So if you decided to cancel someone, it only affected your view of a group. These days, we make killfiles a matter of voting, with a very low treshold. What is it? You just need 4 grumpy people and your opinion has just been tanked? Great, conservatives hiding under a left umbrella must really love that.
- bayindirh 5y agoI think discussions about a software project has nothing to do with politics. HN's dynamics are hard to understand at times, but it's not opaque or chaotic.
- cratermoon 5y ago> killfiles were not shared amongst users. My friend, usenet KILL files were absolutely shared. I ran a usenet NNTP server back in the day. There were many killfiles shared and usenet admins could also institute certain kinds of blocks. See http://www.kibo.com/kibokill/ http://www.kibo.com/kibokill/
- miohtama 5y agoSystemd of course has had its share of issues. But a lot of also comes down as natural resistance of change by sysadmins, which is a well documented psychological phenomenom https://journals.sagepub.com/doi/full/10.2466/09.02.10.CP.1.17 https://journals.sagepub.com/doi/full/10.2466/09.02.10.CP.1.... … and sysadmins tend to be at the deep end of the spectrum
- rovr138 5y agoI was with you at the beginning. This part just takes away from your argument, >… and sysadmins tend to be at the deep end of the spectrum Source?
- tapas73 5y ago> I was ... We'll need a peer reviewed article to believe that.
- bayindirh 5y ago> But a lot of also comes down as natural resistance of change by sysadmins... I find this "meh, you're just being stubborn" labeling is a bit dismissive. Especially when a lengthy technical comment about systemd is replied with the tone of "You just used to old ways eh? Time to freshen your knowledge, hehe". Today's sysadmin dynamics doesn't allow one to stagnate with old knowledge either. Yes it's very useful, but not eternally. Instead it allows you to build knowledge faster.
- pid-1 5y agoI'm a young-ish (late 20s) sysadmin and I've been reflecting on how I'm becoming increasingly cynical and resistant to change over time. I will probably organize my thoughts at some point, but here are some unsorted ones: * Infrastructure is often untestable. I've been bitten by the silliest changes in unexpected ways. We use IaC extensively, which makes things more organized and easier to operate, but still, testing stuff is insanely hard and time consuming, often impossible. * Infrastructure is often thightly coupled. Many architectural decisions will come back to haunt you in the future, in very serious and unexpected ways. * Infrastructure is often shared. Consequently, balancing requirements from different teams with different goals is very hard. * Often, I have no skin in the game. I will not earn more money to implement changes that will benefit my peers, but my life will suck more if I do. Often, being a intransigent bureaucrat is the most rational path I can take. * Often, devs have no skin in the game. They will earn more money if features get delivered, but won't have to deal with the long term operational and security consequences of the changes they ask for. That was already repeated ad nauseam by others, but my best professional experiences were: * The times I was responsible for software and infrastructure of a project. * The times I was working in a small team, very close to devs and thinking about a single project.
- deleted 5y ago[deleted]
- denton-scratch 5y ago> But some people seem to have an almost irrational hatred for it, far beyond what a mere software package calls for. That could be because somehow it's managed to become the default init on all mainstream distros, leaving few good options for those who would prefer to avoid it. I don't want to use a distro whose main raison-d'ètre is avoiding systemd.
- edoceo 5y agoGentoo and others exist for far more reasons than just avoiding systemd.
- denton-scratch 5y agoHmm, I thought Gentoo defaulted to systemd. Rather, I learn that it's an 'alternative'. https://wiki.gentoo.org/wiki/Gentoo_Without_systemd https://wiki.gentoo.org/wiki/Gentoo_Without_systemd Looks like you have to do a bit of tinkering to ensure it stays free of systemd. Same with Debian, which I use with SysV init. But it took a couple of hours tweaking to switch - perhaps one of the other inits might have been easier to switch to.
- edoceo 5y agoMy Gentoos have been OpenRC since forever. And maintaining that requires just one USE flag. I've never tried to move debian to not-systemd.