One node's ipmitool sensor report (and self-monitoring PSU, so grain of salt, but my UPS side monitoring tracks closely), reports 250-300w average power use. This though, mind you is for running 22 spinning disks, 2 SAS/SATA SSDs, and 4 NVME ssds, and 768GB of DDR4.

Mid-gen 2015ish Xeons were not great at power reduction, but if you are pegging the cores, they were never particularly slow, and they did have lots of PCIe lanes. This boils down to the CPU/mobo itself not being that big a cost floor, especially if you have high utilization rates.

As a comparison, my main desktop development machine, running a Threadripper 9970X, 128GB of DDR5, a RDNA4 GPU, and a small pile of NVME drives has a power floor of roughly 250W. Some CPU centric workloads you'll definitely lose out on on the older gens of machines, but they are by no means impractical.

Maybe for a desktop usecase they are absolutely suboptimal nowadays, but for a lot of realworld usecases I would say they're still relevant.

---

Like the author posts for the LLM usecase, I think optimizing the hardware choice to the application and not leaving levers unpulled is a big key, especially considering how wide a variety of bandwidth/power draw/peak frequency/corecount SKUs exist in the Xeon lines. Without knowing what you intend to run and fitting the correct processor to it, you will end up with a disappointingly poor environment fit.

Combine that with the character of practically every law written involving data privacy, use, IP, and associated regulation of activity around these since the 1990s. It becomes painfully clear that the interests of private citizens have not had a seat at the table, and the Constitution has been taken as an inconvenience to bypass, not a guiding document.

In the modern landscape, where practically every mainstream (and most of the non mainstream even) platform has extensive policies and applies them in a manner that's equivalent to editorial control, they are no longer a common carrier, they are a publisher.

Should that exemption and safe harbor be expanded to all publishers? If no, do you really want the Government picking and choosing favorites? Either way you choose, I believe there will be many first and further order implications.

You can either get Congress to modify the definition, or you could try to get a case through the courts to clarify its interpretation. As one of those indirect implications, I am actually not sure which one would be more of a footgun.

You could likely improve gobee to use tinygo's packages directly, instead of transpiling to C and calling into clang, and the licenses of the two projects look compatible. You'll still need to deal with defining a subset to pass the verifier, of course.

---

From the README:

> Replace clang. clang's BPF backend gives us CO-RE, BTF, and verifier-friendly codegen for free. Reimplementing that costs years and gains nothing.

The primary gotcha you may hit if you try this is how much of the BPF features are implemented by clang, and how much is instead implemented in core LLVM. Even with a LLVM sitting next door you could pull out, the harnesses may not exist independent of clang, but I have not looked THAT deep.

Yes, I know the author's writeup then goes on to say that it is not a libc with a pile of questionable justfication. This is a custom runtime, in a single header no less, which is admittedly impressive, especially considering it provides runtime and thread safety primitives. This does not rise to the level of claiming the idea of a 'standard libarary' though, IMO. In that, I think the author misses the point.

Maybe early/MVP product engineers should know better, but CFs own education materials do not teach you to expect that.

The CVE system arose as something of a mediating factor to enable coordinated disclosure of discovered issues and make something of a standard that vendors could point to and they they were being responsive, vs wondering if a random exposure on Bugtraq in the 90s would ruin your week.

If it no longer aids in that, then it has ceased to be a system useful for its original purpose, and it would be foolish to continue to feed it resources. It probably doesn't help that all sides viciously game the CVE system these days.

That's still a good question, though. Do any of them have anything more substantial than 'anonymous' sources, or even their own anonymous sources not linked to the breaking article's?

I am generally suspicious when anonymous sources quoted these days, but I am rather more suspicious of reports that only come from a single source and get repeated in multiple outlets more or less immediately.

I know there is some amount of synchronicity induced by syndicated news feed outlets like AP, but like many single source/anonymous stories, this reads to me like some 'suggested copy' was sent out to some reporters or outlets ahead of time.

Anonymous sources are important for the integrity of reporting, but it must also be recognized that they are essentially non-authenticatable information.

The author of the secondary source I see most mainstream sources quoting (Mattia Ferraresi) has also come out and said people are stretching and misrepresenting what he wrote: https://xcancel.com/mattiaferraresi/status/20424925662396866...

There is at least one outlet that appears to have asked the both Pentagon and the Church what was up and both parties told them the meeting was overstated as well: https://www.pillarcatholic.com/p/nuncios-pentagon-meeting-wa...

https://xcancel.com/BrianBurchUSA/status/2042307511504519366

I'm going to put this in the "Extraordinary claims require extraordinary proof" bin.