Coc and Systemd

> or if im just a fucking crazy person
don't let people gaslight you the patterns you're seeing are legit

This

There is no connection. Glow in the darks will have their way with Linux no matter what since it's such a huge platform now. If you don't like this you can simply install BSD, Haiku, Plan9, ReactOS, macOS, Solaris, or any other non-Linux system.

I would personally recommend OpenSolaris forks like OpenIndiana or Tribblix, which seem to be the only reasonably up to date illumos based operating systems.

Attached: 1539287792555.jpg (567x449, 33K)

debianuserforums.org/viewtopic.php?f=11&t=3707

The writing is on the walls. But you're just a frog poster so what do I know.

>The writing is on the walls
If you want to suggest that there's a conspiracy going on then be direct about it. Stop posting cryptic horse shit, nigger. You're spinning your wheels like a useless little downie and wasting my time.

bloated af

>conspiracy
No
>link between within ideologies and choices
Yes

CoC was introduced by intel as punishment for constantly calling them out over spectre/meltdown and performance hits

Prove me wrong

B L O A T
L
O
A
T

Okay, then that's not tech related. Take your shit to another board. And thanks for yet another short and vague answer, you fucking sped.

The only problem with dumping Linux and windows is that I need CAD for my job. Sad face

Somebody translate this for a linux noob

I've had the same thoughts. They are after all america's most JUST company.

>without-systemd.org/wiki/index.php/Arguments_against_systemd
a common saying in system development is that you should make systems that accomplish one thing well, and if you're slowly adding more functionality to a system that makes the scope gradually increase, you may be doing it wrong

Now, with systemd, they've added so much shit that it's a boot system that is somehow also a DHCP client. Some people will say that's fine, they're both related to booting a computer and getting it ready for the user; other people will say that you shouldn't put low-level booting code and higher-level networking code in the same project and expect the same group of people to maintain both. Further down in the page they talk about how this "scope creep" leads to some WTFs, such as vulnerabilities in systems that wouldn't be there if specialists were writing the code (I may be wrong on this point however)

other issues (writing this as I scroll down the page): they use Google services by default for a couple of things that have excellent alternatives (DNS: 1.1.1.1 or Cloudflare; NTP: NIST servers), and the devs just handle certain issues weirdly.

I read through some of the issues and it just appears that the devs sometimes come down on the other side from the Linux community on some philosophical issues. Nothing too bad.

There are some really hardcore systemd haters on Mastodon; maybe ask them for some better talking points, because some are actually knowledgeable about Linux

not the guy you're replying to, and if this is easily answered elsewhere then let me know and I'll fuck off, but are there any real reasons something like this becomes the backbone of so many distros?

yeah it's convenient, as a distro maintainer, to just drop this in and stop caring about the systems that it replaced

also some argue that configuring this is nicer than configuring the stuff that preceded it (an actual config format vs scripts that kill you if you put spaces in the wrong places)

guess that makes sense. the less you have to worry about, the better.

systemd is the equivalent of a God class in oop. Doing too many things in a system that's designed around each component doing 1 specific thing or set of related things.

Regardless of "connection", it's something a lot of corporate players absolutely do love.

Linux development today is largely corporate done by corporate employees who will, naturally, do and work on whatever their employer tells them to.

Then there's people like Linus himself who isn't controllable. There's also quite a few more independent sub-system maintainers. These are people who will say no, we're not going to put that shit in the kernel when corporations ask for features that restrict end-user control and things of that nature. So they are a "problem".

From this corporate perspective it's great if independent developers leave over a CoC or are kicked out with a supposed CoC violation as an excuse. I've seen people say silly things like "development could stop" if that happens; that's just not true: Plenty of bigger corporations could very easily hire a few people - who could and would be controlled - to replace them.

As for how this relates to things like systemd.. there's a number of perhaps not very desirable features that would be merged into the kernel very quickly if someone working for RH were put in charge of the kernel, that's for sure

It all comes down to control in the end, in my opinion. I have no doubt there are strings being pulled in certain directions to achieve desired outcomes in open source development. Linux was something that couldnt really be controlled, so I think they are hoping to use the CoC as a weapon to change that. They already tried something similar to try to prevent Kavanaugh from being appointed imo.

What is your BIOS then?

>take a bunch of different components made by different people that communicate using standards and conventions
>replace it with a bloated mess made by a single person whose main talent is self-promotion

why is there such a push to force the end-user into a passive role?
what's your opinion?

it certainly seems like it.
i dont know what the agenda is, or the end-game, but i dont understand how anyone can look at all this and not think that there is something very strange going on

How do you "replace" something that nobody owns? You can always make your own fork right?

>debianuserforums.org/viewtopic.php?f=11&t=3707
wow what a fucking disaster, how sad

>make your own fork
what about people like me who dont have the skills, or that desire/time to learn how to make my own fork.
all i want is a relatively easy to use distro, that's customizable to my needs, isnt being politicized, and that my involvement wont be contributing to some corporate/political agenda
fuck me dead, why is this becoming so difficult to achieve, and not just in tech either

>have no skills, desire or time to make something happen
>wonder why it doesn't happen
install gentoo

>wanting a car to drive without having to learn how to fabricate steel and process petroleum
>wow so entitled
fuck off faggot, wasnt that the whole point of distros like ubuntu and debian?

You pay for a car. You can make a generous donation to Devuan if you don't have the skills

I've got no issue paying for, or donating to a project. But i just want the option to not "pay for"/"donate to" a company or community that's fucking their users in the ass