Un desarrollador ucraniano creĂł un agujero negro en su terminal para obligarse a tomar descansos.
Cuanto mĂĄs trabajas sin parar, mĂĄs crece y deforma tu cĂłdigo con su lente gravitacional. Descansas y se encoge.
Red Hat might have committed the biggest open source betrayal in Linux history.
CentOS had been the backbone of enterprise Linux since 2004. Disney, Toyota, Verizon, GoDaddy. All running on it. All completely free.
In December 2020, Red Hat announced CentOS 8 would die eight years earlier than promised.
Gregory Kurtzer, the original co-founder of CentOS, was still watching.
Hours after the announcement he committed to building a replacement. He named it after Rocky McGaugh, his CentOS co-founder who died in 2004 without ever seeing the project succeed.
He called it Rocky Linux.
Within two months Rocky Linux had 10,000 contributors. Within half a day of its first stable release, it was downloaded over 10,000 times. AWS backed the build infrastructure. Within a year it was running in production across the industry.
Red Hat did not stop there.
In 2023 they restricted access to RHEL's source code entirely, aiming directly at Rocky Linux and its rival AlmaLinux. Without the source, neither project could stay compatible.
The community's response was bigger than one distro this time.
Oracle, SUSE and Rocky's parent company CIQ formed an entirely new alliance called OpenELA specifically to keep enterprise Linux source code public. Their actual tagline: "No subscriptions. No passwords. No barriers. Freeloaders welcome."
Red Hat tried to kill CentOS once. The community rebuilt it.
Red Hat tried to cut off the replacement. The community built an alliance to protect it.
Some companies think open source means you can take it back whenever you want.
The community keeps proving them wrong.
Someone turned Kubernetes trauma into a video game.
It is called K8sQuest. 50 levels. Each one breaks something real in a local cluster. CrashLoopBackOff. ImagePullBackOff. Pending pods. Broken services. RBAC failures.
Your job is to fix it using real kubectl commands on a real local cluster. No cloud. No AWS bill. No risk of actually taking down production while you learn.
- 5 worlds, beginner to advanced, 10,200 total XP
- Real-time monitoring so you watch your fix take effect live
- Progressive hints that unlock only when you are actually stuck
- Post-mission debriefs explaining why the fix worked, with real production incident examples
- Built-in safety guards so you cannot nuke your own cluster by mistake
- Level 50 throws 9 simultaneous failures at you at once
This is not a tutorial. This is a flight simulator for the exact 2am panic every Kubernetes engineer has lived through.
1.2k stars. 126 forks. Apache-2.0. Free.
Repo here: https://t.co/j2mzCduLlN
Six books that will teach you system design properly, not just for the interview.
Start here if you want to truly understand how real systems work (Save this for later): â
Day 11 - Kubernetes Networking (K8s Networking)
Kubernetes introduces a dynamic, flat-network paradigm that every DevOps engineer must master.
> The Flat Network:
Every single pod in a cluster gets its own unique, routable internal IP address. Pods can talk to all other pods across nodes without NAT.
> Service Types:
Core primitives to expose your workloads:
- ClusterIP: Internal access restricted within the cluster.
- NodePort: Exposes the service on a static port across each Nodeâs IP.
- LoadBalancer: Automatically provisions a cloud providerâs external load balancer.
- Ingress: Manages external HTTP/S routing to services via host or path matching.
> CNIs & Service Meshes:
Research Container Network Interface (CNI) plugins like Calico or Cilium (powered by eBPF), and see how a Service Mesh (like Istio) can inject sidecars to provide advanced features like mutual TLS (mTLS) and retries without changing a single line of application code.
ÂĄALGUIEN ACABĂ CON EL DOLOR DE BUSCAR TORRENTS EN 2026!
OlvĂdate de las pĂĄginas llenas de anuncios, botones falsos que abren 17 pestañas y resultados muertos con 0 seeders. Alguien se hartĂł y creĂł la herramienta definitiva.
Se llama torlink y es un cliente torrent para terminal que hace exactamente lo que todos queremos:
âą Escribes tu bĂșsqueda y ataca al mismo tiempo a un montĂłn de trackers confiables
⹠Los resultados llegan en tiempo real, ordenados por fuente, tamaño y seeders
âą Flecha arriba/abajo â Enter o aprieta âdâ â descarga directa al disco
âą Si un sitio estĂĄ caĂdo, lo salta automĂĄticamente y sigue con los demĂĄs
âą Las descargas van en segundo plano y retoman solas si cierras la terminal
Todo en un solo comando:
npx torlink
Solo necesitas Node.js. Sin instalar nada, sin navegador, sin cuentas raras, sin basura en tu mĂĄquina. CĂłdigo abierto y licencia MIT.
Es simple, råpido, limpio y hace una sola cosa⊠pero la hace jodidamente bien.
Si estĂĄs cansado de sufrir buscando torrents, esto es lo que estabas esperando. ÂżYa lo probaste? Comparte si te salvĂł la vida (o al menos la paciencia).
Microsoft finally lets you install WSL Containers.
It just went live in public preview today.
Developers are already celebrating in the comments. One wrote: "The days of Docker Desktop are numbered, I hope."
Here is what actually shipped:
â A new CLI called wslc.exe ships directly with WSL. Same commands you already know. Just type wslc instead of docker.
â A full developer API lets Windows apps run Linux containers as part of their own code in C, C++ and C#.
â File access on the new virtiofs filesystem is 2x faster than before.
â Works with VS Code Dev Containers, Microsoft Defender and Intune out of the box.
â Install today with one command: wsl --update --pre-release
Docker Desktop costs $9 to $24 per user per month for commercial use. WSL Containers is built into Windows and free.
General availability lands this fall.
Full announcement here: https://t.co/ns7AWUjMBf