Justify bitreich-branches.md. - bitreich-documents - The repository to track the core bitreich documents.
HTML git clone git://bitreich.org/bitreich-documents/ git://enlrupgkhuxnvlhsf6lc3fziv5h2hhfrinws65d7roiv6bfj7d652fid.onion/bitreich-documents/
DIR Log
DIR Files
DIR Refs
DIR Tags
---
DIR commit 02ecbd1fe12e21cbff51611fc0271b883819dd63
DIR parent d2c974a7bc5e0768ec1bace8bb3637a961fe0ca7
HTML Author: Christoph Lohmann <20h@r-36.net>
Date: Fri, 26 Jan 2018 19:46:35 +0100
Justify bitreich-branches.md.
Diffstat:
M bitreich-branches.md | 43 ++++++++++++++++---------------
1 file changed, 22 insertions(+), 21 deletions(-)
---
DIR diff --git a/bitreich-branches.md b/bitreich-branches.md
@@ -1,15 +1,16 @@
# Bitreich Branches
-Bitreich has several branches which represent ideas of the current time where
-the to be done work to change the software around us can be categorized to a
-certain or certain tasks. New branches can be created just by your work on
-them. Please try to collect them to have at least an index.
+Bitreich has several branches which represent ideas of the current time
+where the to be done work to change the software around us can be cate‐
+gorized to a certain or certain tasks. New branches can be created just
+by your work on them. Please try to collect them to have at least an in‐
+dex.
## New Applications
* This branch can be abstracted further, when more software is produced.
* Write new applications.
-* The first goal is to change existing software. If not possible, rewrite as
- simple as possible.
+* The first goal is to change existing software. If not possible, re‐
+ write as simple as possible.
## Graphical Interface
* Work on new graphical interface ideas.
@@ -21,33 +22,33 @@ them. Please try to collect them to have at least an index.
## Abstractions
-Most libraries tend to be written in complex ugly programming languages, but
-they do their task well. The basic fact that the solutions are written in ugly
-complex programming languages forces some other programmer to rewrite a
-solution or some algorithm.
+Most libraries tend to be written in complex ugly programming languages,
+but they do their task well. The basic fact that the solutions are writ‐
+ten in ugly complex programming languages forces some other programmer
+to rewrite a solution or some algorithm.
* Write commandline interfaces for ugly abstracted software.
## Ugly World
-Big applications like for example libreoffice are enforced into our life by
-public request. Easier access is needed to the ugly world.
+Big applications like for example libreoffice are enforced into our life
+by public request. Easier access is needed to the ugly world.
-* Collect or write small utilities, polish them and give examples in how to
- access the ugly world out there in an easy way using the commandline.
+* Collect or write small utilities, polish them and give examples in how
+ to access the ugly world out there in an easy way using the commandline.
## Code Cleanup
-There is software out there which was written by some hobbyist but it does a
-very good job.
+There is software out there which was written by some hobbyist but it
+does a very good job.
* Collect small application, polish them and make them reusable.
Other software is really big but only got big by applying metaphors from
-university which were never really understood but are annoying our life just
-by their existence.
+university which were never really understood but are annoying our life
+just by their existence.
-* Find software you daily use, find ugly for example object abstractions and
- remove them using a good functional style. Then try to get the patches into
- mainline.
+* Find software you daily use, find ugly for example object abstractions
+ and remove them using a good functional style. Then try to get the
+ patches into mainline.