Fantastic software that I've used for over a decade. Interacted with Karl a few years ago about Adobe's AMF format; very generous with his time.
I was surprised to learn that it's over 20 years old! https://en.wikipedia.org/wiki/Charles_Proxy
Worked for an eCom store for 3 years, was on-call 24/7 for most of it due to understaffing. In this context, every second of downtime was actual money being lost. CEO drilled in the gravity of each outage.
Took me a good few months after changing jobs to not get crazy anxiety every time my phone rang.
After working in a much healthier on-call setup later in my career supporting a large SaaS, I actually really like it. High stakes produce quick learnings.
Not for everyone, but everyone should try it (and be compensated FFS).
Perhaps it's less about billing and more about disincentivizing excessive use? Even if the service is free, it's not infinite and is ultimately a shared resource that should not be monopolized.
Nothing interesting to add, just an anecdote.
As someone based in a semi-rural part of South Africa, this dual cable break was a huge PITA for a few days. Latencies went through the roof; remote work was made very difficult.
Very accurate! Just 10 points off my chess.com rating.
Although, there was an unfortunate bug... I couldn't promote a pawn, and that severely impacted the endgame. I'm on mobile Brave, and attempting to promote presumably tried to bring up some modal, but instead it just glitched.
It replaces no other projects. Continuous profiling solves a different problem to Mimir, Cortex, and Tempo. Mimir and Cortex are for metrics, Tempo is for distributed tracing, Phlare is for collecting profiling samples over time.
Profiling is a layer below tracing and metrics in that it requires very minimal and generic instrumentation (of the runtime), while the others require specific instrumentation (of the application).
Profiles like CPU, heap allocs, goroutines, etc are collected on a continual basis, allowing you to see at any time how your application was making use of its runtime resources.