No, it doesn't. Bone marrow regenerates, the same is for blood (which is a tissue). One thing is donating organs, other is donating tissues. While you may define an organ as a "set of tissues" (therefore, skin). In "transplantation slang" is commonly referred to "organs" as not regenerating ones, i.e. kidneys, heart, etc.
As long as you can't sell it, there is no price at it.
Nonsense. Saying that kidneys should be "commoditized" to avoid the black market it's like saying that slaves should be legal to avoid people travelling in a container.
In particular, kidneys can be transplanted from "dead" to living, and donning between living - even inside your family - is very restricted (at least in Uruguay). Although one case may be very altruistic and reasonable, there are thousands of subtle situations which are horrendous, and all the donning process will be heavily affected.
It's a moral statement: you can't put price on life or your body.
Improving the donors rate with policies is a better way to go and it hasn't reached its limits so far.
A subtle attack may be by making bots stop indexing it or using SEO practices to lower it enough so it would become unsearchable, and therefore, non-existent.
A subtle attack may be by making bots stop indexing it or using SEO practices to lower it enough so it would become unsearchable, and therefore, non-existent.
> In the real world where not everyone is a programmer people don't feel restricted by proprietary software. Only in some hypothetical ivory tower manned by RMS are non-developers restricted by proprietary things.
This is irrespective and has nothing to do with the point. I can figure out tons of adjectives to """describe""" you. Also, I don't know why people think their reality is "the real world" and extrapolates it to others' "real worlds".
It is not about being a dev or not, it's about a system which someone relies on (even a society with Google) and ensuring its continuity and the best for all. If you ensure it, people will recognize your work and the money will come.
> While writing that list of open source software I use, I realized that only Emacs and GCC are GPL. Why is it that the most popular open source software is not GPL licensed? If the GPL encourages and fosters collaboration why is the MIT, BSD, and MPL licensed software more active and popular? It almost seems as if removing the restrictions from the GPL encourages collaboration. The Linux kernel is a notable exception, so I'm not saying this is 100% true, but the evidence seems to support it in many cases.
A software is "good" independent of its license. Licenses don't fix bugs. If you measure by adoption, then you should conclude that Visual Studio is what has encouraged most of the software developing in the past - and I think it's true, but hasn't to do with licensing and business models.
Your evidence supports that many licenses are being used, and that's a good thing. If you want to do things because many people does them, then you should adopt the Chinese culture. We have a phrase here: "Eat Shit: Trillions of flies can't be wrong." (this is not about Chinesse culture, they have outstanding good things and others not so good).
It took about 10 years to the industry to understand that they could earn money with open source software. It was very hard to try to explain someone that he could do better with a different model. Now that the industry has "internalize" it, everybody loves open source. AGPL is the next step: there is room for improvement and you will probably (IMO) do better with a more sustainable model.
If your marketshare is based on amount of resources, then your position is sustained by entry barriers, not your skills.
If someone can gather the resources and do better than you, then it's better for all the market - not just you. What you do with AGPL is making sure that if it is based on your knowledge, you will be able to improve from who has already improved from you.
If you can't stand someone to do better than you and you can't learn from him, then you have personal issues - and those are holding back everyone. There is nothing bad in not being the best (I think is bad measuring success on money and market share, that's circumstancial) and if you are not willing to improve, then you are in the wrong place.
The same applies (IMO) to patents and industrial secrets. A patent is "public" industrial secret: while you know it, you must act as you wouldn't unless you pay. I think that is for lazy people, they want money for an idea from people who actually implement it - work. Open source is a good example about this.
A free market relies on perfect informatios on whatever technology is being used, otherwise, there is no real competition in the supply and you might end up with a captive demand.
Yes, most business models would need to adapted to this, it is not what most of the markets do. Think of the Nuclear Power Plant market (to be extreme and explain my view). There won't be many suppliers because of the activity, if you totally "opensource" the industry, you will still be buying plants and paying a lot of money - but you will be "safer" because you rely on it.
The same applies to software, there are big players who are willing to outsource and pay more (because is out of their core business or just don't have interests on the topic) if the supplier fully opens and doesn't lock in them. You will end up on a better and "fairer" position.
As we say here, "your freedom ends where others' start". You are not forcing anyone to distribute the software or do whatever they want to as long as you respect others' freedom.
What you are doing is not giving the power to restrict others if you distribute it so you keep it flowing. The only way of achieving freedom and equality is (IMO) to equally distribute power on all, so you will end up with the phrase at the beginning.
If you want to use that sense of "restriction", it is restricting power, not freedom. Restricting power is granting others their freedom.
You can't go to your college with an Uzi and start shooting classmates. Although you "can", it is not allowed.
Is the constitution restricting your freedom? NO, that's not your freedom, that's power on taking others' life.
Another example - a less extreme and more realistic one - is a judge (or a jury). Are they "freerer" than you because they can put you on jail? Is your freedom "less" than theirs? No, you have the same freedom, what they have is power over you in a circumstance already """agreed""".
If someone wants to build on top of it, if he can't find a link like some closed drivers do with GPL software, then they are improving it. If they use your code as a base, why don't give back?
Note that this only affects you when you provide the service (AGPL) or distribute the software (GPL).
As long as you don't distribute it and use it "internally" (as US Army and DoD does) you don't have to show the source. If you provide public access to the system, then you have to show the code. So, you become another giant to step on his shoulders.
As for money, you only need (IMO) the amount for doing what you enjoy, not more (it isn't a goal per se, it's a way, not a goal). If you want to have an empire and build a sphinx with your face on it, then you have a problem with your brain's reward system, not with money - nothing will fill you up (stop using cocaine! :D hahahah! =P)
Yes, I think so - especially with algorithms: math can't be owned.
On Google's implementation of them, yes, of course! This would have tremendous impacts and benefits for all.
I think your sarcasm came from "What happens with Bing? They are hungry!", and you can't understand the point inside that reasoning framework.
If Goog releases their algos, the would gain even a better position in the market.
All the society would benefit of controlling what makes you exists for others (if you can't google it, it doesn't exists), a storm of commits improving it would come (even fixing what makes that disgusting SEO practices) and you will have a viable alternative to Google: you will be able to choose.
Can Microsoft manage an infrastructure as big and efficient as Google - tuned over the years for a SE, with thousands of people with expertise, experience, motivation and values? I think not.
If Goog releases under AGPL, if Bing uses it, they will be able to look at the implementations, its improvements and merge them "back".
If Microsoft doesn't want to use the code, then they will have to spend years developing the same (and find the right people for it - which are already in Google). In that timeframe, Goog will keep improving - otherwise, a better alternative will eventually surpass them.
Yes, the can plain steal and don't enforce the license, but, Microsoft stealing?!?!?!? =P
This model relies on two things:
- You are willing to work continuously on it because it makes you happy
- You want to be on top because of how you do your job, not because you know a secret
- Money is irrelevant to you: you live (luckily) between 80 and 100 years, and suppose that you are on your 30s - if I was given 100 million dollars, I will probably not be able to spend them as I won't have time to do it (think Larry Page or Billionaires, but at a smaller scale). If you get a huge amount of money, after some years of "livin; la vida loca", would you return to code?
I agree with everything but the "core business" stuff and the MIT License.
The same principles apply to your core business - independent of what it is (not only GitHub).
By opensourcing all of your business, you will gain all the synergy you mentioned (i.e. libgit2) within your core.
Your competitors will benefit from it, but they won't be a challenge to you as long as they don't have the passion and insights from your team. If they can find a way to do better than you with that knowledge (expressed as software), then your position in the market is based on imperfect information (and therefore, monopolization power).
Although you may have everything to start a DVCS frontend, it is not an easy task which doesn't rely only on software: you need the ability to understand the infrastructure needed for the problem and maintain it at a reasonable speed - armies of proficient developers extending and fixing bugs, armies of sysdamins, coordinate them, decide adequate directions, etc.
Besides that, you need passion about what to do in order to keep kicking asses. Without it, it is not sustainable in the long run. Think about Launchpad, I think they add extra functionality to bzr than GitHub to git, yet people still sticks to GitHub. Why?
Also if you opensource your "core", people will need also customizations, so your competitors can become your clients where you provide developing to them - they may target other niche that you can't or your are not interesting.
This is where the license comes in: the best way of achieving this is by using AGPL3.
With AGPL3, you make sure that everything you gave it won't be restricted to others - as you haven't restricted anyone by opensourcing it.
You are not restricting others' freedoms, they can do whatever they want with the software. When someone closes the source, it's restricting others freedom, not his. What you can't do with AGPL is taking away others' freedom and right to know what they are using.
If someone improves it, then it will come back to you, and you will be able to improve from others as they improved from you.
The MIT license is good, but it doesn't close the loop and may have leaks, :D heheh!
As long as you can't sell it, there is no price at it.