Found 27 bookmarks
Custom sorting
A Framework for Evaluating Browser Support • Josh W. Comeau
A Framework for Evaluating Browser Support • Josh W. Comeau
Lots of exciting new features have been landing in CSS recently, and it can be tough trying to figure out if they’re safe to use or not. We might know that a feature is available for 92% of users, but is that sufficient? Where do we draw the line? In this blog post, I’ll share the framework I use for deciding whether or not to use a modern CSS feature
·joshwcomeau.com·
A Framework for Evaluating Browser Support • Josh W. Comeau
Yes, progressive enhancement is a fucking moral argument
Yes, progressive enhancement is a fucking moral argument
I rolled my eyes when I saw this post circulate around the webosphere. I knew it was clickbait, but I clicked it and read it, because what else is a whiney SJW feminist fuck meant to do while she’s drinking her coffee in the morning? But then, as I scanned the page, I realised what deeper level of fucked-up-ness it represents. But let me back up and explain this. First of all, the article by @joshkoor revolves around the central notion that bringing Progressive Enhancement (PE from now on) into our work is a burden on the modern web developer. You see, any site should be able to be rendered 100% in javascript, and that’s okay. Because the modern user has javascript, and expecting javascript to not be available is just plain pig-headedness. Those whiny PE proponents are making a moral case for PE, rather than taking a utilitarian and path-of-least-resistance approach.
·awfulwoman.com·
Yes, progressive enhancement is a fucking moral argument
Embrace the Platform
Embrace the Platform
At the end of 2021, CSS-Tricks (RIP) asked a bunch of authors “What is the one thing people can do to make their websites better?”. This here, is my submission for that end-of-year series.
·bram.us·
Embrace the Platform
Reluctant Gatekeeping: The Problem With Full Stack
Reluctant Gatekeeping: The Problem With Full Stack
We need to identify exploitation. While there are some gleeful Full Stack Developers, many are computer scientists given too many responsibilities, and over things for which they are not willing or qualified to be held accountable.We need to address the undervaluing of HTML and CSS for what it is: gender bias. Even though we wouldn’t have computer science without pioneering women, interloping men have claimed it for themselves. Anything less than ‘real programming’ is now considered trivial, silly, artsy, female. That attitude needs to eat a poisoned ass.We need to revisit the separation of concerns principle. We simply can’t afford for people to have to know everything just to do something. It’s good that we conceptualize designs in terms of self-contained components now, but that can be a mental model without being a technology-specific land-grab.Most of all, we need to educate people who don’t code at all just how many different things different types of code can do, and how different each is to understand and write. Hopefully, this way, more of us will be writing the kind of code that suits us best, and not spending our time anxious and demoralized because we don’t know what we’re doing, or we simply have too much on our plate. That’s not to say that if you do take to JS, CSS, HTML, SQL, and C# you shouldn’t be writing all of them if you‘d like to and you have enough time!
·medium.com·
Reluctant Gatekeeping: The Problem With Full Stack
Read-only web apps
Read-only web apps
It’s fine to require JavaScript for read/write functionality. But have you considered a read-only mode without JavaScript?
·adactio.com·
Read-only web apps
The Performance Inequality Gap, 2023 - Infrequently Noted
The Performance Inequality Gap, 2023 - Infrequently Noted
To serve users at the global P75 of devices and networks, we can now afford ~150KiB of HTML/CSS/fonts and ~300-350KiB of JavaScript (gzipped). This is a slight upgrade on last year's budgets, thanks to device and network improvements. Meanwhile, web developers continue to send more script than is reasonable for 80+% of the world's users, widening the gap between the haves and the have-nots. This is an ethical crisis for frontend. Meanwhile, the most popular tools and frameworks remain in stubborn denial, but reality is not moved by ignoring it: when digital is the default, slow is exclusionary.
·infrequently.org·
The Performance Inequality Gap, 2023 - Infrequently Noted
Components Are Pure Overhead
Components Are Pure Overhead
With many starting to look at incorporating Reactivity into existing Frameworks I wanted to take a moment to look at how Frameworks evolved into using Components, the evolution of change and state management, to best understand the impact of where things are going.
·youtube.com·
Components Are Pure Overhead
The JS-industrial-complex
The JS-industrial-complex
The JS-industrial-complex are complexity merchants. They sell increasingly baroque solutions to imagined problems, or challenges created by the JS-industrial-complex itself. It's mostly nonsense.
·twitter.com·
The JS-industrial-complex