

Wheezy was the first version I used
I make things: electronics and software and music and stories and all sorts of other things.


Wheezy was the first version I used
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
Keyboards are way more efficient than voice tho


were forthcoming about shelling out the real work to c
When did they shell out “real work” to C?
There is no C in the repo: https://github.com/uutils/coreutils
They aren’t wrapping the GNU coreutils in a Rust shell; it’s a total unaffiliated reverse-engineering


deleted by creator


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?


Overhead
And for a number of reasons this isn’t like flatpak at all.


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:
fs-docs group for access to /home/<whoever>/Documents/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)


Bc I’ve never heard of that


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.


I am begrudgingly moving to gitlab, slowly but surely
The modern one:
When there’s a function that can be written manually in 10 minutes but you find a way to do it in 10 days using LLMs
As others said, it means nullable, but to put it in more intuitive, less-jargony way - it’s a question mark bc you don’t know if the value is actually there or not. It could be a Singleton, but it isn’t until you check if there is a value. Whereas if you have, idk, int a no question mark, then you’re saying you actually have data.
Essentially with C# 8, they “removed” null and reused the idea of null references in creating what is essentially an Option like in other languages. You either have some data of some type, or none (a null reference, in this case). By default, everything has to be there. Then when you need null, e.g. you may not have something initialized or an operation could fail, you explicitly grab for it. Thus it reduces null pointer bugs. If you don’t need nullability, you can ensure that you don’t accidentally write in an issue. It safety checks statements and parameters.
typedef struct {
bool a: 1;
bool b: 1;
bool c: 1;
bool d: 1;
bool e: 1;
bool f: 1;
bool g: 1;
bool h: 1;
} __attribute__((__packed__)) not_if_you_have_enough_booleans_t;
Also bots