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
Good point, the sensor count exponentiates and the optics get a lot more complicated if you want a fully integrated system. Nothing on the market I know of but with where we are on the scaling curves now might be the time to try something like it - you could put together a basic proof of concept with a load of commercial sensor elements and wide angle lenses on a sphere. Eventually you can consolidate the central sensors and lenses into concentric hemispheres. You can reduce the data volume by narrowing the camera angles eventually too
Not sure there’s a market but maybe with VR stereo 360 becomes more valuable, who knows. Technologically doable though
Responses so far say to optimize neck latency or use a joystick but why not use a 360 camera and handle it in reprojection. First pass could literally be a gopro or insta360 streaming to the headset and you could eventually integrate cameras and do the stitching yourself. The tech already exists and works, and it removes moving parts and actuators
But are they designed to carry those loads with a drone flock. They’ll also increase the received wind load. Unlikely to cause an issue but you still have to do the math to determine the decrease to the margin of safety
I agree, perfection isn’t a realistic expectation. I also think effort spent building better defenses leads to fewer exploits over time than adding more of the same defenses. The marginal cost of bypassing a given defense is far lower than the initial cost to bypass a new defense
I saw that deno did this but cool to see node picked it up too. I wish there was an option to run turbofan at build to generate the instructions rather than shipping the entire engine, but i guess that would require static deps and no eval, which can’t really be statically checked with certainty
Interesting thoughts on using axis lines only when the relative comparison is meaningful, though I don’t think the downsides to superfluously adding them outweigh the other design benefits like providing clear bounds and a visual anchor to attach tick marks to. The article seems a bit objectivist but I think the right tradeoffs depend on the context as well as the data
https://en.wikipedia.org/wiki/6-7_(meme)