Yet another fascinating technology from the sixties still in use today; at least the database part of it came back into fashion with NoSql; the language, on the other hand, does not exactly promote readability.
If you consider funneling a non-negligible fraction of US medical costs into paying for Intersystems Cache licenses fascinating, then yes!
Those fuckers are well aware of their captive markets and extract rent like no other. The licensing costs on such an outdated piece of technology are obscene.
> extract rent like no other .. The licensing costs on such an outdated piece of technology are obscene.
They're in "good" company. Do you think its less obscene to pay the horrendous license costs to companies like Oracle or SAP?
Anyway, I'm talking about the technology, which btw. has established open source alternatives. I once had an argument with the main person in charge of hospital IT, and he made it clear that he didn't want to risk his good sleep by using technology from non-mainstream suppliers, no matter what the cost. As long as we allow such people to value their personal sleep quality over the cost to the health care system, we need not complain about the consequences.
If you don't depend on the MUMPS/ANSI-M language or don't have to be backwards compatible, a lot more alternatives with similar features are available, e.g. https://github.com/facebook/rocksdb run behind e.g. Node.js.
A couple of jobs ago, I was working somewhere where the big niche app they used was based on an Intersystems Cache DB. Cache is literallyactual commercialized MUMPS. It had a SQL translation layer, but it was still...very weird.
I remember Intersystems Cache ads. I dreamt about how nice it would be to use as I grappled with hand crafted (remember to escape untrusted inputs!!) SQL statements in the “Lower Level Business” layer of a ASP.NET1.0 app. Sounds like it wasn’t such a silver bullet?
