789
submitted 3 months ago by Flax_vert@feddit.uk to c/selfhosted@lemmy.world
you are viewing a single comment's thread
view the rest of the comments
[-] AstralPath@lemmy.ca 92 points 3 months ago

Honestly, as a newbie to Linux I think the ratio of well documented processes vs. "draw the rest of the fucking owl" is too damn high.

The rule seems to be that CLI familiarity is treated as though its self-evident. The exception is a ground-up documented process with no assumptions of end user knowledge.

If that could be resolved I think it would make the Linux desktop much more appealing to wider demographics.

That said, I'm proud to say that I've migrated my entire home studio over to linux and have not nuked my system yet. Yet... Fortunately I have backups set up.

[-] hactar42@lemmy.ml 20 points 3 months ago

Don't forget the situations where you find a good blog post or article that you can actually follow along until halfway through you get an error that the documentation doesn't address. So you do some research and find out that they updated the commands for one of the dependency apps, so you try to piece together the updated documents with the original post, until something else breaks and you just end up giving up out of frustration.

[-] Someonelol@lemmy.dbzer0.com 6 points 3 months ago

That sounds an awful lot like modifying an ESP32 script I've been trying to follow from a YouTube tutorial published a while back. Research hasn't uncovered anything for me to troubleshoot the issue so it's a really shit experience.

[-] Archer@lemmy.world 2 points 3 months ago

Pre-systemd tutorials 💀

[-] winterayars@sh.itjust.works 1 points 3 months ago

That shouldn't be too bad if you understand systemd though, right? Or is there something weird i'm missing? Do you have an example guide that illustrates the problem?

load more comments (10 replies)
this post was submitted on 02 Aug 2024
789 points (96.7% liked)

Selfhosted

40383 readers
363 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS