sisyphus is the term coming to my mind when reading about this - your - journey!
It's very clear that you voluntarily mastered that task... which though does not mean that it will ever be easier... something will be broken all the time, no matter what the chosen approach. I usually tend for the integrated approach out of one hand than a bag full of fleas (Germanism)... they tend to be jumping around all the times: the perfect implementation of the anti-pattern of stability. Over time though - when things mature and get more standardized / normed - life gets easier... road has less bumps... sailing becomes smooth(er): just thinking of the browser builder specifics in html / css / JS / etc... 20 years ago versus today...
Said so, it cold become possible with docker to compose such a setup more easily, easier to test and maintain. The 'bridges' between SW and HW will though stay contentious subjects.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
sisyphus is the term coming to my mind when reading about this - your - journey!
It's very clear that you voluntarily mastered that task... which though does not mean that it will ever be easier... something will be broken all the time, no matter what the chosen approach. I usually tend for the integrated approach out of one hand than a bag full of fleas (Germanism)... they tend to be jumping around all the times: the perfect implementation of the anti-pattern of stability. Over time though - when things mature and get more standardized / normed - life gets easier... road has less bumps... sailing becomes smooth(er): just thinking of the browser builder specifics in html / css / JS / etc... 20 years ago versus today...
Said so, it cold become possible with docker to compose such a setup more easily, easier to test and maintain. The 'bridges' between SW and HW will though stay contentious subjects.