And how do you plan to go for the blockchain developpement ?
You want to start from an existing code base, or code a whole new blockchain node/wallet/block explorer from scratch ? That is monthes of steady daily work, at best
Especially if you want to have high level scripting engine, on top of Blockchain protocol, how many time to get all this from scratch ?
Because I have already large part of this already done, not sure after how you see the priority between the blockchain itself, the script language, and the application layer , and if you plan to start from scratch how many time before an application can be programmed with it ?
If you are ok with the model of script I explained before (
https://bitcointalksearch.org/topic/m.18375980 ), I can start working on it and have something working soon, but it would probably not be directly suitable for javascript transpiling as such.
What you have in mind is starting on node.js code directly, or develop the transpiler first, and then develop the blockchain and application with the language directly and transpile it to node.js ?
Or starting from a code base in c++ or other ?
Normally my framework in C can do the node.js job for many things and I still have the prétention to say it's much better on all aspect, less memory use, more stability, direct access to kernel api for i/o & threads, compiled to binary code, can put in line sse or avx in the code direct, integrate ffmpeg with ogg, deal with binary data easily, and have efficient crypto, and it has the reference counter and dynamic typing, so I dont see how you can have better in shorter time
If you see big problem with it or how it can be improved nothing is really fixed
My criteria is i want cpu power and parallelisation, opencl/opengl, modularity and dynamic typing.
With node.js I dont have cpu power and efficient parallelisation, and not sure about opencl/opengl support. Dynamic typing and modularity ok, but not at the price of giving up on all the rest
For quick prototyping ok, but then need something else at some point too than node.js modules.
The things I like with node.js is the module system to manage large software stack in js, but the node.js runtime in itself not too much, it doesnt look all that stable etc. To export node.js app to browser bundles with html5 app ok, but not to run full nodes with the node.js runtime.
My main objective with blockchain is to develop distributed applications, because I think it open new paradigm with public sharing of information etc, the fact that there are well valued coins only add to the attractivity of the ecosystem, cause real value can be traded "in app" which is completely cool
After im not here to invent the perfect blockchain or ideal currency, im only in to program distributed application, for the economic aspect I trust the high valued coins, and i make a module to use them in the applications
I believe more in user controlled private network based on modular application layer to optimize security for the application / user group purpose, rather than having to rely on complex whole chain conscensus for everything, hoping that everything will always sort itself out the best for everyone by itself
The way i would see it is application producer have key pair to authentify affiliated nodes who run their modules, to have a degree of verticalisation in private network, and nodes not involved with this application just skip the block data, and just keep the proof of existence hash in the block headers, if they just keep track of coin transactions. And the node running the modules can validate the blocks based on higher level protocol rule implemented in the modules. People who are affiliated and run the application modules can get some form of reward from application supplier if their module is run, or if transactions happen through it ( nodes never have to know private key , all signature happen in the browser with in browser crypto). Need to be careful it doesnt turn into some pyramidal scheme too much, but with only one level of affiliation normally it's ok. But I bet there are always some people who can turn it into a pyramidal scheme
Only the nodes involved with the application affiliation can validate the application blocks, and the higher level of the protocol is handled in the affiliated group. It could have its own pow difficulty targeting , or pos based on app tokens.
I also plan to develop tradional web market, to integrate app in cms or prestashop, symphony etc for integration of web app in traditional web platform.
Either it's blog content, audio, app data for social media ( caregories / threads / post / users ), or shop with article item, it can be handled in application layer modules.
It's more the way i view it globally