One of the worst parts of the JS ecosystem is that it walls itself off from markup. It tries to act as though it's "above" or disconnected
-
-
...and so we see endless re-invention of the same components, over and over, without any real connection to markup.
1 reply 0 retweets 2 likes -
Which from the markup perspective means we don't actually learn much about user needs. Crawlers don't see them.
1 reply 0 retweets 1 like -
Replying to @slightlylate @seldo
So there might be universes being born and dying out in JS land, but the markup world doesn't think of them as "their problem".
1 reply 0 retweets 1 like -
Replying to @slightlylate @seldo
Web Components -- incl AMP vocabulary -- begin to force the question. If something really *is* common & we can prove it, why not standard?
1 reply 0 retweets 3 likes -
Replying to @slightlylate @seldo
Obviously the form of the built-in will change vs. whatever's in AMP or any other library, but now that's an argument for data to help solve
1 reply 0 retweets 1 like -
Replying to @slightlylate @seldo
So this isn't so much "bizzaro HTML" as it is what we were doing anyway out in script, but exposed to markup, which helps us learn faster
2 replies 0 retweets 2 likes -
Replying to @slightlylate @seldo
I think maybe it feels bizzaro because the ecosystem isn't shifting towards markup like this but closer to script instead.
2 replies 1 retweet 2 likes -
Replying to @TheLarkInn @seldo
That is a very JS-centric view; one that lives in a JS echo-chamber. Nearly all content that's searchable is produced in markup format.
1 reply 0 retweets 2 likes -
...which at the limit is nearly all content that isn't gated by login or VPN.
1 reply 0 retweets 1 like
Web Components try to heal the rift; to enable us to continue to describe the structure of our apps in markup while making them in script
-
-
The "we're just gonna do everything in script" camp is also costing businesses tons in terms of interop friction. Every hill a mountain.
1 reply 1 retweet 2 likes - 5 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.