My impression of github since switching to Linux
My impression of github since switching to Linux
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.
As someone who works fairly extensively with all three major platforms... You're definitely wrong about macOS here. Almost everything on GitHub that works on Linux also works on Mac, aside from GUI applications which are often more OS dependent. The readme pages often just lump Mac and Linux together as they can be pretty similar, especially for things written for interpreted languages (python) where it's often literally the same.
I recently bought a MacBook Air M1 and I came at it from a classic "ThinkPad with Fedora on it" Linux nerd perspective. I got given a Mac at work a couple of years ago, and I warmed to it. I agree that Macs are great tools for DevOps work. I used to think they were just for posers but I've been converted.
I find shit for macOS on GitHub all the time lmao.
People ask for money from Mac users.
They bought the hardware... So they'll buy the software too!
in other words your impression of a microsoft run website with the least foss example of git, since switching to linux
Correct! It's where web searches bring me so it's what I use until I git gud enough to learn how to find things better.
OP listened to some trolls and unironically picked Gentoo as their first distro.
Yeah. Pretty much.
The worst part about free Linux programs is that they have 0 visibility or marketing.
Almost everything I know of is from other people whom are far more passionate about keeping track of the foss landscape.
Sorry, guys I don't check AUR every night before bedtime.
Be the change you want to see in the world.
I'm currently in the process of updating Slackware's documentation, some of which hasn't been touched in 12 years.
It's completely out of date, so no one uses it anymore.
And because no one uses it, no one updates it.You're doing "Bob's" work son, thank you for your service!
As a devout SubGenius myself it is my destiny to use Slackware one day but alas I fear it is currently above my skill level, more documentation will help people like me greatly! PRABOB!
Where's the meme
GitHub is a place you can use to easily put a copy of your code online. Many people just want to build a working solution and move on. Building a useful GitHub project, with fancy stuff like releases, is work that isn't really solving any issues. Many people don't like doing it. Many people especially don't want to invest time in proprietary solutions like GitHub. They might not even accept pull requests on GitHub.
Quality assessment though 😄
Just a reminder to https://sfconservancy.org/GiveUpGitHub/ and that GitHub is Microsoft.
One good alternative: codeberg.org
Tell this guy
I have 2 plugins for rofi on Linux and it's true, no releases - best I can do for you is tags, take it or leave it
If your distro was arch, you most likely have the nightly build available on the AUR
Aur and pacman are 90% of why I use arch.
Also fyi to OP: never install software system-wide without your package manager. No
sudo make install, nocurl .. | sudo bashor whatever the readme calls for. Not because it's unsafe, but because eventually you're likely to end up with a broken system, and then you'll blame your distro for it, or just Linux in general.My desktop install is about a decade old now, and never broke because I only ever use the package manager.
Of course in your home folder anything goes.
never install software system-wide without your package manager.
What's the alternative of
sudo make installandcurl | sudo bashif a package is not available in AUR? I am unfamiliar withmake install.Also fyi to OP: never install software system-wide without your package manager. No
sudo make install, nocurl .. | sudo bashor whatever the readme calls for.And that is why Linux isn't ready for mass adoption.
I had to fuck around for hours to make my wifi adapter work and everyone was referencing this one project on GitHub and the way to install it and what actually worked was to sudo make install.
You're the first person I see that's saying not to do that, I had to use instructions from the Linux Mint forum to try and get it installed the first time and no one mentioned that, I found alternative projects but none of them had clear instructions "You must have installed X, Y, Z first" without any explanation how to do it.
So, for new users, Linux is all about blind trust in strangers to make stuff work and if you have no interest in learning programming that's what your experience will continue to be.
How the fuck do you have a decade old arch installation? I have to reinstall it about every half a year because something breaks and its to complicated to fix it so I just choose to reinstall everything. In the 18 Months or so that I used Arch I had to reinstall it about 4 times. I don't even install that much stuff and I also don't go absolutely wild with configuration, but Theres A lot of stuff breaking in my system.
I also got used to just ignoring problems because I'm to lazy to reinstall everything or spend hours upon hours fixing my system.
Absolutely. Funky installs go in ~/bin. (Ok, plus the valve directory)
Everything else comes from standard repositories.
😁I prefer yay to search and install stuff from AUR using a single command 🥰 and if you choose the endeavour flavour of arch, then you have yay preinstalled 😋👌🏻
Really love arch and the AUR. I've been tempted to get nix set up for the rare cases when there's no AUR package or the AUR package is unmaintained. I figure if there's no package in the AUR or nixpkgs, it's probably not worth running.
I yet hope to find a unmaintained arch package to have a reason to write my own PKGBUILD file😁
Learn to read code (git gud) /s but it's the only way to be sure (nuke from orbit)
Or, look at the stars...
Or, look at the stars…
Today my horoscope tells me to not use github in particular and avoid compiling any code in general.
K, I asked for that apparently, well played...
Was talking github stars though.
That's what I've been trying to tell my boss for the last 6 months...
Wait until you install some package and then scratch your head not knowing how to run it.
If I install a package, I don't even know what it installed and/or where.
I can't believe Linux can't even tell you what it installed where - even Windows can do that.
Most package managers have a way to list all the files a package will install
Helix Editor did this to me. They have so much documentation on their site about how to use the editor, how to extend it, theme it, etc., etc. What they didn't seem to document, though, is that the binary is named
hx, nothelix:/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 justhxor with./hxor 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...When I'm confused like that, I check https://packages.debian.org and open the file list for the package. That way I know what binaries are installed.
g7KQoYF8KCagJf0b5o90YSXepATfbmfZJVXolEQhOm81htnxqJqHzNEuCuKO1JzP Z8xV1YZPyFy5vYNUsGmujCDTS91ZXM5Sz3TWuUiqFmMHUc2wa9mmpKRUp9pR8idI vHrv8c5ieuLEofvq7QObYrTPA5A3xrG82CLI3wsBD7CVsstEyvSU7zT2s884qkJ8 gWgevSqT6Z84ApvHKSrFCcy8MERPPKsQHzwNkb54eoEoNbNWupGU8WlPo1NtTv94 UyKRGtUqKyn9DXNwYdvY5cB9qodPjfq3jQ1NzqeiQzNlSOwEIeKyHp0Bph2xgP44 qGbwNbffyFmYkmCAC2E03ppv7b3yz5qIIehcr7NECFlkESRTgkWi14PfhvLfLHna bCgih77yfzco17aegRVvZc5j9YfcXGh2ImCR2ltTVK7whXgRHlpzlLKVV3OD73oa jffqjihDegZVe6QbHMu9ULxRmQyQoJIQYqKKe9nxCf5TNJpnLGbu0dGw4OvDObuo pHP3N7sFd1vILXGzu6Sk7pmZmYgMZxkvSizllWqIK2GXv4CzUbTJ4zWsKx4VUPHF rakm9O23lVgf8ljtAWwezGQxtSfPmnr2UAmeRmGKlNiy7WjYzQOx0mEe372u974T yt6vRz2hPAuWe6apVPzL5HvpYbCNg0Py93lEHshLpNSnbNJnxSLZHibnulvgwPVd YYETL7OilsMYoYsJ3tQQH109II0ySUjhRrZfB83E8doN5F5GQXTyyFjab3p6sFoX NOl4TW1l4p3eEPbI101qOUFMSHMjMnsRrocd51LvtQLr2Lq8RFiDZ5yPVF4O7Jhy ITdIfBLarSlQy4yvCJvFmwdQYkNNo0EI1vLGmt6tc7oPHxOdKWGkvUd1Q1NzTXPl YypVuuMvyZelHuRZC2KiowuzmV6d8cfTEniyozpzJFbzGKeR7KbQXvvcwr0JEhD0 d7r926p7tnZyRRwVnhkJvORrAxoRfxvdhb00qjq8MgwDWvRQxXgs4ZyYfzpkYsVA UdbRJBTIgQP95feYkp8gTN1niS4tQB33uFiC75Yc6lek624t1cLn4kUO5ffINV1k eFRv2KCsPy0mPL8SGPNdYAipMTlMkenOupEJ3wGifJg6NGLdQiyrTZD4a3OeZ9Kv 3I1ams8ENnoacRL1eQZTHiciWxQApi2b7HzF0t9DpS93xsggYMiAoSkNsNk3FHje EfJxF4vcFSJpeCvnG61j31qCpByNye7LgL8ODFyvZ9dK3vudpg43vB4x6mZbVYXR GPv1WBbzNiH0h97YL2IfFF7rUlVzu7opdPHXGp0A7nIP0gKyE6bGFVc5lRIVemTW TW3j09LFRh0HrWyMinoc1a037YCwYrudEjraL4BSNgC2iwOLVzFUdWDnEKUG2sU8 udUuYh4jG3v5mTbO8FZQkxBdPYkihwWZmQ0sn6WOcePez2AJpFJe6oXY97pZiK28 McVjJmPzyr6g2dT5lS9z2rHh3zSf8sXUt62OQ16pTI5QMPvvpqxvh2tSkGUW1qMd 5NqUL8iEosuhj3NZCx81oSFToyCtf6NYO905q2Dg76N1Bgz2x9E7br1d6sOLWqQE ozuZVzi4lGYhYD61kNsjk7a17b1UROvdKxl48cmAsmPpe9zxbITWHL974V7j6YvB F5rLT6BWVuuXiWp2VNGTPQ0rqLYvD2Wh3v9L9hmxmSTd30BXCTwXajbay2D7GHpd MBr1kaPhWATm3JbYcf4H3WR00PoDreKWQXw5Lwv9nDQFlvK2uJvZxifkM6Ug3GGw uuLvngnnQ9YPCdRcZeFFBTmlSLh9v8aHk6ZWVgM1zDG1LsBkVw6pOwKZnBXSdR6w 9o6k7GMpgYYXisZaEjJ7TRnjked41PUDPGllA9JKydDRAYdueyCyyhOcEk9xTSVq skw1Nk34QUUsKeldaMperlj3fKzmRiLqnOgfZJKebsJW8DVck6krXkzgkFXp2Tew sP97OVhGl4EX8OcuUJwmTFoHVhJE1dt54fGeGFgD6vCp5YFsKeVINfgB1atGZEbk
Then think “I’ll figure it out later” but you never do. Only to be reminded of it a month later when you happen to see it scroll by in an apt-or-whatever package upgrade.
“Oh yeah, I forgot about that. I should check that thing out again” you think to yourself. But you never do. Repeat for eternity.
Devs who make the -h command actually useful are modern day saints.
I think they meant you don't know what the binary is called because it doesn't match the package name. I usually list the package files to see what it put in
/use/binin such cases.
Yeah you want to know the funny thing: I ended up on Github a lot when I was new to Linux, but that has happened less and less over time and I think it's due to two unrelated factors:
-
I have assimilated. As a Microsoft emigrant, I was used to doing things a certain way, there were things I didn't know about Linux, I hadn't really chosen the hardware I owned for Linux compatibility, etc. So I kept having to go get weird device drivers and weird little software packages to work on my distro and open my old files and such. But as I've gotten used to the ecosystem, replaced my old hardware with that which is Linux compatible out of the box etc. I've needed to do something weird less and less often.
-
Flatpak and Appimages have risen in popularity. It's easier to get the software you need, that runs on your distro, that is up to date and modern, even if it's not very popular. Because a variety of software is available in these formats it's easy to get what I need, be it commercial software, esoteric little stuff for my niche pastimes, etc.
-
Just a small (or maybe big?) tip for you 🙂
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
There's a tool called Distrobox.
You can install it (via CLI I think?), and then manage it the easiest graphically way via BoxBuddy (available in your Software Center), or just the terminal if you prefer it.With it, you can screw all those "Doesn't work on my distro" moments.
You're on Linux Mint? No problems, here's the AUR for you!
✨✨✨ BONUS: Your OS won't break anymore randomly due to some AUR incompatibility, because everything is containerized! ✨✨✨
Even if you run Arch, use it to install AUR stuff. Or Debian/ Ubuntu, add PPAs only via Distrobox.
It's absolutely no virtual machine. It basically only creates a small, lightweight container with all dependencies, but it runs on your host. Similar to Flatpaks.
You can also export the software, and then it's just like you would have installed it natively!
Your distro choice doesn't matter anymore. You now can run any software written only for Suse, an abandoned Debian version 10 years ago, Arch, Fedora, Void, whatever. It's all the same.I hope that was helpful :)
Oh cool, I'll have to check it out! Thanks!
That's great, but it should still be possible and well documented for people to run things natively. Some people want less bloat for technical reasons (maintaining a product with very little storage or memory). Tinycore Linux is my go-to example of the benefit of keeping things lightweight for a purpose.
When you're maintaining a product that is based on linux, you're surely qualified to port that thing to your platform yourself.
Open source developers are thanklessly giving away their work for free already, and for the many things where there's just a github page it is just a one man show run in spare time. Don't demand them to give away even more of their time to cater for whatever distro you're using, just because you are not willing to invest the time to learn how linux works and also not willing to give a way a few megabytes for the dependencies they're developing against.
All the discussions about things like distrobox and flatpak where linux novices express their dissatisfaction due to increased disk space are laughable. In the linux universe sole users have no power in deciding what goes, they do not pay anything and at worst pollute the bug tracker. Developers are what make up the linux universe, and what appeals to them is what is going to happen. Flatpak is a much more pleasant experience to develop for than a gazillion distros, hence this is where it is going, end of story. As a user either be happy with wherever the linux rollercoaster goes, or - if you want to see change- step up and contribute.
Each to their own. Linux is, in my opinion, about choice. If one prefers everything to be ultra minimalist, native and lightweight, then that's fine.
I personally just find to be Linux' most overlooked strength is containerization. It's one of the main reasons why most servers run Linux, because of things like Docker. On the desktop, containers are way underutilized, but that's now slowly changing with things like Flatpak or Distrobox.
A distrobox container is technically more bloated than a native install, sure, that's correct.
But, in my opinion, it's like saying "Drawers and closets are bloat for my apartment. I throw everything on the floor." Yeah, now you have less things in your room, but it looks like shit, you can't find anything and you fall over your tubberware that's mixed with your underwear and shampoo.
Having everything collected in a container only costs me a few hundred MBs and a small amount of RAM if needed. But, literally every PC has more than 50 GB hard drive space and 8 GB RAM. If your system slows down because of one container, then your PC is the problem, not distrobox.
That absolutely doesn't mean we should stop optimizing software of efficiency. But it can help us to spend our time on more important stuff, like fixing bugs or adding new cool features.
I really love Flatpak because of that. Sure, it has some drawbacks, but as soon as more devs support Flatpak officially, and iron out some issues we currently have, like misconfigured permissions, they're (imo) the best package format. Why should a distro maintainer have to apply every software change to their package format? That's needlessly duplicated work.
Interesting how we live in different bubbles ✌️
Yes the world of github and linux is vast and I am like a newborn baby. I hope to visit your bubble one day my friend.
My bubble is mostly lm, which comes in two flavors:
(1) useless repo made up entirely of jupyter notebooks and 28363 requirements achieved via pip freeze
(2) simple, friendly, well documented, runs
I release a lot of my software in GitHub and I’m offended at how accurate this is.
Use docker
I do in my server! But I didn't even consider it in terms of a workstation.
your distro has it prepackaged 1 version out of date
And the only reason you wanted to install the thing is because it's a prerequisite for some other thing you wanted to install, which requires the latest version.
The story of yt-dlp and ffmpeg on my raspberry pi.
God, I hate that.
Then you do a clean up day and start removing shit you don't know what is or even use. Then a few weeks later something doesn't work and you don't know why, but it was probably something you removed, so you go through the entire git journey again, throwing and taking the exact same punches to get things running.
What's your bubble of interests? I mean I've seen Github projects where that description fits very VERY well. Usually when I'm attending to some very niche hobbies. Or try to get some exotic electronics from 20 years ago running again... With the everyday tools it's most of the times some active community and I copy and paste the 3 commands and I have it installed successfully.
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.
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.
How did you describe my repositories so perfectly?
While I do see most of the listed stuff happened to me before, they only appear once in a while and it's often just one sentence in the list is true. I think OP is trying to make an exaggerating slander where it's extremely unlucky to have more than 5 sentences is right
You get used to how to find the right way of doing stuff. If you're still in the Windows biased search results space, everything FOSS is made to look sketchy. Those search results are not deterministic. That bias is intentional. Eventually Microsoft stops biasing you or bribing Google to do the same and your search results will be better. Then you stop using the search results all together for the most part. You'll figure out that the ways you did things in the past were inefficient and usually wrong. There are better ways that you'll discover and those repos are self hosted or on gitlab or elsewhere. You eventually just use RPM fusion, or you setup distrobox with Arch and the AUR, or you toss on the Nix package manager and start using flakes. The vast majority of my initial headaches were due to trying to replicate Windows workflows. Then I learned all of that was weird and pretty backwards.
Guy, nobody is making FoSS pages and documentation hard to find or read. The developers take care of that themselves. You've invented a story that had no basis in reality. At least the other posters admit it's lack of time and some overworked dude in his basement.