e_y_

Importantly, the non-uniformity may have a big impact on weather patterns, leading to an increase in hurricanes and flooding and other adverse effects.

It's close to zero over short distances (ignoring solar wind and LEO atmosphere), although you're still trying to dock with a moving target.

If you've played KSP or read about Gemini 4, the relative motion can be unintuitive due to orbital mechanics. The SpaceX docking simulator puts you right next to the ISS with low relative velocity -- as it would be in real life if everything went as planned -- but it would be much more challenging if you needed to do it manually from a greater distance and relative velocity.

From a gameplay perspective, there isn't much sense in a full N-body simulation. Players only care about their spacecraft, which is a restricted three-body problem (small spacecraft, massive gravitational bodies) outside of special cases like gravity tractors. And the simplified two-body SOI worked pretty well in practice.

In any case, the bigger gameplay problem tends to be the vehicle physics simulation, where you have hundreds+ parts interacting and not in the most stable fashion especially above 2x time warp. That's the part that seemed amazing when KSP first came out, moreso than the orbital simulation (although the solar system exploration clinched the overall experience).

Google had a short-lived experiment called Google Contributor, where you could pay a monthly subscription to hide AdSense ads. Each page view would subtract from your monthly balance and the leftovers would be refunded. I had mine set up to show cat photos instead.

https://en.wikipedia.org/wiki/Google_Contributor

It would not surprise me if "we can use your brand for advertising" is explicitly mentioned in the GrubHub/DoorDash contracts. I think the overall problem is that restaurants don't have much leverage; their main option is to refuse to cooperate.

Now the (gradually becoming less common) practice of auto-creating order pages for restaurants that didn't agree to be a partner, I would agree should be totally illegal, or at least needs a very large disclaimer that the restaurant is not involved.

Although I think the WHO has been way too cryptic talking about the issues surrounding antibodies and immunity, I think the real questions are really around degrees of immunity.

It might be that 80% of people get antibodies and immunity, but 20% don't. Or some people get antibodies but it doesn't prevent them from being a carrier. Or the immunity is only partial, etc. And then there's the ADE stuff which is theoretical but scary.

Where you can get into trouble is if the problem affects all your instances across the entire cluster. If all your organization's code is running in the same process, if any of that code has a severe memory leak or other serious issue, it could impact the stability of everything else.

Not to say that wouldn't happen for SPOF microservices (e.g. your auth servers), but the surface area is potentially larger for monoliths.

Some landlords charge application fees for dozens of applicants but they only run the credit check/screening for the first few. Also the amount of personal information requested is ridiculous.

I'd much rather use one of those systems where you get your own report from a reputable company and share the report id. Instead of paying an overpriced application fee to a bunch of places.

Even if you trust them on privacy or are willing to let them analyze your emails in exchange for some feature, there are very few companies that I trust to handle my email securely.

If a hacker gained access to my Gmail access tokens, they're a password reset link away from taking over most of my other online accounts and probably more than a few banking accounts. And then deleting the password reset emails.

Having worked for large and small companies (including ones that handle emails), security is always second (or third) compared to other business priorities. It takes a large effort to make sure everything is locked down and most companies don't have the skills, resources, and commitment to properly secure everything even if they nominally claim that security is important.

On top of the cost of the extra pointer lookup, you also run into cache coherency issues when dealing with threading. So then you need to use atomic ops or locks or cache flushing which makes it even more expensive.

Rust is better suited to deal with it since there's a similar issue with refcounting across threads, so you might be able to get away with doing it for objects that are exclusive to one thread.

You could always use a userspace implementation of WireGuard like https://blog.cloudflare.com/boringtun-userspace-wireguard-ru... . I imagine the advantage of the kernel module is good performance for normal users who are not trying to wring every last bit of performance out of their network setup.

Sure, you can climb in and out of a walled garden with a grappling hook, but that's not really the point.

It's been a while since I've taken high school biology, but the odds should be the same as the mother. Scottish-ness is not something that's limited to the X or Y chromosome.

Mitochondrial DNA will only come from your mother, but I don't think we're talking about that here.

Scott Manley's latest video ( https://www.youtube.com/watch?v=R-HOQrinzlY ) says the capsule should be able to survive in the water for at least 24 hours at minimum, but probably longer.

AI also has a lot of training data. Humans are highly adaptable but most of us have limited experience with situations like hydroplaning, sudden tire failure, etc.

