Nerd stuff
We could tell you. But then we'd have to refactor you.
Very little is known about how API4UI is built. What follows is everything our legal department allows us to confirm.
API4UI is built by an order of monks in a monastery high in the Tibetan mountains, at an altitude where garbage collection happens naturally. They have taken a vow of silence, which has done wonders for the signal-to-noise ratio of their code reviews: approvals are given by raising one eyebrow, breaking changes require both.
The monks eat only mushrooms they pick themselves, at dawn, in the most impenetrable forests of the valley. Each mushroom is inspected, blessed, and unit-tested. Legend has it the entire dependency tree fits in a single begging bowl.
Releases follow the lunar calendar. Hotfixes are meditated upon for nineteen days, then turn out to no longer be necessary.
Builds run on a ridge above the clouds — the original cloud infrastructure. Artifacts are carried down by yak; latency is measured in days but the packet loss is zero, because a yak never forgets. The only outage in recorded history was caused by a snow leopard sitting on the keyboard, which the monks interpreted as a sign to simplify the API. They were right.
Because the UI builder that comes out of this is genuinely good, and the monks fear that publishing the architecture would end the mystery — and with it, the eyebrow-based code review, which several large tech companies have already tried to acquire.
The core algorithm is based on which resolves to .
* Any resemblance to an actual VS Code extension for OpenEdge UI development, built by entirely non-monastic people, is purely coincidental.