313 private links
Une histoire de prédation en deux toots.
2017 : j'achète une licence oXygen. Soit-disant à vie. Quelque chose comme 200 euros mais bon, pour une licence permanente ça vaut le coup.
2019 : y a de plus en plus de mises à jour, c'est chiant, et je dois faire bosser des étudiants, je trouve une alternative un peu moins bien mais gratuite, j'utilise moins oXygen.
2024 : ma licence n'est plus valable (je m'en rends compte au hasard d'un changement d'ordinateur, oups je peux plus installer oXygen depuis la version de 2020 en fait). Je me passe d'oXygen.
2025 : je tombe sur un os, il y a un truc que je ne peux faire bien qu'avec oXygen. Je regarde les tarifs pour racheter une licence. Je crie.
It’s a "crisis" when immigrants "take jobs away", but "innovation" when machines do. Funny.
How money flows between big US AI companies
CSS styling has no perfect solutions but tradeoffs between the different approaches. Choose the one that fits best to the project
<output> is currently underused in so many SPAs and apps, because it announces
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 junktimeseries 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.
- Find out what is seen as valuable
- Deliver value as often as possible to get feedback
- Write and maintain integration tests that survive refactoring
- Avoid Object-Oriented Programming, or at least be extra careful with it
- Remember you can still add in that complication tomorrow
- Be conscious of what makes you over-engineer
- Get yourself a better definition of perfection