Not Every Article Needs A Picture

Adults do not need pictures to help them read. I understand that not putting photos on top of every single article might seem like a big undertaking at first, but once a few braves sites take it up, others will quickly follow suit. Putting a generic photo of a cell phone on top of an article about cell phones is insulting. To be clear: I am not an iconoclast. Including images in a story can be a nice addition; the problem is that this has now become a mandatory practice. Not every article should require a picture.

via Not every article needs a picture | The Outline


Read Only Web |

Are we moving to a text-only reading view experience of the web?

With Safari 11 able to launch pages in reader view by default, is this a signal from Apples metrics, that people want a stripped back reading view of the web only?

Has the elegance of Mediums typography and sparse presentation, along with the speed of Fb Instant Articles and AMP conditioned readers to a slick minimal experience? Do people associate content with a fresh post in a timeline rather than navigating to a new website? Or did the persistent adverts and interstitials drive people to wanting something plainer? Yes, probably.

via Read Only Web |

Web development explained to a time traveler from ten years ago

I’m glad that you’re still interested in computers! Today we have many more of them than we did 10 years ago, and that comes with new challenges. We wear computers on our wrists and faces, keep them in our pockets, and have them in our fridges and kettles. The cars are driving themselves pretty well, and we’ve taught programs to be better than humans at pretty much every game out there — except maybe drinking.

Crazy what can happen in 10 years.

via Web development explained to a time traveler from ten years ago

iPhone Next?

With the iPhone 8 and X now out. I have to say I’m not blown away by either design. I’m really not sure about the black screen border of the X. Regarding the notch, I don’t think you will notice it in use – web designers will mind that yet again there is Apple specific meta tags and code to include in web pages again.

What can Apple do next year?

The inspiration for this post, apart from those quick thoughts. What happens to the iPhone next?

  • An iPhone 9 and an X-S?. A ‘tock’ year? Likely.
  • A single iPhone 9 – OR call it 11 – that embodies the X design and drop the X? I like this idea. I cant see how you could skip back from X(10) to 9.
  • Skip a year completely and concentrate on other hardware? I feel like this would help focus things at Apple but there is too much money at stake to consider this.

I think they have made it tricky for themselves going forwards. The X might continue as showcase but if that accelerates away from the regular iPhone you risk overshadowing it. Its going to be tricky to keep two distinct designs and specs that are different enough and don’t disrupt each other. Mr Cook keeping logistics interesting at Apple.

Frustrations With Live Streaming

I just don’t get the live streaming trend. Every app decided it must have chat, then ‘stories’, next must-have seems to be live streaming.

The argument for timeliness, live video is made for this. See events unfold via people at the scene, get up to the minute reaction, interactivity, FOMO.

Was Live, Didn’t Miss Much

However, the timeliness becomes the issue, the ‘live’ part. I am very familiar with the, ‘Sorry, stream ended’ message. Ninety five percent of live streams, I miss.

On the rare occasions I make it in time (or the rare case they provide recording), live streams break down to this:

  • The broadcaster asking viewers if they can be seen and heard
  • Awkwardly presenting whatever it is they wanted to show, live is hard
  • Interrupting themselves answering the same questions with viewers in the chat, to the point of frustration

I just don’t see how you monetise something like this long-term. The timeliness ensures it is quickly no longer relevant. The quality is often not good enough to justify seeking out to watch. I know I will read this post in a few years and tut to myself. Right now, I just don’t get it.

Saying Goodbye To Firebug

Firebug has been a phenomenal success. Over its 12-year lifespan, the open source tool developed a near cult following among web developers. When it came out in 2005, Firebug was the first tool to let programmers inspect, edit, and debug code right in the Firefox browser. It also let you monitor CSS, HTML, and JavaScript live in any web page, which was a huge step forward.

Firebug caught people’s attention — and more than a million loyal fans still use it today.

So it’s sad that Firebug is now reaching end-of-life in the Firefox browser, with the release of Firefox Quantum (version 57) next month. The good news is that all the capabilities of Firebug are now present in current Firefox Developer Tools.

via Saying Goodbye to Firebug ★ Mozilla Hacks – the Web developer blog

Firebug was a revelation when I first downloaded it around 10 years ago. Live editing and learning almost as fast what mistakes I had made. So long friend.