[–] 5 points 2 days ago (1 child)

Install git. Then type git clone <url>

For example to download miniaudio you would type

git clone https://github.com/mackron/miniaudio.git

And it downloads all the code for you. There's a button on github that says "code" if you click it you can copy the URL for cloning.

  • source
  • parent
  • context
  • [–] 4 points 2 days ago (7 children)

    Aahhh, so you’re saying when it’s a MIT and BSD licenses, the original developer doesn’t really have to maintain the code since the business isn’t really obligated to contribute back their changes. “Hey, I’m giving you this code and it’s up to you if you want to maintain/improve/add more to it”. Does that sound right?

  • source
  • parent
  • context
  • [–] 5 points 2 days ago (2 children)

    Legal questions.

    If I contribute a line to m1n1 when it was licensed under MIT, is my line also MIT-licensed?

    Am I still the author of my line, thus retaining my right to revoke the license?

    Can someone (say, Jack) who received a MIT license to use my line release it under a more restrictive licence?

    Then, is someone else who received a GPL licence from Jack to use that line of mine, violating the licence if they keep modification private?

  • source
  • [–] 3 points 2 days ago* (last edited 2 days ago)

    since I want to go from Linux Mint Debian Edition single boot, to LMDE + CachyOS/Fedora/endeavour. I'm doing this post to ask some questions:

    Splitting a partition through GParted is relatively straightforward.

    Boot into a GParted iSO with a thumb-drive, determine which partition you want to modify which is quite easy if you know the size of it, once you figured that out you should be able to shrink “Free” space to make room for your new partition which will house your new distro.


    Debian is very resilient, I’ve swapped my SSD, GPU, Motherboard, CPU and RAM without having to reinstall the operating system, all it needed was to remove the old packages/drivers to then install the new packages/drivers.

    Edit: I recommend all beginners to learn a tiny bit of BASH, whenever you distro hop like this BASH is what your “terminal” or “console” will typically use for shell commands, the main thing that differs between Arch, Fedora and Debian is package management (apt, yum, pacman, etc) and how software is installed.

    If you need advice or suggestions feel free to shoot me a DM!

  • source
  • [–] 1 point 2 days ago*

    Honestly, anyone distributing compiled code from GitHub should at a minimum set up a basic GitHub page with a link to it at the top of the readme... Probably wouldn't be very hard to set up a CI workflow to automatically update the page with the latest releases and a link to the relevant release page for details.

  • source
  • parent
  • context
  • [–] 2 points 2 days ago (8 children)

    It doesn't explicitly, but because all subsequent forks and software that makes use of GPL licensed code must also adhere to the GPL license, the original developer more naturally becomes the sole maintainer unless you can build a community of like-minded developers. Free and open source software doesn't have much incentive for maintenance outside of those passionate about it.

    With an MIT license, attribution is sufficient and a business that finds value in that code may repackage, redistribute or sell that code without making their whole product strictly open source. In this way, you end up with larger business investment in your works because there's an inherent value in keeping it maintained that has a direct return.

  • source
  • parent
  • context
  • [–] [S] 1 point 2 days ago

    I find that the performance itself isn't drastic outside of code compilation and video editing, but the responsiveness and smoothness is incredible. To me the 1000Hz tickrate is the biggest improvement, feels like the first time you upgraded your old 60Hz monitor.

  • source
  • parent
  • context
  • [–] 8 points 2 days ago (4 children)

    I used to select MIT primarily to keep my name associated with the code. The idea being if companies picked up my projects and used them in their products, it would be a good thing to have on my resume, and could land me a job.

    I'm at a very difficult point in my career now, and the days of this xkcd are probably coming to an end. Nobody wants to use libraries anymore, they just vibe-code their own.

    Now I'm reconsidering publishing my personal project source code at all, because I've rarely got contributions, and lets be real, a non-commercial license won't stop the code being stolen anyway.

  • source
  • parent
  • context
  • [–] 4 points 2 days ago* (4 children)

    I'm good at figuring things out. I don't know how to get code on GitHub even though I've lazily tried multiple times.

    I get frustrated because I'm looking for something that I feel should be easily found (code on GitHub). Instead I'm given a puzzle I have to navigate through. I thought getting the code off GitHub was going to be the easiest part of my project. Nope.

    Everyone wants your data so apps and websites are intentionally designed to keep people moving through them. I'm not saying that is what GitHub is doing here but it's the reason I have little curiosity to explore apps and websites anymore. It's flawed by design. Not because the opportunity to improve the end user experience hasn't occurred yet.

  • source
  • parent
  • context
  • [–] 3 points 2 days ago

    It was Ikey Doherty's of Solus and Intel Clear linux fame passion project; was, because he basically left yet another project behind. Now it's being carried over by solus contributors and other interested parties who are working on making it a stable base for power users and distribution makers to use of.

    It's basically build atop of a declative Nix/Guix-like package manager if it was made for a more sensibly readable config language like kdl, essentially toml but good, and it only deals in packages, not configs, simplifying it a lot, thus, you can just use as if it was a normal imperative package manager (it isn't) and just:

    sudo moss pkg add whatever

    And it'll declaratively update the config file to add the package to it, which you can just copy to another machine to replicate the current system's state, all without having to edit a config file in a language that requires some knowledge In functional programming, nor a degree in compsci to create a package for the distro. "System model" they call it.

    As far I know, solus is intending to eventually use it as base. They pretty notoriously banned AI to their distro codebase a while back, definitely not slop.

  • source
  • parent
  • context
  • [–] 13 points 2 days ago (5 children)

    Are people just not exploring websites anymore? Surely my household can't be the only one where if you don't know how to use a website or find something on it, we actively explore it. (Dodgy sites notwithstanding, I mean safe and legit sites). Am I strange that if I can't work out how to use something, I look for a manual. And barring that, I try different things, trouble shoot using logic, etc. to work it out for myself.... I'm not a programmer but I can't say as I had a great deal of difficulty working out how to use Github (as a consumer) for myself...

  • source
  • [–] -3 points 2 days ago*

    A user is not owed "ease of use"

    I already covered this in the comment you just replied to.

    At the end of the day, GitHub is a developer platform

    This was also covered several comments up. If you don't have anything new to present, I'll bid you good day.

  • source
  • parent
  • context
  • [–] 3 points 2 days ago

    I think there is some pride and value in setting things up in a way that reduces friction.

    I myself am of a similar opinion tho. Someone maintaining a thing as a hobby doesn't owe me shit. If it's too tedious to figure out, I'll move to another solution. It's really nice, when I get the option of a consumable bundle. But if they can't, don't like or simply don't care for ease of consumption — tough luck for me I guess.


    tl;dr

    Don’t look a gift horse in the mouth

  • source
  • parent
  • context
  • [–] 0 points 2 days ago

    Over on programming.dev, in this comment, you posted a chatbot's analysis of the flake. You then deleted it, perhaps after reading it and realizing that it was inane and uninsightful. At the same time, you're over here getting into a fight over the word "clanker", which you used to refer to the very same chatbots whose output you uncritically posted.

    I understand that you have some inner turmoil, and that your behavior is merely an external facet of your emotional processing. However, I think that it's important to understand that the chatbot never has any ideas; indeed, it cannot ideate or cogitate. As such, your fencesitting is not gaining you any actual insights. To the current example, before you deleted the chatbot-output comments, I noted that the biggest and most insightful takeaway that the chatbot found was the ability to build a NixOS configuration locally, SSH to a remote host, copy the configuration to that host, and switch that host to the new configuration without rebooting; this is a standard part of NixOS which is in the man page, the official wiki, and the unofficial wiki. I get why you deleted the original comment, but I don't get why you posted it unless you genuinely believed that it was full of "hallucinate[d] useful ideas."

  • source
  • parent
  • context
  • [–] 2 points 2 days ago (1 child)

    Does this use the same config performance settings able CachyOS? I don't use Cachy anymore but when I did, the minimal performance improvement didn't just come from using the kernel. There were configurations that also helped with this.

  • source
  • view more: ‹ prev next ›