Earlier quoted context omitted.
Because it's dead-simple to parse? Remember that not all machines back then had hardware call-stacks.
It’s definitely easier to parse, but you can use shunting yard to do operator precedence parsing using very little extra memory and no recursion. I feel like the language is just poorly designed.
MUMPS
21–30 of 75 posts
Re: MUMPS
#22https://docs.intersystems.com/latest/csp/docbook/DocBook.UI....
Re: MUMPS
#23Part-time MUMPS programmer here for a health system in NYC. I still love writing in it. The rates are way better than other eco-systems (e.g. Python, Java, blah blah) , probably because the eco-system isn't diluted with low-wage workers from India/China. This is because 95%+ of Epic/Ex-Epic employees are American. I would even argue it is the patriotic language of choice due to that reason. Expected pay of 85-120/hou…
Re: MUMPS
#24Worth linking for a hotter take: https://thedailywtf.com/articles/A_Case_of_the_MUMPS
Re: MUMPS
#25Feast your eyes on Caché Server Pages. Mumps on the web. https://docs.intersystems.com/latest/csp/docbook/DocBook.UI....
Re: MUMPS
#26Part-time MUMPS programmer here for a health system in NYC. I still love writing in it. The rates are way better than other eco-systems (e.g. Python, Java, blah blah) , probably because the eco-system isn't diluted with low-wage workers from India/China. This is because 95%+ of Epic/Ex-Epic employees are American. I would even argue it is the patriotic language of choice due to that reason. Expected pay of 85-120/hou…
I'm not sure I love paying it with worse health services though. My city has sunk almost a billion dollars into a dysfunctional Epic pile of MUMPS. But I guess it's nice to see the healthcare software disgrace works well at least for some.
I don’t know if the alternatives - e.g. Oracle Health/Cerner - are really that much better - and if Epic is as bad as you say, I suspect that says more about their corporate culture than choice of programming language
Re: MUMPS
#27Re: MUMPS
#28Earlier quoted context omitted.
It’s definitely easier to parse, but you can use shunting yard to do operator precedence parsing using very little extra memory and no recursion. I feel like the language is just poorly designed.
To be charitable to its original designers, information was much less easily accessible in the 1960s than today-although the shunting yard algorithm had been published in the research literature in 1961, practitioners working 5-6 years later may plausibly have been unaware of it-it wasn’t like nowadays where they could easily discover it in Wikipedia or by asking an LLM.
Re: MUMPS
#29Part-time MUMPS programmer here for a health system in NYC. I still love writing in it. The rates are way better than other eco-systems (e.g. Python, Java, blah blah) , probably because the eco-system isn't diluted with low-wage workers from India/China. This is because 95%+ of Epic/Ex-Epic employees are American. I would even argue it is the patriotic language of choice due to that reason. Expected pay of 85-120/hou…
I'm not sure I love paying it with worse health services though. My city has sunk almost a billion dollars into a dysfunctional Epic pile of MUMPS. But I guess it's nice to see the healthcare software disgrace works well at least for some.
Re: MUMPS
#30These kind of hierarchical / network database systems are what caused E.F. Codd to tear his hair out and write https://www.seas.upenn.edu/~zives/03f/cis550/codd.pdf