The people that really need to know how to insert a 500mb string will actually explain why they need to do so (beyond the typical “it doesn’t work”).
The ones that can’t explain why are almost always unaware of the actual problem they need to solve.
The ones that can’t explain why are almost always unaware of the actual problem they need to solve.
Also good questions shouldn't need explanations for the reason you're trying to do something. It's not like I'm going to explain my business requirements on a public forum to complete strangers.
And I'm going to mention this again — if the purpose of SO is to provide a searchable database of questions and answers, then the answer has to match the question, not a supposed use case that the user may or may not have, because that answer is then useless to others.
Of course you can include 500 MB in a separate file and read that. It's totally uninteresting and now that SO question, along with its non-answer is showing up in search results, having precedence over others. Which is a pity, because I thought SO is a place where you can ask questions on obscure features of the tools we're using.
You can, as long as you're clear on why you need these obscure features. So there's nuance... if someone asks "hi, I want to call `add` like `add(10, 20, 30)` and it's not working" and the answer is "Use `10 + 20 + 30` instead!", they're answering the intent of the question. They've totally not answered the original question (I want to call add) but OP is probably misguided.
It'd totally be fair to say "Oh, declare a function with 3 params and return the sum, or even make a function with variable arguments, then enumerate over each of them, summing into an accumulator. You can also do this as a functional reduction. In fact, you can use the mapreduce framework to do this, and here's how to create an adder circuit" - Every tidbit of the above is just... overkill.
I totally empathize with you - it sucks to google "how to do X given good reasons Y Z" only to find a question "how to do X given terrible reasons A B" that's answered by "don't do X"! I think the way that's respectful of others' time is to ask another question and clarify why you truly need X.
If you've taught a multidisciplinary class, you'll have faced people who truly are confused - EE students who want to understand, for example, "how do I declare a 20 bit integer in C for this program that's running on Windows?"...
Not 100% for me, but easily 30%. And you can almost taste the authoritarian arrogance dripping from the moderators words. I was disappointed this incredibly negative aspect of the site wasn't even mentioned in the post.
But sometimes explaining how the situation arises:
* Violates NDA/secrecy/licensing agreements.
* It can be complicated to explain the conditions that created the situation to people that aren't working with a custom/proprietary tech stack.
* Is irrelevant. If the operation needed to solve my problem can be concisely stated, why type a distraction?
I remember one post where someone said something like: "It'd be better if you tried this, but if you really need to do X..." followed by an explanation that solved my problem. It made my day.