TIL Markdown hyperlink and image syntax doesn’t support whitespace in targets (`href` or `src` HTML attributes, respectively).

![Image](space in filename.jpg)

is rendered as:

<p>![Image](space in filename.jpg)</p>

😭

The tragedy of cross posting across multiple social networks is that most don’t bother to give proper attribution to the appropriate accounts on each network.

It’s nice to use “Real Name” but it’s so much better and valuable to the author to use @​RealName.

we fought hard to vanquish the corporate hackathon in ages past but as prophecy has foretold they have returned—clawing back up from the depths of hell to claim many an unpaid hour of labor in service of insatiable marketing KPIs

Reading breaking changes in a JavaScript framework’s release notes and thinking about all of the web components I published that will just keep working without any upstream third-party maintenance burden.

Web components pay dividends.

The harmful anti-Web Components rhetoric from JavaScript framework authors is out of control. I almost prefer the React team’s tact of largely ignoring Web Components over this current environment of framework authors saying they “hate web components” and claiming that web components are a “danger to the future of the web.”

Just to be clear, a web standard for authoring components would not exist if it required consensus from popular JavaScript framework authors (and they probably wouldn’t be bothered by that that outcome either). The discussion needs to acknowledge that bias up-front.