Also self-driving cars could have better sensors that don't have blind spots, and the multitasking ability to monitor all of them at once.

Also frugal habits learned from agonizing over $100 and $10,000 spending sometimes trickle down to those $2 decisions. It becomes an instinct even if it doesn't make sense.

I have to give credit to Apple for taking power away from the telcos. They wanted to nickel and dime you for every app and feature. Getting even a dumb feature phone out the door required months of certification and the OS might get an update once in the device lifetime if at all.

Sometimes it takes an 800 lb gorilla (with fresh iPod $$$$$) to take on the other 800 lb gorillas, even if it mostly meant we spent the first 8 years or so paying ridiculous 2-year contracts for "subsidized" $700 phones.

It made sense in the early days when apps were $0.99 and credit cards charged approx $0.19 + 3% per transaction (Apple likely gets better rates, but just as an approximation).

There's still a lot of apps that fall in that range, but I'd agree with you that it's completely unfair for subscriptions and more expensive apps.

Steam is probably also overcharging with their 30% cut (once upon a time that was an amazing deal compared to boxed retail) and most games are $30+ so it's a pretty hefty chunk of change. I don't necessarily agree with the exclusivity tactics taken by Epic or EA/Ubisoft but having more diverse options for buying PC games is a good thing.

I think their argument is that they're providing you exposure through the App Store, so they deserve a referral fee for maintaining the App Store, reviewing apps, etc. Normally, user acquisition (getting a user to even think about installing your app the first time) is much more expensive than maintaining a subscription -- also why so many companies are pushing subscription models -- so Apple probably considers it to be worth more. There's also a higher risk of fraudulent purchases or refunds (and associated support costs) for the initial purchase than a subscription.

In the past, developers were prohibited from telling users that they could sign up cheaper on your website, allegedly to avoid user confusion; I think it was relaxed somewhat so I don't know if it's still the case.

Of course the main reason why they charge 30% for the first year is because they can, and the reason they charge 15% after that is because app/content developers have been starting to gripe about it (probably after realizing they need to make a profit and can't live entirely off VC money). It has little to no relation to how much it actually costs Apple. There's no justification for why it takes a year to get the reduced rate, instead of something like 2 months.

Apple's App Store didn't really have competition. The iPhone was pretty much an entirely new class of smartphone. The sheer volume of users compared to early smartphones meant you could sell an app for $1.99 and make loads of money, compared to Palm/WinMo apps that were more like $10+.

It took off because it was a good experience (one stop shopping) and because of the popularity of the iPhone. And of course it doesn't hurt that it was the only App Store for iOS.

I don't think we need to divide the market into specialized segments (iOS devices, luxury smartphone, etc) to make the case against Apple. They have somewhere around 50% of the global market in terms of smartphone revenue (not devices shipped).

For the App Store, which is what matters to developers, revenue was around $25 billion in the first half of 2019, vs $14 billion for Google Play Store.

It's not literally mono- but as the article notes, just having a significant share of the market (I would say 30% would be enough) allows companies to dictate prices, and iOS has more like 2/3rds of the revenue.

That's not even getting into all the restrictions that Apple puts on third-party developers, including categories of apps that you can't even make if you wanted to -- unless you're willing to sit out half the market, and assuming that Google doesn't do the same thing. As a software guy, I consider that a bigger deal than the % cut (which is not entirely unreasonable given how much of that goes to credit card fees for low-dollar-amount transactions)

If your WASM code doesn't change (isn't being downloaded at runtime from the Internet), then you could ahead-of-time compile it to native machine code (ARM/ARM64) and link it into your app.

It doesn't look like anyone's tried to do it for iOS but InNative has a compiler for Windows/Linux.

Also if accessibility is a requirement, you'll have to implement a fallback in DOM, although you're probably no longer optimizing for raw speed in that case.

If you're actually using OSX's word list, each "digit" could be one of ~235886 words, which is more than 17 bits of entropy or the equivalent of 2-3 normal keyboard characters (and a lot of luggage lock tumblers).

In practice few people are going to remember how to spell words like "aceanthrenequinone" correctly so the practical dictionary size is a lot smaller, but still in the tens of thousands of possible words. The xkcd comic says 44 bits for a 4-word combination of common words.

They can increase battery life by making the watch bigger and heavier. Don't laugh -- okay, do laugh, but it's surprising what people will put up with. We used to think that 6" phones were ridiculous.