MUMPS
en.wikipedia.org
MUMPS
1–10 of 75 posts
Re: MUMPS
#2Worth linking for a hotter take: https://thedailywtf.com/articles/A_Case_of_the_MUMPS
Re: MUMPS
#3Hey there to all the EPIC kids poking their head in this thread. Where did you all end up post-EPIC?
Re: MUMPS
#4Looks like someone just got hired to work at Epic!
Re: MUMPS
#5> First appeared 1966; 59 years ago
That's honestly impressive. Though I don't envy people who have to work on this stuff.
Re: MUMPS
#6> OPERATORS: No precedence, executed left to right, parenthesize as desired. 2+3*10 yields 50.
How do you even come up with this?
Re: MUMPS
#7> OPERATORS: No precedence, executed left to right, parenthesize as desired. 2+3*10 yields 50. How do you even come up with this?
It's easier to parse since you can process it in-order, makes for an easier single pass approach.
Re: MUMPS
#8> OPERATORS: No precedence, executed left to right, parenthesize as desired. 2+3*10 yields 50. How do you even come up with this?
Simplicity of implementation?
Re: MUMPS
#9> OPERATORS: No precedence, executed left to right, parenthesize as desired. 2+3*10 yields 50. How do you even come up with this?
Smalltalk does the same thing!
Re: MUMPS
#10The core idea-a language with a built-in persistent key-value store-is actually pretty cool.
The classic implementation is filled with horrible warts, although arguably many of them were helpful in squeezing a production multiuser system into the tiny resource constraints of the original 1960s implementation platform (18-bit PDP-7, same machine as Unix was birthed on, although Unix soon moved to the 16-bit PDP-11, which was in practice more spacious)
Modern implementations make many of those warts optional, although they still support them for backward compatibility
The biggest problem with the language in practice is that many major code bases (e.g. VistA) are still predominantly written in the legacy extremely terse coding style rather than a more modern readable style. I do wonder why there isn’t more effort put into migrating to a more modern style, especially since with the kinds of tools we have nowadays that migration could be (at least partially) automated.