Blog
Recent Entries
MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge
The MatchBox open beta is live at https://boxlang.ortusbooks.com/boxlang-framework/matchbox, and it brings something genuinely new to the BoxLang ecosystem: a path into WebAssembly.
That means BoxLang code can now move into browser applications, static-site deployments, edge runtimes, and WASI-style containers - without requiring a JVM. The feature is still beta, but the core direction is already useful: write BoxLang, compile it with MatchBox, and ship the generated WASM artifact to wherever a small portable runtime makes sense.
One Language, Every Runtime: BoxLang Expands Beyond the Server
Discover how BoxLang’s multi-runtime architecture helps developers build beyond the server with support for serverless functions, desktop applications, CI/CD workflows, Java integrations, containers, runtime management, and more.
BoxLang 1.14.0 : Introducing Inner Classes
BoxLang has always embraced a simple truth: the way you organize code shapes the way you think about problems. For a long time, if you needed a helper class, you needed a file. One class, one .bx file, no exceptions. That's clean and predictable, but it creates real friction when a class is tightly coupled to exactly one caller and has no business existing anywhere else.
Add Your Comment
(2)
Dec 01, 2007 17:15:53 UTC
by Luis Majano
UPDATE:
I have made this work by using a combination of a coldfusion mapping and the virtual folder.
Dec 02, 2007 18:43:37 UTC
by Aaron Roberson
Is this related to the error I am receiving on BlueDragon 7:
Expression Error
Detail Problem occurred while parsing: coldbox.plugins.MTlogger.logErrorWithBean-F58B9C85-C8A9-1565-95ABA9CA1CC64A6E
Extended Info Encountered . Was expecting one of: <EOF> ... ... ... ... ... ... ... ... ... "&=.+-*/\^EQUALEQUALSISEQNEQLTGTCONTAINSLTELEGTEGENOTLESSGREATER" ...