> 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…
> looking at OCaml it just felt horrible care to elaborate?
It'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?
> 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…
> looking at OCaml it just felt horrible care to elaborate?
It'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?