Open Source Software Community - it's about ethics in Code of Conducts

  • 🏰 Deploying update to the Tatarus security page. If you encounter issues, post here.
  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Kokonut Kangs Klan said:
Shit nobody needs, your server can take an extra 10 seconds to boot. Or just let services fail until their dependencies are ready, either way it doesn't actually matter. You either need the service or you don't, socket activation is fake and gay.
Click to expand...
Hah, you've never dealt with embedded (or just generally non-standard PC hardware) systems requirements that need this to deal with garbage baked into hardware + regulatory requirements for response times from first boot.

Really, there's a lot of people who think they use the full capabilities of an OS but barely touch it. They don't need any of the fancy stuff that systemd incorporates.
 
AmpleApricots said:
I maintain this opinion and it has always been true so far. This is *especially* true for a desktop system which is a lot less complicated to begin with.
Click to expand...

I'd argue that the average modern desktop is more complicated than the average server and has been for quite a while. Servers generally don't have to worry about X, video acceleration, Bluetooth or Wifi radios, audio, web video DRM, or other such things that are expected to just work on modern desktops.

777- said:
There's still no fully featured discord alternative normal people can use
Click to expand...

There are, but they don't have the network effect of Discord and likely never will, so very few people use them.
 
Also, I was trying to find a good video on how to work blender and this transgender freak would kept screaming about the God damn fascist trying to infiltrate. Open source software nigger. I just wanna know how to use this to make 3D models and edit videos.
 
AmpleApricots said:
How often in that time did a systemd user need to relearn and redo things because systemd moved it's goalposts?
Click to expand...
Zero times.
I have genuinely never had a problem with systemd. I've had my fair share of problems with other software (and even other Poettering-ware; hi PulseAudio, you still suck), but systemd has never been anything but stable for me.
The whole systemd debate is fucking retarded. Sure, it's got crazy scope creep (why does my init process need to manage my DNS and NTP all of a sudden?), but that is my only concern about it, and it's quickly outweighed by the sheer practicality of just using systemd and forgetting about it.
I don't give a single flying fuck about the init system you're using; you can rawdog it with the Bourne Shell for all I care. And frankly, I don't think you should care either.
 
Kokonut Kangs Klan said:
socket activation is fake and gay.
Click to expand...
inetd would like a word.
bort420 said:
Hah, you've never dealt with embedded (or just generally non-standard PC hardware) systems requirements that need this to deal with garbage baked into hardware + regulatory requirements for response times from first boot.
Click to expand...
That's a place I'd never even consider thinking about possibly using systemd. Having a non-deterministic init system sounds like a bad time. At that point you're likely better off with init being: "execl("/bin/sh","init","/etc/rc");"
 
Lard Shart said:
"Portable init scripts". This actually meant something back when people ran a variety of different operating systems, different shells, and different init systems. Now 99% of servers run some Linux distribution, with systemd and bash. There's nothing quite as portable as using Linux with systemd and bash.
Click to expand...
Have the larping hipsters finally given up on zsh?
I guess they needed something buggier, slower, bloated, insecure and with more supply chain attack opportunities during installation, aka. Written In Rust™.
 
Hannibalistique said:
Have the larping hipsters finally given up on zsh?
I guess they needed something buggier, slower, bloated, insecure and with more supply chain attack opportunities during installation, aka. Written In Rust™.
Click to expand...
LARPing hipsters no longer care about their login shell, when they've got two easy options that fit all of your criteria (including being Written in Rust™) in the form of fish and nushell. Neither is POSIX-compatible, but why should they care?
The level of hipster beyond that uses powershell.
 
AmpleApricots said:
I just want shit to work. I also still want it to work - the same way - in a month, or a year, or five years. I don't like suprises. If something changes, then it needs to be because I wanted that change, not because somebody forced it on me.
Click to expand...
Probably the one thing I absolutely despise in modern computing. My computer should just work with everything out of the box, with internet. But, once you connect to the internet, it comes with such a mirage of issues and problems because “nuh uh, you’re not allowed to”. Older MacOS’s work perfectly fine, until you have to use anything with an internet connection because “durr we don’t maintain this anymore, eat shit”. Okay, are older versions available? “Durr, you REALLY want to download an OLDER version??? Urrr returd, that comes with security risks! We have to ‘protect’ your retarded ass because fuck you.” Would a non-computer literate person even be interested in the slightest about downloading an older version of software? No, I don’t want to use Edge, I want IE. No, I don’t want Manifest V3, I want V2. No, I don’t fucking want Microsoft Minecraft Launcher, I want basic-bitch Mojang Launcher. Nuh, uh, fuck you. All that software would work PERFECTLY fine if it was downloaded in the past and had the internet cord ripped the fuck out to disable updates forcefully. - Goddamn Windows 7 REFUSED to work back when Win10 was a few years old and I installed a new CPU because my CPU was “too new”. I’m still goddamn pissed about it ever since.
 
