[–] 15 points 3 weeks ago (12 children)

I actually an agree an independent rust project would be really cool. If it was also GPL. I have yet to encounter any argument against GPL that doesn’t boil down to corpo boot licking.

You say “Even if it ends up being in a proprietary program, it’s better than not being able to use the code”. This is a bad faith argument. Everyone can use GPL code freely, the restriction is only that you must also publish under GPL if you publish. I’m sorry your favorite corporation can’t profit off community projects without giving back to that community… not. If GPL was a real problem BSD would have overtaken Linux ages ago. But it didn’t because GPL is good not just for the community but for the project. The only people that don’t stand to gain from GPL are corporations that want to monopolize the technology.

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

    Uh call it whatever you want but canonical pouring money and resources into development of corporate friendly licensed clones to existing tools so they can avoid copyleft restrictions in the future is not good. I never understand when people feel the need to defend corporations obviously harmful behavior.

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

    Because Canonicals real goal is to move Ubuntu entirely to corporate friendly licensing under the pretense of migrating to rust. Obviously they leave the original untouched, it’s a matter of adoption. Without the oxidization argument nobody would have gone along with Ubuntu just deciding to do a clean room implementation of gnu tools in corporate friendly licensing, by making it about oxidation they are able to manipulate a large portion of the rust community into contributing/supporting their license laundering.

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

    What kinda dependency hell? I’ve been running my jellying server with it installed via pacman for over year and never had any problems. I admit I’ve also not messed with docker much in general but I assumed that would be more annoying cuz it would have to be updated separately and such

  • source
  • parent
  • context
  • [–] 10 points 1 month ago (1 child)

    Cool project idea! Some questions:

    It seems the project currently exclusively watches docker related stuff. Is there any plan to watch services more broadly? Most of my stuff is running directly on the machine as a systemd service without any container (probably bad practice sue me). I’m not sure how feasible it would be to chase down everything that’s supplying a local host endpoint tho.

    What’s your AI workflow like? What model, what harness etc

  • source
  • view more: ‹ prev next ›