Although the leanest and cleanest uses of WebFrame will consist of a static frontend communicating with the C++ backend, there are embedded runtimes for languages such as php, which offer the ability to interpret dynamic content on the fly. This would probably require some enhancements to be made to the existing framework, specifically archive management, but opens the door to people who prefer using dynamic languages for web development.
Additionally, this would be a feature that Electron could not support beyond server side js.
Although the leanest and cleanest uses of WebFrame will consist of a static frontend communicating with the C++ backend, there are embedded runtimes for languages such as php, which offer the ability to interpret dynamic content on the fly. This would probably require some enhancements to be made to the existing framework, specifically archive management, but opens the door to people who prefer using dynamic languages for web development.
Additionally, this would be a feature that Electron could not support beyond server side js.