Performance reasons aside, TrustTunnel is developed by the team whose main language is C++ (and the client library is actually written in C++) so Rust was a more natural choice for them.
Likewise interested in the authoritative answer, but: if I needed to write a decent chunk of code that had to run as close to wire/CPU limits as possible and run across popular mobile and desktop platforms I would 100% reach for Rust.
Go has a lot of strengths, but embedding performance-critical code as a shared library in a mobile app isn't among them.
Debian testing is about as stable as it gets while also being a rolling distribution. The promotion of package updates from unstable to testing does not take that long either depending on the severity. I would venture a guess that there is more to it.
And over Fedora/RHEL. If I had to guess, it could be that new entrants find it easier to submit changes to Arch Linux packages [1]. ChromeOS also steered away from Debian-based distributions, choosing a Gentoo base.
Monotype does not have the same consolidation with CJK when compared to the virtual monopoly it has with Latin script typefaces.
They still have a healthy selection of competitive companies to choose from such as Morisawa, Iwata, Motoya, Ricoh, JIYUKOBO, DynaComware, Arphic, Sandoll...
Until I switched, it would only peer with other Tier 1 providers 2000 mi away from my location, even though there is a large IX 5 mi from home co-located with a large regional ISP with several other networks and appliances connected to it.
I filed a complaint but it is impossible to escape the event horizon of the customer service black hole, and customer protection regulation agents fail to appreciate how clownish it is to have 100 ms ping to my university 5 mi away.
So I switched and recommended everyone within earshot to do so as well.
To this day I fail to understand the logic behind not peering locally.
> Typst has made some basic choices, which as someone who typsets a lot of math, makes it a no go.
For me, breaking from not just a 40-year-old history of mathematical typesetting but also from the American Mathematical Society recommendations is the dagger. Plus doubling work if you want to reuse what you wrote to render MathJax or KaTeX.
> $\alpha x$ is correct and $\alpha\beta$ is correct, but $\alphax$ is not.
Like you said, braces can be used so all of the following are valid: ${\alpha}x$, $\alpha{x}$ or the odd $\alpha{}x$.
I taught Digital Design this semester - all models output nonsensical VHDL. The only exception is reciting “canonical” components available on technical and scientific literature (e.g., [1]).
Any particular reason to adopt Rust for this project instead of Go as many of your other products?
Because I think since you have quite extensive Go codebase I would imagine you had to rewrite possibly a significant amount of code.
reply