>What is the equivalent of the Java 𝚜𝚢𝚗𝚌𝚑𝚛𝚘𝚗𝚒𝚣𝚎𝚍 keyword?

The closest equivalent would be using a lock, semaphore or barrier object with a context manager .i.e. the with keyword.

Making the locking and unlocking of data automatically managed for you.

I generally try to stick to a deque in Python if I am doing anything concurrent.

A second button on your website beside the "RSS" button that says "RSS but with fancy features." when you click on it, it is the same content on your blog but via a substack newsletter.

I believe that has all the features you listed as wants.

I am kind of half joking but people do have very specific ways they want to consume content even if it is the same content.

How hard it is to come up with good ideas is greatly underestimated.

Here is a paper on A/B testing that the Bing search team conducted under Microsoft.

https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3171224

Hidden in there in a distribution graph is that 2% of the ideas that were A/B tested resulted in 74.8% of the improvements.

Now you can ask yourself what are they considering improvements which is a valid answer but that really struck me.

Section 4.3 Figure 3a.

I read the article and I have read a lot of comments here.

I couldn't find a single reference to where the data set came from that trained the model they are using to do facial recognition.

Someone did theorize that it could be taken from a hypothetical law firm website but IIRC a single photo of someone is not good enough to reliably train a model that is not overfit.

This is great, thank you for posting it.

Why is it always telegram involved with these scams?

Why do they bother with the javascript obfuscation when it can be easily seen what they are doing in the network tab?

This seems like the most traditional and respectful of REST way to go.

You could try a HATEOAS approach if you want to get a bit more fancy.

https://restfulapi.net/hateoas/

If you are following REST strictly there should be only objects, actions and verbs.

> If you are following REST strictly there should be only objects, actions and verbs.

Not quite. That would be a resource-based architectures much like REST, but REST dials requirements a notch higher, with stuff like adding capabiliy-discovering semantics to resources such as navigation links to related resources and operations to express it's state and state-changed, in the form of HATEOAS.

cough https://news.ycombinator.com/item?id=32487190

>Seems like in order to practise their art, they need a reliable but remedial job to pay the bills. Unfortunately, the nature of that kind of work is energy depleting zapping any creative juices needed for the concentration and initiative to produce content.

I'd highly recommend quitting your job. 10/10 experience.

Just make sure to check your funds war chest before hand.

>I thought all those examples were awesome.

They are great examples. Great examples of what not to do.

The only use case I can think of is meta programming which most people don't need.