That's pretty awesome, wasn't expecting typescript support too, and thought it would just be bound to the Unity/C# API but you've added support for rendering modern React into Unity as well.
Tyty! To be honest, Godot and UE have been very tempting. I'm just too deep into Unity at this point. Even I'm surprised that their years of fiascos didn't shake me off. But it looks like things are getting better over there.
Toucan has a similar concept, but it works on individual words rather than sentences. Beyond a smaller scope, it's also quite difficult to accurately translate single words without context - Nuenki has it disabled by default.
The tradeoff is that Toucan is free, and translation is quite expensive.
This is available to anyone in Australia, although ~$500-600 a week isn't enough to support the carer and the one they care for in most personal circumstances.
https://www.servicesaustralia.gov.au/carer-payment
Note: In order to improve the readability of the text, the masculine form is used to refer to persons, functions, etc. However, it stands for all genders without exception.
Assuming that you’re male, would you be inclined to apply for a job if the description referred only to the “female employee who will hold this position” and what “her” responsibilities will be?
That’s essentially analogous to the situation that women have when applying for jobs in German-speaking countries.
This is a recent thing insisting that words don't include women because they have a male genus. And only in this specific direction. Nobody complains that men are not persons because "person" is always a "she" in German.
The burden of proof still lies on the people arguing that word X does not include women.
German work anti-discrimination laws are very pro-employee. I know a case where a company had an advert for a "junior developer" and a guy in his late 50s who got rejected after sending his application sued for sole purpose of age discrimination. The company settled in the end for almost a years salary after the judge hinted that a settlement would be wise (labour cases are often settled in Germany). Just because the usage of the word "junior".
In German, "Softwareentwickler" (software developer) is the male form, so for a long time, any job ad would say "Softwareentwickler/in" (short for "Softwareentwickler oder Softwareentwicklerin") to cover both forms. Nowadays, you can't do that either because that'd exclude people who don't identify with either gender, so I guess this is the workaround they use now to not get sued into oblivion even before interviewing the first candidate.
Have you seriously looked at this and thought "yeah thats better than using a single native function (fetch)"?
As for the rest of the API - what would you even use besides the css and selector functions? Which again, the native `classList` and a simple bind to the selectors are simpler and less verbose.
https://old.reddit.com/r/Candida/comments/17sdvm0/people_iod...