Stories like this are sometimes more complicated than they appear. The infamous examples of $500 hammers, for example, were anti sparking hammers for working around flammables or munitions, hence requiring special materials, certification, and low production runs.

For this case, we have liquid hand soap dispensed by a pump. Pumps require a sealed vessel. Unlike commercial planes, military planes are required to anticipate prolonged operation with an unpressurized cabin. At max altitude of a C17, atmospheric pressure is only 20% of sea level. Off the shelf dispensers are unlikely to be designed to withstand that pressure difference, let alone function normally. In a high demand environment like aerospace, even apparently minor failures like an exploding soap container needs to be taken seriously due to the possibility of unexpected cascading failures. Why not use bar soap, then? Unfortunately this too has complications, like not being able to be securely mounted, liquid soaps having superior hygiene and cross contamination characteristics, and necessity for military standardized soap, sometimes designed for heavy metal, eg lead, which is likely if the cargo were munitions.

This unusual set of requirements unlikely to be seen outside the military context, so whether designed by Boeing or off the shelf the unit would likely have low quantity manufacturing runs, significantly increasing per unit costs. Combine that with the necessary certifications and the per unit costs balloon even further.

While a soap dispenser having an 80x markup seems absurd, it might be more reasonable than it seems at first glance. To be clear, there absolutely is military contractor graft. I just don't expect even a $10,000 soap dispenser would be a substantial proportion if it even within the C17.

The comments from that article are some of the most vitriolic I've ever seen on a technical issue. Goes to prove the maintainer's point though.

Some are good for a laugh though, like assertions that Rust in the kernel is a Microsoft sabotage op or LLVM is for grifters and thieves.

Key detail in the actual memo is that they're not using just an LLM. "Wallach anticipates proposals that include novel combinations of software analysis, such as static and dynamic analysis, and large language models."

They also are clearly aware of scope limitations. They explicitly call out some software, like entire kernels or pointer arithmetic heavy code, as being out of scope. They also seem to not anticipate 100% automation.

So with context, they seem open to any solutions to "how can we convert legacy C to Rust." Obviously LLMs and machine learning are attractive avenues of investigation, current models are demonstrably able to write some valid Rust and transliterate some code. I use them, they work more often than not for simpler tasks.

TL;DR: they want to accelerate converting C to Rust. LLMs and machine learning are some techniques they're investigating as components.

Well this is a tremendous step in the wrong direction. The economic problem is the ad supported model in the first place, no matter how it's run. This is the same thing Google does, they keep user data to themselves and sell the ad placement. So now Mozilla has the same economic incentives as Google. Unfathomably bad move.

The moment that shocked me was when printers, network cards, and even motherboard integrated Ethernet didn't work on Windows without driver downloads but Linux was plug and play. Full reversal of the situation.

Note the versions, none of the results give you the official operators page for the current version, 16. They give 9, which went EOL in 2021.

Codeberg is run off of donations, they have no service contract revenue. Nobody, much less a volunteer, wants to commit to a 5 or 10 year service plan like that, it's not sustainable for a small project from a non profit.

This is almost entirely misdirected. The success of Wikipedia is from its human structures, the technical structure is close to meaningless. To propose a serious alternative you'd have to approach it from a social direction, how are you going to build a moderation incentive structures that forces your ideal outcomes?

Federation isn't a magic bullet for moderation, alone it creates fractal moderation problems.

It runs great now. Most importantly, it supports extensions like ublock.

This is a classic problem for machine learning systems, sometimes called over fitting or memorization. By analogy, it's the difference between knowing how to do multiplication vs just memorizing the times tables. With enough training data and large enough storage AI can feign higher "intelligence", and that is demonstrably what's going on here. It's a spectrum as well. In theory, nearly identical recall is undesirable, and there are known ways of shifting away from that end of the spectrum. Literal AI 101 content.

Edit: I don't mean to say that machine learning as a technique has problems, I mean that implementations of machine learning can run into these problems. And no, I wouldn't describe these as being intelligent any more than a chess algorithm is intelligent. They just have a much more broad problem space and the natural language processing leads us to anthropomorphize it.

This was true maybe 10 years ago, nowadays Linux has better driver support than Windows. Printers, networking, input devices, everything I've tried is plug n play with Linux, Windows you gotta driver hunt.

People complaining about the promotion of FOSS on a FOSS powered site. Lemmy amd Mastodon are a golden opportunity to get people onboard with FOSS, no shit they're going to evangelize it. Not to mention the early adopters were obviously FOSS devs.