6

What the fucking shit, Arch. In what universe/reality is a user expected to easily/quickly address GPG/PGP bullshit when they install Arch. It's already hilarious enough as it is for the user to input every single command in order to install the thing. -- That's actually what's great about Arch; you get return and assurance from each command. -- I understood the fact that you need the latest ISO release in order to even install Arch, but now, if you decide to pacstrap linux-hardened, or god forbid, a package that is who knows what, less maintained?... fuck knows what will happen.

The fantastic part, is that you can't do shit when you're in an arch ISO install. All of the simple and possible solutions that involve GPG DBs/keyrings/etc require you to have the all of the shit installed already; which is fucking impossible if the package manager is bitching about keys not being imported. The most fantastic part, is that there is probably some complete bullshit, ultra-exclusive command or simple solution that will fix this crap. - And if you even dare ask the Arch forums, you'll be branded as a "newbie" and sentenced to read the fucking wiki. - ??? -- That's not a fucking good thing. -- The majority of people who are installing Arch right now, are people who are installing it for the first time, and chances are, most of those people have no fucking clue what is happening; they're learning what is happening. Furthermore, they're probably the kind of people who aren't inclined (or they don't know how) to scour Google or the Arch forums for answers to vague, lazy-ass error messages. The whole point of this thing is show and confront the user about what they're installing and what they want on their computer. Holy shit. This is all the more reason to ensure that total, stupid, ambiguous bullshit errors do not occur. -- "error: key "dogshit master <dogshitmaster@dogshit.org>?" could not could not be imported". -- That's it. That's the error in it's entirety. For a fucking OS install. What the fuck.

Comments
  • 5
    If you don't know or don't want to learn, why do you use Arch then?

    The same for the installation: That's on purpose.
  • 2
    Installing Arch is from and for people who have nothing to do with their lives. Regarding an OS installation as skill in 2020 is ridiculous, and if this even needs skill, it's crappy software.

    Also, the "devrant" tag is not for "developer rant" because there are ONLY developers here so that EVERY rant is a "developer rant". It's for stuff related to devRant itself.
  • 2
    Arch's install is difficult, and it would have taken me ages without a laptop on hand to look things up and to walk me through the process. I don't think anyone claims that it's easy, or comparable to any other OS install. But there's a reason. The final product is an operating system that will do whatever you want. That state is worth the difficulty to me a hundred times over.
  • 0
    @molaram Well yeah most devs don't want to learn e.g. how to make shoes. They just want to put them on and fucking walk. BUT! with that (completely reasonable) approach, Arch doesn't make too much sense.

    If Linux, I'd go with Mint anyway, and I'm already cool enough even with Windows so that I don't give a shit.
  • 0
    @sbiewald I know what Arch is. I've been using is it for the last three years.
  • 1
    @Fast-Nop The arbiter for what people should do and not do with their lives.
  • 2
    @molaram Then they just should not use arch, but any other Linux distribution that at least aims to be user friendly.
    Arch does not, on purpose.
  • 1
    @sbiewald It's "on purpose" for a reason. I fucking said it in my rant. -- It's to show/highlight/confront the user about what thing they're installing on their computer. When you install any other popular Linux dist, whatever packages, are, whatever packages; no need for you to think/worry about anything... computer works. -- I'm not even talking about the fact the Arch is hard to install or whatever; it's a specific error/nuisance in the install.
  • 0
    Been there, tried to install arch 7times (see me other rant) but during that time I learned (since arch forced me to) on what is actually going on. Which is very valuable (at least for developers/computer enthusiasts).

    Point is: yes, it’s not as easy as ubuntu, yes it’s on purpose, yes it takes time, but when you got there, you’ll be proud and will most probably be able to maintain the system and fix bugs/errors/system errors. (Whereas back when I used ubuntu/fedora, I was just reinstalling the entire OS...)
  • 3
    @Fast-Nop

    Or maybe, just MAYBE, there is a market for people who LIKE using a computer. People who LIKE linux, and people who LIKE putting in the effort to get things the way they want. I understand you prefer not to tinker, and have other interests. Great for you! Parade for you! But your personal opinions do not summarize the position of everyone in the world. Nobody made the assertion that most devs like Arch. Anybody who would say that would be insane. But that's the non-statement to which you are responding. Leave the straw man alone. He's had enough.
  • 1
    If you want everything to be automated, use something else and expect the automatic solution to be okay at best. Regardless of what year it is, general solutions will never be as good as specific solutions that take into account your specific situation.
  • 0
    @Lor-inc Oh, absolutely. I am entirely and hopelessly unaware of what year it is right now and therefore, I "want everything to be automated". I chose Arch because I was expecting that everything will be "automated".
  • 0
    @bahua I agree. That's why I like it. I've used it for several years. It forces the user to figure out every single thing about what they're installing on their computer.
  • 1
    Manjaro
Add Comment