Human foveala, the central part of your vision, has on average about one cone every 30 arcseconds, but resolution of 20 arcseconds is still quite common because the variety in cone density is quite high. So someone with good vision, maybe someone who would naturally be inclined to work in graphics, would need over 430ppi at 2 feet, or 290 at 3 feet. This screen seems to be perfect for someone with good vision at 3 feet, if you place the screen closer you would need even higher resolution.
But the past didn't use ASCII as such, but extended character sets, or multiple characters sets, which did allow for Russian, German, etc. text interfaces.
Someone who is good at learning can just learn for free, only someone who is not confident in their abilities would pay for the name of a college attached to a degree (with likely less actual skills transferred, because paid colleges depend on throughput, not on results). The actually good students at paid colleges are the ones who got a academic scholarship, i.e. free like community college.
As mentioned it works for valid short hashes, if there are multiple commits with those first 5 characters then you need to make it more specific by bruteforcing, appending a 2, 4, 7, or 8 will lead to a valid commit.
It seems like the first variant is overly complicated. When you write about set theory you should be able to figure out that you don't have to rely on the effects of the union operator, the result you want is a simple difference with previous levels of the recursive cte, or a terminal query that groups by the table and shows the minimum level
I suspect this is also to provide a legal framework to automatically remove malware from victim's computers, as has been done before by Dutch authorities without any law permitting such actions, and removing malware is obviously good for society.
And of course it can also be used for gaining entry to hackers systems by infiltrating c&c servers on third party hardware, which also had been done before by Dutch authorities without any existing legal framework to allow this.
> Also had a 2:1 desktop:laptop ratio -- would have guessed more laptops. (The author questions how Plausible determined this.)
For my personal analytics without third party dependencies for privacy reasons I use the fact that Javascript allows access to the battery API, so a laptop uses a desktop browser, with a desktop resolution and zoom, while still having a battery.
You could use the name of the foreign key, together with FKs namespaced to the table they are on would allow very expressive joining, and the query might even survive schema changes. ORMs tend to work like this.
A modern phone with a 5 Ah ( ~ 18.5 Wh) battery can run for many hours streaming to a builtin screen, meaning it uses far less (anything over 45 minutes is more energy efficient) than a chromecast despite doing more. Same scenario with a laptop with a 60 Wh battery, which can also run a long time in idle, and even while streaming, and is able to resume from sleep in a second. Running more than 2.5 hours on battery means it's more energy efficient than a Chromecast.
When you are casting your smartphone on a built-in tv, the TV is doing all the work (downloading and decoding the signal). Your phone is just a fancy remote control.
The Chromecast is downloading the video and sending it to the TV on the contrary.
