Found 22 bookmarks
Custom sorting
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
Much of my career as a web designer has been spent, quite happily, working alongside programmers, engineers, people with computer science…
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
Speed for who?
Speed for who?
Frameworks are often touted as something like “a lightning fast development experience” and that’s fine I guess, but the speed is in the wrong hands. Why not “a lightning fa…
·andy-bell.co.uk·
Speed for who?
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
The Great Divide Was Indeed Divisive - Chris Coyier
The Great Divide Was Indeed Divisive - Chris Coyier
Zach reflects on 17 years in the game and my essay The Great Divide, four years old this month: The Great Divide really resonated with me. I keep coming back to it and I do think it continues to accurately describe what feels like two very distinct and separate camps of web developer. And despite […]
·chriscoyier.net·
The Great Divide Was Indeed Divisive - Chris Coyier
State of Web Components August 2022
State of Web Components August 2022
Join this special “State of Web Components” event and catch up on all the latest news about what is possible, improved, and coming soon in the ever growing adoption and use of web components. Covering new tooling and unique ways to incorporate web components that you might not have thought about yet!
·youtube.com·
State of Web Components August 2022
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