this post was submitted on 07 Apr 2024
490 points (96.8% liked)

linuxmemes

21410 readers
729 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS
     

    It's not about the destination, it's about the journey.

    you are viewing a single comment's thread
    view the rest of the comments
    [–] affiliate@lemmy.world 1 points 7 months ago (1 children)

    i think i would’ve probably had to package the specific kind of vim that i needed, because i wanted neovim and a gui too or something. this was also like 3-4 years ago so its possible the documentation for this kind of stuff has considerably improved since i tried, or that there are now packages that make this sort of thing easier. and it’s definitely possible everything existed at the time and i just couldn’t figure it out.

    but i ended up with a similar feeling to the one you described: stuff is easy when you do it their way, using their tools; but things are very hard to do if you deviate from the path.

    i know this is just sort of an inevitable part of the design paradigm they use, and that everything probably works very nicely if you learn their language and the various ins and outs of the operating system, but i just wasn’t willing to commit that much to it.

    [–] itslilith@lemmy.blahaj.zone 3 points 7 months ago (1 children)

    I really like most of it and started to daily drive NixOS a few months ago, but there's still some very valid criticisms to be made. Lack of documentation is probably the biggest one

    [–] affiliate@lemmy.world 2 points 7 months ago (1 children)

    i would like to give it another try at some point because it seems like it will probably feel really nice to use once i get the hang of it. but the lack of documentation is pretty rough.

    i also think that for nixos, a lack of documentation is a much more difficult thing to overcome. other distros can piggyback off the arch documentation for most things, but that doesn’t work as well for nixos.

    [–] itslilith@lemmy.blahaj.zone 2 points 7 months ago

    that's certainly true. I'd like to help improve the documentation, but unfortunately I'm still pretty green at Nix myself, so there's not much I can do at the moment. But it seems to be picking up speed recently, so there's hope that with more people better documentation is coming soon