No documentation for web developers #6842

[ghost]

domenic

There is plenty of documentation available in sources such as MDN.

Documentation available in sources such as MDN is non-authoritative. I don't want to be wasting time learning from potentially incorrect sources. I always go straight to the authority to learn.

As editors we don't have time to both specify browser/conformance checker behavior exhaustively and help developers learn how to use all this technology; it's simply too big of a job. We do our best with time-efficient tricks such as the developer's edition, or examples that show tricky edge cases, or intro sections that are easy to write. But we aren't full-time web developer evangelists; we're standards engineers.

So in other words what you are saying is you don't develop finished products.

I don't think it's a big job. Slow down implementing new features and finish the previous features - web browser documentation - web developer documentation - code validator. The end-user is WHATWG's main customer, as I have said - there can be no standard without the end-user in which case if you neglect the end-user then you are wasting your life working on a standard because that standard will never be used.

I am not a web developer evangelist or an engineer, but I know what makes a good product, and I am also an end-user with first hand experience trying to use HTML.

Your sentence suggesting that if we don't make time to take on an additional full-time job we "cease development and stop wasting your life working on a standard thst web developers don't know how to use" is pretty insulting.

Not really. If your not going to give something 110% in life then you are not giving your best and should stop. Success doesn't come from laziness, it comes from passion.

I'll remind you again, code of conduct or not, this is my opinion. You can either stick your head in the sand or listen to complaints and use it to improve the product, whether or not you agree with it or not. You cannot tell people how to construct a complaint if you want to know what is happening in reality. You must find out what is happening in reality to improve the product.

You implying I was not able to use HTML because I couldn't find the documentation is actually what is false. Fix the naming of the web developer edition of the standard and that problem will not happen again. You have used the term 'developer' in reference to yourself as a software developer as well as web browser developer. Which one is it?! Do you see the problem??!!

I was contributing but now I have stopped because there is no point continuing when people like you close threads in disagreement without allowing for any discussion. The WHATWG was formed because the people that started it where not happy that W3C would shut them down when they voiced themself. So keep eating your own words.

Your problem is you think like a developer, not a user, and this is why 99% of websites on the internet will never be standard-compliant while people like you are in charge.