Machine VM + Cloud API - Rewriting The Cloud From Scratch
highscalability.com
highscalability.com
I just went through Ertl's dissertation for the third time in as many years, and my impression is that Forth stands somewhere beside formal theories of programming languages, not within. His dissertation provides 3 implementations of forth, just as Dybvig provides 3 for scheme. The two papers are nearly identical in scope; showing different implementation techniques for a tiny kernel language. However, the Forth paper is entirely in C and assembly, without the slightest hint of formal semantics or any other mathematical reasoning. It's a hack upon glorious hack. You can't reason about Forth code without FULL abstract execution, to wit, implementing a full Forth VM with side-effects, or emitting 3-address-code, or some other linear tuple IR, and using traditional techniques from register-based languages with variable assignment.
Having said that, I can see why Forth might be fun, as a soul-cleansing language for a programmer who has spent too long in abstraction. Haskellers should use it to bring themselves down a notch [grumble, mumble mumble, something rude, under my breath]
[Edit:
Oh fuck, I forgot about Factor!
I pre-accept defeat, and retract my possibly under-informed arguments if and when Slava shows up to this discussion :-)
If his opinion differs, I don't think I am qualified to disagree with the sharpest dude hacking on a language implementation today, and Forth domain expert to boot]
The idea that we can forgo operating systems because there are APIs to call doesn't make sense if your company heavily invests in infrastructure. Sometimes you need low-level access to hardware to fine-tune performance and scalability because your use-case is not the general use-case, even in a "cloud" environment.
That the complexity of shared hosting would make it uneconomic vs VPSes in the long run.
Don't hesitate to delight yourself, no one will do it for you.