Hashicorp co-founder Mitchell Hashimoto says GitHub's frequent outages have made it "no longer a place for serious work," prompting him to move his Ghostty terminal emulator project elsewhere after 18 years on the platform. The Register reports: "I've been angry about it. I've hurt people's feelings. I've been lashing out. Because GitHub is failing me, every single day, and it is personal. It is irrationally personal," he wrote. The reason for his ire is the service has become unreliable. "For the past month I've kept a journal where I put an 'X' next to every date where a GitHub outage has negatively impacted my ability to work," he wrote. "Almost every day has an 'X'. On the day I am writing this post, I've been unable to do any PR review for ~2 hours because there is a GitHub Actions outage." Hashimoto penned his post a few days before an April 28 incident that saw pull requests fail to complete due to an Elasticsearch SNAFU. Incidents like that mean Hashimoto has decided GitHub "is no longer a place for serious work if it just blocks you out for hours per day, every day." "It's not a fun place for me to be anymore," he lamented. "I want to be there but it doesn't want me to be there. I want to get work done and it doesn't want me to get work done. I want to ship software and it doesn't want me to ship software." The developer says he wants GitHub to improve, but "I also want to code. And I can't code with GitHub anymore. I'm sorry. After 18 years, I've got to go." He's open to a return if GitHub can deliver "real results and improvements, not words and promises." But for now, he's working to move Ghostty to another collaborative code locker. "We have a plan but I'm also very much still in discussions with multiple providers (both commercial and FOSS)," Hashimoto wrote. "It'll take us time to remove all of our dependencies on GitHub and we have a plan in place to do it as incrementally as possible." He's doing the equivalent of leaving a toothbrush at a former partner's house by leaving a read-only mirror of Ghostty on GitHub, and by keeping his personal projects on the Microsoft-owned service. But Hashimoto's moving his day job somewhere new. "Ghostty is where I, our maintainers, and our open source community are most impacted so that is the focus of this change. We'll see where it goes after that," he concluded.

Read more of this story at Slashdot.

La version 11 de Wine, ce n'est pas juste une accumulation de petits patchs. C'est un game-changer (haha désolé pour le jeu de mots pourri).

Les changements importants:
- NTSYNC est implémenté. Si vous avez un noyau 6.14 ou plus récent, Wine pourra utiliser NTSync au lieu de esync/fsync. Si vous utilisiez déjà esync/fsync vous ne verrez pas beaucoup de différence (mais ntsync est plus propre), mais dans le cas contraire cela améliore les performances dans certains jeux de manière spectaculaire.
- WoW64 est terminé. Vous n'avez donc plus à jongler entre librairies système 32 et 64 bits dans les préfixes Wine. Installez tout en 64 bits, et les applications 32 bits fonctionneront tel quel. C'est particulièrement intéressant pour faire tourner les anciens jeux.
- et il y a bien entendu encore des tas d'autres améliorations (support Wayland, support contrôlleurs, etc.)

Si vous étiez sous Wine 9 ou 10, je vous encourage fortement à passer à la 11.

Contexte : Wine est un logiciel Linux qui permet de faire fonctionner les applications et jeux Windows sous Linux sans avoir besoin d'installer Windows. Plus de 90% des jeux Windows existants tournent sans problème dans Wine.

Pour voir si le module ntsync est chargé dans votre système:
💻 lsmod | grep -i ntsync

Pour le charger:
💻 sudo modprobe ntsync
(et /dev/ntsync doit apparaître)

L'activer au lancement du système:
Créer le fichier /etc/modules-load.d/ntsync.conf
contenant juste : "ntsync"
(Permalink)

Sous le coude: Un émulateur d'Arduino dans le navigateur pour tester vos projets.
(Permalink)