Two lessons from algorithms:

1. Debugging complex code is hard, first simplify, then debug.
2. Single source of truth is good

Second, algorithms teach about properties and invariants.
Third, algorithms occasionally are useful at the job!
Fourth, connecting to the previous ones, the ideas really do form interconnected web which, on a deep level, underpins a whole lot of stuff.

Here again a list of algorithms.

About one disadvantage of the deployment on the edge

Pas con du tout:

Il faudrait obliger les éditeurs, que ce soit des JV, films ou musique, ebook… de libérer le produit si jamais ils décident de le retirer de leur « store ».

S'ils ne le font pas, alors le droit au copyright leur ai retiré.

"Cela nous permettrait - enfin - d'arrêter de voir notre patrimoine culturel disparaître (ce qui est gravissime pour l'humanité)." - Sebsauvage

Resources to learn programming: in which order or why. Sources are different

On the part about algorithms:

We teach algorithms so that students learn to think about invariants and properties when writing code. Real-life code is usually simple enough that it mostly works if you just throw spaghetti onto the wall. But it doesn’t always work. To write correct, robust code at work, you need to think about invariants.

There is a list of algorithms too :)

And there is one site for every main programming topic: compilers, OS, ...

There are silo sites, unrepairable miniaturized hardware, and streaming services...

The irony …is that they used our tech to do all three of these things. Oh well. AGPL for the win, next time.

People do not experience the same sense of the flow of time. For some, only now and not now exists.

Defining a subset of the web that removes a lot of complexity :)

Provide a local index of sites complying with the requirements above, so that sites can be found without the use of an external search engine.

How does this scale? How is the index sorted? That was originally the answer provided by search engines.

If a state is important enough to indicate visually, it's probably important enough to expose to assistive technologies.

With an example such as <a href="/about" aria-current="page" class="current-page">, we now have two meanings that convey the same information: the aria attribute and the class. This can leads to bugs while refactoring.

Another example is provided with dropdowns or toggle buttons, and sorted table columns.
Mentions to :disabled or aria-disabled, :invalid or aria-invalid, aria-selected, role="tab", and the list can go on!

When you develop a major new feature, product, anything, one of the defining characteristics is that you don't know what you're building. The only way you know what you're building is if you've built it before.

This leads to a problem: If you don't know what you're building, how do you know where the rough edges are? How do you know what the design demands, and what technical decisions to make?

Or the limit of altruism:

As lovely as it might seem, our selfless actions usually get prioritized above looking after ourselves.

We will go to unending lengths to look after the ones we love, and even the ones we don’t. We are empaths, we want the best for everyone, so we do our best to try and give them that, usually to our own detriment through self-neglect.

Here is why:

• there are also hundreds of blogs out there
• you're not an expert
• you are showing the world how stupid you are
• people noticizing your blog will trash it

On the other hand,

• it is notes to your future self
• release ideas that you have in your head
• learn to write and express ideas
• add a personal view
• writing about a subject can lead to being someone's hero some day.
• it's cool
• you can write whatever you want

Dancing ftw

Why Wikipedia can not be written by AI for now, and its limits.

One thing is that AI needs human in order to get better. Another is AI can only know what is public on the Internet. At last its output is not fact-checked.

One advantage in svelte is that we can integrate JS libraries quickly

In his 1959 classic, The Sociological Imagination, the great sociologist C. Wright Mills told students of the discipline:

As a social scientist, you have to … capture what you experience and sort it out; only in this way can you hope to use it to guide and test your reflection, and in the process shape yourself as an intellectual craftsman. But how can you do this? One answer is to set up a blog: there is joined personal experience and professional activities, studies underway, and studies planned. In this blog, you … will try to get together what you are doing intellectually and what you are experiencing as a person. here you will not be afraid to relate your experience directly to various works in progress. By serving as a check on repetitious work, your blog also enables you to conserve your energy. It also encourages you to capture ‘fringe thoughts’: various ideas which may be byproducts of everyday life, snatches of conversation overheard in the street, or, for that matter, dreams. Once noted, these may lead to more systematic thinking and lend intellectual relevance to more directed experience.

and a reference to the currently very small Blue Dwarf social network

1. Succeed is a blurry term. How a social network will succeed?
2. Every social network is there for a limited duration and will be useful to a limited niche of people. Even Facebook: there are more people without an account than with one.
3. Everyone live in a small niche (or communities) that uses only some social networks.
4. Our communities are worth a lot more than the underlying tool used at some point in time.

Brackets are allowed in URLs. It makes it hader to handle than first though!

The author propose a regex, but it is still not valid as only the extended ascii is in it.

Yes, it is hard to parse URL correctly.

Par comparaison, Internet ressemble à la rue