Ingwie Phoenix (aka. birb) 10 months ago

Today I got an email on an ipfs/kubo issue ticket I subscribed. It was opened in 2016 and is about limiting bandwidth usage to not immediately eliminate your internet connection. It made my OpenWrt router, back then, keel the fuck over...twice. xD Guess what; another guy, in 2025, is asking for the exact same feature _STILL_. What are these people over there coding or working on?! How is this still not a feature? :0 Genuenly baffled.

Ingwie Phoenix (aka. birb) 10 months ago

Today I learned that logging sucks. Not producing them - oh no, that's just an fmt.Println() away. Oh no... I mean reading them. `tail -F $logdir/*.log` is _THE FUCKING ONLY_ not-actually-sucking method to read multiple log files at once. lnav kinda works but the library it uses - notcurses - is not happy with VSCode, and multitail hates the flat and thin terminal layout. So, classic `tail -F` is all I have. And oh my god - I hate it, so much. JSON logs in this are aaaaaawwwwwwwffffffffuuuuuuuuulllllllll... Like, how are we living in a world where we have highly complex systems like Kubernetes and stuff, where we work to make cars fly and code write itself... How does reading a log still suck so much?! o_o Yes, I might be overreacting - but, seriously. Like, for real. This drove me /MAD/ today. xD Context: I use dinit as my init system in my devcontainer. In order to actually read and retain logs, I am now writing them to files instead of the console - because the latter gets lost when I close out of VSCode (because in their infinite wisdom, you actually can not monitor the plain container output...cuz, why wouldya wanna do that...ermahgerd...). So, writing to file it is. In the DevContainer config, there is `postAttachCommand` which pops up immediately after you launch into the container - and this is the perfect opportunity to pop a panel with logs. But all I have is `tail -F`. How.