I personally prefer the fzf UX, but I liked atuin's better tracking of history and sync abilities so I combined them: https://github.com/prashantv/atuin-fzf
The stack trace and return path are pretty similar if the flow goes through function calls on a single goroutine, but if errors propagate across goroutines or across different stacks (E.g., via channels), then it can miss some useful details.
Since the HTTP library uses a separate goroutine to create connections, the stack trace at creation time doesn't have details about the user request that triggered the connection.
I evaluated Jsonnet and Starlark for configuration generation at a previous job, and found Starlark more practical -- the similarity to Python made it much simpler for everyone to pick up and use.
I'm glad Meter published this post as I've been fighting this issue for the last couple of weeks and wasn't able to find much information on the root cause.
I started getting packet loss recently, and after being unable to find the cause,
I tried upgrading my router. That somehow made things worse -- rather than intermittent packet loss, it would get into a completely unavailable state and not recover. I couldn't even switch to other networks without restarting wifi.
This affected multiple M1 machines and an iPhone, so I was quite sure it was an Apple issue, but wasn't able to find the root-cause. After some limited testing, I'm pretty sure this issue caused both my intermittent packet loss as well as complete downtime.
bufdev brought up some good concerns on that issue:
> This as a community project defeats the purpose of creating a definitive grammar/spec that protocolbuffers/protobuf holds itself to - without that component, having a community-written spec is no improvement over the current situation from what I can see, and in fact could create even more fragmentation and confusion, just my two cents.
It looks like the protobuf team created a repo intended for this (https://github.com/protocolbuffers/protobuf-grammar), perhaps the spec could be contributed there, including a review/blessing from the official team.
I switched from a Macbook Pro to the X1 Extreme as well, and have been very disappointed.
* The touchpad doesn't feel as smooth as the Macbook Pro (despite it also being glass) -- there's some sort of matte finish which gives it a more rubbery finish.
* The gestures are less accurate (I frequently activate 3-finger gestures despite only using 2 fingers).
* The buttons at the top are harder to use than buttons on the bottom.
* You can only click the touchpad on the bottom half.
This was my favourite course at UNSW, very intense but that's also what made it fun! Many nights spent debugging race conditions and bugs till 4am.. The OS courses at UNSW are all pretty great.
We're trying to solve this problem with more of a focus on priorities - mainly to try and prioritise what one person should be working on at a time:
https://mijura.com/
