but it's a 10.0 in our hearts :p
comments
Its only a 9.8, guys.
Has anyone tried to use such a device with Ubuntu? How was your experience so far?
True.
Yes the harness is what i was talking about.
You can get footguns also from your own cli commands, misunderstanding the documentation, or by copy/pasting from a guide without knowing what you're doing. But in both those cases it is clearer that it is your responsibility for understanding the context. And eventually that's how you learn.
A generative, agentic system that does things for you without you needing to understand, and gets it right a lot of the time, but trains the user to enter the sudo password wihout understanding is not the UX I would encourage in an operating system.
True but a system like that wouldn't just rely on the model training. It'd also rely on the harness around it. The program that takes the text from the clanker's output and executes it. It can have, as existing tools do, a hefty static ruleset that allows / disallows / asks for user confirmation before executing. The ruleset would have to be significant and well designed to catch most disasters. Still wouldn't be foolproof, but neither are my own CLI commands, or my brain at all times of the day. A not-so-reliable operator can be further mitigated by using a snapshotting filesystem.
Any system like this is going to be limited by the fundamental inability of genAI to be hallucination-free. Being programmed with best practices will help but eventually it will suggest something that will be bad for the user.
Quite possibly. But also possibly not. I've see plenty hosed systems by colleagues at work as they start using Ubuntu workstations with no experience.
Some years ago: "Why can't do I get permission error, let me fix it good chmod -R 777 /. Hey Amoeba, my system doesn't boot anymore."
One could in principle create a model that knows the best practices, the no-nos, the dos and don'ts of Linux and try to stand in the way of the user holding the hose.
It's going to train new people to blindly type in their admin passwords and risk hosing the system
Given how open the traditional Linux desktop APIs are, how much functionality is exposed in CLI form, a "desktop" OpenCode-like system could transform a Linux desktop into something other OSes coild achieve with a lot more difficulty. For example, reducing the size of a video file is just a cryptic ffmpeg command on Ubuntu. If ffmpeg isn't installed, it's an apt command to get it. A "make this big video 4GB" prompt is trivial to execute by a local model. And yes, an "AI desktop" would only work for most of us if it can do it all on-device. Not throwing our trusted data to OpenAI's servers. A system like that would also require a strong harness to prevent hallucinations from rm -rf-ing the wrong thing.
Probably OpenAI "accidentally" hacking the site.
People must really not like their /boot decision for the next release.
You have to be careful with in-house developed tools though. Canonical outright owns the majority of the code and outside contributors need to sign a contributor's licensing agreement that would allow Canonical to use their code in a proprietary version if Canonical chose to do so.
Yes, the GPL version would still exist, but Canonical could continue working on the proprietary version and not push the commits to the GPL version.
I'm not saying Canonical would do this. And you can replace "Canonical" in the prior sentences with any company and/or software that requires a contributor licensing agreement.
-- consider as in a counterargument that they're going to make a proprietary linux?
Consider: Canonical developed and released new tools made in-house this year. They're GPLv3 licensed.
i just started learning rust and intend to get my feet wet w lemmy, so i'm becoming inclined to believe in its virtues so i can understand why someone would prefer it over the alternative.
i've also been painfully duped by google's "don't be evil" motto and it's segued me into learning about the intrinsic nature of corporations that make them capitalize on any advantage they have at their disposal if it results in a profit -- be it a well intentioned & needful technology improvement or a fascist leader w expectations as an audience.
if history repeats itself -- and i'm inclined to agree that it usually does -- seager will not have a say if they end up making an mit licensed linux.
i'm also inclined to look for silver linings in dark clouds and ubuntu represents a majority of my professional life as a software engineer, so i'm know i'll atleast like the new canonical Linux^TM^ if it comes into being. lol
I'm not a believer in the theory that Canonical is trying to migrate everything to MIT so they can have their proprietary Linux. Some people think that their move to Rust projects is a cover for that goal.
But in this case, Canonical Sequoia PGP is still GPL, so the conspiracy doesn't make sense here. Hence my joke.
All evidence just points to Jon Seager, VP of Engineering at Canonical, just really liking Rust.
the sarcasm tag makes it tough to tell if you're serious.
I find it highly concerning that Ubuntu is using Rust as a guise to replace GPL components like GNU GPG with GPL components like Sequoia PGP.
/s
The vast majroity of tasks work without issue. But there's a lot of edge cases where uutil fails. When those are found, new tests are added to track them and prevent future regressions.
And new test cases are constantly being added. And with those new cases, the pass rate drops.
Rust Coreutils continues to be at around a 95% pass rate compared to the GNU Coreutils with its test suite.
Huh? Is this really ready for release?
do they not do Kubuntu previews?
EDIT: here https://cdimage.ubuntu.com/kubuntu/releases/26.10/release/snapshot-4/
These should be very close to what the Beta candidates will look like next week, so don't shy away from testing them and making sure you're ready for the Stonking Beta on September 24th.
About time really, still doubtful whether this could ever surpass a vulkan backend but still good to have!