ColdBox 4.0: What We Kept

CacheBox, ColdBox MVC, LogBox, Tutorials, WireBox

Nathaniel Francis February 20, 2015

Spread the word

Nathaniel Francis

February 20, 2015

Spread the word

Share your thoughts

State of the ColdBox

ColdBox 4.0 is a major release. The most significant major release since it went alpha/1.0 in June of 2006.

Most of the changes have been focused around streamlining, efficiency, extendability, and leaning out those things aren't really essential.

This may leave you wondering, "What's left?"

Helping the core

Outside of the absolute core, essential code that makes ColdBox tick; three of the iconic Box products are "baked in" to the core.

WireBox 2.0
CacheBox 2.0
LogBox 2.0

Each of these libraries are automatically in ColdBox 4.0 because we use them to do ColdBox magic - they are an essential part of ColdBox processes.

Everybody gets an update!

As part of the ColdBox 4.0 release, each of these libraries also got their own major updates.

Wirebox 2.0 got some new functions and features
LogBox 2.0 deprecated its xml support and had some bug fixes
CacheBox 2.0 also deprecated its xml support

Not just for ColdBox

Each of these libraries are also available for non-ColdBox CFML use. We find them so useful that we don't want to keep them to ourselves. Each of them is available on ForgeBox for download and use in any CFML application.

To make working with these libraries easy, whether you are working in ColdBox or separately, each library has their own refcard to help make things simple and clear.

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.

BoxLang 1.14.0 : BoxSet is Here: BoxLang's New First-Class Set Type

BoxLang 1.14.0 ships something that JVM developers have wanted for a long time: a true first-class Set type baked directly into the language. Not a wrapper you reach for manually, not a createObject( "java", "java.util.HashSet" ) incantation you paste from a Stack Overflow answer years ago. A real BoxSet with literal syntax, operator overloads, a full functional pipeline, change listeners, JSON serialization, and deep Java interop.

Blog