browda

I was logged-in -- and composing a message -- a few minutes ago. First there was that cannot reach backup server message followed by a bunch (don't you just love technical jargon?) of messages saying "Could not..." and then lost the message when the site itself apparently went down. (Well, Firefox was seriously unhappy...) I was ready to blame my ISP again but no, this one is on proton mail. (It's pingable and traceroute is happy.)

I'm really glad that we didn't move our business over...

Yes, the final example code reads reasonably nicely, but alas -- unless ConcurrentHashMap.merge() has been rewritten since Java 8 time -- it is definitely not as performant as the author appears to think it is since the actions will be contained in a fairly long synchronized block. This is not to say the code is bad, but you can't get around that.

Somewhat surprisingly, the code the author pooh-poohs is actually more performant (although it's better if the test is for the presence of the key rather than the "putIfPresent/computeIfAbsent combination) because the JVM will properly optimize a membership test (in keyset) and the use of a ternary expression makes the action clear.

Premise 5: My expectation is that you don't have anything close to what I would expect -- especially for an 80% share -- so why should I waste my time with you?

You’re not alone (http://babeingeekland.blogspot.com/2018/06/an-open-letter-to...) but if you are persistent and happen to have a computer that Google knows, you should be able to recover.