2,311 karma · joined July 31, 2017
If I work 42 hours/week, how many minutes is that per year?
I've downloaded 4.91GB in the last minute, what's that in Mbps? How long will it take to download a 76GB game?
This AWS feature costs $0.045/hour, how much is that per month?
This guy I read about traveled 58,000km in 27 years, what's his average speed in m/s?
How much would a 10cm sphere of gold be worth in GBP?
If a 36 inch pipeline can deliver 25580 acre-feet of water in a year, how fast is the water flowing in m/s?
I don't think it's a bug in the javascript either, it seems intentional that it only fills in the x's automatically if you've filled in the squares for that row/column.
Let's say that I magically manage to find a private key whose public key has a chosen prefix that is the entire length of the key - i.e. the entire key is vanity. Something like myveryveryveryverylongvanitypublickey. Is that equivalent to a 0 length public key in terms of security? I'd say obviously not - there is still no way to get started when it comes to finding the private key.
Viewing this site: 40 (0.0000005%)
My reasoning is that the full public key could be seen as a 256 bit fixed prefix, but knowing the public key is meant to give no information about the private key by design.
I really enjoy precision, and that's what vim provides. It's the same reason I'd much rather play an FPS video game with a mouse and keyboard, than an analog control stick. And the same reason I hate doing anything important on a touch screen.
It really is the modal editing style that's the main draw. Someone who edits frequently should find vim more convenient, not less, but it does require a lot of time to learn all the available commands and burn them into your muscle memory.
Ironically one of the things that's unique to humans is our ability to feel guilty about our impact on the environment.
It’s not a moral judgement, that’s just how humans are wired. The lows make the highs higher.
This sounds very difficult to review to be honest. At a minimum unrelated changes should be in their own pull request (U and V in your example).
> For example, if you observe that it's silly for people to move from iPhones to Android phones because they think that Apple is engaging in nefarious planned obsolescence when Android devices generally become obsolete more quickly, due to a combination of iPhones getting updates for longer and iPhones being faster at every price point they compete at, allowing the phone to be used on bloated sites for longer, you can't really make money off of this observation.