Well, I'm glad that SDL solved the wrapping problem of SDL_GetTicks() by using 64 bit integers but they didn't warn me that it TOO wraps every ~584942417 years!

How am I suppose to use this for my high availability software?

🤡

via @gruber.foo

bonjour les bleus cielzard

🥶

>paye 45 euros pour un abonnement dans une salle sans engagement
>accès libre à 5 euros (pour le dimanche)
>paye l’accès libre (on est plus à ça près)
>arrive à la salle un dimanche
>il faut une carte pour l’accès libre qu’on ne m’a pas donné

J’ai comme l’impression qu’on m’a craché à la gueule

Decided to move to ghostty and give it a try, so far:
- Configuration is easy, as good as kitty/wezterm
- Performances are great, seem faster than wezterm but slower than kitty

Nix does not provide any module yet but writing a config that copies itself in the config folder is easy.

Eclipse applications and toolings are just terrible. So much error prone and barely usable on some platforms.

so if I'm understanding the tech-bro position correctly, it's this

NixOS/Nix is just good in this era of software engineering. Being able to reproduce a dev environment is mandatory, even more if you work in a company and tend to work on a lot of small projects.

lads see this and go « hell yeah »

Quelle belle fin Arcane 🥹

Most of my work in my last year of master degree has been interacting with an LLM and writing reports about it. Never felt as shitty as recently, I’m basically a golem feeding LLMs.

We are cooked.

(On est en train saigner les universités)

www.lemonde.fr/societe/arti...

can I code fast? no. but can I code well? also no. but does my code work? alas, no

React 19 and NextJS are just piles of shit.

I thought I was just being an hater because I had little professional experience with it and with web overall but past months made me realize how shitty this thing is.

Let it die

>code coverage: 0.1%