I still want dynamic linking, but only a few trusted library files would be allowed to make system calls. Like libc. Sorry but golang would have to change to use libc.
This breaks the ABI, but it breaks it for naughty programs the most.
An open source Ipod Nano is a great idea. It could be useful for many years, much longer than a phone. I’m interested in the idea of making one that is modular too - made from little interconnected open source PCBs that you can get from say Lilygo, Seeed, DFRobot, Adafruit, Sparkfun.
I think open source and modular hardware could be a way to make electronics repairable and user-upgradeable, and also prevent future e-waste. Modularity = repair & reuse. [1] And this means you don’t have to be good at PCB design to get started.
For example I think you can make an MVP Ipod entirely out of existing adafruit modules. And sell the MVP for 2-3x BOM / distribute the design as a production model, not just a prototype.
If you get any traction, you can make a better product by designing better modules, and make them high quality, open source, and documented, so that manufacturers will pick them up and start supplying them to the community. If the modules aren't picked up by a manufacturer (with no money exchanging hands) that means the module isn't general purpose enough and would lead to future e-waste.
Have a look at zolaelectric.com. They sell small modular solar pv + battery power units. These units are meant to be purchased by businesses (micro-generators) who then sell the power generated to their subscribers.
This breaks the ABI, but it breaks it for naughty programs the most.