Github va devenir de plus en plus important pour Microsoft.

Je parie que le service va se merdifier durant les prochaines années; comme déjà les PRs de Copilot.

858TB of data over 8 years.
In fact, their G-Drive is designed as a high-capacity, low-performance storage system, and they have regulatory constraints that require exclusive storage on this platform to prevent data leaks.

In short, for all official documents that have gone through formal approval processes, there is hope of recovery via their OnNara system (another government system that stores final reports), but for everything else (drafts, work-in-progress files, internal notes, etc.), it's dead as a doornail...

Lidarr, Prowlarr, Radarr, Sonarr, and Whisparr are collectively referred to as "arr" or "arrs". They are designed to automatically grab, sort, organize, and monitor your Music, Movie, E-Book, or TV Show collections for Lidarr, Radarr, Sonarr, and Whisparr; and to manage your indexers and keep them in sync with the aforementioned apps for Prowlarr. This list aims to list all *arrs and things related to them

After a few years of using both (see Optimizing SQLite for servers for example), I've found that SQLite particularly shines when used for internal services or public services where a small amount of downtime is tolerable.

So, I choose PostgreSQL (preferably with a managed provider) if the service needs (close to) 100% uptime, if the service needs more than 5 Gbps of bandwidth or if the database is expected to grow larger than 200GB. [...] Bascially, all the situations where running on a single server is not possible.

It's important to note that with the advent of DuckDB, Parquet and Apache Iceberg, there is less and less reasons to stuff your main database with useless junk timeseries data, and instead only keep some kind of materialized view and send the raw data to S3. Thus, there are less and less reasons for your main database to be over 200 GB.

1. Find out what is seen as valuable
2. Deliver value as often as possible to get feedback
3. Write and maintain integration tests that survive refactoring
4. Avoid Object-Oriented Programming, or at least be extra careful with it
5. Remember you can still add in that complication tomorrow
6. Be conscious of what makes you over-engineer
7. Get yourself a better definition of perfection

from https://shaarli.lyokolux.space/shaare/4Rg2EQ

Looking for examples of web magazines made with html/css [so the 3. option].
The spectrum:

1. a website with branching levels of navigation, average content-heavy website
2. a website with single level of linear paginated navigation, back and forth, text-heavy html/epub
3. a responsive paginated website that mimics printed magazines in the best way possible, and looks interesting on all screens
4. embedded static PDF viewer with page turn and zoom
5. static PDF

Usages:

1. Circular menus or item lists
2. Wavy layouts (DNA strands, wave)

Fancy animations

1.2. Train est une initiative d'un seul développeur. Cependant le service croît constamment depuis ses débuts.

La suite https://www.macg.co/mobilites/2024/09/billets-de-train-12train-le-petit-poucet-qui-prend-le-contrepied-de-sncf-connect-146067

C'est délirant puisque l'IA n'est pas encore capable de remplacer les jobs.

Lien du projet: https://framagit.org/framasoft/lokas/

Le coût de l'IA doit se rentabiliser.

Et c'est le moment où Framablog suggère GNU/Linux, et comment le faire.