I do hope it's going to be capable enough to be plugged into CI/CD to discover that the top-talent today made another obvious XSS, SQLi or other trivial issue that just created a 0-day. Even a few of those cyber-models, so they verify each other. I do hope it's going to be trained on all prior issues, like the one with xz, or Axios, and be vigilant against these things.

GECOS in 1962, and UNIX in '70s had them as well, and nobody threatened to kill their creators.

Having a field in a database is not equal to mandatory data collection. Let me remind of data that /etc/passwd allows to store on even an OS without systemd:

- User's full name (or application name, if the account is for a program)

- Building and room number or contact person

- Office telephone number

- Home telephone number

- Any other contact information (pager number, fax, external e-mail address, etc.)

Nah, I don't think so. It sucks at that.

We'll be certainly less performant and less capable, but the data will continue to flow and business processes will proceed. If cloud data centers are destroyed, everything that's important to sustain us stops and we die.

I am yet to see how a one-legged business model with just a single product (that is not crude oil), without a plan and money is going to become sustainable. Oh yeah, maybe they'll finally make money on those autonomous lethal weapons. That sounds the easiest.

Did AMD engineers or seasoned hardware experts from server vendor assist in this implementation?

Were the "Nodes Per Socket", "CCX as NUMA", "Last Level Cache as NUMA" settings tested/optimized? I don't see them mentioned in the article. They can make A LOT of difference for different workloads, and there's no single setting/single recommendation that would fit all scenarios.

"The locality of cores, memory, and IO hub/devices in a NUMA-based system is an important factor when tuning for performance” - „AMD EPYC 9005 Processor Architecture Overview” page 7

What was the RAM configuration? 12 DIMM modules (optimal) or 24 (suboptimal)?

Was the virtualization involved? If so, how was it configured? How does bare metal performance compare to virtualized system for this specific code?

So many opportunities to explore not mentioned in the text.

Aren't there static analyzers in widespread use that would catch these?

I needed recently to make an exe that would work on anything from 32-bit Windows 95 up to and including Windows 11 (to accommodate some old machines on production lines), and the only language that made that easily achievable was FreePascal. I think it can also handle the older Windows NT if that is a requirement. There are lots of architectures supported with a single code base.

But for many the Pascal language is just to be laughed upon. Well, I make fast money using it and laugh from JavaScript.

https://www.phoronix.com/review/linux-70-filesystems

At most... Think 10x rather than 0.1x or 1x.