Smaller and fresher.
297 karma · joined May 24, 2012
Smaller and fresher.
Because it is a FAQ, the major differences between this project and uutils are:
1. Wider scope: posixutils is far more ambitious than uutils from a breadth standpoint: posixutils will include bc, m4, c99 compiler, fort77 compiler, a cron daemon etc. uutils is far more limited in the scope of programs covered, mimicing GNU coreutils.
2. More minimalist: Each posixutils utility implementation is intentionally more minimalist, intending to avoid the bloat of supporting rarely-used, non-POSIX features. Our common denominator and baseline is the POSIX spec, then add non-POSIX features that users cannot live without.
3. Transportable: Each posixutils utility should look like normal Rust code, easily stand alone with little-or-no deps, and be used in another project. This project is MIT-licensed, not GPL licensed, to aid in that transportability goal.
Some of the wisdom from the recent XZ backdoor incident was that cmake was a contributing factor, due to its internal complexity.
Some of the current trend is to strip out autotools and cmake, and go back to the basics, because modern OS support is a subset of what was relevant 20 years ago.
Call me a greybeard; I want multiple implementations and a spec.
I would prefer to write a parser with zero dependencies.
Here's another: https://github.com/jbush001/NyuziProcessor
Question: What features would developers like to see, in a clone-and-start-hacking API server skeleton?
Far beyond the usual source code examples, this should be production-ready, taking developers from zero to production in minimal time.
Now that the project has reached a stage of completness, suggestions solicited. Thanks!
Number of nodes is a poor metric that is easily gamified (pumped up), presenting an artificial picture. If a blockchain's economics purposefully incentivizes nodes, then number-of-nodes is entirely subsidized, in one common example.
Further, the "Sybil" factor - which one party controls many nodes - and other centralizing factors - e.g. 90% of nodes are on Big Cloud - also complicates the number-of-nodes use as a simple metric and useful comparator.