As a controls engineer who has implemented and assisted with dozens of robotic manufacturing cells, the problem isn't the motion planning or compute, it's legacy product support and ease of onboarding new hires.
Any given cell may be in production for 10 years - some only for 5, but some for 20 or more - and you need The problem is that academia is working in ROS (now ROS 2), writing Python and VHDL, while the real work in the industry is being done in proprietary vendor tooling that's backwards compatible with training from the 80s. They're proudly advertising touchscreens and full-color 5.7" displays on their teach pendants, as if their customers were still 20 years in the past.
Yes, academia, I do want sub-millimeter repeatability, and flawlessly smooth motion planning. I want collision detection that accommodates both the inertia of the arm itself and any end-of-arm tooling, including cable harnesses with distributed loads. I want automatic singularity avoidance and trivial point and frame manipulation. I want 24-bit encoders for resolution, and I want angular velocities to the moon, and to make those work together I need servo loop rates and high-speed skip responses at 1, 2, or 10 kHz. I want 4D stop position prediction to avoid intersection of the robot arm with complex assemblies and safety zones imported from CAD. I want all these things cheaper and faster, with more storage.
But I need these to be accessible by Billy Joe, whose only credentials that got him the job in the maintenance department is that he helped out his daddy working with a welder and an old clapped-out Bridgeport on the farm growing up. Billy is probably my best tech on 3rd shift, and he's never learned to type on a full-size keyboard, just his smartphone... and on a robot teach pendant.