Path: ...!2.eu.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!newsfeed.CARNet.hr!Iskon!.POSTED!not-for-mail From: Yazoo Newsgroups: rec.autos.sport.f1 Subject: Re: **2024 Pool** Race 22, United States GP Date: Tue, 05 Nov 2024 10:44:11 +0100 Organization: Iskon Internet d.d. Lines: 33 Message-ID: References: NNTP-Posting-Host: 89-172-20-42.adsl.net.t-com.hr Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sunce.iskon.hr 1730799851 12898 89.172.20.42 (5 Nov 2024 09:44:11 GMT) X-Complaints-To: abuse@iskon.hr NNTP-Posting-Date: Tue, 5 Nov 2024 09:44:11 +0000 (UTC) X-Newsreader: Forte Agent 1.6/32.525 Bytes: 2275 On Tue, 5 Nov 2024 09:16:10 -0000 (UTC), Mark wrote: >All because web designers these days are *so* sloppy, they can't even >get basic validation of data right...and browser companies are complicit >as they have built acceptance of this brokenness into their browsers, so >that they can render even the most broken pages (mostly). > >* I'm talking about a level of unmatched and mismatched tags that it > makes validation tools and parsers give up in frustration. Just a > simple example is the 96 violations (24 errors, 4 warnings, 68 info > advisories) that the W3C validator comes up with just on the front > results page: > >https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.formula1.com%2Fen%2Fresults%2F2024%2Fraces I feel you. The whole HTML concept is soooo losely defined and "out of control" that such horrible stories are widespread. As a former developer (back in the days, 25 years ago when everything was much more defined and strict), I understand the frustration with this mess. Why in the world you'd need to write the parser!? They have all data already structured, so they only need to publish them properly. No big deal, really. But, someone have to make the decision about it. -- It's better to be judged by twelwe than carried by six.