Which version of macOS are you on? And have you configured macOS to allow "app downloaded from the internet"?
Polypane is fully signed and notarized, so Apple should be happy. They are for installs on my devices. (but I'm still on 15.7 for as long as I can get away with)
THIS WASN'T STRESSFUL AT ALL
The E-ink device has wifi and bluetooth so there's nothing* stopping it from being paired more tightly to other things. There's even a phone app to send it books, and I think it can also support Calibre's web server thingy.
* apart from every damn thing being a walled garden nowadays.
Small gadgets are my thing. There's two I recently came across that I probably wouldn't use but I still kinda want.
www.xteink.com ultra small and thin ereader. I already have a Kindle that doesn't get enough use.
ikko.com/products/min... ultra small phone. Hardware looks great. Android + AI = 👎
AI Business Excellence Awards Most Innovative Web Developer Browser Polypane
We just got recognised as the most innovative web developer browser in the Business Excellence Awards by Acquisition International magazine! 😎
Progressive enhancement as a benefit of CSS Nesting
Something I knew is that in browser that support CSS nesting you can nest @media queries inside of other CSS declarations. What I only fully grasped a few days ago is how well this works for progressive enhancement.
don't you mean
✨ make it slop ✨
The number of concurrent connections can also be hard-coded on the server. An example of this is the NextJS devserver, which only supports one tab/pane at once and beyond that stalls requests.
Beyond getting a job at vercel, fixing that and then resigning, there's not much I can do.
So running on localhost solves most of those cases for now.
More involved is running your local server in http/2 mode, which requires self-signed SSL certs (Polypane accepts those silently for local urls) and a little more setup. Benefit is that you're also running http/2 on the server, probably.
Polypane has specific remediation for localhost/10.0.0.1. If your local URL is different (like josh.local) the number of allowed simultaneous connections is capped at 4 (usually).
A future version of Polypane will add all local urls to the remediation list. Now localhost:port will be faster.
🎉 new blogpost 🎉
Un-Sass'ing My CSS: Native CSS Nesting
Nesting was a dream feature in Sass and it's recently become 'native' in CSS.
This post covers syntax, specificity, real patterns, and the key differences you need to know.
www.alwaystwisted.com/articles/UnS...
#CSS #Sass #FrontEnd #WebDev
I've been experiencing too much gression lately. Time to add some regression.
Why the slow notification?
Poorly configured local servers can only handle ~6 requests at a time. If you load a page with 10 resources in 3 panes, that means your server is stalling and this slows down Polypane.
People blame Polypane but should blame their own server. It's easily solvable.
I might have tricked myself into building a new network panel for Polypane. All I wanted was to show when a local server was using slow HTTP/1.x with a limited number of connections.
And now I'm building a whole panel with consolidated/average load times per resource, split out by origin.
Congrats! 🥳
Congrats! 🥳
Excellent
Miriam no.
No.
It's super nice for sure. I basically took it for granted in a 'this is how nesting works on a technical level' and missed that it actually enabled much more interesting things until that moment.
Progressive enhancement as a benefit of CSS Nesting
Something I knew is that in browser that support CSS nesting you can nest @media queries inside of other CSS declarations. What I only fully grasped a few days ago is how well this works for progressive enhancement.
totally get that!
(Via @meijer.ws, who I didn't want to give the impression that I was quote-dunking on him.)
A dialog titled "Code faster with AI-powered suggestions". There is a block saying "Things to consider", and within it highlighted is that your code "may be seen by human reviewers"
If you turn on "AI-suggestions" (that are so bad they preemptively warn you it's probably wrong and also maybe don't run it), Google will slop up your console history and let human reviewers see it.
Use a browser where the dev can't be bothered to ex-filtrate your data. Try @polypane.app.
I've written a post containing some tips for giving better presentations!
None of these tips can replace great content, but they will help you start strong and keep the energy going all the way through to the applause at the end.
philna.sh/blog/2026/03...
Do you have any more tips to share?
rub some butter on them so you can sell them as vintage
yeah, pretty far. But matchContainer will also work for style queries etc, so it's massively more convenient.
Saw this LinkedIn post too. It was clearly AI slop.
There is a lot of confidently incorrect a11y slop on LinkedIn nowadays.
"[..] said Bossavit, who also described "wanting to crawl into a hole when I encounter bullshit masquerading as empirical support for a claim, such as 'defects cost more to fix the later you fix them'."
More here. I have to scream into the void now.
www.theregister.com/2021/07/22/b...
Are bugs easier to fix if they're in the feature you're currently working on? Of course.
Is having to re-download and setup an old project to fix a bug for an unhappy customer a bunch of extra work? Of course!
Do you need bullshit made-up statistics to make this point? No, not really.
