linuxmemes

20880 readers

5 users here now

I use Arch btw

Sister communities:

LemmyMemes: Memes
LemmyShitpost: Anything and everything goes.
RISA: Star Trek memes and shitposts

Community rules

Follow the site-wide rules and code of conduct
Be civil
Post Linux-related content
No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago

MODERATORS

[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] 8 points 2 months ago

The fun part is that as a dev, you don't really know that either. It's just the file name of the executable. Anyone can rename that.
And even if it's not renamed, you still don't know, if your users need to call it with just hx or with ./hx or some other path.

Obviously, you should mention somewhere that the executable is likely called hx, but because that requires an explanation, there's certainly a tendency to not mention it very often...