Ah, but you need to separate the art/revolution from the artist/revolutionary
/s
Ah, but you need to separate the art/revolution from the artist/revolutionary
/s
Please keep the discussion polite, and don't get too much carried away into trying to convince others of your own ideas. Exchange is less than that. And sometimes, less is more. Thanks in advance.
fwiw in football, the white line is considered part of the field and the ball only crosses it after the outer border of the stroke itself...
I believe the community had expressed a lot of valuable ideas here, so I will keep the post. But I am locking the thread because it's just not information given in good faith. That's not to say that the points are all wrong, these can be debated. And we did debate. But the infographic itself is border to being just propaganda against a distro that serves well to a lot of users (this is a fact! even if me or you think those users could be served better.)
the reason: support for developers. You can install it yourself to save that amount.
There's a deGoogled version too!!
I would prefer GrapheneOS (If I can live with the irony of getting a Pixel phone just to deGoogle it...). Sandboxing there is way better. But you lose the Repairability.. Gotta check and compare the new EU metrics too.
They are just two different devices.
They still store the passwords like that? I remember that quote of Zuckerberg doing so, in the early days, and boasting about it to a friend... This was so outrageous at the time. Now it's beyond absurdity.. Not to mention the fine is so small!
Btw, libgen domains were seized recently. Here are new ones: https://lemmy.dbzer0.com/post/26690539
This is the first time I enjoy a meme of this format / situation.
This is exactly why we love Python (and other languages with rich package ecosystem, even when only on their niche usage cases). You can build upon other people's knowledge and effort to do cool things efficiently and effectively!
iirc it started as a spinoff since vanilla arch preferred to stay conservative in regards to compiling packages with "the new" cpu optimizations. They are not so new at all, but since it meant breaking support with old hardware... Hence, the dillema that called ina fork and here we are.