reactionary said:
And frankly, I don't think you should care either.
Click to expand...
It's true, I don't care if you want to shove coconuts up your backside while convincing yourself good for you because they contain coconut milk. I'm still going to tell everyone that shoving coconuts up their backsides is retarded and there are much easier, more comfortable ways to get their coconut milk fix. It may require husking the coconut, or drilling a hole in it, which may take a little longer and may require some more work, but the end result is you have coconut milk, coconut meat, and maybe even a useful shell.

But, y'know, you do you.
306h4Ge5eJUJ said:
Worrying about boot times is natural when you're used to Windows. It reboots 15 times a day for good measure, you gotta optimize that shit.
Click to expand...
Well, thanks to systemd, now you can also have that same experience in linux.
 
teriyakiburns said:
It's true, I don't care if you want to shove coconuts up your backside while convincing yourself good for you because they contain coconut milk. I'm still going to tell everyone that shoving coconuts up their backsides is retarded and there are much easier, more comfortable ways to get their coconut milk fix. It may require husking the coconut, or drilling a hole in it, which may take a little longer and may require some more work, but the end result is you have coconut milk, coconut meat, and maybe even a useful shell.

But, y'know, you do you.

Well, thanks to systemd, now you can also have that same experience in linux.
Click to expand...
actually eating a coconut whilst reading this wtf
 
DavidS877 said:
inetd would like a word.

That's a place I'd never even consider thinking about possibly using systemd. Having a non-deterministic init system sounds like a bad time. At that point you're likely better off with init being: "execl("/bin/sh","init","/etc/rc");"
Click to expand...
Don't really have a choice if the vendor BSP uses it/it's certified for the use case and they won't support anything else!

systemd is fine overall. people really got the panties in a twist over it for reasons that I cannot comprehend. nothing is stopping them from rolling their own systemd-less distro's!
 
bort420 said:
systemd is fine overall. people really got the panties in a twist over it for reasons that I cannot comprehend. nothing is stopping them from rolling their own systemd-less distro's!
Click to expand...
Other than the fact it's subsumed so many formerly independent daemons that basically all of userspace is now tied to systemd in one way or another. Something that was, incidentally, predicted very early in its adoption, based on poettering's own statements and desires to that effect.
 
Rullepoelse said:
I thought you were joking, but they actually considered good ole sircmpwn aka Drew DeVault. Amazing.

Apparently it's no problem to be a pedophile in those circles.

View attachment 9492259
Click to expand...
Oh cool it's Stephen Chandler Lyude Paul, the Brave and Stunning furry transwxmxn (with a fart fetish) working for Red Hat who got Vaxry banned from Freedesktop.org because of CoC violations. And Vaxry also shows up on Drew's shitlist, no wonder they're friendly with each other
 
bort420 said:
Hah, you've never dealt with embedded (or just generally non-standard PC hardware) systems requirements that need this to deal with garbage baked into hardware + regulatory requirements for response times from first boot.

Really, there's a lot of people who think they use the full capabilities of an OS but barely touch it. They don't need any of the fancy stuff that systemd incorporates.
Click to expand...
That, but there are also a lot of workloads nowaday that are extremely bursty in nature.

A dataset becomes available, you spin up 10.000 VMs and have them process it for a few minutes then shut down.
If you do this a few times every hour, the 10 seconds in boot time you save on each VM adds up to real big money in your cloud spend.
 
Cuckoman said:
That, but there are also a lot of workloads nowaday that are extremely bursty in nature.

A dataset becomes available, you spin up 10.000 VMs and have them process it for a few minutes then shut down.
If you do this a few times every hour, the 10 seconds in boot time you save on each VM adds up to real big money in your cloud spend.
Click to expand...
Congratulations, you've just described containers which should have no init or systemd.
 
You must log in or register to reply here.
Back
Top Bottom