Re: Do you think "iamnotback" really has the" Bitcoin killer"?
I saw the discussion went on rust too, and there was a very good discussion on this topic on devos too, with a guy who was firm supporter of rust to develop os, but another person explained that in fact the whole concept of rust unsafe code make it actually virtually useless, specially if you want to see the broad picture at system level, it's impossible to have an operating system made only out of safe code, and from the moment you have 'unsafe code' it mean the whole rest of the program is vulnerable to issues in those unsafe zone, which make the real usefulness of rust rather low all together. Maybe for some purpose it can still make memory handling more easier in certain case, but if the application has to make use of any unsafe code, and ultimately there will always be unsafe code executed somewhere in the whole software stack to the cpu, so it's more fake impression of security, or maybe a better way to organize data and code to avoid certain mistake, but certainly not silver bullet.
You are pointing out the brittleness of relying on total orders, because total orders don't exist over the entire universe. The challenges of blockchain consensus is tied into this fact.
Beyond this, there is the whole Turing Halting pb, and the whole theory saying Turing like computer program are fundamentally unpredictible , even with 100% tape based standalone computer, add interrupt, thread to this, and you are not far from chaos
All framework or high level language do is adding more restriction in the synthaxe to have more determined state and less freedom, to increase predictibility.
But I believe much more in good runtime rather than more complex language and compiler , all expérience like intel atom who wanted to rely on compile time order didn't show very good result.
There are experience with Lisp to define complete grammatical language interpretation that are interesting, but anything in between for me nah
My goal is more to get to something like this with protocol message parsing based on data definition tree template, to have good runtime type checking, and compiler/system independant code who can be executed in distributed environment with a layer above the compiler to deal with data location/availability/sharing with the layer of the data tree, directly from C language compiled to binary machine code.
https://github.com/iadix/purenode/blob/master/protocol_adx/protocol.c#L1363
With this there is all the comfort of high level language with soft typed reference tree, and still easy to compile to cross compiler/system binaries.
But I will probably develop higher level language script at some point to encapsulate modules and api and interface better, I looked into CHARM ( https://en.m.wikipedia.org/wiki/Charm_(programming_language) )some time ago, it seemed to fit my purpose.