Correct, there are lots of abstractions under the hood it doesn't mean they need to be intertwined with our business logic. What's next exposing the microcode o

Correct, there are lots of abstractions under the hood it doesn't mean they need to be intertwined with our business logic. What's next exposing the microcode or physical RAM layout? Even worse majority of ISAs are register-based, not stack-based. So this abstraction is virtual. What I meant is that Forth wasn't designed from first principles. Instead of solving the problem "how to help developer to transform business logic into an application", it solves the problem "how to help developer to program a stack machine". It was fitted to a simple, but useful abstraction - stack machine. Same with Lisp, APL, C, etc. In case of the C language the abstraction was PDP-11 ISA ;) Glorified data structures -> PL: array -> APL list (cons) -> LISP stack -> Forth relation -> Prolog Glorified data structures -> DB: relation -> SQL (RDBMS) map -> NoSQL K/V stores hashpointer -> IPFS hashchain -> Blockchain Merkle Patricia Tree -> EVM