Let me dispel one myth: The bitter lesson can be true, and you can still want a bespoke, customized solution.

If it is true that eventually a general approach that scales with compute/data will supersede a bespoke expert solution, it is not necessarily true that today's expert solution should be thrown away at the first sign of a data-driven model.

It says nothing about what you should use today to build things, it says everything about how you should do research that lasts.

If you're building for billions of users in 10 years, sure go with whatever you think is the bitterest.

But if you're building for right now, you probably mashup whatever works best. That might still be a PID loop, EKF, and Homographies sometimes. But when you hit the frontier of what "works", then you have to reach for new things anyway.

Chesterton's baby/bathwater

WRT humanoids - I am making no statements.

As an analogy, it is currently possible to cross the country in 6 hours.

That fact does not imply that a person in Boston in the year 1850 should wait until commercial flight was available to travel to California.

So the fact that we will eventually have simpler/more efficient algorithms doesn’t tell us anything about what to do today.

>It says nothing about what you should use today to build things, it says everything about how you should do research that lasts.

Right! So who are you arguing with lol?