I don't get the link between enterprise software and predictive optimizations. But call stacks don't prevent them (the argument seems so assume you can only really store data on the stack), nor does it prevent automatic optimization (like call site monomorphisation in a dynamic language or memoization - again, that's entirely orthogonal), nor am I sure it always should be automatic instead of in a library; seems like they just chose the words "SDSM", "predictive optimization" and "enterprise" and threw them together. Their "silver bullet" seems to be a rules engine.

Another company offering a proprietary silver bullet to the enterprise.

Condemning the stack is a novel entry point, I’ll admit.

Every enterprise timesheet and expense system I've ever used was a slow, barely usable, confusing disaster. But I don't think that was because the VM failed to pre-allocate memory for some operations.

Without the superlatives and strawman attacks and with an actual description of how things should be done instead this would be an interesting read.

Sometimes I read stuff like this and think I must be stupid. Other times I read it and think the author is full of it. I am struggling to see how a language can help with our enterprise applications because I approach the problem from the view of architecture and treat language as irrelevant. Hopefully, I am stupid and someone can enlighten me.

The author does not seem to know f.e. Erlang.

Here are all the reasons why capitalism is inefficient. Stay tuned for our alternative and sign up for our mailing list.

Replace capitalism with programming languages.