4 ms·
Why? It is a reasonable proxy for how long it would take to replace something, and it's the effort to replace something that is core to the "you wouldn't be wh
by tedunangst 15y ago
Why? It is a reasonable proxy for how long it would take to replace something, and it's the effort to replace something that is core to the "you wouldn't be where you are without us" argument. How would you measure contribution?
- rwl 15y agoI'm not the OP, but one way would be to look at the dependency graph for packages. My guess is that a whole heck of a lot of them depend either directly or transitively on GNU code -- for example, GLibC.
- aniket_ray 15y agoIt doesn't really measure how time it would take to replace. Compared to KDE or Firefox code, GNU code is much more succinct and optimally written. I really doubt that that code could be replaced easily in a single pass.
- djmdjm 15y agocitation needed
- simias 15y agoHere you go: http://lists.freebsd.org/pipermail/freebsd-current/2010-August/019310.html http://lists.freebsd.org/pipermail/freebsd-current/2010-Augu...
- tedunangst 15y agoSo wrong. GNU grep may be fast, but it's also the most bloated grep with the most lines of code. I think that's the opposite of what you're trying to prove.
- 3am 15y agoOptimizations are the hardest part. So those additional LOC are actually the most valuable and difficult to replace. Your utility of those optimizations might be vary from other peoples'... personally, I would hesitate before calling Gnu grep bloated.