There is a trade off... easy integrate-able FRAM/MRAMs are only both of smaller capacities and more expensive than (Flash)EEPROMs. With a huge (Flash)EEPROM compared to the space needed and the (Flash)EEPROM run on a wear leveling driver you do not run THAT quickly into issues. The MCs with FRAM/MRAM have only 16..128..256 KB of that type of memory and for the vast amount of read-only needs they still run (Flash)EEPROM. Having all your application state in transparent, non-volatile RAM makes a sleep and resume very simple and and even more so quick. Last but not least not having to save and restore state saves battery...
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
There is a trade off... easy integrate-able FRAM/MRAMs are only both of smaller capacities and more expensive than (Flash)EEPROMs. With a huge (Flash)EEPROM compared to the space needed and the (Flash)EEPROM run on a wear leveling driver you do not run THAT quickly into issues. The MCs with FRAM/MRAM have only 16..128..256 KB of that type of memory and for the vast amount of read-only needs they still run (Flash)EEPROM. Having all your application state in transparent, non-volatile RAM makes a sleep and resume very simple and and even more so quick. Last but not least not having to save and restore state saves battery...