trevor (any/all)

I think if someone licenses their applications wrong, they shouldn’t use my library. That’s why I license them as GPL.

But there’s also LGPL if you’re more tolerant to having your work used for less free software than I am.

Yep. I hate to see it being used as a default license in the Rust ecosystem. Wonderful language, but terrible corporate culture.

The problem with macOS is that they use BSD utils, which are lacking functionality from GNU utils. If anything, Rust uutils being pushover-licensed means that Apple would be more likely to replace their broken coreutils with uutils and you’d get more parity with the coreutils installed on most Linux systems.

And I say that as someone that despises pushover licenses, but this creates the probably that macOS utils won’t suck someday.

Seriously. I had to read that five times to see if I was missing sarcasm. What a fucking awful product.

They have a good DSP for sure, but those speakers on their own can get louder than any other laptop I’ve ever heard while maintaining pretty decent clarity (to my layperson ears). The DSP can help with the clarity and quality, but the actual loudness and hardware capabilities also seems better.

Oh, also speakers. Apple puts decent speakers in their laptops. The FW 16 had worse sound than many phones that I’ve had.

I use it because Apple is the only manufacturer that understands that laptops need great displays, keyboards, and trackpads. Most other laptop manufacturers fail in one or all of those categories. The new Framework 13 may be an exception to this, but as someone that bought the 16, that was hot garbage. So I gave it up for a Macbook.

With Asahi, I have a rock-solid Linux experience on a laptop with good build quality.

My understanding of gccrs is that it merely provides a way to compile Rust software with GCC instead of LLVM, which is great! But it’s such a small piece of the Rust ecosystem (it’s merely a frontend). Maybe it’d be a good starting point for a more copyleft ecosystem in the future though.

This is a bit of a tangent, so I didn’t include it in the above comment, but I don’t think “open source” is sufficiently anti-capitalist, so the (A)GPL was never going to save us to begin with. “Open source”, as defined by the OSI (a.k.a. a handful of megacorps in a trench coat) and the FSF, prevent “discrimination of use”. So if you want your software to be “open source” or “free software”, you have to accept that your software can be used by for-profit entities to exploit your labor, and potentially to perform heinous acts, such as military or surveillance usage. What we currently call “copyleft” is actually just copylib 😭

No open source license, not even the (A)GPL, allows you to forbid this. Unfortunately, I don’t see an alternative framework being widely adopted anytime soon. It seems that the best you can do for now is use niche licenses like this and just accept that your software can’t be considered “open source” :/

IMO it isn’t in bad faith any speech making that apparent.

I’m not sure I understand what you meant (there may be a typo in there).

The language, as an inanimate object, doesn’t have an ideology, sure. However, people running the show in partnership with the ruling class have.

This, I agree with. It is very concerning that Rust has so much corporate buy-in. And the structure of The Rust Foundation being operated more like a business than something like the Zig Software Foundation does worry me.

But I often feel the need to chime-in and correct the common misconception that Rust rewrite == corpo-relicense. It’s false and I think the conspiratorial coupling of Rust to corporate embrace-extend-extinguish only serves to discourage people from writing better software.

I would love to see a community fork of Rust and its ecosystem one day, but I don’t think we get there by discouraging people from writing or using Rust software.

Which speaks to my other comment: nothing about Rust necessitates using corpo licenses. The reason so many things are being rewritten in Rust is that it’s a great language and it provides tangible benefits to users. The owning class doesn’t need a special language as a pretext to de-GPL an ecosystem. They could do it with C, OCAML, or any other lang.

Lemmy is written in Rust. I don’t think dessalines is a stray liberal on lemmy.ml lol

Using Rust in no way requires the usage of pushover licenses. While it’s true that many devs are using pushover licenses, there are plenty of GPL Rust projects. You are just focusing on the sensationalized ones that get mentioned in news cycles.

• AGPL Rust projects on GitHub
• GPL Rust projects on GitHub
• Unfortunately, Codeberg doesn’t support filtering by license, but there are Rust projects on Codeberg, some of which will use copyleft licenses here.
• GNOME’s GitLab is also rife with GPL-licensed Rust projects.

Your reading comprehension could use some work. Anyway, I’m sure just telling people that Nix is just JSON is gonna make Nix easier to learn. Good luck!

I second the recommendation for running Asahi on your MacBook. I’ve been running it for years and it’s great. The hardware support isn’t perfect (Apple has nicer trackpad drivers for their hardware), but it’s like still very good.

I attempted to learn two weeks ago. I know Rust, C, and Python. Nix documentation is getting better, but still nowhere near as good as most other langs. And the LSPs are genuinely useless.

Unfortunately Nix documentation is sparse, the LSPs are almost useless, and the learning curve is the steepest of any programming language I’ve ever tried.

Nix is better of you can understand it, but very few people I work with do.

Partial HDMI 2.1 FRL support is huge (even if it’s from upstream)! I finally have 12bit color on my home theater PC! Content looks amazing now 😍

Unfortunately, it does flicker occasionally if VRR isn’t enabled, but that’s why it’s behind a debug flag to begin with. I can’t wait for Linux 7.3 to complete the implementation.

Eat shit, HDMI Forum.

Partial HDMI 2.1 FRL support is huge (even if it’s from upstream)! I finally have 12bit color on my home theater PC! Content looks amazing now 😍

Unfortunately, it does flicker occasionally if VRR isn’t enabled, but that’s why it’s behind a debug flag to begin with. I can’t wait for Linux 7.3 to complete the implementation.

Eat shit, HDMI Forum.

Actually, /bin/sh is available on NixOS 🤓

Yes, it’s true that #!/usr/bin/env bash is a more reliable way to get bash, but you mentioned that you wanted a POSIX shell, not that you specifically needed bash, so #!/bin/sh will work on any system including NixOS.

Also, export a=b does work in Fish. But you don’t have to use it if you don’t know how it works.