![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/4271bdc6-5114-4749-a5a9-afbc82a99c78.png)
Bleeding edge? Isn’t that just called stable?
Bleeding edge? Isn’t that just called stable?
It’s not even a single binary blob. Shows your competence around this topic. Feel free to continue rambling and whatever without knowing anything about it.
And what knowledge makes that opinion have any factual value?
You don’t know the details of why it was chosen, yet you complain about people with obviously more knowledge on these topics having chosen it… reminds me of science deniers.
And what concerns did/do you exactly have? Did you as a “democratic” user make yourself loud instead of crying about “corruption” on lemmy?
The choice of making way more things than just the job of an init system harder than it has to be, especially when both flavors have to work. Feel free to call generous people who work for the community “assholes”, but it’s you who’s that, if anyone
It’s not just an init system. Look up what it does and why it exists, instead of blindly hating some software for some obsessive reason.
Plus, do rust coreutils do anything exceptionally better than GNU coreutils? If not, I don’t think many would switch
time to snapshot my latest snapshot
(btrfs)
While that works, it sometimes might break things: https://fedoramagazine.org/offline-updates-and-fedora-35/
How would an AOSP fork help with an app not using the notifications API correctly? Just magically rewrite the app?
Doesn’t ReVanced work?
ha I already am (Android)
!i actually daily-drive fedora on my laptop!<
Neckbeards love to pretend open source magically has no security vulnerabilities
Who does? Feels like you’re just talking about inexperienced “btw i use arch” kinda skiddies
Don’t e.g. alarm apps not work after that until you unlock your phone since the device data decryption keys weren’t kept in RAM after rebooting? I have that feature off since I don’t want that to happen. Afaik AOSP has added that to make installing updates more seamless, but it’d be useful for this too. (And since Samsung usually sucks at improving their already self-made stuff to align with AOSP, like Virtual A/B updates, I’m just assuming this)
Yeah but that defeats the purpose of an universal format.
Sure, how about 2018-W06-1? Or 2018-036?
ISO 8601 contains way too many obscure formats. RFC 3339 is pretty much a subset and defines only sensible ones. It also allows 2018-02-05 08:02:43-00:00
(no T and explicitly specifying no timezone)
More like having Microsoft and Windows live rent-free in their head competition
comedy heaven?