Why do you need to do research for GPL? It’s the OG opensource license AFAIK that forces users to also opensource their stuff. MIT let’s anybody close source your code and make money with it.

GPL isn’t perfect as it doesn’t solve the funding problem, but MIT is about the worst thing one can do for opensource: do the work for companies, for free, and be OK with never contributing back to the opensource ecosystem.

But why MIT? How come that became the default? Why not GPL? Is Microslop Github suggesting MIT by default?

Or maybe not so curious…

I don’t understand what’s going on with the rust community insisting on cuck licences. Do they love writing on their Mac books so much?

Are they just dumping stuff into the Epstein files, hoping that it will artificially bloat its size and scare of potential readers? “OMG, 3 million pages? There’s no way I’m reading that”.

Wouldn’t that be like an obstruction of justice?

It’s been a while since I left the forums, but there always seems to be drama and something going on. I didn’t the community to be very helpful and inviting. It left a very bad taste in my mouth and in mostly avoid it. Now I ask LLMs to whip something up when in need it.

At least as long as you don’t really need WiFi of course…

I thought that was a solved problem on Linux. Is it the reluctance to use binary blobs?

For some reason, stuff like libre wolf isn’t in the guix repo. Not even Firefox. It’s very confusing.

I’m not that much a fan of brackets and jumping through hoops to install anything non-GNU.

Well, I’m not in Microslop platforms, so that’s going to be difficult.

Second, the way things work in the current nix/nixos community make it easy to create a PR but very difficult to get it merged. Attempts at writing documentation are nitpicked to death, unless you belong to the privileged class of the documentation team or have merge rights on Microslop’s Github.

A fork would also give an attempt at forming a new community with different rules and focus.

I haven’t yet found out where its major differences lie. And it seems like they haven’t taken a firm stance on flakes (yes or no). They also only forked the interpreter, not nixpkgs. A good step, but their documentation wasn’t good, the last time I checked.

If only the battles were about software. They are about unrelated beliefs and political ideologies. I’d very much prefer ideological battles about software trust me.

What happened?

Damn right. And the Nixos community forums are full of people unwilling to accept this. They will gaslight you into thinking you’re the problem. “Just do this”, as I’d it’s completely obvious and you’re dumb for not realising that. Of course if they find out you have some ideological incompatibility with them, you’re out anyway.

NIXOS really needs a fork. One that embraces or rejects flakes outright. One that stops inviting ideological battles. And one that embraces documentation.

I just looked it up and - x means one filesystem. But does - v give you a progress bar or just a lost of stuff copied?

IIRC rsync also treats the trailing slash in a special manner that I always have to look up.

How do you get the progress bar?

It’s a damn pain to remember all the flags. How many flags can a program friggin have? I’m always afraid that some flag I enter will reverse the sync and delete everything in the source folder because the target is empty.

I use rsync only when all params have been reseasrched and tested. cpx presumably just requires cpx - r source target instead of 5 rsync flags.

There are better linux laptops for less. No need to send tour money to the US.

Based on NixOS maybe? Wouldn’t surprise me

They have to enable webgl. @Geodes_n_Gems@lemmy.ml

Quodlibet is pretty nice and has been my default for a good decade now. However, it still being on github makes it difficult to contribute to since I left Microslop’s ecosystem.

I wish there were something out there in Rust that were extensible, but plugins seem to be difficult in rust.