Python is culling stuff all the time, but that doesn't warrant a major version jump.
You are probably right about Pythons careful approach of when to ship v4, but for the wrong reasons. Python 3 was necessary not for the removal of functions, but because of the syntax changes e.g., moving print from a statement to a method.
In-general it seems that Rust proponents want ease and modernity to replace the ability to do the same in C better, with more control and intent, and with better results.
Rust is less tight. That’s fine for an application, but the kernel is used by everyone who uses Linux.
Rustians disparage C because it doesn’t have Rust behavior.
I don't think C should be disparaged at all. Just because I prefer torx screws doesn't mean phillips screws were a horrible idea. They were brilliantly simple and enormously effective. I can't think of a single situation in which I wouldn't prefer torx, but torx wasn't an option historically and phillips was not the wrong decision at the time. Times change.
If you need idempotent db writes, then use something like Temporal. You can't really blame Celery for not having that because that is not what Celery aims to be.
With Temporal, your activity logic still needs to ensure idempotency e.g. by checking if an event id / idempotency key exists in a table. It's still at-least-once delivery. Temporal does make it easy to mint an idempotency key by concatenating workflow run id and activity id, if you don't have a one provided client-side.
Temporal requires a lot more setup than setting up a Redis instance though. That's the only problem with it. And I find the Python API a bit more difficult to grasp. But otherwise a solid piece of technology.
All software is vulnerable, so what you're saying is not true. The only reason the products you listed seem more vulnerable is because they are focused by malicious actors due to their popularity and hence, also more often in the news.
Actually, the more the popularity or criticality of a product or system, the higher the likelihood that malicious actors may target it. So any such product or system needs adequate security measures and IT staff to protect and maintain it.
That's why iPhones and Androids get jailbroken (as they dominate the mobile OS market), that's why Windows has max viruses and worms to infect it (since it is on max number of PCs worldwide), that's why even Linux is being hacked/targeted (these days via malicious github packages, because Linux is becoming more popular, especially due to Valve's pushing SteamOS for Linux gaming).
No, I think you’ll find certain legacy corporations have terrible codebases and very little incentive to fix it, because why fix what makes money and has no liability?
Naive people in corporations think Linux and other FOSS (Free & Open Source Software) can save them from Microsoft, Oracle, etc. woes.
But the reality is that corporates have very less incentive to migrate to open-source alternatives. Because it would mean negligible/no support, less work and hence less staffing (senior management have to justify the staffing headcount somehow).
FOSS solutions typically don't get proper (or in some cases, not even any) support from the solution makers (developer company/persons).
Corporates thrive internally on liability (they always want to blame someone, easiest target are their IT staff), and thrive externally by trying to avoid liability.
e.g., Big Pharma (Pfizer, sold hundreds of millions of COVID vaccines worldwide, after ensuring those target countries (including their own country) first gave them complete indemnity from any liability for the negative effects or lack of efficacy of the vaccines.
reply