I know that automotive parts of the standard requirement to withstand 80°C (or 120°C for military use). A robot vacuum working in a living room can probably be made cheaper because it does not have to face as harsh environments?
Also, range is probably a factor. In a living room, you probably need something like 20m max. You car should "see" farther.
Sure, these are the assumptions but silicon is silicon, copper is copper and solder is solder. They don't use easy melting electronics in vacuums and hardened stuff in cars, the tech is about the same unless it is supposed to work in highly radioactive environment. The plastics are different but car interiors are full of plastics, so its unlikely that the costs of temperature resistant plastics needed for this is more than a cupholder.
As for the range, again pretty powerful lasers are sold for sub 10SUD prices on retail. I am sure that there must be higher calibration and precision requirements as the distance increase but is it really order of magnitudes higher? 120 meters laser measurer with 1cm accuracy is 15 Euros on Temu and that thing has an LCD screen and a battery as a handheld device. How much distance do you actually need?
Vibrations are surely an issue with electromechanical systems but hardly with electronics. There are plenty of cheap electronic accessories for cars and you can observe that those keep functioning for years.
I do love jetbrains for its nice-to-have features (eg highlight a few lines in the middle of a spaghetti function -> right click -> extract to new function) and was paying for it out of my own pocket for several years; but had to switch to vscode for a couple of required features that jetbrains was missing (remote dev over ssh, and devcontainers); and now switched to zed for being "like vscode but faster"
Zed can "extract function" for Rust code. I guess, it depends on the language server you use? Since vscode and zed use the same there is not distinction between them.
100%. I came here to find something new from a field that I don't know but imagine has some good lessons for software. Instead I found someone commenting on small iterations vs big design which is quite ho-hum by comparison.
> There are two main schools of thought in software development about how to build really big, complicated stuff.
That feels like a straw man to me. This is not a binary question. For each small design decision you have a choice about how much uncertainty you accept.
There are no "two schools". There is at least a spectrum between two extremes and no real project was ever at either of the very ends of it. Actually, I don't think spectrum is a proper word even because this is not just a single dimension. For example, speed and risk often correlate but they are also somewhat independent and sometimes they anti-correlate.
Sudo’s networking functionality is infuriating too, because if my system’s DNS is broken, I get to wait 60 seconds for sudo to work, during which time I can’t even ctrl+c to cancel!
(It has to do with sudoers entries having a host field, since the file is designed to be deployed to multiple servers, which may each want differing sudoers rules. It’s truly 90s era software.)
I was thinking the same, and read it as “Xi”kipedia. Then sure enough, one of the articles that it immediately showed when it loaded was for “General Secretary of the Chinese Communist Party”, or Xi Jinping.
Also, range is probably a factor. In a living room, you probably need something like 20m max. You car should "see" farther.
reply