-
@myfonj @NOVALISTIC @mmatuzo I also vaguely recall something about Google endorsing invalid markup (2006? 2007? before my time at Google), but I think this was a misfire, an isolated incident. But overall Google engineering never really cared much about validation (and neither about optional markup). 1/Permalink On twitter.com
Mood -3 🙁
-
@myfonj @NOVALISTIC @mmatuzo It was some individuals and teams that cared, however. On the @GoogleWebStudio, the team I was on, we invested in it. We measured quality, including validation, and improved it. One testament to those days: meiert.com/en/blog/google-code-quality/. /2Permalink On twitter.com
-
@myfonj @NOVALISTIC @mmatuzo @GoogleWebStudio I was not the only one thinking like this, but I ended up in a visible position to push for both valid HTML and CSS output as well as omitting optional markup on a corporate level. I proposed both for the Google HTML/CSS Style Guide, when I took on stewardship for that team. 3/Permalink On twitter.com
-
@myfonj @NOVALISTIC @mmatuzo @GoogleWebStudio Both are still in the Google style guide, actually. However, what you can see today is what we also observed 10 years ago: Few Google teams adhere to the style guide. And promoting it more was something I couldn’t pursue anymore when I left. google.github.io/styleguide/htmlcssguide.html 4/Permalink On twitter.com
-
@myfonj @NOVALISTIC @mmatuzo @GoogleWebStudio Maybe some Google devs will pick up valid output again, as a goal. As for me, I believe in both valid output and omitting optional code. If anyone’s interested, why or how: meiert.com/en/blog/critical-frontend-development/ meiert.com/en/blog/optional-html/ Got carried away; thanks for listening 🙏 5/5On twitter.com