> It will be interesting to see how they make this arrangement approachable for Arduino’s audience which generally expects ease of use to be a high priority.
Would not be surprised to see both approaches to developing only for one of the two systems: programming the MCU and deploying some ready-made stuff to the big Qualcomm chip, like a stacking a shield on top of the Uno only that the shield is software-defined (providing some compute service), and running some ready-made interface abstraction on the MCU, running everything individually programmed on the powerful Linux chip. Likely within some form of JVM or a Python runtime, or node.
Would not be surprised to see both approaches to developing only for one of the two systems: programming the MCU and deploying some ready-made stuff to the big Qualcomm chip, like a stacking a shield on top of the Uno only that the shield is software-defined (providing some compute service), and running some ready-made interface abstraction on the MCU, running everything individually programmed on the powerful Linux chip. Likely within some form of JVM or a Python runtime, or node.