verassol

It’s a thing!

I think you have a point there, but the reasons why Mint does not ship a streamlined version may be simply because the maintainers don’t want to bother with a whole different context to build, document and support.

I do think there would be value in a less “batteries included” Mint. I disagree with people in this thread who claim the “whole purpose” of Mint is all the stuff it packs, because it goes far beyond the essentials. Mint develops a lot of GUIs for the user to be able to configure the system. I think just these plus the in-house Mint core apps would make for a sweet, lightweight and less bloated system that would have real appeal, but that would also mean more work for the Linux Mint team and perhaps it wouldn’t really mean much for their audience.

Your mileage may vary for performance. It really depends what OS and what hardware. In my experience saying all BSDs are slower at rendering would be too broad a statement.

If you’ve done Arch and Debian server installs, you’ll be fine installing a major BSD. Just answer prompts and you are done, particularly if you are using the default disk partitioning scheme. Consider NetBSD. It’s known for its wide hardware compatibility. X is pre-installed, just “startx”.

Consider antiX. It’s very lightweight, supports 32 bit and you’ll have access to the Debian Repos.

It wouldn’t be fair to say zsh is slow because ohmyzsh is slow. ohmyzsh is notorious for being a bit bloated. If you pull the whole thing, it makes a mess of your shell and you really can’t tell anymore what is what.

It’s possible to install the individual stuff you need from oh my zsh without pulling the whole thing.

I am a happy antidote user. With it, you can do something like this on your zsh_plugins.txt file:

ohmyzsh/ohmyzsh path:plugins/extract

Though ohmyzsh provides its own means to enable and disable plugins, this will allow you to cut that down to the pulling only of individual plugins in the first place.

Your mileage may vary, but other plugin managers may give you different ways to accomplish the same.

zsh is quite an advanced shell. You will find other shells that do things radically different and have their own bells and whistles, but if you are going for feature parity it may be hard to find a replacement.

Thank you for sharing. Your perspective broadens mine, but I feel a lot more negative about the whole “must benefit business” side of things. It is fruitless to hold any entity whatsoever accountable when a whole worldwide economy is in a free-for-all nuke-waving doom-embracing realpolitik vibe.

Frankly, not sure what would be worse, economic collapse and the consequences to the people, or economic prosperity and… the consequences to the people. Long term, and from a country that is not exactly thriving in the scheme side of things, I guess I’d take the former.

That’s interesting. I was looking up “Lemmy Terms of Service” for comparison after getting that quote from the Reddit ToS and could not find anything for Lemmy.ml. Now after you mentioned it, looking on my Mastodon instance, nothing either, just a privacy policy. That is indeed kinda weird. Some instances do have their own ToS though. At least something stating a sublicense for distribution should be there for protection of people running instances in locations where it’s relevant.

the claimants were set back because they’ve been asked to prove the connection between AI output and their specific inputs

I mean, how do you do that for a closed-source model with secretive training data? As far as I know, OpenAI has admitted to using large amounts of copyrighted content, numberless books, newspaper material, all on the basis of fair use claims. Guess it would take a government entity actively going after them at this point.

Yeah, their assumption though is you don’t? Neither attribution nor sharealike, not even full-on all-rights-reserved copyright is being respected. Anything public goes and if questions are asked it’s “fair use”. If the user retains CC BY-SA over their content, why is giving a bunch of money to StackOverflow entitling OpenAI to use it all under whatever terms they settled on? Boggles me.

Now, say, Reddit Terms of Service state clearly that by submitting content you are giving them the right to “a worldwide, royalty-free, perpetual, irrevocable, non-exclusive, transferable, and sublicensable license to use, copy, modify, adapt, prepare derivative works of, distribute, store, perform, and display Your Content and any name, username, voice, or likeness (…) in all media formats and channels now known or later developed anywhere in the world.” Speaks volumes on why alternatives (like Lemmy) to these platforms matter.

StackOverflow: *grabs money on monetizing massive amounts of user-contributed content without consulting or compensating the users in any way*

Users: *try to delete it all to prevent it*

StackOverflow: *your contributions belong to the community, you can’t do that*

Pretty fucked-up laws. A lot of lawsuits going on right now against AI companies for similar issues. In this case, StackOverflow is entitled to be compensated for its partnership, and because the answers are all CC BY-SA 3.0, no one can complain. Now, that SA? Whatever.

Recently did something similar and yeah it seems Mint, specially LMDE in my case, is a great fit for such cases. It’s on that sweet spot between being too bare and too bloated.

I’m not the biggest fan of VBox either, it’s just very popular and full of sequential “wizards” to guide the user along the process of creating VMs, so it might be one way to get started. I’d much rather work with QEMU though.

That might be fun then.

QEMU can be as simple as this:

qemu-img create -f qcow2 mydisk.qcow2 20G

