Earlier quoted context omitted.
Bun was rewritten for software used by millions.
Mechanical translation.
It was done with LLMs.
I changed my license
71–80 of 193 posts
Re: I changed my license
#72[deleted]
Re: I changed my license
#73For FOSS I personally prefer Apache 2.0 license, as 10 years from now I have no idea what people will need for their projects. Personally, it makes me happy if people can make a business using a bit of my work. Just don't redirect commercial support tickets onto community projects, or get neglected customers to contact authors. The way I see it... is symbiotic commercial relationships are important, as people can get…
I think people getting time sponsored working on FOSS is quite rare. Would like to do that myself, but instead I just develop in my free time.
You mean you have never written or used FOSS applications at work?
I find that very surprising, but I have seen some shops practice clean room coding policies. =3
Re: I changed my license
#74> We won the debate, and gained little for users or developers. All that our efforts did was to make it easier for big corporations build things more cheaply and for billionaires to become trillionaires. As a long-time developer and consumer of OSS I have to disagree. Open-source software has had an enormous effect on the world, and that... was kind of the point? When we licensed things as MIT we knew that corporatio…
The complaint here is, that those business are not necessarily "bringing people into the community", unless you are talking about passive users, who do not contribute. The businesses simply use the stuff built at no cost to rake in big money, while the person, who did the actual work does not see a cent. This is different with copyleft licenses like AGPL. Only that many businesses are so afraid of contributing anything at all, that they often don't want to use AGPL or even GPL licensed software.
Re: I changed my license
#75Perfect, I've been looking for a license I can get behind for new projects. I just made a few tweaks https://aeupl.org/
Re: I changed my license
#76Earlier quoted context omitted.
Looks nice. Two main differences: - BUSL is OSI-approved and listed in SPDX, so corporate lawyers won't be scared away by it: https://spdx.org/licenses/BUSL-1.1.html - With BUSL the restriction is revenue-based. You can still create competing products, but would have to pay a licensing fee.
> BUSL is OSI-approved Of course it isn‘t.
I was a bit surprised to read that there was an OSI-approved license with usage restrictions and wondered if I had missed the memo. But you seem to be correct and it's not OSI-approved and therefore is not generally considered to be an open source license.
Re: I changed my license
#77>All that our efforts did was to make it easier for big corporations build things more cheaply and for billionaires to become trillionaires. This is not true. Open source is fundamental to how easy users can create software in the LLM era. Users and developers have gained tremendous value. Saying they have gained little is simply false. And it's a good thing to make it possible for big corporations to make things che…
Rather feels like post LLMs being everywhere, salary levels for developers are dropping left and right. Where did we gain value?
Re: I changed my license
#78What are people's thoughts/experiences about dual licencing? Eg: is there a clean way to dual license such that hobbyist, and exploratory work (eg: a proof of concept done in a commercial setting) are allowed, but using it in production requires a fee? If you've done this, has it been successful? Obviously there's been many projects relicense over recent years (terraform, redis, etc) - but it's less clear to me if th…
I think it definitely hurts adoption. No hobbyist or experimenter wants to delve into legalities head first by first having to understand the licensing terms of software, whereas permissive licenses like MIT and Apache 2.0 are easily-understood and familiar. The solution is probably to be more selective what you're open sourcing if you're planning to build a business. And what you open source, you do it under a permi…
"The solution is probably to be more selective what you're open sourcing if you're planning to build a business."
Fully agree, FOSS maintainers are - in the grand economic scheme of things - beggars high on altruism. The whole model of FOSS from the position of a non-corporate sponsored developer was already broken and with the advent of AI is now most probably broken beyond-repair. Buy-me-a-coffee with a <0.01% hit rate compared to open feature requests/gh issues on some of the more popular projects out there, all while companies like atlassian - using FOSS to run their business on for free - can charge 50k EUR for a single 1h migration call. Time is the most valuable resource one can waste, something you get to realize once all the mental gymnastics wear off(either by itself or due to less fortunate life situations)
Re: I changed my license
#79What are people's thoughts/experiences about dual licencing? Eg: is there a clean way to dual license such that hobbyist, and exploratory work (eg: a proof of concept done in a commercial setting) are allowed, but using it in production requires a fee? If you've done this, has it been successful? Obviously there's been many projects relicense over recent years (terraform, redis, etc) - but it's less clear to me if th…
No success yet, but I recently found BUSL - used by Terraform: https://en.wikipedia.org/wiki/Business_Source_License It stops companies from building high-revenue products for free, while not being as scary as AGPL/LGPL from the business perspective, and completely unrestricted for everyone else (despite not being technically an open-source license).
Once you decide on a non-free license, in the FSF sense, in the DFSG sense, and in the open source sense, does the details of the license matter much? You want as many people to pay as possible, and you do not wish for others to compete with you providing this software.
It's pretty much a standard non-free commercial license, which exact wording will matter only to purchasing department of your customers. It will be inconsequential to the broader open source community. Literally thousands of those exist and the specific wording matters very little.
Re: I changed my license
#80What are people's thoughts/experiences about dual licencing? Eg: is there a clean way to dual license such that hobbyist, and exploratory work (eg: a proof of concept done in a commercial setting) are allowed, but using it in production requires a fee? If you've done this, has it been successful? Obviously there's been many projects relicense over recent years (terraform, redis, etc) - but it's less clear to me if th…
If you are trying to monetize your software, the biggest factor is whether or not your customer trusts you.
MIT and source out on GitHub is the easiest way to build trust. You will find that some people simply "steal" your work in this arrangement, but much like with movie piracy I don't think they ever intended to compensate you or anyone else.
So, we wind up alienating all potential customers because we are so worried about preventing ideological crime.
People will steal your ideas and they will get away with it. The more you react to this in first order terms, the more it will destroy you.
Most money in software is made with support contracts, not the initial sale.