Ask two EO programmers to lay out the same object and you may well get two different files. One stacks everything vertically, another folds it onto a single line, and both are correct. We would rather the compiler decided, and always arrived at the same, prettiest answer. So we taught it to score every possible layout and pick the one that hurts the least.

A while ago we explained what the >> syntax stands for: it auto-names an abstract object when a meaningful name is unnecessary, and the compiler quietly generates a random unique one under the hood. Recently we let this same >> carry a handle of your choosing, and this small change gave EO a new way to hide things. We call it “encapsulation by obfuscation”.

It’s been a difficult year… It’s been a while since our last blog post. Today, we’re back and starting by answering a question from our Telegram chat reader: “What does the >> EO syntax stand for”?

Since the last blog post, we released a new version of EO where we got rid of the σ (Sigma) attribute. So, this blog post will try to explain all special attributes and assets such as Δ (Delta), φ (Phi), σ (Sigma), λ (Lambda), and ρ (Rho) as promised in one of the previous blog posts.

We’re continuing to observe the features of the latest release of EO, and today we’re talking about new syntax for nameless @-bound-only objects.

After the previous blog post, one of the followers brought an interesting suggestion in our Telegram chat (join it btw). He proposed getting rid of the object bool and making if an object, not an atom. And it was quite interesting. So we made a new release where we followed our follower’s proposal.

It’s been a while since our last blog post. All this time, we were working hard on fixing bugs, creating new objects, and improving EO in general. And here it is - release 0.36.0, which contains many new features. So, this blog post is a summary that highlights the most significant changes.

We’re continuing to observe new features of the latest release 0.34.1 of EO, and today we talk about the new recursive implementation of the tuple object and why we got rid of varargs in our language.