“If Apple keeps letting its software slip, the next big thing won’t matter - Macworld”
The issues mentioned here are only scratching the surface. Software dev at Apple is seriously dysfunctional
“A random man walks into my office and asks if I’m single… - Stephanie Stimac’s Blog”
“Apple, Its Control Over the iPhone, and The Internet — MatthewBall.vc”
“Tale of the Tape: Highlight.js vs Shiki - Begin”
The only thing I’d add is that you should also go and read the code of each potential dependency. I’ve had deps that won out on all other points but I noped out when I saw how it was written.
The irony of the view-source drama is that the fearmongers are siccing their attack dogs on one of the devs who actually cares about view-source and, not only writes thoughtfully about it here but has been fixing it in Chrome.
The fear-mongering over Chrome updating an enterprise policy feature to let device admins block ‘view-source is kind of mind-boggling. “They’re letting websites block view-source!” No, they’re not. This entire drama is just pure, unadulterated scaremongering for attention.
If anything, Robin is being too generous towards Web3.
“Adactio: Articles—The State Of The Web”
Gonna link to this again ‘cause it’s so good.
Web dev communities seem to be one part “X is bad UX, unusable on mobile, inaccessible, and an all-around bad idea” mixed with ten parts of “here’s how you implement X using unstable tech you shouldn’t be using!” with a very rare “here’s how you do the right thing” as a garnish
“Microsoft and the Metaverse – Stratechery by Ben Thompson”
An interesting insight into the mind of somebody thoroughly converted to a new buzzword. (That VR, even perfectly implemented, is good for work is completely unproven.)
“System76: A Case Study on How Not To Collaborate With Upstream – Chris’s Design & Development”
“Restyling apps at scale – Space and Meaning”
The tragedy of Gnome over the past fifteen years or so is that it’s an OSS project with an ingrained culture of caring about UX, catering to an audience that couldn’t care less.
Been thinking a lot about evaluating tech because I have a new project starting and Jeremy touches on a lot of the same thoughts I had (tho, obv. a diff conclusion as I can choose what I want 😎)
“Why you should prioritise quality over speed in design systems by Amy Hupe, content designer.”
“Designing better file organization around tags, not hierarchies”
Interesting. Another entry in the common genre of “intellectual designs a system they think is superior without referencing any research supporting the notion that it’s actually easier to use”.
“Fire-breathing requirements. The mythical design tool. - by Alan Cooper - Nov, 2021 - Medium”
“Web Development Best Practices: What The Data Tells Us”
These are always interesting although many of the conclusions seem to be logical non-sequiturs. I’m assuming the slides are missing some context.
“Let’s talk about AMP - by Barry Adams - SEO for Google News”
“Google penalised these publishers for not using AMP”
“AMP Has Irreparably Damaged Publishers’ Trust in Google-led Initiatives – WP Tavern”
“I think it’s important that Google leadership acknowledge how AMP has damaged publishers’ trust”
Another day, another npm/node-related exploit.
“Breaking down Apollo Federation’s anti-FOSS corporate gaslighting”
Web dev has a host of ‘lost arts’: previously well-documented practices that have since faded away from the discourse. Behold RFC5005, a more detailed yet nuanced take on pagination than any ‘best practices’ blog post published in the past decade.