Rather, don't use threading for the sake of parallelism in Python.
Threads in Python are mostly useful to avoid blocking:
- you need to make io calls and don't want to bring asyncio
- you need to process things in the background without blocking the main thread (e.g: zippping things while you use a GUI)
- you want to run a long process on a c-extension based data structure (they release the gil, so you get the perf boots), such as a numpy array or a pandas DF
This is for real, but this doesn't mean you can't use parallelism. Only that you can't use thread for them most of the time .
Parallelism strategies in Python usually revolve around using the multprocessing module, a c extension (numpy will release the gil, and hence all the science stack) or using a 3rd party tools (dask is pretty popular, and allow easy parallelism: https://dask.org/).
Even python's parallelism is subpar because objects passed across processes have to be pickled. This both takes time and limits the kinds of objects that can be sent across processes (no lambdas, for instance).
> For instance, a local cache of some values is basically useless when python is used as backend. Since there will be multiple processes handling the requests (in the same node), they don't share memory.
That's like claiming the ability to share JS ArrayBuffer's between workers supplants the need for the ability to share high level objects like a Map.
What I'm getting at is that JS had the exact same problem, and it offers the same ability for sharing blocks of raw memory. But the same pitfalls for any actual structured object.
Instead, we have to serialize/unserialize (creating a copy) from a separate worker, process, or disk source, it's performance is shite for objects of large size.
Message passing is not ideal for large pieces of data. Shared memory is hundreds of times faster.
I see what you mean. Does diskcache still have to do deserialization of the mapped data? Nested objects (large disparate heap pointer graphs) would suffer performance penalties.
We have been down this road before in 2000, so we know it leads to the total opposite of "make development simpler".
When IE6 became the engine mono culture, it was the best.
But then it stopped innovating, because it didn't need to. It also pushed moves that were only for the good of Micorosoft, since they had monopoly, trying to make the web a less open place.
It was a pain to develop for, a pain to debug, and a capricious master.
Google has shown they can be very naughty as soon as they got power over something.
Regularly, on imgur, you see a pic in interest for a celebrity, a rich person, a movie. It looks organic, but if you look closely, there are plenty of weird things about it. Then it disappears as suddenly as it arrived.
I believe that they sell the front page to PR firms that need to promote something in a way the people think themself came up with the hype.
It's probably the same for a lot of communities with a strong influence on trends, like popular sub reddits or hacker news.
There is no better ads than the one you don't see. There is no better slogan than the one you repeat to your friends as a catchphrase. And there is no better propaganda than the one based on ideas you thought you had by yourself.
I one time posted an album on Imgur of my hobby project. I was hoping it would do well on the niche subreddit it involved.
It did ok on reddit (100 upvotes) but a few thousands upvotes on Imgur and made the front page with hundreds of thousands of views. I was shocked since I didn't even know that was a thing. But my guess is popular with people who are on their phone a lot, are not as tech saavy, or international.
For the uninitiated, this is a meme reference to a clip from the TV show Arrested Development, popular on Imgur as a reaction to show support for someone else who expresses a sense of loneliness in their appreciation or affection.
It's so easy to absorb 'celebrity' gossip, I always wondered if it'd be possible to do the same with say science or maths, if it was presented in the same kind of format.
I think the hardest part is the rigour. Math and science build on concepts over time, and mastery is easier with more hands-on experience. Just presenting it to someone in a feed might be waaay too passive for absorption.
I recall being in high school (around 2013, 2014) and some of my classmates would browse imgur while slacking off from work. Not sure how big it is these days, but I think some people use it the same way you'd browse r/funny on reddit, or iFunny. Except there isn't really a topic, it's just images of whatever people think is interesting.
I scrolled through it for five minutes just now. Advice animals, rage-bait about politicians, political cartoons, cute animals—this is complete garbage.
I remember going on the front page of Imgur once a couple of years back and it seemed less entertaining and more rage-baity than now -- think I'll revisit that decision...
The way some of the replies talk about the front page of imgur (huge time sink, insightful, entertaining, keeps you in the loop) is the same way I'd talk about the FYP on tiktok.
I'm aware of one such company that uses Imgur like that and that deals with celebs. Imgur isn't their primary target, it's just a handy layer of abstraction away from the real target so the content can't TRULY be taken down on the target site. Plus, it shows you how many impressions you get for free. That way they can gather up their campaign image urls and views at the end of the contract and show hard results without the need for a fancy, paid analytics dashboard or campaign tracking system.
I don't know, but it's an unlikely mistake to make, and they have a lot of know how in the business. I expect them to know something we don't about the protocol, and setup things in a way that they get the money with plausible deniability.
It's not. This is like not subtle at all, there's a lot of real time monitoring on fees to decide the optimal one for your transactions. If this was not a mistake and it's really someone trying to hide the 23m transaction, they just didn't know what they were doing. A normal transfer would have been sneakier.
Threads in Python are mostly useful to avoid blocking:
- you need to make io calls and don't want to bring asyncio
- you need to process things in the background without blocking the main thread (e.g: zippping things while you use a GUI)
- you want to run a long process on a c-extension based data structure (they release the gil, so you get the perf boots), such as a numpy array or a pandas DF