TL;DR;

Capitalism was aware of the Y2K bug and took action even if it costs millions.

This is because my colleagues and my friends and I had been engaged in a multi-billion dollar, multi-year, multi-million person, quasi-coordinated project to fix the problem.

There are two obstacles to climate change to follow the same path though:

Responsibility for climate change is sparse and does not benefit an actor in particular if one makes some effort.

Capitalism's secondary tenet, short-termism, doesn't permit it to respond to non-specific risks, even if they're real, because that would require committing wealth to an effort from which 1-year or 5-year returns can't be measured in terms of greater wealth.

Social Networks provide a social status, so they can be compared to Status as a Service tools.

We can define a Social Capital ROI: If a person posts something interesting to a platform, how quickly do they gain likes and comments and reactions and followers?

It also explains why copying proof of work is a lousy strategy for status-driven networks

Social capital accumulation skews young: I'd wager that we'd see that young people, especially those from their teens, when kids seem to be given their first cell phones, through early 20's, are those who dominate the game. Young people tend to be the tip of the spear when it comes to catapulting new Status as a Service businesses, and may always will be.

We can then define a social network on 2 axes: social capital and utility, with both ranging from low to high.

IMDb, Wikipedia, Reddit, and Quora are more prominent examples here. Users come for the status, and help to build a tool for the commons: they are low social capital, but high utilities

The best high social utility seems to be WeChat at the moment.

The author go in depth into when a status as a service business will stop to grow. The so-called social capital inflation and devaluation, because it is what is valued on those platforms. it is too much for me at the moment, but it seems relevant.

Presumption of innocence -> every person is considered innocent until proven guilty.
⬇️
Presumption of bug-free -> every issue is considered innocent until proven with minimal reproduction.
👌

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