Thee was never the purposeful simple choice about software packages. It was either printf or bloat, no in between. The confusion about setting up bloat is easy to solve, but the options lose priority. An open software process start as a need to get the simple done. Great, they have just enough to easily get 65% when you had 20% of the function. Then the add ons start and bloat is when the functions lose priority, the simple necessary is no longer observable amongst the bloat of options. User confusion and racing the wheel happens.
I am putting a stop to that, am connecting all the snippets and putting them on the Bus. The software world I want, collect snippets and organize them into a functioning group. Like the ncurses thing vs printf, why the huge jump in complexity? And a thousand line file of reasonable polygon fill,arcs and ext for xcb, why the files and files. Why does loading a tool set inevitably mean digging down five levels of empty directories.
From the lab, you want in and out of the computer; never could get that, until this code i have. This code allows me to collect any snippet with a main() interface in linux, and that is a huge set. And they all have APIs, just fine in he linux man pages.
No comments:
Post a Comment