A Phoenix Rises

The EWD Files

This is the third in a series of articles which explores a way forward for the future of the Mumps database and a solution to recruiting a new generation of developers to support, maintain and onwardly-develop the vast and important legacy of healthcare applications that have been developed using the Mumps language and database.

In summary, the direction I’m suggesting is to:

  • replace the Mumps language with Javascript, a hugely popular and highly-capable modern language that happens to share the key characteristics of and has a similar free-and-easy feel to the Mumps language;
  • tightly integrate the Mumps database with Javascript in a way that has an equivalent level of intimacy as found between the Mumps language and database.  In doing so, the Javascript community can benefit from the Universal NoSQL database capabilities afforded by the Mumps database technology, but do so in terms that are meaningful and relevant to them.

View original post 3,154 more words


Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s