Hey friends,

August never quite winds up feeling like SUMMER summer, with as much back-to-school prep and events that cycle up in August, it's more of a mini-September!

Thinking Too Hard

When do you break something into an external component, and when do you leave it colocated?

This week I was working on a very specific feature in a React web app and I started to run up against the upper level of readability for a single component. There were 3 data helper functions and 3 sub-components that existed ONLY for this one specific feature. So, what to do?

After taking a poll of several smart folks (AKA pestering the Viget development chats) the overall sentiment was to leave everything colocated if possible, but with some practical things to try:

• Move logic that's not component scoped into functions in the same file.
• Break larger components down into smaller components in the same file (don't leave as one mega component).

THEN if it's STILL too large should we start looking at externalizing some of these components.

Interesting Web Bits

• I'm always a sucker for a new monospace font: Server Mono
• This neat demo uses SVG filters to dither a video.
• Jake Archibald explores video with transparency. (Spoiler: we're not quite there yet but we can use shaders to clear the hump for now).
• If YouTube had actual channels
• Yes, WezTerm is fantastic. If you're looking for a new terminal editor, WezTerm is a great choice.
• Jim thinks about good URL examples.
• More progress for the Rust-In-Everything Empire, Blitz is a alternate HTML/CSS renderer intended to be part of a larger Rust framework that runs EVERYWHERE. I'm not quite sure yet how I feel about this... 🤔
• An interesting look in how the SNES graphic system worked