Equation Framework Philosophy

Equation Is:

  • ... an execution engine that uses an object-oriented scheduler to run managed application code.
  • ... procedural, object-oriented, and functional - with no bias to any monolithic coding paradigm.
  • ... developer-centric.

Equation Becomes:

  • ... a CMS when it loads a web request.
  • ... a dynamic script or service when run from the command line.
  • ... a desktop kiosk interface, X11 shell replacement, or native GUI application.

Equation Framework Overview:

  1. When the Equation Framework core is initialized, it reads the configuration settings to determine how to proceed.
  2. The "core" runs through a list of "execution phases" and loads components in the order they are configured.
  3. That's it.


Yes, that is the only fundamental thing to understand about the Equation Framework: It's primary function is to schedule and run module code.

...so how does it deliver a web site?

"Equation CMS" is a set of modules that are called by the Equation Framework "core" scheduler. These module functions process your web request and deliver the page to your browser.

...what else could it possibly do?

File synchronization, backup, image processing, "kiosk" desktop shell, native desktop applications... pretty much anything.

...that's impossible. PHP doesn't do that.

There is more to PHP 8.1 than just Laravel and WordPress. This is a general-purpose application framework, so it does a lot more than serve pages.

Platform Objectives:

Be fast. Be simple. Be easy to configure. Be flexible. Be easily debuggable. Use the least memory possible. Do not impose complex class structures on the developer. Make the scheduling of code easy to control. Provide, but do not impose an MVC architecture. Use a clean and simple folder structure. Be as "cluster-ready" as possible. Only load code that is actually needed. Do not require extensive documentation to understand. Minimize requirements for 3rd-party integrations.

Equation CMS: