“Decentralization is Not Enough - A conversation with Nolan Lawson”
“Limiting JavaScript? - TimKadlec.com”
“If Webkit pursues the idea further, they wouldn’t be alone.”
“Ending our Medium integration — write.as blog”
“Sometime in the past few weeks, Medium abruptly deleted third-party access to their publishing API”
So many reasons not to use Medium
“Google Play Store now open for Progressive Web Apps 😱”
Very interesting.
Reading, Dyslexia, and Typefaces
The following is prompted by seeing Adrian Roselli’s blog posts (see below) on this topic crop up again.
Something that’s cropping up semi-regularly in my research for the reader (or Ink, whatever) is the fact that the benefit of fonts for dyslexia generally aren’t supported by research, at least not to the degree that you can confidently make product design decisions. In some cases ~50% of readers think their reading has improved when it objectively hasn’t.
Also, the core thesis behind these designs, that all readers with dyslexia see letters flip or rotate is pretty controversial and, even if true, only counteract a subset of issues readers with dyslexia face.
And another thing that seems consistent is that other typographical variables like type size, alignment, contrast, paragraph spacing, line length, serifs, and italics have a greater effect on readability for readers with dyslexia than a specific typeface for dyslexia.
(One likely thesis at this point is that dyslexia is a symptom and the cause can vary enormously.)
- “Typefaces for Dyslexia”
- “Variable Fonts and Dyslexia”
- “6 Surprising Bad Practices That Hurt Dyslexic Users”
It’s important to note that there is considerable controversy around whether or not fonts can provide any benefit for people with dyslexia.
(From “Dyslexia, Fonts & Open Source”)
What is missing from these news reports is scientific evidence that special dyslexia fonts are actually better for dyslexic readers than commonly used fonts
(From “TYPOGRAPHY & DYSLEXIA”)
“194028 – Add limits to the amount of JavaScript that can be loaded by a website”
JS people, in their zeal to pile on the idea of JS budgets, forget that iOS at least already has rudimentary budgets. I can tell you that as an iOS user I do notice that forgetfulness
“HTML, CSS and our vanishing industry entry points”
Pretty sure I already linked to this. Doing it again.
“Manton Reece - Custom templates, categories, new theme, and more”
Very nice. 👍🏻
“Using ES modules as a modern baseline for progressive enhancement – Alex Gibson”
‘”Never-Slow Mode” (I113b0dc6) · Gerrit Code Review’
I find the various proposals for limiting web page resources to various budgets to be really interesting.
This looks really nice.
“Accessible Page Navigation in Single Page Apps - daverupert.com”
‘PWAs on iOS 12.2 beta: the good, the bad, and the “not sure yet if good”’
“Progressive Web App Progress in iOS 12.2 Beta 1 (Build 16E5181f)”
“A look at CSS hyphenation in 2019 - justmarkup”
I wouldn’t describe support for CSS hyphenation as “solid”. But it’s still pretty usable.
“HTML is and always was a compilation target – can we deal with that? - Christian Heilmann”
I don’t care about how the HTML is structured long as the things that need to be semantic are (aria, tables, figures, quotes). Many devs seem to forget that HTML is an API.
Not writing semantic HTML is a bit like not using hardware acceleration when that’s available. You aren’t letting the device help you do your job.
“The Legacy of Firefox OS – Ben Francis“
“the legacy of Firefox OS is currently tens of millions of phones and TVs across the world running an out of date browser engine which can probably never be updated”
“Benefits of a daily diary and topic journals - Derek Sivers”
It was pretty snowy outside today.
![mp-photo-alt[]=mp-photo-alt[]=mp-photo-alt[]=](https://cdn.uploads.micro.blog/5097/2019/c9b01d0030.jpg)
