Mmm, but you'll need to test the higher-level instructions built on top of the lower-level instructions too right? Or will we be leaving that for third parties to figure out what higher-lev instructions they want?
Instead of longer dev time for 28 instructions, we have (presumably) shorter dev time for 1 instruction and while that is being done simultaneously test the higher lever instructions and C compiler and C library functions. Not that most C library functions will be used as it will be expensive, but I figure if relatively complicated C library functions works based on a single opcode (which we can test right now!), then it bodes well for Turing scripts to function properly
I am optimizing time to market by splitting the projects into pieces that can be developed in parallel. Maybe not the perfect split, so always open to improvements as measured by quicker expected time to market
James