They made ChromeOS because a separate team developed it independently of Android and the company didn't have the good sense to kill/combine efforts. 15 years later and the combination of the two is still half assed.

As far as regimes opposed to the US are concerned, maybe they'll start poisoning AI and open source data with deliberately false and misleading information because the intelligence are too stupid to do some due diligence. Maybe that's what happened here, or the AI just hallucinated something. I doubt it would be hard to drop some poisoned information in the wild and have missiles hit targets with nothing of strategic value in them.

I think ChromeOS is a good OS but it's suited to casual consumption and education. It should be running on cheap laptops running mobile processors.

Google also hasn't helped itself by having ChromeOS *and* Android and trying to mush them together so badly. I have no idea if "Googlebook" is where the two finally become the one, or not, but the company must have wasted hundreds of millions in development, customer confusion / dissatisfaction by having this disconnect.

You've looked at them. Now try changing them and understand what brittle means.

A search on "unsafe" in uutils shows about ~70 usages (excluding tests, logging) and they're mainly calls out to kernel / API via libc. e.g. calling libc::signal(). The exception is some calls to a rust lib that gets/sets environment variables whose functions are marked unsafe because they're process global, not thread safe.

KDE still hasn't figured out that sometimes less is more. It wants to be a Windows knockoff but throws more buttons and menus in the face of users, introduces too much unforgiving behaviour, lacks discoverability, has too many settings, has little consistency between core applications and expends little effort to ever to address these issues. It's a dog's dinner of a desktop.

And when you read KDE's human interface guidelines it becomes clear why it's such a mess. The HIG reads like a developer free-for-all. It points at existing apps as precedent, or mentions some class or another, or waffles into wordy sections. But what it doesn't do is layout a clear vision of what KDE UX should be including illustrative examples, usage patterns and so forth. Some of the HIG is hilariously stupid, such as explicitly refusing concepts like basic & advanced settings. No wonder its a kitchen sink.

Compare to the GNOME HIG if you want to see what a HIG should be. And no that doesn't mean KDE needs to "dumb down" to become GNOME but it needs to lay out its stall in a way that developers can follow and its UX needs to be designed on sound principles. e.g. KDE has Kirigami to produce modern usage patterns, so write the HIG around that. Make it fit for purpose and maybe some of that kitchen sink mentality will go away.

And he posts moronic shit like this out on a daily basis. The end of his presidency can't come soon enough. Hopefully he is wiped out in the mid terms to limit the amount of stupidity he can get away with and increase the chances of his removal from office.

Exactly. It's just an arrogant and dumb statement that ignores reality.

This has to be one of the most idiotic statements I've read in some time. Every programmer, including you, writes bugs. It's the height of arrogance to pretend this is not true or that you can blame programmers because bugs are a fact in every piece of code ever written. The sane response would be to acknowledge that and the benefit of using a language not actively assisting in causing bugs.

Secondly, no Rust is not going to stop programmers making all bugs. But it will stop a whole raft of bugs caused by using C (and C++) that are easy to find in the CVE database. And nobody uses "unsafe" everywhere. But even if they did Rust's unsafe mode is still safer than C. The unsafe keyword unlocks some mutation and pointer functions but the compiler is still doing lifetime and borrowing checks. In fact, the only reason someone would use "unsafe" is interact with C, the OS or metal. There is literally no reason to use it when Rust is talking to Rust. It's a pain in the ass to use and very conspicuous which is the whole point.

Busybox, Toybox and others. The vast majority of docker images running in the wild probably aren't even using coreutils because their aim is small containers with minimalist userland with some even going distroless. They don't even use glibc, using something like musl instead.

I think for a general purpose Linux dist you'd definitely need coreutils or a drop-in replacement. I think coreutils has a lot of very esoteric features, which uutils have copied so even so, there is merit in examining these and deprecating or entirely removing which no longer serve a purpose.

I think Ubuntu (and other's desire) to remove coreutils is precisely because coreutils is old, brittle and written in an unsafe language. So they've chosen to modernize the code base, attract new developers while still maintaining strict compatibility. And since uutils is MIT instead of GPLv3, and far more portable between operating systems it may encourage adoption elsewhere, e.g. Microsoft already have build for example.

That said, rewriting code always carries risk and uutils has its own set of bugs which have been uncovered and need fixing. There is a "if it isn't broke don't fix it" mantra but I suppose it depends on the definition of broke - if development is moribund then that could be considered an issue too.

It's worth noting that coreutils have derived benefit from the exercise too. The extensive test suite for uutils has uncovered bugs in coreutils and improved the overall code coverage. So even if people don't want to switch (even though they're functionally interchangeable), the existing package has derived benefit too.

Yes it matters assuming Valve wants to drive sales and make the device popular & desirable beyond a small % of people who want to drop $1200 to play a golf sim.

Oculus Quest made a lot of strides with portability and untethered game play but the Frame looks like more of the same. It's good it plays games standalone and streaming too, but so did the Quest. It still doesn't solve the fundamental issue with VR that it is a niche and it still hasn't found a killer game to sell the tech. If Valve released a battle royale or an MMO and gave it away for free then it might incentivize people to buy and use the thing as a casual device. Think quests, skins, clan bases, hang out areas etc. Something that people want to visit and re-visit and which grows organically.

Oculus had this chance too and managed to squeeze out the most boring, group studied, micromanaged, turd in the form of Horizon Worlds. It didn't even stink, it it was so bland and pointless it smelt of nothing. But Valve could pull it off if they wanted.

Sam practiced "effective altruism" which is a pseudo-philosophy for being a selfish, thieving cunt - that dressing up a self-dealing with the odd charitable donation somehow serves the greater good.

But ironically effective altruism actually worked in this case. Being a selfish, thieving cunt landed him in prison and arguably the greater good was served. It needs to happen more often.

Anyone who types "fiji hotel" can be shown a map of fiji with hotels marked on it. If they click on a marker, they can be shown as the first result the hotel's own website and rates before any other site's. If there are any sponsored hotels, or booking sites parasitizing from the search, including Google's own affiliate deals, then they also can be shown below the true result. This is not rocket science.