Salesforce going alllllllllllll in on Web Components is inspiring, particularly given the tough browser support matrix they face in enterprise. If they can, most everyone can too!https://twitter.com/SalesforceDevs/status/1135927561035366400 …
-
1:53 -
Replying to @slightlylate @KevinJHill
if one of the richest, best staffed companies can do it, anyone can?
1 reply 0 retweets 0 likes -
Replying to @marypcbuk @slightlylate
Tweets can sour quickly :( Honestly, the reason I joined Salesforce was because of the investments to go with Web Standards. With browsers supporting more app features JS frameworks should all be pointing in this direction.
1 reply 0 retweets 0 likes -
Replying to @KevinJHill @slightlylate
Salesforce absolutely has a great dev organization that makes investments in technology; I just don't get why they're an 'if anyone can' example ;)
1 reply 0 retweets 0 likes -
Replying to @marypcbuk @KevinJHill
One of the persistent arguments I get when discussing the value of a standard component model is "what about IE11?". Both YouTube and Salesforce have nontrivial legacy browser use, but both moved to standards with much stricter performance and a11y requirements than most projects
1 reply 0 retweets 1 like -
The argument has always been slightly specious (the polyfills work great, most sites have minor legacy browser use), and teams tend to look to big properties adopting something to build confidence.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @KevinJHill
yes "it's stable enough for X" is much more helpful than "if giant company can do it, anyone can" ;)
1 reply 0 retweets 1 like
Apologies for the poor choice of words!
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.
