it's thread safe on operations on the dict but not on the values. Same relates to other immutable structures like tuples. Lock will not help here cause unsafety comes from operation on value after value is obtained.
I don't say it's bad. It's commercialized experiense and it's cool if you love it. I just wouldn't treat it the same as devs fun of hiding things for valuable user who loves their product and I'm talking from dev prospective, not user.
I'm not trying to punish others, I just don't find it fun anymore with all respect to everyone who keeps up. Before it was naïve and simple, right now it just more complicated, often looks commercialized or not appropriate.
I'm against easter eggs, at least right now. First of all not of them are harmless, can you make sure that it wouldn't break anything important, would it tolerate race, religion, gender and after all of these would it remain fun? It's hard to be responsible and fun in the same time.
This will never happen. No matter what you think, sending you reject email is opening can of worms with no benefits for the company. You can start arguing, wasting their time and resources and one day all these emails can go public with harm to their reputation.
But you're not in control of fragment part. Server doesn't receive fragment for request, it's all managed completely by the browser. To handle this you need to do client side redirect with javascript.
I had only one problem, all certificates were outdated, so all https resources didn't work (like 99% of web). I had to download certificate updates to flash drive on another PC to install them, then all worked fine, I used outdated Firefox but it still good.
How is this different from GET arguments in the URL? I mean is this relates only to URL fragment, because javascript can parse URL parameters as well and any spam site can abuse it even with rewrite in the path part in the URL.
Well I meant other particles treated in the regular study of them. Because effect of pm10 and pm2.5 is studied. Do break pad particles somehow worse than usual.
Instincts often cheat you. I'm not saying that it's healthy but Does it really have any effect at all? What's the concentration of particles? How harful is it comparing to cooking or peeling onions? Do we need to care about it at all?
Clickbait. "The toxicity and health effects of brake wear particles are largely unknown". Is there any real harm found? What's the concentration of them close to the dangerous road? What's effect of them comparing to pm10 or pm2.5?
SQS has eventual consistency, you can get the same message twice on 2 different intances for example (which was often the case for my projects). I would rather suggest Amazon MQ.
PostgreSQL will be horizontaly scaling if you can avoid joins and index range locks. But the thing is you don't want to, or why do you need SQL database then. I found MongoDB good for cases when you need a lot of upserts, your data model is looks like document and you don't need joins. Like you store events data for further processing or collect stats or counters with tags/indexes.
Technically you could do any web requests which contain SQL in query paramaters even before with images/backgrounds and return data to the page. The thing is that it cannot work just between CSS and DB.
There is a logic error in this email. If this is not a request they cannot claim 45 days to response. So refernce to CCPA 1798.130 was clearly just to scary.