It's not really 130-150 words per min though bc mostly the words we say are nonsense, "uhms" and saying the wrong thing and starting over and pausing and such.
Not to mention, when we speak to a computer, it's not like to a person, as others have pointed out. The 130-150 wpm number comes from in context speaking where we already know what we're going to say. That isn't the case when doing things on a computer such as responding to a comment, anything requiring thinking, coding, etc.
Also, speech-to-text systems do not immediately recognize the speech we say, adding further delay.
So it's not actually 130-150 words a minute.
In terms of meaningful day-to-day use, I maintain that it's far slower and less precise than a keyboard, especially if you're a proficient typer.
And this makes sense as everyone I've ever met who likes to use speech-to-text (excluding those who MUST use it for disability reasons) are simply those who are bad at typing. Cope harder. slow-mo. This comment was written using a keyboard
EDIT:
so what they’re saying is true for that one use case
This doesn't follow. Both of us are talking about inputing in english. Vibe-coding with a keyboard is also superior there
Are they using any original GNU coreutils code as reference? My understanding is nothing is 1:1. They're trying to build, from the ground up, a totally new codebase that has the same user-facing functionality but under the hood is idomatic Rust code (so nothing like the GNU C code)
They are recreating something that matches behavior not using licensed GPL code. Which is the same way the GNU coreutils were a recreation of the proprietary Unix tools in an effort to provide open source alternatives.
Like you wouldn't say "An appropriate amount of work to slap a GPL license on somebody else's work" in reference to GNU recreating the Unix tools, so why say it here?
I'm not suggesting containers but rather running binaries natively, just as separate users. No cgroups or overhead. Just normal binary access, just you won't have access to all files (and since everything is a file, "all files" includes hardware as well)
No my proposed solution uses the "everything-is-a-file" aspect of Unix-like systems with the built-in permissions systems around files. You don't need cgroups at all for what I'm suggesting
I have this idea. It's taken from the Android world. In Android, apps all get their own user, and can only access their own filesystem. They are then added to groups like Sound or Files or whatever to gain access to other things. This is simplifying but gave me an idea.
So my idea is two parts:
We add more groups to our Unix and Unix-like codebases. Piecemeal access to different folders like a fs-docs group for access to /home/<whoever>/Documents
Each app, when installed, gets a user and a folder (maybe /opt/<pkgname> or /apps/<pkgname> and a group called app-<pkgname>). It requests during install (or maybe runtime via a permissions management application) access to specific groups for its user. Launching an app then becomes sudo -u app-<name> /opt/<pkgname>/<binname>.
You login as a user with access to limited permissions and then run the application. Thus you run it sandboxed but without special software like Flatpak or AppImage - just standard Unix groups.
Claude code I believe has its own sandboxing system, but with this system it would be the system itself restricting claude, not the claude code app, truly limiting accidental outreach.
I built a demo package manager using this concept a while back called 'bokspm,' though I kept it private (and now, my current job will not let me open source it)
The future of AI in Ubuntu [Except it's Internet and Slackware in 1996 instead of AI and Ubuntu in 2026]
As 1996 progresses, internet-based tools are becoming more and more ubiquitous. Adoption across the tech industry has been mixed, both in terms of which projects are embracing "Web" technologies, and in how companies are structuring their adoption. As a result, I'm frequently asked about what Slackware will do (or not) to incorporate networks.
In this post I'll detail how the internet will play a part in Slackware's future, my framework for classifying internet features in the OS, and how Slackware is currently approaching adoption internally, because I think that will help paint a picture of our intent.
The bottom line is that Slackware is ramping up its use of Internet tools in a focused and principled manner that favours open network tools with license terms that feel most compatible with our values, combined with open source contracts. Internet features will be landing in Slackware throughout the next year as we feel that they're of sufficient maturity and quality, with a bias towards private networks by default.
Internet features in Slackware will come in two forms: first as a means of enhancing existing OS functionality with networking in the background, and latterly in the form of "Internet native" features and workflows for those who want them.
Mobile application require strange wrappings and packagings to run native code like that.
On android you could potentially use termux and build from source for aarch64, but iOS doesn't have anything like that.
Furthermore, iOS is very locked down, so running some random source from GitHub is essentially impossible without proper developer tools and a mac to run them.
I just dont enjoy it. It feels extremely sluggish, the ui is far more confusing with 100s of menus and weird names, and it doesnt have any basic file hosting for releases which is annoying. There are more but it's basically just lots of annoying little things that are super inconvenient.
Maybe this is wrong, but my understanding is BTRFS is generally slower than EXT4, and that's okay. It's not going for speed
Where it shines is not in its speed but in its versatility offering compression, rollback, subvol, etc
For example, for applications, you do a lot of writes/reads to Documents or load resources like for games, so use EXT4 for /home or for a dedicated /games partition
For your system, it could be broken via config tweaks or updates, so use BTRFS to have the rollback options
I'm in stage 2