There are gaming consoles, or you can just not run their games, it's not like there aren't literally thousands to choose from. They're also just games, cheating is not a life or death thing, or it shouldn't be.
Alternatively, you could stream a game from a remote server like on Stadia. These anti-cheat systems are only for online games anyway, and you can let Google deal with their kernel driver.
You can migrate docker deployments to K8s just by adding the parts you were missing, so when in doubt, it always makes sense to start with docker, docker-compose, and only consider K8s as an alternative to docker swarm.
The Internet Archive just announced a no-waitlist book lending due to COVID-19, I'd guess their servers might not be too happy about the inrush of users.
If you want to ask those questions, you also need to ask what's the alternative. What happens if we continue business as usual and 5% of the population dies in a couple months? What if the virus mutates and another 5% die in the next couple months after that? What if immunity only lasts for half a year, and we get a 5% death rate every year from now on? Is it reasonable and the price worth paying?
Semicolons in JS is how you differentiate between someone who understands that code ambiguity leads to pain, vs someone who shouldn't be allowed near multi-line statements.
The important part is the cortex, so in this case he might have lost some white matter connectivity but kept most of the gray matter structures. IQ of 75, though.
Half-life means that after 5750 years half of it will have decayed, then half of that in another 5750 years, half of what's left in another 5750 years, and so on. That's about 20000 years for still 10% of the original power output, and it won't go totally dead for some million years more.
The same as from using Electron, but a step further: less overhead from unneeded browser features, ability to lock the user into a kiosk/fullscreen mode, while most of the code is still reusable.
If people want to use WebAssembly to write non-browser applications, then it needs some non-browser API to replace the user interaction capabilities a browser's API would usually provide.
I'd also wonder how that "watching" time gets counted.
For example, I know of people who would turn on the TV, then go about their chores, but they aren't paying attention to whatever is on. Would that be better or worse, from a cognitive point of view, than intently watching a program?
As a different example, I like "watching" films or series while doing some work, as in watching for a few minutes when I get stuck on something, then hitting pause and going back to work. Other times, I'd just stare at a blank wall for a couple of minutes. Would that count as daily watching time?
Ingesting data and evaluating it according to some model, sounds like what a good cluster node would do. No need to permanently store neither the data nor the output on the node itself, but you might want it to update its process via learning.
You may find some cheap Chinese "body massage" vibrating devices with adjustable speed settings, probably in pink. You may not want to trust them with any intimate parts, but I've found that they're great at vibrating toner or flour down a paper funnel, so wouldn't be surprised if they also worked for this.
What kind of "value" can not be specified as a feature? Whether it's a better SLA, expertise adapting the product to the customers needs, or anything else, those are just features which some clients may want, and others may not.
They correct the predictions for past data, but I'm sceptical as to whether it's possible to correct for emerging feedback loops when the results of the analysis are public and cause a change in the behavior patterns being analyzed.
It's transparency when the information is about protest planned for the next day or further in the future.
It's less clear cut when it becomes more of a "barrier has been breached on this street" along with "cops are moving to this other street" in realtime.
"Peaceful" does not mean destroying the streets, setting cars on fire, throwing incendiary devices at the cops, or bullying those who don't agree with you.
It returns a "Repository unavailable in your location" message, which is kind of ironic since the website itself is still accessible from
https://tsunamidemocratic.github.io
It means masked individuals breaking sidewalks with a mace to make rubble which they can put in a stolen supermarket cart to supply their friends at the front line made from burning trash from where they can safely hurl stones, fireworks and incendiary devices at the cops, while other groups use apps like this to know where they can safely go to build new burning trash front lines or rebuild the ones some neighbor might have extinguished.
Whether one agrees or not with the demands, both HK and Barcelona are serious, public, and the opposite of order.
The user probably wants to know where they are in a list while scrolling, but otherwise it shouldn't be a problem to reclaim that screen space by hiding the scroll bar when they're done.
Probably true, but also COBOL usually encodes the business logic, which is much harder to throw away and rewrite from scratch, than any presentation layer written in PHP.
I wonder if privacy conscious browsers making their users have to solve more captchas will lead to more people disabling the privacy features... or there will be a time when captchas may become micro transaction based, so for a fee you might be able to skip them. A browser with support for an anonymous cryptocurrency to make the payments should be private and easy to use enough, but it might become an interesting world where you need to pay to remain anonymous.
That's the problem with any biometric data being used for authentication: once an attacker gets a copy, it's game over.
Biometric passports are a means of identification, not authentication, with the biometric data being signed by a trusted third party, but not considered a secret. The only protection they include is a password printed inside the passport to thwart silent NFC data access.
The more ISPs migrate to IPv6 and CG-NAT, the more free IPv4 addresses for everyone else. Wich means the migration will take a really long time.
Also the only way to reach an IPv6 target from a IPv4 source is through a CG-NAT, so dual stack IPv6+CG-NAT deployments should be the norm for many years to come.
Yes. Customer services, as in both support and feature development, should be enough to keep paying customers paying. If a bunch of "use at your own risk" software can replace it, what's the actual value of a business?