The Elastic programming language is destinated to all-level programming. It's possible to use the high level, the middle level and even low level. For most of applications programmers need just high-level programming. And at this point the Elastic is Php-alike. And we may distinguish that it's the Elastic, not Php, if the programmer use features that the Elastic has. For example virtual functions, inheritance and other things, belonging to object-oriented programming.
On middle and low level the Elastic is C++-alike. Programmers can write code without using the garbage collector and using the machine stack for function call. Using clear assembly language is possible too. Therefore, the programmer in the Elastic loses nothing in comparison to C++. Currently, we is on the compilation stage of the Elastic code by itself. The Elastic is written in C++. When we compile its own code by itself successfully, we may say that the Elastic is compatible to the basic C++ completely.
The Elastic programming language is the compiler into native code. The executive machine is part of compiled native code. It give us all benefits of the native code usage as speed and size of the executable file.
For the safe execution of applications we are planning to allow the exclusion of low-level function from execution. It's needed for execution on third-party servers.
The arhitecture of the Elastic is designed in a way that futher extension of the language is easy. Therefore, we want implement object marshalling, when a server creates objects and executes methods, but from the application point of view the local computer executes code.
The Elastic has been assumed with different language syntax support from the begin. If it's necessary, we may add the syntax of any language, f.e the Basic or the Python.
But, the main thing - it's the ability to save code into the single database (not into files) as mutually connected syntax objects.