[–] 2 points 3 weeks ago

IMHO, the problem with deno was trying to be too different. That is it. De facto standard tooling and existing knowledge about server side JS/TS goes out of the windows. Don't get me wrong, it does force NodeJS to be more innovative but those friction is too big of a cost compared to myriad of example using NodeJS. So when Bun is trying to be 1-1 drop in replacement with added frail, everyone loves that

  • source
  • [–] 3 points 3 weeks ago

    Exactly. And that's before adding in all the "source available" code that's publicly available but not actually Free, let alone the leaked proprietary code that they've probably shoved into the training corpus willy-nilly, too.

  • source
  • parent
  • context
  • [–] 4 points 3 weeks ago

    The wording is weird. But the project (openslop) defines permissive as basically having a path for AI to enter the code. This lumps together both measured approaches like NetBSD's and fully embracing slop contributions in the same category.

    I think this only makes sense if you view AI contributions as a taint, something that threatens the licensing of a project. In that optic, it really is an all or nothing. But it doesn't help users choose among the options as much.

  • source
  • parent
  • context
  • [–] [S] 2 points 3 weeks ago

    I’m going to try it on my ThinkPad X250 this weekend. I managed to install Gentoo with a handbook printout 25 years ago. This can’t be that much harder or am I in for a rough surprise?

  • source
  • [–] 3 points 3 weeks ago

    That is good to know. I've also just checked the commits, and now I'm unsure if the LLM-related lines actually signified LLM use or just were copied from updated software changelogs. I will remove my above comment and stop with this topic until I learn more.

  • source
  • parent
  • context
  • [–] 3 points 3 weeks ago (2 children)

    There were more commits, the scanner basically checks the most recent history and stops, just to confirm that the project still allows LLMs. I don't have a laptop or good internet right now to clone the entire repo and grep logs.

  • source
  • parent
  • context
  • [–] 6 points 3 weeks ago* (1 child)

    But which? Creative Commons have a range of different restrictions some aren’t even GPL compatible, copyleft as per OSI or GPL would still impede on the source available code licensed under CC BY-NC and vice versa.

    And that’s forgetting all the blogs and books where no open license is given.

    Theft is theft. AI CEO’s should be in jail.

  • source
  • parent
  • context
  • [–] 8 points 3 weeks ago (6 children)

    In fact, it matches two of the "Permissive" criteria: generated code has been merged, and the policy defines conditions that allow such merges (approval by core). The list still recommends various software made by NetBSD developers as viable alternatives to slop projects, where appropriate.

  • source
  • parent
  • context
  • [–] 1 point 3 weeks ago (1 child)

    Biggest problem is proving where the code came from. Trying to pick out what software vibe code comes from is loke.trying to pick out a single hay strand from a pile of sharp broken glass and used needles. Can you do it? I'm sure with enough time you can, but at that point was the time spent worth it instead of learning how to be an actual programmer and/or developer?

  • source
  • parent
  • context
  • view more: ‹ prev next ›