O3marchnative
Joined 2 years ago
Joined 2 years ago
Infantry troops still operate in 3D as they can/will direct mortars, air assets, etc.
In general, what you laid out is a bit of an apples and oranges comparison. An infantry platoon applies fire and maneuver using all of its elements to "close with and destroy" a smaller element.
You emplace your weapons squad which has machine guns and other large weapons (e.g., mortars) that will keep your enemy's heads down. This allows your maneuver elements (i.e., assault squads) to maneuver to the enemy force.
In the case of missile defense, you have a limited set of complex and expensive bullets, and your enemy has cheap bullets. If you want to defend yourself, you're attempting to hit your opposition's bullets with your own bullets.
It's almost always the case that you'll expend more than one interceptor per incoming missile as interception is probabilistic. In general, you can estimate the number of missiles you'll need to achieve a certain probability of interception with the following formula: 1 - (1.0 - sspk)^n, where sspk is the single shot probability of kill (i.e., successful interception with a single interceptor) and n is the number of interceptors.
Shameless plug here, but I wrote up a post about this problem: https://smu160.github.io/posts/missile-defense-is-np-complet...
Thus far, I've written two libraries that utilize Rust, and they are usually associated with "high performance". I was able to exceed the performance of similar libraries written in C/C++.
To be perfectly clear, this doesn't mean Rust can replace C/C++ in every scenario, but the actual perf gap is narrower than some folks may be willing to admit.
[0] https://shnatsel.medium.com/how-to-avoid-bounds-checks-in-ru...
One of the main contributors to v1.0 of fearless_simd started out by helping me evaluate portable SIMD crates for PhastFT. Once we landed on fearless_simd, he ported PhastFT from std::simd to fearless_simd. We did find that more functionality was needed than fearless_simd offered at the time. So, he started contributing significantly to fearless_simd. It’s really rewarding to see how working on a hobby open source project can help improve the Rust ecosystem.
It's always better to take off with less than a full tank of fuel. Once you're airborne, the aircraft can top off its tank to complete its journey. Of course, it may even be more economical to top off at multiple legs as the journey proceeds. To your point, a "reverse" refueling would also be ideal in order to lower the weight of the aircraft.
In certain contexts, it's already being done. It'd likely need to be much safer in order for civilian aircraft to carry out aerial refueling though.
[0] https://en.wikipedia.org/wiki/2015_Office_of_Personnel_Manag...
[0] https://www.economist.com/graphic-detail/2026/05/11/by-one-m... (no paywall: https://archive.ph/X9zzc)
> intact and combat capable
On its own, this claim is likely true. Nevertheless, this does not mean one's opponent is going to carry out one's will. Hence, one cannot declare victory. It follows that anything short of achieving one's goal is a loss. A loss doesn't have to be complete and utter destruction. It's fair to say that Argentina did not achieve its strategic objectives during the Falklands War, no?
> Losing is what happened to Germany after both World Wars.
Yes, but Germany is not as good of an example in this case as Japan during WWII. Japan would have likely accepted something short of unconditional surrender much sooner than August 1945, but the U.S. insisted on unconditional surrender. As such, the U.S. did not win until Japan agreed to unconditional surrender.
GitHub: https://github.com/smu160