clnhlzmn

fwiw I just received the adept trackball and I too was worried about the quality of the enclosure but upon seeing it in person I'm fine with it. As far as fdm prints go it's really well done.

The way we do it in modern languages with things like std::optional and even that is not the best example.

Because to control the autofocus motor and other features it makes sense to have a microcontroller in the lens. If you have a microcontroller in the lens you have software in the lens and if you have software in the lens you're going to need to update it.

You could argue that the camera should do firmware updates but the manufacturers for (semi) open mounts like the ones Tamron is making lenses for don't want to have to design a protocol to do updates for third party lenses through the body when the lens manufacturer can just slap a USB port on the lens and call it a day.

The port is also useful for customizing the lens functions. For third party lenses the camera can't be expected to manage those functions.

I use this knot usually but it doesn't work for my pisgah range laces. They have their own recommended knot, which does work, but it's annoying to tie and asymmetric. I'll be trying this "secure" knot now.

The really crazy thing is they returned to the origin instead of the nearest airport. If it was really an emergency they would have got out of the air at the nearest runway of suitable length instead of flying all the way back. Just theater.

You learned something different then because this finding is that some kinds of additional roughness delay the transition to turbulent flow which is pretty clear in the article.

doesn't ieee754 define a decimal format? Specifically "decimal64"

It's probably a faux pas to be left handed

I think you're mistaken on that. Maybe me and the engineers I know are below average on this but even our combined knowledge of the kinds of things _real_ compilers get up to probably only scratches the surface. Don't get me wrong, I know what compilers do _in principle_. Hell I've even built a toy compiler or two. But the compilers I use for work? I just trust that the know what they're doing.

I need that "RUB OUT" key on my keyboard

So instead of carrying a slightly larger but perfectly useful computer (a laptop) I have to carry a smaller but useless keyboard and mouse for the benefit of not having a keyboard and mouse sitting on a desk when the desk isn't being used? I still don't get it.

I could see the benefit if this thing dropped the keyboard entirely to make it as small as possible but still I'd rather just carry a small laptop.

If this is better than a laptop for mobile work why include the keyboard? Why not just make it a tiny box with a single USB C connector to plug into the dock on your home and work desks? Since you already must have monitors and mice at those locations (or bring them with you) I'm failing to see the point of including the keyboard in this package (except of course to be able to advertise the "copilot key")

Seems like you could make the corners round (not making a judgement on that in any way) and still give the resize handle a more sensible size/shape/location right? As in this isn't a visual design problem.