It's not anywhere near one step away. Designing the peptides and getting one or more candidates is the easy part. The next steps are the hard ones, the ones that make pharmaceutical chemists and drug researchers cry:

• Phase I trials to see if it even works as claimed. Expect a 95+% failure rate here. Note that this is where you're going to see the best results for your drug candidate, things never improve from here. The best you can hope for is that they don't get any worse. So if you don't get strong results here you're probably wasting your money.
• Phase II trials to determine the best dosage and pharmacokinetics. Again expect a 95+% failure rate here, and results showing less effectiveness than shown in Phase I.
• Phase III trials to determine behavior in a large sample representative of the target population. Expect a failure rate upwards of 99% here, and a major drop-off in effectiveness. This is where toxicity and serious negative side effects show up, and those can kill your trial dead even if your candidate is working.

Getting through this process will take multiple tries and years of work, assuming you succeed at all. There's a reason they say that the clinic (clinical trials) is where drug candidates go to die.

"the manager" lol you sound like you work at a gas station

True, misinformation coming from "trusted" sources is much more damaging than some idiot with a blog posting nonsense, simply by the fact that it's framed as something trusted by so many others.

False dichotomy. Nobody here is talking about an idiot with a blog posting nonsense.

False information coming from sources that "look" trustable but are actually not are very damaging - on purpose, as that is literally the intent.

Incomplete/biased information from trustable sources that are not deliberately attempting to mislead (as in sources that adhere to the ethics of not presenting information that is factually false, even if the picture is not "complete" as you suggest) is a slight wrong, and has existed since the dawn of the printed word - it's editorial in nature - but its effects on creating social problems pales in comparison to weaponized disinformation campaigns.

Hand-wringing about the later as if it's some kind of new thing, or something most people don't know about strikes me as super naive. The insidiousness of the former is simply that people don't appreciate the scale to which it's happening.

No, but treating two wrongs as the same degree of wrongness is pretty dumb.

Or just shit like this: https://www.wsj.com/business/m...

yes yes "i'm old and cranky"

That's why everything running in the cloud runs in containers on a cluster (Kubernetes or similar). If a physical server dies, the cluster control software just drops that server from the cluster. Load management then automatically moves the containers to the remaining servers in the pool. When enough servers are dead they send a tech and a truckload of replacements out. Same for storage: everything's on RAID arrays and as physical SSDs die the array drops that drive and keeps on going with no data loss. Once enough drives in the bay are dead they send someone to swap them out and the RAID controller takes care of initializing them and restoring data from the existing drives as required. It's not uncommon for 30% of the capacity to be out-of-service before replacements are ordered.

They still have to catch up to IBM's old mainframes though. Those you could go in during peak business hours and start pulling and replacing CPUs and memory modules and I/O controllers while everything was live and not disrupt anything.

The language part, true. The problem is dependencies. Any time you upgrade, especially if you're jumping a large number of versions, you're going to have packages your code uses needing upgrades too. Those package upgrades will usually require code changes to accommodate. Some of those changes will require refactoring to handle structural changes needed for things to work right. That is usually where you end up down a rabbit-hole.

I'd prioritize updating Java 8 applications to Java 11 first. Those are going to be the hardest to bring up-to-date with Java 25 (latest LTS), bringing them up to Java 11 buys the most time. Then upgrade to Java 25 starting with Java 17 applications, then Java 21, then Java 11.

Remember that Java 25 will end support in 2033, so plan on starting your upgrade from Java 25 to the next LTS version basically as soon as your last upgrades to Java 25 are done.

Yes. The construction jobs are very short-term, and once built the data centers bring huge costs (financial and otherwise) while contributing only a handful of permanent jobs. Remember, these are lights-out hands-off facilities. They'll employ a handful of security guards and maintenance workers, the rest will all be handled remotely from Malaysia or the like.

True up to a point, and governments are past that point. They can in fact tell companies what formats the government will accept and generate and companies can't afford to just ignore that. And that's actually the first step towards sovereignty: dictate formats that aren't controlled by hostile entities. So, start by declaring the ODF formats the official government standard formats. You'll accept documents in other formats, but you can't guarantee they'll be correctly rendered on your end and you won't put any effort into trying to clean up Word and other non-standard format documents. If they're bad or unreadable or whatever, they'll be rejected and it's on the sender to fix the problem. When you send documents you'll only send them in ODF format, no others, and it's on the receiver to be able to read them.

Internally you standardize on something like LibreOffice that natively handles ODF formats. Anyone else can use anything they want as long as it can handle ODF. Word, BTW, actually does a decent job of handling ODF. Inertia may be a thing, but remember that governments have a lot more mass behind them than private companies. If the government insists and won't budge, any company that needs to do business with the government will slowly come around.

Or more like "cloud infrastructure running within physical and legal jurisdiction of the EU is running locally to the EU" if you prefer .. if it's software they've written, running on hardware within the EU's physical and legal reach, voila, "sovereignty".

"The only way to ensure sovereignty and control is with software running locally with NO cloud dependency."

They're not talking about personal sovereignty. Cloud infrastructure an organization owns is "running locally" to that organization.

that particular amendment was voted down, bozo - the system works, no hand wringing required

doesn't mean hate speech doesn't exist

So now NHS has nearly half a million headaches. I'm not sure this is an improvement.