It sounds like Remix takes a sensible approach to progressive enhancement.
The speed with which Twitter recedes in your mind will shock you. Like a demon from a folktale, the kind that only gains power when you invite it into your home, the platform melts like mist when that invitation is rescinded.
A terrific piece by Maggie Appleton that starts with a comparison of graphical user interfaces and command line tools—which reminds me of the trade-offs between seamless and seamful design—and then moves into a proposed paradigm for declarative design tools:
Small, scoped areas within a graphical interface that allow users to read and write simple programmes
This observation feels spot-on to me:
The shift that I noticed, totally anecdotally, is literary writers are starting to write more dystopian climate futures and science fiction writers are starting to write about climate solutions.
One for the server - where you can go wild.
One for the client - that should be thoughtful and careful.
Yes! This! I’m always astounded to see devs apply the same mindset to backend and frontend development, just because it happens to be in the same language. I don’t care what you use on your own machine or your own web server, but once you’re sending something down the wire to end users, you need to prioritise their needs over your own.
I think that’s the primary benefit to developers. The primary benefit to users is that what you build will faster and more resilient.
Anyway, this is a really good deep dive into different architectural choices for building on the web. Although I was surprised by this assertion in the first paragraph:
The most popular architecture employed by web developers today is the Single Page App (SPA)
Citation needed. Single Page Apps do indeed dominate the discussion, but I don’t think that necessarily matches the day-to-day reality.
I really like the format of this bit of journo-fiction. An interview from the future looking back at the turning point of today.
It probably helps that I’m into nuclearpunk just as much as solarpunk, so I approve this message.
Atomkraft? Ja, bitte!
But is it always the case that faster websites are greener websites? We reluctantly have to consider another facet: if making a website for a car manufacturer faster leads to an increase in the number of cars sold, can we really say that our website is greener?
This is very timely for me, given that Clearleft is currently engaged on a project that’s making me decidedly queasy for this exact reason—the success metrics of the project would be net negative for the world.
Adrian brings an excellent historical perspective to the horrifying behaviour of Facebook’s in-app browsers:
Somewhere along the way, despite a reasonably strong anti-framing culture, framing moved from being a huge no-no to a huge shrug. In a web context, it’s maligned; in a native app context, it’s totally ignored.
Yup, frames are back—but this time they’re in native apps—with all their shocking security implications:
By the way, this also explains that when you try browsing the web in an actual web browser on your mobile device, every second website shoves a banner in your face saying “download our app.” Browsers offer users some protection. In-app webviews offer users nothing but exploitation.
While I’ve always been bothered by the downsides of SPAs, I always thought the gap would be bridged sooner or later, and that performance concerns would eventually vanish thanks to things like code splitting, tree shaking, or SSR. But ten years later, many of these issues remain. Many SPA bundles are still bloated with too many dependencies, hydration is still slow, and content is still duplicated in memory on the client even if it already lives in the DOM.
Yet something might be changing: for whatever reason, it feels like people are finally starting to take note and ask why things have to be this way.
Interesting to see a decade-long perspective. I especially like how Sacha revisits and reasseses design principles from ten years ago:
- Data on the Wire. Don’t send HTML over the network. Send data and let the client decide how to render it.
It’s since become apparent that you often do need to send HTML over the network, and things seem to be moving back towards handling as much as possible of your HTML compilation on the server, not on the client.
A fascinating and inspiring meditation on aerodynamics.
The best climate fiction can do more than spur us to action to save the world we have — it can help us conceptualize the worlds, both beautiful and dire, that may lie ahead. These stories can be maps to the future, tools for understanding the complex systems that intertwine with the changing climates to come.
Some welcome perspective on healthcare, conservation, human rights, and energy.
Prompted by my talk, The State Of The Web, Brian zooms out to get some perspective on how browser power is consolidated.
The web is made of clients and servers. There’s a huge amount of diversity in the server space but there’s very little diversity when it comes to clients because making a browser has become so complex and expensive.
But Brian hopes that this complexity and expense could be distributed amongst a large amount of smaller players.
10 companies agreeing to invest $10k apiece to advance and maintain some area of shared interest is every bit as useful as 1 agreeing to invest $100k generally. In fact, maybe it’s more representative.
We believe that there is a very long tail of increasingly smaller companies who could do something, if only they coordinated to fund it together. The further we stretch this out, the more sources we enable, the more its potential adds up.
Ben is writing a chapter a day of this cli-fi story. You can subscribe to the book by email or RSS.
This is a terrific and nuanced talk that packs a lot into less than twenty minutes.
(The secret sauce in transitional web apps is progressive enhancement.)
Twelve short stories of solarpunk cli-fi “envisioning the next 180 years of equitable climate progress.”
Whether built on abundance or adaptation, reform or a new understanding of survival, these stories provide flickers of hope, even joy, and serve as a springboard for exploring how fiction can help create a better reality.
These days I tend to think of dystopias as being fashionable, perhaps lazy, maybe even complacent, because one pleasure of reading them is cozying into the feeling that however bad our present moment is, it’s nowhere near as bad as the ones these poor characters are suffering through.
Kim Stanley Robinson on dystopias and utopias.
The energy flows on this planet, and humanity’s current technological expertise, are together such that it’s physically possible for us to construct a worldwide civilization—meaning a political order—that provides adequate food, water, shelter, clothing, education, and health care for all eight billion humans, while also protecting the livelihood of all the remaining mammals, birds, reptiles, insects, plants, and other life-forms that we share and co-create this biosphere with. Obviously there are complications, but these are just complications. They are not physical limitations we can’t overcome. So, granting the complications and difficulties, the task at hand is to imagine ways forward to that better place.
At its core, and despite its appropriation, Solarpunk imagines a radically different societal and economic structure.