What not to use FM for

While FM does have its purposes, FM is not an interface one would normally use for:

"massively portable" applications

While the FM interface is portable to a wide variety of platforms, we currently have FM implementations for only NT. As FM uses a nonstandard API, applications that need to be ported frequently would be better off using one of the more standard HPVM APIs.

"dusty-deck" applications

Because messaging layers built on top of FM achieve most of FM's raw performance, there is little value to be gained from rewriting a program that already uses one of the other HPVM APIs to use FM instead.

Go to the first, previous, next, last section, table of contents.