3 ms·
It’s open source. You take ownership of it for your deployment and stop relying on continued free work. You can use llm to pull in updates as they are released
by pyrolistical 3mo ago
It’s open source. You take ownership of it for your deployment and stop relying on continued free work.
You can use llm to pull in updates as they are released. It’s not gpl, so you don’t need to publish your port
- ahartmetz 3mo agoYou don't even need to publish your port if it's GPLv3 as long as you don't publish the binary.
- sdevonoes 3mo agoThe companies I have worked for before all have used open source software like postgres, mysql, go, python, k8s, etc. 99% of the time we relied on free work; never contributed to these projects nor forked them for our own needs. I don’t think this behaviour is the unusual path tbh
- cyphar 3mo ago1. Nobody, not even the Googles or NSAs of the world do that. No single entity has the expertise nor resources necessary to maintain a fork for every open source project they use -- forking and maintaining Linux alone takes teams of people. And no, going full psychosis mode with LLMs is not going to save you. 2. This project is AGPLv3.
- imhoguy 3mo agoExcept Amazon (Linux, Elastic, RDS..)
- egorfine 3mo ago> going full psychosis mode with LLMs is not going to save you People in AI psychosis don't know that.
- megous 3mo agoForking and maintaining Linux does not take teams of people. I've been at it for > 10 years and maintained support for my 15 or so various SBCs/mobile devices, writing drivers, debugging, cleaning things up. It's a weekend project every 3 months + whatever you want to put in for development. And there are others doing it for projects like Armbian, openwrt, etc.