In general, Google objected to the broadness of the class, which on initial filing covered all non-White employees. Specifically in regard to Black employees, they pointed out that some of the evidence presented suggested that Black employees actually earned less even than Latino and indigenous employees, so they might actually have opposing interests. There was also reference made to a different class action (Curley v. Google, in federal court) that would cover Black employees instead.
This got down to a pretty low level of details, not only specifically cutting the class down to "Hispanic, Latinx, Indigenous, Native American, American Indian, Native Hawaiian, Pacific Islander, and/or Alaska Native" employees but also explicitly excluding anyone in any of those groups who identified as Black.
It appears to be because the person who filed the suit was mostly concerned with oppression of people of "Hispanic, Latino, Indigenous, Native American and other minority backgrounds."
The bigger issue really is that Google should start reviews of a lot of managerial decisions in this regard. If you've got courts agreeing with plaintiffs, then these people you've been hiring are pursuing their, um, "preferences", a little bit too openly. You have to take things back in hand.
I'm guessing the court made no statement either way if there was a settlement? A civil court's job in the USA is to try every possible means to help both sides to reach a settlement (or other disposition) without trial. Trial is an extraordinary remedy.
A court will never make a statement favoring either side in a settlement. A settlement means the case never went to trial, and therefore, the sides never presented their cases in full to the court, so such a statement would be completely out of line.
In my brief experience with litigation the only role the court has in helping both sides achieve a settlement is forcing the litigants to go through endless and expensive procedure until they both realize it's not worth it. Before trial, the court does little to indicate to you that it even knows you exist.
I've done a lot of litigation.. the last settlement I did the federal judge basically sat in her pajamas in front of her web cam all day flicking back and forth between plaintiff and defendant doing her best to talk through both sides of the arguments while trying to keep secret what the other side was telling her. She was very patient, despite how tiring and tedious the negotiations were. She was very actively engaged, though, bless her cotton socks.
By the same numbers "Latinx+" are actually over-represented at Google and white people underrepresented. Neither by a large amount though.
With how close the numbers actually are I wonder if the different biases of different HR people and hiring managers actually cancelled out pretty well.
Side rant. Cut the Latinx crap please, Latinos don't really feel represented by the force-fed "inclusive" name that straight up goes against their gendered languages. It's overriding the language to seem more inclusive in English
Just to be clear on this one: are you Latino? Why do you speak for them? I have latino friends who insist on that language, some who don't give a fuck, and latinx friends who own that jab at the patriarchal idea of forcing gender on genderless objects or groups.
Put another way: The NAACP didn't change their name, but if you called most black folk I know "colored" they'd punch you in the throat. Language is fluid and all that.
So again I ask: Why the generalization on how a whole mish mosh of people feel.
I probably agree much more with you on these issues in general than I do with the other poster, and there are so many bigger problems right now, but we don't need to speak for anyone here. We just listen to what's already been said.
Less than half of Hispanics have even heard the term "Latinx", and of those that have, an overwhelming majority (75%) say they'd rather you don't use it. This is true regardless of age, gender, race, education level, party affiliation, orientation/gender identity, and immigration status - you don't get a much clearer picture than that in a poll. The plurality, and usually majority, preferred term across all demographic slices was "Hispanic", which is also not gendered.
If we choose particular terminology, and ask others to do so as well, shouldn't it be with the clearly-expressed preferences of the people we're talking about in mind? To me, that seems like the most obviously-respectful path.
> Less than half of Hispanics have even heard the term "Latinx"
It doesn't help that it's unnatural to even pronounce.
> there are so many bigger problems right now
Indeed, I'm more worried about the loss of true freedom of speech and the impending sense of WW3 coming. Having HR mix up race and sexual identity in some select countries is a minor complaint.
Yes, and look at the stats that the sibling post shared. I'm talking from experience and obviously some generalisation from what I saw among a few separate groups of Latinos. I'm not making stuff up just to be offended on the internet.
> I have latino friends who insist on that language, some who don't give a fuck, and latinx friends who own that jab at the patriarchal idea of forcing gender on genderless objects or groups.
Yes, but the ratios I saw had a clear trend and everyone agreed that the X at the end was clearly made up and force-fed instead of borrowed from Spanish/Portuguese/Italian/French.
> I don’t use LatinX, but I don’t think it changes anything and it doesn’t bother me that other people do.
Surely it doesn't change anything for you, but I'm not complaining because absolutely no one got mad, people were furious, but unsure how to get angry at the Diversity stuff without getting cancelled.
On the one hand, this is linguistically correct… if we were speaking Spanish.
As we're not actually using real Spanish, such criticisms feel to me like objecting to the way Star Trek dares to boldly split infinitives that have never been split before on the basis that Latin (the language) didn't split them — Latin couldn't split infinitives because infinitives in Latin are single words, just as the -x suffix to denote -[o/a in this case but way more complex when you get to all the other gendered suffixes] doesn't make sense in Spanish.
(And now I'm wondering if anyone says "una hombra" and "un mujero" for trans people…)
This is mainly a comment about English speakers borrowing the word as an exonym, my grasp of the Spanish language itself is "tourist" at best.
> On the one hand, this is linguistically correct… if we were speaking Spanish.
I don't see many English words ending in X, so I doubt it's linguistically correct in English either.
Normally you just borrow the word as closely as possible, maybe trying to make it easier to pronounce (see any word the Japanese borrow from English), but here people that didn't speak Spanish, but apparently knew a little bit took over.
English corrupts a lot of stuff it borrows, the examples which come to mind are when people try to be fancy. See also "chai tea", the difference between beef and cow. Also corrupts itself spontaneously, what with all the "u"s in British English or how many "i"s there are in aluminium.
Ok, but this isn't a Portuguese/Spanish/French word that was borrowed into English that naturally got a final X because it suited English better.
I didn't say there are no words ending in X, but it isn't common and it's not a way to help borrow words from other languages, nor is the X also borrowed.
> this is linguistically correct… if we were speaking Spanish
That the linguistically correct in both English and Spanish (and other Latin-derivative languages) term “Latin” got passed over in favour of Latinx sort of speaks to the motivations of those who pushed it.
It’s not--it's still a neologism. But it’s grammatically conventional to both languages in a way LatinX is not. (The idea of neutering languages without a neuter tense is its own can if worms.)
Nice! It's great to have more open source platforms in the CRM space.
This feels a lot like Directus [0] except that the latter is a more general data platform you build upon. They have a 100 Apps in 100 hours playlist where they build sample apps on top on Directus, even a simple CRM [1].
Have you taken a look at Masonite Framework's ORM [0]? It's an implementation of ActiveRecord. I'm not sure why the framework [1] doesn't get enough attention though. I think it's a nice option for projects that have outgrown Flask but aren't keen on Django.
Sentry is great but I’ve noticed that it significantly increases the request response time which makes it unusable for high traffic web apps. This happens with both the hosted and self-hosted instances. I’m not sure if it’s due to bad configuration or PHP. I’ll give this a try and see…
This is due to how PHP and Sentry for PHP works. It sends out the data after every request to Sentry backend via HTTP. Depending on your network path to their servers, I have seen this take 10-100ms. This is different on how other APMs work for PHP, for example Tideways that I work on, or DataDog/NewRelic/Blackfire. They have a local agent running that accepts the data over socket/tcpip before sending it to the backend for processing.
The workaround in case of Sentry is to deploy the Sentry Relay in your network and send all data there.
Synology Audio Station [0] should be a good replacement for Apple Music and Other streaming apps. Their iOS and Android DS Audio apps are quite good. You can even access your Synology NAS remotely so that should tick quite a few boxes.
I would suggest Masonite [0]. It’s lightweight enough to replace Flask and has a plethora of built in features if you need to build a “production-ready” app. It tends to imitate Laravel in its project setup and naming conventions which, depending on your preference, can either be a boon or a bane.
