Just to power users? I keep getting suggestions to finish viewing last 1-2 minutes of each episode - the end credits that I previously skipped using big "start next episode" button.
Some monitors just have bad backlight. I had old one where maximizing terminal(which is mostly black) window caused taskbar and window handle also to turn almost black.
Last time I tried hackerrank i wasn't impressed - the problem specification was lacking, input/output wasn't defined well enough. Quality varied wildly between problems.
Storing hashes in source repo would make it very hard to manage and I am not sure if processing raw names into hashes as part of build would be any help against such DMCA request.
> My job is not to balance an arbitrary math equation that x% of engineers are supposed to be women
It really sound like Goodhart's law. It no longer matters that corporations wanted to remove bias from hiring process and access mostly untapped pool of talents. Now it is important how well they are doing it, measured by single % value.
Buying ASICs is high risk and (probably) high reward - in event of crash you are left with worthless machines. GPUs will still have some value, even after all crypto currencies drop.
I saw thin layer of ice appear on parking sensors after few minutes of driving in snowy conditions, triggering "close object" warnings. And cars get dirty all the time, I wonder if cars will end up with separate wiper for each sensor.
As a counter counter anecdote, scientists where estimating that perfecting automatic text translation will take another 10-15 years... in ~1960.
I guess hoping that future technology will solve all out problems is similar to expecting next generation to pay our debts.
Yeas, what about it? Oh right, it might stop working after Firefox 57: https://github.com/piroor/treestyletab/issues/1224 . There are people working on it but that isn't true for many other extensions that are no longer under active development.
Yeah, worst example ever. They should make it harder to make inner anonymous classes, not easier. When such code is used inside JEE/CDI/Spring Beans it leads to some annoying leaks or issues with serialization.
Lucky for us (in this case) certificate pinning is considered to risky to actually deploy in production, it is to easy to make the page completely unacceptable with single mistake.
Maybe it is even worse when it is just few - people won't know that website creator isn't responsible for all of its content. And sometimes is hard to know who is the culprit like in https://news.ycombinator.com/item?id=12091900 .
Is there any solution other than totally killing HTTP that protects from HTTPS stripping attacks? HSTS won't protect first visit and STS preload lists can only be so large.