These systems are often trained on data obtained from driving the car around. I think the only real solution would be planning routes through more diverse neighborhoods. Although any company that is taking this seriously from a safety perspective has multiple radars and a top mounted LiDAR on their vehicles. Those sensors should be sufficient for detecting humans regardless of race even in a completely dark environment. Relying solely on camera data is just asking for problems for this and many other reasons.
Not really sure about in fabs for manufacturing, but whenever I was in college I had access to an electron microscope. It had its own foundation separate from the rest of the building to minimize vibrations. I’m sure there’s more to it than that, but that’s at least one technique.
I’m not entirely sure because I don’t really frequent those instances. But if Reddit is any indication, the revisionist communities have a significantly larger presence online than anti-revisionist communists, which is unfortunate to say the least.
Within real communist communities? No. Within revisionist communities absolutely.
Communists haven’t supported China since the death of Mao whenever Deng Xiaopeng and his ilk took power. You can read plenty of official statements by Peruvian, Indian, and Filipino communists parties (that have actually attempted/are attempting revolution) who denounce China as a revisionist social imperialist power in exactly the same way that China denounced the USSR following the revisionists rise to power.
This same dude came into a programming subreddit earlier and got dragged for their shitty uninformed opinions there too. I’d say they’re a troll, but they got big mad and deleted their comments after a while, so I think they’re just an edgy teenager or something.
Maybe you should check how python compares relative to shell scripts before you comment. You’re making it very apparent that you don’t actually know what you’re talking about. Regardless of how slow python is, it is significantly faster than bash, or any other shell language purely by virtue of the fact that shell languages are primarily glue between other programs. Spawning a new process has a ton of overhead, which you would know if you were capable of doing anything other than projecting.
You’re also woefully unaware that it is completely possible to write python bindings for C++ code, which many popular libraries do. In practice python is not as slow as you think it is. That’s not even considering the fact that python 3.12 increased performance of the language.
It’s not perfect for everything, but this performance argument shows that you don’t know enough to understand why that isn’t really a drawback for writing scripts, which is undeniably an area that python excels at.
Tbh you’d still be better off writing them in python. They’ll be more maintainable, and you’ll learn valuable skills.
Also, since you commented that python was the slowest language ever, shell scripts are often significantly slower. This is due to the fact that shell commands are actually calling other programs, which is very very slow.
To be fair, sometimes that runtime difference matters. That’s why it’s C++ and python is a fairly common skill-combo amongst devs. But the fact that this dude is basically bragging about writing shell scripts as if that’s something an experienced dev couldn’t figure out tells me that they don’t really know anything about when you would choose either.
If they had mentioned the Global Interpreter Lock or dynamic typing maybe they would have had some sort of real case for why you should avoid python in certain situations.
You should check out Click. Way more user friendly than argparse imo. I agree with all of your points though, and I’d also add if you are working on a team that it will be infinitely easier for a co-worker to decipher your python code compared to a bash script. And you can write unit tests with py test, the list goes on and on. If the environment you are deploying to has the python interpreter, you should use python over bash.
I work in software and I haven’t touched windows in a very long time. Even back whenever I worked on FPGA development all of that software ram on Linux, so I think you’ll find that this is very field dependent.
You may already know this, but this depends on the focal length of the lens. For example, a 50mm focal length on a 35mm camera will represent objects in the background fairly accurately. Larger focal lengths have background compression, making their background look closer than it actually is. Focal lengths below 50mm will have the opposite effect, making backgrounds appear further away.
Some phones with multiple cameras have a 50mm (or similar) effective focal length lens as one of the options. Basically without knowing the focal length of the lens it’s hard to say how accurately the distance of the background is portrayed.
I wish you could buy a decent house for 500k in NYC…