I like to think about websites along two axes:

• Static vs. dynamic — how much of the page updates in response to user interaction?
• Online vs. offline — how much functionality requires a persistent Internet connection?

I like the quadrant that can be built with that: every site I know can be put in it.

The big issue here is, Desktop browsers are irrelevant. Same for people that may read this is on Mastodon.

The vast majority of browser activity is coming from young people (12-25), which use their mobile device for browsing. And, believe it or not, these folks click way more content in a minute than I do.

Still, it would be nice to have 100% FF users on my blog, at least if they are using Linux. But even there it is 50/50.

More and more of the traffic comes from mobiles and the young are the majority of this browsing activity. It is different for companies though!

« L'apartheid était légal.
L'holocauste était légal.
L'esclavage était légal.
Le colonialisme était légal.
La légalité est une question de pouvoir, pas de justice.
»

Emails are not good enough: they can change.

Another ode to the web

KISS

The values of HTML are not exactly the ones of HTML first.
https://html-first.com/

The author recommends to include instead:

• HTML that is actual HTML, i.e., that is valid (common sense, until you start checking)
• HTML that makes full use of HTML features, i.e., that’s not XHTML–HTML
• HTML that is used according to purpose (aka semantic HTML)
• HTML that is accessible

#futurBilletDeBlog
#idea #browserExtension a view source with automatic indentation

Programmers want to write fast apps. But the market doesn’t care.

And the list goes on for th rest of the characteristics: reliability, lightweight, etc...

Programmers have power though.

The butterflies are often represented dead instead of alive.

It can be a meme: instead of talking about semantics, UX is trendy and can be used as trendy shit word instead.
UX HTML is more accessible, less error-prone, more maintainable because it uses the right tags and attributes. Yes it is semantic at the end.
So UX of HTML matters.

The web of things is built on the web of documents, which is built on the web of computers controlled by Domain Name owners, which itself is build on a set of interconnected cables. This is an architecture which provides a social backing to the names for things. It allows people to find out the social aspects of the things they are dealing with, such as provenance, trust, persistence, licensing and appropriate use as well as the raw data. It allows people to figure out what has gone wrong when things don't work, by making the responsibility clear.

The value of this architecture is that each layer leverages the social components of the lower layer's architecture

• Universality
• Open Standards
• Open Web Platform (OWP)
• Open Government through Open Data
• Openness with personal data on the Social Net
• Open Platform
• Open Source
• Open Access
• Open Internet and Net Neutrality

Too many websites could generate nice reports as documents, but had no way to access the data behind it to check and build on the results.

Hypertext systems should take about 1/4 second to move from one place to another. If the delay is longer, people may be distracted; if the delay is much longer, people will stop using the system. If the delay is much shorter, people may not realize that the display has changed.

It is funny how thoughts about speed and user experience were already there before the 2000's.

Issue: Links on the web are often quite slow

One solution is to abandon hypertext links. [...] Have a one-page view.

Another strategy is to exchange one large delay for many small ones. We can sometimes arrange a Web site to to bundle large parts of the data in a package that is pre-loaded at the entrance. Within the site, link response is quick because time-consuming sound, graphic, video, and applets have been pre-loaded onto the user's computer.

A better solution, for sophisticated hypertexts that must provide crisp performance, may be to use the Web as a way to provide access to, and information about, hypertexts that can be downloaded (or purchased) as a unit and then performed on the user's machine.

Principles:

1. Know what motivates you
2. Not everybody needs to (or wants to) progress
3. The way up (or sideways. Or backward.): all roles are relative

The levels of experience in a company, range from Engineer I to III, then Senior engineers (and there are a variety of it).

Other potential sideways steps: Developer relations, Sales engineering, or specialist consultancy roles.