Am…I don’t have to?
also no other Linux user has to do either
Just because one systemd dev prepared something to be optionally used for a stupid law, doesn’t mean anyone using Linux is forced to do that
Seems you don’t know how anything on Linux, and it’s ecosystem, works, if you believe that
And the relation to that news is also a mystery to me
Kissaki@programming.dev
on 10 Apr 17:08
nextcollapse
Seems you don’t know how anything on Linux
What makes you think that is what they think? They referenced other people. They didn’t make any claims themselves or made any indications that they agree with those “flipping out” (who misunderstand).
I read it as the opposite. They know and criticize those who don’t and flip out because of that.
Just because one systemd dev prepared something to be optionally used for a stupid law, doesn’t mean anyone using Linux is forced to do that
Seems you don’t know how anything on Linux, and it’s ecosystem, works, if you believe that
This is disingenuous at best.
Sure, its ‘just’ a single text field that ‘optionally’ can be used. until it isn’t.
SystemD itself is a perfect example of this. Sure you have choice in theory, but in practice its a wildly different story. Name one mainstream Linux distro that can be used for casual day to day use, ranging from doing taxes to playing Steam games that does not use SystemD.
A lot of people drew issue with SystemD when it came out and as time progressed, but the number of fully supported core distros that do not use SystemD is zero.
Nobody’s concerns were considered, and not one uses Runit, InitRC, or even just refused to move on from SysVInit, unless you count Gentoo. Debian is SystemD. Arch is SystemD. Fedora is SystemD. And so are almost all their derivatives.
In order to get away from SystemD, you have to switch to forks that intentionally go out of their way to make it happen like Artix. Arch’s wiki page literally tells you that you can have any init system as long as it’s SystemD.
You are left to rewrite entire core system components yourself and maintain them if you really want to make it happen.
So yea, you technically have a choice, but not really.
SystemD is not just init. There are no hard rules to use all of it, btw. Not to mention that if you have a field left to control users age, no one is stopping them to write the value 30 and have full access for the system…
WhatAmLemmy@lemmy.world
on 10 Apr 17:28
nextcollapse
It’s great to know that there has been a “notification db” storing a history this entire time, yet users have no way of viewing a notification the moment it is interacted with in any way, even accidentally… You’re just renting apples computer, so fuck you, I guess?
threaded - newest
Meanwhile, Linux people are flipping out over having to tell their os they are >18.
Am…I don’t have to?
also no other Linux user has to do either
Just because one systemd dev prepared something to be optionally used for a stupid law, doesn’t mean anyone using Linux is forced to do that
Seems you don’t know how anything on Linux, and it’s ecosystem, works, if you believe that
And the relation to that news is also a mystery to me
What makes you think that is what they think? They referenced other people. They didn’t make any claims themselves or made any indications that they agree with those “flipping out” (who misunderstand).
I read it as the opposite. They know and criticize those who don’t and flip out because of that.
Well, ok, maybe I got it wrong
This is disingenuous at best.
Sure, its ‘just’ a single text field that ‘optionally’ can be used. until it isn’t.
SystemD itself is a perfect example of this. Sure you have choice in theory, but in practice its a wildly different story. Name one mainstream Linux distro that can be used for casual day to day use, ranging from doing taxes to playing Steam games that does not use SystemD.
A lot of people drew issue with SystemD when it came out and as time progressed, but the number of fully supported core distros that do not use SystemD is zero.
Nobody’s concerns were considered, and not one uses Runit, InitRC, or even just refused to move on from SysVInit, unless you count Gentoo. Debian is SystemD. Arch is SystemD. Fedora is SystemD. And so are almost all their derivatives.
In order to get away from SystemD, you have to switch to forks that intentionally go out of their way to make it happen like Artix. Arch’s wiki page literally tells you that you can have any init system as long as it’s SystemD.
You are left to rewrite entire core system components yourself and maintain them if you really want to make it happen.
So yea, you technically have a choice, but not really.
Try out GuixSD, it got herd. It works great!
SystemD is not just init. There are no hard rules to use all of it, btw. Not to mention that if you have a field left to control users age, no one is stopping them to write the value 30 and have full access for the system…
What’s with the all or nothing approach, tho?
Yea, that’s kind of the problem.
It’s great to know that there has been a “notification db” storing a history this entire time, yet users have no way of viewing a notification the moment it is interacted with in any way, even accidentally… You’re just renting apples computer, so fuck you, I guess?
Turn off message previews on your notification settings.