AVIF est à préférer. Le codec est plus performant que VP9 (dans WebP) et H.264 (dans JPEG). La qualité de l'image est aussi meilleure (gammes de coloeur, divers espaces colorimétriques) et sans redevance. Le support d'AVIF n'est pas encore optimal pour les navigateurs, mais atteint Baseline 2024.

WebP est au contraire établi, avec ou sans perte.

L'interface web de Pandoc pour convertir des documents

Using text files. The expenses can be tracked with beancount. It tracks many in or out of many bank accounts with the "double-entry accounting".
Documents can be attached to transactions, etc...

The dataflow is the following:

1. Download transactions from the bank (csv, pdf or ofx files).
2. Convert these files to the beancount format. There are many plugins available.
3. Balance the transactions to get the "double-entry accounting"

In my experience so far, it has been the exact opposite. The entire process has never taken me more than 45 minutes to finish. Considering that I do this once a month, the time investment seems more than fair. And the added benefit is that by balancing these transactions by hand, I get a fairly good idea of what was happening in my accounts in the previous month.

Visualization can be made with SQL queries, or Fava as UI. See a demo

L'une de mes inquiétudes est la gestion du projet. Typst est à 100 % du logiciel libre (licence Apache) mais son développement est apparemment étroitement contrôlé par une seule entreprise, qui commercialise des extensions privatrices à Typst et dont il n'est pas certain qu'ils acceptent d'ouvrir le projet.

Sinon le projet a l'air excellent

Des fichiers .http normalisent les appels d'APIs

PNG renders top to bottom but the interlaced mode increase significantly the file size. WebP too at 28%.

AVIF has a progressive flag for it. It creates two layers. One at 1/8th resolution and minimum quality and one at full resolution and good quality. The first layer has 5.8kB as example, and the full image is 151kB. It's still experimental with avifenc.

JPEG XL (abbreviated JXL) renders on Chrome at 39% of the file.

The AVIF image provided as example is 56.4kB, which is incredible for a more than HD image.
For many images, there's little benefit to progressive rendering (the fox with many details is an exception). So progressive rendering is often a mix of good and bad luck.

The author claims JXL progressive rendering promises won't work, because there is a significant lag between each of the progressive rendering steps. It can work efficiently with srcset for example.

JXL still looks promising, but the AVIF progressive rendering of the fox is somewhat better than the 17-27kB alternative of JXL.

Note: a post-processed blur on a scaled down image results in 2kB. 10kB makes the image "acceptable" for the human eyes. The image is still pretty good for previews. The post-process blur would need to be part of the format, rather than left to something like CSS to make JXL.

and because it's an entirely separate image, the decoding overhead is zero if the browser doesn't see a benefit to displaying the preview. As in, in cases where the browser has the whole file, it can just skip the preview.

I will have to look after the AVIF format, because it seems to be the best of Webp (20-30% better compression), GIF (with animation) and better image quality than JPEG.
See the german wikipedia page or the english one

S3 is the format used in companies nowadays.

WebDAV is however here since a long time and works well.

Typst has a simpler markup system and easier customization.

There are several reasons for this dissatisfaction: the LaTeX installation is huge, compilation of large documents is not fast, and its error messages are riddles delivered by an infuriating oracle

In 2019 two German developers, Laurenz Mädje and Martin Haug, decided to try to write a LaTeX replacement "just for fun". In 2022, Mädje wrote his computer science master's thesis about Typst. In March 2023, its first pre-release beta version was announced; a month later, semantic versioning was adopted with the release of v0.1.0. Typst is now at v.0.13.1 and shows 365 contributors on its GitHub repository.

Markup in Typst is less verbose and easier to read than in LaTeX.

The simplest markup looks similar to markdown.

Typst drawbacks:

• Typst's page layout algorithm doesn't always permit the refinements that LaTeX is capable of.
• lack of specialized package (it's obvious compared to LaTeX)
• the documentation is criticized:
• inability to include PDF documents (for now)

One day, one line.

YYYY-MM-DD wWW Aaa HH event. HH-HH another event.

For example: 2021-02-15 w07 Mon 9-12 project groups. 17 jogging.

It has limits if informations needs to be stored for each event though :/

An argumentation against Xz. For later in case I will come up to the topic.

How a QR code encodes information step by step. How to decode it by hand.

PNG 3.0 https://www.w3.org/TR/png-3/

1. Animated PNG will be supported (.apng)
2. HDR support
3. Exif metadata support

The working group work on better interoperability of HDR/SDR.

More on https://www.programmax.net/articles/png-is-back/

application/x-www-form-urlencoded and multipart/form-data are still messy years later.

All smallest possible file per format

10 topics to consider while creating a file format.

Import et Export of software forges (issues, PR/MR, milestones, release assets, etc...)

age.xml is a free and easy-to-use website label that gives parental control systems information about a website’s age rating

(via https://nicolas-delsaux.hd.free.fr/Shaarli/shaare/LMJ21Q)