Rereading ancestor comments I think we are on the same page actually, but in case I’m wrong… In general, I could appreciate the decision to make a stance in th

Rereading ancestor comments I think we are on the same page actually, but in case I’m wrong… In general, I could appreciate the decision to make a stance in this way on a personal level, but when evaluating a real landing page for a paid product from business perspective—which would be an inseparable aspect—I would not be able to recommend preferring “technically correct” over “actually working”. This does not only hurt sales/business, but also causes stress to non-technical end users. All they experience is their browser exiting when they visit the page (thankfully, tabs are preserved on next launch); they are not concerned with implementation and do not become more aware of Apple’s standard non-conformance as a result. A non-commercial website oriented towards developers, or indeed a joke such as in this case, is fine, of course. In short, violating open standards—bad, taking a stance—good, hurting regular users and business—bad.