HN user
We believe that substantial improvements can be achieved through an incremental transition to a partially-memory-safe C++ language subset, augmented with hardware security features when available.
Google’s own Carbon language is positioning itself as C++ successor with an incremental path towards a memory-safe subset. It is odd that the article didn’t even mention it.
My friend’s startup is working to make the dialysis itself more portable and accessible by dramatically relaxing the water and other operational requirements. They are now running a human trial in Canada.
A device that can be in the body feels like the ultimate holy grail in this area. Medical advances like this take a lot of effort and time.
I believe the library mentioned in the article (i18next) provides the necessary hooks to do this. See ‘saveMissing’ option [1].
Though you need a backend to save this and manage translations. The maintainer of that library, locize, business model is to provide such a service.
Compatibility with the existing widely used technology is almost always a winning move.
This is the reason I am bullish on Mojo.