Absolutely in favour, the non-free blobs are a persistent thorn in my side. I myself have always been tempted to replace all the fedora and debian templates with alpine or OpenBSD to get smaller VMs (and without systemd), built as many things as unikernels as possible (e.g. the MirageOS firewall), and I’d love if X11 got replaced with Wayland (that one is hard, the X11 modifications are kind of the core of what Qubes provides).
What am I supposed to do?
Learning to write a problem description that is remotely intelligible would be a start. What Distro are you on? What are you trying to accomplish? What have you tried? What error occurs (error messages or what expectations you have that are not met), etc.
Sure, just not something I am comfortable actively recommending myself.
I cannot, in good conscience, recommend a project with a lead that is as verbally abusive and utterly unable to appreciate even highly constructive criticism as Micay, technical merits notwithstanding. I am fine when others recommend it though.
Let’s call a spade a spade: He is a raging asshole with severe clinical paranoia. I’m literally certain that if he saw this post he’d accuse me of being a shill for calyxos and to never fucking again interact with any grapheneos account. Both have happened to me before (Hence I refuse to ever interact with his troupe again, even though I use graphene and agree with the vast majority of its technical decisions; I have also stopped actively recommending it to anyone, the social media experience is simply way too attrocious).
If you can find a way, so can “the bad guys™”. If you feel charitable towards MS do a “responsible disclosure” and inform them and agree to a release embargo, so they can fix it first; If you don’t, do a “full disclosure” and just publish =^_^=
I personally favour Alpine Linux for its minimalism, but Devuan or Debian are fine, and more familiar choices, too. Depending on what you intend to run, especially appliance-like things, OpenBSD might be a good alternative.
No shit. “More” is technically correct. “A metric fuckton more” conveys the appropriate scale. It’s not like systemd added a handful small features, it has subsumed nearly everything between kernel and userland. (Note that proponents usually point this out as a good thing; It’s uncontested, you just seem blissfully unaware)
Have you considered that we don’t think any of those are “good points” worthy of comment?
Nope, but “more” doesn’t adequately capture the scale of it. Given that you talk about a predecessor (singular) I presume systems programming is not your specialty?
Ahem, it does a ton more than merely “initiate booting” (logging, time, user management, device management, the list is long and it is really hard to find a piece of basic system functionality it hasn’t subsumed), please don’t spread misinformation.
Come on, that’s pure ragebait… It’s not like it"s hard to search for all the different reasons… https://nosystemd.org/ collects a few in semi-coherent form. The short answer is: It combines a lot of previously independent systems responsibilities under one umbrella organization that holds decidedly strong opinions and is not exactly open to criticism.
2035? I’d have argued most of these things are already here or at least trivially close…
no privacy - Corporate overlords have been declaring us “post-privacy” for a looooong-ass time, and Governments and their enforcers have been chomping at the bit for at least as long, because they want in on the game
robot cops - Palantir Gotham plus semi-autonomous drones; It’s a question of degree, not of when.
robots displacing workers - Has literally been happening for more than half a century; The current LLM bullshit is going to give it another push, obviously.
robot rights - Well, are LLM companies just violating copyright or are LLMs simply ordinary artists that learn by looking at other folks art, just like their human forebears? (It doesn’t matter what you think, it matters what we as society ultimately make of that and I wouldn’t be optimistic)
criminals with hundreds of drones - They’ve been running humongous botnets for decades; If they see a business case for doing something drone-wise in meatspace they’ll absofuckinglutely do so today rather than tomorrow, and maybe they already are and we’re just not aware because it’s still flying under the radar.
If you aren’t expecting some variation of full-on Cyberpunk right now I honestly don’t know what you’re waiting for…
Somehow I expect a “GUI+Mouse is clearly better and thus your suggestions are worthless” response :-P
I wish people realized that there are vastly different possible approaches to different tasks and that one can be a lot less disappointed/stressed/angry by accepting one may have to learn a different paradigm once one has chosen to (semi-)commit to a new piece of tech…
Frankly: You come across less as “I am missing these features in many Linux file managers” and more like “I tried the default filemanager of my Linux distro and am angry the UX isn’t identical to that of Windows”. That’s not going to garner you much sympathy. Of the things you listed, I’d only consider a “preview” pane (that I’d rather not have, because of the security implications of having a separate potentially vulnerable parser that may receive less dev attention when issues are found) and maybe a “recent panel” (Not sure what one needs that for, I’d rather my system not track my actions so blatantly easy to find) actual features, and, yeah, quite a few Linux file managers can do something like those, obviously.
chuckle Oh noes!
Thanks for the clarification.
Well, I’d expect Meta to drag their feet as much as they can, tbh. So: Years and as many “regrettable” technical hiccups and UX inconveniences as they can get away with without having to pay too stiff a fine. Same as always.
I am aware of adverserial interoperability, but, frankly, it’s one of those ideas that make me chuckle benevolently. I don’t see much practical merit in it. As for Facebook getting big that way in the first place: I strongly disagree. They got big by being early, good enough to capture the zeitgeist, and then being as anticompetitve as they could. Just like Microsoft before them, for example.
Who ever promised that? Just because both use Axolotl/Double Ratchet? hat is far from enough. Not to mention that neither Meta nor Signal Messaging have any economic incentive to do it…
I personally go with QubesOS which uses VMs to compartmentalize. It doesn’t reduce the risk of a supply chain attack itself (fedora & debian by default), but if your VMs only contain the bare minimum for a given task the risk of having a compromised package installed is lower than in a full-featured system and any compromise is also contained to that VM.