Why was this question closed?

It was closed about 5 minutes after asking. I can accept if I ask a wrong or inappropriate question which gets closed, but I wish to understand what led people to close this one.

My question was definitely to the topic. It was clearly written. I believe, everyone, who has ever put a lot of effort into developing a website has asked himself this question.

  • 1
    "What are the options when protecting HTML, JavaScript, CSS, and the whole Website content against code stealing and reverse engineering?" sounds like a shopping question. It might take some effort to tune it into the kind that is welcome at SE network
    – gnat
    Commented May 17, 2012 at 18:02
  • 4
  • 1
    ... also note that just because these questions didn't get closed don't take it to mean that yours shouldn't have been Stack Overflow is not a perfect model of its guidelines Commented May 17, 2012 at 18:08
  • @SomeHelpfulCommenter, hi thanks for your respnse. Does it mean, that the true reason, why the question got closed was, that some people do not like the idea of protecting their content? This is even more disappointing, as a person should be able to freely ask on this topic too. Thanks for your answer, anyway. Commented May 17, 2012 at 18:13
  • 2
    @Bunkai.Satori I think the problem is that this question comes up quite frequently. It even has a Thick-client version. People generally don't like questions that get asked a lot , especially when the answer is it is not technologically possible to achieve. Commented May 17, 2012 at 18:25
  • @SomeHelpfulCommenter, thanks for your answer. Commented May 17, 2012 at 18:28
  • @Bunkai.Satori, to an extent I think you're right -- this question was closed with rather more prejudice than usual because asking how to prevent HTML from being reverse engineered is like asking how to put toothpaste back in the tube.
    – Kirk Woll
    Commented May 18, 2012 at 1:42
  • @KirkWoll, hi Kirk. Thanks for the answer. Whatever, this message was deleted, and I do not wish to put any more energy into it. I still think, it was correct to ask it. Even if there is no way of protecting HTML, who can be 100% sure, that anybody in the world did not invent a way. Thanks for your answer. Commented May 18, 2012 at 11:22

1 Answer 1


What are the options ...

This is likely asking for suggestions, personal opinions, which are not welcome on Stack Exchange.

Additionally, your "question" is not question but questions. They should be separated (HTML, javascript, CSS). All of them have different options

  • @Marting, thanks for your attempt to answer. But asking what options are to do one thing or the other is clear question an can be answered scientifically. Option 1...., Option 2...., Option 3..... . Regarding mixing HTML, JavaScript, CSS, they all relate so closely, that it is not possible to separate them, in regards protecting a website. This is why we have web-development discussion topic in Stack Exchange. Commented May 17, 2012 at 17:53
  • 1
    @Bunkai.Satori: We're actually trying to get rid of the web-development tag.
    – animuson StaffMod
    Commented May 17, 2012 at 18:06

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .