"I could rewrite curl"

daniel.haxx.se

5 points·latexr··6 comments

I have a few qualms with this app:

1. For a Linux user, you can already build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem. From Windows or Mac, this FTP account could be accessed through built-in software.

2. It doesn't actually replace a USB drive. Most people I know e-mail files to themselves or host them somewhere online to be able to perform presentations, but they still carry a USB drive in case there are connectivity problems. This does not solve the connectivity issue.

3. It does not seem very "viral" or income-generating. I know this is premature at this point, but without charging users for the service, is it reasonable to expect to make money off of this?

https://news.ycombinator.com/item?id=9224

Everyone posting that would do well to read the whole thread and not just the first post. It’s right there in your link.

BrandonM—in their very next reply—conceded a bunch of points, wished them luck, and was generally polite.

That interaction should be celebrated, not ridiculed. It is a prime example of not being stubborn and learning from a conversation.

I really don't get why the 99% posts are there. Accepting that close to 100% of curl runs to ever happen were at most `curl -X ... -H ... -o file url` (and usually without the X or headers) doesn't negate the overall achievement, versatility, scope, etc. of the project. Some are not even directly criticising the project.

What they fail to recognize is curl was around in like the late 90s. PYthon et. al. didn't exist back then.

Python existed even in the early 90s. Not that cURL should have been written in it, though.

ahh ok, well maybe not python but you get the idea.

Reply on news.ycombinator.com