Last Saturday, Sam introduced me to Chris Coyier’s talk on serverless-ness, The All-Powerful Front-End Developer. Pretty interesting and useful. I’m glad he leads it by breaking down the problematic nature of the word “serverless”! The following day was spent in agorama’s p2p workshop at furtherfield. Coincidentally, there is a lot of overlap in these topics.
I’ve spent the past few days wrapping my head around all of this, contextualising it against the sorts of concerns and projects we work with. Though I desperately want to get going with Dat, I’m starting with serverless because it may solve an urgent need in my day-to-day work. Right now, I’m spending much more time than I realistically can maintaining CMSs and hosting environments for older websites.
All of the below is a thought dump on the topic, an attempt to pick apart the meaning of and the use cases for a serverless website architecture. I am by no means an expert, so if anyone out there in the big wide 🌎 reads this and has suggestions, particularly if I’ve misstated anything, let me know. This site is comment-less on purpose, so tell me on Twitter or send me an email at email@example.com.
- Remote Only manifesto
- CSS-Tricks Screencast #160: The All-Powerful Front-End Developer
- Dotori, a Japanese+Korean restaurant in London
- Enoki Panel
- How I publish taravancil.com on the peer-to-peer Web
- Webtask – high hopes for this, but running in to issues w/ connecting to Airtable; TBC
- IPFS – not sure how I feel about IPFS, but worth being aware of it
- Txt file of all IETF RFCs – see 1630 specifically (!)
- NYC Mesh
- devMode.fm on support/maintenance retainers
- P2P Superchannel on Are.na
Going to write up more about serverless and P2P, and how they kind of intersect, once I’ve digested some of this.
Surfing w/ coffee 3. Order of exploration, seems more single-track than usual:
Open Hacker News, drawn to Frequent versus infrequent developers (in languages and so on) (↓B) (↓C)
Is it worth the time? on XKCD; pleased to find this again
Hello, I am a DWiki (↓D)
Wiki Principles (↓E)
Wiki Is Not Wikipedia (↓F)
Cunningham & Cunningham Inc., “a small consultancy that has specialized in object-oriented programming” (↓H) (↓I) (↓J)
Plate Blading; “As he skates away he feels the need to fabricate further explanation.”
C2.COM as Public Space; “Have you ever noticed that some publicly owned museums can be hard to see while privately owned billboards are hard to avoid?”
Did some research on Chinese web font best practices a while back when working on Memory Machine for Tyler Coburn + Asia Art Archive with Luke Gould. It was an interesting challenge. This was my overall takeaway from the research:
- Self-hosted fonts are out, the font files are prohibitively enormous due to the number of characters
- The Great Firewall can cause issues with most font services, so no Google Fonts or Typekit
- If you need to render a mixture of Latin and Chinese characters and want them to use different fonts, the font stack structure and naming is critical (see article by Kendra Schaefer for more info)
- Bold and italic should never be used for emphasis on Chinese characters since it distorts their meaning
The e-newsletters we made for Penguin Classics got a mention in a recent newsletter from The Better Email [✉ ∞]. Made me smile. Here are a few newsletters from the Penguin Random House team that I particularly like.
We’re picking up a Shopify site that was put on hold for a little bit, and I’m pleasantly surprised by a few things I’ve come across. The pause might have been blessing in disguise for the site on the whole. The dev tools have progressed a bit during the hiatus, and I’ve come across a Sections workaround that might 🤞 give a little more content flexibility beyond the homepage.