Maybe lossy is the wrong word, but the transforms historically had gotchas. PPX and what not. Especially when converting between Reason syntax version upgrades and the more stable OCaml syntax (locked to OCaml 4.2 because of bucklescript).
That doesn't necessarily mean lossy, but just that knowing what refmt will error out on depending on the version of Reason the code was written to target vs. locked down ML.
I think the ReasonML parser and formatter have numerous issues that'll keep it from being adopted more widely.
Especially with nested expressions, the inability to find mismatched parens and braces ultimately turned my team's experiment with it sour.
The base language's grammar is said to have inconsistencies, but I think Reason's 1:1 matching while keeping older constructs makes translating very difficult. There is a tool to do so, but it's lossy.
That said, I use Reason React for a small front end project at work and sort of wish that the ppx for JSX wasn't tied to Reason, so that vanilla OCaml could be used instead.
An example of lossy translation from Reason -> OCaml:
Long ago, when I was at Amazon, we used Collaborative Filtering pretty heavily. It's great when there's a heavily sweetened path with lots of things ordered together or in a chain.
It's horrible for moderately popular items though.
As an American that took a substantial pay cut (taxes add to the pain) to get into Germany, this sounds about right for my experience. I came over mostly as a cultural thing, and salary was less of a concern.
I work with a few Canadians as well, and they didn't have access to the same salary levels back in North America that Americans do, so salary is less of an issue for them coming to Germany.
Does the article handle ethnically discriminatory hiring practices? Neither "Divers-" and "ethnic"show up in the article, and if it's like Boston's Chinatown, workers are overwhelmingly Chinese.
Boise, ID has the same problem with air quality (and it's also in the Mormon heartland). As a non-Mormon growing up in Southern Idaho, it's hard to argue the church isn't very influential politically and also good at social works.
It would be nice if they focused on the JavaScript backend a little bit. There's issues like https://github.com/purescript/purescript/issues/2577 that show the serious performance issues the language has with its primary back end.
In all seriousness, people using non-mainstream languages are very attached to them. At least in my sample size of one.