3 ms·
For most of these it's a case of replacing old, poorly designed, unmaintained (and in light of the poor design, mostly unmaintainable) code with better designed
by cperciva 17y ago
For most of these it's a case of replacing old, poorly designed, unmaintained (and in light of the poor design, mostly unmaintainable) code with better designed and well-maintained versions.
This was definitely the case for replacing GNU tar/cpio/pax with libarchive-based versions.
- jrockway 17y agoWhy write new versions rather than fix the GNU versions? More eyeballs, and all that...
- cperciva 17y agoTo borrow a phrase from the rollout of DNSSEC: It's really hard to rebuild a plane while in flight. Sometimes it's easier to build a second plane, fly it up parallel to the old plane, then jump across. For what it's worth, I've talked to some people at linux distributions who are excited about ditching gcc too. (Not going to say who they are, because I don't want to get them in trouble.)
- jrockway 17y agoBut it's kind of like building the new airplane out of rusty metal, to replace the rusting airplane you currently have. While you're taking the effort to rebuild something, you might as well use new metal. What I mean here is, why replace a big collection of flaky C apps with another big collection of flaky C apps? Sure, maybe your new version uses strlcpy instead of strncpy, but that doesn't really fix any fundamental implementation problems.
- cperciva 17y agoIf you think libarchive is flaky, you have incredibly high standards.
- cubicle67 17y agoIt's really hard to rebuild a plane while in flight Obviously these people didn't know that http://www.youtube.com/watch?v=L2zqTYgcpfg http://www.youtube.com/watch?v=L2zqTYgcpfg [Disclaimer - I used to work for them]