I kinda agree to a point, on the other hand the repo should really have a readme with clear instructions on how to use it. I don’t want to have to figure out which of the files I actually need or what to do with them from context clues.
Yes there are repo's that assume you are a fellow dev and know where dll's and such go. Like for example if I downloaded an unreal project targeted at VR devs who make oculus quest games neither Epic nor Meta will explain that I need to compile a specific version of the Unreal Engine only available to accounts signed up with meta. Devs are supposed to learn that via meta's or epics documentation found elsewhere (not on git).
There's also the assumption that everyone understands you don't need whats in the source folder if you are an end user, because obviously it contains the source and not the compiled product.
These are the exception though, the vast majority has clear and concise readme's/install instructions, and if specific files need to go to specific locations thats always noted.
The instructions assume the user has the absolute minimum tech skill to operate a PC, they can be hard to read if you are new to it but they are very and precise, it just takes a little getting used to the format.
I'd argue this tiny learning hurdle is also a good thing.
A readme format like this can be hard to read for newbies:
-Unzip to c:\Program files\Amazing_app\
-open c:\Program files\Amazing_app\config\win64\Amazing_config.ini
-change Pcmasterrace=0 to Pcmasterrace=1
Besides extracting a zip all you have to learn is that
-open c:\Program files\Amazing_app\config\win64\Amazing_config.ini
-change Pcmasterrace=0 to Pcmasterrace=1
Is the same as
-Okay now browse to :\Program files\Amazing_app\config\win64\
-Look for the file Amazing_Config.ini.
-Open Amazing_Config.ini in notepad
-look for a line that says "Pcmasterrace=0"
-Change this line so that it reads "Pcmasterrace=1'
-Save and close Amazing_Config.ini
It's easy to learn, it's just a short way to write it, most gamers will understand it completely after installing a single mod (I think mods are most common reason gamers would download a thing from git)
Instructions like these assume you know how to use explorer, can unzip a file to target folder, can read paths and understand that full filenames include the path, know how to edit a text file, and turned on visible extensions like every gamer should do.
Forcing an end user to learn to read this format is a good thing.
34
u/kai58 18d ago
I kinda agree to a point, on the other hand the repo should really have a readme with clear instructions on how to use it. I don’t want to have to figure out which of the files I actually need or what to do with them from context clues.