I'd pay more for being able to fumble about in the codebase and add exactly what I want.
Battery life is real.
Dead Comment
>extraordinary ability in the sciences, education, business or athletics
This illustrates the textbook argument for why mass surveillance is bad: these tools can quickly end up in the wrong hands.
Play silly games, win silly prizes.
Ironic indeed.
The incident reconstruction video a bit further down the article is well done:
There are plenty of cases where you want to manipulate an object but it's not guaranteed that it exists before your code is run. You get similar functionality with:
while not parentObj:FindFirstChild("childObj name") do wait() end
AFAIK, wait() is >= 1/30 of a second, if you wanted to be extra timely you'd instead run every heartbeat.
https://www.google.com/amp/s/www.msnbc.com/msnbc/amp/shows/t...
I read your comment carefully to see whether you've taken the GP's joke further, but alas :)
So assume it's a bit of an inaccurate phrasing.
EDIT: nope, the email itself seeks disclosure coordination etc. So yeah, oops.
I recently added it to a SaaS web app I'm working on, and the number of new sign ups went up 8x overnight. You don't necessarily have to create an account to use the minimal functionalty of our app, but after signing up you do get some perks, and we get a way to communicate with the user through email. So I think it can be beneficial for both parties.
What's the number if you adjust for quality of signups? E.g. how many people convert and how many people stay on and convert later.