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.
HN user
varelaz
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.
Is it just a marketing tool of a mega-corp which tries to look nicer and engage you more?
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.
It doesn't require AI to solve the game. It's possible to do with probabilistic theory, dynamic programming and game theory (minimax)
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.
This video somehow looks even more interesting than the pre-print of the article
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?
That's reply to Amazon abuse of MongoDB (DocumentDB)
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.
All operations related to a single document are ACID. MongoDB supports multi-document transactions, but with higher performance cost. https://www.mongodb.com/docs/manual/core/transactions/
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.
AFAIK on space stations right now CO2 is just removed, oxygen is restored from water, but I could be wrong.
Technically moon has enough oxygen to sustain 8B for indefinite time, while you have energy to convert it. If you're going to use oxygen from rocks, why not use it from CO2 that we produce
Codecs are algorithms how to generate B and P frames. I frames are just jpegs. Yes, codecs can split video differently, but in case of the same split the same frame will be encoded the same way. In most cases key frame frequency is just a number. Some formats like HLS cannot work with variable key frame frequency at all. Why it matters, because different version of the same codec can replay the same video differently for B and P (no guarantee), but not I frames. So I frames are the most stable.
I don't know if it makes sense to query hamming distance for hash. Closest hashes don't guarantee closest images at all. You can check for amount of parts matching by query like: select video_id from video_hashes where hash in (...) group by video_id order by count(distinct hash) desc limit 10
technically it can be fast since selection on hash could be very narrow. You need only index by hash, video_id.
I used similar approach for video hashing. Instead of interval I used key frames with ffmpeg, then you don't depend on codec. Also didn't rescale but took hash of every frame. For youtube I found that it still produces different hashes sometimes.
edit: to get only keyframes use select=eq(pict_type,I)
Barchart is basically your percentiles (just more of them) so why not show it? Bars and whiskers could be more complicated for them but still the same sort of data
Percentiles for sure are better than average if you want to explore distribution: there are several percentiles comparing to single average. However median is harder to use if you want to do calculations based on this metric. For example distribution of sample median could be a problem, if you want to understand confidence interval for it for example.
Brexit was a way to leave EU by country which wants this. But Hungary doesn't want to leave, they want all benefits and keep doing what they want. EU has very little power to punish Hungary. To do something serious all countries should vote for this, but Hungary and Poland have agreement on protection of each other. So EU is kind of hostage there.
I think we need to treat such threats as a rear disease which could happen whenever you ready or not. We need to check for it but be prepared to have it anyway.
Industry should start thinking more about insurance, negotiation and investigation services.
The thing is that these bare numbers say nothing without "in compare with". There should be comparison with other job types or historical at least to make certain assumptions. Also for such burnouts developers often have some type of compensation, while other jobs rather not. Compare for example developers problems with Amazon devilery service drivers problems with toilets. A lot of jobs just luck minimal comfort and compesations and hardly can complain.