I think up to jerk is intuitive, even if the term isn't well-known. Most people have no problem figuring out how to ease-up on brakes in a car, and a hobbyist can usually figure out how to make things smoother when ramping up or down a motor.
I've found even the cheap stuff to be long-lasting if you disassemble it before moving it. Carrying or pushing shelves in a way that turns them into a parallelogram is what damages them.
The problem with that approach is the cheap stuff is particle board, and repeatedly screwing into particle board isn't a fantastic idea.
The best result (in terms of a strong joint) from particle board furniture would be to add glue when screwing (i.e. in the hole with the screw) but that completely removes the option of disassembling it.
I agree, at the low end it's miles ahead of pricier, worse stuff from Wal-Mart or Conforama (in Europe), covered in wallpaper instead of synthetic veneer. At the higher end, it's very good value. In the middle, it's hard to even find competing products.
I don't think hellishly dense cities even exist. There's only hellishly dense neighborhoods and slums. The stereotype some people have is the densest 12 square blocks of Hong Kong extrapolated to the overall size of Hong Kong. Yet if you visit Hong Kong you will find yourself taking a pleasant walk from your hotel, through a park, to a restaurant.
Click any link on the list of densest cities[1] and you will see a lot of low-rises and parks in every one. The ones that are actually hellish are the ones that are car-centric. Dense cities are quite pleasant when you're walking.
It sounds impressive. One could argue for a physical LED tied to the power of the internal camera and microphone. But if I understand correctly, this exclave/dot will be work on external monitors (so the LED is not hidden just because you use one) and probably works with external cameras and microphones (which don't normally have their own LEDs). At least, it probably works with "normal" external cameras and microphones that one uses for zoom, etc.
This is definitely true, especially when rpi is probably more popular than all other SBCs combined. I always feel burned about 2 years after buying anything but beaglebone, rpi or Jetson nano and can't find support. With rpi you can always find an up to date OS image (for the boards that need an OS).
If you use complex devices like cameras, you can probably find recent drivers and readme files for rpi. For other SBCs you will probably end up trying to adapt documentation for rpi and getting stuck because your OS is using a weird version of libc, or something like that.
Beaglebones were popular for a while for GPU farms for crypto, and the shortages were way worse than raspi. I fried one in a PhD project and had to spend a few hundred dollars to get a new one. I used to swear by beaglebones, and they had some nice features, like one usb cable to provide power, expose a serial console, and bridge your internet connection to the board. And one killer feature: 2 independent microcontroller cores that can access the main CPU's memory directly. You could use them to bitbang almost anything. Over time though, most of the newer beaglebones focused on one specific feature and used several different form factors, and most lost the features I loved. BeagleV fire looks interesting but it's missing wifi.
Back in the day (like 12+ years ago) I used some intel SBCs with GPIO, i2c etc. At that time they were nice because they just worked with your favorite linux distribution and put your binaries on it. At the time it was painful to setup an environment for cross-compilation. Today that's easy.
Raspberry Pis are never the best SBC available, and have some very closed aspects but they are usually available, have good community and corporate support and are supported for a long time. I've bought a lot of the other SBCs out there and after a couple of years you find that you're almost the only user left, and the vendor has 30 new products and don't support yours. Then one day you're trying to update your linux kernel for feature y but it breaks feature x, and searching for help yields workarounds and patches, or even OS images for the same issue... for rasberry pi. After a few times, you learn to stick to raspi, or maybe Jetson if you need more.
Me too, especially for engineering, where you often work with people with different locations and backgrounds, and very often work/document in English even in non-English speaking countries. Depending on your native language, you might tend to use one or the other word and it shouldn't matter.
reply