andyblum - Network

@drupal is trying to grow their audience in the #fediverse "We're actively building presence on Mastodon and Bluesky, platforms...

@drupal is trying to grow their audience in the #fediverse

"We're actively building presence on Mastodon and Bluesky, platforms that align with our open-source values. We’ll give it 6 months of effort and see if we can grow audiences, and then re-assess.

"If either platform reaches 5,000 followers, we’ll promote them to being a priority platform. We’d love to see them become our preferred platforms."

https://www.drupal.org/project/drupal_cwg/issues/3498933#comment-16126762

Help us get Drupal off the birdsite!

#followfriday #OpenSource

It's honestly wild how my different work streams have all converged on "Andy needs to get better at writing tests" this...

It's honestly wild how my different work streams have all converged on "Andy needs to get better at writing tests" this week.

Client work:
* backstop.js
* jest
* cypress
* phpunit

Drupal Contrib:
* phpunit
* nightwatch

Personal Project:
* bats

There’s only one mug in the cabinet for days like today.

There’s only one mug in the cabinet for days like today.

📝 Closing out the year with a new blog post about "how I wish #WebComponents worked" - specifically as a tool for building...

📝 Closing out the year with a new blog post about "how I wish #WebComponents worked" - specifically as a tool for building #DesignSystems. Includes code samples and a ✨demo✨ at the end.

https://andy-blum.com/articles/how-i-wish-web-components-worked/

Omg I need this. The only thing it’s missing is an @eleventy possum keyhttps://modedesigns.com/products/dss-fontawesome-keycaps

Omg I need this. The only thing it’s missing is an @eleventy possum key

https://modedesigns.com/products/dss-fontawesome-keycaps

The Macys Thanksgiving Day Parade is such a weird experience every year. Just 4 hours of commercials as one big commercial intercut with...

The Macys Thanksgiving Day Parade is such a weird experience every year. Just 4 hours of commercials as one big commercial intercut with more commercials.

And yet it’s a nearly century long tradition loved by millions

I might be in the minority, but I don’t love swipe gestures in @ivory I just dropped my phone and managed to make a new post in the...

I might be in the minority, but I don’t love swipe gestures in @ivory I just dropped my phone and managed to make a new post in the process.

@FirefoxDevTools

@FirefoxDevTools

Would love to hear from some insiders if they're willing/able to share. Tagging some of the ones I know off the top of my head:@tomayac...

Would love to hear from some insiders if they're willing/able to share. Tagging some of the ones I know off the top of my head:

@tomayac @argyleink @jensimmons

I'm a firefox/duckduckgo user, but I don't think splitting Chrome away from Google or Android helps anyone.And I worry that this...

I'm a firefox/duckduckgo user, but I don't think splitting Chrome away from Google or Android helps anyone.

And I worry that this decision could end the current golden age of web advancement. Without Google's competition, are Apple and Mozilla motivated enough to continue pushing the web platform forward? There will be individuals, teams even, that are, but will the corporate leaders still be willing to fund those efforts?

https://www.inc.com/jason-aten/why-the-governments-plan-to-force-google-to-sell-chrome-wont-work/91021629

@scottjehl @syntaxfm @brad_frost So what's better?I don't know. Web Components are definitely more portable and a safer long-term...

@scottjehl @syntaxfm @brad_frost

So what's better?

I don't know. Web Components are definitely more portable and a safer long-term bet than react, vue, angular, etc.

They also don't add any additional languages/syntaxes like JSX

But the goal of building components in a design system is to make easily-usable chunks of markup, styles, and javascript. Web components do that and then build a wall between the component and the page in which it's used.

@scottjehl @syntaxfm @brad_frost WC may add reactivity to your HTML, but they'll also likely hurt your FCP, LCP, and CLS scores. Some...

@scottjehl @syntaxfm @brad_frost

WC may add reactivity to your HTML, but they'll also likely hurt your FCP, LCP, and CLS scores. Some SSR options exist, but they don't cover every use case.

@scottjehl @syntaxfm @brad_frost Next topic: Web Components are "platform native" so you don't have to bring along a library...

@scottjehl @syntaxfm @brad_frost

Next topic: Web Components are "platform native" so you don't have to bring along a library to render them.

But they do still require JS to be fetched, parsed, and executed before your components can be rendered.

@scottjehl @syntaxfm @brad_frost I've seen issues with tools that don't know to look into open shadowroots. For example, an internal...

@scottjehl @syntaxfm @brad_frost

I've seen issues with tools that don't know to look into open shadowroots. For example, an internal webchat tool built to add event listeners to links with a specific data-attribute. If that tool doesn't walk the DOM and check for shadowroots along the way, it'll miss your custom elements with anchor tags in the shadowdom.

@scottjehl @syntaxfm @brad_frost Next topic: web components make components harder for 3rd party teams to work with.If you're building...

@scottjehl @syntaxfm @brad_frost

Next topic: web components make components harder for 3rd party teams to work with.

If you're building components for a design system for a big organization, your adopters are probably also interfacing with other teams (eg marketing & analytics). In my experience, those teams don't have a lot of experience with web components (tbf they're still pretty new) and their tools might not be fully compatible.

@scottjehl @syntaxfm @brad_frost On top of all that, global styles and component styles exist in different contexts (similar to CSS layers)....

@scottjehl @syntaxfm @brad_frost

On top of all that, global styles and component styles exist in different contexts (similar to CSS layers). Global styles *always* beat internal styles regardless of specificity. Unless you use `!important` in which case component styles always win regardless of specificity

@scottjehl @syntaxfm @brad_frost Adopters could address those little bugs in a global stylesheet, but now we have to expose the...

@scottjehl @syntaxfm @brad_frost

Adopters could address those little bugs in a global stylesheet, but now we have to expose the component's internals through shadowparts, creating a whole new API you have to maintain.

Also, we've spent so much time & effort putting the styles into those compoennts it feels weird to add component styles to a global stylesheet.

@scottjehl @syntaxfm @brad_frost If you've built a design system where you've got WC slotted into WC slotted into WC the little...

@scottjehl @syntaxfm @brad_frost

If you've built a design system where you've got WC slotted into WC slotted into WC the little idiosyncracies that pop up in adoption become problems that live in no-man's land. Which component should be responsible for fixing the inconsistencies?

Components, by design, should really only need to care about their own internal styles.