The problem with old computers isn’t that they’re slow but fail randomly so they don’t need “smaller” Linux, they need more resiliency that can work with random RAM erros, corrupt disks, absurd CPU instruction failures.
The size was a 90s problem.
Readit Newsmonus commented on Runc breaks pods when CPU requests aren't multiples of 10 github.com/opencontainers... · Posted by u/dropbox_miner
Whether this is a real bug or not, the fact that the entire report is LLM generated AI slop makes my eyes glaze over.
I'm sure it's also a waste of maintainers time to drop a wall of AI bullet points instead of just sharing the critical information.
Agreed. Use LLM all you want to do the discovery and proof but do not use it to replace your voice. I literally can’t read, my brain just shuts off when I see LLM text.
monus commented on I use zip bombs to protect my server idiallo.com/blog/zipbomb-... · Posted by u/foxfired
The hard part is the content of isMalicious() function. The bots can crash but they’d be quick to restart anyway.
monus commented on There isn't much point to HTTP/2 past the load balancer byroot.github.io/ruby/per... · Posted by u/ciconia
> bringing HTTP/2 all the way to the Ruby app server is significantly complexifying your infrastructure for little benefit.
I think the author wrote it with encryption-is-a-must in the mind and after he corrected those parts, the article just ended up with these weird statements. What complexity is introduced apart from changing the serving library in your main file?
monus commented on The "email is authentication" pattern rubenerd.com/the-email-is... · Posted by u/Brajeshwar
Well, yeah, “magic link” is a thing and one of the easiest form of authentication supported by many providers, like Supabase, Vercel and libraries like Next Auth.
Another great side effect is that your backend doesn’t have to store user passwords which means removal of a lot of compliance headaches.
> Every now and then I would update a plugin in Neovim and everything would break, and I would have to spend time fixing it instead of getting work done.
This is true, but only if you're not using one of the ready made distributions. I didn't switch to NeoVim until I discovered LazyVim and this amazing guide https://lazyvim-ambitious-devs.phillips.codes/.
That changed everything. I just use LazyVim out of the box, as if it was a Jetbrains IDE. No config hassle, no issues with updates. It just works.
Regarding Zed:
It's a small niche they're trying to fill in a very competitive market. Currently they have the advantages of being the current cool thing. But that's not enough in the long run. If I would knew some killer feature, I'd go ahead and write it here. But that's the thing, I can't think of any. For simple, mainstream usage, VS Code is there. Ulimate IDE features: JetBrains IDEs. Ultimate productivity: LazyVim (or other NeoVim setups), ootb modal editing: Helix.
> If I would knew some killer feature, I'd go ahead and write it here. But that's the thing, I can't think of any.
Speed to open and general snappiness. Nothing comes close to Zed especially in larger codebases as most agree in the thread.
monus commented on CRIU, a project to implement checkpoint/restore functionality for Linux criu.org/Main_Page... · Posted by u/JeremyNT
My process connects to, say, Postgres. What's going to happen to that connection upon restore?
Does crik guarantee the order of events (saving a checkpoint should be followed by killing the old process/pod, which should be followed by a restoration - the order of these 3 events is strict) and given that criu can checkpoint and restore sockets state correctly - how does that work for kubernetes? The new pod will have a different IP.
TCP connections are identified with source IP:port and target IP:port tuples. When a new pod is created, it gets a new IP so there is not much way to restore the TCP connections. So crik drops all TCP connections and lets the application handle the reconnection logic. There are some CNIs that can give a static IP to pod, but that’s rather unorthodox in k8s.
monus commented on CRIU, a project to implement checkpoint/restore functionality for Linux criu.org/Main_Page... · Posted by u/JeremyNT
I built crik[1] to orchestrate CRIU operations inside a container running in Kubernetes so that you can migrate containers when spot node gets a shutdown signal. Presented it at KubeCon Paris 2024 [2] with a deep dive for those interested in the technical details.
[1]: https://github.com/qawolf/crik
[2]: The Party Must Go On - Resume Pods After Spot Instance Shutdown, https://kccnceu2024.sched.com/event/1YeP3
We run them on bare metal without VM brittleness, fully GPU-accelerated with WebRTC streaming using hardware encoder. As good as it gets and it’s amazed every single person who tried it.
Still behind waitlist, give me a heads up at hello@limrun.com to try it out.
https://lim.run