ibitreich-manifesto.md - bitreich-documents - The repository to track the core bitreich documents. Err bitreich.org 70 hgit clone git://bitreich.org/bitreich-documents/ git://enlrupgkhuxnvlhsf6lc3fziv5h2hhfrinws65d7roiv6bfj7d652fid.onion/bitreich-documents/ URL:git://bitreich.org/bitreich-documents/ git://enlrupgkhuxnvlhsf6lc3fziv5h2hhfrinws65d7roiv6bfj7d652fid.onion/bitreich-documents/ bitreich.org 70 1Log /scm/bitreich-documents/log.gph bitreich.org 70 1Files /scm/bitreich-documents/files.gph bitreich.org 70 1Refs /scm/bitreich-documents/refs.gph bitreich.org 70 1Tags /scm/bitreich-documents/tag bitreich.org 70 i--- Err bitreich.org 70 ibitreich-manifesto.md (4358B) Err bitreich.org 70 i--- Err bitreich.org 70 i 1 # Bitreich Manifesto Err bitreich.org 70 i 2 Err bitreich.org 70 i 3 ## Introduction Err bitreich.org 70 i 4 Err bitreich.org 70 i 5 We live surrounded by complex software which receives new versions and Err bitreich.org 70 i 6 updates day after day. RAM and CPU consumption never reduce, they in‐ Err bitreich.org 70 i 7 crease. Software still provides the same features from years ago, but Err bitreich.org 70 i 8 everything looks new. This is called »advance« in the new speak of pro‐ Err bitreich.org 70 i 9 prietary software development. Err bitreich.org 70 i 10 Err bitreich.org 70 i 11 This has to change! Err bitreich.org 70 i 12 Err bitreich.org 70 i 13 ## Suckless Err bitreich.org 70 i 14 Err bitreich.org 70 i 15 Suckless failed. Err bitreich.org 70 i 16 Err bitreich.org 70 i 17 ## Consumerism Err bitreich.org 70 i 18 Err bitreich.org 70 i 19 Consumerism is the ability of persons to lose their skill in thinking on Err bitreich.org 70 i 20 their own, producing things, applying logical and practical ways of be‐ Err bitreich.org 70 i 21 having. This disease of consumerism is striking the devices and comput‐ Err bitreich.org 70 i 22 ers we humans produced to make them not scale in the possibilities they Err bitreich.org 70 i 23 could be used for. Computers can do things consumers cannot want and Err bitreich.org 70 i 24 imagine before they use the computer for something. The market economy Err bitreich.org 70 i 25 of demand and supply does simply not work here. Err bitreich.org 70 i 26 Err bitreich.org 70 i 27 ## UNIX Principles Err bitreich.org 70 i 28 Err bitreich.org 70 i 29 In the beginning of the development of software principles were intro‐ Err bitreich.org 70 i 30 duced how to create software which can be reused in ways the original Err bitreich.org 70 i 31 developers never imagined. Small utilities are combined using simple Err bitreich.org 70 i 32 pipes, speaking to eachother, just doing one task well. Err bitreich.org 70 i 33 Err bitreich.org 70 i 34 ## Dawn Of Ugliness Err bitreich.org 70 i 35 Err bitreich.org 70 i 36 By not applying this methodology to its extreme, by trying to force new Err bitreich.org 70 i 37 features of computers into the UNIX principles, binary blobs evolved into Err bitreich.org 70 i 38 a complexity no young programmer can understand. They are forced into Err bitreich.org 70 i 39 the industry due to »life events«, where they are degrading to robots Err bitreich.org 70 i 40 which only apply what they learned at programming school (e.g. life, Err bitreich.org 70 i 41 university ...). This circle is producing even bigger binary blobs. Err bitreich.org 70 i 42 Nowadays this evolved into shipping whole operating systems in images Err bitreich.org 70 i 43 which you run separately. Err bitreich.org 70 i 44 Err bitreich.org 70 i 45 This has to end! Err bitreich.org 70 i 46 Err bitreich.org 70 i 47 ## Bitreich Err bitreich.org 70 i 48 Err bitreich.org 70 i 49 We form a movement to improve our daily software life. Software has to Err bitreich.org 70 i 50 not misbehave, it has to follow our rules, it has to be reusable, it has Err bitreich.org 70 i 51 to be easily maintainable, it has to provide its recompilable source and Err bitreich.org 70 i 52 it has to be easily understandable. Err bitreich.org 70 i 53 Err bitreich.org 70 i 54 ### Bitreich Principles Err bitreich.org 70 i 55 Err bitreich.org 70 i 56 #### KISP – Keep It Simple Perfect Err bitreich.org 70 i 57 Err bitreich.org 70 i 58 Software needs to do one thing well / perfect. Err bitreich.org 70 i 59 Err bitreich.org 70 i 60 #### Commandline Interfaces Err bitreich.org 70 i 61 Err bitreich.org 70 i 62 Always add a commandline interface to your software. Graphical User In‐ Err bitreich.org 70 i 63 terfaces are for sissies. Pipes are welcome. Err bitreich.org 70 i 64 Err bitreich.org 70 i 65 #### When Possible Use GPLv3 Err bitreich.org 70 i 66 Err bitreich.org 70 i 67 The signs of MIT‐appearance in the community is based on the circle of Err bitreich.org 70 i 68 complexity introduced into the minds of libre software programmers by Err bitreich.org 70 i 69 their oppressors transferring money to their bank accounts every month. Err bitreich.org 70 i 70 Your software is used in war machines to kill people and the companies Err bitreich.org 70 i 71 will never give back. So enforce GPLv3, it’s needed. Err bitreich.org 70 i 72 Err bitreich.org 70 i 73 #### Users Are Programmers Err bitreich.org 70 i 74 Err bitreich.org 70 i 75 Software should be written for programmers, which means the code is the Err bitreich.org 70 i 76 documentation, it should be easy readable, low abstraction levels should Err bitreich.org 70 i 77 be used (OOP sucks most of the times) and a simple Makefile to build ev‐ Err bitreich.org 70 i 78 erything needs to be present. This is subject-oriented programming. Err bitreich.org 70 i 79 Err bitreich.org 70 i 80 #### Bugreports Are Patches Err bitreich.org 70 i 81 Err bitreich.org 70 i 82 Bugtrackers are obsolete. Whenever you find a bug, fix it. The other Err bitreich.org 70 i 83 principles make it possible for you to send a patch instead of a report. Err bitreich.org 70 i 84 Err bitreich.org 70 i 85 #### Straightforward Documentation Err bitreich.org 70 i 86 Err bitreich.org 70 i 87 There are all kind of tools like javadoc, info etc. which fragment the Err bitreich.org 70 i 88 way to find useful information. All software should provide manpages. If Err bitreich.org 70 i 89 you need more features than manpages require, rethink what you are try‐ Err bitreich.org 70 i 90 ing to document. Manpages have a well defined structure which makes Err bitreich.org 70 i 91 finding and extracting the required information easier and uniform. Err bitreich.org 70 i 92 Err bitreich.org 70 i 93 #### Applications Can Be Done Err bitreich.org 70 i 94 Err bitreich.org 70 i 95 When a project solves a problem, keep it done and declare it so. New Err bitreich.org 70 i 96 problems are solved by different projects. Err bitreich.org 70 i 97 Err bitreich.org 70 i 98 #### Freedom Of Language Err bitreich.org 70 i 99 Err bitreich.org 70 i 100 The software world is spammed with new revolutionary programming lan‐ Err bitreich.org 70 i 101 guages every month. Choose whatever you need to solve your problem, but Err bitreich.org 70 i 102 keep to the above mentioned principles. Most new programming languages Err bitreich.org 70 i 103 solve a non‐problem the principles of bitreich solve. Err bitreich.org 70 i 104 Err bitreich.org 70 i 105 #### Do Not Hate Your Userbase Err bitreich.org 70 i 106 Err bitreich.org 70 i 107 Corporations start to hate their users, sell their data, reduce features Err bitreich.org 70 i 108 to make profit. Projects adhering to the bitreich principles do not Err bitreich.org 70 i 109 follow this. Err bitreich.org 70 i 110 Err bitreich.org 70 i 111 #### Inevitability Of Change Err bitreich.org 70 i 112 Err bitreich.org 70 i 113 These principles can change, based on the consent of the bitreich elite. Err bitreich.org 70 i 114 Err bitreich.org 70 .