Thoughts on agile software development
Every now and then, I look into the capabilities of other template engines for new features. If something offers added value and fits within FreshMarker’s concept, then it gets adapted. Sometimes the result is something completely different, and sometimes it’s very similar to the original. Since FreshMarker 2.3.0, the built-ins find, matches, and split have been available. Why not add a few new built-ins using regular expressions?
I’m excited to announce the release of FreshMarker 3.0.0! This major version brings significant improvements and modernizations to the template engine.
Some features of a framework are so expected that you end up being surprised when they don’t actually exist. Just recently, it happened again: our team thought it would be better to write a Spring Data construct using a query method. But at first, it didn’t work.
When you write ${date + 3} in a template, TemplateLocalDate knows how to add an integer. When you write ${3 + date}, the roles are swapped: the number is on the left, and TemplateNumber has never heard of dates. Historically FreshMarker only dispatched operators on the left operand, which meant that a new type could never opt into being the right operand of an operator without patching every other type. This post walks through the design and implementation of the new symmetric operator dispatch that fixes exactly that.
Some algorithms are real classics and yet nobody really knows them. Day in, day out, everyone is happy about the beautiful wrapping of their text in the word processor, but why does the text actually look so beautiful spread across the lines?
This article is a slightly updated English version of the article “REST Endpunkte mit Filtern”.
In addition to sorting and pagination, filtering is a fairly common action on REST endpoints. In contrast to the first two, however, there is no adequate solution for filtering in the Spring Boot framework. With little effort, however, this can be elegantly implemented with the Spring Boot tools.
Tunnel constructions are classic waterfall projects in which extensive planning is carried out and then construction can be completed without major changes. There are geological surprises from time to time, but a tunnel plan is, quite literally, set in stone.
FreshMarker has introduced the ~ operator, which concatenates values with a space. With FreshMarker 3.0.0, ~~ is introduced: the same concept, but this time non-textual primitives are passed through the configured formatter before concatenation—numbers, dates, and other primitives thus appear exactly as they do in the rest of the template. The Problem with Simple Concatenation FreshMarker has … Read more
The previous post looked at the Stage 1 (untyped) compiler and finished with an honest observation: Stage 1 removes fragment-dispatch overhead but still evaluates every expression through TemplateObject. This third and final post explains how the Stage 2 compiler uses a TemplateTypeSchema to emit raw Java that talks directly to your data model — and how that unlocks the ~2.5× AOT speedup from the benchmark chart in the first post.
The first part of this series introduced the new FreshMarker compiler and compared it against the tree-walking interpreter. This second part zooms in on Stage 1, the untyped compiler, and shows exactly what code it emits, how the class is assembled
FreshMarker 3.0.0 will introduce an ahead-of-time (AOT) and just-in-time (JIT) template compiler. This first post in a three-part series explains what changes under the hood, what you gain, and what you give up compared to the classic interpreter.
Macro-based templates often need a sensible default body for the common case, while still allowing customization at the call site. FreshMarker 3.0.0 will support exactly that: <#nested/> can carry inline fallback content that renders automatically when no caller body is provided.
This article explains how the feature is implemented, from grammar to runtime, and includes a design note on one carefully chosen trade-off.
Memory management is a major challenge when it comes to improving the performance of Java applications. When many objects are created, memory must be allocated for them; these objects must be managed and eventually deleted, and their memory released. This comes at a cost, and an application that consistently works with fresh objects will suffer from reduced performance.
With Freshmarker 2.7.0, the PooledTemplateProcessor has been added, which guarantees a performance boost in template processing; however, this comes at the cost of compromises elsewhere.