Update
This commit is contained in:
parent
8dbbd1acb0
commit
367af6e637
22 changed files with 1863 additions and 1829 deletions
2
bloat.md
2
bloat.md
|
@ -81,7 +81,7 @@ The **path of [degeneracy](degenerate_software.md)** drawn in the graph shows ho
|
|||
|
||||
Please note there may arise some disagreement among minimalist groups about where the band is drawn exactly, especially old Unix hackers could be heard arguing for allowing (or even requiring) even trivial programs, maybe as long as the source code isn't shorter than the utility name, but then the discussion might even shift to questions like "what even is a program vs what's just a 10 characters long line" and so on.
|
||||
|
||||
As a quick [heuristic](heuristic.md) for judging programs you can really take a look at the lines of code (as long as you know it's a simplification that ignores dependencies, formatting style, language used etc.) and use the following classes (basically derived from how [suckless](suckless.md) programs are often judged):
|
||||
As a quick [heuristic](heuristic.md) for judging programs you can really take a look at the [lines of code](loc.md) (as long as you know it's a simplification that ignores dependencies, formatting style, language used etc.) and use the following classes (basically derived from how [suckless](suckless.md) programs are often judged):
|
||||
|
||||
- < 10: Extremely small but may be useful, may be also too trivial for such small size to be justifiable, can aim to be completely bug-free. Example could be the [cat](cat.md) program.
|
||||
- 11 to 100: Very small, can be debugged to a great level, many greatly useful utilities, e.g. [compression](compression.md) programs, may fit this class.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue