trevor (he/they) @ trevor @lemmy.blahaj.zone

Hello, tone-policing genocide-defender and/or carnist 👋

---

Read more

Posts

0

Comments

450

Joined

2 yr. ago

Has anyone here tried Rust dev on Haiku OS? I love these "niche" OSes, and it'd be cool to write some utilities for it. I assume that a lot of the syscalls might be completely different, so it'd be more challenging as well?

I don't have a strong use for this because i mostly just let it rip when it comes to dependency updates, but I wanted to say that Rust makes the absolute best CLIs (mostly thanks to clap and ratatui).

I love that basically any CLI made in Rust will usually get you easy, readable help output, sensible argument parsing, and with just a small amount of additional effort, shell completions.

Nah. Even if the Snapstore backend were FOSS, you should still avoid Snaps because the way they implemented sandboxing subtly breaks many applications.

Not to mention, they dishonestly co-opt your apt install invocations to sneakily install the Snap version. Actual Microsoft behavior. If a company is that eager to deceive you and shove their tech down your throat, you should avoid it at all costs.

Does Mistral actually provide the training datasets, or are they using the fake definition of """open source AI""" that the OSI has massaged into being as megacorp friendly as possible?

On Macs, I remap it to the Command (super) key. On Linux, I remap it to Ctrl.

It makes copying, pasting, etc. way more ergonomic and doesn't strain your pinky 😌

I'm running GrapheneOS, and they unfortunately do not have that implemented yet.

Thanks!

Unfortunately, it seems the Pixel/GrapheneOS kernels don't support limiting the battery charge limits :/ I tried ACCA, and it installed the ACC magisk module, but the device kept exceeding the charge limits.

Does anyone know of a FOSS app that can limit charging on Pixel devices? I imagine it would require root, which is fine for my usage.

I'm using one called "Healthy Battery Charging", but it only gives you notifications and you have to manually plug and unplug the device.

If you want Alacritty with tabs, COSMIC Term uses libalacritty, so you get the same performance, but with tabs (among other things).

I can't find the video, but i saw someone interview him, and PepsiCo asked him to use a different name.

He now goes by Skylar Spence. It's a different genre, but I love the songs he's released under that name.

I've cloned a drive from my LCD to use in my OLED. It's mostly fine, but occasionally (every few days), the interface would crash. Weirdly, those crashes went away with time, so maybe an update resolved the crashing I was experiencing?

If you want to reliably leave your games on standby for any amount of time, it's probably best to use a fresh image instead of reusing the existing installation from the LCD model.

Perhaps that's true. Although, I think that should be tested because I'm a little unsure since pipes are just the stdout of one command being used as the stdin of the following command. There's still some output, even if you don't see it.

In any case, find has many uses, many of which will print data to the screen, and find is far from the only use case in which this would be apparent. There are tons of situations in which you're going to have to work with large amounts of stdout/stderr, and having a GPU-accelerated terminal will be much faster in all of those situations.

For those that are, for some reason, incredulous of having more performant software (???), here's a simple program to demonstrate the point:

 rs

    
use std::{
    fs::File,
    io::{BufWriter, Write},
};

fn main() {
    let buf = File::create("/dev/stdout").unwrap();
    let mut w = BufWriter::new(buf);
    let mut i = 0;

    while i <= 100000 {
        writeln!(&mut w, "{}", i).unwrap();
        i += 1;
    }
}

  

It simply prints the numbers 0-100000 to the screen. Compile it (rustc path-to-file). Run it in a non-accelerated terminal with time ./path-to-bin. Now time that same binary in a terminal emulator with GPU-acceleration.

The difference becomes more apparent with more text. Now, imagine needing to use something like find on a large set of files. Doing this on a non-accelerated terminal is literally slower.

It's fine if you don't need a GPU-accelerated terminal, but having acceleration is genuinely useful and a noticeable quality-of-life improvement if you do anything more than just basic CLI usage.

WASM is a better way to run code client-side, and has the benefit of not being a terribly slow, untyped mess 😌

W. JavaScript was a mistake.

They would still have disproportionate control over web standards. They should not be allowed to keep Chrome/Chromium under any circumstances.

Authy is garbage too. You're just one small step away from SMS 2FA and your keys are held by Twilio, who has been breached.

Ente Auth is e2e encrypted, zero-knowledge, and cross-platform if you want a secure and convenient authenticator.

"Banned" used to mean "you're done". Now every little time-out is a "ban". Can we use words correctly instead of lying for clicks?

Shouldn't we also have the opposite list; a sort of name and shame or if you use these banks, you're screwed list?

In part, because it can be more conclusive to take a bank that has consciously made the decision to block access, rather than having a list of banks that maybe just haven't gotten around to it yet.

I had a pretty good time rewriting various coreutils in Rust. I liked it because the difficulty of doing so ranges from something as easy as the true command, where you simply exit with a success status, to more challenging stuff like writing a basic shell.

Granted, it's not that complicated to write CLIs with simple inputs and outputs, so maybe it's not valuable for others but it certainly helped me understand Rust better than before.