andreynech

This might be helpful to imagine what it is useful for in a real robot localization: https://veterobot.com/demos.html . Video for Unit3 nicely illustrates how fast (just in several steps) particles grouped up around real location. It is done with just four ultrasound range finders.

Part 2 – remote control is added: https://news.ycombinator.com/item?id=22073929

Part 1 - mechanics is here: https://news.ycombinator.com/item?id=22063837

I see your point with single application. However, do not you think that, for example, highly stripped special purpose kernel and distribution built with let's say buildroot will do the job equally well? The advantage is that it will run on bare metal (without supervisor or any other type of micro-kernel to manage microserviceS). If there will be the need for the second application, the bunch of functionality will be shared and hardware resources will be used way more efficient. Also, I am wondering if it would be better to spend resources addressing existing issues with OSs (like not strong enough security, etc.) instead of just giving up and hope that supervisors/micro-kernel will do it better?

Huge efforts and a lot of time was spent to develop multi-user, multi-application infrastructure (aka. standard kernel, FS, networking, etc.). The reason was to offer reusable functionality for applications on top of it to get the most out of hardware. Now they start building exactly in the opposite direction by packaging everything in one artifact where probably the most content will be duplicated (multiplied). Somehow I am failing to see how it should improve/increase/advance/blah/blah...