A cute explanation of different browser caches:
- memory cache,
- service worker cache,
- disk cache, and
- push cache.
A cute explanation of different browser caches:
Here’s a great opportunity for somebody looking to level up in web development—mentorship from the one and only Aaron Gustafson.
There’s going to be an evening of astro events out at Sussex University next Wednesday, January 18th. Stargazing, an inflatable planetarium, and the Ensonglopedia of science—fun for all the family!
A wonderfully thoughtful piece from Robin, ranging from the printing technologies of the 15th century right up to the latest web technologies. It’s got all my favourite things in there: typography, digital preservation, and service workers. Marvellous!
Well, this is nice! Susan has listed the passages she highlighted from Resilient Web Design.
In the spirit of the book, I read it in a browser, and I broke up my highlights by chapters. As usual, you should read the book yourself, these highlights are taken out of context and better when you’ve read the whole thing.
This looks like an interesting little Markdown editor. I think I’ll take it for a spin.
Chris redesigned CSS Tricks and it’s got some really nice touches. I particularly like the stacked card view on mobile.
As always with sci-fi interfaces, the important part is telling the story, not realism or accuracy. Personally, I liked the way that the World War II trappings of Rogue One extended to communications and networking technologies.
Watching this data visualisation on its high speed setting is quite hypnotic.
Making fire, building shelter, throwing spears …all useful post-apocalyptic skills documented on the primitive technology blog.
Primitive technology is a hobby where you make things in the wild completely from scratch using no modern tools or materials. This is the strict rule. If you want a fire- use fire sticks, an axe- pick up a stone and shape it, a hut- build one from trees, mud, rocks etc. The challenge is seeing how far you can go without modern technology. If this hobby interests you then this blog might be what you are looking for.
I can relate to what Rachel describes here—I really like using my own website as a playground to try out new technologies. That’s half the fun of the indie web.
I had already decided to bring my content back home in 2017, but I’d also like to think about this idea of using my own site to better demonstrate and play with the new technologies I write about.
Paul is turning his excellent talk on design systems into a three part series. Here’s part one, looking at urban planning from Brasília to London.
When a solid 67% of your soul is engaged with battles elsewhere, how do you continue on with our ongoing, non-revolutionary work?
A resource for American citizens put together by former congressional staffers. If you’re a US citizen wondering how you can resist Trump’s agenda, this should provide solid advice on what action you can take.
I love this recasting of the internet into a fantastical medieval setting. Standards become spells, standards bodies become guilds and orders of a coven, and technologies become instruments of divination. Here, for example, is the retelling of IPv4:
The Unique Rune of the Fourth Order is the original and formative Unique Rune, still commonly in use. All existing Unique Runes of the Fourth Order were created simultaneously in the late 1970’s by the Numberkeepers, at a time when Rough Telepathy was a small and speculative effort tightly affiliated with the Warring Kingdom of the United States. There were then and are now 4.3 billion Unique Runes of the Fourth Order, a number which cannot be increased. The early Numberkeepers believed 4.3 billion would be more than enough. However, this number is no longer sufficient to provision the masses hungry to never disengage from participation in Rough Telepathy, and the Merchants eager to harness Rough Telepathy as a “feature” in new and often unnecessary consumer products. This shortage has caused considerable headache among the Fiefdoms, the Regional Telepathy Registers, and the Coven.
So if AMP is useful it’s because it raises the stakes. If we (news developers) don’t figure out faster ways to load our pages for readers, then we’re going to lose a lot of magic.
A number of developers answered questions on the potential effects of Google’s AMP project. This answer resonates a lot with my own feelings:
AMP is basically web performance best practices dressed up as a file format. That’s a very clever solution to what is, at heart, a cultural problem: when management (in one form or another) comes to the CMS team at a news organization and asks to add more junk to the site, saying “we can’t do that because AMP” is a much more powerful argument than trying to explain why a pop-over “Like us on Facebook!” modal is driving our readers to drink.
But the danger is that AMP turns into a long-term “solution” instead of a stop-gap:
So in a sense, the best possible outcome is that AMP is disruptive enough to shake the boardroom into understanding the importance of performance in platform decisions (and making the hard business decisions this demands), but that developers are allowed to implement those decisions in standard HTML instead of adding yet another delivery format to their export pipeline.
The ideal situation looks a lot more like Tim’s proposal:
Aaron documents how he posts to his website through his Amazon Echo. No interface left behind.
I understand how bloated and non-reusable code can get when a dozen people who don’t talk to each other work on it over a period of years. I don’t believe the problem is the principle of semantic markup or the cascade in CSS. I believe the problem is a dozen people working on something without talking to each other.
I really like Liz’s long-zoom perspective in this look ahead to journalism in 2017.