this post was submitted on 19 May 2021
15 points (100.0% liked)
Asklemmy
44847 readers
911 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The thing about configs vs C is that many apps have their own config conventions, they deviate a lot from one implementation to another and you have to study their documentation (if it exists).
C on the other hand is one standard, some things differ in conventions in libraries, but most standard ones hold to one convention and you may apply solution from one adaptation to different suckless programs.
Of course it requires knowlege of C and the technology application works on, but that's not entirely true.
Thing is while other configs have their own documentation, C language has many books, standards, articles code snippets et cetera, which is C's documentation (sort of).
I guess it is inherently hard to understand for regular individual that while configurable apps explicitely direct you to the config documentation, suckless software doesn't do that with directing to C books because that should be merely obvious.
Suckless software is definitely not for all and it isn't universal (in some sense) but that's how it can stay simple, elegant and maintain small codebase.
Some additional info and explanations: