HEAT works on JVM so what is the original programming done in?
if you are a nerd and want details
Don't have the time to dive into this but I see the point you are making.
While its true that compression of numbers could potentially save lots and lots of space.
What is also true is that to make our storage backend run in a memory efficient manor we try and re-use heap memory as much as possible and re-populate heap memory from off-heap OS memory to have as little GC downtime as possible.
For this we need fixed sized variables where those optimizations don't work.
Also in HEAT there is no use of floating points, we only use whole numbers, you can't write financial software using floating points, you use cents instead (when using dollars for instance).
Using a JVM language and for the sake of code simplicity (simpler code is easier to debug) I don't think those solutions offer a net benefit, the drawbacks will likely be greater than what they offer us.
I have been looking at - what to learn or AI and Quantum.
Wolfram language or Lisp is great.
Shen is a very interesting Lisp combine that to go to Shen,
I taught myself Scala this year (always try to learn two new languages each year).
Choice fell on Scala since it's the base language for Play! Framework which after extensive research turned out to be the best complete-package to solve all our cloud/backend needs for everything we now and in the future need to build out HEAT backend to million-user levels.
And Scala integrates naturally with HEAT since both are JVM based.
Never got to learn Lisp.
But since most higher level functional languages (Scala, Clojure etc) are based off Lisp principles, there is a big change that if you learn Lisp you have a better change of deeper understanding anything based off Lisp.