News for hackers. Stuff that matters.
Re:Why curl defaults to stdout by coldtea on Monday November 17, 2014 @09:11AM (#8618231)
>I find that weird. Why are you wanting to copy stuff from http all of the time?

This kind of question (and the other question you make above) remind me of the people that answer Stack Overflow questions with their opinions of "best practices" and "what you should be doing instead" instead of answering what the poster asks. E.g:

Q. "How do I store JSON in mysql?"

A. "Why do you ask? What do you want to achieve with this? You'll be better served with a NoSQL database".

etc, etc.

Re:Why curl defaults to stdout by Morgawr on Monday November 17, 2014 @10:09AM (#8618472)
That is called the XY problem[0]. It is a fairly common practice especially in technical IRC channels. Honestly, it can be very frustrating but a lot of times it is useful and actually helps both the person asking the (wrong) question and the group of people trying to provide a proper answer. Some (maybe most?) people do take it too far and even refuse giving you a straightforward answer just to be pedantic and annoying. Those types of people have made this much of a bigger problem than it actually is, however thinking about the XY problem before you ask a question is always a good idea, regardless.

[0] - http://mywiki.wooledge.org/XyProblem

Re:Why curl defaults to stdout by LeonidasXIV on Monday November 17, 2014 @10:06AM (#8618460)
I actually like this, because posters often have XY-problems. Especially if the solution the poster wants seems strange if often makes sense to question and propose a more sane solution to the whole problem he is actually having.
Re:Why curl defaults to stdout by Touche on Monday November 17, 2014 @10:39AM (#8618635)
That's not what I was doing at all. My use of curl/wget is much different so I was curious of what they use cases are.