Yeah, this was the first thing that came to mind, how does this compare to the Truffle WASM implementation. The Graal Polyglot API is pretty incredible, we've been using it for a JavaScript/Python plugin system in a JVM app, and it's been amazing.
Same for me, I used it as a welcome opportunity to get rid of the Reddit habit, which was surprisingly easy. I haven't gotten much useful content out of it for quite some time.
I've been using a Logitech trackball for two years now and they're incredibly easy to clean and don't accumulate much dirt on the surface (since they're very smooth), just a little bit on the ceramic balls that they rest on in the case. You just pop out the ball every few weeks, remove the dirt with a cloth and that's it, doesn't take more than a minute.
Isn't this like the #1 problem people have with wireguard? I've had clients with the MTU issue every time I've set it up for more than a few clients. Also how on earth is "connection reset by peer" dreaded?
Had the same experience using it for a refactor of a 3k LOC monolith via the Pi harness and OpenRouter. After burning through $8 worth of tokens it left the code in a broken state, the "thoughts" were full of loops where it would edit the monolith, then refer back to the original file, not finding it and then overwriting its changes with "git checkout --"
We're doing this with a few dozen GiBs of logs a day (rsylog -> central rsylog -> elasticsearch). It works reliably, but the config is an absolute nightmare, documentation is a mixed bag and troubleshooting often involves deep dives into the C code. We're planning to migrate to Alloy+Loki.
Absolutely, it's probably the most consumer-friendly and reliable part of all of the Bahn services. Personnel is usually pretty great too, and that despite them having to suffer the most from all the inept decisions made in the upper ranks.
On the other end of the spectrum, "experimental artist" (whatever that is) Lawrence English wrote "A Young Person's Guide to Hustling (in Music and the Arts", which seems more like what you're after.
Yup, it's great, at least for live action content. I've found that for Anime, a small amount of motion interpolation is absolutely needed on my OLED, otherwise the content has horrible judder.
Also not like logging setups outside of k8s can't be a horror show too. Like, have you ever had to troubleshoot a rsyslog based ELK setup? I'll forever have nightmares from debugging RainerScript mixed with the declarative config and having to read the source code to find out why all of our logs were getting dropped in the middle of the night.
Am I in the minority when I actually like those AI features on GitHub? The ability to interrogate any open source codebase is __amazing__, this feature alone has saved me days of work/research. The AI code reviews are nothing to write home about, but occasionally catch stuff that I would've missed, a net benefit for me. I don't really get all the outrage... Sure, having an "Ask AI" Clippy-like thing in your face everywhere gets old quick, but at least on GitHub I find it non-obtrusive and often actually useful.
It really is. I've been using Revanced to patch out the Shorts feature on my phone, works decently well, but I'm technically violating the ToS with that, despite shelling out 15€/month for it. Obnoxious.
I tried implementing a Matrix bot a few months back, and it was an absolutely miserable experience, since Device Verification/E2EE was not working with any of the available open source Python implementations I found.
I then stumbled upon their internal Rust SDK[1] that they use for Element X, which is actually quite nice, and even has FFI bindings for Python and Kotlin[2]. Unfortunately the documentation was really lacking at the time. I managed to put something together with the help of an LLM and the source code and examples to find my way around the various APIs, and it actually works with emoji verification and E2EE (although there are weird bugs around synchronization, but that's probably just an API misuse on my end).
It seems they've improved the documentation since and even provide a reference client[3] to see how things work.
100% this. Sometimes it's not even the filer itself. `hard` NFS mounts on clients in combination with network issues have led to downtimes where I work. Soft mounts can be a solution for read only workloads that have other means of fault tolerance in front of them, but it's not a panacea.