I just watched Homebound, Neeraj Ghaywan’s second feature film. And it left me devastated.
The film is based on Basharat Peer’s article ‘Taking Amrit Home’ (which has since been retitled ‘A Friendship, a Pandemic and a Death Beside the Highway’).
I highly recommend this film. But if you can’t watch it for whatever reason you must read the article.
I’m a web designer-developer who has mostly designed and built marketing websites for small to medium-sized businesses. I started designing because my clients didn’t have a designer and expected me to handle everything. But I’ve always felt like an imposter. It’s not a nice feeling.
I’m really determined to change that, which is why I just bought Scott Riley’s course, Mindful Design. Piccalilli is running a Black Friday sale on all their courses, including Mindful Design, and I can wholeheartedly recommend them.
Mandy Michael uses a brilliant analogy to explain why developers must get to know the HTML elements available to them and use the appropriate one for their content.
In TypeScript, we have the concept of an
anytype. When you assign a type ofanyit means the content can be anything. […] But if everything is typed asanythen you lose the benefits of the language.This is the same with HTML. If you use the
<div>everywhere, you aren’t making the most of language. Because of this it’s important that you actively choose what the right element is and don’t just use the default<div>.
This reminded me of the following quote by Jen Simmons from their HTML course:
HTML syntax itself is fairly simple. The trickier part is knowing which tags to use when.
Images on the web are hard. After trying and failing so many times before, now I finally understand how to configure srcset and sizes attributes to serve differently sized images for different viewports.
Also worth checking out: Image Display Elements by Stephanie Eckles.
@ts-expect-errorwill let you know when there’s no TypeScript error to silence and when it has become useless.@ts-ignorewill stay put and sit silently wherever you placed it.
Not only did I not know the difference between @ts-ignore and @ts-expect-error, I was totally unaware there was such a directive as @ts-expect-error.
The <meta name="theme-color"> tag is no longer supported in Safari 26 on macOS and iOS.
If a fixed or sticky element touches the top or bottom edge of the window, then and only then, Safari extends that element’s background color into the corresponding top or bottom bar. Otherwise, on iOS, the bars remain translucent and have no solid color background.
As Wenson Hseih explained on WebKit Bugzilla:
A solid background color extension (“top bar tint”) is only needed in cases where there’s a viewport-constrained (fixed or sticky) element near one of the edges of the viewport that borders an obscured content inset (such as the top toolbar on macOS, or compact tab bar on iOS), in order to avoid a gap above or below fixed elements in the page that would otherwise appear when scrolling. This color extension behaviour is more critical on iPhone, where there’s a much “softer” blur effect underneath the browser UI (and so more of the page underneath is otherwise directly visible).
The goal of linking is about building community and creating networks that truly exist to support you and those around you; those networks will persist when social media lets you down.
When I consume AI art, it also evokes a feeling. Good, bad, neutral—whatever. Until I find out that it’s AI art. Then I feel deflated, grossed out, and maybe a little bit bored.