this post was submitted on 23 Aug 2024
447 points (94.6% liked)

linuxmemes

20880 readers
5 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
447
My impression of github since switching to Linux (lemmy.world)
submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]
122 comments fedilink hide all child comments
 

I've been transitioning to Linux recently and have been forced to use github a lot when I hadn't much before. Here is my assessment.

Every github project is named something like dbutils, Jason's cool photo picker, or jibbly, and was forked from an abandoned project called EHT-sh (acronym meaning unknown) originally made by frederick lumberg, forked and owned by boops_snoops and actively maintained by Xxweeb-lord69xX.

There are either 3 lines of documentation and no releases page, or a 15 page long readme with weekly releases for the last 15 years and nothing in between. It is either for linux, windows, or both. If it's for windows, they will not specify what platforms it runs on. If it's for Linux, there's a 50% chance there are no releases and 2 lines of commands showing how to build it (which doesn't work on your distro), but don't worry because your distro has it prepackaged 1 version out of date and it magically appears on flatpak only after you've installed it by other means. Everything is written in python2. It is illegal to release anything for Mac OS on github.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 27 points 2 months ago (1 children)

When I first moved to linux I felt this same way. It gets better. Now days I fucking love those 15 page ReadMes and I'm not bothered if there's no steps for my distro. The sheer volume of documentation surrounding linux packages is insane. There's often a ton of ways to configure and manage the to fit your needs. That freedom is what I love so much about linux.

As for the ones with 2 lines, I don't think I've seen that as much. I generally would avoid them unless the source was clear what the project did.

At any rate there will come a day when it starts to click. It's just a marathon not a sprint.

[โ€“] [email protected] 3 points 2 months ago

Learning to read docs is basically learning how to learn. If good docs exist and you have the skill of reading them, your life will get significantly easier.