On Tue, Aug 7, 2012 at 7:53 PM, Micah Cowan <[email protected]> wrote: > Wget is monolithic, portable to non-Unix, written entirely in > C, and can be built to have few dependencies. My "Niwt" project has the > specific aims to be as hackable and behavior-changeable as possible,
Then I say both serve specific purposes... ie ´classic wget´ is more easily portable (win32, os2, you-name-it), while next-gen wget would be unix-linux oriented. Why not just bump the version and let´s keep ´classic´ wget and ´wget 2.0´ in parallel?. If ´classic´ wget rots someone else will come along and continue enhancing it to support new protocols etc (spdy anyone?) because he needs a current tool for his non-unix based OS... FC
