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

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

---

Read more

Posts

2

Comments

664

Joined

2 yr. ago

Moderating

---

Our treatment of animals is really a litmus test for how seriously we oppose fascism. If we want to know what we’d do when we have total and complete control over someone, we need only look at how we treat other animals. Right now, we’re showing that when the time comes to prove we care about liberty for all, we cave - just like the dictators we so vehemently oppose.

100000% yep. We're either all free, or no one is. As long as people continue justifying non-human animal exploitation, human animal exploitation will continue.

This is literally the only humane way to keep everyone safe.

Bye 👋

Yes! The three-finger drag + this getting merged into COSMIC recently almost completely covers all of the things I like about macOS.

This is probably the most underutilized, but extremely helpful features from macOS and I never expected to see it ported to Linux because i thought no one else knew about it.

Super happy to see it going into libinput!

That's not what any of that means. Your reading comprehension could use some work.

You are really trying hard to contort things into things I didn't say.

The people problem is being ignored, and it wasn't until Linus was made aware of a technical justification for slapping Hellwig down that Linus focused his disapproval away from Marcan, who was rightly calling this out, to the person creating the problem.

And we lost at least three solid R4L devs, of which, Marcan was one, and there's zero acknowledgement from Linus that fixating on Marcan rightly calling this shit out was wrong.

The people problem of letting obstinate babies block valid code for any non-technical reason still has not been addressed, and this will keep happening until that changes.

I'm very firmly in the Rust for Linux camp because I am in the "make Linux better" camp, and I don't see why eventually getting Zig in the kernel would be a problem. If Zig solves problems that C and Rust don't, by all means, it should be brought in.

However, one of the primary reasons Rust was chosen is that it is memory-safe by default. Zig, on the other hand, has opt-in safety. So unsafe Zig should probably only go in very specific places where C and Rust can't do the job. And ideally, there would be some rules that require the usage of safe Zig everywhere else.

Ignoring Zig, the language, Zig's compiler toolchain is hands-down, the best I've ever seen, and I think introducing Zig to the kernel by making "Zig-built Linux" a thing, would be a really natural way to get that process going.

Nothing speculative about it. The substance of the problem (obstinate, crotchety baby that was blocking useful code) was ignored and Linus instead chose to wrongly focus on Marcan calling out the problem. There's nothing wrong with people calling out toxic bullshit, and it seemed that social media was necessary for that in this case, yeah.

Exactly. Airing-out Hellwig's successful attempt to sabotage Rust efforts (and it was successful, given that at least two important maintainers have already resigned) was good, actually.

Unfortunately, it seems that Linus doesn't have the maturity to recognize that, and this cycle is likely to continue, barring something good and unforeseen happening.

I just cant wrap my head around why they're willing to go so far to gain good will from people by having such a generous free tier, but somehow licensing the code under a FOSS license is out of the question??

Why not just go all the way and make sure everyone who cares about reading the souce could also give you free contributions?

Well, hopefully the get on that. They have to realize that a large portion of their target demographic (people fed up with garbage search) also rightly don't want their search histories tied to their real identities.

Yes, because private property is theft. But unequal enforcement of copyright law is worse. Right now, LLMs are just lying machines trained on pirated data and the companies that run them are acting with impunity for doing something a normal person would get put in jail for.

Copyright is immoral, but as long as it exists, the laws should be extra strict on companies that steal others' works.

What does this actually do? Is it possible to use Kagi without providing them personal information to create your account yet?

I don't disagree with most of that, but none of what you said actually addresses the problem. The problem is that there are functionally two (notable) flatpak repositories, but one of those is going against the will of the upstream software devs and shipping broken software that they have asked them to stop packaging. And Fedora users are getting the broken flathub repository as the default, without really having reason to suspect that their "flathub store" would ever trick them into installing from a different source. The "verified" badge, especially the lack thereof, does not address that.

As for users feeling “tricked”? That’s a difficult thing to say. I would like to say that users should at least know something about the distro they are choosing (ie Ubuntu users should know about snap; Fedora/Debian users should know about their stances on FOSS, security, and patents; Arch users should know its a DIY distro).

You can RTFM someone all day, but if you actually want Linux to be adopted by more people, you need to reduce the anti-patterns. Snaps are generally known about because they are infamous for also breaking packages. And they're still major footguns when people are recommending Ubuntu to people that are new to Linux, who are the least likely to know that their apt package installations are going to be installing differently-packaged software that has its own set of problems. If we get to a point where Flatpaks have a similar problem to Snaps, we've taken a wrong turn, and it will only hurt Linux adoption.

The OBS and Bottles packages have been broken for a long time. Long enough that both upstream projects asked them to stop many months ago. They don't get to pretend it was a mistake. This isn't just another case of a minor packaging bug getting to users. They are packaging the software incorrectly.

I answered most of this in the other thread, but I am aware that anyone can make flatpaks. What I meant is that flatpaks were supposed to make it easier for devs to get their software to end users by allowing them to not have to worry about distro-specific packaging requirements or formats.

But when someone else takes it upon themselves to make broken flatpaks, ones that you've requested they stop doing, now they're making things worse for everyone involved and should be considered a hostile fork and treated as such.

They work on other distros... if they work at all. If those "strict guidelines" are resulting in flatpaks like OBS and Bottles, which are broken and the devs have tried to get them to stop shipping, then I'll pass on Fedora flatpaks.

I dont criticize Flatpaks for allowing alternative packaging sources. I criticize Fedora for sneakily (whether intentionally sneaky or not) setting their broken flatpak repo as the default, leading to a bunch of confusion by Fedora users that don't know they're actually using different, sometimes broken, packages from everyone else.

The uBlue downstreams of Fedora know this, and they have the decency to present the user with that information upon installation. So thankfully, their users don't end up wasting their time with problems that Fedora introduced.

I think a sort of Linux compatibility layer could go a long way toward making Redox more viable. It may already have one, but that seems like a good place for an ex-Linux kernel dev to work.

can they simply fork?

Forking the Linux kernel will effectively guarantee that no one will run their software. None, but the most niche distros would ship it. If the Rust people are forced to fork, their time may be better spent contributing to Redox.

Why do people love Rust so much?

Rust makes it very difficult (but not impossible) to write dangerous code, whereas C pretty much guarantees you'll write something dangerous (and therefore insecure or buggy) at some point, especially in larger codebases, like the Linux kernel. Arrogant devs will defend keeping Rust out of the kernel by saying things like "write better code", but if the people writing kernel code for 20 years are still writing dangerously flawed code, it's safe to say that at a certain point, we need a better tool. That tool is Rust.

Rust also has very high-quality libraries that produce nicer finished products. I learned Rust because of clap and ratatui, which make superior CLIs and TUIs to anything else. Seriously, go use a CLI or TUI that was made in Rust. Try bat, a cat clone. You'll get easy, great command-line completions, easy-to-read help output, optional, beautiful syntax-highlighting, theming, etc. It's hard for me to go back to vanilla cat.

And I say all of that as someone that likes C. C is really fun, and it's a very powerful language, but it was not designed to be memory-safe. If it was, the people complaining about Rust would just complain about C too.