date: 2019-03-12 21:05:28
slug: 12-210528
status: published
display_format: short-note
link: https://jj.isgeek.net/2019/03/12-210528/
reply_to: {"url": "https://twitter.com/getify/status/1105572296637452288", "title": "getify on Twitter: \"On this #Web30 birthday, I still feel we're propagating divisions with \"JS only whenever HTML/CSS can't\", and those divisions harm the web.\n\nWhy not \"HTML, CSS, & JS all have strengths, but you can often do X with various combinations. Pick the best fit, whatever it is\"?\u2026 https://t.co/7EynrL2tB8\"", "is_image": false, "scrape": false, "_url": null, "type": "article", "description": "\u201cOn this #Web30 birthday, I still feel we're propagating divisions with \"JS only whenever HTML/CSS can't\", and those divisions harm the web.\n\nWhy not \"HTML, CSS, &amp; JS all have strengths, but you can often do X with various combinations. Pick the best fit, whatever it is\"? https://t.co/RBCsWG37IW\u201d", "site_name": "Twitter", "summary": "\u201cOn this #Web30 birthday, I still feel we're propagating divisions with \"JS only whenever HTML/CSS can't\", and those divisions harm the web.\n\nWhy not \"HTML, CSS, &amp; JS all have strengths, but you can often do X with various combinations. Pick the best fit, whatever it is\"? https://t.co/RBCsWG37IW\u201d", "author_photo": "https://pbs.twimg.com/profile_images/1103839041794043904/zpoeOVj8_400x400.jpg"}
titleless: True
syndication: https://twitter.com/jjdelc/status/1105575755243761666
title: Mar 12 2019 - 09:05:28 PM


I think the problem begins when JS starts doing the job of HTML and CSS, generating 100% of document markup, inlining styles and not following progressive enhancement. Then the web relies 100% on JS to be consumed.