However if you spread a finite amount of energy / matter over an infinite distance, the density would approach zero, thus we would not even perceive that it exists.
This assumes an even distribution of mass / matter / energy. If the distribution weren't even (because another unstable force, like gravity, caused it to collect together) you would see vast swaths of "empty" space and clumps of matter / energy as it collected together.
Also consider that "speed" is a function of distance over time and "time" is actually space/time and altered by gravity. It could very well be that the qualities of time did not exist as it does today, making the speed of light infinite.
Or, we could educate people on how to determine what a credible source is and teach people critical thinking skills.
Most of the "fake news" articles were blog posts, reddit threads, and sites that popped up to pander to fears for advertising dollars. Stuff that was easy to spot as being fake.
Yeah, sometimes I would see the "fake" sites come up with a real story a couple days before everyone else did, but generally the real sites were better researched and less blatantly biased than the "fake" article.
The problem with integrating it into cars is that it isn't efficient enough. If you consider that most solar panel installations require that they be placed at the best angle to the sun and that cars are not going to be at the correct angle, likely to be under shade/snow/garage, and the surface area of the car is low compared to typical roof installations, the maximum power from integrated solar cells is extremely low.
Even if you used solar paint and solar windows for maximum surface area, you won't be able to power a car completely off of the energy hitting the car. That said, you could probably trickle-charge to increase the car's range between full charges, which would be of great benefit to the car's current mediocre range.
HR is brain-dead when it comes to understanding technical qualifications and abilities. And they don't care.
While true, it isn't for the reason you think it is. HR, especially for non-tech companies, has no clue what all of these programming terms or software things mean. You're lucky if you get an HR person that understands anything more than Microsoft Office. They depend upon the managers, who write up the job listing, to tell them what they need.
HR makes the assumption that if you put in a specific version of the software, you really do need an expert on that version of the software. Even if you and I know that it hasn't changed much in the past six versions, HR sees it as something completely different because they don't know better. Even recruiters for technical contracting companies sometimes aren't much better.
HR expects you, the prospective employee, to understand what those terms mean and for you to tailor your resume to what the specific job requirements are. That can mean letting them know that the products are similar or that the newer version is the same as the older version. You can put it in the cover letter.
If HR is posting nonsensical job listings, you can blame the hiring manager for giving them poor requirements. Take that as an opportunity to judge the company communication and/or who you might be working for in the future.
Something that I've learned about Pandora is that you can't have multiple genres in the same station (use a mix for that) and you can't thumb up certain songs or you'll skew your playlist towards a certain genre or a small subset of songs even if the rest of the music on the station doesn't match that song.
It's like certain songs or dimensions are weighted more heavily than others and adding songs with those dimensions skews the entire playlist dataset in a direction that you don't necessarily want. When you have a small group of songs that do that, you can actually make Pandora tell you that you need to add more variety to the station to keep playing music.
But in terms of selecting and engaging targets on its own without a communications link, that technology is not there yet
Actually, not true. We are there now. MIT already has fully automatic and autonomous flying helicoptors that can perform stunts in mid-air, and there are many, many videos of targeting systems using machine vision to target and "attack" specified targets. Most of them use nerf guns and lasers, but the point remains. We know the technology to do fully automated drones that engage and eliminate targets.
The only reason that we're not doing fully automated drone strikes is exactly because it is controversial and nobody wants to take the responsibility in case a fully automated drone mistakes a preschool for a terrorist compound.
Extremely common, actually. It's one of the major pitfalls and difficulties of doing multi-threaded programming and one of the hardest things for programmers new to multi-threaded design to learn how to solve. It can also be extremely difficult to debug, even for experienced programmers.
Improper garbage collection is another extremely common bug that becomes harder to find and debug with multi-threaded programming, and that can also lead to memory leaks.
There are time tested techniques to mitigate these issues and strategies to find and squash the bugs, but as you said, they can be extremely hard to reproduce while testing.
Windows Store has more mobile games that have been ported to Windows 10 than Steam or GoG. I've also seen a lot of "free" games that have huge advertising banners covering most of the screen. They're the same type of cheap and easy to make clones filled with advertisements and pay-to-win crapware that you'll find on any other mobile platform.
These aren't AAA titles, nor are they decent, older games with great gameplay like you'd find at Steam or GoG.
What you're talking about is a forward proxy. Forward proxy servers do this (and will even proxy SSL traffic).
In the whitepaper, they're actually talking about making a new protocol that measures the one way distance time and compares it to their database of network speeds and distances to determine your location. Their solution is an application-level solution, which depends upon a Forward Proxy to know about the protocol and spoof it correctly.
The problem with their solution is that network speeds are fluid and a computer with a problem (e.g. a local neighborhood node or a legitimately slow client that is delaying all traffic 20-30ms) can make their estimates wildly inaccurate. Even today, Cogent to Level 3 has a 197ms ping in LA. In the paper, they used average speeds for various known networks. This can be mitigated somewhat by measuring client traffic and only counting outliers (e.g. all traffic from a certain area being delayed the same, except for our rogue client) but it still doesn't mitigate the local computer problem.
A second problem with their solution is that it only measures distance - a server in Miami, Florida accepting data from a client in Seattle, Washington is 2732 mi and the same distance (roughly) as Lima, Peru. This means that a client in Lima should pretend to be from Seattle when they connect to their combo VPN/Forward Proxy in Miami. Satellite customers are will almost always have extremely high latency because of the round trip between Earth and the Satellite, even if they're legitimately in the correct area.
In addition, they were only able to make this accurate to about 400km, which means if you have a nearby beneficial country within that range, you can use a VPN in that country and they still won't know.
"355/113 -- Not the famous irrational number PI, but an incredible simulation!"