it makes cleanup logic convoluted when you can’t easily pthread_cleanup_push, forcing you to either block on the join or signal cancellation and detach
i agree with your sentiment, and them botching the license was clearly a problem, but at the same time i think a dev waives their right to be indignant about someone forking and commercializing their code when they provide a perpetual, irrevocable, commercial license to do so. if continue was GPL’d or something i would respect the uproar more
you assume professionalism and technical ability are positively correlated. my anecdotal observations would lean the other way but i have no data to substantiate this on
i do disagree with the methodology of the paper though - adherence to standards is a metric of conformance to a status quo, which as someone else’s comment points out feels like the midwit meme
this is incredibly negative but lacks examples, could you back your statements up with evidence or ease off the hyperbole? the middle ground is the worst
start relatable: “my experience”
add reinforcing detail: works well with fx2 hw
add negative experience: bad for analog logic
introduce habit trigger: next time use ngscopeclient for analog logic
I'm a bit confused, is the implication that they're shilling for ngscopeclient or something? It's not a paid product (neither is sigrok). They're not wrong either, Pulseview (sigrok) is great doesn't feel very designed for interactive use from the little bit I played with it.
I didn't use an LLM, but on rereading in the morning, I am cringing at "wasn't so interactive", so maybe I should have. There had to be a better way to put my complaint.
it makes cleanup logic convoluted when you can’t easily pthread_cleanup_push, forcing you to either block on the join or signal cancellation and detach
reply