News for hackers. Stuff that matters.
Re:Curl vs. Wget by eru on Wednesday March 02, 2016 @05:58PM (#11213749)
Looks like a frontend to curl that has wget's defaults would be useful.
Re:Curl vs. Wget by theoh on Wednesday March 02, 2016 @06:19PM (#11213866)
Merge the code, hard link the filenames to the same executable and get it to change behavior based on the name it's invoked under.
Re:Curl vs. Wget by eru on Wednesday March 02, 2016 @07:10PM (#11214127)
No need to merge code. Take curl as is, and set different defaults based on executable name.
Re:Curl vs. Wget by lucb1e on Thursday March 03, 2016 @01:21AM (#11215338)
In that case I'd love for it to include resuming downloads though, but given the differences I don't think merging is going to be more useful than just adding the feature in curl.

Edit: nevermind, I just learned that wget can download a page's resources or even inline them (-k apparently), that's a bit of a way off from curl's purpose. Better keep them separate tools, although wget might benefit from using libcurl so they don't have to implement lots of stuff like https or http2.

Re:Curl vs. Wget by kcbanner on Wednesday March 02, 2016 @06:40PM (#11213994)
Sounds like a lot of complexity for no benefit.
Re:Curl vs. Wget by theoh on Wednesday March 02, 2016 @06:46PM (#11214016)
Either tool can provide the functionality of the other with a little work, is what I meant to imply...
Re:Curl vs. Wget by baudehlo on Wednesday March 02, 2016 @07:47PM (#11214289)
It's what vi does.