Fun fact, it's actually not just for paid apps, it's for free apps too!
I just said fuck it and listed my home address, cause if someone really wants to find me it's not like that info is actually hidden in other public records.
3,968 karma · joined February 18, 2011
Fun fact, it's actually not just for paid apps, it's for free apps too!
I just said fuck it and listed my home address, cause if someone really wants to find me it's not like that info is actually hidden in other public records.
Although BMW is making some nice EVs and they are selling more than they used to, the headline is misleading.
And if you're worried about the energy usage of crypto, wait until you hear about this AI thing...
I realize I'm a bit of an edge case. But also, ideally we could make PWAs that operate with similar data guarantees as native apps. That's kind of the idea of PWAs, that web apps should be able to mostly be the equivalent of native apps.
And it almost works, except for the data loss issue. Kind of sad. Cause there are so many other advantages of a PWA... like being able to target all platforms with one PWA is incredible. Having no gatekeepers to "approve" my app updates is incredible. But the cost is sometimes users lose all their data :)
This is true even if you use Google's own tool to wrap your PWA and put it in the Play Store, and even if you use the so-called "persistent storage API" to have users request their data not be deleted - still get random data loss, and it makes it very hard to maintain a 4+ star rating when there are a bunch of 1 star reviews about users losing all their data.
But on the plus side, random deletions also happen on Android!
Okay, how does that compare to what pharma companies spend? The article cites some unrelated numbers, doesn't actually compare.
A quick Google search says:
The average cost of phase 1, 2, and 3 clinical trials across therapeutic areas is around $4, 13, and 20 million respectively.
So... not really that different? What's the big deal here?
But all the premed students hated it lol
Besides that, every other bio course I ever took was just rote memorization (except ones taught in math/engineering departments). Bio 101 was maybe the hardest class I ever took because it was so damn boring to memorize all those random facts.
Code is Apache license, and you can do whatever you want with the output. If you want to be nice, lmk if you use it somewhere, I like seeing it in the wild!
What you see now is already after another contributor came through and redid all my artwork. You don't want to know what it looked like back before then lol
A nice thing about the current API is the face objects can be trivially serialized to JSON, which I need do in the application I originally wrote the library for.
Also the `display` function works with a DOM element as the first argument too, in which case you don't need to make up an ID. That's how I use it.
That being said, the API might not be perfect, but you should at least appreciate that it's been stable since v1 in 2015!
> Even if a tick is attached, it must have taken a blood meal to transmit Lyme disease. At least 36 to 48 hours of feeding is typically required for a tick to have fed and then transmit the bacterium that causes Lyme disease.
Results of clinical trials (if successful) can then be used in ads, but that would not be R&D expenditure.
I remember as a TA I caught a student cheating (very blatant, included a paper trail with obvious lying) and the professor was like "eh, give him an 8/10 instead of a 10/10". That was the attitude 15 years ago, I can't imagine what it's like now if trends have continued..
And currently there are also other situations where browsers will delete your data, in addition to low disk space and the weird iOS usage requirements.
1. That heuristic is not just in Safari, it's in Chrome too. Firefox is the only one with a normal permission dialog. And the heuristic is really confusing for users! They come to me and say "how can I stop my data from being deleted?" and I have no answer if the heuristic says they can't enable persistent storage.
2. It only helps with eviction (deleting data due to low disk space), not other scenarios where data may be deleted. Such as clearing the "browser cache" without realizing what that implies, which may even be done automatically or through some third party app.
3. I have a place in my app settings page where users can see their persistent storage setting and also enable it if they want. I have many reports of users who enable it, then check back some time later, and somehow it's disabled. So the persistent data setting seems to not be persistent.
It kind of makes sense, given the constraints the browser devs have given themselves. Since there's no way for users to see/manage these OPFS files directly, there is no good alternative except automatically deleting stuff if disk space is low.
What would really be nice would be if we could just create normal files and let users control them, but that doesn't seem to be in the cards. And it sucks. The #1 question I get for my PWA is "how do I stop it from sometimes deleting all my data?" and there's really no good answer.