eggsnbacon1
Python, Ruby and friends are bad for page speed metrics. REST response time of ~200ms vs ~10ms for our java backends
Devs have to deal with all the bugs and messy codebase
Median is very misleading because of rise in income inequality. More than 50% of gains in median income last 20 years have gone to the top 25% https://www.pewsocialtrends.org/2020/01/09/trends-in-income-...
And working less hours is also skewed by the rise of millions of gig jobs that don't have set hours.
The top 25% of the population is doing great by any measure. But when you discard the top 25%, the rest doesn't look so good. Income inequality in US is higher than almost every other industrialized nation. As high as it was in the 30's when massive social unrest gave rise to unions and worker protections.
When you factor in student loan debt and minimum wage being degraded by inflation and gig jobs, the bottom 50% are poorer than ever. As of this year, student loans have eclipsed credit card and auto loans as the second largest form of consumer debt behind mortgages
To blue eyes again, you could make a facial recognition system that just looked for 2 blue iris shapes and probably score 90%+ accuracy on most datasets (of exclusively blue eyed people and non-human objects) because blue is so rare in animal eyes, and so rare in nature. With such a strong face signal it may be impossible to match accuracy for non-blue-eyes humans without purposely making match quality for blue eyes worse.
We may be seeing a similar but weaker bias for darker skin. Light skin is fairly rare among mammals. The only solution to eliminating recognition accuracy bias may be to nerf accuracy for people with light skin. There have been many reports of facial recognition erroneously classifying dark skinned humans as animals. If part of model accuracy classifies lighter skin animal = more likely human, its going to be very hard to remove that bias because its empirically true. If the classifier is unsure if a shape is a human or animal face, but its very lightly colored, it may make the model statistically more accurate to report higher confidence that a lighter colored face is more likely to be human.
this may be more of a "most animals are brown" than a "brown people look more like animals" problem with the models. A possible path to fixing the bias is to crop all faces detected, disregarding model confidence of whether the face is human
Brown is, next to green, the most common color in nature. Lighter color also has a greater contrast with the background when using camera flash or other subject lighting.
To be really blunt, I think white faces are easier to see. A common example in nature, white tailed deer. When tail is raised, their white fur is a clear danger signal because it stands out from the background. Like most mammals, the rest of their body is a shade of brown.
I don't think its racist to suggest that light skin, just like blue eyes, is a conspicuous highly visible signal suggesting a human face.
I find it hard to believe that such a large number of facial recognition models have an easier time identifying white people after years of publicity solely because of biased training data.
The ultimate example is probably blue eyes. Almost no other animal has blue eyes. Blue is extremely rare in nature. I want to see a study on facial recognition, blue eyes vs other colors. I bet money you will find that models excel at recognizing human faces with blue eyes above all other factors
Yet they're both perfectly fine with blocking apps for arbitrary reasons citing "app store policy".
Lets be blunt here, whether you agree with the Tiktok issue or not, for Apple and Google this is purely a money issue. They are probably afraid this will increase support for third party app stores among the masses
Its impossible to eliminate echo and stereo bleed with speakers. If you try to EQ a room using mics you will see this clearly. You might get close building an anaerobic chamber, but headphones are still better.
If you're on a budget don't waste money on expensive speakers, just use headphones
https://pubs.acs.org/doi/10.1021/acsmedchemlett.0c00316
By most anecdotal accounts GS-441524 is better and possibly safer. And its readily available on the black market for treatment of cat FIP because apparently its much easier to make than Remdesivir.
So yes, probably the only reason Remdesivir exists is patents
The TDD cult doesn't consider that its the last thing you should try, test everything. If you need high reliability you should move to a safer language first. Dynamic typing to static. Unsafe memory to safe, like Rust or Go. Turn on a bunch of linters too. Move to a language that doesn't allow nulls.
Once you've got a bunch of linting and a static language that doesn't allow memory corruption, do you really need to test everything? Probably not. The linux kernel is a good example as usual. Virtually no tests and its the backbone of the internet
There are some satellites like telescopes that need to be far from the earth. But the vast majority could be banned from orbits beyond a distance where they won't decay in a reasonable amount of time, with the only downside being cost
The only reason to use higher orbits is to save money on satellites and complex communication systems. Orbits that allow space junk to hang around for centuries should be banned.
With the technical might that is Silicon Valley, California only needs to hold their ground for a few months, then Lyft/Uber will become an afterthought
Best example I've seen https://www.reddit.com/r/TwoXChromosomes/comments/hzis4w/a_n...
"A message to all men" . Basically telling "all men" their opinions aren't valued or wanted on the sub. Wonderful. And it hit the Reddit front page. Imagine a "mancave" sub on Reddit with mods saying women's opinions don't matter and aren't welcome here and shit like that. It would be banned immediately, probably after making 5 o'clock news
tar.gz is ancient
They should focus on integrating Rust in portions of the API instead of exposing a gigantic unsafe API surface, essentially making all their code unsafe. Unless the Chrome codebase is really such a mess that they can't do anything without exposing this giant API surface. In that case they should rewrite it to... not do that.
"We can't use Rust unless it allows us to write all our code in C++ without showing unsafe warnings"
I echo that AC is quite efficient. Far more efficient than traditional heating. There's a misconception that hot areas are less environmentally friendly due to AC. The opposite is true.
Hot areas are only 25 freedom units hotter than humans prefer. Cold areas have months of 50+ temperature difference.
The misconception persists because heat uses gas, which is 5-10X less expensive per BTU of energy than electricity. So it might be cheaper to heat cold areas than run AC in hot ones, but its much more damaging to the environment. Plus, hot climates are using a lot of renewables these days which impacts the environmental friendliness of electric but not gas.
I expect migration to the sun belt to accelerate, at least in the US. It makes a lot of sense from environmental perspectives. In some southern cities there's already long stretches every summer where daytime AC use runs on 70%+ renewable energy.
Nobody should have access to this without a warrant, its a huge invasion of privacy.
In Java, distributing libraries as cross-platform "jars" is very common.
Networking is another example. And casting to interface while the built-in collections secretly use generics.
A good way to avoid all these problems is to use a language with great cross-platform support like Java or C#.