ronilav·6 lat temu·discuss> Treating unicode as something optional was fine for early 2000s, but it's really not fine today.The issues are:* how unicode support is implemented in third party libraries: how easy it turns out to manipulate this datatype with those libraries* how easy it is to integrate third party libraries in a projectOCaml went a long way in both accounts since the early 2000s, perhaps you should give it a second look?
ronilav·6 lat temu·discussIt's clear that closed source device makers will never want to prove that there are no HW backdoor, or even monitoring chip in their products, but for a device like this one, is there a will to provide such guarantee?
The issues are:
* how unicode support is implemented in third party libraries: how easy it turns out to manipulate this datatype with those libraries
* how easy it is to integrate third party libraries in a project
OCaml went a long way in both accounts since the early 2000s, perhaps you should give it a second look?