Shrinking the kernel with a hammer

Yet again excellent article in the series!

My comments:
> The ability to develop and update the kernel and user space independently of each other;

If you mean it for development phase, then I totally agree. It's invaluable.
But production systems, in my opinion, are better updated with a single firmware image
containing the whole system (kernel+userspace).
This allows for easier tracking of what is the actual update status of a particular system,
especially if you're managing significant number of them.

When it comes to memory usage, I think RAM is the biggest challenge as of today.
This opinion is based on the desire to have the PCB layout as simple as possible.
With the recent addition of possibility to execute from QSPI memories, the Flash memory
can be extended quite easily with no much wiring.
But RAM is on the opposite. It's clunky, i.e. it requires quite some PCB traces and microcontroller's GPIOs to get started with.

--
Best regards,
Andrzej Telszewski