339 private links
The website we needed
The website we needed
A Dragon Ball Z text generator
We need to ask ourself the question whether "saving for later" is still a rational strategy in an age where more content will always be generated tomorrow.
Some read it for later is useless, but there is nowadays a chance to get personalized feeds with personal curation.
The act of saving for later is an illusion compared to learning or engaging.
Why do we keep saving content we know we’ll never consume?
What we are observing here is a societal pressure to consume endlessly, to be productive, enriched, and entertained.
How to break the cycle:
- two-minute rule
- 80/20 rule: sort content, only read high-quality articles for you
- schedule dedicated reading time
- one in, one out: maybe have a limited backlog size
It's very chromium dependent though
A good use of <picture>, sparingly creating a system to fetch the main content of the page, minification, image optimization of all formats,
The final product was lightning-fast even on the weakest data connections and most underpowered devices. Showing it off at trade shows, we found that competitive products were still displaying a loading spinner when our application was already loaded, rendered, and running.
Oh ok: the new UA styles will have uniform headings and not :is(article, aside, nav, section)
Score: 29
You are the web developer equivalent of the quiet old man in the bar who lurks in the corner and only interjects when the main character reaches a moment of crisis. You've seen some shit, enough to know when to sit down and shut up. You are so far into nerd territory that you're now cool again.
I also discovered the blog post via ThePrimeagean.
A follow-up post is published on the blog of Turso https://turso.tech/blog/working-on-databases-from-prison
It may be useful later:
- storing response variables
- transposing data
- showing SQL statements and output in the same file
Let's call the company Microslop
DeepSeek écrase OpenAI en volume mais perd sur la vraie valeur : pendant que le géant chinois se tape du roleplay, Claude rafle 60% des contrats de programmation qui rapportent
L'Asie a le plus d'utilisateur en un an (13% à 31%) pendant que l'Europe dort : Singapour dépasse l'Allemagne et la Chine, l'Afrique reste à 0,46%.
Les modèles qui réfléchissent passent de zéro à 50% des nouveaux usages en moins d'un an : on n'utilise plus des chatbots, on utilise des cerveaux numériques qui délibèrent avant de répondre
Note qu'il s'agit d'un aggrégateur open source de différents IA
There are already many libraries in different languages. The goal is to encode mushroom information in QR codes. So it's a sort of specification for it.
The official website https://www.wemush.com/open-standard with its github project https://github.com/wemush/open-standard
Les autres domaines restent accessibles:
A quick analyzer of a website.
The source code is available at https://github.com/Lissy93/web-check
A great summary of the database news in 2025
PostgreSQL is the state of the art database with wide range support of features.
If 2023 was the year every DBMS added a vector index, then 2025 was the year that every DBMS added support for Anthropic's Model Context Protocol (MCP)
New file formats emerged. Why not using Parquet?
The main problem with Parquet is not inherent in the format itself. The specification can and has evolved. Nobody expected organizations to rewrite petabytes of legacy files to update them to the latest Parquet version. The problem is that there are so many implementations of reader/writer libraries in different languages, each supporting a distinct subset of the specification. Our analysis of Parquet files in the wild found that 94% of them use only v1 features from 2013, even though their creation timestamps are after 2020.
The use of a lot of icons in menus is a bad pattern.
12px icons are also too small for details.