Here you are first creating a disk image with the format qcow2 and maximum 20G capacity. This is a QEMU disk image format that will take up very little space and grow as you use up the VM disk.

qemu-system-x86_64 -m 256M -cdrom alpine.iso mydisk.qcow2

This will start a VM with 256MB of RAM, the alpine.iso image in its virtual CD/DVD slot, and the disk image you just created as a virtual drive. This will come with networking enabled by default, so you’ll have internet access from within the VM.

It should now drop you into the Alpine installation. Alpine is very lightweight so it’s great for experimenting, but you could do virtually the exact same for most other flavors of Linux and BSD images out there.

Once you are done installing, you can power off the VM and then start it with this:

qemu-system-x86_64 -m 2G mydisk.qcow2

That’s basically the same without the -cdrom argument, this time with 2GB of RAM. I find QEMU a delight to play with because it has sane defaults like that. Hope you have fun too!

I think you might like DIstroSea. If you’d like to persist your experiments, then likely learning how to emulate systems with QEMU or VirtualBox (the latter if you’d like a friendlier GUI-led experience, the former if you want to go full-CLI virtualization). QEMU is great in how lightweight and easy to create and discard self-contained VM disk images can be.

What I mean is that no one will stop you. When you ascertain your own right to do it, it doesn’t mean much that I don’t believe you are entitled to it. It’s pretty much common practice. That is more a semantic matter at this point, but yes I stand by that being messed up for a project the size of Nix.

I don’t think that being a dictator for your project is necessarily “toxic”

Yeah, it is not necessarily toxic. It is at a lot more risk of being, though. Even a collectively managed project will mess up and upset the community, but then there is a sense of shared responsibility and more deliberation on what to do. With a BDFL, it’s just whatever. After your project reaches a certain size, that risk keeps increasing… exponentially.

I have projects that take contributions and I work on others that do not

Precisely. You see, if we take this into the context of a smaller project, specially one managed by a single person as you seem to be coming back to, that is a very different context. I don’t think an OSS maintainer should be laboring physically and emotionally to meet the demands of users. That is a well-known problem there. If this person doesn’t even want to have contact with the community and just ship code once an year, fine. They are just sharing things with the world at no cost. In this context, “suck it up and just fork it” is indeed the way to go.

When you take something as big as NixOS though, that can really be inverted. Now you have a very large number of people who are laboring physically and emotionally to sustain a very large project, and the original creator shifts to a very different place to. It’s another discussion entirely.

If pursuing your own vision is the sole purpose intended, it would not be limited at all.

I guess you can, yeah.

My point is not that you can’t. You clearly can. And many do. The thing is, when you create your foundation that “you fill with whoever you see fit”, when you faithfully believe that the BDFL will “stop them doing stupid things”, or that you get to choose your board members arbitrarily and tell everyone it’s not a democracy like you are proud of running it as a dictatorship, that’s just a incredibly narrow and toxic culture you have set up. It’s not impossible. The ethic you are posing is actually quite widespread in the world I live in, anyone arguing for it will get many around to agree, it’s very assertive and rightful. Still, a shitty choice the way I see it. And from this bleak outset of things, I suppose forking is indeed the only option you have.

I guess it can be simple like that when you are the maintainer. It is definetly not as simple when there are many of them. Of course you can run it like that and many do, but the whole mentality is pretty limited.

My statement is not that you have to do whatever anyone asks in your project that you maintain. My statement is that a community that contributes towards a project has a say in it. You might want to ignore it, handle it BDFL-style, politely and cynically decline, whatever.

Not really about what is the absolute correct answer. Our values are clearly different. More like what I believe works best in the long term.

I think the easy answer to that is “because it is not as trivial as forking a small app that could run off of a git repo”, it’s a whole operating system involving a lot of infrastructure and a huge community around it. It might get forked, but people fight probably because they see value in what exists and would rather try and advocate for whatever direction they believe is best. Those who would disagree are not very different, just passive.

An even more trivial alternative is settling for “whatever the founder wants” and seeing the ability to fork as the final justification for this mentality. This is a lot less work, but also can amount to doing nothing, even if shitty decisions are being made. Even if that is your stance, you will have to fight for it. The alternative is everyone just sit idly and pretend not to have opinions. I’d much rather embrace the chaos that comes with collaboration and let it find proper processes to manifest.

I understand that and it is indeed a good thing to publicly license your work rather than keep that to yourself. Still, no matter how virtuous one’s actions are, that does not mean the people who come to deposit their time and work for a project should accept everything that person does simply because they started it.

People are entitled to argue about the project they participate in, and that is even more true for open source software, where the contributions of the community eventually become much greater than any single human can accomplish. I really do not understand this mentality of “this person created it, therefore if you don’t like any of their decision suck it up or go make your own fork”, it is very narrow and a horrible way to conduct anything, really anything, much less a collaborative project.