ZPE 1.14.5 is another major update, and it builds on the incredible work that ZPE 1.14.3 and 1.14.4 have already delivered. ZPE 1.14.5 will deliver on many promises, too.
The first big feature coming to ZPE is a breaking change. It is one that improves the syntax and performance for ZPE now and in the future, and it's something I've been wanting to do for some time.
When I say it's a breaking change, I mean that several predefined functions are now part of modules rather than being predefined functions. Those functions are:
- random_number () -> Math::random_number ()
- calculate_range () -> Math::range ()
- calculate_mean () -> Math::mean ()
- calculate_median () -> Math::median ()
- calculate_mode () -> Math::mode ()
- calculate_minimum () -> Math::minimum ()
- calculate_maximum () -> Math::maximum ()
- calculate_standard_deviation () -> Math::standard_deviation ()
- generate_histogram () -> Math::generate_histogram ()
- calculate_linear_interpolation () -> Math::linear_interpolation ()
- shutdown -> System::shutdown ()
- get_environment_variables () -> System::get_environment_variables ()
- limit_real () -> Math::limit_number ()
- is_headless () -> System::is_headless ()
- is_command_line () -> System::is_command_line ()
- aes_encrypt () -> Cryptography::aes_encrypt ()
- aes_decrypt () -> Cryptography::aes_decrypt ()
- file_encrypt () -> Cryptography::file_encrypt ()
- file_decrypt () -> Cryptography::file_decrypt ()
Two functions (so far) have been transformed into module constants.
- get_os_name () -> System::OS_NAME
- get_max_memory () -> System::MAX_MEMORY
I will update this post as I continue to work on ZPE 1.14.5.
March 2026 has been a hugely important month for ZPE, with changes that go far beyond small fixes or minor additions. The overall direction is clear: ZPE is continuing to evolve from a scripting engine into a much broader and more capable platform, with major improvements to performance, web functionality, tooling, deployment, and the YASS language itself.
One of the biggest themes throughout the month has been performance. A great deal of work has gone into improving execution speed, especially in the runtime, the ZEN Web Parser, and ZPEC. The parser has seen repeated optimisation work, and the runtime itself received considerable performance improvements later in the month. ZPEC, the ZPE Performance Enhanced Cache, also saw major gains. It is now enabled by default, can be listed and purged more easily, and is robust enough that cached files can now be run through ZPEKit as well. Altogether, these changes make repeated execution and web-driven workloads significantly faster and more practical.
In addition to the performance improvements noted earlier, ZPE performance got an additional improvement that made it around 2 times faster than it was even after that improvement at the end of the month. This improvement speeds up both development as well as the runtime.
Another of the most significant developments has been the rapid growth of ZPE’s web capabilities. The ZEN Web Parser was extended to support sessions, cookies, and GET and POST parameters, making it much more suitable for real-world web applications. A particularly important design change was the introduction of the RequestObject, which redefines the role of the ResponseObject. Incoming data now comes from a RequestObject, while outgoing data is represented separately in the ResponseObject. This is a much cleaner and more logical model for web execution.
Session handling has also advanced considerably. Sessions can now store full ZPE values rather than being restricted to strings, which is a major improvement in flexibility. That change also led to updates in how VWS stores objects in sessions, bringing things more into line with the capabilities of the ZPE runtime. Session persistence bugs were fixed, expiry times were added, and responsibility for session handling was shifted away from VWS and into ZPE-PM. This is one of the clearest signs that the web architecture is maturing quickly.
A major new addition this month is ZPE-PM, the ZPE Process Manager. This is one of the standout features of the entire changelog. ZPE-PM allows scripts to be run over a socket, streams output directly, caches .yas files, and now handles sessions as well. It also accepts parameters through JSON requests and has effectively replaced the old JSON communication mode, which has now been removed. This is a major architectural step because it gives ZPE a much stronger service-based execution model and opens the door to cleaner integration with web servers and other tools.
The relationship between ZPE-PM and the VelocityWebServerModule also developed further. Both now handle sessions, and when ZPE is used with Apache, session information is passed to ZPE-PM through the JSON request. VWS also now passes the request over to ZPE itself for handling, so VWS no longer manages sessions directly. This centralisation makes the overall design more coherent and should make the platform easier to maintain and extend.
There were also important changes for YASS as a language. The new arrow expression syntax is one of the most exciting additions for day-to-day coding. Expressions such as x.where(n => n % 2 == 0) are now fully implemented, and the feature has also been extended to work with maps, allowing forms such as x.where(k, v => v > 40). This is a very modern addition to the language and makes working with collections far more expressive and convenient.
March also introduced compiled YASS webpages through the new .yep file format. This is another major milestone because it strengthens ZPE’s role as a web platform rather than simply a scripting environment. Alongside that, LAMEX3 was added in experimental form as an AI-improved version of LAME, showing that experimentation and forward-looking development are continuing alongside the core runtime work.
Tooling and usability have also improved noticeably. A new Interactive Actions feature was introduced, allowing interactive code sessions. New ZAC tools were added, including --tools and --zpec, and there was some useful command-line tidying too, such as moving properties help from -p to -h properties. These are the kind of improvements that make the platform easier and more pleasant to work with as it grows in complexity.
Installation and deployment have become simpler as well. The old createInstallScript approach has been removed, and ZPE now installs itself. A dedicated ZPEInstaller class was introduced to support the growing range of installer responsibilities. This is an important quality-of-life change because it reduces friction and helps the system feel more complete and self-contained.
There were also several internal architectural changes that, while less flashy, are very important. Undefined is now internally defined as a singleton, which is cleaner and more efficient. Aliases have been moved from the runtime to the compiler, meaning they are now compiled into their corresponding function calls rather than resolved dynamically at runtime. This should improve both performance and compatibility. The runtime was also updated to use its own standard output, and native methods now include checks for returned data types.
DepthGuard has also been added. DepthGuard protects and guarantees against stack overflow in recursive toString functions. This is needed for ZPE's debug features, but it's also good practice.
Parsing and reliability also received attention. The JSON parser was improved, syntax errors now report proper line numbers, and a CSV parser bug was fixed so that line breaks are handled correctly. There was also a fix for a recent bug that caused the first argument in an executable to be ignored. These may sound like smaller details, but they make a big difference to the day-to-day experience of using and debugging the platform.
ZPE's performance was improved through plugins and internal functions; it now also uses a special caching method for internal functions to further improve performance.
Several smaller additions round out the month’s work. A new directory_is_empty function was added, and list_add_element now has the append and list_append aliases. These are not as fundamental as the web and runtime changes, but they still help make the language and standard library more convenient to use.
Looking across all these updates, the biggest story is that ZPE is becoming broader, faster, and more mature. Performance has improved significantly, caching is now a central part of the system, web support has become much more capable, session handling has been redesigned for greater scalability, and ZPE-PM introduces a powerful new execution model built around sockets and structured requests. At the same time, YASS is gaining more modern language features, and the surrounding tooling is becoming easier to use and deploy.
In addition, ZPE 1.14.3 introduced built-in debugging that works very well. But ZPE 1.14.4 has improved this considerably, making it faster and much more reliable. Now, instead of relying on internal commands, ZPE uses a port system to send them.
Last but not least, ZPE 1.14.4 introduced static built-in objects. These are like the Math library in Java or Python. For example, ZPE now has a CLI class with static methods. HTMLBuilder is now static also. This means they can be accessed at startup with their name. For example CLI->overwrite($i).
In short, March 2026 has been one of the most substantial periods of development for ZPE in quite some time. The platform now feels far closer to a complete application environment, with serious web capabilities, stronger architecture, better performance, and a more modern developer experience. There is still more to come, but this month has laid down some very important foundations for where ZPE is heading next.
ZPE 1.14.4 has had the most builds of any minor version of ZPE to date, with over 2,000 builds.
Arrow expressions are another new feature coming to ZPE 1.14.4. They make light work of simple expressions:
$x = [11, 34, 55, 66, 74, 87, 93, 102] print($x.where(n => n % 2 == 0))
And for maps:
$x = ["a" => 11, "b" => 34, "c" => 55, "d" => 66, "e" => 74, "f" => 87, g" => 93, "h" => 102] print($x.where(key, value => value > 40))
These new expressions are designed to simplify statements that would normally require a lambda function:
$x = [11, 34, 55, 66, 74, 87, 93, 102] print($x.where(n => function ($n) { return $n % 2 == 0}))
Underneath, arrow expressions are actually running a lambda function themselves, but the syntax is simpler and easier on the eye than a lambda function.
In addition, I have also made some other significant changes:
- Firstly, internal aliases are no longer part of the runtime but are now part of the compiler, so that they are compiled to the appropriate internal function. This improves performance slightly, too.
- New features in the parser mean that line numbering in compiler syntax errors and any other compile errors now show correct line numbers.
- And finally there's been a major fix in the CSV parser.
With a significant improvement to mod_zpe over the last few days, coupled with ZPE-PM and the new ZPE 1.14.4 performance improvements, YASS is now fully capable of running as a server-side language. And you can see what I mean if you visit the section of my website which is all powered by YASS at https://www.jamiebalfour.scot/yass. This part of my website is running the Apache module mod_zpe, and ZPE-PM is permanently running on my webserver as the backend.
ZPE 1.14.4 will be out a week on Thursday, bringing massive improvements to ZPE. Also launching this Thursday is VWS 1.1.3, which brings major updates to VWS.
mod_zpe was first written in 2024 and has been pretty decent since. Its only letdown was one of ZPE's biggest weaknesses - it needed a fresh start every time it was required. Now with the latest update and ZPE 1.14.4's new ZPE-PM, it's finally possible to get exceptional performance from ZPE.
ZPE-PM is a daemon that runs YASS code via a socket. That means that there is no start-up cost associated with running code. This makes responses very quick - almost instant.
ZPE is even more integrated into VWS than into Apache, offering an easy-to-manage installation. But at least now it works with Apache too.
ZPE-PM is the latest feature to make it into ZPE 1.14.4, and it's a major addition.
ZPE-PM or ZPE Process Manager works like PHP-FPM (FastCGI Process Manager). ZPE-PM is designed to run as a daemon process, much like ZPE Lite (more on that later).
One of the biggest limitations of traditional scripting setups is that every request starts from scratch.
- Load runtime
- Parse code
- Execute
- Tear everything down
That’s fine for small scripts, but as things grow, it becomes inefficient — and harder to scale.
So I built ZPE-PM.
ZPE-PM is a long-running process that executes ZPE scripts over a socket connection.
Instead of launching ZPE for every request, you:
- Start ZPE-PM once
- Send it execution requests over a socket
- Receive results (or live output)
It acts as a bridge between:
- clients (CLI tools, web servers like VWS)
- and the ZPE runtime
ZPE Lite is now, well, really lite. Using the zpe -l command to run the Lite mode is easy. You simply provide a file name to run through ZPE-PM (ZPE-PM must be running), and a host and port number are optional. By default, the host is localhost, and the port is 8940.
You can also communicate with ZPE-PM with Python, C#, or any programming language that supports sockets.
It's very fast. Processing with ZPE 1.14.4 has become considerably faster overall, so the Standard Algorithms went from 650ms to around 300ms in the latest update. But ZPE-PM makes the whole process really fast, and the newly improved ZPEC caching system comes in really handy for further performance improvements. Running a script once caches the byte codes for the next run. But not only that, ZPEC is designed for low-latency internalised communication, so requests are very lightweight, adding only around 7ms of overhead.
ZPE 1.14.4 is a big update. It mainly focuses on performance but also on integration with VWS.
First performance. This is big. Running the Standard Algorithms library in ZPE 1.14.3 took an average time of ~600ms. With ZPE 1.14.4, the mean time is now ~350ms. This is a massive improvement. ZPEX has gone from 30ms to 23ms to run the same library too.
VWS has recently been revisited, so ZPE's support for VWS has been improved. New session variables, cookies and much more have been added to ZPE. ZPE's web performance has also been improved. As well as this, in addition to the YASS Web Pages (ywp) files you can create, you can now also compile these to YASS Executable Pages (yep) files for up to 5x faster processing. Nice.
ZPE now has a new --tools option for special tools in ZPE. ZPE --install now actually installs ZPE. ZPEC has been improved too, offering much better and faster performance than before. LAMEX3 comes to ZPE - 'improved' by ChatGPT (although performance has occasionally been lower than LAMEX2, I am working to ensure it is consistently faster than X2).
ZPE 1.14.4 will be out very soon, as I am just adding the finishing touches.
ZPE 1.14.3 is another big update, and it's coming at the end of this week.
x509_pem_fingerprint
There is a new predefined function in ZPE, x509_pem_fingerprint, previously available only through the new zpe.lib.security library.
In addition, the direct inclusion of X.509 fingerprinting means that ZPE now supports different types of plugins and libraries. Some libraries are what are called trusted libraries - they are signed by me. Then there are untrusted libraries. ZPE will soon block these on their first load, but they can still be used after approval. These untrusted libraries will also not have the same access in sandbox mode, with restrictions on system files and being limited to the sandbox folder. In addition, certain activities, such as reflection, executing commands, and networking, will be banned. If the sandbox is disabled, they are free to do what they want. Sandbox is now enabled by default in ZPE 1.14 and later.
Stricter lockdown procedures
Lockdown is a feature added in July 2025 that allows ZPE to run in a safe mode, ensuring that certain features cannot be run or loaded. Lockdown is stricter than before in ZPE 1.14.3, as plugins will not load at all during lockdown.
Further module improvements
Modules also received a major update. When modules were first introduced, they worked fine with a main function, unless the code was compiled using the YASS Compiler in ZPE and saved to an executable file. Now that's all changed. During compilation, the main function is identified and referenced, thus ensuring that main functions within a module load correctly.
Plugin and library updates
With all the work I've been doing on plugin and library security over the last few versions, this update further improves how libraries are integrated into ZPE.
Libraries have deep access to ZPE, and they are core to expanding its possibilities even further. However, in recent versions, due to the number of plugins and libraries available to ZPE on the rise, and the inclusion of trust checks within them, plugin loading has become a burden on startup times. As a result, I realised that plugins and libraries should be loaded asynchronously on startup. This, however, causes another issue: if a library is loaded after a program is run in ZPE, it will throw an error. To combat this, I've added an additional form of loading - using the already included import command:
import "zpe.lib.sqlite"
This means you can force the loading of a plugin right there and then, and if it's already been loaded asynchronously, the import statement does nothing. Nice!
Check out the new plugins
Several new plugins are under development. These new plugins, which are currently mostly libraries, are designed to extend ZPE's functionality and were one of the key goals when ZPE was first conceptualised. A couple of the new libraries are:
libMSAccess, libSQLite, libUI, libSerial, libSystemInfo, libMQTT, libMySQL
Plugins can now be added via ZULE (ZPE Uploads, Libraries and Extensions) package manager (which is getting an update in the next version) using the --plugins option:
--zule install --plugins
You can find out more about the libraries and plugins available on my GitHub page, where I share all the source code and the latest trusted builds.
New compiler feature
Previous versions of ZPE did not support using the arrow operator (->) to access an object after a function call, such as print(get_wikipedia_reference("USB")->title). This has been a problem for a while, but after a five-minute look at the compiler, it was an easy fix. So you can now probe the result of a function with an arrow operator.
ZPE 1.14.2 has been released this weekend. The new version brings a ton of new enhancements including the ability to view variables at certain points in the program through proper debugging tools that offer step over and execution pausing - not just termination.
ZIDE v.0.1.0-alpha has also been released, and this is the first version to be properly released. You can download the JAR from my GitHub and the individual binaries from my website (Linux coming soon).
ZIDE is not like ZPE in the sense that ZIDE is still in very early days. Each time a new binary is built, it will automatically be uploaded to my website for downloading. GitHub also will continue to feature release tags for each version. You can see the full source code for ZIDE on my GitHub as well.
ZPE 1.14.2 brings three major features.
Universal template parsing
Template parsing was introduced some time ago, but was released only in January 2026 with ZPE version 1.14.1. In the latest release, version 1.14.2, template parsing is available anywhere, including in parameters and return values.
Scope blocks
Many languages have scope blocks, and now YASS does too. They are nice and easy to use as well. Simply using the double brace syntax ({{ }} or the block syntax (block . . . end block), you can create an isolated scope block:
// Everything here runs inside the implicit GLOBAL function $total = 100 print("Start total: " & $total) block // This variable exists ONLY inside the block $total = 25 print("Inside block: " & $total) // Blocks can still see outer variables $discount = 10 $total = $total - $discount print("After discount: " & $total) end block // Block variables are discarded print("End total: " & $total)
Variable scoping
Additionally, variables declared as private in a function are scoped to the containing function and no longer modify parent or global variables, allowing safer encapsulation while preserving YASS’s simple scoping model.
